WG Action: RECHARTER: Audio/Video Transport WG (avt)

IESG Secretary <iesg-secretary@ietf.org> Tue, 23 October 2007 21:15 UTC

Return-path: <ietf-announce-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkR67-0007FW-3C; Tue, 23 Oct 2007 17:15:35 -0400
Received: from [] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkR64-0007DI-QO for ietf-announce@ietf.org; Tue, 23 Oct 2007 17:15:32 -0400
Received: from ns4.neustar.com ([]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkR64-0001hg-6a for ietf-announce@ietf.org; Tue, 23 Oct 2007 17:15:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com []) by ns4.neustar.com (Postfix) with ESMTP id 1AF2F2AC8B; Tue, 23 Oct 2007 21:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IkR5Z-0004Xa-Re; Tue, 23 Oct 2007 17:15:01 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce@ietf.org
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1IkR5Z-0004Xa-Re@stiedprstage1.ietf.org>
Date: Tue, 23 Oct 2007 17:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: Roni Even <roni.even@polycom.co.il>, Colin Perkins <csp@csperkins.org>, Tom Taylor <tom.taylor@rogers.com>
Subject: WG Action: RECHARTER: Audio/Video Transport WG (avt)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

The charter of the Audio/Video Transport (avt) working group in the
Real-time Applications and Infrastructure Area of the IETF has been
updated. For additional information, please contact the Area Directors 
or the working group Chairs.


Audio/Video Transport (avt)

Current Status: Active Working Group

Colin Perkins <csp@csperkins.org> 
Roni Even <roni.even@polycom.co.il> 
Tom Taylor <tom.taylor@rogers.com> 

Real-time Applications and Infrastructure Area Director(s):
Jon Peterson <jon.peterson@neustar.biz> 
Cullen Jennings <fluffy@cisco.com> 

Real-time Applications and Infrastructure Area Advisor:
Cullen Jennings <fluffy@cisco.com> 

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

Description of Working Group:

The Audio/Video Transport Working Group was formed to specify a 
protocol for real-time transmission of audio and video over unicast 
and multicast UDP/IP. This is the Real-time Transport Protocol, RTP, 
together with its associated profiles and payload formats. The 
current aims of the working group are:

- to review and revise existing payload formats to advance those 
are useful to Draft Standard, and to declare others as Historic.
Milestones will be established as a champion for each payload
format is identified.

- to develop payload formats for new media codecs, and to document
best-current practices in payload format design. The group 
to be precluded from work on codecs themselves because of 
overlap with
the other standards bodies, and because the IETF does not have the
ability to effectively review new codecs. An exception was made 
the freeware iLBC codec on a highly experimental basis, but 
of new codec work is unexpected and subject to rechartering.

- to complete the forward error correction work to update RFC 
2733 in
the form of the ULP payload format

- to extend RTP to work with Source-Specific Multicast sessions with
unicast feedback

- to provide a framing mechanism for RTP over TCP and TLS

- in collaboration with the MPLS and ROHC WGs, to develop a solution
for header compression of RTP across MPLS networks that avoid
decompression and compression at each MPLS node.

- to develop a new RTP profile for the combination of the SRTP 
and the Extended RTP Profile for RTCP-based Feedback (RTP/SAVPF)

- to maintain and enhance the SRTP Profile, with review and input 
the Security Area

- to develop a new RTP profile for usage of TFRC (RFC 3448) with RTP
over UDP to allow application developers to gain experience 
with TCP
friendly congestion control.

- to develop a MIB for RTCP XR (RFC 3611).

- to update the RTP MIB, including aligning it with RFC 3550.

- to clarify how RTP is used for media in conferencing with 
nodes performing relay, translation or mixing of media.

- to develop the mechanisms needed for efficient control of media 
its encoding process in RTP based conferencing, both over 
and transport containing relays, translators and mixers. An 
example of
such a mechanism is a method to request a full intra coded 
frame of
video. This would be used to allow joining participants to receive
video immediately after joining instead of waiting for the next 
coded frame. It also allows mixers to perform switching between 
sources without the need to re-encode the media.

- to develop a solution for carrying media meta data, specifically
SMPTE timestamps, to enhance the media stream. Such transport 
may be
done in either RTP or RTCP depending on which is most suitable. 
The WG
may consider if a generalized mechanism should be developed to 
future types of meta data to be easier to include.

- to develop two new metric blocks for the RTCP XR (RFC 3611) 
to provide information on the media quality experienced by the
receiver of RTP flows. One metrics block is for high resolution
measurements of audio and speech quality. A second one for 
information on the quality of video. The timescale to complete 
second block and the included metrics are highly dependable on the
development of standardized subjective metrics for video 
quality. The
WG will consider what metrics that are available and if they 
should be
included or not. The metrics blocks shall not duplicate signalling
information anyway necessary for the establishment of the session.

- to specify how the RFC 3550 requirement on RTCP senders to always
send compound packets can be relaxed to allow for non-compound
packets. The specification need to define under which criteria
non-compound RTCP packets may be sent while maintaining the
functionality that motivated the usage of compound RTCP packets
and keep the bandwidth within specified limits.

The longer term goals of the working group are to advance the SRTP 
Profile, the Extended RTP Profile for RTCP-based Feedback, the 
Compressed RTP framework, and the RTP MIB to Draft Standard.

The group has no plans to develop new RTP profiles beyond those 
listed above, but will consider rechartering to produce profile level 
extensions if appropriate.


- Sep 2008 Submit Non-Compound usage specification for PS

IETF-Announce mailing list