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 found in the offer/answer SDP.

I'm proposing to add the remote port to RTCSctpCapabilities as a remotePort port 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 an SCTP port is not really a 'capability'.

Edit: I've withdrawn my suggestion to rename the attributes as other transports that provide parameters do not prefix the attributes with local or remote either.

Cheers,
Lennart