Proposed RTCRtpSender / Receiver / DTLS and Ice objects draft update

After feedback from the community, I've decided to incorporate Peter's 
RTCRtpSender / Receiver and dtls / ice object split concepts / proposals.

I've incorporated the ideas proposed thus far:

http://htmlpreview.github.io/?https://raw2.github.com/robin-raymond/ortc/1c2065af84d21882203f6f735f06d181312cc6ec/ortc.html


As compared to the previous version:
http://htmlpreview.github.io/?https://raw2.github.com/openpeer/ortc/1458338dbfe13dcabb2f0d9d5ddb73e490e23a5a/ortc.html


These changes have some impact and require some fixes as a result:
1) RTCSocket - this object is still required to allow for forking 
situations, but perhaps should be renamed to something more appropriate 
and also likely something that can be passed into the RTCIceTransport 
instead. We still need Ice server options which are currently missing 
from the proposal too.

2) RTCStream - not sure having a stream object makes much sense anymore 
if we treat each MediaStreamTrack as an independent thing constructed 
from and RTCRtpSender / RTCRtpReceiver object, and it's also no longer 
obtainable from the RTCIceTransport (formerly known as RTCConnection)

3) RTCDTMFTrack - this object doesn't make much sense anymore and I 
think we should entertain proposals on how to rework this idea into a 
new model (left in document to be reworked)

4) RTCDataChannel - this object now requires some reworking because it 
doesn't wire the same way give the Dtls/Ice object split.

5) Dtls fingerprinting needs to be incorporated into the dtls object

I'll have more feed back to provide in subsequent emails to follow...

Regards,
Robin

Received on Thursday, 23 January 2014 04:48:23 UTC