- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 May 2020 06:43:35 +0000
- To: public-webrtc-logs@w3.org
> This is going to bite people. Ordering is a pretty natural guarantee actually. See https://tools.ietf.org/html/rfc6120#section-10.1 if you want a more formal description. It is a fundamental assumption in protocol design. For example it ensures that the join confirmation for a chatroom arrives before you get any messages. E.g. you get ``` C: join X S: you joined X S: here is an offer from the room jingle focus ``` I've only once seen a signaling protocol which didn't have this property. Signaling protocols aren't simple and there is a point where one should strongly consider whether reinventing the wheel makes sense. I'm biased of course and still prefer jingle over sending SDP on the wire :-) Suppose you get candidates with a ufrag X. Then you get a remote description with ufrag Y. Do you reject the remote description or silently discard the generation with ufrag X? -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-622272086 using your GitHub account
Received on Friday, 1 May 2020 06:43:39 UTC