You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am learning the ice logic about ice-lite and found an interesting case TestConnectivityLite in agent_test.go
There are 2 agents, aAgent works as full ice agent and bAgent works as lite ice agent, in TestConnectivityLite case. They connect each other in function connectWithVNet
In connectWithVNet, the 2 agent start to check the connectivity after they exchange their candidates, like below code. But why, bAgent start to Dial instead of aAgent calling Accept? The bAgent is a lite agent, maybe it should be listener according RFC 5245.
# RFC 5245 https://www.rfc-editor.org/rfc/rfc5245#page-30
One agent full, one lite: The full agent MUST take the controlling
role, and the lite agent MUST take the controlled role. The full
agent will form check lists, run the ICE state machines, and
generate connectivity checks. That agent will execute the logic
in Section 8.1 to nominate pairs that will be selected by ICE, and
use the logic in Section 8.1.2 to end ICE. The lite
implementation will just listen for connectivity checks, receive
them and respond to them, and then conclude ICE as described in
Section 8.2. For the lite implementation, the state of ICE
processing for each media stream is considered to be Running, and
the state of ICE overall is Running.
I am learning the ice logic about ice-lite and found an interesting case
TestConnectivityLite
inagent_test.go
There are 2 agents, aAgent works as full ice agent and bAgent works as lite ice agent, in
TestConnectivityLite
case. They connect each other in functionconnectWithVNet
In
connectWithVNet
, the 2 agent start to check the connectivity after they exchange their candidates, like below code. But why, bAgent start toDial
instead ofaAgent
callingAccept
? The bAgent is a lite agent, maybe it should be listener according RFC 5245.The text was updated successfully, but these errors were encountered: