- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Dec 2016 21:03:28 +0000
- To: public-ortc@w3.org
lgrahl has just created a new issue for https://github.com/w3c/ortc: == RTCSctpTransport lacks remote port == If I haven't overlooked something, there's no way to determine the SCTP port of the remote peer. For WebRTC, the remote port can be located in the [offer/answer SDP](https://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-19#section-5). I'm proposing to add the remote port to `RTCSctpCapabilities` as an `remotePort` attribute. `port` in the constructor should also be renamed to `localPort` to avoid confusion. Furthermore, we should discuss whether `RTCSctpCapabilities` could be renamed to `RTCSctpParameters` because the remote port is not really a 'capability'. Cheers, Lennart Please view or discuss this issue at https://github.com/w3c/ortc/issues/625 using your GitHub account
Received on Friday, 16 December 2016 21:04:04 UTC