Re: [AVTCORE] New Version Notification for draft-zhao-payload-rtp-vvc-00.txt

Hi,
I hope you noticed that the payload WG was concluded and the work was moved to AVTcore WG

It will be easier for us if you resubmit the draft as  draft-zhao-avtcore-rtp-vvc-00

 Thanks

Roni Even

AVTcore co-chair


From: payload [mailto:[email protected]] On Behalf Of shuaiizhao(Shuai Zhao)
Sent: Friday, September 06, 2019 2:01 PM
To: [email protected]; [email protected]
Subject: [payload] FW: New Version Notification for draft-zhao-payload-rtp-vvc-00.txt

Hi,

A initial draft of “RTP payload format for VVC/H.266 (versatile video coding)” has been uploaded for public review (see below to access the draft).

I am soliciting comments from the experts with the emphasis on the following items:

  1.  AFAIK the MRST/MRMT mode, which was proposed for HEVC (RCF7798), was never deployed in the market. Wondering if we should keep the similar mode for the VVC. If you know anyone has such implementation, please let us know.
  2.  RFC 7798 had the PACI (payload content information) and has the only payload, the temporal scalability info message.  Now, the current framemarking draft<https://datatracker.ietf.org/doc/draft-ietf-avtext-framemarking/> has made the temporal scalability information stuff obsolete.  Anyone sees a need for PACI?  Has anyone ever seen a use of PACI in 7798 implementations?
  3.  Looking forward to the input from people who wish to make comments on the NAL unit header design (which is also the payload header).  We would be happy to forward the outcome of such discussion to the JVET meeting.  They should comment within a week, so we can make the JVET doc deadline.


We would be grateful for any comments or suggestion you might have.

Best,
Shuai




On 9/4/19, 10:25, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> wrote:


    A new version of I-D, draft-zhao-payload-rtp-vvc-00.txt
    has been successfully submitted by Stephan Wenger and posted to the
    IETF repository.

    Name:                              draft-zhao-payload-rtp-vvc
    Revision:        00
    Title:                 RTP Payload Format for Versatile Video Coding (VVC)
    Document date:           2019-09-03
    Group:                             Individual Submission
    Pages:                              35
    URL:            https://www.ietf.org/internet-drafts/draft-zhao-payload-rtp-vvc-00.txt
    Status:         https://datatracker.ietf.org/doc/draft-zhao-payload-rtp-vvc/
    Htmlized:       https://tools.ietf.org/html/draft-zhao-payload-rtp-vvc-00
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-zhao-payload-rtp-vvc


    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 others.




    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

_______________________________________________
Audio/Video Transport Core Maintenance
[email protected]
https://www.ietf.org/mailman/listinfo/avt