RTCIceCandidate: Support for "generation"

[aboba]

Issue raised by Philipp Hancke:
https://lists.w3.org/Archives/Public/public-ortc/2015Jun/0010.html

"> 17) page 12, section 3.11 (RTCIceCandidate)

WebIDL
how does this deal with the extensibility defined in RFC 5245 --
https://tools.ietf.org/html/rfc5245#section-15.1 (extension-att-name etc)

[BA] It is possible to add variables to the dictionary. so it is possible to add new attributes for extension-att-name/extension-att-value. Do you think there is something missing in particular that needs to be added?

[Philipp] the generation attribute from
http://xmpp.org/extensions/xep-0176.html#protocol-syntax is pretty common."

[BA] Indeed. An example of generation support (from Chrome):
"candidate:3735874944 1 udp 2122197247 typ host generation 0"

[robin-raymond]

generation does not apply to ORTC since the candidates come from the gatherer which never changes its usernameFragment / password. The restart mechanism happens in the IceTransport which can take a substitute gatherer. So the tracking of the generation has to happen at a high level.

[rshpount]

Furthermore, I am not aware of generation being defined in any IETF RFC
document. It is present in XMPP but I am not sure where it is defined for
SDP.

---

Roman Shpount

On Fri, Jun 5, 2015 at 5:09 PM, Robin Raymond notifications@github.com
wrote:

generation does not apply to ORTC since the candidates come from the
gatherer which never changes its usernameFragment / password. The restart
mechanism happens in the IceTransport which can take a substitute gatherer.
So the tracking of the generation has to happen at a high level.

—
Reply to this email directly or view it on GitHub
#212 (comment).