[media-types] [IANA #1429060] application/asyncapi+json , asyncapi+yaml registration request

Hi Murray,

Sending a reminder for this combined request from 9/11.

thanks,
Amanda

On Thu Sep 11 19:39:03 2025, amanda.baber wrote:
> Hi Murray,
> 
> Would you be able to review this/these by September 25th? Linux
> Foundation is on the approved organization list, and Andy and Orie
> confirmed that listing them as the owner/change controller works here.
> 
> If these are OK, we'll post a separate plain-text file for each
> registration. Would you want us to leave the subtype name field
> intact, or just list one subtype in each file? If the latter, are the
> RFCs named in the sec cons field relevant to both asyncapi+json and
> asyncapi+yaml, or do those need to be separated as well?
> 
> thanks,
> Amanda
> 
> ====
> 
> Media type name: application
> 
> Media subtype name: asyncapi+json, asyncapi+yaml
> 
> Required parameters: None
> 
> Optional parameters: version; ignore all other parameters
> 
> Encoding considerations: binary
> 
> Security considerations: See Section 4 of RFC 9512 and Section 6 of
> RFC 4627.
> 
> Interoperability considerations: See Section 3 of RFC 9512.
> 
> Published specification:
> https://www.asyncapi.com/docs/reference/specification/v3.0.0
> 
> Applications which use this media: HTTP
> 
> Fragment identifier considerations:
> https://www.asyncapi.com/docs/reference/specification/v3.0.0
> 
> Restrictions on usage: None
> 
> Provisional registration? (standards tree only): No
> 
> Additional information:
> 
> 1. Deprecated alias names for this type: None
> 2. Magic number(s): None
> 3. File extension(s): .json, .yaml
> 4. Macintosh file type code: TEXT
> 5. Object Identifiers: None
> 
> Person to contact for further information:
> 
> 1. Name: AsyncAPI Initiative
> 2. Email: [email protected]
> 
> Intended usage: COMMON
> 
> Author/Change controller: Linux Foundation (AsyncAPI Initiative)

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