Network Working Group O. Levin
Request for Comments: 3762 Microsoft Corporation
Category: Standards Track April 2004
Network Working Group O. Levin
Request for Comments: 3762 Microsoft Corporation
Category: Standards Track April 2004
Telephone Number Mapping (ENUM) Service Registration for H.323
H.323的电话号码映射（ENUM）服务注册
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
Abstract
摘要
The H.323 specification defines a means for building multimedia communication services over an arbitrary Packet Based Network, including the Internet. This document registers a Telephone Number Mapping (ENUM) service for H.323 according to specifications and guidelines in RFC 3761.
323规范定义了在包括因特网在内的任意基于分组的网络上构建多媒体通信服务的方法。本文档根据RFC 3761中的规范和指南为H.323注册电话号码映射（ENUM）服务。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. ENUM Service Registration . . . . . . . . . . . . . . . . . . . 2
3. The E2U+H323 ENUM Service . . . . . . . . . . . . . . . . . . . 2
4. Conventions Used in this Document . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
7. References. . . . . . . . . . . . . . . . . . . . . . . . . . . 3
7.1. Normative References. . . . . . . . . . . . . . . . . . . 3
7.2. Informative References. . . . . . . . . . . . . . . . . . 3
8. Author's Address. . . . . . . . . . . . . . . . . . . . . . . . 4
9. Full Copyright Statement. . . . . . . . . . . . . . . . . . . . 5
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. ENUM Service Registration . . . . . . . . . . . . . . . . . . . 2
3. The E2U+H323 ENUM Service . . . . . . . . . . . . . . . . . . . 2
4. Conventions Used in this Document . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
7. References. . . . . . . . . . . . . . . . . . . . . . . . . . . 3
7.1. Normative References. . . . . . . . . . . . . . . . . . . 3
7.2. Informative References. . . . . . . . . . . . . . . . . . 3
8. Author's Address. . . . . . . . . . . . . . . . . . . . . . . . 4
9. Full Copyright Statement. . . . . . . . . . . . . . . . . . . . 5
The H.323 specification [2] defines a means for building multimedia communication services over an arbitrary Packet Based Network, including the Internet. When H.323 is used in the context of the Internet, it would be useful to take advantages of such services as domain name system (DNS) and ENUM in order to help facilitate the completion of multimedia calls.
H.323规范[2]定义了一种在包括因特网在内的任意基于分组的网络上构建多媒体通信服务的方法。当H.323在因特网的上下文中使用时，利用诸如域名系统（DNS）和ENUM之类的服务来帮助完成多媒体呼叫将是有用的。
This document registers an ENUM service for H.323 according to specifications and guidelines in RFC 3761 [3].
本文档根据RFC 3761[3]中的规范和指南为H.323注册了ENUM服务。
As defined in [3], the following is a template covering information needed for the registration of the enumservice specified in this document.
如[3]中所定义，以下模板涵盖了注册本文档中指定的enumservice所需的信息。
- Service Name: "E2U+H323" - URI Scheme(s): "h323:" - Functional Specification: see section "3. The E2U+H323 ENUM Service" - Security considerations: see section "5. Security Considerations" - Intended usage: COMMON - Author: Orit Levin - Any other information that the author deems interesting: None
- 服务名称：“E2U+H323”-URI方案：“H323:”-功能规范：请参阅“3.E2U+H323枚举服务”一节-安全注意事项：请参阅“5.安全注意事项”一节-预期用途：通用-作者：Orit Levin-作者认为感兴趣的任何其他信息：无
This document defines the "E2U+H323" service to be used in the "service" sub-field of the "enumservice" as defined in [3].
本文件定义了[3]中定义的“enumservice”的“service”子字段中使用的“E2U+H323”服务。
The H.323 related ENUM record MUST be populated with a standard H.323 URL as defined in [2]. This URL MAY include parameters specifying the specific protocols and the transport means the H.323 entity supports.
必须使用[2]中定义的标准H.323 URL填充与H.323相关的枚举记录。该URL可包括指定H.323实体支持的特定协议和传输方式的参数。
The H.323 entity MUST fully comply with the procedures defined in [3] for both record retrieval and processing by the DNS client.
H.323实体必须完全遵守[3]中定义的程序，以便DNS客户端检索和处理记录。
If, as a result of the ENUM DNS lookup, an H.323 URL matching local policies and capabilities is retrieved, the procedure defined in section O.8.1 "Locating H.323 Destination" of [5] SHOULD be performed.
如果作为枚举DNS查找的结果，检索到与本地策略和功能匹配的H.323 URL，则应执行[5]第O.8.1节“定位H.323目的地”中定义的过程。
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 BCP 14, RFC 2119 [1].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[1]中的描述进行解释。
The h323-URL information, once populated in the DNS, effectively becomes publicly accessible. The access to the H.323 destinations (published using ENUM) can be secured by techniques and procedures defined in H.235 [4] - the security framework for H.323. The framework defines means for achieving integrity, authentication, non-repudiation, encryption, etc. for H.323 calls. An analysis of threats specific to the dependence of ENUM on the DNS, and the applicability of DNSSEC [6] to these, is provided in [3].
h323 URL信息一旦在DNS中填充，就可以有效地公开访问。对H.323目的地（使用ENUM发布）的访问可以通过H.235[4]-H.323安全框架中定义的技术和程序进行安全保护。该框架定义了实现H.323呼叫的完整性、身份验证、不可否认性、加密等的方法。[3]中提供了对ENUM依赖DNS的特定威胁的分析，以及DNSSEC[6]对这些威胁的适用性。
This document registers the E2U+H323 ENUM service according to specifications and guidelines in RFC 3761 [3] and the definitions in this document.
本文档根据RFC 3761[3]中的规范和指南以及本文档中的定义注册E2U+H323枚举服务。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] "Packet-based multimedia communications systems", ITU-T Recommendation H.323, 2003.
[2] “基于分组的多媒体通信系统”，ITU-T建议H.323，2003年。
[3] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[3] Faltstrom，P.和M.Mealling，“E.164到统一资源标识符（URI）动态委托发现系统（DDDS）应用程序（ENUM）”，RFC 3761，2004年4月。
[4] "Security and encryption for H-Series(H.323 and other H.245- based) multimedia terminals", ITU-T Recommendation H.235, 2003.
[4] “H系列（H.323和其他基于H.245的）多媒体终端的安全和加密”，ITU-T建议H.235，2003年。
[5] "Usage of URLs and DNS", ITU-T Recommendation H.323 Annex O, 2003.
[5] “URL和DNS的使用”，ITU-T建议H.323附录O，2003年。
[6] R. Arends, et al., "Protocol Modifications for the DNS Security Extensions", Work in Progress, February 2004.
[6] R.Arends等人，“DNS安全扩展的协议修改”，正在进行的工作，2004年2月。
Orit Levin Microsoft Corporation One Microsoft Way Redmond, WA 98052 USA
奥利特·莱文微软公司美国华盛顿州雷德蒙微软大道一号，邮编：98052
EMail: oritl@microsoft.com
EMail: oritl@microsoft.com
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。