Strategic Circle Briefing
Join to unlock strategic briefings after signing in.
Join Strategic CircleGovernance / IETF
IETF
The IETF writes the protocols every network runs on. We follow the drafts, the working-group fights and the standards that ship, and explain what each one changes for operators before it reaches production.
GlobalProtocol GovernanceInteroperability Risk
Latest Coverage
Latest from IETF
1,656 articles
IETF
The Boundary Router Can Hide the Map. It Still Has to Deliver the Packet.
A new BGP-LS-SPF proposal would let a routing area keep its detailed links to itself while selling reachability to everyone else. That bargain has an awkward middleman: the boundary router must announce a distant prefix without showing the distant topology. The draft knows how to…
IETF
The Exchange Gave One Router Four Addresses. Who Owns the Map?
An Internet exchange wants to retire public IPv4 addresses on its peering LAN while a legacy member still expects an IPv4 next hop. A July IETF draft offers a workaround: the route server gives that member a private, client-specific address for the same physical neighbor, and the…
IETF
The IETF's Administrative Company Has One Written Prohibition, and the Rest Is a Process
RFC 8711 removes authority over standards work from IETF Administration LLC in a single sentence. What it says about the company's purpose, who may change the arrangement, and how large a contract can grow before the board must see it is either handed to another document or left…
IETF
Two Months to File an IETF Appeal. The Board Answers in 'a Reasonable Period'.
The Internet Architecture Board is the last stop for a complaint that the standards process was run improperly. Its rulebook measures the complainant's clock to the month — and leaves its own answer at "a reasonable period of time".
IETF
DNS Changed the Order. The Switch Rebooted.
A resolver changed where it placed CNAME records in an otherwise familiar DNS answer. Clients failed, and some switches restarted while resolving their time server. A November IETF draft chooses the old order for a very practical reason: the installed fleet has a vote even when…
IETF
The ROV Benchmark Stopped Its Clock Before the Router Was Done
The ROV Benchmark Stopped Its Clock Before the Router Was Done 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
GOAWAY Can Send a Relay's Audience to Your Server
A Media over QUIC relay can tell connected clients where to resume. The November threat analysis points to the ugly version: one relay names an unrelated host, and its audience obediently makes that host's day worse.
IETF
The Detour Was Nearly Full. Existing Traffic Kept Its Seat.
An IETF congestion proposal gives a crowded escape route two different orders: stop admitting new traffic, then evict the traffic already there. Operators who confuse those orders can move a jam rather than clear it.
IETF
Two Byte Orders, One Multicast Tree. Who Picks the Spine?
Five leaf routers can ask for the same multicast stream and still pull copies through different spines. The 2 November PIM working-group draft proposes a shared rule for choosing an equal-cost upstream. Its appendices reveal the awkward part: deployed equipment already makes that…
IETF
The Quantum Relay Had an Address. IS-IS Wouldn't Check It.
A router can announce where a quantum key manager lives, and a controller can turn that announcement into a relay path. A 2 November proposal makes the handoff concrete: IS-IS carries the address but explicitly leaves its format unchecked. The question moves to the controller…
IETF
The Link Never Failed. Its TLV Changed Fragments.
A routing update can make a healthy link disappear on a neighbour’s screen. The link has not moved; its description has. A 2 November IS-IS proposal tries to stop a receiver from computing a new path before both halves of that paperwork arrive.
IETF
The Probe Found Congestion. It Had to Stop Adding to It.
A network probe can see a queue mark and still keep pouring test packets into the queue. The [2 November STAMP ECN draft](https://www.ietf.org/archive/id/draft-ietf-ippm-stamp-cos-ecn-02.txt) closes that loop in both directions: the sender asks how its packets were marked, asks…
IETF
The BGP Session Fell. Its Counter Was Supposed to Stay Up.
A BGP peer drops, comes back, and resumes sending routes. The monitoring station has a Peer Down record, but it may have missed the messages that led there. A new BMP proposal wants the message count to survive the flap. The dangerous reset is a different event.
IETF
The Link Looked Idle. Its Queue Filled Anyway.
An average utilization chart can stay calm while one egress queue fills in a short burst. A new IPFIX proposal would export how often that happens and how often a burst includes packet loss. The counts are useful only beside the queue, time window and local rule that declared an…
IETF
The Update Skipped a Field. The Inventory Kept It.
YANG-Push v2 revision 01 gives two very different meanings to a missing data node. In a change event, silence leaves the receiver's old value in place. In a completed periodic snapshot, absence can remove it. A collector that ignores the distinction can erase live state or…
IETF
Four Bytes Came In. The Server Replaced the File.
A client wants to change four bytes in a twelve-byte file. It sends the fragment with a range saying where those bytes belong. A server that treats the range as a mere hint can replace the whole file with the fragment. The [IETF Byte Range PATCH…
IETF
The Email Was Signed. The Mail App Put the Button There.
A flight update arrives with a familiar name, a plausible itinerary and a button to change the booking. The signature can establish who signed the message or its embedded data. The mail app still decides whether the button appears, what it does and whether displaying it sends the…
IETF
The Router Added Headers. The Counter Took Credit.
A new IETF SR Policy YANG revision counts bytes on both sides of encapsulation. The output side includes headers the router just added; the input side alone can identify traffic steered by a Binding SID. One dashboard subtraction could tell a very confident lie.
IETF
RADIUS Sent an Error. The Proxy Owns the Next Attempt.
A login request reaches a RADIUS proxy. The next hop returns an error. The proxy now has a decision to make: find another route or send a fresh error toward the access device. Passing the packet along unchanged would be cheaper, and wrong. A new IETF draft puts that small…
IETF
The Bundle Arrived. Its Revocation Server Did Not.
A signed message can cross a broken network while a certificate-status query cannot. A 2 November IETF revision puts that contradiction in the operator’s hands: choose a reachable OCSP responder, or move the online work toward short-lived certificate issuance.
Member Unlock
Restricted Profile Intelligence
Login is required to unlock full profile briefings and deep-dive sections.
Leadership Alliance Briefing
For IP-asset owners and leadership teams: alliance briefings, private reports and direct analyst support.
Join Leadership Alliance