Summary

  • The IESG approved the Agent Communication Protocols charter on 8 October. Its first milestone is to adopt an informational use-cases draft in December 2026.
  • The draft-agentic-ai-usecases-requirements-04 page says it was updated on 15 October, but labels it an individual Internet-Draft with no RFC stream or intended RFC status.
  • A draft’s presence or revision date does not establish working-group adoption. The formal adoption record is the meaningful signal to watch before the December target.

One milestone, two document states

The latest Agentproto timeline contains two entries that can look like one step. The approved charter schedules an informational use-cases draft for adoption in December. The IETF Datatracker’s related-documents page already lists revision -04 of “Agentic AI Use Cases and Requirements,” last updated on 15 October. Its own page, however, classifies it as an active individual Internet-Draft. It has no RFC stream and no intended RFC status. The page also says that anyone may submit an Internet-Draft and that an I-D is neither IETF endorsement nor a document with formal standing in the standards process.

That status is not a criticism of the authors or of the document. Individual submissions are part of how technical work becomes visible. It does mean that the upload date cannot stand in for the action the charter names: adoption by the working group. The December checkpoint is still ahead, and the public record reviewed here does not turn the October revision into an adopted Agentproto deliverable.

The charter’s later milestones make the distinction consequential. It calls for an informational architecture draft to be adopted in February 2027, one or more standards-track protocol drafts in March 2027, and submission of protocol draft(s) to the IESG as proposed standards in March 2028. The charter history records the October approval and changes that use plural “draft(s)” for the later standards-track steps. These are targets in a work plan, not evidence that any draft has already cleared them.

The authorized subject is narrower than the phrase “agent communication” can suggest. Agentproto is tasked with a baseline dialog-management protocol and a reference architecture. The charter says it will not replace application-layer agent protocols or define a new transport. It focuses on dialog identifiers, lifecycle and context propagation over existing IETF protocols. It explicitly leaves model implementation, agent decision and planning semantics, user-interface design and audit-data structures outside scope.

Readers should therefore track two records separately: the working group’s adoption action and the individual document’s revision history. If the group adopts a use-cases draft, the version and decision should be identifiable. If it revises the charter milestones, Datatracker should show that too. Until then, an updated I-D is evidence of document activity, not proof that the first charter checkpoint has been met.

Sources