Re: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-12.txt

A few comments:

General: I believe the overview document should include the gateway document, rather than being a separate document.

2.4: Definition of WebRTC device: This refers to protocols, but does not say what the scope of those protocols are. Does it include only the protocols listed in this document, other protocols that could be used in conjunction with webrtc, or what.

5: My understanding is that one of the security documents is a requirements document, which leads to the other document containing the security specification. Therefore the reference to the first should be at most informative, and the normative reference only to the second. I sought clarification on this at the last meeting, and that was the understanding I received. 

I believe it would be useful to have an offline discussion in Honolulu to spend some time reviewing the overview and gateway documents. Would there be an hour somewhere to slot this in. It would at least be useful to know what direction you think should be taking on the on-list discussion of some of the terms.

Regards

Keith

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of 
> internet-drafts@ietf.org
> Sent: 13 October 2014 10:51
> To: i-d-announce@ietf.org
> Cc: rtcweb@ietf.org
> Subject: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-12.txt
> 
> 
> 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           : Overview: Real Time Protocols for 
> Browser-based Applications
>         Author          : Harald T. Alvestrand
> 	Filename        : draft-ietf-rtcweb-overview-12.txt
> 	Pages           : 22
> 	Date            : 2014-10-13
> 
> 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 - "real time communication on the Web".
> 
>    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 document is an Applicability Statement - it does not itself
>    specify any protocol, but specifies which other 
> specifications WebRTC
>    compliant implementations are supposed to follow.
> 
>    This document is a work item of the RTCWEB working group.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-overview/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtcweb-overview-12
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-overview-12
> 
> 
> Please note that it may take a couple of minutes from the 
> time of submission until the htmlized version and diff are 
> available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> 