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

"shuaiizhao(Shuai Zhao)" <shuaiizhao@tencent.com> Fri, 06 September 2019 11:01 UTC

From: "shuaiizhao(Shuai Zhao)" <shuaiizhao@tencent.com>
To: "avt@ietf.org" <avt@ietf.org>, "payload@ietf.org" <payload@ietf.org>
Thread-Topic: New Version Notification for draft-zhao-payload-rtp-vvc-00.txt
Thread-Index: AQHVZKJYqRRcOmORrE+X5hhGdbi6lA==
Date: Fri, 06 Sep 2019 11:00:51 +0000
Message-ID: <2FF04390-52D0-4352-97FE-E3B35CD91A3A@tencent.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.1c.0.190812
Content-Type: multipart/alternative; boundary="_000_2FF0439052D0435297FEE3B35CD91A3Atencentcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/EKUGfsas4gr3IirCZ7vreUy6kzw>
Subject: [payload] FW: New Version Notification for draft-zhao-payload-rtp-vvc-00.txt
Precedence: list

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, "internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>" <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> 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

[payload] FW: New Version Notification for draft-… shuaiizhao(Shuai Zhao)