[AVTCORE] RFC 9328 on RTP Payload Format for Versatile Video Coding (VVC)
rfc-editor@rfc-editor.org Wed, 21 December 2022 05:50 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 765B4C14CE34; Tue, 20 Dec 2022 21:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.647
X-Spam-Level:
X-Spam-Status: No, score=-6.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAHRfrNF5NLs; Tue, 20 Dec 2022 21:50:14 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C79BBC14F75F; Tue, 20 Dec 2022 21:50:09 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6BB121A0A361; Tue, 20 Dec 2022 21:50:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, avt@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221221055009.6BB121A0A361@rfcpa.amsl.com>
Date: Tue, 20 Dec 2022 21:50:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/FLehDMeFWENnucOQZTO_zM2VHsg>
Subject: [AVTCORE] RFC 9328 on RTP Payload Format for Versatile Video Coding (VVC)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 21 Dec 2022 05:50:18 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9328
Title: RTP Payload Format for Versatile Video Coding (VVC)
Author: S. Zhao,
S. Wenger,
Y. Sanchez,
Y.-K. Wang,
M. M Hannuksela
Status: Standards Track
Stream: IETF
Date: December 2022
Mailbox: shuai.zhao@ieee.org,
stewe@stewe.org,
yago.sanchez@hhi.fraunhofer.de,
yekui.wang@bytedance.com,
miska.hannuksela@nokia.com
Pages: 54
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avtcore-rtp-vvc-18.txt
URL: https://www.rfc-editor.org/info/rfc9328
DOI: 10.17487/RFC9328
This memo describes an RTP payload format for the Versatile Video
Coding (VVC) specification, which was published as both ITU-T
Recommendation H.266 and ISO/IEC International Standard 23090-3. VVC
was 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.
This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC