- From: Cullen Jennings (fluffy) <fluffy@cisco.com>
- Date: Mon, 3 Sep 2012 15:02:44 +0000
- To: Eric Rescorla <ekr@rtfm.com>
- CC: Justin Uberti <juberti@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Aug 20, 2012, at 10:39 AM, Eric Rescorla <ekr@rtfm.com> wrote: >> I also think the m= index strategy has several shortcomings, so using "mid" >> when available allows us to avoid chaining ourselves to m= index. > > In that case, I propose that the spec at minimum require that only either > mid or index be present. That way there's no room for disagreement > about the semantics. > > Thoughts? Hmm, given that browser does not know when creating a candidate if the candidate is being used by Jingle, SIP or something else, that seems a bit problematic. Perhaps we should say when a candidate is generated by the browser, it will have both mid and index. When the browser consumes a candidate, if both are present and they do not indicate the same thing, then an error is reported since clearly something is borked in this case. The browser needs to be able to receive candidates that only have only mid or only index.
Received on Monday, 3 September 2012 15:03:15 UTC