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

Hi Murray,

Could you review this request by May 18th? This is request #2 out of 2 from this requester.

Thank you!

Best regards,

David Dong
IANA Services Sr. Specialist

On Sat May 02 00:36:33 2026, [email protected] wrote:
> Davide,
> 
> Thanks. Updated templates for both registrations are below.
> 
> I've added a note on the subtype naming reasoning, and confirmed that public
> review on the [email protected] list is acceptable for both requests. 
> 
> ---
> 
> Hello IANA,
> 
> Per our previous correspondence, this is the updated registration
> template for the AGTP Agent Identity Document YAML format, now
> registered in the vendor tree rather than the standards tree. This
> registration is the YAML companion to the concurrent registration
> of "application/vnd.agtp.identity+json".
> 
> Note on subtype name: "vnd.agtp.identity+yaml" 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.
> 
> Type name: application
> 
> Subtype name: vnd.agtp.identity+yaml
> 
> Required parameters: none
> 
> Optional parameters:
> 
>   charset: must be UTF-8 if present.
> 
>   version: identifies the Agent Identity Document schema version.
>   The current version is "1.0".
> 
> Encoding considerations:
> 
>   The content is YAML 1.2 encoded as UTF-8 per the YAML 1.2
>   specification (yaml.org/spec/1.2.2). The "+yaml" structured
>   syntax suffix per RFC 9512 indicates that the content can be
>   processed by generic YAML 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.
> 
>   YAML deserializers MUST be configured to disable language-native
>   type instantiation (e.g., Python's yaml.safe_load rather than
>   yaml.load). The Agent Identity Document schema is purely scalar
>   and collection types — strings, numbers, booleans, lists, and
>   maps; no custom tags or language-native objects are used or
>   permitted.
> 
>   All other security considerations from
>   "application/vnd.agtp.identity+json" apply: claim integrity,
>   agent_id matching, issuer validation, no executable content.
> 
> Interoperability considerations:
> 
>   This media type is a presentation alternative to
>   "application/vnd.agtp.identity+json". The two carry the same
>   information modeled in the same eleven-field schema. AGTP servers
>   MAY support both formats and select via content negotiation;
>   clients SHOULD accept "application/vnd.agtp.identity+json" as the
>   baseline interoperable format.
> 
>   The YAML form exists for human readability — agent authors who
>   hand-edit Agent Identity Documents typically prefer YAML;
>   automated consumers typically prefer JSON.
> 
> 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/>
> 
> Applications that use this media type:
> 
>   The Agent Transfer Protocol (AGTP). The reference AGTP server
>   serves Agent Identity Documents in this format on request via
>   Accept header content negotiation. The "elemen" desktop browser
>   displays Agent Identity Documents in this format in its YAML
>   view.
> 
> Fragment identifier considerations:
> 
>   AGTP does not define fragment identifier semantics for this type
>   beyond those defined in the YAML 1.2 specification.
> 
> Restrictions on usage: none
> 
> Provisional registration: no
> 
> Additional information:
> 
>   Deprecated alias names for this type: none
>   Magic number(s): none
>   File extension(s): .agent.yaml, .agent.yml
>   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]