Audio/Video Transport Core Maintenance (avtcore)
------------------------------------------------
Charter
Last Modified: 2011-01-25
Current Status: Active Working Group
Chair(s):
Roni Even <even.roni@huawei.com>
Magnus Westerlund <magnus.westerlund@ericsson.com>
Real-time Applications and Infrastructure Area Director(s):
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Robert Sparks <rjsparks@nostrum.com>
Real-time Applications and Infrastructure Area Advisor:
Robert Sparks <rjsparks@nostrum.com>
Secretary(ies):
Tom Taylor <tom111.taylor@bell.net>
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
Jan 2011 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
Internet-Drafts:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Jun 2007 Mar 2011 <draft-ietf-avt-app-rtp-keepalive-10.txt>
Application Mechanism for keeping alive the Network Address
Translator (NAT) mappings associated to RTP/RTCP flows.
Sep 2007 Aug 2010 <draft-ietf-avt-forward-shifted-red-06.txt>
Forward-shifted RTP Redundancy Payload Support
Jul 2008 Jul 2010 <draft-ietf-avt-srtp-not-mandatory-07.txt>
Why RTP Does Not Mandate a Single Security Mechanism
Jul 2009 Jan 2011 <draft-ietf-avt-srtp-aes-gcm-01.txt>
AES-GCM and AES-CCM Authenticated Encryption in Secure RTP
(SRTP)
Jan 2011 Jan 2011 <draft-ietf-avtcore-srtp-vbr-audio-00.txt>
Guidelines for the use of Variable Bit Rate Audio with Secure
RTP
Jan 2011 Jan 2011 <draft-ietf-avtcore-ecn-for-rtp-00.txt>
Explicit Congestion Notification (ECN) for RTP over UDP
Jan 2011 Jan 2011 <draft-ietf-avtcore-ports-for-ucast-mcast-rtp-00.txt>
Port Mapping Between Unicast and Multicast RTP Sessions
Feb 2011 Feb 2011 <draft-ietf-avtcore-feedback-supression-rtp-00.txt>
RTCP Extension for Feedback Suppression Indication
Request For Comments:
None to date.