[media-types] Re: [IANA #1433073] application/3gpp-med ia-delivery-metrics-report+json registration request

This registration looks good.  It would be helpful if future 3GPP specifications could eliminate their use of the term "MIME media type". The term "Media Type" is more appropriate when describing formats that will be used outside of email.

Darrel

________________________________
From: Amanda Baber via RT <[email protected]>
Sent: Wednesday, November 12, 2025 9:27 PM
Cc: [email protected] <[email protected]>; Darrel Miller <[email protected]>
Subject: [IANA #1433073] application/3gpp-media-delivery-metrics-report+json registration request

Hi Darrel,

Sending a reminder for this request from October 7th.

thanks,
Amanda

On Tue Oct 07 04:13:41 2025, amanda.baber wrote:
> Hi Darrel,
>
> Can you review this request for us by October 21st?
>
> 3GPP media subtype names usually begin with "vnd.", but we've
> registered a few that don't, like this one.
>
> thanks,
> Amanda
>
> =====
>
> Name: Dongwook Kim
>
> Email: [email protected]
>
> Media type name: application
>
> Media subtype name: 3gpp-media-delivery-metrics-report+json
>
> Required parameters: version (see clause E.2.2 of 3GPP TS 26.510).
>
> Optional parameters: N/A
>
> Encoding considerations: 8bit
>
> 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 report Quality
> of Experience metrics in 3GPP Media Delivery Systems such as the 5G
> Media Streaming (5GMS) System.
> This format is highly susceptible to manipulation or spoofing for
> attacks designed to inject fake metrics. Both integrity protection and
> source authentication are recommended to prevent misleading of the
> recipient.
>
> Interoperability considerations: The specification defines a platform-
> independent metrics reporting document format, and it is intended that
> wide interoperability can be achieved.
>
> Published specification: 3GPP TS 26.510 clause 9.5.3.2 (if version
> needs to be provided, please see v19.0.0)
>
> Applications which use this media: 3GPP 5GMS-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
>
> General Comments: 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]