Audio/Video Transport Core Maintenance (avtcore) Internet Drafts

      
 RTP Payload Format for Visual Volumetric Video-based Coding (V3C)
 
 draft-ietf-avtcore-rtp-v3c-11.txt
 Date: 11/08/2025
 Authors: Lauri Ilola, Lukasz Kondrad
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 A visual volumetric video-based coding (V3C) [ISO.IEC.23090-5] bitstream is composed of V3C units that contain V3C atlas sub- bitstreams, V3C video sub-bitstreams, and a V3C parameter set. This memo describes an RTP payload format for V3C atlas sub-bitstreams. The RTP payload format for V3C video sub-bitstreams is defined by relevant Internet Standards for the applicable video codec. The V3C RTP payload format allows for packetization of one or more V3C atlas Network Abstraction Layer (NAL) units in an RTP packet payload as well as fragmentation of a V3C atlas NAL unit into multiple RTP packets. The memo also describes the mechanisms for grouping RTP streams of V3C component sub-bitstreams, providing a complete solution for streaming V3C encoded content.
 RTP Control Protocol (RTCP) Messages for Temporal-Spatial Resolution
 
 draft-ietf-avtcore-rtcp-green-metadata-06.txt
 Date: 14/08/2025
 Authors: Yong He, Christian Herglotz, Edouard Francois
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This specification describes an RTCP feedback message format for the ISO/IEC International Standard 23001-11, known as Energy Efficient Media Consumption (Green metadata), developed by the ISO/IEC JTC 1/SC 29/ WG 3 MPEG System. The RTCP payload format specified in this specification enables receivers to provide feedback to the senders and thus allows for short-term adaptation and feedback-based energy efficient mechanisms to be implemented. The payload format has broad applicability in real-time video communication services.
 RTP Payload Format for SFrame
 
 draft-ietf-avtcore-rtp-sframe-01.txt
 Date: 07/10/2025
 Authors: Peter Thatcher, Youenn Fablet
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This document describes the RTP payload format of SFrame.
 RTP Payload Format for Haptics
 
 draft-ietf-avtcore-rtp-haptics-07.txt
 Date: 13/05/2025
 Authors: Hyunsik Yang, Xavier de Foy
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This memo describes an RTP payload format for the MPEG-I haptic data. A haptic media stream is composed of MIHS units including a MIHS(MPEG-I Haptic Stream) unit header and zero or more MIHS packets. The RTP Payload header format allows for packetization of a MIHS unit in an RTP packet payload as well as fragmentation of a MIHS unit into multiple RTP packets. The original subtype registration for haptics/ hmpg, registered with IANA in RFC9695, did not include any required or optional parameters. This memo updates RFC9695 and the haptics/ hmpg registration to add optional parameters.
 Viewport and Region-of-Interest-Dependent Delivery of Visual Volumetric Media
 
 draft-ietf-avtcore-rtp-volumetric-media-roi-00.txt
 Date: 04/05/2025
 Authors: Srinivas Gudumasu, Ahmed Hamza
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This document describes RTCP messages and RTP header extensions to enable partial access and support viewport- and region-of-interest- dependent delivery of visual volumetric media such as visual volumetric video-based coding (V3C). Partial access refers to the ability to access retrieve or deliver only a subset of the media content. The RTCP messages and RTP header extensions described in this document are useful for XR services which transport coded visual volumetric content, such as point clouds.
 SDP Offer/Answer for RTP over QUIC (RoQ)
 
 draft-ietf-avtcore-sdp-roq-00.txt
 Date: 11/10/2025
 Authors: Spencer Dawkins, Victor Avila
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This document is intended to allow the use of QUIC as an underlying transport protocol for RTP applications that commonly use SDP as a session signaling protocol to set up RTP connections, such as SIP and WebRTC. The document describes several new SDP "proto" and "attribute-name" attribute values in the "Session Description Protocol (SDP) Parameters" IANA registry that can be used to describe QUIC transport for RTP and RTCP packets, and describes how SDP Offer/ Answer can be used to set up an RTP connection using QUIC. This document also contains non-normative guidance for implementers.

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 avt@ietf.org
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 draft-ietf-avtcore-rtp-haptics
Sep 2025 Submit Proposed Standard for RTP Payload Format for Visual Volumetric Video-based Coding (V3C) 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)