Content Type
Briefing
Within the Content Type facet, Briefing intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
ICANN
Ghana’s DNSSEC Rate and Nigeria’s Signed Zone Are Different Kinds of Progress
ICANN’s latest account of African DNS security puts mobile-network resolvers beside a country-code registry. The gains are real but belong to different operators and measure different parts of a secure lookup.
CASE FILE
The Domain Was Canonical. The Local-Part Was Not Normalized: RFC 9598
Two email addresses can look identical on a screen and still name different certificate identities. RFC 9598 makes that uncomfortable result deliberate: prepare the domain under IDNA2008, preserve the UTF-8 Local-part exactly, and never let visual similarity stand in for byte…
History
The Guaranteed Circuit Began with an Unguaranteed Message
In August 1998, RFC 2379 confronted a small architectural embarrassment inside RSVP over ATM: the control message requesting reserved service was supposed to travel first across the ordinary best-effort path. That choice was not a contradiction to be hidden. It was a disciplined…
Europe and Middle East Datacenter Trends
VIRTUS closed £2.45bn of funding. £1.2bn is identified as green capex
VIRTUS Data Centres has secured a large committed financing framework for growth. Its value will be decided after the announcement: by what is drawn, which eligible projects receive the green-capex money, and how quickly permits, grid access and construction become live IT load…
History
The Envelope Reached the Area. The Application Still Had to Believe It: RFC 2370
RFC 2370 gave OSPF a reusable envelope for information the base routing protocol did not itself define. The envelope could be scoped, flooded, acknowledged and stored with ordinary link-state machinery. That success stopped at a precise boundary: the receiving application still…
IETF
The exporter saw a QUIC field. It did not see the whole connection
IPFIX can give operators a common vocabulary for QUIC observations. It cannot turn one configured vantage point into a complete connection, application or outcome receipt.
History
One Record, Five Different Directories: RFC 2378
RFC 2378 described a people directory in which a field could exist without being discoverable, be discoverable without being searchable, be searchable without being returned, and be editable without being changeable over the network. The important invention was not a phone book.…
CASE FILE
The Claim Was Visible Before It Was Trusted: RFC 9597
RFC 9597 lets a COSE entity expose selected CWT claims before decryption or without an attached payload. That convenience can guide key discovery and routing, but it creates a dangerous interval in which a claim can influence the system before the system has earned the right to…
IETF
A CCF Receipt Draft Now Names the Proofs Its Registry Number Would Need
The latest IETF text corrects a missing half of its registration request. It does not yet put a new CCF algorithm or its proofs into IANA's public tables.
History
The Link Wrote the Message. The User Still Had to Send It: RFC 2368
RFC 2368 turned a web-era address link into a compact message template: recipient, selected headers and even a short body could arrive prefilled. Its decisive safeguard was the remaining gap. Resolving `mailto:` created a draft, not a transmission, and the user still owned the…
History
The Identifier Looked Like Email. It Was Not a Mailbox: RFC 2377
RFC 2377 tried to make LDAP naming deployable by borrowing names the Internet already had. Its most revealing warning concerned a value that looked perfectly familiar: `uid=mailbox-shaped-identifier` could name a directory entry without being a working email address. Reuse…
IETF
The window grew. The path did not promise the next burst
A congestion window is a sender’s control state, not capacity booked from the network. That distinction matters most when the application or receiver has left much of the window unused.
Europe and Middle East Regional ISP Trends
Melita’s Epic deal asks whether scale can replace an independent rival
Melita says buying Epic would create the scale to invest in Malta’s fixed and mobile networks. The harder test is what replaces Epic’s independent choices—as a mobile quality leader, a retail price setter, a buyer of fixed access and a small network builder—if those choices move…
CASE FILE
The Header Named the Object. It Did Not Authorize the Action: RFC 9596
A protected type label can stop one COSE entity from masquerading as another. It cannot tell an application that the payload is true, that the signer was entitled to send this class of entity, or that any requested action should occur.
History
The Envelope Overruled the Document: RFC 2376
RFC 2376 gave XML two places to declare its character encoding: the transport envelope and the document itself. In one common case, a missing value outside the document defeated an explicit declaration inside it. The history is a compact lesson in where protocol authority…
CASE FILE
W3C Approved Two French WCAG Translations. Their Pages Still Say Candidate
Two newly updated accessibility translations have two status labels on the same W3C pages. The difference is small in typography and large in document control: an adopting organization needs to know whether it is reading a candidate for review or the version W3C has authorized.
History
The Manager Deleted the Row. The Circuit Could Still Exist: RFC 2366
RFC 2366 gave operators a common SNMP view of multicast over ATM. Its most revealing rule was not a counter or an address: a client, server or MCS row could disappear while associated virtual-circuit rows still existed or were in use. The management model could forget a parent…
Story
AFRINIC Asked Quiet French Readers to Speak. The Survey Opens in English
AFRINIC wants its next policy webinars to answer the barriers that stop people from posting to RPD or taking a PPM microphone. The 23 September invitation is unusually direct about seeking those quiet voices. Yet the advertised French route returned the English landing page…
History
The Group Number Stayed the Same. The Membership Did Not: RFC 2375
RFC 2375 gave early IPv6 multicast services durable names across several scopes. It also drew a line that operations still depends on: the same group number at another scope is another group, and a node has to join it separately. The registry named the destination. It did not…
IETF
BTPU could repeat every segment. It still could not say the bundle arrived
On a one-way link, sending another copy can improve the odds. It cannot manufacture the missing observation at the receiver, or carry that observation back.