Profile
Briefing
Briefing profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
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.
CASE FILE
The Token Opened the Door. The KDC Still Had to Admit the Member: RFC 9594
An access token can be authentic, correctly scoped and still prove no group membership at all. RFC 9594 makes that distinction operational: permission is issued at one authority, admission is completed at another, and usable group state exists only after a further exchange.
North America Regional ISP Trends
Lumen sells five-minute bandwidth on a contracted port
Lumen can now raise or lower enterprise internet capacity in minutes, but the speed of that control begins after a qualified physical port is ready. Intelligent Internet turns connectivity into a two-part purchase: a durable access commitment underneath and software-priced…
History
The Hierarchy Was in the Address. The Router Did Not Read It: RFC 2374
RFC 2374 divided an IPv6 address into a public hierarchy, a site hierarchy and an interface identifier. Then it stated the more important rule: routers would match prefixes on arbitrary bit boundaries without knowing that internal structure. The labels organised allocation.…
History
The Codec Had a Name. The Decoder Had Not Arrived: RFC 2361
In 1998, the Internet learned how to point at multimedia formats that had grown up somewhere else. RFC 2361 carried Microsoft's WAVE numbers and AVI FourCC values into MIME's vendor tree. The bridge solved an identification problem. It did not ship software, inspect the body…
ICANN
A DNS-Abuse Check Meets the Boundary Between Sister Registrars
A new public comment asks ICANN to look past a registrar's individual accreditation when the same company controls another registrar. The question is not whether every domain sharing an attribute is suspect; it is which institution must investigate an evidenced campaign when a…
CASE FILE
The Tao Was Retired. The Web Page Inherited the Change-Control Problem: RFC 9592
Two engineers can follow the same official IETF link six months apart and both truthfully say they read the newcomer guidance. They may not have read the same words. That is not an argument for freezing the page. It is the reason a living page needs a receipt.