Repository navigation
draft-rapp-ammp-00: rename to the Agent Mediated Messaging Protocol - #21
Merged
Merged
Conversation
The protocol is renamed AMMP before its first submission. "Mailbox access"
named only the first channel; the contract mediates an agent's
correspondence, mail and peer traffic alike. AMAP was also already in use by
an expired 2003 individual draft.
- draft: title, abbreviation, docName and prose; a -00 history entry
records the rename. The 3.1.0 entry recording the earlier AMP to AMAP
rename is left as written.
- schemas: descriptions cite "AMMP, section ..." (descriptions only).
- dist/: renders as draft-rapp-ammp-00.{xml,txt}.
- tooling, docs and the site now use the new filename.
Not renamed: the repository, draft/draft-amap.xml, the amap-* names and
amap.router example address, the $id authority amap-spec, and the
AMAP-Peer-Statement / AMAP-Peer-Control header fields. contract_version
stays "2"; no fixture changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The abstract now calls the Runtime "trusted, credentialed, store-and-forward messaging", and says the agent sends and receives messages (email, and under the optional profile, messages to other agents). The framing sentences follow it: the opening of the Introduction, "The approach", the Agent and Runtime definitions, the trust table, and the trust rationale. "Mail" as a term of art (the mail tree and origin class, demotion, mail admission, SMTP) is unchanged, and email remains the only transport defined. The -00 history entry for the rename says so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The protocol is renamed AMMP before its first submission. "Mailbox access"
named only the first channel; the contract mediates an agent's
correspondence, mail and peer traffic alike. AMAP was also already in use by
an expired 2003 individual draft.
records the rename. The 3.1.0 entry recording the earlier AMP to AMAP
rename is left as written.
Not renamed: the repository, draft/draft-amap.xml, the amap-* names and
amap.router example address, the $id authority amap-spec, and the
AMAP-Peer-Statement / AMAP-Peer-Control header fields. contract_version
stays "2"; no fixture changes.
🤖 Generated with Claude Code