datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

Audio/Video Transport Extensions (avtext)

Group
Name: Audio/Video Transport Extensions
Acronym:avtext
Area:Real-time Applications and Infrastructure Area (rai)
State: Active
Charter: charter-ietf-avtext-01 (Approved)
Personnel
Chairs: Keith Drage <keith.drage@alcatel-lucent.com>
Jonathan Lennox <jonathan@vidyo.com>
Area Director: Richard Barnes <rlb@ipv.sx>
Mailing List
Address:avtext@ietf.org
To Subscribe:https://www.ietf.org/mailman/listinfo/avtext
Archive:http://www.ietf.org/mail-archive/web/avtext/
Jabber Chat
Room Address: xmpp:avtext@jabber.ietf.org
Logs: http://jabber.ietf.org/logs/avtext/

Charter for 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.

Milestones

Done
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
Done
Submit Support for multiple clock rates in an RTP session for Proposed Standard
Done
Content splicing for RTP sessions as Informational
Done
Request Publication of specification for duplicating RTP Streams with intended status as Proposed Standard
Oct 2013
Taxonomy of RTP (as informational) to IESG
draft-ietf-avtext-rtp-grouping-taxonomy
Nov 2014
Submit Mechanism for RTP Stream Pause & Resume for Proposed Standard
draft-ietf-avtext-rtp-stream-pause
Nov 2015
Submit Mechanism for Indication of Content Splicing Times in Multimedia Content for Proposed Standard