Audio/Video Transport Core Maintenance (avtcore) Internet Drafts

      
 RTP Payload Format for VP9 Video
 
 draft-ietf-payload-vp9-16.txt
 Date: 10/06/2021
 Authors: Justin Uberti, Stefan Holmer, Magnus Flodman, Danny Hong, Jonathan Lennox
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This specification describes an RTP payload format for the VP9 video codec. The payload format has wide applicability, as it supports applications from low bit-rate peer-to-peer usage, to high bit-rate video conferences. It includes provisions for temporal and spatial scalability.
 Video Frame Marking RTP Header Extension
 
 draft-ietf-avtext-framemarking-16.txt
 Date: 04/03/2024
 Authors: Mo Zanaty, Espen Berger, Suhas Nandakumar
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This document describes a Video Frame Marking RTP header extension used to convey information about video frames that is critical for error recovery and packet forwarding in RTP middleboxes or network nodes. It is most useful when media is encrypted, and essential when the middlebox or node has no access to the media decryption keys. It is also useful for codec-agnostic processing of encrypted or unencrypted media, while it also supports extensions for codec- specific information.
 RTP over QUIC (RoQ)
 
 draft-ietf-avtcore-rtp-over-quic-12.txt
 Date: 21/10/2024
 Authors: Mathis Engelbart, Joerg Ott, Spencer Dawkins
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This document specifies a minimal mapping for encapsulating Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) packets within the QUIC protocol. This mapping is called RTP over QUIC (RoQ). This document also discusses how to leverage state that is already available from the QUIC implementation in the endpoints, in order to reduce the need to exchange RTCP packets, and describes different options for implementing congestion control and rate adaptation for RTP without relying on RTCP feedback.
 RTP Payload Format for Visual Volumetric Video-based Coding (V3C)
 
 draft-ietf-avtcore-rtp-v3c-07.txt
 Date: 19/09/2024
 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-04.txt
 Date: 07/10/2024
 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.
 H.265 Profile for WebRTC
 
 draft-ietf-avtcore-hevc-webrtc-06.txt
 Date: 15/11/2024
 Authors: Bernard Aboba, Philipp Hancke
 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. With support for H.265 under development in WebRTC browsers, similar guidance is needed for browsers considering support for the H.265 codec, whose RTP payload format is defined in RFC 7798.
 RTP Payload Format for sub-codestream latency JPEG 2000 streaming
 
 draft-ietf-avtcore-rtp-j2k-scl-04.txt
 Date: 08/10/2024
 Authors: Pierre-Anthony Lemieux, David Taubman
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 This RTP payload format defines the streaming of a video signal encoded as a sequence of JPEG 2000 codestreams. The format allows sub-codestream latency, such that the first RTP packet for a given codestream can be emitted before the entire codestream is available.
 RTP Payload for Haptics
 
 draft-ietf-avtcore-rtp-haptics-01.txt
 Date: 05/07/2024
 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.
 Closing the RTP Payload Format Media Types IANA Registry
 
 draft-ietf-avtcore-rtp-payload-registry-05.txt
 Date: 18/10/2024
 Authors: Magnus Westerlund
 Working Group: Audio/Video Transport Core Maintenance (avtcore)
 A number of authors of RTP Payload Formats and the WG process have failed to ensure that the media types for RTP payload formats is registred in the IANA registry "RTP Payload Formats Media Types" as recommended by RFC 8088. To simplify the process and rely only on the media types registry this document closes the RTP payload specific registry. In addition it updates the instruction to payload format authors in RFC 8088 to reflect this change.

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
Issue tracker
Wiki
Zulip Stream
Personnel Chairs Dr. Bernard D. Aboba, Jonathan Lennox
Area Director Zaheduzzaman Sarker
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
Jul 2021 Submit RTP Payload format for Essential Video Coding (EVC)
Feb 2021 Submit RTP Mixer Formatting of Multi-party Real-time Text rfc9071 (was draft-ietf-avtcore-multi-party-rtt-mix)
Feb 2021 Submit RTP Payload format for Versatile Video Coding (VVC) rfc9328 (was draft-ietf-avtcore-rtp-vvc)
Mar 2020 Submit RTP Payload Format for ISO/IEC 21122 (JPEG XS) for Proposed Standard rfc9134 (was draft-ietf-payload-rtp-jpegxs)
Nov 2019 Submit RTP Payload Format for VP9 Video for Proposed Standard draft-ietf-payload-vp9
Jun 2019 Submit Feedback Mechanism for RTP Congestion Control for Proposed Standard rfc8888 (was draft-ietf-avtcore-cc-feedback-message)
Apr 2019 Submit RTP Header Extension for Video Frame Information for Proposed Standard draft-ietf-avtext-framemarking

Done milestones

Date Milestone Associated documents
Done Submit RTP Payload Format for TTML Timed Text for Proposed Standard rfc8759 (was draft-ietf-payload-rtp-ttml)
Done Submit Guidelines for using the Multiplexing Features of RTP for Informational