Open standards body with worldwide implementation impact.
Governance / IETF
IETF
IETF governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.
GlobalProtocol GovernanceInteroperability Risk
Protocol process and standards legitimacy.
Spec-to-implementation gap across vendors and operators.
Major standards shifts usually affect systems over 120d+ cycles.
Latest Coverage
Latest from IETF
1,098 articles
IETF
Jen Linkova and the Five-Minute Clock That Kept IPv4 on Call
The most revealing part of RFC 8925 is not that a device can decline an IPv4 address. It is that the refusal expires. A client asks for DHCPv4 option 108, a configured server returns a waiting time, and the client pauses DHCPv4 only until that clock runs out or the network…
IETF
The IETF’s $270 Remote Pass Does Not Set the Price of Participation
At IETF 126, a remote week pass started at USD 270. On the same registration path, the IETF offered an unlimited, confidential waiver with no eligibility test and no loss of interactive functions. Those are not contradictory prices. They are two institutional routes serving…
IETF
Warren Kumari and the Wi-Fi Link That Encrypted Without Knowing Who Was There
A public wireless network need not choose between a shared password and sending every nearby listener a readable copy of the radio exchange. RFC 8110's Opportunistic Wireless Encryption creates a different bargain: derive a fresh secret for each association, encrypt the local…
IETF
Álvaro Retana and the Prefix That Left the RIB but Kept the Link
An OSPF adjacency can remain full, its topology edge can continue to influence SPF, and packets can still cross the link even after the link's numbered prefix has vanished from remote routing tables. RFC 6860 makes that separation an operational tool. For Álvaro Retana, one of…
IETF
Acee Lindem and the LSA That Travelled Unread
In a mixed-version OSPFv3 area, a router can receive a well-formed Extended LSA, store it and relay it within the encoded flooding scope while understanding none of its optional meaning. RFC 8362 makes that behaviour deliberate. Acee Lindem, one of its five co-authors, helps…
IETF
IETF Executive Director Takes On a Legacy RFC Role
Jay Daley says he appointed himself Managing Director, IETF Secretariat, closing a vacancy in a role that still exists in IETF standards but whose work has long since spread across the LLC. The appointment may have no practical effect, as his report says, yet it exposes a useful…
IETF
Susan Hares and the Two Clocks of BGP Convergence
A router can finish explaining a new route before it finishes carrying packets over it. RFC 4098 names the first event in the control plane; RFC 7747 measures the second from outside the forwarding plane. Susan Hares co-authored both documents. Read together, they turn the word…
IETF
Enke Chen and the Best Path That Kept Its Seat
A BGP router can change its forwarding choice even when the challenger is no better by policy, path length, origin, MED, session type or interior cost. RFC 5004 asks a narrower question: if the only remaining reason to move is the remote speaker's lower BGP Identifier, why move…
IETF
David Meyer and the Address That Had to Ask Where It Lived
LISP lets an endpoint keep one identifier while its network attachment is described separately. That does not make location disappear. It moves forwarding into a chain of registered, resolved, cached, selected and reachable EID-to-RLOC state—and turns each link in that chain into…
IETF
Alan DeKok and the RADIUS Variant That Moved Trust into TLS
RFC 9765 is unusual not because it promises a clean break, but because it records a protocol author revisiting a choice he helped make: Alan DeKok's RADIUS/1.1 removes old packet-security machinery only where two peers explicitly negotiate a protected transport profile. The…
IETF
Joe Abley and the Trust Anchor That Had to Declare Where Trust Began
DNSSEC can prove a chain only after a resolver has decided where the chain starts. Joe Abley's work on the root trust-anchor publication format makes that first decision unusually legible: a signed file can prove where data came from, but it cannot order an operator to believe…
IETF
Vint Cerf and the Nine Exceptions Hidden Inside “Everyone”
Vint Cerf’s 2002 declaration that the Internet is for everyone is often remembered as a promise. Its more useful architecture lies in the next words: “but it won’t be.” Repeated nine times, that qualification turns universality from applause into unfinished work.
IETF
The IAB Can Set Architectural Conditions. It Cannot Set Child-Safety Law
Technical advice acquires borrowed authority one citation at a time. A regulator cites an architecture statement, a supplier cites the regulator, and a service describes the resulting product as though the design were required by law. By the time an age gate reaches a user, the…
IETF
Geoff Huston and the IPv6 Default That Withdrew Itself
For a decade, `/48` looked like the neat answer to a difficult IPv6 question: how much address space should an ordinary site receive? Geoff Huston helped write the document that withdrew that single answer without surrendering the protections it was meant to provide.
IETF
Ray Bellis and the DNS Connection That Became a Session
A TCP socket can remain open without anyone agreeing what state it carries. RFC 8490 made that distinction explicit for DNS: the connection is transport; the session is a mutually recognized set of rights, timers and obligations. Ray Bellis and his co-authors turned persistence…
IETF
The IETF NOC Is Volunteer-Managed Again. Its Authority Handoff Is Still Shared
Joe Clarke’s appointment as IETF NOC Lead restores volunteer management to the network that makes an IETF meeting function. It does not turn that network into a volunteer-only service. Community engineers, Linespeed, Meetecho, the IETF LLC and the IESG occupy different parts of…
IETF
Ray Bellis and the Proxy That Had to Forward the Unknown
A small gateway often presents itself as a helpful DNS interpreter: one address for the household, one upstream resolver, one place to cache an answer. RFC 5625, authored by Ray Bellis, starts from the more difficult premise. The gateway cannot know what DNS will mean after its…
IETF
IETF's Stand-In Draft Names the Successor, Not the Trigger
Picture a transfer panel with two circuits. One is marked for the IETF Chair; the other is wired to a named stand-in. The second circuit is ready, but the sensor between them is missing. The panel says power will switch “automatically and immediately” when the first circuit…
IETF
IETF's Chair-Delegation Draft Reaches the IAB Seat
A notice on a public page can say who will chair a meeting, for how long, and on whose authority. That may be enough to move work without moving office. It is less obviously enough when the same notice says another Area Director now holds the IETF Chair's full membership on the…
IETF
DNS Serve-Stale Lets the Recursive Resolver Decide When Expired Data Is Better Than Failure
A DNS record reaches the end of its TTL just as every authoritative server becomes unreachable. The old address may still preserve a working service—or it may lead users back to infrastructure the zone owner meant to retire. Serve-stale keeps resolution alive by giving the…
Member Unlock
Restricted Profile Intelligence
Login is required to unlock full profile briefings and deep-dive sections.
Strategic Circle Briefing
Join to unlock strategic briefings after signing in.
Join Strategic CircleLeadership Alliance Briefing
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance