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

>If people are quick with comments, I can get another version done before our
September 7 meeting;

Some wording about the standards for the signaling between the two Web
servers in Fig.2 would help.
Even if only stating this is out of scope for the rtcweb WG.
(Or does this WG really cover only the single Web server case?)
Leaving many folks scratching their heads...

Thanks, Henry

On 8/24/11 10:08 AM, "Harald Alvestrand" <harald@alvestrand.no> 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