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
Agent Routing's Policy Tag Travels. The Agreement Stays Put.
A task can cross a company boundary with a policy tag attached. The tag may be meant to control where work runs, what priority it receives or which contractual rules apply. The next company can see the tag. The company after that may see it too. The contract that gives the tag…
IETF
Two Clones Enter TLS. Who Gets a Name That Survives the Key?
An attestation can show that a confidential workload runs the approved image. Put two copies of that image online and the measurement gives them the same face. A new IETF individual draft asks whether a peer needs to recognize a particular copy—and who gets to give it a name that…
IETF
IANA Has Listed the New SFrame Ciphers. The RFC Is Still at the Printer.
A public standards table can move faster than the document that explains it. IANA's SFrame registry already displays three new cipher-suite numbers, five extra parameter columns and a row of “Y” recommendations. The defining draft is still in the RFC Editor queue. Engineers can…
IETF
Same VPN Number. No Right to Import the Route.
Ten routers can share a VPN and still have different reasons to receive a particular route. A draft at the IETF proposes a tag that carries a Route Target's identifying numbers without carrying its power to distribute and import routes. The wire format changes only at the…
IETF
A Protocol Number Has an Owner for Its Next Edit. The Registry Should Say Who.
A code point can survive its author, its working group and several generations of software. Its entry in an IANA registry may need a new contact, reference or description years later. Someone has to approve that edit. A new IETF draft wants the answer written into more registry…
IETF
Two Keys Can Land on One IPv6 /64. Who Gets the Address?
A 27 October IETF proposal would derive a workload’s IPv6 subnet from its public key. It sounds like an address that carries its own identity card. The draft says a different key can match the same /64 subnet bits in about 2^16 trials under a /48 aggregate. The operator still has…
IETF
The RFC Edit Has a Pull Request. The Author’s Yes Still Arrives by Email.
The RFC Production Center is testing a more visible way to show authors its edits: a pull request against the source that entered the publication queue. In its 30 September report, the Center said 31 queued documents had authors who opted in, while the pilot would accept five…
IETF
The Agent Got a Fast Lane. The User’s Approval Was on a List
A 27 October IETF proposal would let a personal AI agent get access to a service without interrupting its user each time. The switch is a pre-approved list held by an Agent Authorization Center. The service can receive a valid token even when the token does not say whether a…
IETF
Oblivious CoAP Hides the Sender. The Proxy Can Still Press Send Twice
A 28 October IETF proposal would let small devices make protected CoAP requests without telling the destination which device sent them. Its relay cannot read the payload, but it can repeat the envelope. The draft puts the replay decision at the receiving server—precisely where a…
IETF
Erase the Agent’s DNS Badge. Its OAuth Client Is Still the Off Switch
An October IETF proposal would let a service check whether an agent’s operator still stands behind it. The public DNS record points to an OAuth client; the operator’s authorization server issues the proof. Removing the pointer can make a new receiver ask fewer questions.…
IETF
The Agent Needs Help. DAWN Asks It to Name the Helper First
DAWN is building a way to discover AI agents and services. A 28 October paper finds a catch at the door: a client may know what it wants done without knowing the capability name it must search for. The fixes move the bill between the client, a local catalog and a broker—and move…
IETF
RPKI's New Push Alarm Rings. The Data Still Takes the Slow Lane
A 28 October Internet-Draft promises faster delivery of route-security changes. Its urgent message contains a serial number and a warning, while the packet that actually carries changed data runs on a negotiated schedule. The existing RTR protocol already has an unsolicited…
IETF
Platform Support Is a Name Anyone Can Type. Who Gets to Wear It?
A new Internet-Draft brings sender impersonation inside job boards and marketplaces, where the platform controls the inbox and the trust label. Its two sharpest traps are technical: a Unicode skeleton match can miss a lookalike, and a validator can return a host name with an…
IETF
TLS Changed Its Key Schedule. The Authenticator Next Door Needs the Memo
A TLS cipher suite can keep its familiar hash label while a separate extension chooses a different key schedule. The 27 October XOF draft revision makes the resulting handoff explicit: an identity check running outside the TLS library needs to know which KDF was negotiated, and…
IETF
The Deleted Email’s First Lock Was Set Yesterday
A new JMAP draft gives destroyed mail a recovery drawer. In a shared account, the first test for opening it looks back to who could read the item when it was deleted. Purging and restoring use different rights, and a changed sharing rule sits between those clocks.
IETF
The Server Wants a Drawer in Your Device
A revised QUIC proposal lets your device carry a server's network memory into the next connection. The awkward questions are whose drawer it is—and whether “clear cookies” empties it.
IETF
The Proposed Agent Registry Wants to Know Who Pays for the Vote
A new revision of an AI identity charter goes beyond counting subsidiaries. It asks whether someone else is financing or directing the member who raises a hand.
IETF
The Code Point Gets Two Years. The RFC Gets Forever.
A new IETF draft draws a line between a provisional registry number and the permanent page that might quote it. The number can expire; the page will keep telling readers to use it.
IETF
Two Green Ledgers, One £250 Bill
A signed £200 limit can pass two separate checks and still leave its owner with a £250 bill. An individual IETF draft names the missing sum.
IETF
The New ISP Offers /56. Your /48 Network Plan Gets the Bill.
A revised IETF draft puts an awkward number on broadband switching: one provider's address block may be too small for the layout a customer built under another.
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