Content Type
Research
Within the Content Type facet, Research 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.
History
Demi Getschko and the Country Code That Arrived Before Brazil Spoke TCP/IP
On 18 April 1989, `.br` entered the DNS root while Brazilian academic networks were still speaking BITNET, HEPnet and other protocols. Demi Getschko's part in that sequence reveals a neglected infrastructure skill: securing a durable name, accepting responsibility for it and…
Story
BCAP’s Prize Entry Preceded Training. Its Outcome Receipt Has Not.
The WSIS Prize submission window closed two days before BCAP’s published professional-development start window opened. The project won in July and is still listed as ongoing through 2027. The award may be sound; the public record still needs to say which finished phase and which…
CASE FILE
The Private Number Was Valid. The Instruction Was Still Unowned: RFC 9752
A vendor payload can cross a stateful PCEP session with a real enterprise number and perfect framing while leaving the decisive questions unanswered: who published its meaning, what the PCC was allowed to do, what the device installed, and what the traffic experienced.
IETF
A Signed Epoch Marker Is Not a Universal Clock
Remote attestation needs a way to reject stale evidence even when an attester has no dependable real-time clock. The RATS Epoch Marker proposal supplies a signed coordinate from an Epoch Bell, but the signature proves only what that Bell emitted. It does not make the marker a…
CASE FILE
The Message Continued. The Constraint Went Missing: RFC 9753
RFC 9753 lets stateful PCEP peers keep working when selected entities are optional. That is a useful availability mechanism. It is not evidence that the ignored meaning survived, that the replacement LSP is equivalent, or that forwarding remained safe.
IETF
The Template List Was Present. The Intended Configuration Was Not Yet Proven
Revision 03 of the YANG configuration-templates draft turns list order and ancestor depth into configuration semantics. Reconstructing the intended tree is therefore possible only from a complete, same-version evidence bundle—and even a perfect reconstruction stops before…
IETF
Immutable to the Client Is Not Immutable in Time
A proposed YANG metadata annotation lets a network-management server identify system configuration that clients cannot change. Its name—`immutable`—is accurate only across a particular control boundary. The server can still create, update or delete the underlying system…
History
Ginny Strazisar and the Gateway Code That Traveled Before the Packets Did
The celebrated packet path began with a less cinematic journey: an engineer arriving at a site where the machine for her software was not yet ready. Virginia “Ginny” Strazisar Travers helped turn internetworking from a protocol idea into installed boundary equipment at BBN…
IETF
An Uncacheable Attribute Does Not Prove the Client Cache Is Empty
NFSv4.2 is gaining a way for a server to mark a file's data as unsuitable for ordinary client caching. That is useful policy vocabulary. It is not an observation of what any particular client has already seen, retained, revalidated or committed. Operators need both records before…
CASE FILE
The Server Accepted the Message. The User Still Could Not Find It.
RFC 9755 gives IMAP a precise UTF-8 handshake, but a capability banner and a successful APPEND are only the first receipts in a much longer chain from stored octets to usable mail.
History
Karen Sollins and the Delayed ACK That Made Every Packet Appear Twice
TFTP could deliver a file correctly and still damage the network carrying it. In the failure later called the Sorcerer’s Apprentice syndrome, one delayed acknowledgement could start a feedback loop in which every remaining data block and acknowledgement travelled twice. Karen…
IETF
A Planned Boundary Change Needs Two Validation Times
A civic boundary can change at midnight while every address stays physically where it was. The database problem begins earlier: operators need to prepare records for the new administrative reality without pretending that a forecast is already the truth. An active ECRIT…
History
Elise Gerich and the Backbone Shutdown That Needed a Dress Rehearsal
The NSFNET backbone did not disappear when someone threw a master switch. Its retirement was a year-long exercise in proving that exchange points, commercial providers, route servers, databases and regional networks could stand without the system they were replacing. Elise…
IETF
The Highest-CoS Probe Does Not Measure Every BIER Service
A green continuity result can be both correct and dangerously overinterpreted. RFC 9974 allows an operator, in a particular composite-flow case, to test the highest Class of Service and derive the continuity state of lower classes. The sentence is operationally useful. It is not…
CASE FILE
The Receipt Behind the Cipher: What RFC 9771 Makes AEAD Buyers Prove
An authenticated-encryption label can be correct and still leave the decisive deployment question unanswered. RFC 9771 gives operators the vocabulary to distinguish a mathematical property, an implementation convenience, and an interface with different security rules. The next…
IETF
The Requirements Were Written. The Solution Was Not Proven
Revision 14 gives YANG versioning work a disciplined list of obligations: evolve modules without detonating dependency graphs, disclose compatibility, protect old clients, clarify retired nodes and explain migration. Its value is the questions it preserves. A requirements…
History
Mary Ann Horton and the Dial-Up Network That Had to Publish Its Own Map
Before an email address became a name, it could look like a set of directions. Every exclamation mark told a queued message which machine to visit next — and every omitted or stale hop could leave it stranded.
IETF
The eap.arpa Lane Must Close After Provisioning
The dangerous moment in device onboarding is not always the first packet. It can be the quiet minute after a certificate has been delivered, the dashboard has marked provisioning successful and the temporary access rule is still alive. RFC 9965 gives an uncredentialed EAP peer a…
History
Jean Armour Polly and the Internet Connection That Still Needed a Librarian
In 1992, “going online” at a public library did not begin with a browser. It began with a desk computer, communications software, a modem, a telephone line — and somebody who could turn that fragile stack into a public service.
IETF
The Router Remembered a Listener. The Receiver Saw Nothing: RFC 9777
MLDv2 gives an IPv6 router a disciplined account of multicast interest on one attached link. The danger begins when that local, aging account is promoted into proof that an authorized application still wants the traffic—or that the traffic arrived.