Members,<\/p>\n\n\n\n
A status update on our upstream dependency, the referenced protocol specification.<\/p>\n\n\n\n
The IETF Independent Submissions Editor has concluded consideration of draft-saihm-memory-protocol<\/strong> and released it from the ISE queue; the datatracker stream is now set to None. The direction from the ISE is to bring this work to the IETF proper. Agent-to-agent and agent-to-tool protocol work is now being taken up there \u2014 an “agentproto” Birds-of-a-Feather session<\/strong> was held at IETF 126 (Vienna, July 2026)<\/strong> to identify what needs standardizing and whether to charter a working group \u2014 and the Independent stream defers to IETF working-group work, active or forming, in the same space (RFC 4846, RFC 8730).<\/p>\n\n\n\n Charter section 2.1 (de-confliction).<\/strong> Our charter placed a time-bound restriction on developing a competing normative specification, in force “until the IETF Independent Submission concludes (\u2026 is published as an RFC, or is withdrawn or declined).” That condition is now met, so the section 2.1 restriction lifts by its own terms.<\/p>\n\n\n\n Our posture is unchanged.<\/strong> Lifting the restriction does not change what this Group does. We continue to operate one layer above the protocol \u2014 interoperability profiles, a use-case catalogue, and conformance criteria and test vectors \u2014 and we do not re-specify the protocol here (charter sections 3 and 4).<\/p>\n\n\n\n Forward normative home.<\/strong> The natural home for the protocol’s normative evolution is the IETF working-group work now forming in this space. The Group will track that work and align our profiles and test vectors to it. When it produces a citable document, I will bring an amendment (section 11) to re-point our normative reference \u2014 currently draft-saihm-memory-protocol-01<\/strong> \u2014 to that document, for your review and consensus.<\/p>\n\n\n\n No charter change today.<\/strong> I am not proposing an amendment in this note. The -01 draft remains our current normative reference and stays citable on the datatracker; I will keep it available as the reference text in the interim.<\/p>\n\n\n\n If you follow agent-memory or interop work at the IETF and would like to engage the agentproto effort directly, its BoF materials and mailing list are on the IETF datatracker; I will circulate the specific list address once I have confirmed it. I will keep this list posted as the IETF work takes shape.<\/p>\n\n\n\n Best regards, <\/p>\n","protected":false},"excerpt":{"rendered":" Members, A status update on our upstream dependency, the referenced protocol specification. The IETF Independent Submissions Editor has concluded consideration of draft-saihm-memory-protocol and released it from the ISE queue; the datatracker stream is now set to None. The direction from … Continue reading What this means for the Group:<\/h2>\n\n\n\n
Russell Jackson<\/strong>
Chair, AI Agent Memory Interoperability Community Group<\/p>\n\n\n\n