[AVTCORE] FW: I-D Action: draft-ietf-avtcore-rtp-vvc-05.txt(Internet mail)

"shuaiizhao(Shuai Zhao)" <shuaiizhao@tencent.com> Mon, 02 November 2020 22:11 UTC

Return-Path: <shuaiizhao@tencent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 66A393A1294 for <avt@ietfa.amsl.com>; Mon, 2 Nov 2020 14:11:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tencent.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 2zeD8N9gUAf1 for <avt@ietfa.amsl.com>; Mon, 2 Nov 2020 14:11:26 -0800 (PST)
Received: from mail3.tencent.com (mail3.tencent.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D7E93A1389 for <avt@ietf.org>; Mon, 2 Nov 2020 14:11:10 -0800 (PST)
Received: from EX-SZ021.tencent.com (unknown []) by mail3.tencent.com (Postfix) with ESMTP id 20FDC94263 for <avt@ietf.org>; Tue, 3 Nov 2020 06:11:09 +0800 (CST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tencent.com; s=s202002; t=1604355069; bh=OWLfZ4BEIsvgP67g8GiX6xj1Wt0bqGSds7tvzxIINL8=; h=From:To:Subject:Date:References:In-Reply-To; b=U29bAudjS9F//XqCvj+/3+iaAwWHbgpfmdgEOb+LDIizNfZxkTjWInUxdHj+HDEAY khTX7jSXmPdvZzLwHwjVQVay7V7xLxOxyuCrNZbbht9niad4wvzXpyhruOy/Sr7O/4 d2Pf2gbhrAneTl8XrJKkJTraA08fSLSv9V50/wpU=
Received: from EX-US02.tencent.com ( by EX-SZ021.tencent.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 3 Nov 2020 06:11:08 +0800
Received: from EX-US01.tencent.com ( by EX-US02.tencent.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 3 Nov 2020 06:11:07 +0800
Received: from EX-US01.tencent.com ([fe80::2871:b384:ea95:2ddc]) by EX-US01.tencent.com ([fe80::2871:b384:ea95:2ddc%4]) with mapi id 15.01.2106.002; Tue, 3 Nov 2020 06:11:07 +0800
From: "shuaiizhao(Shuai Zhao)" <shuaiizhao@tencent.com>
To: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-vvc-05.txt(Internet mail)
Thread-Index: AQHWsWR/pstVRYglAE6Cv29jmwvMgqm0WxuA
Date: Mon, 2 Nov 2020 22:11:06 +0000
Message-ID: <D8FE659E-2998-4902-83D1-1B89E95947D0@tencent.com>
References: <160435478934.13143.10979812851215084343@ietfa.amsl.com>
In-Reply-To: <160435478934.13143.10979812851215084343@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
user-agent: Microsoft-MacOutlook/16.42.20101102
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D8FE659E2998490283D11B89E95947D0tencentcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/YNCeF6xH8mBDmc8cd-iHBDq3g6g>
Subject: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-rtp-vvc-05.txt(Internet mail)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2020 22:11:36 -0000

In this revision, Yago’s proposal for SDP parameters were implemented in section 7.2.1.

Editor’s notes were added for things we will provide clearfication in next revision.  So do review and critisize lightly. ☺


From: avt <avt-bounces@ietf.org> on behalf of "internet-drafts@ietf.org" <internet-drafts@ietf.org>
Reply-To: "avt@ietf.org" <avt@ietf.org>
Date: Monday, November 2, 2020 at 14:07
To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-vvc-05.txt(Internet mail)

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Core Maintenance WG of the IETF.

        Title           : RTP Payload Format for Versatile Video Coding (VVC)
        Authors         : Shuai Zhao
                          Stephan Wenger
                          Yago Sanchez
                          Ye-Kui Wang
                Filename        : draft-ietf-avtcore-rtp-vvc-05.txt
                Pages           : 61
                Date            : 2020-11-02

   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 datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

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.

Internet-Drafts are also available by anonymous FTP at:

Audio/Video Transport Core Maintenance