IETF 79 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Audio/Video Transport Core Maintenance (avtcore) (WG)

No Minutes Submitted  | Audio Archives  |  Jabber Logs  |  Mailing List Archives

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

Chair(s): Magnus Westerlund Roni Even Real-time Applications and Infrastructure Area Director(s): Gonzalo Camarillo Robert Sparks * The Real-time Applications and Infrastructure Area Directors were seated during the IETF 65. Real-time Applications and Infrastructure Area Advisor: Robert Sparks Secretary(ies): Tom Taylor

Meeting Slides

No Slides Present

Internet-Drafts:

• Application Mechanism for keeping alive the Network Address Translator (NAT) mappings associated to RTP/RTCP flows. (22603 bytes)
• Forward-shifted RTP Redundancy Payload Support (26213 bytes)
• Why RTP Does Not Mandate a Single Security Mechanism (20493 bytes)
• AES-GCM and AES-CCM Authenticated Encryption in Secure RTP (SRTP) (38445 bytes)
• Encrypted Key Transport for Secure RTP (111945 bytes)
• Guidelines for the use of Variable Bit Rate Audio with Secure RTP (13744 bytes)
• Explicit Congestion Notification (ECN) for RTP over UDP (139084 bytes)
• Port Mapping Between Unicast and Multicast RTP Sessions (75069 bytes)
• RTCP Extension for Feedback Suppression Indication (39360 bytes)
• Monitoring Architectures for RTP (40382 bytes)

No Request For Comments

Charter (as of 2011-04-15)

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
Feb 2011		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