Network Working Group J. Livingood
Request for Comments: 5278 Comcast Cable Communications
Category: Standards Track D. Troshynski
Acme Packet
July 2008
Network Working Group J. Livingood
Request for Comments: 5278 Comcast Cable Communications
Category: Standards Track D. Troshynski
Acme Packet
July 2008
IANA Registration of Enumservices for Voice and Video Messaging
IANA语音和视频消息服务注册
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）。本备忘录的分发不受限制。
Abstract
摘要
This document registers the Enumservice named "vmsg", which is used to facilitate the real-time routing of voice, video, and unified communications to a messaging system. This vmsg Enumservice registers three Enumservice types: "voicemsg", "videomsg", and "unifmsg". Each type also registers the subtypes "sip", "sips", "http", and "https", as well as the subtype "tel" for the "voicemsg" type.
本文档注册了名为“vmsg”的Enumservice，该服务用于促进语音、视频和统一通信到消息传递系统的实时路由。此vmsg Enumservice注册三种Enumservice类型：“voicemsg”、“videomsg”和“unifmsg”。每种类型还注册子类型“sip”、“sips”、“http”和“https”，以及“voicemsg”类型的子类型“tel”。
Table of Contents
目录
1. Introduction ....................................................3
1.1. Selected Use Cases for Illustrative Purposes ...............4
1.2. Consideration of Other Existing Enumservices ...............5
2. Distribution of Data ............................................5
3. Security Considerations .........................................5
4. ENUM Service Registration for voicemsg ..........................6
4.1. Registration for "voicemsg" with Subtype "sip" .............6
4.2. Registration for "voicemsg" with Subtype "sips" ............7
4.3. Registration for "voicemsg" with Subtype "tel" .............7
4.4. Registration for "voicemsg" with Subtype "http" ............8
4.5. Registration for "voicemsg" with Subtype "https" ...........9
5. ENUM Service Registration for videomsg .........................10
5.1. Registration for "videomsg" with Subtype "sip" ............10
5.2. Registration for "videomsg" with Subtype "sips" ...........10
5.3. Registration for "videomsg" with Subtype "http" ...........11
5.4. Registration for "videomsg" with Subtype "https" ..........12
6. ENUM Service Registration for unifmsg ..........................13
6.1. Registration for "unifmsg" with Subtype "sip" .............13
6.2. Registration for "unifmsg" with Subtype "sips" ............13
6.3. Registration for "unifmsg" with Subtype "http" ............14
6.4. Registration for "unifmsg" with Subtype "https" ...........15
7. Selected Examples for Illustrative Purposes ....................16
7.1. Example Using a 'sip' URI .................................16
7.2. Example Using a 'tel' URI .................................16
7.3. Example Using a Backreference .............................16
7.4. Example Using a 'sip' URI without a Telephone Number ......17
7.5. Example of Failover Using E2U+videomsg:sip ................17
8. Implementation Recommendations .................................17
8.1. Call Processing When Multiple Records Are Returned ........17
8.2. NAPTR Configuration Issues ................................18
9. IANA Considerations ............................................18
10. Acknowledgements ..............................................18
11. Contributors ..................................................19
12. References ....................................................19
12.1. Normative References .....................................19
12.2. Informative References ...................................20
1. Introduction ....................................................3
1.1. Selected Use Cases for Illustrative Purposes ...............4
1.2. Consideration of Other Existing Enumservices ...............5
2. Distribution of Data ............................................5
3. Security Considerations .........................................5
4. ENUM Service Registration for voicemsg ..........................6
4.1. Registration for "voicemsg" with Subtype "sip" .............6
4.2. Registration for "voicemsg" with Subtype "sips" ............7
4.3. Registration for "voicemsg" with Subtype "tel" .............7
4.4. Registration for "voicemsg" with Subtype "http" ............8
4.5. Registration for "voicemsg" with Subtype "https" ...........9
5. ENUM Service Registration for videomsg .........................10
5.1. Registration for "videomsg" with Subtype "sip" ............10
5.2. Registration for "videomsg" with Subtype "sips" ...........10
5.3. Registration for "videomsg" with Subtype "http" ...........11
5.4. Registration for "videomsg" with Subtype "https" ..........12
6. ENUM Service Registration for unifmsg ..........................13
6.1. Registration for "unifmsg" with Subtype "sip" .............13
6.2. Registration for "unifmsg" with Subtype "sips" ............13
6.3. Registration for "unifmsg" with Subtype "http" ............14
6.4. Registration for "unifmsg" with Subtype "https" ...........15
7. Selected Examples for Illustrative Purposes ....................16
7.1. Example Using a 'sip' URI .................................16
7.2. Example Using a 'tel' URI .................................16
7.3. Example Using a Backreference .............................16
7.4. Example Using a 'sip' URI without a Telephone Number ......17
7.5. Example of Failover Using E2U+videomsg:sip ................17
8. Implementation Recommendations .................................17
8.1. Call Processing When Multiple Records Are Returned ........17
8.2. NAPTR Configuration Issues ................................18
9. IANA Considerations ............................................18
10. Acknowledgements ..............................................18
11. Contributors ..................................................19
12. References ....................................................19
12.1. Normative References .....................................19
12.2. Informative References ...................................20
ENUM (E.164 Number Mapping, RFC 3761 [1]) is a technology that transforms E.164 numbers (the International Public Telecommunication Numbering Plan, ITU-T Recommendation E.164 [2]) into domain names and then uses DNS (Domain Name System, RFC 1034 [3]) delegation through NS records and Naming Authority Pointer (NAPTR) records (Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database, RFC 3403 [4]) to look up what services are available for a specific domain name.
ENUM（E.164数字映射，RFC 3761[1]）是一种将E.164数字（国际公共电信编号计划，ITU-T建议E.164[2]）转换为域名，然后通过NS记录和命名机构指针（NAPTR）记录使用DNS（域名系统，RFC 1034[3]）委托的技术（动态委托发现系统（DDDS）第三部分：域名系统（DNS）数据库，RFC 3403[4]），以查找特定域名的可用服务。
This document registers Enumservices according to the guidelines given in RFC 3761 [1] to be used for provisioning in the services field of a NAPTR [4] resource record to indicate the types of functionality associated with an end point and/or telephone number. The registration is defined within the DDDS (Dynamic Delegation Discovery System [4][5][6][7][8]) hierarchy, for use with the "E2U" DDDS Application defined in RFC 3761.
本文件根据RFC 3761[1]中给出的指南注册Enumservices，用于在NAPTR[4]资源记录的services字段中进行配置，以指示与端点和/或电话号码相关的功能类型。注册在DDDS（动态委派发现系统[4][5][6][7][8]）层次结构中定义，用于RFC 3761中定义的“E2U”DDDS应用程序。
Voice messaging systems are used widely with telephony and voice communication services. The need for a voice messaging service type has become clear in order to provide certain applications with direct access to various voice messaging services (for example, voicemail), most typically via the use of SIP.
语音信息系统广泛用于电话和语音通信服务。为了向某些应用程序提供对各种语音消息服务（例如，语音邮件）的直接访问（最典型的是通过使用SIP），对语音消息服务类型的需求已经变得很清楚。
The authors considered the use of Voice Profile for Internet Mail (VPIM) [14] but found that VPIM was best suited to the non-real-time and non-session-based routing of a voice message once it had been deposited into a voice messaging system. Thus, VPIM was a good solution for the non-real-time and non-session-based routing of voice messages between and within domains, but it did not enable real-time interaction with a voice messaging system.
作者考虑了互联网邮件语音配置文件（VPIM）[14]的使用，但发现VPIM最适合语音消息存入语音消息系统后的非实时和非基于会话的路由。因此，VPIM对于域之间和域内的语音消息的非实时和非基于会话的路由是一个很好的解决方案，但它不能实现与语音消息系统的实时交互。
Thus, a need has been identified for this voice messaging service type that would enable, for example, some of the use cases listed in this section.
因此，已经确定了这种语音消息服务类型的需求，例如，它将启用本节中列出的一些用例。
Video messaging systems, sometimes called visual voice messaging systems, are beginning to be used with real-time communication services. The need for a video messaging service type has become clear in order to provide certain applications with direct access to various video messaging services, most typically via the use of SIP. Thus, a need has been identified for this video messaging service type that would enable, for example, some of the use cases listed in this section.
视频信息系统，有时称为可视语音信息系统，开始与实时通信服务一起使用。为了向某些应用程序提供对各种视频消息服务的直接访问（最典型的是通过使用SIP），对视频消息服务类型的需求已经变得很清楚。因此，已经确定了这种视频消息服务类型的需求，例如，它将启用本节中列出的一些用例。
Finally, several service providers and software developers have indicated that their system for voice messaging and video messaging either have been or soon will be unified into a single system. As such, they desired to have the option of using an Enumservice type that represents a subscriber's mailbox as being a so-called unified messaging repository. Thus, a need has been identified for this unified voice and video messaging service type that would enable, for example, some of the use cases listed in this section.
最后，一些服务提供商和软件开发商表示，他们的语音消息和视频消息系统已经或即将统一为一个单一系统。因此，他们希望能够选择使用Enumservice类型，将订户的邮箱表示为所谓的统一消息存储库。因此，已经确定了这种统一语音和视频消息服务类型的需求，例如，它将支持本节中列出的一些用例。
The following is a partial, non-exclusive list of use cases that the vmsg Enumservice could address:
以下是vmsg Enumservice可以解决的部分非独占性用例列表：
* A called party is busy or does not answer a call. A client or server then determines that a messaging service should be used and sends the calling party's session to such a service. The client or server needs to be able to determine which server to direct this real-time session to, whether that is within or outside of the called party's domain.
* 被叫方忙或不接听电话。然后，客户机或服务器确定应使用消息传递服务，并将呼叫方的会话发送到此类服务。客户端或服务器需要能够确定将此实时会话定向到哪个服务器，无论该服务器位于被叫方的域之内还是之外。
* Similar to the above use case, a real-time session is attempted to a messaging system, but that system is currently unavailable. Since multiple service type records may be returned by the original ENUM query, the client or server could then attempt to initiate a session with one or more backup messaging servers in a manner that is transparent to the calling party and that supports better overall availability of a messaging service.
* 与上述用例类似，尝试与消息传递系统进行实时会话，但该系统当前不可用。由于原始ENUM查询可能返回多个服务类型记录，因此客户端或服务器可以尝试以对呼叫方透明且支持消息传递服务更好的总体可用性的方式启动与一个或多个备份消息传递服务器的会话。
* Similar to the above use case, this service type could be used to balance load across multiple messaging servers, whether those are in the same or in different physical locations.
* 与上述用例类似，此服务类型可用于跨多个消息传递服务器平衡负载，无论这些服务器位于相同或不同的物理位置。
* A user with an account on a messaging service needs to connect to the messaging service in order to retrieve messages. They initiate a real-time session, and an ENUM query is performed to discover the messaging server that holds its mailbox.
* 拥有消息服务帐户的用户需要连接到消息服务才能检索消息。它们启动实时会话，并执行枚举查询以发现保存其邮箱的消息服务器。
* In the process of invoking and supporting a real-time, automated and interactive session with a user, whether for message deposit or retrieval, VoiceXML files are referenced and utilized, via either HTTP or HTTPS. Multiple VoiceXML servers could be associated with a user and returned via ENUM query, for the purposes of load balancing, for example.
* 在调用和支持与用户的实时、自动和交互式会话的过程中，无论是用于消息存放还是检索，都会通过HTTP或HTTPS引用和使用VoiceXML文件。例如，出于负载平衡的目的，多个VoiceXML服务器可以与一个用户关联并通过枚举查询返回。
The authors considered whether this service type could simply use the SIP Enumservice type [19], but found that it does not satisfy their voice messaging requirements, particularly given the non-SIP URI sub-types specified herein. Even with sub-types for SIP URIs, however, there are challenges to using the SIP Enumservice type. For example, a request for access to such a service could be extended to the requesting SIP client, or User Agent Client (UAC), rather than relying upon the local policy of a SIP server, or User Agent Server (UAS), which means that special routing logic within a UAS cannot be relied upon to solve this problem. More importantly, however, the authors have found that without this service type, a UAC or UAS will be presented with multiple SIP URIs, with no ability other than in non-standards-based routing rules or application logic to recognize which one is related to a voice messaging, video messaging, or unified voice and video messaging service.
作者考虑了该服务类型是否可以简单地使用SIP Enumservice类型[19]，但发现它不能满足他们的语音消息传递要求，特别是考虑到本文指定的非SIP URI子类型。然而，即使使用SIPURI的子类型，使用SIP枚举服务类型也存在挑战。例如，访问此类服务的请求可以扩展到请求SIP客户端或用户代理客户端（UAC），而不是依赖SIP服务器或用户代理服务器（UAS）的本地策略，这意味着不能依赖UAS内的特殊路由逻辑来解决此问题。然而，更重要的是，作者发现，如果没有这种服务类型，UAC或UAS将呈现多个SIP URI，除了在基于非标准的路由规则或应用程序逻辑中，没有能力识别哪一个与语音消息、视频消息或统一语音和视频消息服务相关。
The authors believe that it is more likely that these records will be distributed on a purely private basis, but they may also be distributed in public ENUM trees. Distribution of this NAPTR data could be either (a) on a private basis within a service provider's internal network, (b) on a private basis between one or more parties using a variety of security mechanisms to prohibit general public access, or (c) openly available.
作者认为，这些记录更可能是在纯粹私人的基础上分发的，但它们也可能在公共枚举树中分发。该NAPTR数据的分发可以是（a）在服务提供商的内部网络内以私有方式进行，（b）在一方或多方之间以私有方式进行，使用各种安全机制禁止一般公众访问，或（c）公开提供。
DNS, as used by ENUM, is a global, distributed database. Should implementers of this specification use e164.arpa or any other publicly available domain as the tree for maintaining voicemsg Enumservice data, this information would be visible to anyone anonymously. While this is not qualitatively different from publication in a Telephone Directory, it does open or ease access to such data without any indication that such data has been accessed or by whom it has been accessed.
ENUM使用的DNS是一个全局分布式数据库。如果本规范的实施者使用e164.arpa或任何其他公开可用的域作为维护voicemsg Enumservice数据的树，则任何人都可以匿名看到此信息。虽然这与在电话簿中发布没有本质上的区别，但它确实可以打开或方便地访问这些数据，而没有任何迹象表明这些数据已经被访问或被谁访问过。
Such data harvesting by third parties is often used to generate lists of targets for unsolicited information. Thus, a third party could use this to generate a list that it can use to make unsolicited telemarketing phone calls, or so-called SPAM over Internet Telephony (SPIT). Many countries have do-not-call registries or other legal or regulatory mechanisms in place to deal with such abuses.
第三方收集的此类数据通常用于生成未经请求的信息的目标列表。因此，第三方可以使用它生成一个列表，它可以使用该列表进行未经请求的电话营销电话，或所谓的互联网电话垃圾邮件（SPIT）。许多国家没有设立登记处或其他法律或监管机制来处理此类侵权行为。
As noted earlier, carriers, service providers, and other users may simply choose not to publish such information in the public e164.arpa tree, but may instead simply publish this in their internal ENUM routing database that is only able to be queried by trusted elements of their network and/or partner networks, such as softswitches and SIP proxy servers. They may also choose to publish such information in a carrier-only branch of the e164.arpa tree, should one be created.
如前所述，运营商、服务提供商和其他用户可以简单地选择不在公共e164.arpa树中发布此类信息，而可以简单地在其内部ENUM路由数据库中发布此信息，该数据库只能由其网络和/或合作伙伴网络的可信元素查询，例如软交换和SIP代理服务器。他们也可以选择在e164.arpa树的纯运营商分支中发布此类信息（如果已创建）。
Although an E.164 telephone number does not appear to reveal as much identity information about a user as a name in the format sip:username@hostname or email:username@hostname, the information is still publicly available; thus, there is still the risk of unwanted communication.
尽管E.164电话号码显示的用户身份信息似乎不如sip格式的姓名显示的那么多：username@hostname或电邮：username@hostname，该资料仍然公开；因此，仍然存在不必要通信的风险。
An analysis of threats specific to the dependence of ENUM on the DNS and the applicability of DNSSEC [16] to this is provided in RFC 3761 [1]. A thorough analysis of threats to the DNS itself is covered in RFC 3833 [17].
RFC 3761[1]中提供了对ENUM依赖DNS的特定威胁以及DNSSEC[16]对此的适用性的分析。RFC 3833[17]对DNS本身的威胁进行了全面分析。
Enumservice Name: "voicemsg"
Enumservice名称：“voicemsg”
Enumservice Type: "voicemsg"
枚举服务类型：“voicemsg”
Enumservice Subtypes: "sip"
枚举服务子类型：“sip”
URI Schemes: 'sip:'
URI方案：“sip:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a voice communication session to a voice messaging system.
此Enumservice表示标识的远程资源可以通过相关联的URI方案寻址，以便发起到语音消息传递系统的语音通信会话。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "voicemsg"
Enumservice名称：“voicemsg”
Enumservice Type: "voicemsg"
枚举服务类型：“voicemsg”
Enumservice Subtypes: "sips"
枚举服务子类型：“sips”
URI Schemes: 'sips:'
URI方案：“sips:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a voice communication session to a voice messaging system.
此Enumservice表示标识的远程资源可以通过相关联的URI方案寻址，以便发起到语音消息传递系统的语音通信会话。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "voicemsg"
Enumservice名称：“voicemsg”
Enumservice Type: "voicemsg"
枚举服务类型：“voicemsg”
Enumservice Subtype: "tel"
枚举服务子类型：“电话”
URI Schemes: 'tel:'
URI方案：“电话：”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a voice communication session to a voice messaging system.
此Enumservice表示标识的远程资源可以通过相关联的URI方案寻址，以便发起到语音消息传递系统的语音通信会话。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "voicemsg"
Enumservice名称：“voicemsg”
Enumservice Type: "voicemsg"
枚举服务类型：“voicemsg”
Enumservice Subtype: "http"
枚举服务子类型：“http”
URI Schemes: 'http:'
URI方案：“http:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information.
此Enumservice表示由关联URI方案标识的远程资源能够成为信息源。
Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'http:' [11] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even voice message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource.
请注意，检索到的信息可能是多种多样的。通常，通过“http:”[11]URI联系资源会提供一个文档。此文档可以包含引用，这些引用将触发许多不同类型信息的下载，例如文本、音频、视频、可执行代码，甚至语音消息文件。因此，在联系资源时，不能更具体地说明所期望的信息类型。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "voicemsg"
Enumservice名称：“voicemsg”
Enumservice Type: "voicemsg"
枚举服务类型：“voicemsg”
Enumservice Subtype: "https"
枚举服务子类型：“https”
URI Schemes: 'https:'
URI方案：“https:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information, which can be contacted using TLS or the Secure Socket Layer protocol.
此Enumservice表示由关联URI方案标识的远程资源能够作为信息源，可以使用TLS或安全套接字层协议联系这些信息源。
Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'https:' [12] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even voice message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource.
请注意，检索到的信息可能是多种多样的。通常，通过“https:”[12]URI联系资源会提供一个文档。此文档可以包含引用，这些引用将触发许多不同类型信息的下载，例如文本、音频、视频、可执行代码，甚至语音消息文件。因此，在联系资源时，不能更具体地说明所期望的信息类型。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "videomsg"
Enumservice名称：“videomsg”
Enumservice Type: "videomsg"
枚举服务类型：“videomsg”
Enumservice Subtypes: "sip"
枚举服务子类型：“sip”
URI Schemes: 'sip:'
URI方案：“sip:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a video communication session to a video messaging system.
该Enumservice指示所标识的远程资源可以由相关联的URI方案寻址，以便发起到视频消息传递系统的视频通信会话。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "videomsg"
Enumservice名称：“videomsg”
Enumservice Type: "videomsg"
枚举服务类型：“videomsg”
Enumservice Subtypes: "sips"
枚举服务子类型：“sips”
URI Schemes: 'sips:'
URI方案：“sips:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a video communication session to a video messaging system.
该Enumservice指示所标识的远程资源可以由相关联的URI方案寻址，以便发起到视频消息传递系统的视频通信会话。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "videomsg"
Enumservice名称：“videomsg”
Enumservice Type: "videomsg"
枚举服务类型：“videomsg”
Enumservice Subtype: "http"
枚举服务子类型：“http”
URI Schemes: 'http:'
URI方案：“http:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information.
此Enumservice表示由关联URI方案标识的远程资源能够成为信息源。
Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'http:' [11] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource.
请注意，检索到的信息可能是多种多样的。通常，通过“http:”[11]URI联系资源会提供一个文档。此文档可以包含引用，这些引用将触发许多不同类型信息的下载，例如文本、音频、视频、可执行代码，甚至视频消息文件。因此，在联系资源时，不能更具体地说明所期望的信息类型。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "videomsg"
Enumservice名称：“videomsg”
Enumservice Type: "videomsg"
枚举服务类型：“videomsg”
Enumservice Subtype: "https"
枚举服务子类型：“https”
URI Schemes: 'https:'
URI方案：“https:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information, which can be contacted using TLS or the Secure Socket Layer protocol.
此Enumservice表示由关联URI方案标识的远程资源能够作为信息源，可以使用TLS或安全套接字层协议联系这些信息源。
Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'https:' [12] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource.
请注意，检索到的信息可能是多种多样的。通常，通过“https:”[12]URI联系资源会提供一个文档。此文档可以包含引用，这些引用将触发许多不同类型信息的下载，例如文本、音频、视频、可执行代码，甚至视频消息文件。因此，在联系资源时，不能更具体地说明所期望的信息类型。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "unifmsg"
Enumservice名称：“unifmsg”
Enumservice Type: "unifmsg"
枚举服务类型：“unifmsg”
Enumservice Subtypes: "sip"
枚举服务子类型：“sip”
URI Schemes: 'sip:'
URI方案：“sip:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a unified communication session to a unified messaging system.
此Enumservice表示标识的远程资源可以由关联的URI方案寻址，以便发起到统一消息系统的统一通信会话。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "unifmsg"
Enumservice名称：“unifmsg”
Enumservice Type: "unifmsg"
枚举服务类型：“unifmsg”
Enumservice Subtypes: "sips"
枚举服务子类型：“sips”
URI Schemes: 'sips:'
URI方案：“sips:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified can be addressed by the associated URI scheme in order to initiate a unified communication session to a unified messaging system.
此Enumservice表示标识的远程资源可以由关联的URI方案寻址，以便发起到统一消息系统的统一通信会话。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "unifmsg"
Enumservice名称：“unifmsg”
Enumservice Type: "unifmsg"
枚举服务类型：“unifmsg”
Enumservice Subtype: "http"
枚举服务子类型：“http”
URI Schemes: 'http:'
URI方案：“http:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information.
此Enumservice表示由关联URI方案标识的远程资源能够成为信息源。
Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'http:' [11] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource.
请注意，检索到的信息可能是多种多样的。通常，通过“http:”[11]URI联系资源会提供一个文档。此文档可以包含引用，这些引用将触发许多不同类型信息的下载，例如文本、音频、视频、可执行代码，甚至视频消息文件。因此，在联系资源时，不能更具体地说明所期望的信息类型。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
Enumservice Name: "unifmsg"
Enumservice名称：“unifmsg”
Enumservice Type: "unifmsg"
枚举服务类型：“unifmsg”
Enumservice Subtype: "https"
枚举服务子类型：“https”
URI Schemes: 'https:'
URI方案：“https:”
Functional Specification:
功能规格：
This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of information, which can be contacted using TLS or the Secure Socket Layer protocol.
此Enumservice表示由关联URI方案标识的远程资源能够作为信息源，可以使用TLS或安全套接字层协议联系这些信息源。
Note that the kind of information retrieved can be manifold. Usually, contacting a resource by an 'https:' [12] URI provides a document. This document can contain references that will trigger the download of many different kinds of information, such as text, audio, video, executable code, or even video message files. Thus, one cannot be more specific about the kind of information expected when contacting the resource.
请注意，检索到的信息可能是多种多样的。通常，通过“https:”[12]URI联系资源会提供一个文档。此文档可以包含引用，这些引用将触发许多不同类型信息的下载，例如文本、音频、视频、可执行代码，甚至视频消息文件。因此，在联系资源时，不能更具体地说明所期望的信息类型。
Security Considerations: See Section 3.
安全注意事项：见第3节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Don Troshynski (dtroshynski@acmepacket.com)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)唐特罗辛斯基(dtroshynski@acmepacket.com)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
Implementers should review a non-exclusive list of examples below in Section 7.
实施者应在第7节中查看下面的非排他性示例列表。
The following sub-sections document several examples that implementers may find informative. These examples shall in no way limit the various forms that this Enumservice may take.
以下小节记录了实施者可能会发现的一些示例。这些示例不得以任何方式限制本服务可能采取的各种形式。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+voicemsg:sip" "!^.*$!sip:12155550123@gw.example.com!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+voicemsg:sip”“！^.*$！sip:12155550123@gw.example.com!".
In this example, a calling party has attempted a session that has gone unanswered after a certain period of time. The calling party's session is sent to the appropriate voice messaging server, a personalized greeting is played to the calling party, after which it records a voice message to the called party.
在本例中，呼叫方尝试了一个会话，但该会话在一段时间后没有应答。主叫方的会话被发送到相应的语音消息服务器，向主叫方播放个性化问候语，然后向被叫方录制语音消息。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+voicemsg:tel" "!^.*$!tel:1-215-555-0123!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+voicemsg:tel”“！^.*$！电话：1-215-555-0123！”。
In this example, a calling party has attempted a session that has gone unanswered after a certain period of time. The calling party's session is sent to the appropriate voice messaging server, a personalized greeting is played to the calling party, after which it records a voice message to the called party.
在本例中，呼叫方尝试了一个会话，但该会话在一段时间后没有应答。主叫方的会话被发送到相应的语音消息服务器，向主叫方播放个性化问候语，然后向被叫方录制语音消息。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+voicemsg:sip" "!(^.*)$!sip:\1@example.net!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+voicemsg:sip”“！（^.*）$！sip:\1@example.net!".
In this example, a backreference is used to reduce the size of the NAPTR record. The sip URI uses "\1", which would dynamically replace the expression with the TN, in this case +12155550123.
在本例中，使用反向引用来减小NAPTR记录的大小。SIPURI使用“\1”，它将动态地用TN替换表达式，在本例中为+12155550123。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+voicemsg:sip" "!^.*$!sip:johndoe@gw.example.com!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+voicemsg:sip”“！^.*$！sip:johndoe@gw.example.com!".
In this example, a calling party has attempted a session that has gone unanswered after a certain period of time. The calling party's session is sent to the appropriate voice messaging server, a personalized greeting is played to the calling party, after which it records a voice message to the called party. The URI that this session is directed to does not include a telephone number, as this user has multiple service that are not particularly tied to telephone numbers whereby text, audio, video and other multimedia messages can be received and accessed.
在本例中，呼叫方尝试了一个会话，但该会话在一段时间后没有应答。主叫方的会话被发送到相应的语音消息服务器，向主叫方播放个性化问候语，然后向被叫方录制语音消息。该会话指向的URI不包括电话号码，因为该用户具有多个服务，这些服务不特别与电话号码相关，因此可以接收和访问文本、音频、视频和其他多媒体消息。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+videomsg:sip" "!^.*$!sip:12155550123@gw1.example.com!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+videomsg:sip”“！^.*$！sip:12155550123@gw1.example.com!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 200 "u" "E2U+videomsg:sip" "!^.*$!sip:12155550123@gw2.example.com!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 200“u”E2U+videomsg:sip”“！^.*$！sip:12155550123@gw2.example.com!".
In this example, the preference indicates that gw1.example.com is used first (100), and if this is unreachable, then the next higher preference (200) is used and gw2.example.com is contacted. While out of scope for this document, a service provider could thus mirror or cluster a message store and fail from the primary to secondary using the DNS in an active-standby mode.
在此示例中，首选项表示首先使用gw1.example.com（100），如果无法访问，则使用下一个更高的首选项（200），并联系gw2.example.com。当超出本文档的范围时，服务提供商可能因此镜像或群集消息存储，并在主备用模式下使用DNS从主到辅发生故障。
It is likely that both E2U+sip and E2U+voicemsg, E2U+videomsg, and/or E2U+unifmsg Enumservice type records will be returned for a given query. In this case, this could result in what is essentially E2U+sip records for real-time communications with an end user, while, for example, the E2U+voicemsg records will be used for real-time communications with a voice messaging service, when the called party is not available or does not wish to be disturbed. Therefore, the network element that receives the results of this ENUM query will need to know enough information in order to select the voicemsg service type, rather than the sip service type.
对于给定查询，可能会同时返回E2U+sip和E2U+voicemsg、E2U+videomsg和/或E2U+unifmsg Enumservice类型记录。在这种情况下，这可能导致基本上是E2U+sip记录用于与最终用户的实时通信，而例如，当被叫方不可用或不希望受到干扰时，E2U+voicemsg记录将用于与语音消息服务的实时通信。因此，接收此枚举查询结果的网元需要知道足够的信息，以便选择voicemsg服务类型，而不是sip服务类型。
In addition, it is likely that multiple E2U+voicemsg, E2U+videomsg, and/or E2U+unifmsg Enumservice type records will be returned for a given query. In this case, multiple records may include order and preference to allow recursion or load balancing. Order could be used to designate a primary and a backup voice, video, or unified voice and video messaging service. Preference could be used to load balance across multiple voice, video, and/or unified voice and video messaging servers by weight, for example.
此外，对于给定查询，可能会返回多个E2U+voicemsg、E2U+videomsg和/或E2U+unifmsg Enumservice类型记录。在这种情况下，多个记录可能包括顺序和首选项，以允许递归或负载平衡。订单可用于指定主要和备份语音、视频或统一语音和视频消息服务。例如，首选项可用于按重量跨多个语音、视频和/或统一语音和视频消息服务器进行负载平衡。
Finally, as with multiple records resulting from a typical ENUM query of the e164.arpa tree, it is up to the application using an ENUM resolver to determine which record(s) to use and which record(s) to ignore. Implementers should take this into consideration and build logic into their applications that can select appropriately from multiple records based on business, network, or other rules.
最后，与e164.arpa树的典型枚举查询产生的多条记录一样，使用枚举解析器的应用程序可以确定要使用哪些记录以及要忽略哪些记录。实现者应该考虑到这一点，并将逻辑构建到他们的应用程序中，这些应用程序可以根据业务、网络或其他规则从多个记录中进行适当选择。
Implementers may wish to consider using regular expressions in order to reduce the size of individual NAPTRs. This will have a significant effect on the overall size of the database involved.
实现者可能希望考虑使用正则表达式以减少单个NAPTR的大小。这将对所涉及数据库的总体大小产生重大影响。
This document registers the 'voicemsg' Enumservice type and the subtype "tel", "sip", "sips", "http", and "https" under the Enumservice registry described in the IANA considerations in RFC 3761. Details of this registration are provided in Section 4 of this document.
本文档在RFC 3761中IANA注意事项中描述的Enumservice注册表下注册'voicemsg'Enumservice类型和子类型“tel”、“sip”、“sips”、“http”和“https”。本文件第4节提供了该注册的详细信息。
This document registers the 'videomsg' Enumservice type and the subtype "sip", "sips", "http", and "https" under the Enumservice registry described in the IANA considerations in RFC 3761. Details of this registration are provided in Section 5 of this document.
本文档在RFC 3761中IANA注意事项中描述的Enumservice注册表下注册“videomsg”Enumservice类型和子类型“sip”、“sips”、“http”和“https”。本文件第5节提供了该注册的详细信息。
This document registers the 'unifmsg' Enumservice type and the subtype "sip", "sips", "http", and "https" under the Enumservice registry described in the IANA considerations in RFC 3761. Details of this registration are provided in Section 6 of this document.
本文档在RFC 3761中IANA注意事项中所述的Enumservice注册表下注册“unifmsg”Enumservice类型和子类型“sip”、“sips”、“http”和“https”。本文件第6节提供了该注册的详细信息。
The authors thank Rich Ferrise, Chris Harvey, Tong Zhou, and Hadriel Kaplan for their detailed assistance in developing the ideas behind this document in numerous brainstorming sessions, with information gleaned from their work to solve real application architecture issues. The authors also thank Lawrence Conroy and Jean-Francois Mule for their feedback in developing this document.
作者感谢Rich Ferrise、Chris Harvey、Tong Zhou和Hadriel Kaplan在众多头脑风暴会议中详细帮助开发本文档背后的想法，并从他们的工作中收集信息以解决实际的应用程序架构问题。作者还感谢Lawrence Conroy和Jean-Francois Mule在编写本文档时提供的反馈。
Tong Zhou Comcast Cable Communications Email: tong_zhou@cable.comcast.com
通州康卡斯特有线通信电子邮件：通_zhou@cable.comcast.com
Richard Ferrise Comcast Cable Communications Email: rich_ferrise@cable.comcast.com
Richard Ferrise康卡斯特有线通信电子邮件：rich_ferrise@cable.comcast.com
Chris Harvey Comcast Cable Communications Email: chris_harvey@cable.comcast.com
Chris Harvey Comcast有线通信电子邮件：Chris_harvey@cable.comcast.com
Hadriel Kaplan Acme Packet Email: hkaplan@acmepacket.com
Hadriel Kaplan Acme数据包电子邮件：hkaplan@acmepacket.com
[1] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[1] Faltstrom，P.和M.Mealling，“E.164到统一资源标识符（URI）动态委托发现系统（DDDS）应用程序（ENUM）”，RFC 3761，2004年4月。
[2] ITU-T, "The International Public Telecommunication Numbering Plan", Recommendation E.164, May 1997.
[2] ITU-T，“国际公共电信编号计划”，建议E.164，1997年5月。
[3] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, November 1987.
[3] Mockapetris，P.，“域名-概念和设施”，STD 13，RFC 1034，1987年11月。
[4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403, October 2002.
[4] Mealling，M.“动态委托发现系统（DDDS）第三部分：域名系统（DNS）数据库”，RFC3403，2002年10月。
[5] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS", RFC 3401, October 2002.
[5] Mealling，M，“动态委托发现系统（DDDS）第一部分：综合DDDS”，RFC 3401，2002年10月。
[6] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm", RFC 3402, October 2002.
[6] Mealling，M.，“动态委托发现系统（DDDS）第二部分：算法”，RFC3402，2002年10月。
[7] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)", RFC 3404, October 2002.
[7] Mealling，M.“动态委托发现系统（DDDS）第四部分：统一资源标识符（URI）”，RFC34042002年10月。
[8] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures", BCP 65, RFC 3405, October 2002.
[8] Mealling，M.“动态委托发现系统（DDDS）第五部分：URI.ARPA分配程序”，BCP 65，RFC 3405，2002年10月。
[9] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, December 2004.
[9] Schulzrinne，H.，“电话号码的电话URI”，RFC 3966，2004年12月。
[10] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002.
[10] Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.，和E.Schooler，“SIP：会话启动协议”，RFC 3261，2002年6月。
[11] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[11] 菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC2616，1999年6月。
[12] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[12] Rescorla，E.，“TLS上的HTTP”，RFC 2818，2000年5月。
[13] Peterson, J., Liu, H., Yu, J., and B. Campbell, "Using E.164 numbers with the Session Initiation Protocol (SIP)", RFC 3824, June 2004.
[13] Peterson，J.，Liu，H.，Yu，J.，和B.Campbell，“将E.164号码与会话启动协议（SIP）结合使用”，RFC 38242004年6月。
[14] Vaudreuil, G., "Voice Message Routing Service", RFC 4238, October 2005.
[14] Vaudreuil，G.，“语音信息路由服务”，RFC 4238，2005年10月。
[15] Brandner, R., Conroy, L., and R. Stastny, "IANA Registration for Enumservices email, fax, mms, ems, and sms", RFC 4355, January 2006.
[15] R.Brandner、L.Conroy和R.Stastny，“IANA注册电子邮件、传真、彩信、ems和短信服务”，RFC 43552006年1月。
[16] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "Protocol Modifications for the DNS Security Extensions", RFC 4035, March 2005.
[16] Arends，R.，Austein，R.，Larson，M.，Massey，D.，和S.Rose，“DNS安全扩展的协议修改”，RFC 4035，2005年3月。
[17] Atkins, D. and R. Austein, "Threat Analysis of the Domain Name System (DNS)", RFC 3833, August 2004.
[17] Atkins，D.和R.Austein，“域名系统（DNS）的威胁分析”，RFC 38332004年8月。
[18] Foster, M., McGarry, T., and J. Yu, "Number Portability in the Global Switched Telephone Network (GSTN): An Overview", RFC 3482, February 2003.
[18] Foster，M.，McGarry，T.，和J.Yu，“全球交换电话网络（GSTN）中的号码可移植性：概述”，RFC 3482，2003年2月。
[19] Peterson, J., "enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record", RFC 3764, April 2004.
[19] Peterson，J.，“会话启动协议（SIP）记录地址的枚举服务注册”，RFC 3764，2004年4月。
Authors' Addresses
作者地址
Jason Livingood Comcast Cable Communications One Comcast Center 1701 John F. Kennedy Boulevard Philadelphia, PA 19103 USA EMail: jason_livingood@cable.comcast.com
Jason Livingood Comcast有线通信一号Comcast中心1701美国宾夕法尼亚州费城肯尼迪大道19103号电子邮件：Jason_livingood@cable.comcast.com
Donald Troshynski Acme Packet EMail: dtroshynski@acmepacket.com
Donald Troshynski Acme数据包电子邮件：dtroshynski@acmepacket.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
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.
本文件受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, THE IETF TRUST 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.