Network Working Group J. Livingood
Request for Comments: 4769 Comcast Cable Communications
Category: Standards Track R. Shockey
NeuStar
November 2006
Network Working Group J. Livingood
Request for Comments: 4769 Comcast Cable Communications
Category: Standards Track R. Shockey
NeuStar
November 2006
IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information
包含公共交换电话网（PSTN）信令信息的Enumservice的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）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
Abstract
摘要
This document registers the Enumservice type "pstn" and subtype "tel" using the URI scheme 'tel', as well as the subtype "sip" using the URI scheme 'sip' as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice is used to facilitate the routing of telephone calls in those countries where number portability exists.
本文档根据枚举规范RFC 3761中定义的IANA注册过程，使用URI方案“tel”注册枚举服务类型“pstn”和子类型“tel”，以及使用URI方案“sip”注册子类型“sip”。这项服务用于在存在号码可携性的国家方便电话呼叫的路由。
Table of Contents
目录
1. Introduction ....................................................3
2. Distribution of Data ............................................4
3. ENUM Service Registration for PSTN ..............................5
3.1. ENUM Service Registration for PSTN with Subtype "tel" ......5
3.2. ENUM Service Registration for PSTN with Subtype "sip" ......5
4. Examples ........................................................6
4.1. Example of a Ported Number, Using a 'tel' URI Scheme .......6
4.2. Example of a Ported Number, Using a 'sip' URI Scheme .......6
4.3. Example of a Non-Ported Number, Using a 'tel' URI Scheme ...7
4.4. Example of a Non-Ported Number, Using a 'sip' URI Scheme ...7
4.5. Example Using a Regular Expression .........................7
5. Implementation Recommendations ..................................7
5.1. Call Processing When Multiple Records Are Returned .........7
5.2. NAPTR Configuration issues .................................8
6. Examples of E2U+pstn in Call Processing .........................8
6.1. Dialed Number Not Available On-Net .........................8
6.2. Dialed Number Available On-Net and on the PSTN .............9
7. Security Considerations .........................................9
8. IANA Considerations ............................................10
9. Acknowledgements ...............................................10
10. References ....................................................10
10.1. Normative References .....................................10
10.2. Informative References ...................................11
1. Introduction ....................................................3
2. Distribution of Data ............................................4
3. ENUM Service Registration for PSTN ..............................5
3.1. ENUM Service Registration for PSTN with Subtype "tel" ......5
3.2. ENUM Service Registration for PSTN with Subtype "sip" ......5
4. Examples ........................................................6
4.1. Example of a Ported Number, Using a 'tel' URI Scheme .......6
4.2. Example of a Ported Number, Using a 'sip' URI Scheme .......6
4.3. Example of a Non-Ported Number, Using a 'tel' URI Scheme ...7
4.4. Example of a Non-Ported Number, Using a 'sip' URI Scheme ...7
4.5. Example Using a Regular Expression .........................7
5. Implementation Recommendations ..................................7
5.1. Call Processing When Multiple Records Are Returned .........7
5.2. NAPTR Configuration issues .................................8
6. Examples of E2U+pstn in Call Processing .........................8
6.1. Dialed Number Not Available On-Net .........................8
6.2. Dialed Number Available On-Net and on the PSTN .............9
7. Security Considerations .........................................9
8. IANA Considerations ............................................10
9. Acknowledgements ...............................................10
10. References ....................................................10
10.1. Normative References .....................................10
10.2. Informative References ...................................11
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 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记录（动态委托发现系统（DDDS））使用DNS（域名系统，RFC 1034[3]）委托的技术第三部分：域名系统（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应用程序。
Number Portability allows telephone subscribers to keep their telephone numbers when they change service providers, move to a new location, or change the subscribed services [14]. In many countries, such as the United States and Canada, the functions of naming and addressing on the Public Switched Telephone Network (PSTN) have been abstracted. In the case of a ported number, the dialed number is not directly routable on the PSTN and must be translated into a routing number for call completion. Other numbers, which are not ported, and which can be routed directly on the PSTN based on the dialed number, are typically assigned to carriers and other entities in large blocks or pools. Number Portability and other numbering information are distributed in a variety of methods and formats around the world.
号码可携性允许电话用户在更换服务提供商、移动到新位置或更改订阅的服务时保留其电话号码[14]。在许多国家，如美国和加拿大，公共交换电话网（PSTN）的命名和寻址功能已被抽象。在端口号码的情况下，拨号号码不能在PSTN上直接路由，必须转换为路由号码才能完成呼叫。其他号码通常分配给大数据块或池中的运营商和其他实体，这些号码没有端口，可以根据所拨号码直接在PSTN上路由。可移植性和其他编号方法在世界各地分布。
The Enumservices described here could enable service providers to place ported numbers, pooled numbers, and blocks of numbers and their associated PSTN contact information, into externally available or highly locally cached ENUM databases. This, in turn, could enable such parties to consolidate all telephone number lookups in their networks into a single ENUM lookup, thereby simplifying call routing and network operations, which would then result in either an on-net (IP-based) response or an off-net (PSTN-based) response.
此处描述的Enumservices可使服务提供商将端口号码、池号码、号码块及其相关PSTN联系信息放入外部可用或高度本地缓存的ENUM数据库中。这反过来可以使这些方能够将其网络中的所有电话号码查找合并为单个枚举查找，从而简化呼叫路由和网络操作，这将导致网络上（基于IP的）响应或网络外（基于PSTN的）响应。
The following Enumservice is registered with this document: "pstn" to indicate PSTN routing data, including number portability data, non-ported telephone number data (individually or in number blocks), and other PSTN-oriented data that is associated with E.164 telephone numbers. The purpose of this Enumservice is to provide routing information for telephone numbers that do not designate an endpoint resident on the public Internet or a private/peered Internet Protocol
以下Enumservice在本文件中注册：“pstn”表示pstn路由数据，包括号码可携性数据、非端口电话号码数据（单独或在号码块中）以及与E.164电话号码相关的其他面向pstn的数据。此服务的目的是为不指定驻留在公共Internet或专用/对等Internet协议上的端点的电话号码提供路由信息
(IP) network. Thus, these are numbers that are only routable via the traditional PSTN, even if the call originates from an IP network. The URIs returned in this service may use the TEL URI parameters defined in RFC 4694 [10], and implementations must be prepared to accept them.
（IP）网络。因此，这些号码只能通过传统的PSTN路由，即使呼叫来自IP网络。此服务中返回的URI可能使用RFC 4694[10]中定义的TEL URI参数，实现必须准备好接受这些参数。
The service parameters defined in RFC 3761 indicate that a "type" and a "subtype" may be specified. Within this set of specifications, the convention is assumed that the "type" (being the more generic term) defines the service and the "subtype" defines the URI scheme.
RFC 3761中定义的服务参数表示可以指定“类型”和“子类型”。在这组规范中，约定假定“类型”（更通用的术语）定义服务，“子类型”定义URI方案。
When only one URI scheme is associated with a given service, it should be assumed that an additional URI scheme to be used with this service may be added at a later time. Thus, the subtype is needed to identify the specific Enumservice intended.
当只有一个URI方案与给定的服务相关联时，应该假定稍后可以添加与该服务一起使用的附加URI方案。因此，需要使用子类型来标识所需的特定枚举服务。
The distribution of number portability data is often highly restricted, either by contract or regulation of a National Regulatory Authority (NRA); therefore, NAPTR records specified herein may or may not be part of the e164.arpa DNS tree.
号码可携性数据的分发通常受到国家监管机构（NRA）的合同或法规的高度限制；因此，此处指定的NAPTR记录可能是也可能不是e164.arpa DNS树的一部分。
The authors believe that it is more likely that these records will be distributed on a purely private basis. Distribution of this NAPTR data could be either (a) on a private basis (within a service provider's internal network, or on a private basis between one or more parties using a variety of security mechanisms to prohibit general public access), (b) openly available or, (c) distributed by the relevant number portability organization or other industry organization, but possibly on a national basis and subject to or in accordance with national regulatory policy.
作者认为，这些记录更可能是纯粹以私人方式分发的。该NAPTR数据的分发可以是（a）在私人基础上（在服务提供商的内部网络内，或在使用各种安全机制禁止公众访问的一方或多方之间以私人基础上），（b）公开可用或（c）由相关号码可携性组织或其他行业组织分发，但可能以国家为基础，并遵守或符合国家监管政策。
If such data were distributed nationally, the national telephone numbering authority, or some other regulatory body or numbering organization, may have jurisdiction. Such a body may choose to restrict distribution of the data in such a way that it may not pass over that country's national borders.
如果此类数据在全国范围内分发，则国家电话号码管理局或其他监管机构或号码组织可能具有管辖权。这样一个机构可能会选择限制数据的传播，使其不会越过该国的国界。
Enumservice Name: "pstn"
枚举服务名称：“pstn”
Enumservice Type: "pstn"
枚举服务类型：“pstn”
Enumservice Subtype: "tel"
枚举服务子类型：“电话”
URI Scheme: 'tel:'
URI方案：“电话：”
Functional Specification:
功能规格：
These Enumservices indicate that the remote resource identified can be addressed by the associated URI scheme in order to initiate a telecommunication session, which may include two-way voice or other communications, to the PSTN. These URIs may contain number portability data as specified in RFC 4694 [10].
这些服务指示所识别的远程资源可以由相关联的URI方案寻址，以便发起到PSTN的电信会话，该电信会话可以包括双向语音或其他通信。这些URI可能包含RFC 4694[10]中规定的号码可移植性数据。
Security Considerations: See Section 7.
安全注意事项：见第7节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Richard Shockey (richard.shockey@neustar.biz)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)理查德·肖基（理查德。shockey@neustar.biz)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
A Number Portability Dip Indicator (npdi) should be used in practice (see examples below in Section 4).
在实践中应使用数字便携性倾角指示器（npdi）（见下文第4节中的示例）。
Enumservice Name: "pstn"
枚举服务名称：“pstn”
Enumservice Type: "pstn"
枚举服务类型：“pstn”
Enumservice Subtype: "sip"
枚举服务子类型：“sip”
URI Scheme: 'sip:'
URI方案：“sip:”
Functional Specification:
功能规格：
These Enumservices indicate that the remote resource identified can be addressed by the associated URI scheme in order to initiate a telecommunication session, which may include two-way voice or other communications, to the PSTN.
这些服务指示所识别的远程资源可以由相关联的URI方案寻址，以便发起到PSTN的电信会话，该电信会话可以包括双向语音或其他通信。
Security Considerations: See Section 7.
安全注意事项：见第7节。
Intended Usage: COMMON
预期用途：普通
Authors:
作者：
Jason Livingood (jason_livingood@cable.comcast.com) Richard Shockey (richard.shockey@neustar.biz)
杰森·利文戈德（杰森·利文戈德）_livingood@cable.comcast.com)理查德·肖基（理查德。shockey@neustar.biz)
Any other information the author deems interesting:
作者认为有趣的任何其他信息：
A Number Portability Dip Indicator (npdi) should be used in practice (see examples below in Section 4).
在实践中应使用数字便携性倾角指示器（npdi）（见下文第4节中的示例）。
The following sub-sections document several examples for illustrative purposes. 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+pstn:tel" "!^.*$!tel:+1-215-555-0123;npdi;rn=+1-215-555-0199!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+pstn:电话：“！^.*$！电话：+1-215-555-0123；npdi；rn=+1-215-555-0199！”。
In this example, a Routing Number (rn) and a Number Portability Dip Indicator (npdi) are used as shown in RFC 4694 [10]. The 'npdi' field is included in order to prevent subsequent lookups in legacy-style PSTN databases.
在本例中，如RFC 4694[10]所示，使用路由号码（rn）和号码可携性Dip指示器（npdi）。包含“npdi”字段是为了防止在旧式PSTN数据库中进行后续查找。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+pstn:sip" "!^.*$!sip:+1-215-555-0123;npdi;rn=+1-215-555-0199 @gw.example.com;user=phone!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”“E2U+pstn:sip”“！^.*$！sip:+1-215-555-0123；npdi；rn=+1-215-555-0199@gw.example.com；用户=电话！”。
In this example, a Routing Number (rn) and a Number Portability Dip Indicator (npdi) are used as shown in RFC 4694 [10]. The 'npdi' field is included in order to prevent subsequent lookups in legacy-
在本例中，如RFC 4694[10]所示，使用路由号码（rn）和号码可携性Dip指示器（npdi）。包含“npdi”字段是为了防止后续在旧版中查找-
style PSTN databases. The method of conversion from a tel to a SIP URI is as demonstrated in RFC 3261, Section 19.1.6 [11], as well as in RFC 4694, Section 6 [10].
样式PSTN数据库。从tel到SIP URI的转换方法如RFC 3261第19.1.6节[11]以及RFC 4694第6节[10]所示。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+pstn:tel" "!^.*$!tel:+1-215-555-0123;npdi!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+pstn:电话：“！^.*$！电话：+1-215-555-0123；npdi！”。
In this example, a Number Portability Dip Indicator (npdi) is used [10]. The 'npdi' field is included in order to prevent subsequent lookups in legacy-style PSTN databases.
在本例中，使用了号码可携性倾角指示器（npdi）[10]。包含“npdi”字段是为了防止在旧式PSTN数据库中进行后续查找。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+pstn:sip" "!^.*$!sip:+1-215-555-0123;npdi@gw.example.com;user=phone!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”E2U+pstn:sip”“！^.*$！sip:+1-215-555-0123；npdi@gw.example.com“用户=电话！”。
In this example, a Number Portability Dip Indicator (npdi) is used [10]. The 'npdi' field is included in order to prevent subsequent lookups in legacy-style PSTN databases. The method of conversion from a tel to a SIP URI is as demonstrated in RFC 3261, Section 19.1.6 [11], as well as in RFC 4694, Section 6 [10].
在本例中，使用了号码可携性倾角指示器（npdi）[10]。包含“npdi”字段是为了防止在旧式PSTN数据库中进行后续查找。从tel到SIP URI的转换方法如RFC 3261第19.1.6节[11]以及RFC 4694第6节[10]所示。
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+pstn:tel" "!(^.*)$!tel:\1;npdi!".
$ORIGIN 3.2.1.0.5.5.5.5.1.2.1.e164.arpa。NAPTR 10 100“u”“E2U+pstn:电话”“！（^.*）$！电话：\1；npdi！”。
In this example, a regular expression replacement function is used to reduce the size of the NAPTR record. The tel URI uses "\1", which would dynamically replace the expression with the TN plus the leading "+" -- in this case, +1-215-555-0123.
在本例中，正则表达式替换函数用于减小NAPTR记录的大小。teluri使用“\1”，它将动态地用TN加上前导“+”替换表达式——在本例中为+1-215-555-0123。
It is likely that both E2U+sip and E2U+pstn Enumservice type records will be returned for a given query. In this case, this could result in what is essentially an on-net and off-net pstn record. Thus, one record gives the associated address on an IP network, while the other gives the associated address on the PSTN. 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
对于给定的查询，可能会同时返回E2U+sip和E2U+pstn枚举服务类型记录。在这种情况下，这可能导致本质上是一个网内和网外pstn记录。因此，一条记录给出IP网络上的关联地址，而另一条记录给出PSTN上的关联地址。与e164.arpa树的典型枚举查询产生的多条记录一样，由使用枚举解析器的应用程序确定哪一条记录
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. For example, such a resolver could be configured to grant preference to the on-net record, or execute other logic, as required by the application.
要使用的记录以及要忽略的记录。实现者应该考虑到这一点，并将逻辑构建到他们的应用程序中，这些应用程序可以根据业务、网络或其他规则从多个记录中进行适当选择。例如，根据应用程序的需要，可以将这样的解析器配置为向在线记录授予优先权，或执行其他逻辑。
It has been suggested that tel URIs may be easier and more efficient to use in practice than SIP URIs. In addition, the use of tel URIs may result in somewhat smaller NAPTR records, which, when considering adding hundreds of millions of these records to the DNS, could have a substantial impact on the processing and storage requirements for service providers or other entities making use of this Enumservice type.
有人建议在实践中使用tel-uri可能比SIP-uri更容易、更有效。此外，tel URI的使用可能会导致NAPTR记录变得更小，当考虑将数亿条此类记录添加到DNS时，可能会对使用此服务类型的服务提供商或其他实体的处理和存储需求产生重大影响。
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. Using the example in Section 4.5, above, this is 11 bytes per record.
实现者可能希望考虑使用正则表达式以减少单个NAPTR的大小。这将对所涉及数据库的总体大小产生重大影响。使用上面第4.5节中的示例，这是每个记录11个字节。
These are examples of how a switch, proxy, or other calling application may make use of this Enumservice type during the call initiation process.
以下是交换机、代理或其他调用应用程序在调用启动过程中如何使用此Enumservice类型的示例。
When the dialed number is not available on-net, the call processing is as follows.
当拨号号码在网络上不可用时，呼叫处理如下。
a) A user, which is connected to a calling application, dials an E.164 telephone number: +1-215-555-0123.
a) 连接到呼叫应用程序的用户拨打E.164电话号码：+1-215-555-0123。
b) The calling application uses the dialed number to form a NAPTR record: 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
b) 呼叫应用程序使用已拨号码形成NAPTR记录：3.2.1.0.5.5.5.5.1.2.1.e164.arpa。
c) The DNS finds an E2U+pstn:tel record and returns a tel URI for processing by the calling application: tel:+1-215-555-0123;npdi.
c) DNS找到一个E2U+pstn:tel记录并返回一个tel URI供调用应用程序处理：tel：+1-215-555-0123；npdi。
d) The calling application uses routing logic to determine which media gateway is the closest to this number and routes the call appropriately.
d) 呼叫应用程序使用路由逻辑来确定哪个媒体网关最接近此号码，并适当地路由呼叫。
When the dialed number is available on-net and on the PSTN, the call processing is as follows.
当拨号号码在网络和PSTN上可用时，呼叫处理如下。
a) A user, which is connected to a calling application, dials an E.164 telephone number: 1-215-555-0123.
a) 连接到呼叫应用程序的用户拨打E.164电话号码：1-215-555-0123。
b) The calling application uses the dialed number to form a NAPTR record: 3.2.1.0.5.5.5.5.1.2.1.e164.arpa.
b) 呼叫应用程序使用已拨号码形成NAPTR记录：3.2.1.0.5.5.5.5.1.2.1.e164.arpa。
c) The DNS finds both an E2U+pstn record, as well as an E2U+sip record, since this number happens to be on the IP network of a connected network.
c) DNS同时查找E2U+pstn记录和E2U+sip记录，因为此号码恰好位于连接网络的IP网络上。
d) The calling application prioritizes the on-net record first: sip:+1-215-555-0123;npdi@gw.example.com;user=phone.
d) 呼叫应用程序首先对在线记录进行优先级排序：sip:+1-215-555-0123；npdi@gw.example.com;用户=电话。
e) The calling application sets up the SIP call to gw.example.com.
e) 呼叫应用程序设置对gw.example.com的SIP呼叫。
f) Should the IP call route fail for whatever reason, the calling application may be able to utilize the E2U+pstn record to invoke a fallback route to a media gateway that is connected to the PSTN.
f) 如果IP呼叫路由由于任何原因失败，呼叫应用程序可能能够利用E2U+pstn记录调用到连接到pstn的媒体网关的回退路由。
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 PSTN 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或任何其他公共可用域作为维护PSTN 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 they can use to make unsolicited "telemarketing" phone calls. Many countries have do-not-call registries or other legal or regulatory mechanisms in place to deal with such abuses.
第三方收集的此类数据通常用于生成未经请求的信息的目标列表。因此，第三方可以使用该列表生成一个列表，用于拨打未经请求的“电话营销”电话。许多国家没有设立登记处或其他法律或监管机制来处理此类侵权行为。
As noted earlier, carriers, service providers, and other users may simply choose not to publish such information in the public e164.arpa tree. They may instead simply publish this in their internal ENUM routing database that is only able to be queried by trusted elements
如前所述，运营商、服务提供商和其他用户可以选择不在公共e164.arpa树中发布此类信息。相反，他们可能只是将其发布到其内部枚举路由数据库中，该数据库只能由受信任的元素查询
of their network, 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.
他们的网络，如软交换和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 [12] to this is provided in RFC 3761 [1]. A thorough analysis of threats to the DNS itself is covered in RFC 3833 [13].
RFC 3761[1]中提供了对ENUM依赖DNS的特定威胁以及DNSSEC[12]对此的适用性的分析。RFC 3833[13]对DNS本身的威胁进行了全面分析。
This document registers the 'pstn' Enumservice type and the subtype "tel" and "sip" under the Enumservice registry described in the IANA considerations in RFC 3761. Details of this registration are provided in Section 3 of this document.
本文档在RFC 3761中IANA注意事项中描述的Enumservice注册表下注册“pstn”Enumservice类型以及子类型“tel”和“sip”。本文件第3节提供了该注册的详细信息。
The authors wish to thank Lawrence Conroy, Tom Creighton, Jason Gaedtke, Jaime Jimenez, Chris Kennedy, Alexander Mayrhofer, Doug Ranalli, Jonathan Rosenberg, Bob Walter, and James Yu for their helpful discussions of this topic, and detailed reviews of this document. The authors also wish to thank the IETF's ENUM Working Group for helpful feedback in refining and developing this document.
作者希望感谢劳伦斯·康罗伊、汤姆·克雷顿、杰森·盖德克、杰米·希门尼斯、克里斯·肯尼迪、亚历山大·梅尔霍夫、道格·拉纳利、乔纳森·罗森博格、鲍勃·沃尔特和詹姆斯·余对本主题的有益讨论以及对本文件的详细评论。作者还希望感谢IETF的ENUM工作组在完善和开发本文件方面提供的有益反馈。
[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 Number Plan", Recommendation E.164, February 2005.
[2] ITU-T，“国际公共电信号码计划”，建议E.164，2005年2月。
[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] Yu, J., "Number Portability Parameters for the "tel" Uniform Resource Identifier", RFC 4694, October 2006.
[10] Yu，J.，“电话统一资源标识符的号码可移植性参数”，RFC4694，2006年10月。
[11] 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.
[11] Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.，和E.Schooler，“SIP：会话启动协议”，RFC 3261，2002年6月。
[12] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "Protocol Modifications for the DNS Security Extensions", RFC 4035, March 2005.
[12] Arends，R.，Austein，R.，Larson，M.，Massey，D.，和S.Rose，“DNS安全扩展的协议修改”，RFC 4035，2005年3月。
[13] Atkins, D. and R. Austein, "Threat Analysis of the Domain Name System (DNS)", RFC 3833, August 2004.
[13] Atkins，D.和R.Austein，“域名系统（DNS）的威胁分析”，RFC 38332004年8月。
[14] Foster, M., McGarry, T., and J. Yu, "Number Portability in the Global Switched Telephone Network (GSTN): An Overview", RFC 3482, February 2003.
[14] Foster，M.，McGarry，T.，和J.Yu，“全球交换电话网络（GSTN）中的号码可移植性：概述”，RFC 3482，2003年2月。
Authors' Addresses
作者地址
Jason Livingood Comcast Cable Communications 1500 Market Street Philadelphia, PA 19102 USA
美国宾夕法尼亚州费城市场街1500号Jason Livingood Comcast有线通信公司，邮编：19102
Phone: +1-215-981-7813
EMail: jason_livingood@cable.comcast.com
Phone: +1-215-981-7813
EMail: jason_livingood@cable.comcast.com
Richard Shockey NeuStar 46000 Center Oak Plaza Sterling, VA 20166 USA
Richard Shockey NeuStar 46000中心奥克广场Sterling，弗吉尼亚州20166美国
Phone: +1-571-434-5651
EMail: richard.shockey@neustar.biz
Phone: +1-571-434-5651
EMail: richard.shockey@neustar.biz
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
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.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。