[AVTCORE] RFC 9584 on RTP Payload Format for Essential Video Coding (EVC)

rfc-editor@rfc-editor.org Wed, 12 June 2024 02:58 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 A98D3C1E0D91; Tue, 11 Jun 2024 19:58:21 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 1213E1DEB7A; Tue, 11 Jun 2024 19:58:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240612025821.1213E1DEB7A@rfcpa.rfc-editor.org>
Date: Tue, 11 Jun 2024 19:58:21 -0700
Message-ID-Hash: VNY36YVAGE64G5XVUQORO3KUW3A5MSU4
X-Message-ID-Hash: VNY36YVAGE64G5XVUQORO3KUW3A5MSU4
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-avt.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, avt@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [AVTCORE] RFC 9584 on RTP Payload Format for Essential Video Coding (EVC)
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/1Zzaa46iCLmzXpy-08dOQFElpv0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Owner: <mailto:avt-owner@ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Subscribe: <mailto:avt-join@ietf.org>
List-Unsubscribe: <mailto:avt-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9584

        Title:      RTP Payload Format for Essential 
                    Video Coding (EVC) 
        Author:     S. Zhao,
                    S. Wenger,
                    Y. Lim
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2024
        Mailbox:    shuai.zhao@ieee.org,
                    stewe@stewe.org,
                    yklwhite@gmail.com
        Pages:      42
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avtcore-rtp-evc-07.txt

        URL:        https://www.rfc-editor.org/info/rfc9584

        DOI:        10.17487/RFC9584

This document describes an RTP payload format for the Essential Video
Coding (EVC) standard, published as ISO/IEC International Standard
23094-1. EVC was developed by the MPEG. The RTP payload format allows
for the packetization of one or more Network Abstraction Layer (NAL)
units in each RTP packet payload and the fragmentation of a NAL unit
into multiple RTP packets. The payload format has broad 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