W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2015

Re: [webrtc-pc] Impossible to know if ICE agent is "finished checking", for "failed" and "completed" states.

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 18 Dec 2015 12:15:30 +1100
Message-ID: <CABkgnnXEWPGg-VSW0mOR+Y2N0YknVzPK0FttZ3QTSZi=RuCtew@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 18 December 2015 at 07:57, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:
> However, because "a=end-of-candidates" is not per m-line, it operates only at the level of the "ICE Agent" rather than individually on each of the RTCIceTransport objects and their "state" attributes.

We've certainly implemented it as a per-media-section attribute.
There's no reason that the signal can't be more granular, just that
the signal we have in SDP loses a bit of information.  Firefox does
have a single agent that signals a single end to the gathering phase,
but the attribute is added to every affected media section.

> This means that it is not applicable to ORTC/WebRTC NV.

???  You don't have a notion of an ICE agent?  I thought that we'd
agreed that an ICE agent was a good idea.

In either case, I think that the right answer is to use the underlying
state: have you finished gathering, rather than use
a=end-of-candidates for that state.  If you want to report a failed
state, then you only do so if gathering is done (or stopped for now if
you prefer) and all the checks have failed for those pairs that you do
have.

I'm an anti-fan of the idea of a special candidate, favouring instead
a separate method, but I get the appeal.
Received on Friday, 18 December 2015 01:15:59 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:47 UTC