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

The media type registration template looks good to me here.

The draft itself may get some comments about the SHALL NOT text at the end
of Section 11; you're asserting a normative constraint against a format
that's already defined.  If RTP is incapable of transporting executable
content, I think you just need to say that.  On the other hand, if you're
saying components of a system using this media type SHALL NOT construct RTP
payloads that contain executable content, I think that would be more clear.

-MSK

-MSK

<https://www.norton.com> Virus-free.www.norton.com
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Aug 5, 2025 at 3:51 AM Lauri Ilola (Nokia) <[email protected]>
wrote:

> Hello Marius & Murray,
>
>
>
> Thank you for the feedback and suggestions. I’ve made a new version of the
> draft available hopefully addressing the remaining suggestions (
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-v3c/10/). Below
> you can find a copy of the updated media type registration section:
>
>
>
> ---
>
>
>
> 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: framed
>
>
>
> Security considerations: Please see Section 11
> <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-v3c-10.html#name-security-considerations>
>
>
>
> Interoperability considerations: N/A
>
>
>
> Published specification: Please refer to ISO/IEC 23090-5
> <https://www.iso.org/standard/89030.html>
>
>
>
> 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: Lauri Ilola (
> [email protected]) or Lukasz Kondrad ([email protected])
>
>
>
> 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
>
>
>
> ---
>
>
>
> Please let me know if there are any remaining questions or concerns that
> would need to be addressed.
>
>
>
> Kind Regards,
>
> -Lauri
>
>
>
> *From: *Murray S. Kucherawy <[email protected]>
> *Date: *Wednesday, 23. July 2025 at 10:53
> *To: *Marius Kleidl <[email protected]>
> *Cc: *[email protected] <[email protected]>,
> [email protected] <[email protected]>
> *Subject: *Re: [media-types] Media type review request for
> draft-ietf-avtcore-rtp-v3c
>
> Some people who received this message don't often get email from
> [email protected]. Learn why this is important
> <https://aka.ms/LearnAboutSenderIdentification>
>
>
>
>
>
> *CAUTION:* This is an external email. Please be very careful when
> clicking links or opening attachments. See the URL nok.it/ext for
> additional information.
>
>
>
> 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]