- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Tue, 1 Jul 2014 21:13:53 +0000
- To: "public-ortc@w3.org" <public-ortc@w3.org>
>From Robin Raymond:
https://tools.ietf.org/html/rfc5245#section-9.1.1.1
http://tools.ietf.org/html/draft-petithuguenin-mmusic-ice-sip-sdp-01#section-9.1.1
Important info about restarts...
o An agent is changing its implementation level. This typically
only happens in third party call control use cases, where the
entity performing the signaling is not the entity receiving the
media, and it has changed the target of media mid-session to
another entity that has a different ICE implementation.
ICE restarts aren't just changing ufrag/password for ICE. Nor it is just flushing the candidate checks. Because it's redirecting to a new target, this implies that a restart needs to perform a full DTLS exchange to the new target after establishing connectivity.
This you can't just have a "restart" method on the Ice listener. You actually need to have brand new IceListeners, IceTransports and DTLS transport objects. Seems to me the simpler thing is to do nothing and let those who need to perform this kind of restart stop existing objects, create brand new objects, and insert the object into the list at the right spot for the ice transport controller.
Received on Tuesday, 1 July 2014 21:14:23 UTC