[media-types] [IANA #1451408] Media Type Registration Re quest: application/vnd.agtp.identity+json

Hi Murray,

Just a ping on this request (1/2 from this requester); thank you.

Best regards,

David Dong
IANA Services Sr. Specialist

On Wed May 20 18:34:10 2026, david.dong wrote:
> Hi Murray,
> 
> Please see updated application from the requester in response to your
> feedback:
> 
> ===
> 
> Thanks for forwarding the designated expert's feedback. Both items are
> reasonable and the fully corrected templates are below.
> 
> Changes applied:
> 
> 1. "Required parameters" field changed from "none" to "N/A" per RFC
> 6838 Section 5.6, in both templates.
> 
> 2. Version parameter text in the YAML template aligned with the JSON
> template, since both schemas have identical version semantics.
> 
> Incidental cleanup:
> - Published specification reference updated to draft-hood-independent-
> agtp-07 (current version on the datatracker).
> - "Agent Document" terminology consistently rendered as "Agent
> Identity Document" throughout, matching the registered subtype name.
> - Change controller field cleaned up for vendor tree registration.
> - Duplicate "Restrictions on usage" field consolidated.
> 
> Full templates follow.
> 
> ---
> 
> UPDATED JSON TEMPLATE
> 
> Type name: application
> 
> Subtype name: vnd.agtp.identity+json
> 
> Required parameters: N/A
> 
> Optional parameters:
> 
> charset: per Section 4.2.5 of RFC 6839 (must be UTF-8 if present).
> 
> version: identifies the Agent Identity Document schema version.
> The current version is "1.0". If absent, the receiver SHOULD
> assume the latest version it understands and verify against the
> agtp_version field in the document body.
> 
> Encoding considerations:
> 
> The content is JSON encoded as UTF-8 per RFC 8259. Binary content
> is not used. The "+json" structured syntax suffix indicates that
> the content can be processed by generic JSON tooling without
> AGTP-specific support.
> 
> Security considerations:
> 
> Agent Identity Documents are public identity records; they are
> intended to be served and consumed without confidentiality
> requirements. All security considerations applicable to JSON
> content per RFC 8259 §12 apply.
> 
> The Agent Identity Document carries claims about an agent's
> identity, principal, and capabilities. In future versions of the
> AGTP specification, these claims will be cryptographically signed;
> the v1 schema is unsigned and SHOULD NOT be relied upon for trust
> decisions in adversarial environments.
> 
> Receivers SHOULD validate that the agent_id field in the body
> matches the agent-id used to retrieve the document. A mismatch
> indicates either a misconfigured server or active attack.
> 
> Receivers SHOULD validate the issuer field against expected
> registration authorities for the deployment context.
> 
> Agent Identity Documents do not contain executable content. JSON
> parsers with standard hardening (depth limits, size limits, no
> prototype pollution) are appropriate.
> 
> Interoperability considerations:
> 
> This media type is the canonical wire format for AGTP Agent
> Identity Documents. A reference implementation is publicly
> available at <https://github.com/nomoticai/agtp> with a live
> deployment serving Agent Identity Documents in this format at
> agents.agtp.io.
> 
> Generic JSON tooling can process the content; AGTP-specific
> processing additionally validates the eleven-field schema defined
> in the AGTP specification.
> 
> Published specification:
> 
> Hood, C., "Agent Transfer Protocol (AGTP)",
> Work in Progress, Internet-Draft,
> draft-hood-independent-agtp-07, May 2026.
> <https://datatracker.ietf.org/doc/draft-hood-independent-agtp/>
> 
> The Agent Identity Document schema is defined in Section 5 of the
> Internet-Draft.
> 
> Applications that use this media type:
> 
> The Agent Transfer Protocol (AGTP). The reference AGTP server
> serves Agent Identity Documents in this format in response to
> DESCRIBE method requests. The reference AGTP client and the
> "elemen" desktop browser consume documents in this format.
> 
> Fragment identifier considerations:
> 
> Standard JSON Pointer (RFC 6901) fragment identifiers are
> applicable. AGTP does not define additional fragment semantics.
> 
> Restrictions on usage: none
> 
> Provisional registration: no
> 
> Additional information:
> 
> Deprecated alias names for this type: none
> Magic number(s): none (JSON has no magic number)
> File extension(s): .agent.json
> Macintosh file type code(s): none
> Object Identifier(s) or OID(s): none
> 
> Person & email address to contact for further information:
>   Chris Hood
>   [email protected]
> 
> Intended usage: COMMON
> 
> Author:
>   Chris Hood <[email protected]>
> 
> Change controller:
>   Chris Hood / Nomotic, Inc. ([email protected])
> 
> ===
> 
> Best regards,
> 
> David Dong
> IANA Services Sr. Specialist
> 
> On Tue May 12 20:59:58 2026, [email protected] wrote:
> > Two corrections.
> >
> > -MSK
> >
> > On Mon, May 4, 2026 at 9:36 AM David Dong via RT <iana-mime-
> > [email protected]>
> > wrote:
> >
> > > Hi Murray,
> > >
> > > Could you review this request by May 18th? This is request #1 out
> > > of
> > > 2
> > > from this requester.
> > >
> > > Thank you!
> > >
> > > Best regards,
> > >
> > > David Dong
> > > IANA Services Sr. Specialist
> > >
> > > On Sat May 02 00:37:15 2026, [email protected] wrote:
> > > > Hello IANA,
> > > >
> > > > Per our previous correspondence, this is the updated registration
> > > > template for the AGTP Agent Identity Document JSON format, now
> > > > registered in the vendor tree rather than the standards tree.
> > > >
> > > > Note on subtype name: "vnd.agtp.identity+json" reflects the
> > > > vendor
> > > > tree convention (vendor namespace plus document subtype). AGTP is
> > > > the protocol namespace, and "identity" identifies the specific
> > > > document type, since the Agent Identity Document is a public
> > > > identity record. Other AGTP document types (manifest,
> > > > attribution,
> > > > etc.) would follow the same vnd.agtp.X+suffix pattern.
> > > >
> > > > Type name: application
> > > >
> > > > Subtype name: vnd.agtp.identity+json
> > > >
> > > > Required parameters: none
> > >
> >
> > This should be "N/A" per Section 5.6 of RFC 6838.
> >
> > > Optional parameters:
> > > >
> > > > charset: per Section 4.2.5 of RFC 6839 (must be UTF-8 if
> > > > present).
> > > >
> > > > version: identifies the Agent Identity Document schema version.
> > > > The current version is "1.0". If absent, the receiver SHOULD
> > > > assume the latest version it understands and verify against the
> > > > agtp_version field in the document body.
> > >
> >
> > I suggest this should explicitly say that the content of the string
> > follows
> > the common semantic versioning syntax or something similar;
> > otherwise,
> > for
> > example, "buffalo" is not clearly invalid, and I wouldn't know how to
> > determine "latest".
> >
> > > Encoding considerations:
> > > >
> > > > The content is JSON encoded as UTF-8 per RFC 8259. Binary content
> > > > is not used. The "+json" structured syntax suffix indicates that
> > > > the content can be processed by generic JSON tooling without
> > > > AGTP-specific support.
> > > >
> > > > Security considerations:
> > > >
> > > > Agent Identity Documents are public identity records; they are
> > > > intended to be served and consumed without confidentiality
> > > > requirements. All security considerations applicable to JSON
> > > > content per RFC 8259 §12 apply.
> > > >
> > > > The Agent Identity Document carries claims about an agent's
> > > > identity, principal, and capabilities. In future versions of the
> > > > AGTP specification, these claims will be cryptographically
> > > > signed;
> > > > the v1 schema is unsigned and SHOULD NOT be relied upon for trust
> > > > decisions in adversarial environments.
> > > >
> > > > Receivers SHOULD validate that the agent_id field in the body
> > > > matches the agent-id used to retrieve the document. A mismatch
> > > > indicates either a misconfigured server or active attack.
> > > >
> > > > Receivers SHOULD validate the issuer field against expected
> > > > registration authorities for the deployment context.
> > > >
> > > > Agent Identity Documents do not contain executable content. JSON
> > > > parsers with standard hardening (depth limits, size limits, no
> > > > prototype pollution) are appropriate.
> > > >
> > > > Interoperability considerations:
> > > >
> > > > This media type is the canonical wire format for AGTP Agent
> > > > Identity Documents. A reference implementation is publicly
> > > > available at <https://github.com/nomoticai/agtp> with a live
> > > > deployment serving Agent Identity Documents in this format at
> > > > agents.agtp.io.
> > > >
> > > > Generic JSON tooling can process the content; AGTP-specific
> > > > processing additionally validates the eleven-field schema defined
> > > > in the AGTP specification.
> > > >
> > > > Published specification:
> > > >
> > > > Hood, C., "Agent Transfer Protocol (AGTP)",
> > > > Work in Progress, Internet-Draft,
> > > > draft-hood-independent-agtp-06, May 2026.
> > > > <https://datatracker.ietf.org/doc/draft-hood-independent-agtp/>
> > > >
> > > > The Agent Identity Document schema is defined in Section 5 of the
> > > > Internet-Draft.
> > > >
> > > > Applications that use this media type:
> > > >
> > > > The Agent Transfer Protocol (AGTP). The reference AGTP server
> > > > serves Agent Identity Documents in this format in response to
> > > > DESCRIBE method requests. The reference AGTP client and the
> > > > "elemen" desktop browser consume documents in this format.
> > > >
> > > > Fragment identifier considerations:
> > > >
> > > > Standard JSON Pointer (RFC 6901) fragment identifiers are
> > > > applicable. AGTP does not define additional fragment semantics.
> > > >
> > > > Restrictions on usage: none
> > > >
> > > > Provisional registration: no
> > > >
> > > > Additional information:
> > > >
> > > > Deprecated alias names for this type: none
> > > > Magic number(s): none (JSON has no magic number)
> > > > File extension(s): .agent.json
> > > > Macintosh file type code(s): none
> > > > Object Identifier(s) or OID(s): none
> > > >
> > > > Person & email address to contact for further information:
> > > >   Chris Hood
> > > >   [email protected]
> > > >
> > > > Intended usage: COMMON
> > > >
> > > > Restrictions on usage: none
> > > >
> > > > Author:
> > > >   Chris Hood <[email protected]>
> > > >
> > > > Change controller:
> > > >   Chris Hood / Nomotic, Inc. ([email protected])
> > > >
> > > > Public review on the [email protected] list is acceptable for
> > > > this registration.
> > > >
> > > > Thank you for your consideration.
> > > >
> > > > Best regards,
> > > > Chris Hood
> > > > Author, draft-hood-independent-agtp
> > > > [email protected]
> > >

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]