[media-types] [IANA #1443733] application/vnd.cmmf-con figuration-information+json registration request

Hi Alexey,

Sending a reminder for this request from February 10th. #1 of 3.

thanks,
Amanda

On Tue Feb 10 18:40:13 2026, amanda.baber wrote:
> Hi Alexey,
> 
> Would you be able to review this for us by February 24th? It's a
> revised version of a request you reviewed in early November (IANA
> #1435952). This time it's also accompanied by two more ETSI requests.
> 
> thanks,
> Amanda
> 
> =====
> 
> Name: Miguel Angel Reina Ortega
> 
> Email: [email protected]
> 
> Media type name: application
> 
> Media subtype name: vnd.cmmf-configuration-information+json
> 
> Required parameters: None
> 
> Optional parameters: cmmfProfiles (see clause D.3.3.3.4.3 of ETSI TS
> 103 973),
> cmmfCodeTypes (see clause D.3.3.3.4.4 of ETSI TS 103 973)
> 
> Encoding considerations: binary
> 
> This is a JSON document, and the encoding considerations are the same
> as for media type application/json defined in IETF RFC 8259 [25].
> 
> Security considerations: This media format is a JSON document and
> inherits the security considerations provided in IETF RFC 8259 [25].
> The format does not incorporate any active or executable content.
> However, other forms of material from outside resources can be
> referenced by the format, and this material can contain active or
> executable content. Such material is expected to be identified by its
> own MIME type, and the security considerations of that format should
> be taken into account.
> This format is highly susceptible to manipulation or spoofing for
> attacks designed to inject fake information. Both integrity protection
> and source authentication are recommended to prevent misleading of the
> recipient.
> 
> Interoperability considerations: None
> 
> Published specification: ETSI TS 103 973
> 
> Applications which use this media: The CMMF Configuration Information
> document may be used by CMMF Receivers, either stand-alone or embedded
> within other applications, to provide necessary configuration
> information to identify, locate, and recover media resources from CMMF
> bitstreams/Transport Objects
> 
> Fragment identifier considerations: None
> 
> Restrictions on usage: None
> 
> Provisional registration? (standards tree only): No
> 
> Additional information:
> 
> 1. Deprecated alias names for this type: N/A
> 2. Magic number(s): N/A
> 3. File extension(s): json
> 4. Macintosh file type code: N/A
> 5. Object Identifiers: N/A
> 
> General Comments: None
> 
> Person to contact for further information:
> 
> 1. Name: Jason Cloud
> 2. Email: [email protected]
> 
> Intended usage: COMMON
> 
> Author/Change controller: ETSI

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