Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-vvc-15.txt

["Murray S. Kucherawy" <[e-mail]>]

I still have some concerns about Section 7.1.  I did see Stephan's other
threads about it.  In one of them he said:

> I wonder whether there’s anyone here on this list with a) an interest in
VVC’s media type registration, and b) at least basic knowledge of the
requirements of RFC6838?  If that person would step forward and help us
with that section, I would very much appreciate it.

When not serving on the IESG, I am one of the reviewers of media type
requests, so I think I can be of service here.  :-)

There are two issues.  The first, simpler, one is that you've now added all
the missing fields from RFC 6838, but one of them says "N/A" for
"Applications that use this media type".  If none are using it (or will
be), why are we registering it?

The other is that you list "profile-id, tier-flag, sub-profile-id,
interop-constraints, and level-id" as optional parameters, but then proceed
to describe those plus all of the following:

sprop-sublayer-id
sprop-ols-id
recv-sublayer-id
recv-ols-id
max-recv-level-id
sprop-dci
sprop-vps
sprop-sps
sprop-pps
max-lsr
max-fps
sprop-max-don-diff
sprop-depack-buff-bytes
depack-buf-cap

At a minimum, the upper list should be extended so that it's complete.
However, I would suggest that a section be added that contains the
description of each of the optional parameters, one per subsection.  Then
the current Section 7.1 (which now includes the registration template) can
include the list without also being the full specifications of those
parameters.  Otherwise IANA has to copy that entire blob of text into the
registration, when all they really need is the reference to this document
once published.

Note that this is just a proposal for organizing the material, not changing
anything within it.

-MSK

On Mon, Apr 25, 2022 at 10:18 AM shuai zhao <[e-mail]> wrote:

> Resent to the group and hopefully everyone has a copy now.
>
> Best,
> Shuai
>
> On Apr 24, 2022, at 10:06 AM, shuai zhao <[e-mail]> wrote:
>
> Thanks Murray, Bernard, Christer and Bernard for the review on revision 14.
>
> Note: I could not reply to individual email since I did not receive any
> email from avtcore mailing list since March 25th. A very convenient
> excuse to disappear….
>
> So I compiled some the major comments with proposed fix below… for minor
> and editorial fix, please see the diff.
>
>
> *To Christer Holmberg:*
>
>    - Q1 Section 7.2.1, replace “this parameter” with “fmtp”
>    - Q2 Section 7.2.1, add informative note for more clarity
>    - Q3: Section 7.2.1, no need to add text for “fmtp” since we had such
>    text in a paragraph above
>    - Q4: exemplary SDP O/A is added under section 7.2.1, As well as the
>    RFC6838 template.
>    - Q5: Based on the mailing list discussion, no action is needed here.
>    - Q6: Based on the mailing list discussion, no action is needed here.
>    - Q7: Based on the mailing list discussion, no action is needed here.
>
>
> *To Murray:*
>
>    - Section 1, fix the grammar
>    - Section 7.1, add back informative note for “optional parameters”
>    - Section 3.2 Removed unused “RPS” abbr
>    - Section 4.3.2: Based on the mailing list discussion, no action is
>    needed here.
>    - Add RFC editor note under Appendix A
>    - Fix all editorial typo/errors
>
>
>
> Best,
> Shuai
>
>
> *From: *[e-mail] <[e-mail]>
> *Date: *Friday, April 22, 2022 at 7:07 PM
> *To: *Miska M. Hannuksela <[e-mail]>, Miska Hannuksela <
> [e-mail]>, Shuai Zhao <[e-mail]>, Stephan
> Wenger <[e-mail]>, Yago Sanchez <[e-mail]>,
> Ye-Kui Wang <[e-mail]>
> *Subject: *New Version Notification for draft-ietf-avtcore-rtp-vvc-15.txt
>
>
> A new version of I-D, draft-ietf-avtcore-rtp-vvc-15.txt
> has been successfully submitted by Shuai Zhao and posted to the
> IETF repository.
>
> Name:           draft-ietf-avtcore-rtp-vvc
> Revision:       15
> Title:          RTP Payload Format for Versatile Video Coding (VVC)
> Document date:  2022-04-22
> Group:          avtcore
> Pages:          67
> URL:
> https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-vvc-15.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-vvc/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-vvc
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-vvc-15
>
> Abstract:
>    This memo describes an RTP payload format for the video coding
>    standard ITU-T Recommendation H.266 and ISO/IEC International
>    Standard 23090-3, both also known as Versatile Video Coding (VVC) and
>    developed by the Joint Video Experts Team (JVET).  The RTP payload
>    format allows for packetization of one or more Network Abstraction
>    Layer (NAL) units in each RTP packet payload as well as fragmentation
>    of a NAL unit into multiple RTP packets.  The payload format has wide
>    applicability in videoconferencing, Internet video streaming, and
>    high-bitrate entertainment-quality video, among other applications.
>
>
>
>
>
>
> The IETF Secretariat
>
>
>