[media-types] Re: Media type review request for draft-ietf-a vtcore-rtp-v3c

Hello Marius,

On Tue, Jul 22, 2025 at 10:04 PM Marius Kleidl <marius=
[email protected]> wrote:

> Type name: application
>
> Subtype name: v3c
>
> Required parameters: N/A
>
> Optional parameters: sprop-v3c-unit-header, sprop-v3c-unit-type,
> sprop-v3c-vps-id, sprop-v3c-atlas-id, sprop-v3c-attr-idx,
> sprop-v3c-attr-part-idx, sprop-v3c-map-idx, sprop-v3c-aux-video-flag,
> sprop-v3c-parameter-set, sprop-v3c-tile-id, sprop-v3c-tile-id-pres,
> sprop-v3c-atlas-data, sprop-v3c-common-atlas-data, sprop-v3c-sei,
> v3c-ptl-level-idc, v3c-ptl-tier-flag, v3c-ptl-codec-idc,
> v3c-ptl-toolset-idc, v3c-ptl-rec-idc and sprop-max-don-diff.
>
> Encoding considerations: This type is only defined for transfer via RTP [
> RFC3550
> <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-v3c-08.html#RFC3550>
> ].
>

Please see RFC 6838 Section 4.8 for a list of valid values here.


> Security considerations: Please see Section 11
> <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-v3c-08.html#Security-considerations>
> .
>

There's a large number of other documents referenced in your Section 11.  I
didn't go into them all, but it's good there's a full treatment done.  The
only sticking point for me would be that somewhere in that tree of security
recommendations, the question RFC 6838 poses about executable content is
answered.


> Interoperability considerations: N/A
>
> Published specification: Please refer to [ISO.IEC.23090-5
> <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-v3c-08.html#ISO.IEC.23090-5>
> ]
>
> Applications that use this media type: Any application that relies on
> V3C-based media services over RTP
>
> Additional information: N/A
>
> Person & email address to contact for further information:
>

This needs to be completed.


> Intended usage: COMMON
>
> Restrictions on usage: N/A
>
> Author: See Authors' Addresses section of this memo.
>
> Change controller: IETF [email protected]
>
> Provisional registration? (standards tree only): No
>
> The optional parameters are defined as: (from
> https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-v3c-08.html#name-optional-parameters-definit
> )
> [...]
>

This bit isn't necessary (or part of the template); the referenced
published specification is sufficient.

-MSK

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