Re: [webrtc-pc] addIceCandidate may not need to throw an error when no remoteDescription (#2519)

> @Sean-Der Signaling is out of scope of the WebRTC API. So an application could signal using RFC 1149.

RFC 1149 is a network layer protocol.  You'd use a transport layer protocol between RFC 1149 and signalling, and I think what Sean meant is that he'd like to simplify the implementation of signalling over X over RFC 1149 in the specific case where X preserves message ordering.

@fippo is claiming that the simplification suggested by Sean will not solve all issues in the case where X does not preserve ordering.  He's probably right (I frankly don't know), but I don't feel that's a valid argument against simplifying the implementer's job in the specific case where X is ordered.

-- 
GitHub Notification of comment by jech
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-1532239926 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 2 May 2023 22:34:26 UTC