Audio/Video Transport Core Maintenance (avtcore) Internet Drafts

      
 RTP Control Protocol (RTCP) Messages for Temporal-Spatial Resolution
 
 draft-ietf-avtcore-rtcp-green-metadata-17.txt
 Date: 09/09/2026
 Authors: Yong He, Christian Herglotz, Edouard Francois
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 The RTCP messages specified in this document enable receivers to provide feedback to the senders and thus allow for short-term adaptation and feedback-based energy efficient mechanisms to be implemented. The messages have broad applicability in point-to-point real-time video communication services. Specifically, the messages can be used to convey the video decoder feedback metadata to the encoder to adapte the decoder energy consumption as defined in the ISO/IEC International Standard 23001-11, known as Energy Efficient Media Consumption (Green metadata), developed by the ISO/IEC JTC 1/SC29/WG3 MPEG Systems.
 H.265 Profile for WebRTC
 
 draft-ietf-avtcore-hevc-webrtc-09.txt
 Date: 21/07/2026
 Authors: Bernard Aboba, Philipp Hancke, Jianlin Qiu
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 RFC 7742 defines WebRTC video processing and codec requirements, including guidance for endpoints supporting the VP8 and H.264 codecs, which are mandatory to implement. This document defines a profile of RFC 7798 for browsers supporting the H.265 codec.
 RTP Payload Format for V-DMC
 
 draft-ietf-avtcore-rtp-vdmc-03.txt
 Date: 16/09/2026
 Authors: Hyunsik Yang, Xavier de Foy
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This memo outlines RTP payload formats for the Video-based Dynamic Mesh Coding (V-DMC), which comprises several types of components, such as a basemesh, AC-based displacements, 2D representations of attributes, and an atlas. This document focuses on describing the basemesh and displacement, while the RTP payload formats for the atlas and attributes are addressed in other documents. The RTP payload header formats enable the packetization of a basemesh or displacement Network Abstraction Layer (NAL) unit in an RTP packet payload as well as fragmentation of a NAL unit into multiple RTP packets.
 RTP Payload Format for ISO/IEC 21122 (JPEG XS)
 
 draft-ietf-avtcore-rtp-jpegxs-3ed-07.txt
 Date: 14/09/2026
 Authors: Tim Bruylants, Thomas Richter, Corentin Geeroms, Antonin Descampe
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This document specifies a Real-Time Transport Protocol (RTP) payload format for transport of a video signal encoded with JPEG XS (ISO/IEC 21122). JPEG XS is a low-latency and low-complexity video coding system. Employing this format allows achieving encoding-decoding latencies confined to a fraction of a video frame. This document revises RFC 9134 to incorporate support for new features introduced in the third edition of JPEG XS. Most notably, it contains the necessary provisions to support the TDC coding mode. This document obsoletes RFC 9134; however, the revised payload format is designed to ensure that existing conforming implementations of RFC 9134 remain valid under the updated specification. Additionally, this document consolidates the errata of RFC 9134 and includes improvements and clarifications for implementers and users.
 RTP Payload Format for Avatar Representation Format (ARF) Animation Stream
 
 draft-ietf-avtcore-rtp-avatar-02.txt
 Date: 25/08/2026
 Authors: Hyunsik Yang, Xavier de Foy, Ahmed Hamza, Imed Bouazizi
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This memo outlines RTP payload formats for the animation stream format as defined in the ISO/IEC 23090-39 standard (MPEG-I Avatar Representation Format), in the following referred to as ARF. ARF is composed of Avatar Animation Units (AAU) including an AAU header and zero or more AAU packets. The RTP payload header format allows for packetization of an AAU unit in an RTP packet payload as well as fragmentation of an AAU into multiple RTP packets.
 RTCP Feedback Message and Request Mechanism for Frame-level Acknowledgement
 
 draft-ietf-avtcore-frame-acknowledgement-01.txt
 Date: 06/07/2026
 Authors: Erik Sprang, Gurtej Chandok, Shridhar Majali
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This document describes a mechanism for signaling which video frames have been received and decoded by a remote peer. It comprises an RTCP feedback message and an RTP header extension used to request said feedback. One of the main use cases for this data is to implement various forms of Long Term Reference (LTR) reference structures. Additionally, the mechanism provides a way for receivers to request resynchronization frames that reference acknowledged frames, enabling efficient recovery from partial or full frame loss without requiring a full keyframe.

data-group-menu-data-url="/group/groupmenu.json">

Audio/Video Transport Core Maintenance (avtcore)

WG Name Audio/Video Transport Core Maintenance
Acronym avtcore
Area Web and Internet Transport (wit)
State Active
Charter charter-ietf-avtcore-03 Approved
Document dependencies
Additional resources GitHub Organization
Zulip Stream
Personnel Chairs Jonathan Lennox, Marius Kleidl
Area Director Gorry Fairhurst
Mailing list Address [email protected]
To subscribe https://www.ietf.org/mailman/listinfo/avt
Archive https://mailarchive.ietf.org/arch/browse/avt/
Chat Room address https://zulip.ietf.org/#narrow/stream/avtcore

