[ortc] ORTC shim: How to support 1.0 ICE restart without new DtlsTransport?

aboba has just created a new issue for https://github.com/w3c/ortc:

== ORTC shim:  How to support 1.0 ICE restart without new DtlsTransport? ==
At the WebRTC 1.0 September interim, there was consensus that a new DtlsTransport would not be vended after an ICE restart even if the endpoint changes (e.g. RTCRtpSender.transport remains valid but attributes change).  Does this lead to issues in shimming WebRTC 1.0 over ORTC?  If so, what ORTC functionality is needed?

Related WebRTC 1.0 Issue: https://github.com/w3c/webrtc-pc/issues/1406

WEBRTC WG September Interim slides: https://docs.google.com/presentation/d/1QjSKzQVINl5Cng0wH7oqvaDnkVNIc-JHUlduMZpfyFQ/edit#slide=id.g268f09a8f9_0_19

Please view or discuss this issue at https://github.com/w3c/ortc/issues/755 using your GitHub account

Received on Friday, 15 September 2017 19:36:43 UTC