No more candidates arriving from remote party

[aboba]

In WebRTC 1.0 API Section 4.4.3, the "Completed" state contains the following statement:

"Open issue: it is not clear how the non controlling ICE side knows it is in the state."

There is a similar problem in ORTC, which is that it is not clear how to tell the RTCIceTransport that no more candidates will arrive from the remote party.

[robin-raymond]

Just to be clear, we can tell all candidates have been gathered locally by way of the gathering state (and thus can signal it remotely).

However, when we receive a remote signal that no more candidates will arrive from the remote party we can't tell the ORTC RTCIceTransport that no more candidates are to arrive and thus you are free to go into the completed state and clean up and resources.

[ibc]

And that is why I strongly suggest the removal of the "completed" state, as it adds zero value to the "connected" one (in fact, it is the same box in the diagram).

[robin-raymond]

@ibc we will post this to the list too, just capturing as an issue. There is "some" value to the completed state because some implementation can know it's safe to shutdown non used candidates (like turn) when completed.

[robin-raymond]

In SDP for 1.0, it's signalled with a=end-of-candidates so that's how 1.0 works (although I don't know any implementation that actually does it).