Audio/Video Transport Core Maintenance (avtcore)

Last Modified: 2011-08-18

Additional information is available at tools.ietf.org/wg/avtcore

Chair(s):

Real-time Applications and Infrastructure Area Director(s):

Real-time Applications and Infrastructure Area Advisor:

Secretary(ies):

Mailing Lists:

General Discussion: avt@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/avt
Archive: http://www.ietf.org/mail-archive/web/avt/index.html

Description of 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 itself has
been shepherded to Full Standard. Its associated profiles, extensions,
and payload formats are currently at various levels of standards maturity.

The AVTCORE working group is chartered 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. While other working groups may be
chartered to work on application-specific extensions to the protocols,
extensions that are generally applicable will be developed in AVTCORE.

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

In addition to the milestones called out below, the AVTCORE working
group's initial tasks will include completing any remaining work
identified in those drafts from the AVT working group already in IESG
Evaluation, with the exception of the Rapid Acquisition of Multicast RTP
sessions, which will complete in the AVTEXT working group.

Goals and Milestones:

Done  Submit Guideline for Choosing RTCP CNAME as Proposed Standard
Done  Submit use of AES-192 and AES-256 in Secure RTP for Proposed Standard
Done  Submit Port Mapping Between Unicast and Multicast RTP Sessions for Proposed Standard
Feb 2011  Submit Monitoring Architecture for RTP for Informational
Done  Submit Guidelines for the use of Variable Bit Rate Audio with Secure RTP as Informational (or possibly BCP)
Apr 2011  Submit in band keying mechanism for SRTP draft for Proposed Standard
Apr 2011  Submit Explicit Congestion Notification (ECN) for RTP over UDP for Proposed Standard
May 2011  Submit RTCP indication for retransmission suppression as Proposed Standard
Sep 2011  Submit Encryption of Header Extensions in the Secure Real-Time Transport Protocol (SRTP) for Proposed Standard
Dec 2011  Submit Real-Time Transport Control Protocol (RTCP) in Overlay Multicast for Proposed Standard
Mar 2012  Submit Specification for Inter-destination Media Playout Synchronization in RTP to IESG for publication as Proposed Standard

Internet-Drafts:

Why RTP Does Not Mandate a Single Security Mechanism (24339 bytes)
AES-GCM and AES-CCM Authenticated Encryption in Secure RTP (SRTP) (46403 bytes)
Guidelines for the use of Variable Bit Rate Audio with Secure RTP (13999 bytes)
Explicit Congestion Notification (ECN) for RTP over UDP (148251 bytes)
RTCP Extension for Third-party Loss Report (37549 bytes)
Monitoring Architectures for RTP (40118 bytes)
Encryption of Header Extensions in the Secure Real-Time Transport Protocol (SRTP) (28714 bytes)
RTCP for inter-destination media synchronization (55050 bytes)

Request For Comments:

Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) Flows (RFC 6263) (23345 bytes)
Port Mapping Between Unicast and Multicast RTP Sessions (RFC 6284) (73289 bytes)
Forward-Shifted RTP Redundancy Payload Support (RFC 6354) (26488 bytes) updates RFC 2198,RFC 4102