Subject: Re: [rtcweb] ROAP Example Application
From: Matthew Kaufman <[email-masked]>
To: Cullen Jennings <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Date: Fri, 21 Oct 2011 19:37:13 +0200 (CEST)
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>

Thought experiment:

If one had a connection object that supported an underlying protocol that could send one or more encrypted flows of both real-time media and reliable data, what information would you need to exchange between the two browser endpoints in order to ensure that any pair of browsers with any future audio or video codec could use the best mutually-supported codecs?

(And note that if you had this, you could even send that information over the peer-to-peer data channel itself, once established.. Or you could send it up to a server... Your choice as programmer.)

Now, what does it take to swap out the protocol underneath that connection object with ICE, DTLS-SRTP and TCP-over-UDP (or equivalent) for the data?

If we can successfully do this, we will have achieved a much cleaner software architecture within the browser, separated the connection setup from the media setup, enabled the substitution of alternative transports, etc.

Matthew Kaufman

Sent from my iPad, on a plane