[RTW] [dispatch] Fwd: New Version Notification for draft-alvestrand-dispatch-rtcweb-protocols-00

[Peter Musgrave]

I'd also like to echo Alan's thanks for these drafts. 

The protocol doc is very clear. [If you read only one dispatch draft this Christmas, make it this one. ;-)  ]

One observation to the group. The mandatory to implement video CODEC is VP8 (presumably since it does not have IPR issues - which some other choices would have). 

Regards, 

Peter Musgrave


Nits
Introduction
s/veichle/vehicle/

Section 2 Para "Within each.."
s/implementaiton/implementation/

Section 4 Para1
"such as" (something missing here?)

Section 5 Para2
"There is no third mandatory to implement" 
? Was there a mention of a third before. Not sure why this statement is there.


On 2010-11-10, at 6:34 AM, Harald Alvestrand wrote:

> This is the overview document for the IETF-related RTC-WEB work.
> 
> -------- Original Message --------
> Subject:	New Version Notification for draft-alvestrand-dispatch-rtcweb-protocols-00
> Date:	Wed, 10 Nov 2010 03:31:05 -0800 (PST)
> From:	IETF I-D Submission Tool <idsubmission at ietf.org>
> To:	harald at alvestrand.no
> 
> A new version of I-D, draft-alvestrand-dispatch-rtcweb-protocols-00.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository.
> 
> Filename:	 draft-alvestrand-dispatch-rtcweb-protocols
> Revision:	 00
> Title:		 Overview: Real Time Protocols for Brower-based Applications
> Creation_date:	 2010-11-11
> WG ID:		 Independent Submission
> Number_of_pages: 9
> 
> Abstract:
> This document gives an overview 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 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.
>                                                                                   
> 
> 
> The IETF Secretariat.
> 
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch at ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.alvestrand.no/pipermail/rtc-web/attachments/20101217/77557ac2/attachment.html>