[media-types] [IANA #1431117] application/3gpp-mbs-objec t-manifest+json registration request

Hi Alexey,

Sending a reminder for this request from October 1st (#2 of 2).

thanks,
Amanda

On Wed Oct 01 18:28:05 2025, amanda.baber wrote:
> Hi Alexey,
> 
> Additional information for this second request: "v17.9.0" should be
> removed from the request form, but that's the preferred version. It
> looks like it may not be available for public download yet, but the
> applicant says that 17.8.0 can be used instead, if necessary:
> 
> https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=4018
> 
> thanks,
> Amanda
> 
> On Wed Oct 01 18:08:26 2025, amanda.baber wrote:
> > Hi Alexey,
> >
> > Can you review this one by October 15th? #2 of 2 from 3GPP.
> >
> > thanks,
> > Amanda
> >
> > =====
> >
> > Name: Dongwook Kim
> >
> > Email: [email protected]
> >
> > Media type name: application
> >
> > Media subtype name: 3gpp-mbs-object-manifest+json
> >
> > Required parameters: version (see clause E.3.2 of 3GPP TS 26.517
> > v17.9.0).
> >
> > 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 used to describe a set
> > of objects to the MBS Transport Function to be transmitted in an MBS
> > Distribution Session as part of an MBS User Service. This format is
> > highly susceptible to manipulation or spoofing for attacks designed
> > to
> > affect the set of objects ingested by the MBSTF and transmitted to
> > receivers. Both integrity protection and source authentication are
> > recommended to prevent misleading of the receiver.
> >
> > Interoperability considerations: The specification defines a
> > platform-
> > independent manifest document format, and it is intended that wide
> > interoperability can be achieved.
> >
> > Published specification: 3GPP TS 26.517 clause D.1
> >
> > Applications which use this media: 3GPP MBS-based applications and
> > services
> >
> > Fragment identifier considerations: The provisions of RFC 6901 (JSON
> > Pointer) apply.
> >
> > 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
> > 4. Macintosh file type code: None
> > 5. Object Identifiers: None
> >
> > Person to contact for further information:
> >
> > 1. Name: 3GPP Specifications Manager, Dongwook Kim
> > 2. Email: [email protected]
> >
> > Intended usage: COMMON
> >
> > Author/Change controller: 3GPP TSG SA WG4,
> > <[email protected]>

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