Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Sections 2.2 and 2.3: RTCDtlsTransport #38
A RTCDtlsTransport instance is optionally constructed from an RTCIceTransport object or an RTCIceTransport is automatically constructed.
[BA] Should this be "or an RTCDtlsTransport is automatically constructed"?
2.3 Interface Definition
[Constructor(optional RTCIceTransport transport)]
Assuming we have a DTLS transport constructed without an ice transport object as an argument, what happens when an app calls start() on the DTLS transport? Is an RTCIceTransport object really an optional argument to the constructor?
I do think it's an optional argument. Start will have to do nothing until it's attached later to an ICE transport. It's kind of in an "awaiting attachment" state. Once attached, it should continue to perform it's operations. If reattached to another ICE transport it should continue its internal state exactly where it left off. If it becomes detached it should freeze its state "as is" and await attachment again to any ICE transport.