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.

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,017 articles

IETF
An Expired Internet-Draft Is Not a Rejected Proposal
The standards register had only two columns: document and outcome. Beside an Internet-Draft, a reviewer had copied the Datatracker label `Expired` and entered “Rejected by the IETF.” No rejection notice was attached. There was no adoption call, consensus record, Last Call, IESG…

IETF
An RFC MUST Without a Subject Is Not an Audit Finding
The compliance sheet looked decisive: “RFC 8200 — MUST — failed.” It named no component, packet condition, conformance profile or test. It did not say whether the cited sentence governed a sender, receiver, router or operator. A capitalized word had become the entire finding. The…

IETF
The Packet Arrived Last. That Does Not Mean the Event Happened Last
In a wraparound test, a CoAP server sends one notification just before its Observe value rolls over and another just after. The newer datagram reaches the client first. The older one has been sleeping in a queue inside the network and arrives second. A client that sorts the two…

IETF
Jana Iyengar and the Connection That Outlived Its Address
A QUIC connection can continue when a device changes networks, but the old session cannot lend every old assurance to the new path. RFC 9000 preserves connection state narrowly, then demands fresh evidence for reachability, sending limits, congestion, ECN and privacy.

IETF
Sally Floyd and the Test That Throughput Alone Could Not Pass
A faster flow can be a worse network result. Sally Floyd’s work on congestion-control evaluation shows why a headline rate must be tested against delay, loss, fairness, instability, difficult paths and the traffic it displaces before an algorithm earns a wider deployment.

IETF
Jeff Tantsura and the Intent That Was Not Yet an Outcome
The system has accepted a clear instruction: keep a protected network path available. It translates the goal, changes lower-level settings and returns success. Hours later, the protection has disappeared after another change, while the accepted intent remains exactly where it…

IETF
Linda Dunbar and the Directory That Must Not Invent a Neighbour
A virtual machine moves between racks, but an edge switch still holds yesterday's answer: the address is reachable through the old location. The reply can be perfectly formatted, delivered by an authenticated channel and still send traffic to the wrong place. Linda Dunbar's…

IETF
Hannes Gredler and the OSPF Link That Had to Drain Both Ways
An operator makes one end of a circuit prohibitively expensive, watches routes leave, and calls the link drained. Yet packets can still enter from the neighbour because OSPF does not advertise one indivisible circuit: each router originates its own directional state. Hannes…

IETF
John Scudder and the BGP Session That Had to Declare Its Capabilities
Two routers may complete a TCP connection and still be unfit for the BGP job expected of them. One may understand an optional extension that the other has never implemented; both may understand it while only one admits support in the OPEN message; or an older peer may reject the…

IETF
Ketan Talaulikar and the Prefix That Kept Its First Router's Name
An OSPF prefix can cross an area boundary without losing reachability and still lose part of its history. The new LSA names the Area Border Router that relayed it, not necessarily the router that first originated it. RFC 9084, edited by Ketan Talaulikar with four co-authors, adds…

IETF
Tony Li and the Four-Byte Envelope That Refused to Rule the Payload
A GRE tunnel gives a packet a second address without taking away the first. The outer header decides how the envelope crosses an underlay; the inner header still decides what happens after the envelope is opened. Between them, the smallest GRE header can occupy only four octets.…

IETF
Acee Lindem and the Router That Had to Remember Rebooting
A valid signature can authenticate an old packet perfectly. That is the danger. If an OSPF router restarts and forgets which authenticated packets it has already accepted, a recording from yesterday can arrive wearing a correct digest and present itself as new. RFC 7474 makes…

IETF
Enke Chen and the Route That Outlived Its Session
A BGP session can disappear while the forwarding state learned through it still works. RFC 9494 permits some of that old state to remain far longer than ordinary graceful restart—but it does not call the state current. It marks the route, lowers its preference, limits where it…

IETF
Susan Hares and the Route That Authorised the Filter
A reachability update tells a router where packets may go. A FlowSpec update can tell it which packets to slow, discard, remark or redirect. That change in consequence makes authority—not syntax—the hard part. Susan Hares's documented work on the revised FlowSpec standards helps…

IETF
Bruno Decraene and the Discipline of Draining Before Shutdown
A planned BGP maintenance window is not a surprise failure. Yet an operator who closes the session first can make it behave like one: the old routes vanish, the network begins searching, and packets arrive while the replacement path is still becoming usable. The more disciplined…

IETF
The IETF Moved Its Secretariat Inside, Not Its Standards Authority
From 1 August, the IETF Secretariat is organised as two teams inside the IETF Administration LLC, after an April transition from a conventional outsourced service to an employer-of-record arrangement. The change shortens the administrative chain, but the constitutional line…

IETF
RPKI draft proposes a separate credential for blackhole routes
RPKI draft proposes a separate credential for blackhole routes intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The IETF…

IETF
IETF makes the multihop BFD Echo ban conditional
Revision 02 of an IETF working-group draft redraws a safety boundary that has stood since 2010. Echo remains forbidden wherever an intermediate node could send the packet back early, but the draft now permits it when the path environment can exclude that shortcut.

IETF
IETF narrows the proposed BGP-LS inter-AS topology key
A one-line deletion in revision 38 changes the identity material proposed for inter-AS link advertisements. The practical question is whether producers and controllers can move to the narrower descriptor set without leaving duplicate half-links or losing separation between…

IETF
IETF formalises work on unicast local discovery
The DNSSD working group has taken ownership of a proposal that would let devices use a selected unicast server for local service discovery instead of answering every query through multicast. The proposed efficiency gain comes with a new dependency: the server-selection and…
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