Internet Engineering Task Force (IETF) M. Westerlund
Request for Comments: 6336 Ericsson
Updates: 5245 C. Perkins
Category: Standards Track University of Glasgow
ISSN: 2070-1721 July 2011
Internet Engineering Task Force (IETF) M. Westerlund
Request for Comments: 6336 Ericsson
Updates: 5245 C. Perkins
Category: Standards Track University of Glasgow
ISSN: 2070-1721 July 2011
IANA Registry for Interactive Connectivity Establishment (ICE) Options
交互式连接建立（ICE）选项IANA注册表
Abstract
摘要
It has been identified that "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols" (RFC 5245) is missing a registry for ICE options. This document defines this missing IANA registry and updates RFC 5245.
已经确定，“交互式连接建立（ICE）：提供/应答协议的网络地址转换器（NAT）遍历协议”（RFC 5245）缺少ICE选项的注册表。本文档定义了缺失的IANA注册表，并更新了RFC 5245。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6336.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6336.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
2. Requirements Language ...........................................2
3. IANA Considerations .............................................3
3.1. ICE Options ................................................3
4. Security Considerations .........................................3
5. Acknowledgements ................................................4
6. References ......................................................4
6.1. Normative References .......................................4
6.2. Informative References .....................................4
1. Introduction ....................................................2
2. Requirements Language ...........................................2
3. IANA Considerations .............................................3
3.1. ICE Options ................................................3
4. Security Considerations .........................................3
5. Acknowledgements ................................................4
6. References ......................................................4
6.1. Normative References .......................................4
6.2. Informative References .....................................4
"Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols" [RFC5245] defines a concept of ICE options. However, the ICE RFC fails to create an IANA registry for ICE options. As one ICE option is under specification in [ECN-FOR-RTP], there is now a need to create the registry.
“交互式连接建立（ICE）：提供/应答协议的网络地址转换器（NAT）遍历协议”[RFC5245]定义了ICE选项的概念。但是，ICE RFC无法为ICE选项创建IANA注册表。由于[ECN-FOR-RTP]中规定了一个ICE选项，因此现在需要创建注册表。
RFC 5245 says: "ICE provides for extensibility by allowing an offer or answer to contain a series of tokens that identify the ICE extensions used by that agent. If an agent supports an ICE extension, it MUST include the token defined for that extension in the ice-options attribute".
RFC 5245说：“ICE通过允许报价或应答包含一系列标识该代理使用的ICE扩展的令牌来提供扩展性。如果代理支持ICE扩展，则必须在ICE选项属性中包含为该扩展定义的令牌。”。
Thus, as future extensions are defined, these ICE options need to be registered with IANA to ensure non-conflicting identification. The ICE option identifiers are used in signalling between the ICE endpoints to negotiate extension support. RFC 5245 defines one method of signalling these ICE options, using the Session Description Protocol (SDP) with Offer/Answer [RFC3264].
因此，随着未来扩展的定义，这些ICE选项需要向IANA注册，以确保识别不冲突。ICE选项标识符用于ICE端点之间的信令，以协商扩展支持。RFC 5245定义了使用会话描述协议（SDP）和提供/应答[RFC3264]向这些ICE选项发送信号的一种方法。
This document updates the ICE specification [RFC5245] to define the "Interactive Connectivity Establishment (ICE) Options" registry.
本文件更新了ICE规范[RFC5245]，以定义“交互式连接建立（ICE）选项”注册表。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
This document defines a registry "Interactive Connectivity Establishment (ICE) Options" for ICE options that can be used in the SDP "ice-options" attribute or other signalling parameters carrying the ICE options.
本文件为ICE选项定义了一个注册表“交互式连接建立（ICE）选项”，该注册表可用于SDP“ICE选项”属性或承载ICE选项的其他信令参数。
An ICE option identifier MUST fulfill the ABNF [RFC5234] syntax for "ice-option-tag" as specified in [RFC5245]. This syntax is reproduced here for simplicity, but the authoritative definition is in the ICE RFC:
ICE选项标识符必须符合[RFC5245]中规定的“ICE选项标记”的ABNF[RFC5234]语法。为简单起见，此处复制了该语法，但ICE RFC中有权威定义：
ice-option-tag = 1*ice-char
ice-char = ALPHA / DIGIT / "+" / "/"
ice-option-tag = 1*ice-char
ice-char = ALPHA / DIGIT / "+" / "/"
ICE options are of unlimited length according to the syntax; however, they are RECOMMENDED to be no longer than 20 characters. This is to reduce message sizes and allow for efficient parsing.
ICE选项根据语法具有无限长度；但是，建议长度不超过20个字符。这是为了减少消息大小并允许高效解析。
Registration of an ICE option in the "Interactive Connectivity Establishment (ICE) Options" registry is done using the Specification Required policy as defined in "Guidelines for Writing an IANA Considerations Section in RFCs" [RFC5226].
在“交互式连接建立（ICE）选项”注册表中，ICE选项的注册是使用“RFCs中编写IANA注意事项部分的指南”[RFC5226]中定义的规范要求策略完成的。
A registration request MUST include the following information:
注册申请必须包括以下信息：
o The ICE option identifier to be registered
o 要注册的ICE选项标识符
o Name, Email, and Address of a contact person for the registration
o 注册联系人的姓名、电子邮件和地址
o Organization or individuals having the change control
o 具有变更控制权的组织或个人
o Short description of the ICE extension to which the option relates
o 与选项相关的ICE扩展的简短说明
o Reference(s) to the specification defining the ICE option and the related extensions
o 定义ICE选项和相关扩展的规范参考
This document registers no ICE option.
本文件未登记ICE选项。
As this document defines an IANA registry for an already existing concept, there are no new security considerations.
由于本文档为一个已经存在的概念定义了IANA注册表，因此没有新的安全注意事项。
The authors would like to thank the people who reviewed the document and provided feedback: Flemming Andreasen, Mykyta Yevstifeyev, Amanda Baber, and Brian Carpenter.
作者要感谢审阅该文件并提供反馈的人员：弗莱明·安德里亚森、Mykyta Yevstifeyev、阿曼达·巴伯和布赖恩·卡彭特。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols", RFC 5245, April 2010.
[RFC5245]Rosenberg，J.，“交互式连接建立（ICE）：提供/应答协议的网络地址转换器（NAT）遍历协议”，RFC 52452010年4月。
[ECN-FOR-RTP] Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P., and K. Carlberg, "Explicit Congestion Notification (ECN) for RTP over UDP", Work in Progress, July 2011.
[ECN-FOR-RTP]Westerlund，M.，Johansson，I.，Perkins，C.，O'Hanlon，P.，和K.Carlberg，“UDP上RTP的显式拥塞通知（ECN）”，正在进行的工作，2011年7月。
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, June 2002.
[RFC3264]Rosenberg，J.和H.Schulzrinne，“具有会话描述协议（SDP）的提供/应答模型”，RFC 3264，2002年6月。
Authors' Addresses
作者地址
Magnus Westerlund Ericsson Farogatan 6 SE-164 80 Kista Sweden
Magnus Westerlund Ericsson Farogatan 6 SE-164 80瑞典基斯塔
Phone: +46 10 714 82 87
EMail: magnus.westerlund@ericsson.com
Phone: +46 10 714 82 87
EMail: magnus.westerlund@ericsson.com
Colin Perkins University of Glasgow School of Computing Science Glasgow G12 8QQ United Kingdom
柯林帕金斯格拉斯哥大学计算科学学院格拉斯哥G128QQ英国
EMail: csp@csperkins.org
EMail: csp@csperkins.org