[RTW] List is now open

[Ian Hickson]

On Wed, 13 Oct 2010, Justin Uberti wrote:
> >
> > One thing that might make sense is for me to write a skeleton of what 
> > I imagine the "next layer" would look like (the spec layer that 
> > defines the format of the data that the browsers use to talk over the 
> > low-latency channel, defines how ICE/STUN/relays/etc are used, defines 
> > what the relays are, defines how to do video codec negotiation, 
> > defines how to identify which packets go with which PeerConnection, 
> > defines how to respond to specific API calls in terms of data on the 
> > wire, etc), and to then hand that off to someone who actually knows 
> > how that is all to be defined. Would that make sense?
> 
> Sure. As you mention, our previous discussions on the Session API are 
> probably a good start for this. I'd be happy to work with you on the 
> details.

Ok, here's a very early first draft at such a skeleton:

   http://hixie.ch/specs/rtc-skeleton/

The bits marked in asterisks *like this* are the bits that I would then 
use in the HTML spec to glue the two specs together. (I haven't yet 
updated the HTML spec to use these terms, but it won't take long.)

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'