Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-06.txt

From: Colin Perkins <[email-masked]>
Date: Sun, 10 Mar 2013 16:47:17 -0400

On 25 Feb 2013, at 16:14, [email-masked] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF.
> 
> 	Title           : Web Real-Time Communication (WebRTC): Media Transport and Use of RTP
> 	Author(s)       : Colin Perkins
>                          Magnus Westerlund
>                          Joerg Ott
> 	Filename        : draft-ietf-rtcweb-rtp-usage-06.txt
> 	Pages           : 62
> 	Date            : 2013-02-25
> 
> Abstract:
>   The Web Real-Time Communication (WebRTC) framework provides support
>   for direct interactive rich communication using audio, video, text,
>   collaboration, games, etc. between two peers' web-browsers.  This
>   memo describes the media transport aspects of the WebRTC framework.
>   It specifies how the Real-time Transport Protocol (RTP) is used in
>   the WebRTC context, and gives requirements for which RTP features,
>   profiles, and extensions need to be supported.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-rtp-usage
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-06

This is a minor updates. The changes are:

- Expand and clarify discussion of RTP session multiplexing in Section 4.4

- Add Section 7.2 on RTCP extensions for congestion control

- Clarify Section 12.1 on RTP Sessions and PeerConnections

- Expand Section 12.4 on SSRC collision detections

- Rewrite and clarify Section 12.5 on Contributing Sources and the CSRC list

- Rewrite and clarify Section 12.9 on differentiated treatment of flows

- Expand security considerations

There's time on the agenda to discuss use of RTCP XR metrics, which is one of the open issues with this draft. If there are any more general comments, please send them by email.

-- 
Colin Perkins
http://csperkins.org/