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

From: shuai zhao <[email-masked]>
Date: Thu, 11 Mar 2021 20:39:51 -0800

Hi All,

Here is the summary for -08, as we discussed during AVTCore session. Comments are welcomed.

- Editorial changes suggested by Ye-Kui in various locations

- removed the following editor’s note:

            - 1, framemarking is no longer supported in VVC payload, therefore removed.

            - 2, VVC draft is mature, nothing to update here, therefore removed

            - 3, there is no needed to describe DONL and sprop-max-don-diff, therefore removed.

            - 4, is not needed. Optional parameter list will be updated in editor-note 20,  therefore removed

            - 7, resolved note: decided not to support opi, therefore removed.

            - 8, 10, 12 13 removed based profile-id text update

            - 18, no long support max-lps, therefore removed

            - 22 and 23: no long support SLI and RPSI, therefore removed

- updated editor-note 20: with list of current supported optional parameters.

- removed informative note under ‘M’ bit

- make sure all informative notes have correct indentation.

- removed max-br, max-lps, max-cpb, max-dpb, max-tr, max-tc

            - updated max-lsr and max-fps subsections due to changes above

- proposed text for editor-note 24, the reserved “R” bit for FU header:

"There is an editor-note 24 for 'R’ in FU header (page 29). When set to 1, the R bit indicates the last NAL unit of a coded picture, i.e., the last byte of the FU payload is also the last byte of the coded picture.  When the FU payload is not the last fragment of a coded picture, the R bit MUST be set to 0."

- removed framemarking section 9 and reference

- removed SLI and RPSI

- current kramdown tool update should resolve the naming error automatically in the reference section.

Best,

Shuai

> On Mar 7, 2021, at 5:13 PM, [email-masked] wrote:
> 
> 
> A new version of I-D, draft-ietf-avtcore-rtp-vvc-08.txt
> has been successfully submitted by Shuai Zhao and posted to the
> IETF repository.
> 
> Name:		draft-ietf-avtcore-rtp-vvc
> Revision:	08
> Title:		RTP Payload Format for Versatile Video Coding (VVC)
> Document date:	2021-03-07
> Group:		avtcore
> Pages:		52
> URL:            https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-vvc-08.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-vvc/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-vvc
> Htmlized:       https://tools.ietf.org/html/draft-ietf-avtcore-rtp-vvc-08
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-vvc-08
> 
> 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.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
>