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

@fippo 

The implementation I would like is caching candidates by the `ufrag`

* If no `ufrag` is specified with the candidate throw an error
* If a `ufrag` is specified cache the candidate
* When a `SRD` happens with the matching `ufrag` use the cached candidates

----

I don't understand this point

```
If you think that your signaling protocol doesn't require order, how do you deal with a subsequent offer with 5 m-lines being processed ahead of the original one with 2 m-lines? That may work but applying the two m-line offer will fail since it looks (from an API PoV) like you are removing m-lines which is a no-no.
```

This is covered by `Session Version` in `o` value (I believe)?


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


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

Received on Wednesday, 3 May 2023 20:09:10 UTC