[media-types] Re: [IANA #1443734] application/vnd.cm mf-encoder-configuration+json registration request
Alexey Melnikov <[email protected]> Wed, 8 Apr 2026 10:05:28 +0100
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <[email protected]> |
Hi Amanda, This is fine to approve. Thank you, Alexey On 18/03/2026 10:10, Amanda Baber via RT wrote: > Hi Alexey, > > #3 of 3 from February 10th. > > thanks, > Amanda > > On Tue Feb 10 18:42:31 2026, amanda.baber wrote: >> Hi Alexey, >> >> This is #3 of 3 from ETSI. >> >> thanks, >> Amanda >> >> ===== >> >> Name: Miguel Angel Reina Ortega >> >> Email: [email protected] >> >> Media type name: application >> >> Media subtype name: vnd.cmmf-encoder-configuration+json >> >> Required parameters: N/A >> >> Optional parameters: profile (see clause E.1.4.3 of ETSI TS 103 973) >> codeType (see clause E.1.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 Encoder configuration may >> be used by CMMF Bitstream Generators/Sources used to configure >> encoding of media resources into one or more 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]