No IceGatherer.stop()

[aboba]

There is no way to stop an IceGatherer once constructed. Let us say that an Offerer offers both Audio and Video, on distinct ports, and constructs and IceGatherer and IceTransport for them. Then the Answer comes back indicating that the Answerer doesn't want video (port = 0). Wouldn't you want to call .stop() on the IceGatherer and IceTransport? Otherwise you'll have the IceGatherer expending energy gathering Server Reflexive and relay candidates that you'll never use.

[aboba]

Potential fix:

partial interface RTCIceGatherer : RTCStatsProvider {
void stop ();
};

stop
Stops and closes the current object.

No parameters.
Return type: void

[pthatcherg]

I like it, but let's call it;

partial interface RTCIceGatherer : RTCStatsProvider {
void close(); // Blows away all local candidates. IceTransports using them will go to disconnected state.
};

[aboba]

If we have an iceGatherer.close() method, we also need a "closed" state for the IceGatherer.

[aboba]

Here is a proposal:

partial interface RTCIceGatherer : RTCStatsProvider {
void close ();
};

close
Prunes all local candidates. Associated RTCIceTransport objects transition to the "disconnected" state.

Here is the proposed definition of the "closed" state:

The RTCIceGatherer has been closed intentionally or as the result of an error.