Section 4.4.4 closed state

[fluffy]

Do we need to add "or all transports are in closed state" ?

[aboba]

Is there another way that RTCIceTransport objects reach the "closed" state, other than via a call to pc.close()?

[fluffy]

If all the m lines are lines are zero I had thought it would go to closed. I guess to put it a different way, is there a way the remote side can cause a PC to end?

[taylor-b]

That won't cause the PC to end ([[isClosed]] will still be false, you can still do a re-offer that recycles the rejected "m=" sections). But it would cause all transports to enter the "closed" state, in which case you'd get an RTCIceConnectionState of "new":

new: Any of the RTCIceTransport s are in the new state and none of them are in the checking, failed or disconnected state, or all RTCIceTransport s are in the closed state.

This was by design, since having a bunch of rejected "m=" sections is somewhat equivalent to having none at all, from an application's perspective. +@pthatcherg