在RFC 8445中更新了ICE协议。ICE lite早于RFC。RFC 8445中的ICE Lite的详细信息在附录A中提供。然而,早在2007年,就有人试图正式确定ICE Lite是什么。这是在这份RFC草案中。它是相当描述性的,但一些陈述与RFC 8445中的陈述相冲突。例如,RFC 8445确实允许两个对等体都是ICE LITE,而文档草案建议不这样做。
有人能指出RFC on ICE LITE草案中的例外或更正,使其与RFC 8445兼容吗?或者指向比RFC 8445中的描述更详细地描述ICE LITE的文档?
我没有使用libnice,但由于ICE上没有相关的标签,所以我使用了libnice,希望libnice的用户能得到一些信息。
发布于 2020-03-09 03:47:05
pion/ice有一个针对ICE Lite的选项。我通过试验和错误做了一些事情,但以下是我在此过程中学到的东西。
来自RFC 8445 6.1.1. Determining Role
Both lite: The initiating agent that started the ICE processing MUST
take the controlling role, and the other MUST take the controlled
role. In this case, no connectivity checks are ever sent.
Rather, once the candidates are exchanged, each agent performs the
processing described in Section 8 without connectivity checks. It
is possible that both agents will believe they are controlled or
controlling. In the latter case, the conflict is resolved through
glare detection capabilities in the signaling protocol enabling
the candidate exchange. The state of ICE processing for each data
stream is considered to be Running, and the state of ICE overall
is Running.我还没有找到一个广泛的学习ICE Lite的地方。但是您可以看看pion/ice是如何运行的,并乐于回答更多的个人问题!
https://stackoverflow.com/questions/60586942
复制相似问题