Re: [rtcweb] Fwd: New Version Notification for draft-ietf-rtcweb-overview-01.txt

Harald,

This looks good. I just have two very minor comments regarding Section 5:

- The correct reference for SRTP is RFC3711, not RFC3550 (the security mechanism in RFC3550 is not compatible with SRTP).

- I agree with the sentiment that "SRTP is used for transport of all real-time media", however this leaves open the choice of RTP profile (there are several that use SRTP). It might be useful to reference draft-perkins-rtcweb-rtp-usage, since that addresses this question.

Cheers,
Colin

On 24 Aug 2011, at 16:08, Harald Alvestrand wrote:
> A few drawings, some more definitions, and a link to the W3C API spec.
> 
> If people are quick with comments, I can get another version done before our September 7 meeting; version numbers are cheap.
> 
>                Harald
> 
> -------- Original Message --------
> Subject:	New Version Notification for draft-ietf-rtcweb-overview-01.txt
> Date:	Wed, 24 Aug 2011 07:37:14 -0700
> From:	internet-drafts@ietf.org
> To:	harald@alvestrand.no
> CC:	harald@alvestrand.no
> 
> A new version of I-D, draft-ietf-rtcweb-overview-01.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository.
> 
> Filename:	 draft-ietf-rtcweb-overview
> Revision:	 01
> Title:		 Overview: Real Time Protocols for Brower-based Applications
> Creation date:	 2011-08-24
> WG ID:		 rtcweb
> Number of pages: 17
> 
> Abstract:
>    This document gives an overview and context of a protocol suite
>    intended for use with real-time applications that can be deployed in
>    browsers - &quot;real time communication on the Web&quot;.
> 
>    It intends to serve as a starting and coordination point to make sure
>    all the parts that are needed to achieve this goal are findable, and
>    that the parts that belong in the Internet protocol suite are fully
>    specified and on the right publication track.
> 
>    This work is an attempt to synthesize the input of many people, but
>    makes no claims to fully represent the views of any of them.  All
>    parts of the document should be regarded as open for discussion,
>    unless the RTCWEB chairs have declared consensus on an item.
> 
>    This document is a candidate to become a work item of the RTCWEB
>    working group.
> 
> 
>                                                                                   
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

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