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 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
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 rfc9628 (was 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 rfc9626 (was 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