[media-types] Re: [IANA #1435952] application/ vnd.cmmf-configuration-information+json registration re quest

Hi Amanda,

A couple of comments below, but otherwise this is Ok to register:

On 05/11/2025 10:22, Amanda Baber via RT wrote:
> Hi Alexey,
>
> Would you be able to review this by November 19th?
>
> thanks,
> Amanda
>
> =====
>
> Name: Miguel Angel Reina Ortega
>
> Email: [email protected]
>
> Media type name: application
>
> Media subtype name: vnd.cmmf-configuration-information+json
>
> Required parameters: N/A
>
> Optional parameters: N/A
>
> 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.
>
> Security considerations: This media format is a JSON document and inherits the security considerations provided in RFC 8259.
>
> 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: The present document defines a platform-independent expression of a document, and it is intended that wide interoperability can be achieved.
I think it would be better to say "none" here, if no backward 
compatibility issues are known or exist.
> Published specification: ETSI TS 103 973 Coded Multisource Media Format (CMMF) for Media Distribution and Delivery
>
> Applications which use this media: Various
This doesn't need to be very extensive or exhaustive, but some 
representative examples need to be mentioned. This is to help 
implementers to decide whether or not they need to care about 
implementing this media type.
> Fragment identifier considerations: N/A
>
> 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
>
> Person to contact for further information:
>
> 1. Name: Jason Cloud
> 2. Email: [email protected]
>
> Intended usage: COMMON
>
> Author/Change controller: ETSI TC BROADCAST
>

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