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
Why IPv4 Fragment Offsets Count in Eights
An IPv4 Fragment Offset is not a byte number. Its 13 bits count blocks of eight octets, turning a compact header field into a coordinate that can span the protocol's full datagram size. That economy comes with a precise cost: every fragment that is not last must end on an…
AFNOG
AfNOG’s Proposal-Type Field Names Formats Without Defining Their Evidence
AfNOG’s 2007 call named three proposal formats without publishing format-specific evidence fields.
IETF
Every Cell Says Stop: RFC 9906 Completes ECC-GOST’s DNSSEC Retirement
Every affected ECC-GOST registry cell now says **MUST NOT**: RFC 9906 closes both the production and validation lanes, unlike RFC 9905’s SHA-1 compatibility transition. The result is not merely a recommendation to stop signing; it is a coordinated retirement covering signing…
Leaders
Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
A first IPv6 exchange can expose network state that steady-state reachability leaves invisible.
AFNOG
AfNOG’s 200-Word Abstract Cap Leaves the Required Signal Unspecified
AfNOG’s 2007 call capped abstracts at 200 words without stating what those words had to establish.
History
When IPv4 Identification Stopped Identifying Every Datagram
IPv4 still carries a 16-bit field called Identification in every header. Yet the current standard says that field has no meaning in an atomic datagram. The apparent contradiction records a deliberate narrowing: an identifier created to reunite fragments no longer has to pretend…
IETF
Stop Signing, Keep Reading: RFC 9905 Makes SHA-1 Retirement Asymmetric
RFC 9905 changes the DNSSEC operating rule at the algorithm-row level: the affected SHA-1 algorithms MUST NOT be used to create new material, while validator implementations MUST continue to support validation during the remaining installed-base transition. The result is…
History
The Attachment Named Its Type. The Local Machine Chose the Command: RFC 1524
A multimedia message could say what it carried, but it could not legitimately appoint the program that would open it. RFC 1524 placed that decision in a local `mailcap` policy—a small indirection that made new formats portable across mail readers while exposing exactly where…
IETF
Four Cells, One Trust Chain: RFC 9904 Moves DNSSEC Algorithm Policy into the Registry
A DNSSEC algorithm number has four separately governed recommendation cells: validator implementation, signer implementation, validation use, and signing use. RFC 9904 changes where that guidance is maintained, not the recommendation status inherited on day one.
History
The Message Arrived Intact. Its Reading Order Still Had Three Owners: RFC 1556
A mixed Hebrew-and-English line could survive every mail relay with its characters unchanged and still arrive as a different sentence on two screens. RFC 1556 named the missing contract: transport had delivered the sequence, but somebody still had to own its order.
History
Why TCP Options Needed Both an End Marker and a No-Operation
TCP made room for future capabilities inside a header whose total extent still had to be known before payload could begin. Two deliberately small option codes—End of Option List and No-Operation—helped keep that variable space parseable without making every sender lay it out the…
CASE FILE
The URL Found the Token Authority. It Did Not Make the Issuer Trusted
An ACME client can be told where to fetch an Authority Token without giving the ACME server any reason to trust the token’s signer. Revision 05 of the JWTClaimConstraints profile draws that line sharply, then builds a separate chain of receipts for issuer trust, exact constraint…
CASE FILE
The Shared Dictionary Saved Bytes. It Joined the Secret Boundary
A compression dictionary may look like a performance asset, but RFC 9841 makes it part of the decoder's effective input. Once exact dictionary bytes can change the recovered content—or reveal secrets through output size—the optimisation belongs inside integrity, provenance and…
History
The Repeater Had to Reply Before It Reset: RFC 1516
The management reply was designed to leave while the Ethernet repeater was still able to send it. Only then could the disruptive reset begin. RFC 1516 turned that small ordering rule into a durable warning: acknowledgement, action, completion and restored service do not share one…
CASE FILE
The Parser Accepted the String. The Protocol Still Had to Refuse It
A green check from a JSON parser can be the beginning of validation, not its end. RFC 9839 shows why a syntactically conforming envelope may still carry character content that no robust protocol should admit, preserve or silently erase.
History
The Internet Asked Who Would Have to Live With Its Next Protocol: RFC 1550
A utility meter and a wireless link appeared before any packet diagram. In RFC 1550, the search for a successor to IPv4 began by asking future users what the new protocol would have to endure—and by keeping the candidates temporarily out of the room.
CASE FILE
Both Instances Scored Eight. The Numbers Did Not Mean the Same Thing
Computing-aware traffic steering can compress a processor, a queue and a path into one convenient score. The new operational section of an IETF working-group draft makes the hidden condition explicit: before a selector compares two eights, every component must agree on how an…
CASE FILE
The Member Was Removed. Exclusion Still Needed Two Rekeys
A group controller can delete a name from its membership state in one administrative act. RFC 9838 shows why the cryptographic consequence is not equally instantaneous: the old key protects the first transition, the new key must protect what follows, and multicast delivery does…
Story
APNIC’s API Outage Notice Did Not Name the Registry API
One hyphen separates `api.apnic.net` from `registry-api.apnic.net`. APNIC’s 5 August incident notice named the first host and five affected member-facing or public services. Its published Registry API specification names the second host for authenticated changes to…
History
The Alarm Had to Wait Five Seconds; the Counter Did Not: RFC 1515
Two bursts of an Ethernet fault could enter the same five-second window. A manager might receive one alarm, poll a normal state a moment later, and still find that the transition counter had advanced twice. In 1993, RFC 1515 made those answers coexist because an alert, a present…