Internet Engineering Task Force (IETF) E. Guy
Request for Comments: 6315 CleverSpoke
Category: Informational K. Darilion
ISSN: 2070-1721 nic.at
July 2011
Internet Engineering Task Force (IETF) E. Guy
Request for Comments: 6315 CleverSpoke
Category: Informational K. Darilion
ISSN: 2070-1721 nic.at
July 2011
IANA Registration for Enumservice 'iax'
枚举服务“iax”的IANA注册
Abstract
摘要
This document registers an Enumservice for the Inter-Asterisk eXchange (IAX) protocol according to the guidelines given in RFC 6117.
本文档根据RFC 6117中给出的指南为星号间交换（IAX）协议注册Enumservice。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非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/rfc6315.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6315.
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许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction ....................................................2
2. IANA Registration ...............................................3
3. Examples ........................................................4
3.1. Simple IAX URI .............................................4
3.2. IAX URI with a Context .....................................4
4. Security Considerations .........................................4
5. IANA Considerations .............................................5
6. DNS Considerations ..............................................5
7. Acknowledgments .................................................5
8. References ......................................................5
8.1. Normative References .......................................5
8.2. Informative References .....................................6
1. Introduction ....................................................2
2. IANA Registration ...............................................3
3. Examples ........................................................4
3.1. Simple IAX URI .............................................4
3.2. IAX URI with a Context .....................................4
4. Security Considerations .........................................4
5. IANA Considerations .............................................5
6. DNS Considerations ..............................................5
7. Acknowledgments .................................................5
8. References ......................................................5
8.1. Normative References .......................................5
8.2. Informative References .....................................6
The E.164 to Uniform Resource Identifiers (URIs) [RFC3986] Dynamic Delegation Discovery System (DDDS) Application (ENUM) [RFC6116] transforms E.164 [E164] numbers into URIs using the Domain Name System (DNS) [RFC1035].
E.164到统一资源标识符（URI）[RFC3986]动态委派发现系统（DDDS）应用程序（ENUM）[RFC6116]使用域名系统（DNS）[RFC1035]将E.164[E164]号转换为URI。
IAX (Inter-Asterisk eXchange) [RFC5456] is an "all-in-one" protocol for handling multimedia in IP networks. It combines both control and media services in the same protocol.
IAX（Inter Asterisk eXchange）[RFC5456]是一种“一体式”协议，用于在IP网络中处理多媒体。它在同一协议中结合了控制和媒体服务。
This document registers an Enumservice for the IAX [RFC5456] protocol according to the guidelines given in [RFC6117].
本文档根据[RFC6117]中给出的指南为IAX[RFC5456]协议注册Enumservice。
<record>
<!-- iax -->
<class>Protocol-Based</class>
<type>iax</type>
<!-- No subtype -->
<urischeme>iax</urischeme>
<functionalspec>
<paragraph>
The 'iax' Enumservice is used to map E.164 numbers to
IAX URIs. Such URIs identify resources capable of being
contacted to provide a communication session using the
IAX protocol <xref target="RFC5456"/>.
</paragraph>
<paragraph>
A client selecting this NAPTR needs to be able to support
communication utilizing the IAX protocol.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="6315"/>, Section 4.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="6315"/>
</registrationdocs>
<requesters>
<xref type="person" data="Ed_Guy"/>
<xref type="person" data="Klaus_Darilion"/>
</requesters>
</record>
<record>
<!-- iax -->
<class>Protocol-Based</class>
<type>iax</type>
<!-- No subtype -->
<urischeme>iax</urischeme>
<functionalspec>
<paragraph>
The 'iax' Enumservice is used to map E.164 numbers to
IAX URIs. Such URIs identify resources capable of being
contacted to provide a communication session using the
IAX protocol <xref target="RFC5456"/>.
</paragraph>
<paragraph>
A client selecting this NAPTR needs to be able to support
communication utilizing the IAX protocol.
</paragraph>
</functionalspec>
<security>
See <xref type="rfc" data="6315"/>, Section 4.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="6315"/>
</registrationdocs>
<requesters>
<xref type="person" data="Ed_Guy"/>
<xref type="person" data="Klaus_Darilion"/>
</requesters>
</record>
<people>
<person id="Ed_Guy">
<name>Ed Guy</name>
<org>CleverSpoke, Inc</org>
<uri>mailto:edguy@CleverSpoke.com</uri>
<updated>2010-11-01</updated>
</person>
<person id="Klaus_Darilion">
<name>Klaus Darilion</name>
<org>nic.at</org>
<uri>mailto:klaus.darilion@nic.at</uri>
<updated>2011-03-24</updated>
</person>
</people>
<people>
<person id="Ed_Guy">
<name>Ed Guy</name>
<org>CleverSpoke, Inc</org>
<uri>mailto:edguy@CleverSpoke.com</uri>
<updated>2010-11-01</updated>
</person>
<person id="Klaus_Darilion">
<name>Klaus Darilion</name>
<org>nic.at</org>
<uri>mailto:klaus.darilion@nic.at</uri>
<updated>2011-03-24</updated>
</person>
</people>
The following examples are just for illustrative purposes and will in no way limit the usage of the 'iax' Enumservice to other usage scenarios.
以下示例仅用于说明目的，不会将“iax”Enumservice的使用限制在其他使用场景中。
The following Naming Authority Pointer (NAPTR) resource record is an example of the 'iax' Enumservice.
以下命名机构指针（NAPTR）资源记录是“iax”枚举服务的一个示例。
$ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa.
$ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa。
@ IN NAPTR ( 10 100 "u" "E2U+iax"
"!^.*$!iax:example.com/alice!" . )
@ IN NAPTR ( 10 100 "u" "E2U+iax"
"!^.*$!iax:example.com/alice!" . )
This contact information indicates that the party addressed by the E.164 number +442079460148 can be contacted using the IAX protocol to domain 'example.com'. The called party, service, or program on that domain is identified by 'alice'.
此联系信息表明，可以使用IAX协议联系E.164号码+442079460148所述的一方到域“example.com”。该域上的被叫方、服务或程序由“alice”标识。
The following is an example of the 'iax' Enumservice using an IPv6 destination address and a destination 'context'.
以下是使用IPv6目标地址和目标“上下文”的“iax”枚举服务的示例。
$ORIGIN 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa.
$ORIGIN 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa。
@ IN NAPTR ( 10 100 "u" "E2U+iax"
"!^.*$!iax:[2001:db8::1]:4569/alice?friends!" . )
@ IN NAPTR ( 10 100 "u" "E2U+iax"
"!^.*$!iax:[2001:db8::1]:4569/alice?friends!" . )
This NAPTR resource record indicates that +442079460149 may be contacted by using the IAX protocol at IPv6 address 2001:db8::1, port 4569 with the called party 'alice' in the context (or user partition) 'friends'. For further usage of IAX URIs, see Section 5 of [RFC5456].
此NAPTR资源记录表明，可以使用IAX协议在IPv6地址2001:db8:：1，端口4569与上下文（或用户分区）“朋友”中的被叫方“alice”联系+44207946149。有关IAX URI的进一步使用，请参见[RFC5456]的第5节。
The 'iax' Enumservice does not introduce any new security issues beyond any already present in the ENUM, DNS, and IAX protocols, except that this Enumservice provides for disclosure of information that may facilitate an attack or a violation of user privacy in some way. The primary result of these exploits is unwanted communications. These issues are discussed in further detail in [RFC3833].
“iax”Enumservice不会引入任何新的安全问题，除了ENUM、DNS和iax协议中已经存在的任何安全问题外，该Enumservice提供的信息披露可能以某种方式助长攻击或侵犯用户隐私。这些攻击的主要结果是不必要的通信。[RFC3833]进一步详细讨论了这些问题。
The use of DNS Security (DNSSEC) [RFC4033] is recommended to improve operational security.
建议使用DNS安全性（DNSSEC）[RFC4033]来提高操作安全性。
For security considerations that apply to all Enumservices, please refer to RFC 6116, Section 7.
有关适用于所有Enumservices的安全注意事项，请参阅RFC 6116第7节。
This document registers the 'iax' Enumservice according to the guidelines and specifications in [RFC6117] and the definitions in Section 2 in this document.
本文件根据[RFC6117]中的指南和规范以及本文件第2节中的定义注册“iax”Enumservice。
Misconfiguration or delays in zone changes can result in call loops, perhaps with different protocols or networks. Implementations should take care to ensure such loops can be detected without interrupting other services, including SIP-based, IAX-based, and DNS itself.
区域更改中的错误配置或延迟可能导致呼叫循环，可能使用不同的协议或网络。实现应注意确保可以在不中断其他服务（包括基于SIP、基于IAX和DNS本身）的情况下检测到此类循环。
This work was supported by Internet Foundation Austria. In addition, thanks to Michael Haberler, Bernie Hoeneisen, and Richard Stastny for their support and guidance in writing this document.
这项工作得到了奥地利互联网基金会的支持。此外，感谢Michael Haberler、Bernie Hoenesen和Richard Stastny在编写本文件时给予的支持和指导。
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC5456] Spencer, M., Capouch, B., Guy, E., Ed., Miller, F., and K. Shumard, "IAX: Inter-Asterisk eXchange Version 2", RFC 5456, February 2010.
[RFC5456]Spencer，M.，Capouch，B.，Guy，E.，Ed.，Miller，F.，和K.Shumard，“IAX:星号间交换版本2”，RFC 54562010年2月。
[RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 6116, March 2011.
[RFC6116]Bradner，S.，Conroy，L.，和K.Fujiwara，“E.164到统一资源标识符（URI）动态委托发现系统（DDDS）应用程序（ENUM）”，RFC 6116，2011年3月。
[RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA Registration of Enumservices: Guide, Template, and IANA Considerations", RFC 6117, March 2011.
[RFC6117]Hoenesen，B.，Mayrhofer，A.，和J.Livingood，“Enumservices的IANA注册：指南，模板和IANA注意事项”，RFC 61172011年3月。
[E164] ITU-T, "The International Public Telecommunication Numbering Plan", Recommendation E.164, May 1997.
[E164]ITU-T，“国际公共电信编号计划”，建议E.164，1997年5月。
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain Name System (DNS)", RFC 3833, August 2004.
[RFC3833]Atkins，D.和R.Austein，“域名系统（DNS）的威胁分析”，RFC 38332004年8月。
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "DNS Security Introduction and Requirements", RFC 4033, March 2005.
[RFC4033]Arends，R.，Austein，R.，Larson，M.，Massey，D.，和S.Rose，“DNS安全介绍和要求”，RFC 4033，2005年3月。
Authors' Addresses
作者地址
Ed Guy CleverSpoke 12 Williams Road Chatham, NJ 07928 US
美国新泽西州查塔姆威廉姆斯路12号Ed Guy CleverSpoke 07928
Phone: +1 973 437 4519
EMail: edguy@CleverSpoke.com
URI: http://www.cleverspoke.com/
Phone: +1 973 437 4519
EMail: edguy@CleverSpoke.com
URI: http://www.cleverspoke.com/
Klaus Darilion nic.at Karlsplatz 1/2/9 1010 Wien Austria
克劳斯·达里翁出生于奥地利卡尔斯普拉茨1/2/9 1010
Phone: +43 1 5056416 36
EMail: klaus.darilion@nic.at
URI: http://www.nic.at/
Phone: +43 1 5056416 36
EMail: klaus.darilion@nic.at
URI: http://www.nic.at/