Audio/Video Transport Extensions (avtext) ----------------------------------------- Charter Last Modified: 2011-12-09 Current Status: Active Working Group Chair(s): Keith Drage Magnus Westerlund Real-time Applications and Infrastructure Area Director(s): Gonzalo Camarillo Robert Sparks Real-time Applications and Infrastructure Area Advisor: Gonzalo Camarillo Mailing Lists: General Discussion:avtext@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/avtext Archive: http://www.ietf.org/mail-archive/web/avtext/index.html Description of Working Group: The Full-Standard Real-time Transport Protocol, RTP [RFC 3550], 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 wide range of applications, ranging from telephony to television over IP. As new applications have emerged, the need for guidelines for the use of the RTP/RTCP protocols and extensions specific to those applications has been identified. The AVTEXT working group is charted 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. Proposals for extensions with general applicability to many different RTP/RTCP usages should be taken to the AVTCORE working group. The AVTEXT working group is constrained to use the protocol extension mechanisms defined in the core protocols (such as RTP Header extensions [RFC5285], AVPF Feedback Messages [RFC4585], and SDES Items [RFC3550]). If new ways to extend the core protocols are needed, they will be developed in the AVTCORE working group. In addition to the milestones called out below, the AVTEXT working group's initial tasks will include completing any new work identified during IESG evaluation for the Rapid Acquisition of Multicast RTP Sessions. Goals and Milestones: Jun 2011 Submit Considerations for RAMS Scenarios for Informational Done Submit RTP Header extension for mixer to client audio level indication as Proposed Standard Done Submit RTP Header extension for client to mixer audio level indication as proposed standard Dec 2011 Submit Support for multiple clock rates in an RTP session for Proposed Standard Dec 2011 Content splicing for RTP sessions as Informational Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jun 2011 Jan 2012 Support for multiple clock rates in an RTP session Jun 2011 Jan 2012 Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) Method Oct 2011 Feb 2012 Content Splicing for RTP Sessions Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC6332 PS Jul 2011 Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs) RFC6464 PS Dec 2011 A Real-Time Transport Protocol (RTP) Header Extension for Client-to- Mixer Audio Level Indication RFC6465 PS Dec 2011 A Real-Time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication