The "underlying data transport" is more than just an SCTP stream pair, though; it's a stream pair _plus_ the extra semantics defined by draft-ietf-rtcweb-data-channel. Is there any reason why we can't just refer to SCTP terminology directly though? Why do we need this hand-wavey terminology in the first place? Is it in case we end up using the RTCDataChannel interface with some other underlying protocol (which seems unlikely)? Can we just cross that bridge when we come to it? -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1699#issuecomment-358820628 using your GitHub accountReceived on Thursday, 18 January 2018 23:49:56 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC