"ICE Agent" and "ICE engine" versus "ICE Transport"

[aboba]

In a number of places, the ORTC API uses terms such as "ICE Agent" and "ICE engine" that make sense in WebRTC 1.0, but do not make sense in ORTC API, where there are ICE Transport objects that can be configured individually (and can have separate states).

Proposed resolution:

In Section 3.9 change:

"all
The ICE engine gathers all types of candidates when this value is specified.

nohost
The ICE engine gathers all ICE candidate types except for host candidates.

relay
The ICE engine must only gather media relay candidates such as candidates passing through a TURN server. This can be used to reduce leakage of IP addresses in certain use cases."

To:

"
all
The ICE transport gathers all types of candidates when this value is specified.

nohost
The ICE transport gathers all ICE candidate types except for host candidates.

relay
The ICE transport must only gather media relay candidates such as candidates passing through a TURN server. This can be used to reduce leakage of IP addresses in certain use cases."

In Section 3.10, change:

"
new
The ICE Agent is gathering addresses and/or waiting for remote candidates to be supplied.

checking
The ICE Agent has received remote candidates on at least one component, and is checking candidate pairs but has not yet found a connection. In addition to checking, it may also still be gathering.

connected
The ICE Agent has found a usable connection for all components but is still checking other candidate pairs to see if there is a better connection. It may also still be gathering.

completed
The ICE Agent has finished gathering and checking and found a connection for all components. Open issue: it is not clear how the non controlling ICE side knows it is in the state.

disconnected
Liveness checks have failed for one or more components. This may trigger intermittently (and resolve itself without action).

closed
The ICE Agent has shut down and is no longer responding to STUN requests."

To:

"
new
The ICE Transport is gathering addresses and/or waiting for remote candidates to be supplied.

checking
The ICE Transport has received at least one remote candidate, and is checking candidate pairs but has not yet found a connection. In addition to checking, it may also still be gathering.

connected
The ICE Transport has found a usable connection, but is still checking other candidate pairs to see if there is a better connection. It may also still be gathering.

completed
The ICE Transport has finished gathering and checking and found a connection. There is no such state for the ICE non-controlling peer.

disconnected
Liveness checks have failed. This may trigger intermittently (and resolve itself without action).

closed
The ICE Transport has shut down and is no longer responding to STUN requests."