The thing that goes into a PeerConnection doesn't have to be the same thing
that goes into an IceTransport.
Plus, if you leave it a separate object, you can add a ufrag on there to
avoid the "which generation of gathering is complete?" problem.
On Wed, Mar 16, 2016 at 11:05 AM, Bernard Aboba <Bernard.Aboba@microsoft.com
> wrote:
> Currently there is a PR in WebRTC 1.0 to allow the null candidate to be
> provided as an argument to addIceCandidate():
>
> https://github.com/w3c/webrtc-pc/pull/527
>
>
>
> Once this PR is merged, the mechanism for signaling “end-of-candidates”
> will be different in WebRTC 1.0 and ORTC.
>
>
>
> This seems awkward.
>
>
>
> Should we go back to defining RTCIceCandidateComplete as a null candidate?
>
>
>
>
>