13. Extensibility Considerations【可扩展性注意事项】

原文链接：https://datatracker.ietf.org/doc/html/rfc8445#section-13

13. Extensibility Considerations【可扩展性注意事项】

This specification makes very specific choices about how both ICE agents in a session coordinate to arrive at the set of candidate pairs that are selected for data.
该规范对会话中的两个 ICE 代理如何协调以到达为数据选择的候选对集合做出了非常具体的选择。

It is anticipated that future specifications will want to alter these algorithms, whether they are simple changes like timer tweaks or larger changes like a revamp of the priority algorithm.
预计未来的规范将希望更改这些算法，无论是简单的更改（如定时器调整）还是较大的更改（如改进优先级算法）。

When such a change is made, providing interoperability between the two agents in a session is critical.
进行此类更改时，提供会话中两个代理之间的互操作性至关重要。

First, ICE provides the ICE option concept. Each extension or change to ICE is associated with an ICE option.
首先，ICE 提供了 ICE 选项的概念。 ICE 的每个扩展或更改都与一个 ICE 选项相关联。

When an agent supports such an extension or change, it provides the ICE option to the peer agent as part of the candidate exchange.
当代理支持此类扩展或更改时，它会向对等代理提供 ICE 选项作为候选交换的一部分。

One of the complications in achieving interoperability is that ICE relies on a distributed algorithm running on both agents to converge on an agreed set of candidate pairs.
实现互操作性的复杂性之一是 ICE 依赖于在两个代理上运行的分布式算法来收敛于一组商定的候选对。

If the two agents run different algorithms, it can be difficult to guarantee convergence on the same candidate pairs.
如果两个代理运行不同的算法，则很难保证在相同的候选对上收敛。

The nomination procedure described in Section 8 eliminates some of the need for tight coordination by delegating the selection algorithm completely to the controlling agent, and ICE will converge perfectly even when both agents use different pair prioritization algorithms.
第 8 节中描述的提名程序通过将选择算法完全委托给控制代理消除了一些紧密协调的需要，即使两个代理使用不同的对优先级算法，ICE 也将完美收敛。

One of the keys to such convergence is triggered checks, which ensure that the nominated pair is validated by both agents.
这种收敛的关键之一是触发检查，它确保提名对由两个代理验证。

ICE is also extensible to other data streams beyond RTP and for transport protocols beyond UDP.
ICE 还可以扩展到 RTP 以外的其他数据流和 UDP 以外的传输协议。

Extensions to ICE for non-RTP data streams need to specify how many components they utilize and assign component IDs to them, starting at 1 for the most important component ID.
对非 RTP 数据流的 ICE 扩展需要指定它们使用的组件数量，并为它们分配组件 ID，从 1 开始，最重要的组件 ID。

Specifications for new transport protocols MUST define how, if at all, various steps in the ICE processing differ from UDP.
新传输协议的规范必须定义 ICE 处理中的各个步骤（如果有的话）与 UDP 的不同之处。