IETF debates AI inference categories, attested TLS, and related drafts

IETF working groups spent the day refining definitions and threat models across AI control, attested TLS, supply chain integrity, and related protocol drafts. Several adoption calls and redesign discussions also advanced, while moderators debated list handling rules.

AI control splits inference into system and user input categories

The ai-control working group debated a pull request that would split inference into separate AI System Inference and AI User Input categories. Participants focused on definitional clarity across roughly sixty messages. The change matters because clearer categories would shape how future AI control mechanisms classify and constrain traffic.

SEAT consolidates threat model for attested TLS

The SEAT working group consolidated discussion of threat models and formal properties for attested TLS drafts. Contributors added TEE-specific clarifications. Readers tracking confidential computing will care because these properties define what attestation can actually guarantee in TLS sessions.

Moderators debate fate of held messages from blocked posters

IETF moderators discussed whether held messages from a blocked poster may be published elsewhere or must be discarded when no explicit BCP covers the case. The thread grew heated among fourteen participants. The outcome will affect how lists handle contested content and moderator discretion.

SCITT closes receiver-side omission gaps

The SCITT list converged on three verification rungs plus external anchors to close omission gaps from the receiver vantage across independent designs. Participants examined what a record must carry. This work matters for anyone building transparent supply-chain ledgers that receivers can verify without trusting the issuer alone.

Coverage attestation profile draft posted to SCITT

A new informational draft, the Coverage Attestation Profile, was posted to the SCITT list with a request for critical review. Early comments flagged inconsistencies in handling withheld units and scope. Implementers should watch because the profile aims to standardize how coverage claims are attested.

ACME public-key draft redesign debated

The ACME working group debated redesigning draft-geng-acme-public-key so it fits the RFC 8555 authorization and order state machine through a new proof-of-possession identifier type. Five participants exchanged detailed comments. The redesign would determine whether public-key challenges can be adopted without breaking existing ACME flows.

IDR adoption call for BGP SRv6-MPLS interworking

An adoption call ran for the BGP SRv6-MPLS transport interworking draft in the IDR working group. One participant flagged a dependency on unresolved changes to RFC 9252. Operators planning SRv6 and MPLS coexistence need the dependency resolved before the draft can safely advance.

Web-bot-auth adoption call for HTTP message signatures

The web-bot-auth working group opened a call for adoption of an HTTP Message Signatures draft aimed at automated traffic. Early responses showed unanimous support from implementers. Adoption would give operators a standard way to authenticate bots without relying solely on IP allow-lists.