1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<pre>Network Working Group J. Livingood
Request for Comments: 5526 Comcast Cable Communications
Category: Informational P. Pfautz
AT&T
R. Stastny
Unaffiliated
April 2009
<span class="h1">The E.164 to Uniform Resource Identifiers (URI)</span>
<span class="h1">Dynamic Delegation Discovery System (DDDS) Application</span>
<span class="h1">for Infrastructure ENUM</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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.
<span class="grey">Livingood, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5526">RFC 5526</a> Infrastructure ENUM April 2009</span>
Abstract
This document defines the use case for Infrastructure ENUM and
proposes its implementation as a parallel namespace to "e164.arpa",
as defined in <a href="./rfc3761">RFC 3761</a>, as the long-term solution to the problem of
allowing carriers to provision DNS records for telephone numbers
independently of those provisioned by end users (number assignees).
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Zone Apex for Infrastructure ENUM ...............................<a href="#page-3">3</a>
<a href="#section-4">4</a>. IANA Considerations .............................................<a href="#page-3">3</a>
<a href="#section-5">5</a>. Security and Privacy Considerations .............................<a href="#page-4">4</a>
<a href="#section-6">6</a>. Acknowledgements ................................................<a href="#page-4">4</a>
<a href="#section-7">7</a>. Normative References ............................................<a href="#page-4">4</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
ENUM (E.164 Number Mapping [<a href="#ref-1" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">1</a>]) is a system that transforms E.164
numbers [<a href="#ref-2" title=""The International Public Telecommunication Number Plan"">2</a>] into domain names and then uses the DNS (Domain Name
Service) [<a href="#ref-3" title=""Domain names - concepts and facilities"">3</a>] to discover NAPTR records that specify what services are
available for a specific domain name.
ENUM as originally defined was based on the end-user opt-in
principle. While this has great potential to foster new services and
end-user choices in the long term, the current requirements for
IP-based interconnection of Voice over IP (VoIP) domains require the
provisioning of large numbers of allocated or served (hosted) numbers
of a participating service provider, without the need for individual
users to opt-in. This way, service providers can provision their own
ENUM information that is separate, distinct, and likely to be
different from what an end-user may provision. This is particularly
important if Infrastructure ENUM is used for number-portability
applications, for example, which an end-user would be unlikely
interested in provisioning but which a service provider would likely
find essential.
In addition, while it is possible that service providers could
mandate that their users opt-into e164.arpa through end-user contract
terms and conditions, there are substantial downsides to such an
approach. Thus, for all these reasons and many others, ENUM for
end-user provisioning is ill-suited for use by service providers for
the interconnection of VoIP domains.
<span class="grey">Livingood, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5526">RFC 5526</a> Infrastructure ENUM April 2009</span>
As VoIP evolves and becomes pervasive, E.164-addressed telephone
calls need not necessarily traverse the Public Switched Telephone
Network (PSTN). Therefore, VoIP service providers have an interest
in using ENUM on a so-called "Infrastructure" basis in order to keep
VoIP traffic on IP networks on an end-to-end basis, both within and
between service provider domains. This requires a means of
identifying a VoIP point of interconnection to which calls addressed
to a given E.164 number may be delivered; Infrastructure ENUM
provides this means. Calls that can originate and terminate on IP
networks, and do not have to traverse the PSTN, will require fewer or
no points of transcoding, and can also involve additional IP network
services that are not possible on the PSTN, among other benefits.
Requirements for Infrastructure ENUM are provided in [<a href="#ref-4" title=""Infrastructure ENUM Requirements"">4</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
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 <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a> [<a href="#ref-5" title=""Key words for use in RFCs to Indicate Requirement Levels"">5</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Zone Apex for Infrastructure ENUM</span>
This document proposes that Infrastructure ENUM be implemented by
means of a parallel namespace to e164.arpa dedicated to
Infrastructure ENUM, in a domain that is yet to be determined. Use
of a parallel namespace allows carriers and end-users to control
their ENUM registrations independently, without forcing one to work
through the other.
Infrastructure ENUM Tier 2 resource records in the Infrastructure
ENUM tree will be controlled by the service provider that is
providing services to a given E.164 number, generally referred to in
various countries as the "carrier-of-record" (see [<a href="#ref-4" title=""Infrastructure ENUM Requirements"">4</a>]). The
definition of a carrier-of-record for a given E.164 number is a
national matter or is defined by the entity controlling the numbering
space.
See also <a href="#section-3">Section 3</a>, "Requirements for Infrastructure ENUM", of [<a href="#ref-4" title=""Infrastructure ENUM Requirements"">4</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
IANA has created a registry for Enumservices as originally specified
in <a href="./rfc2916">RFC 2916</a> and revised in <a href="./rfc3761">RFC 3761</a>. Enumservices registered with
IANA are valid for Infrastructure ENUM as well as end-user ENUM.
<span class="grey">Livingood, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5526">RFC 5526</a> Infrastructure ENUM April 2009</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security and Privacy Considerations</span>
This document proposes a new zone apex for ENUM to meet the
requirements of Infrastructure ENUM. The over-the-network protocol
of ENUM is unchanged by the addition of an apex and, as such, the
Security Considerations of <a href="./rfc3761">RFC 3761</a> [<a href="#ref-1" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">1</a>] still apply. Specific
considerations related to the security of an Infrastructure ENUM apex
are given in more detail in <a href="#section-4">Section 4</a>, "Security Considerations", of
[<a href="#ref-4" title=""Infrastructure ENUM Requirements"">4</a>].
Infrastructure ENUM registrations proposed by this document should
resolve to service provider points-of-interconnection rather than to
end-user equipment. Service providers need to take appropriate
measures to protect their end-user customers from unwanted
communications as with other types of interconnections.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
The authors wish to thank Lawrence Conroy, Patrik Faltstrom, Michael
Haberler, Otmar Lendl, Steve Lind, Alexander Mayrhofer, Jim Reid, and
Richard Shockey for their helpful discussions of this document and
the concept of Infrastructure ENUM.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Normative References</span>
[<a id="ref-1">1</a>] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
Identifiers (URI) Dynamic Delegation Discovery System (DDDS)
Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004.
[<a id="ref-2">2</a>] ITU-T, "The International Public Telecommunication Number Plan",
Recommendation E.164, February 2005.
[<a id="ref-3">3</a>] Mockapetris, P., "Domain names - concepts and facilities", STD
13, <a href="./rfc1034">RFC 1034</a>, November 1987.
[<a id="ref-4">4</a>] Lind, S. and P. Pfautz, "Infrastructure ENUM Requirements", <a href="./rfc5067">RFC</a>
<a href="./rfc5067">5067</a>, November 2007.
[<a id="ref-5">5</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
<span class="grey">Livingood, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5526">RFC 5526</a> Infrastructure ENUM April 2009</span>
Authors' Addresses
Jason Livingood
Comcast Cable Communications
1500 Market Street
Philadelphia, PA 19102
USA
Phone: +1-215-981-7813
EMail: jason_livingood@cable.comcast.com
Penn Pfautz
AT&T
200 S. Laurel Ave
Middletown, NJ 07748
USA
Phone: +1-732-420-4962
EMail: ppfautz@att.com
Richard Stastny
Anzbachgasse 43
1140 Vienna
Austria
Phone: +43-664-420-4100
EMail: richard.stastny@gmail.com
Livingood, et al. Informational [Page 5]
</pre>
|
