Debian Codegraph @

rfc3026.html

raw
1 <pre>Network Working Group R. Blane
2 Request for Comments: 3026 ITU
3 Category: Informational January 2001
4
5
6 <span class="h1">Liaison to IETF/ISOC on ENUM</span>
7
8 Status of this Memo
9
10 This memo provides information for the Internet community. It does
11 not specify an Internet standard of any kind. Distribution of this
12 memo is unlimited.
13
14 Copyright Notice
15
16 Copyright (C) The Internet Society (2001). All Rights Reserved.
17
18 Abstract
19
20 Working Party 1/2, of the International Telecommunication Union
21 Telecommunication Standardization Sector (ITU-T) held a meeting of
22 its collaborators in Berlin Germany 19-26 October 2000. The agenda
23 of the meeting contained several contributions regarding <a href="./rfc2916">RFC 2916</a>:
24 "E.164 Number and DNS" from the Internet Engineering Task Force's
25 (IETF) ENUM Working Group - more specifically, the method for
26 administering and maintaining the E.164-based resources in the Domain
27 Name System (DNS) as related to the ENUM protocol. Consequently, in
28 addition to the WP1/2 collaborators, there were several members of
29 the IETF present to assist with the discussion of issues contained in
30 the aforementioned contributions.
31
32 This liaison from WP1/2 to the IETF/ISOC conveys the understandings
33 of the WP1/2 collaborators resulting from the discussions.
34
35 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Considerations under Question 1/2 (Numbering)</span>
36
37 Throughout this document, the terms "administration" or
38 "administrative functions" refer to the provision and update of the
39 E.164 numerical values, to be contained in the zones of a domain name
40 in the "e164.arpa" domain, in the DNS.
41
42 It is noted that most ENUM service and administrative decisions are
43 national issues under the purview of ITU Member States, since most of
44 the E.164 resources are utilized nationally.
45
46 These understandings are relative only to the provision of E.164
47 information for DNS administrative functions, not policy or
48 operational functions.
49
50
51
52 <span class="grey">Blane Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc3026">RFC 3026</a> Liaison to IETF/ISOC on ENUM January 2001</span>
55
56
57 In order to advance a common terminology for the purpose of this
58 liaison, we have defined the zones of a domain name as follows.
59
60 Using an example, domain name "1.5.1.5.0.2.0.4.1.3.3.e164.arpa" (as
61 in <a href="./rfc2916">RFC 2916</a>) is segmented into zones as follow:
62
63 E164.arpa - domain zone
64
65 3.3. - country code zone (1, 2, or 3 digits dependent on CC)
66
67 1.5.1.5.0.2.0.4.1. - national zone
68
69 The first understandings to be conveyed are those regarding the
70 responsibilities for administration of the various zones within the
71 "e164.arpa" domain:
72
73 o The domain zone administration was agreed to be outside the scope
74 of this meeting and WP1/2.
75
76 o For all E.164 Country Code Zone resources (Country Codes and
77 Identification Codes), the ITU has the responsibility to provide
78 assignment information to DNS administrators, for performing the
79 administrative function. The ITU will ensure that each Member
80 State has authorized the inclusion of their Country Code
81 information for input to the DNS. For resources that are spare or
82 designated as test codes there will normally be no entry in the
83 DNS. However, the ITU will provide spare code lists to DNS
84 administrators for purposes of clarification. The entity to which
85 E.164 test codes have been assigned will be responsible for
86 providing any appropriate assignment information to DNS
87 administrators.
88
89 o The administration of National Zone numbering information is
90 determined by the type of Country Code resource that a National
91 Zone is behind:
92
93 * The national zone, for geographic resources, is a national
94 matter and is, therefore, administered by the ITU Member
95 State(s) to which the country code is assigned. In an
96 integrated numbering plan, e.g., CC "1", each Country within
97 the plan may administer their portion of the resource in a
98 different manner.
99
100 * For national zone resources behind the Country Codes assigned
101 to and shared by Networks, the entity to which the resource is
102 assigned provides the E.164 assignment information, to DNS
103 administrators for performing the administrative function.
104
105
106
107
108 <span class="grey">Blane Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc3026">RFC 3026</a> Liaison to IETF/ISOC on ENUM January 2001</span>
111
112
113 * For national zone resources behind the Country Codes assigned
114 to and shared by Groups of Countries, the administrative entity
115 identified by the Countries of the Group provides the E.164
116 assignment information, to DNS administrators, for performing
117 the administrative function. Note that the creation of this
118 category is dependent upon the approval of draft Recommendation
119 E.164.3.
120
121 o Each of the administrative entities responsible for the
122 administration of resources within the zones (as identified above)
123 is individually and separately responsible for ensuring that DNS
124 administrators are aware of appropriate changes to their resources
125 once they have agreed to their input into the DNS.
126
127 o Assigned geographic E.164 resources, for all zones, not authorized
128 for input by the appropriate administrative entity will not be
129 entered into the DNS under any circumstance. For example, if the
130 ENUM service is not approved for use in a country, by the
131 appropriate ITU Member States, the E.164 numbers of that country
132 will not be input to the DNS.
133
134 o With regard to Number Portability, it was agreed that WP1/2 would
135 further study this issue, in the context of ENUM. However, it is
136 currently understood that this study and its result will not
137 impact the IETF and its work.
138
139 o The study being undertaken within WP1/2 (referred to above) will
140 also attempt to identify options and provide guidance to assist
141 those entities charged with the task of providing the
142 administrative information to DNS administrators.
143
144 o All administrative entities, including DNS administrators, will
145 adhere to all the applicable tenets of all pertinent ITU
146 Recommendations, e.g., E.164, E.164.1, E.190, and E.195, with
147 regard to the inclusion of the E.164 resource information in the
148 DNS.
149
150 o The ITU, IETF, and IAB will jointly cooperate fully to ensure that
151 the agreed administrative procedures to accommodate the above
152 understandings, and any other mutually agreed appropriate future
153 understandings, will be implemented and adhered to on an ongoing
154 basis. The ITU may request the consultation of the WP1/2 experts
155 as necessary and as prescribed in Resolution 20.
156
157
158
159
160
161
162
163
164 <span class="grey">Blane Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc3026">RFC 3026</a> Liaison to IETF/ISOC on ENUM January 2001</span>
167
168
169 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Additional items below are from Q.10/2 Rapporteur Group (Service</span>
170 <span class="h2"> Issues)</span>
171
172 o The issues surrounding number portability are to be addressed in
173 the draft supplement to Recommendation E.370
174
175 o This issue surrounding freephone service was expanded to include
176 other global services (i.e., International Premium Rate Service
177 and International Shared Cost Service). Preliminary findings
178 would indicate that routing the call to the appropriate
179 destination will depend on successfully receiving information
180 about the geographic point of origination (e.g., calling
181 "telephone Number"). A proxy server would process such
182 information and either redirect or forward the call (based on the
183 proxy owner's decision) on to the appropriate destination.
184
185 o The issue surrounding selection of the IP gateway within a PSTN-
186 to-IP call flow may depend on options that may be available to
187 telephony carriers in such selection.
188
189 The WP1/2 collaborators thank their IETF counterparts who attended
190 this meeting and assisted in the resolution of these issues.
191
192 Any questions regarding the contents of this liaison should be
193 referred to the WP1/2 Chairman Roy Blane at [email protected].
194
195 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations (added by the IESG)</span>
196
197 The ENUM solution uses the Domain Name System (DNS) for storage of
198 information. Delegation and distributed administration is done
199 according to DNS routines. The E.164 numbers are though distributed
200 according to a different algorithm than domain names.
201
202 This Liaison Statement describes how mapping E.164 number
203 administration and DNS administration can work together, and how
204 further discussions are delegated to each administrative body for the
205 country codes in E.164 space.
206
207 If delegation and mapping is not done carefully between E.164 and DNS
208 there is a risk of "napping" of E.164 numbers when they are stored in
209 DNS. It is also important that the DNS strictly hierarchal system is
210 preserved (see <a href="./rfc2826">RFC 2826</a> [<a href="#ref-1" title="&quot;IAB Technical Comment on the Unique DNS Root&quot;">1</a>]).
211
212 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
213
214 [<a id="ref-1">1</a>] IAB, "IAB Technical Comment on the Unique DNS Root", <a href="./rfc2826">RFC 2826</a>,
215 May 2000.
216
217
218
219
220 <span class="grey">Blane Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc3026">RFC 3026</a> Liaison to IETF/ISOC on ENUM January 2001</span>
223
224
225 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Author's Address</span>
226
227 Roy Blane
228 ITU
229
230 EMail: [email protected]
231 URI: <a href="http://www.itu.int">http://www.itu.int</a>
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 <span class="grey">Blane Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc3026">RFC 3026</a> Liaison to IETF/ISOC on ENUM January 2001</span>
279
280
281 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Full Copyright Statement</span>
282
283 Copyright (C) The Internet Society (2001). All Rights Reserved.
284
285 This document and translations of it may be copied and furnished to
286 others, and derivative works that comment on or otherwise explain it
287 or assist in its implementation may be prepared, copied, published
288 and distributed, in whole or in part, without restriction of any
289 kind, provided that the above copyright notice and this paragraph are
290 included on all such copies and derivative works. However, this
291 document itself may not be modified in any way, such as by removing
292 the copyright notice or references to the Internet Society or other
293 Internet organizations, except as needed for the purpose of
294 developing Internet standards in which case the procedures for
295 copyrights defined in the Internet Standards process must be
296 followed, or as required to translate it into languages other than
297 English.
298
299 The limited permissions granted above are perpetual and will not be
300 revoked by the Internet Society or its successors or assigns.
301
302 This document and the information contained herein is provided on an
303 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
304 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
305 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
306 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
307 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
308
309 Acknowledgement
310
311 Funding for the RFC Editor function is currently provided by the
312 Internet Society.
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332 Blane Informational [Page 6]
333 </pre>