Charter for Working Group

The Real-time Transport Protocol (RTP) along with its associated profiles
and payload formats provides for real-time transmission of audio and
video over unicast and multicast transports. RTP is widely implemented
and deployed for a broad range of applications, from telephony to
television over IP. RTP itself is now an Internet Standard. Its
associated profiles, extensions, and payload formats are currently at
various levels of standards maturity. As new applications emerge, there
is a need for guidelines for the use of the RTP/RTCP protocols and
extensions specific to those applications.

The AVTCORE working group is chartered for the following tasks:

  1. To maintain the core RTP/RTCP specifications and the AVP, SAVP, AVPF,
    and SAVPF profiles. The group will provide architectural guidance for
    extending the protocols and guidelines for their proper use.

  2. To develop application-specific guidelines for the use of RTP/RTCP
    protocols with the AVP, SAVP, AVPF, and SAVPF profiles, and extensions to
    those protocols that are driven by application-specific needs.

  3. To specify and maintain payload formats for use with RTP. The working
    group will develop RTP payload formats for new media codecs, review and
    revise existing payload formats to advance those that are especially
    useful to Internet Standard, and declare others Historic. The group will
    follow the guidelines established in "Guidelines for Writers of RTP
    Payload Format Specifications" [BCP 36] and "How to Write an RTP Payload
    Format" (RFC 8088), and is responsible for maintaining those guidelines.

  4. To evaluate and process proposals for RTP eXtended Report Block
    (XRBLOCK) definitions containing new metrics. The group will work within
    the framework defined by RFC 3611, "RTP Control Protocol Extended Reports
    (RTCP XR)" along with other RTP monitoring architecture being developed
    in the working group. It will follow the guidelines established in RFC
    5968, "Guidelines for Extending the RTP Control Protocol (RTCP)" and RFC
    6390, "Guidelines for Considering New Performance Metric Development".

The AVTCORE working group will coordinate closely with the Security Area
while working on maintenance and enhancements to the SRTP Profile (SAVP).

Milestones

Date Milestone Associated documents
Aug 2026 Submit Proposed Standard for H.265 Profile for WebRTC draft-ietf-avtcore-hevc-webrtc
Aug 2026 Submit Proposed Standard for Absolute Capture Timestamp RTP header extension draft-ietf-avtcore-abs-capture-time
Aug 2026 Submit Proposed Standard for Viewport and Region-of-Interest-Dependent Delivery of Visual Volumetric Media draft-ietf-avtcore-rtp-volumetric-media-roi
Apr 2026 Submit Proposed Standard for RTCP Messages for Temporal-Spatial Resolution draft-ietf-avtcore-rtcp-green-metadata
Feb 2026 Submit Experimental Spec for RTP over QUIC (RoQ) draft-ietf-avtcore-rtp-over-quic
Feb 2026 Submit Proposed Standard for RTP Payload Format for Haptics rfc9993 (was draft-ietf-avtcore-rtp-haptics)
Sep 2025 Submit Proposed Standard for RTP Payload Format for Visual Volumetric Video-based Coding (V3C) rfc10034 (was draft-ietf-avtcore-rtp-v3c)

Done milestones

Date Milestone Associated documents
Done Submit Proposed Standard for RTP Payload Format for sub-codestream latency JPEG 2000 streaming rfc9828 (was draft-ietf-avtcore-rtp-j2k-scl)
Done Submit RTP Payload format for Essential Video Coding (EVC) rfc9584 (was draft-ietf-avtcore-rtp-evc)
Done Submit RTP Mixer Formatting of Multi-party Real-time Text rfc9071 (was draft-ietf-avtcore-multi-party-rtt-mix)
Done Submit RTP Payload format for Versatile Video Coding (VVC) rfc9328 (was draft-ietf-avtcore-rtp-vvc)
Done Submit RTP Payload Format for TTML Timed Text for Proposed Standard rfc8759 (was draft-ietf-payload-rtp-ttml)
Done Submit RTP Payload Format for ISO/IEC 21122 (JPEG XS) for Proposed Standard rfc9134 (was draft-ietf-payload-rtp-jpegxs)
Done Submit RTP Payload Format for VP9 Video for Proposed Standard rfc9628 (was draft-ietf-payload-vp9)
Done Submit Feedback Mechanism for RTP Congestion Control for Proposed Standard rfc8888 (was draft-ietf-avtcore-cc-feedback-message)
Done Submit RTP Header Extension for Video Frame Information for Proposed Standard rfc9626 (was draft-ietf-avtext-framemarking)
Done Submit Guidelines for using the Multiplexing Features of RTP for Informational rfc8872 (was draft-ietf-avtcore-multiplex-guidelines)