Primary Domain
Internet Standards
Within the Primary Domain facet, Internet Standards intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
IETF
Joyce Reynolds and the Assigned-Numbers RFC That Stopped Being the Registry
In 2002, Joyce Reynolds gave an old standards document a more honest job. RFC 1700 would remain a durable record of what the Assigned Numbers tables looked like in 1994, but it would no longer impersonate the changing registry that engineers actually needed.
IETF
Paul Mockapetris and the Authoritative Bit That Did Not Cover the Whole Reply
One DNS response can carry an authoritative alias, a cached destination and helpful address records under a single AA flag. The bit has done its job; the database that stamped the whole packet “authoritative” has not.
IETF
Jim Schaad and the Key ID That Was Only a Hint
Two keys sit in the same verifier under the same short label. The message supplies that label, the first key is tried, and a dashboard turns the result into the name of a device. Jim Schaad’s COSE specification draws a harder boundary: the label is a search hint; identity and…
IETF
Donald E. Eastlake 3rd and the RBridge Nickname That Could Not Be a Permanent Identity
Two TRILL campuses join, and the same 16-bit nickname suddenly has two claimants. The number has not lied; the inventory that treated it as a permanent device identity has asked it to carry evidence it was never designed to hold.
IETF
Patrik Fältström and the ENUM Answer That Did Not Complete the Call
The number resolved. A signed DNS answer yielded a URI. The phone still never rang. Patrik Fältström’s work on ENUM is most useful when those three facts remain separate.
IETF
David Harrington and the SNMP Context That Did Not Identify the Operator
The command named an engine, a context and an entity with precision. None of those fields said which human had chosen the change. David Harrington’s SNMP architecture makes that absence visible rather than filling it with an assumption.
IETF
Bernard Aboba and the EAP Method That Did Not Grant Network Access
The credential was valid and the authentication method finished cleanly. Yet the controlled port stayed closed. Bernard Aboba’s work on EAP explains why those two observations can coexist without contradiction.
IETF
Chris Newman and the Secure Mail Port That Did Not Authorize a User
Port 465 can require the conversation to begin with TLS, but it cannot decide who may send a message. Chris Newman’s work on secure mail access shows why transport, service identity, user authentication and authorization need separate receipts.
IETF
Keith Moore and the Encoded Word That Changed the Display, Not the Sender
Two ASCII header lines can open into the same accented name on screen. That visual agreement is useful, but it is the end of a decoding process—not a receipt for who sent the message.
IETF
Roberto Peon and the HPACK Table That Remembered Fields but Never Cached a Response
A small integer can recover a long HTTP field inside one connection. It cannot say whether a response is fresh, reusable, authentic or even stored anywhere.
IETF
Jon Callas and the OpenPGP Key ID That Never Identified One Unique Key
An eight-byte label can help a verifier find a key. It cannot make the candidate unique, bind the key to a person, or authorize the action that follows.
IETF
Nathaniel Borenstein and the Base64 Encoding That Never Promised Confidentiality
A Base64 string can cross a transport that would damage the original bytes. It cannot tell an operator who made those bytes, who may read them, whether they changed, or whether opening them is safe.
IETF
Cyrus Daboo and the PARTSTAT=ACCEPTED Status That Did Not Prove Attendance
An accepted invitation is useful evidence of a calendar decision. The standards Cyrus Daboo helped shape also show why it is not evidence that the invited person later appeared, stayed, listened, contributed, or completed anything.
IETF
Mark Crispin and the \Seen Flag That Did Not Prove a Human Read the Message
An email turns from bold to ordinary type, and a shared mailbox quietly acquires a fact: `\Seen`. The interface calls the message read. The server can prove that a flag changed. Between those statements sits the question Mark Crispin’s IMAP makes unavoidable: what, exactly…
IETF
Jonathan Rosenberg and the OPEN Status That Belonged to a Service, Not a Person
A green dot glows beside a name. A message goes unanswered. The apparent contradiction disappears once the dot is read at the level the presence standards actually describe: a communications service may be open to receiving a message while the human remains absent, occupied…
IETF
Ben Campbell and the Hundred-Percent Reduction That Did Not Prove Zero Traffic
The cleanest number on a Diameter console can be the most dangerous one. An overload report says `OC-Reduction-Percentage: 100`, and a post-incident slide turns that instruction into a finding: traffic fell to zero. Ben Campbell’s work on Diameter overload makes the narrower…
IETF
Adam Roach and the Terminated Subscription That Did Not End the Resource
A control-room tile turns red: `Subscription-State: terminated`. Someone closes the incident because the monitored resource is presumed gone. Adam Roach’s SIP event specification permits no such shortcut. The subscription is certainly over; the resource may still exist, remain…
IETF
Scott Hollenbeck and the Transfer Lock That Could Not Explain Itself
A domain-security dashboard finds `clientTransferProhibited` and turns its badge green. The code deserves some of that confidence: in the EPP domain mapping authored by Scott Hollenbeck, a transfer request must be rejected while the status is present. But the badge has answered…
IETF
Henning Schulzrinne and the Ringing Response That Arrived Before Anyone Answered
A caller hears a ring and begins to wait. On a SIP trace, an engineer sees `180 Ringing` and may feel that the network has confirmed the same event. The two impressions can coincide, but they are not identical. In the protocol co-authored by Henning Schulzrinne, 180 is a…
IETF
Mallory Knodel and the Censorship That Begins Before a Packet Is Dropped
A failed connection is the last frame of a longer decision. In the censorship survey co-authored by Mallory Knodel, somebody first defines what is unwanted, a system then recognizes traffic as belonging to that class, and only then does an actor interfere. Keeping those stages…