Debian Codegraph @

rfc2050.html

raw
1 <pre>Network Working Group K. Hubbard
2 Request for Comments: 2050 M. Kosters
3 Obsoletes: <a href="./rfc1466">1466</a> InterNIC
4 BCP: 12 D. Conrad
5 Category: Best Current Practice APNIC
6 D. Karrenberg
7 RIPE
8 J. Postel
9 ISI
10 November 1996
11
12
13 <span class="h1">INTERNET REGISTRY IP ALLOCATION GUIDELINES</span>
14
15 Status of this Memo
16
17 This document specifies an Internet Best Current Practices for the
18 Internet Community, and requests discussion and suggestions for
19 improvements. Distribution of this memo is unlimited.
20
21 IESG Note:
22
23 By approving this document as a Best Current Practice,the IESG
24 asserts its belief that this policy described herein is an accurate
25 representation of the current practice of the IP address registries
26 with respect to address assignment. This does not constitute
27 endorsement or recommendation of this policy by the IESG. The IESG
28 will reevaluate its approval of this document in December 1997 taking
29 into consideration the results of the discussions that will be take
30 place in the IRE Working Group between now and then.
31
32 Abstract
33
34 This document describes the registry system for the distribution of
35 globally unique Internet address space and registry operations.
36 Particularly this document describes the rules and guidelines
37 governing the distribution of this address space.
38
39 This document describes the IP assignment policies currently used by
40 the Regional Registries to implement the guidelines developed by the
41 IANA. The guidelines and these policies are subject to revision at
42 the direction of the IANA. The registry working group (IRE WG) will
43 be discussing these issues and may provide advice to the IANA about
44 possible revisions.
45
46 This document replaces <a href="./rfc1466">RFC 1466</a>, with all the guidelines and
47 procedures updated and modified in the light of experience.
48
49
50
51
52 <span class="grey">Hubbard, et. al. Best Current Practice [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
55
56
57 This document does not describe private Internet address space and
58 multicast address space. It also does not describe regional and
59 local refinements of the global rules and guidelines.
60
61 This document can be considered the base set of operational
62 guidelines in use by all registries. Additional guidelines may be
63 imposed by a particular registry as appropriate.
64
65 Table of Contents
66
67 <a href="#section-1">1</a>. Introduction.......................................<a href="#page-2">2</a>
68 <a href="#section-2">2</a>. Allocation Framework...............................<a href="#page-4">4</a>
69 <a href="#section-2.1">2.1</a> Guidelines for Internet Service Providers.........<a href="#page-4">4</a>
70 <a href="#section-2.2">2.2</a> Submission of Reassignment Information............<a href="#page-6">6</a>
71 <a href="#section-3">3</a>. Assignment Framework..............................<a href="#page-7">7</a>
72 <a href="#section-3.1">3.1</a> Common Registry Requirements......................<a href="#page-7">7</a>
73 <a href="#section-3.2">3.2</a> Network Engineering Plans.........................<a href="#page-8">8</a>
74 <a href="#section-3.3">3.3</a> Previous Assignment History.......................<a href="#page-9">9</a>
75 <a href="#section-3.4">3.4</a> Network Deployment Plans..........................<a href="#page-9">9</a>
76 <a href="#section-3.5">3.5</a> Organization Information..........................<a href="#page-9">9</a>
77 <a href="#section-3.6">3.6</a> Expected Utilization Rate.........................<a href="#page-10">10</a>
78 <a href="#section-4">4</a>. Operational Guidelines for Registries.............<a href="#page-10">10</a>
79 <a href="#section-5">5</a>. In-Addr.Arpa Domain Maintenance...................<a href="#page-11">11</a>
80 <a href="#section-6">6</a>. Right to Appeal...................................<a href="#page-11">11</a>
81 <a href="#section-7">7</a>. References........................................<a href="#page-12">12</a>
82 <a href="#section-8">8</a>. Security Considerations...........................<a href="#page-12">12</a>
83 <a href="#section-9">9</a>. Authors' Addresses................................<a href="#page-13">13</a>
84
85 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
86
87 The addressing constraints described in this document are largely the
88 result of the interaction of existing router technology, address
89 assignment, and architectural history. After extensive review and
90 discussion, the authors of this document, the IETF working group that
91 reviewed it and the IESG have concluded that there are no other
92 currently deployable technologies available to overcome these
93 limitations. In the event that routing or router technology develops
94 to the point that adequate routing aggregation can be achieved by
95 other means or that routers can deal with larger routing and more
96 dynamic tables, it may be appropriate to review these constraints.
97
98 Internet address space is distributed according to the following
99 three goals:
100
101 1) Conservation: Fair distribution of globally unique Internet address
102 space according to the operational needs of the end-users and Internet
103 Service Providers operating networks using this address space.
104 Prevention of stockpiling in order to maximize the lifetime of the
105
106
107
108 <span class="grey">Hubbard, et. al. Best Current Practice [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
111
112
113 Internet address space.
114
115 2) Routability: Distribution of globally unique Internet addresses
116 in a hierarchical manner, permitting the routing scalability of
117 the addresses. This scalability is necessary to ensure proper
118 operation of Internet routing, although it must be stressed that
119 routability is in no way guaranteed with the allocation or
120 assignment of IPv4 addresses.
121
122 3) Registration: Provision of a public registry documenting address
123 space allocation and assignment. This is necessary to ensure
124 uniqueness and to provide information for Internet trouble shooting
125 at all levels.
126
127 It is in the interest of the Internet community as a whole that the
128 above goals be pursued. However it should be noted that
129 "Conservation" and "Routability" are often conflicting goals. All
130 the above goals may sometimes be in conflict with the interests of
131 individual end-users or Internet service providers. Careful analysis
132 and judgement is necessary in each individual case to find an
133 appropriate compromise.
134
135 The Internet Registry system
136
137 In order to achieve the above goals the Internet Registry (IR)
138 hierarchy was established.
139
140 The Internet Registry hierarchy consists of the following levels
141 of hierarchy as seen from the top down: IANA, Regional IRs, Local
142 IRs.
143
144 IANA
145
146 The Internet Assigned Numbers Authority has authority over all
147 number spaces used in the Internet. This includes Internet
148 Address Space. IANA allocates parts of the Internet address space
149 to regional IRs according to its established needs.
150
151 Regional IRs
152
153 Regional IRs operate in large geopolitical regions such as
154 continents. Currently there are three regional IRs established;
155 InterNIC serving North America, RIPE NCC serving Europe, and AP-
156 NIC serving the Asian Pacific region. Since this does not cover
157 all areas, regional IRs also serve areas around its core service
158 areas. It is expected that the number of regional IRs will remain
159 relatively small. Service areas will be of continental
160 dimensions.
161
162
163
164 <span class="grey">Hubbard, et. al. Best Current Practice [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
167
168
169 Regional IRs are established under the authority of the IANA.
170 This requires consensus within the Internet community of the
171 region. A consensus of Internet Service Providers in that region
172 may be necessary to fulfill that role.
173
174 The specific duties of the regional IRs include coordination and
175 representation of all local IRs in its respective regions.
176
177 Local IRs
178
179 Local IRs are established under the authority of the regional IR
180 and IANA. These local registries have the same role and
181 responsibility as the regional registries within its designated
182 geographical areas. These areas are usually of national
183 dimensions.
184
185 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Allocation Framework</span>
186
187 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Guidelines for Internet Service Providers (ISPs)</span>
188
189 This document makes a distinction between the allocation of IP
190 addresses and the assignment of IP addresses. Addresses are
191 allocated to ISPs by regional registries to assign to its customer
192 base.
193
194 ISPs who exchange routing information with other ISPs at multiple
195 locations and operate without default routing may request space
196 directly from the regional registry in its geographical area. ISPs
197 with no designated regional registry may contact any regional
198 registry and the regional registry may either handle the request or
199 refer the request to an appropriate registry.
200
201 To facilitate hierarchical addressing, implemented using Classless
202 Inter-Domain Routing (CIDR), all other ISPs should request address
203 space directly from its upstream provider. ISPs only request address
204 space directly from regional registries if their immediate
205 requirement, when satisfied with a contiguous block allocation, has a
206 reasonable probability of being routable on the Internet, and they
207 meet one or more of the following conditions.
208
209 a) the ISP is directly connected to a major routing exchange
210 (for purposes of this document, a major routing exchange
211 is defined as a neutral layer 2 exchange point connecting
212 four or more unrelated ISPs.)
213
214 b) the ISP is multi-homed, that is, it has more than one
215 simultaneous connection to the global Internet and no
216 connection is favored over the other
217
218
219
220 <span class="grey">Hubbard, et. al. Best Current Practice [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
223
224
225 Note that addresses issued directly from the IRs (non-provider
226 based), are the least likely to be routable across the Internet.
227
228 The following are the IP allocation guidelines for ISPs:
229
230
231 1. CIDR addresses are allocated to ISPs in blocks. It is
232 recommended that those blocks remain intact. Fragmentation of
233 CIDR blocks is discouraged. More specifically, ISPs are
234 encouraged to treat address assignments as loans for the
235 duration of the connectivity provision. At the termination
236 of the Internet connectivity contract, e.g., the customer
237 moves to another service provider, it is recommended the
238 customer return the network addresses currently in use and
239 renumber into the new provider's address space. The ISP
240 should allow sufficient time for the renumbering process to be
241 completed before the IP addresses are reused.
242
243 2. To ensure efficient implementation and use of Classless
244 Inter-Domain Routing (IDR), the Regional Registries issue
245 address space on appropriate "CIDR-supported" bit boundaries.
246
247 3. ISPs are required to utilize address space in an efficient
248 manner. To this end, ISPs should have documented
249 justification available for each assignment. The regional
250 registry may, at any time, ask for this information. If the
251 information is not available, future allocations may be impacted.
252 In extreme cases, existing loans may be impacted.
253
254 4. IP addresses are allocated to ISPs using a slow-start
255 procedure. New ISPs will receive a minimal amount based
256 on immediate requirement. Thereafter, allocated blocks may be
257 increased based on utilization verification supplied to the
258 regional registry. The parent registries are responsible for
259 determining appropriate initial and subsequent allocations.
260 Additional address allocations will provide enough address space
261 to enable the ISP to assign addresses for three months
262 without requesting additional address space from its parent
263 registry. Please note that projected customer base has little
264 impact on the address allocations made by the parent registries.
265 Initial allocation will not be based on any current or future
266 routing restrictions but on demonstrated requirements.
267
268 5. Due to the requirement to increase the utilization efficiency
269 of IPv4 address space, all assignments are made with the
270 assumption that sites make use of variable length subnet mask
271 (VLSM) and classless technologies within their network. Any
272 request for address space based on the use of classfull
273
274
275
276 <span class="grey">Hubbard, et. al. Best Current Practice [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
279
280
281 assumptions will require a detailed justification. The use of
282 classfull technologies for the purposes of administrative
283 convenience is generally insupportable due to the limited
284 availability of free IPv4 address space.
285
286 6. Regional registries may set a maximum limit on assignment sizes
287 such that a second opinion of the regional registry is required.
288
289 7. Due to constraints on the available free pool of IPv4 address
290 space, the use of static IP address assignments (e.g., one
291 address per customer) for dial-up users is strongly discouraged.
292 While it is understood that the use of static addressing may
293 ease some aspects of administration, the current rate of
294 consumption of the remaining unassigned IPv4 address space does
295 not permit the assignment of addresses for administrative ease.
296 Organizations considering the use of static IP address assignment
297 are expected to investigate and implement dynamic assignment
298 technologies whenever possible.
299
300 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Submission of Reassignment Information</span>
301
302 It is imperative that reassignment information be submitted in a
303 prompt and efficient manner to facilitate database maintenance and
304 ensure database integrity. Therefore, assignment information must be
305 submitted to the regional registry immediately upon making the
306 assignment. The following reasons necessitate transmission of the
307 reassignment information:
308
309 a) to provide operational staff with information on who is using
310 the network number and to provide a contact in case of
311 operational/security problems,
312
313 b) to ensure that a provider has exhausted a majority of its
314 current CIDR allocation, thereby justifying an additional
315 allocation,
316
317 c) to assist in IP allocation studies.
318
319 Procedures for submitting the reassignment information will be
320 determined by each regional registry based on its unique
321 requirements.
322
323 All sub-registries (ISPs, Local registries, etc.) must register with
324 their respective regional registry to receive information regarding
325 reassignment guidelines. No additional CIDR blocks will be allocated
326 by the regional registry or upstream providers until approximately
327 80% of all reassignment information has been submitted.
328
329
330
331
332 <span class="grey">Hubbard, et. al. Best Current Practice [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
335
336
337 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Assignment Framework</span>
338
339 An assignment is the delegation of authority over a block of IP
340 addresses to an end enterprise. The end enterprise will use
341 addresses from an assignment internally only; it will not sub-
342 delegate those addresses. This section discusses some of the issues
343 involved in assignments and the framework behind the assignment of
344 addresses.
345
346 In order for the Internet to scale using existing technologies, use
347 of regional registry services should be limited to the assignment of
348 IP addresses for organizations meeting one or more of the following
349 conditions:
350
351 a) the organization has no intention of connecting to
352 the Internet-either now or in the future-but it still
353 requires a globally unique IP address. The organization
354 should consider using reserved addresses from <a href="./rfc1918">RFC1918</a>.
355 If it is determined this is not possible, they can be
356 issued unique (if not Internet routable) IP addresses.
357
358 b) the organization is multi-homed with no favored connection.
359
360 c) the organization's actual requirement for IP space is
361 very large, for example, the network prefix required to
362 cover the request is of length /18 or shorter.
363
364 All other requestors should contact its ISP for address space or
365 utilize the addresses reserved for non-connected networks described
366 in <a href="./rfc1918">RFC1918</a> until an Internet connection is established. Note that
367 addresses issued directly from the IRs,(non-provider based), are the
368 least likely to be routable across the Internet.
369
370 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Common Registry Requirements</span>
371
372 Because the number of available IP addresses on the Internet is
373 limited, the utilization rate of address space will be a key factor
374 in network number assignment. Therefore, in the best interest of the
375 Internet as a whole, specific guidelines have been created to govern
376 the assignment of addresses based on utilization rates.
377
378 Although topological issues may make exceptions necessary, the basic
379 criteria that should be met to receive network numbers are listed
380 below:
381
382 25% immediate utilization rate
383 50% utilization rate within 1 year
384
385
386
387
388 <span class="grey">Hubbard, et. al. Best Current Practice [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
391
392
393 The utilization rate above is to be used as a guideline, there may be
394 be occasions when the 1 year rate does not fall exactly in this
395 range. Organizations must exhibit a high confidence level in its 1
396 year utilization rate and supply documentation to justify the level
397 of confidence.
398
399 Organizations will be assigned address space based on immediate
400 utilization plus 1 year projected utilization. A prefix longer than
401 /24 may be issued if deemed appropriate. Organizations with less
402 than 128 hosts will not be issued an IP address directly from the
403 IRs. Organizations may be issued a prefix longer than /24 if the
404 organization can provide documentation from a registry recognized ISP
405 indicating the ISP will accept the long prefix for injection into the
406 global routing system.
407
408 Exceptions to the criteria will not be made based on insufficient
409 equipment without additional detailed justification. Organizations
410 should implement variable length subnet mask (VLSM) internally to
411 maximize the effective utilization of address space. Address
412 assignments will be made under the assumption that VLSM is or will be
413 implemented.
414
415 IP addresses are valid as long as the criteria continues to be met.
416 The IANA reserves the right to invalidate any IP assignments once it
417 is determined the the requirement for the address space no longer
418 exists. In the event of address invalidation, reasonable efforts
419 will be made by the appropriate registry to inform the organization
420 that the addresses have been returned to the free pool of IPv4
421 address space.
422
423 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Network Engineering Plans</span>
424
425 Before a registry makes an assignment, it must examine each address
426 space request in terms of the requesting organization's networking
427 plans. These plans should be documented, and the following
428 information should be included:
429
430 1. subnetting plans, including subnet masks and number of
431 hosts on each subnet for at least one year
432
433 2. a description of the network topology
434
435 3. a description of the network routing plans, including the
436 routing protocols to be used as well as any limitations.
437
438
439
440
441
442
443
444 <span class="grey">Hubbard, et. al. Best Current Practice [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
447
448
449 The subnetting plans should include:
450
451 a) a tabular listing of all subnets on the network
452
453 b) its associated subnet masks
454
455 c) the estimated number of hosts
456
457 d) a brief descriptive remark regarding the subnet.
458
459 If subnetting is not being used, an explanation why it cannot be
460 implemented is required. Care must be taken to ensure that the host
461 and subnet estimates correspond to realistic requirements and are not
462 based on administrative convenience.
463
464 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Previous Assignment History</span>
465
466 To promote increased usage of address space, the registries will
467 require an accounting of address space previously assigned to the
468 enterprise, if any. In the context of address space allocation, an
469 "enterprise" consists of all divisions and/or subsidiaries falling
470 under a common parent organization. The previous assignment history
471 should include all network numbers assigned to the organization, plus
472 the network masks for those networks and the number of hosts on each
473 (sub-)network. Sufficient corroborating evidence should be provided
474 to allow the assigning registry to be confident that the network
475 descriptions provided are accurate. Routing table efficiency will be
476 taken into account by the regional registries and each request will
477 be handled on a case by case basis.
478
479 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Network Deployment Plans</span>
480
481 In order to assign an appropriate amount of space in the required
482 time frame, a registry may request deployment plans for a network.
483 Deployment plans should include the number of hosts to be deployed
484 per time period, expected network growth during that time period, and
485 changes in the network topology that describe the growth.
486
487 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> Organization Information</span>
488
489 A registry may request that an organization furnish a published
490 description verifying that the organization is what it claims to be.
491 This information can consist of brochures, documents of
492 incorporation, or similar published material.
493
494
495
496
497
498
499
500 <span class="grey">Hubbard, et. al. Best Current Practice [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
503
504
505 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a> Expected Utilization Rate</span>
506
507 As stated in the foregoing text, one of the key factors in
508 determining how much address space is appropriate for an organization
509 is the expected utilization rate of the network. The expected
510 utilization rate is the number of hosts connected to the network
511 divided by the total number of hosts possible on the network. In
512 addition, the estimated number of hosts should be projected over a
513 reasonable time frame, i.e., one in which the requesting enterprise
514 has a high level of confidence. The minimal utilization rate is set
515 by the IANA and may be changed at any time. New utilization rates
516 may be enforced by the regional registries prior to updating the
517 written policy.
518
519 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Operational Guidelines For Registries</span>
520
521 1. Regional Registries provide registration services as its
522 primary function. Therefore, regional registries may charge some
523 fee for services rendered, generally in relation to the cost of
524 providing those services.
525
526 2. Regardless of the source of its address space, sub-registries
527 (Local IRs, ISPs, etc.) must adhere to the guidelines of its
528 regional registry. In turn, it must also ensure that its
529 customers follow those guidelines.
530
531 3. To maximize the effective use of address space, IP addresses need
532 to be assigned/allocated in classless blocks. With this in mind,
533 assignments will not be made in Class Cs or Bs but by prefix
534 length. Consequently, an organization that would have been
535 assigned a Class B in the past will now be assigned a /16 prefix,
536 regardless of the actual address class.
537
538 4. All IP address requests are subject to audit and verification
539 by any means deemed appropriate by the regional registry.
540 If any assignment is found to be based on false information,
541 the registry may invalidate the request and return the
542 assigned addresses back to the pool of free addresses for
543 later assignment.
544
545 5. Due to technical and implementation constraints on the Internet
546 routing system and the possibility of routing overload, major
547 transit providers may need to impose certain restrictions to
548 reduce the number of globally advertised routes. This may
549 include setting limits on the size of CIDR prefixes added to
550 the routing tables, filtering of non-aggregated routes, etc.
551 Therefore, addresses obtained directly from regional registry
552 (provider-independent, also known as portable) are not
553
554
555
556 <span class="grey">Hubbard, et. al. Best Current Practice [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
559
560
561 guaranteed routable on the Internet.
562
563 6. Information provided to request address space is often considered
564 sensitive by the requesting organization. The assigning
565 registry must treat as confidential any and all information
566 that the requesting organization specifically indicates as
567 sensitive. When a requesting organization does not have
568 assurance of privacy, the parent of the assigning registry may
569 be required to do the assignment. In such cases, the parent
570 registry will provide the assigning registry with information
571 regarding the appropriate amount of address space to allocate.
572
573 7. The transfer of IP addresses from one party to another must be
574 approved by the regional registries. The party trying to obtain
575 the IP address must meet the same criteria as if they were
576 requesting an IP address directly from the IR.
577
578 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. In-ADDR.ARPA Domain Maintenance</span>
579
580 The regional registries will be responsible for maintaining IN-
581 ADDR.ARPA records only on the parent blocks of IP addresses issued
582 directly to the ISPs or those CIDR blocks of less than /16. Local
583 IRs/ISPs with a prefix length of /16 or shorter will be responsible
584 for maintaining all IN-ADDR.ARPA resource records for its customers.
585
586 IN-ADDR.ARPA resource records for networks not associated with a
587 specific provider will continue to be maintained by the regional
588 registry.
589
590 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Right to Appeal</span>
591
592 If an organization feels that the registry that assigned its address
593 has not performed its task in the requisite manner, the organization
594 has the right of appeal to the parent registry.
595
596 In such cases, the assigning registry shall make available all
597 relevant documentation to the parent registry, and the decision of
598 the parent registry shall be considered final (barring additional
599 appeals to the parent registry's parent). If necessary, after
600 exhausting all other avenues, the appeal may be forwarded to IANA for
601 a final decision. Each registry must, as part of their policy,
602 document and specify how to appeal a registry assignment decision.
603
604
605
606
607
608
609
610
611
612 <span class="grey">Hubbard, et. al. Best Current Practice [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
615
616
617 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
618
619 [<a id="ref-RFC 1519">RFC 1519</a>] Fuller, V., Li, T., Yu, J., and K. Varadhan,
620 "Classless Inter- Domain Routing (CIDR): an Address
621 Assignment and Aggregation Strategy", September 1993.
622
623 [<a id="ref-RFC 1518">RFC 1518</a>] Rekhter, Y., and T. Li, "An Architecture for IP
624 Address Allocation with CIDR", September 1993.
625
626 [<a id="ref-RFC 1918">RFC 1918</a>] Rekhter, Y., Moskowitz, B., Karrenberg, D., and
627 G. de Groot, "Address Allocation for Private Internets",
628 February 1996.
629
630 [<a id="ref-RFC 1814">RFC 1814</a>] Gerich, E., "Unique Addresses are Good", June 1995.
631
632 [<a id="ref-RFC 1900">RFC 1900</a>] Carpenter, B., and Y. Rekhter, "Renumbering Needs Work",
633 February 1996.
634
635 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
636
637 Security issues are not discussed in this memo.
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Hubbard, et. al. Best Current Practice [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2050">RFC 2050</a> Internet Registry IP Allocation Guidelines November 1996</span>
671
672
673 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Authors' Addresses</span>
674
675 Kim Hubbard
676 InterNIC Registration Services
677 c/o Network Solutions
678 505 Huntmar Park Drive
679 Herndon, VA 22070
680
681 Phone: (703) 742-4870
682 EMail: [email protected]
683
684 Mark Kosters
685 InterNIC Registration Services
686 c/o Network Solutions
687 505 Huntmar Park Drive
688 Herndon, VA 22070
689
690 Phone: (703) 742-4795
691 EMail: [email protected]
692
693 David Conrad
694 Asia Pacific Network Information Center
695 c/o United Nations University
696 53-70 Jingumae 5-chome,
697 Shibuya-ku, Tokyo 150
698 JP
699
700 Phone: +81-3-5467-7014
701 EMail: [email protected]
702
703 Daniel Karrenberg
704 RIPE NCC
705 Kruislaan 409
706 SJ Amsterdam NL-1098
707 NL
708
709 Phone: +31 20 592 5065
710 EMail: [email protected]
711
712 Jon Postel
713 USC/Information Sciences Institute
714 4676 Admiralty Way
715 Marina del Rey, CA 90292
716
717 Phone: 310-822-1511
718 EMail: [email protected]
719
720
721
722
723
724 Hubbard, et. al. Best Current Practice [Page 13]
725 </pre>