Add RTCSctpTransportState #1620
Conversation
aboba
changed the title
| transport.</p> | ||
| <div> | ||
| <pre class="idl">enum RTCSctpTransportState { | ||
| "new", |
There was a problem hiding this comment.
I'm not sure we need "new", since we decided the RTCSctpTransport is only created on applying an answer, in which case it already has enough information to connect? Though maybe we should revisit that decision.
There was a problem hiding this comment.
There might be an advantage to having the RTCSctpTransport created earlier, in which case the "new" state might be used. But I agree that if it is only created on applying an Answer it should be initialized to "connecting".
There was a problem hiding this comment.
Opening another issue relating to the transition text.
webrtc.html
Outdated
| "idlAttrType"><a>RTCSctpTransportState</a></span>, readonly</dt> | ||
| <dd> | ||
| <p>The current state of the SCTP transport. The attribute returns | ||
| the value of the <dfn>[[\SctpTransportState]]</dfn> internal slot.</p> |
There was a problem hiding this comment.
Similar to my comment on the PR that added [[DtlsTransportState]]: we need to either describe when the slot's value is changed, or not use a slot.
In this case it's probably pretty simple:
- When it's first created, the value is
connecting? (See below comment) - When the four-way startup handshake finishes, queue a task to update the state to
connected - When a SHUTDOWN or ABORT chunk is received, queue a task to update the state to
closed - Also can go to
closedfrom applying a description that rejects the data m= section, or changes the sctp-port. Or if the application closes the PeerConnection,
Fix for Issue #1612
Preview | Diff