You are here: Home > Publications > RIPE Document Store > RIPE NCC Internet Numbers Registration Procedures

Changes to RIPE NCC Internet Numbers Registration Procedures

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-072: ripe-638: This document describes the policies for the assignment of globally unique Autonomous System (AS) Numbers within the RIPE NCC Internet Numbers Registration Procedures service region. These policies are developed by the RIPE Community following the RIPE Policy Development Process.

delete:  delete:  This documents obsoletes ripe-65, version 0.6 of this document delete:  delete:   delete:   insert: <h3>

insert: `` Abstract delete: ` ` delete: ` ` delete: ` ` insert: `` insert: `</h3>`

insert: 

This document describes the procedures policies for the reassignment of IP delete:   network numbers from blocks obtained from the RIPE Network Coordination delete:   Centre. It deals with items as providing information for the RIPE delete:   database, as well as reassignment of IP addresses in light of delete:   the "Supernetting" proposal, as documented in RFC 1338, assignment of globally unique Autonomous System (AS) Numbers within the RIPE NCC service region. These policies are developed by Vince Fuller delete:   et al. delete:   delete:   delete:   Introduction delete:   delete:   delete:   Since May 1st 1992, the RIPE Network Coordination Centre (NCC) the RIPE Community following the RIPE Policy Development Process. insert: 

insert: 

insert: 

insert: <h3>

insert: `` Contents insert: `` insert: `</h3>`

insert: 

1.0 insert: <a class="anchor-link" title="" href="#Definition" target="_self"> Definition insert: </a> insert: 

insert: 

2.0 insert: <a class="anchor-link" title="" href="#AssignmentCriteria" target="_self"> Assignment Criteria insert: </a> insert: 

insert: 

3.0 insert: <a class="anchor-link" title="" href="#Returning" target="_self"> Returning AS Numbers insert: </a> insert: 

insert: 

4.0 insert: <a class="anchor-link" title="" href="#Transferring" target="_self"> Transferring AS Numbers insert: </a> insert: 

insert: 

5.0 insert: <a class="anchor-link" title="" href="#ASnumbers" target="_self"> 32-bit AS Numbers insert: </a> insert: 

insert: 

6.0 insert: <a class="anchor-link" title="" href="#Registration" target="_self"> Registration insert: </a> insert: 

insert: 

7.0 insert: <a class="anchor-link" title="" href="#References" target="_self"> References insert: </a> insert: 

insert: 

8.0 insert: <a class="anchor-link" title="" href="#Attribution" target="_self"> Attribution insert: </a> insert: 

insert: 

insert: 

insert: <h3>

insert: `<a name="Definition">` insert: `</a>` 1.0 Definition insert: `</h3>`

insert: 

An Autonomous System (AS) is delete:   acting as a delegated registry for a group of IP networks numbers to NICs and NOCs delete:   in Europe. It run by one or more network operators with a single clearly defined routing policy. When exchanging exterior routing information, each AS is RIPE NCC identified by a unique number. Exterior routing protocols such as BGP, described in insert: <a href="ftp://ftp.ripe.net/rfc/rfc1771.txt"> RFC1771 insert: </a> , "A Border Gateway Protocol 4 (BGP-4)", are used to exchange routing information between Autonomous Systems. An AS will normally use some interior gateway protocol to exchange routing information on its internal networks. insert: 

insert: 

insert: 

insert: <h3>

insert: `<a name="AssignmentCriteria">` insert: `</a>` 2.0 Assignment Criteria insert: `</h3>`

insert: 

In order to help decrease global routing complexity, a new AS Number should be used only if a new external routing policy not to give out is required, see insert: <a href="ftp://ftp.ripe.net/rfc/rfc1930.txt"> RFC1930 insert: </a> . insert: 

insert: 

A network numbers to delete:   individual organisations, who must be multihomed in order to qualify for an AS Number. insert: 

insert: 

When requesting an AS Number the routing policy of the Autonomous System must be provided. The new unique routing policy should refer in turn, to their IP network delete:   service provider. delete:   delete:   The mission of the RIPE NCC is to give network numbers to the various delete:   service providers and NICs. The NICs and NOCs be defined in RPSL language, as used in the RIPE Database. insert: 

insert: 

The RIPE NCC will assign the AS Number directly to the End User upon a request properly submitted to the RIPE NCC either directly or through a sponsoring LIR. AS Number assignments are subject to the policies described in the RIPE NCC document entitled “ insert: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> ”. insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="Returning">` insert: `</a>` 3.0 Returning AS Numbers insert: `` insert: `</h3>`

insert: 

If an organisation no longer uses the AS Number, it should be returned to the public pool of AS Numbers. The RIPE NCC can then reassign the delete:   actual IP network numbers to AS Number to another organisation. insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="Transferring">` insert: `</a>` 4.0 Transferring AS Numbers insert: `` insert: `</h3>`

insert: 

Any holder of Autonomous System (AS) Numbers is allowed to re-assign AS Numbers that were previously assigned to them by the RIPE NCC or otherwise through the Regional Internet Registry System. insert: 

insert: 

AS Numbers may only be re-assigned in accordance with the RIPE Policy, “ insert: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> ”. insert: 

insert: 

Re-assignments must be reflected in the RIPE Database. This re-assignment can either be on a permanent or non-permanent basis. insert: 

insert: 

The RIPE NCC will record the change of AS Numbers after the transfer. insert: 

insert: 

The RIPE NCC will publish a separate list of all AS Numbers transferred under this section. The publication shall occur on monthly basis or more frequently if the RIPE NCC so chooses. insert: 

insert: 

The list will contain information about approved and non-approved transfers. insert: 

insert: 

The following information will be published for approved transfers: insert: 

insert: <ul>

insert: <li>

The name of the transferring party insert: </li>

insert: <li>

The name(s) of the receiving party or parties insert: </li>

insert: <li>

The transferred AS Number insert: </li>

insert: <li>

The date each AS Number was transferred insert: </li>

insert: </ul>

insert: 

Non-approved transfers will be published in aggregate statistics. In the statistics the following information will be published: insert: 

insert: <ul>

insert: <li>

The Number of requested transfers not approved after the RIPE NCC's evaluation insert: </li>

insert: <li>

The sum of the AS Numbers included in the requested transfers insert: </li>

insert: </ul>

insert: 

Neither the AS Numbers nor the organisations requesting IP network delete:   numbers. delete:   delete:   delete:   Class B Network involved will be identified in these statistics. insert: 

insert: 

Please note that the transferring party always remains responsible for the AS Number Allocation Procedure delete:   delete:   Service providers it receives from the RIPE NCC until the transfer of the resource to another party is completed or if the resource is returned. insert: 

insert: 

Re-assigned AS Numbers are no different from AS Numbers assigned directly by the RIPE NCC and so must be used by the receiving party according to the policies described in this document. insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="ASnumbers">` insert: `</a>` 5.0 32-bit AS Numbers insert: `` insert: `</h3>`

insert: 

The RIPE NCC assigns 32-bit AS Numbers according to the following timeline: insert: 

insert: <ul>

insert: <li>

From 1 January 2007 the RIPE NCC will process applications that specifically request 32-bit only AS Numbers (AS Numbers that can request Class B network numbers on a one-by-one delete:   basis from the RIPE NCC. Because class B address space is a critical delete:   resource, a not be represented with 16 bits) and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a class B network number must be accompanied 32-bit only AS Number, the RIPE NCC will assign a 16-bit AS Number. insert: </li>

insert: </ul>

insert: <ul>

insert: <li>

From 1 January 2009 the RIPE NCC will process applications that specifically request 16-bit AS Numbers and assign such AS Numbers as requested by delete:   a justification in terms of the requesting organisation's size, current delete:   network the applicant. In the absence of any specific request for a 16-bit AS Number, the RIPE NCC will assign a 32-bit only AS Number. insert: </li>

insert: </ul>

insert: <ul>

insert: <li>

From 1 January 2010 the RIPE NCC will cease to make any distinction between 16-bit AS Numbers and expected network growth. The requestor should also make delete:   clear why they cannot use a block of class C network numbers to achieve delete:   their goals. The RIPE NCC will review requests using the same standards delete:   as any other 32-bit only AS Numbers, and it will operate AS Number assignments from an undifferentiated 32-bit AS Number allocation pool. insert: </li>

insert: </ul>

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="Registration">` insert: `</a>` 6.0 Registration insert: `` insert: `</h3>`

insert: 

The RIPE NCC will register the resources issued in the RIPE Database. insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="References">` insert: `</a>` 7.0 References insert: `` insert: `</h3>`

insert: 

[RFC1771] "A Border Gateway Protocol 4 (BGP-4)" insert: <a href="http://www.ietf.org/rfc/rfc1771.txt"> http://www.ietf.org/rfc/rfc1771.txt insert: </a> insert: 

insert: 

[RFC1930] " Guidelines for creation, selection, and registration of an Autonomous System (AS)" insert: <a href="http://www.ietf.org/rfc/rfc1930.txt"> http://www.ietf.org/rfc/rfc1930.txt insert: </a> insert: 

insert: 

[RFC2026] "The Internet Registry, particularly the US NIC. delete:   delete:   delete:   Class C Allocation Procedures delete:   delete:   NICs and NOCs accepting a block of class C numbers agree to adhere to delete:   the following procedures: delete:   delete:   A) The RIPE NCC will assign complete class C blocks to individual NICs delete:   and NOCs. They can be requested from <[email protected]>. delete:   delete:   B) In order to prevent implementation problems, network numbers ending delete:   with 0 or 255 should NOT be reassigned. delete:   delete:   C) Full information about reassigned network numbers must be reported delete:   back to the RIPE NCC in full RIPE database format (ref ripe-13). delete:   The complete entries should be sent immediately after reassignment to delete:   <[email protected]>. delete:   The RIPE NCC is ready to accept block entries for the RIPE database. delete:   For block syntax, please contact the RIPE NCC. delete:   delete:   D) Reassignment of class C network numbers should be done in a manner delete:   that facilitates Supernetting (see next section). delete:   delete:   E) Requests for network numbers should be reasonable. All NICs and NOCs delete:   should prevent stockpiling of network numbers. delete:   delete:   F) On first request from the RIPE NCC, the class C network numbers not delete:   yet reassigned, must be returned to the RIPE NCC. delete:   delete:   delete:   Supernetting delete:   delete:   NICs and NOCs reassigning IP network numbers are urgently requested to delete:   read the Supernetting proposal by Vince Fuller et al. Standards Process -- Revision 3 IETF Experimental RFC insert: <a href="http://www.ietf.org/rfc/rfc2026.txt"> http://www.ietf.org/rfc/rfc2026.txt insert: </a> see Sec. 4.2.1 insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="Attribution">` insert: `</a>` 8.0 Attribution insert: `` insert: `</h3>`

insert: 

This document can delete:   be obtained is compiled from the rfc section of the RIPE document store or other RFC delete:   servers. It is called rfc1338.txt. delete:   The Supernetting proposal was made to reduce the increase of routing delete:   table size in the current Internet. It proposes to create a hierarchy delete:   of IP network numbers, which can then be aggregated resulting in less delete:   routing table entries in routing equipment. While this proposal has not delete:   been formally adopted we expect that something at least along the same delete:   principle will be implemented in the near future. delete:   delete:   Here is how it works: delete:   delete:   If an organisation A needs 8 class C network numbers, the numbers should delete:   be given out in such a way that the routing information for each of delete:   these 8 networks could appear as one entry with the correct mask in delete:   routers. delete:   delete:   More concretely: delete:   delete:   Service provider S hands out networks 192.24.8 policies developed by the RIPE community. insert: 

insert: 

The following people actively contributed by making proposals through 192.24.15 to delete:   organisation A. These networks can then appear in routing equipment as a delete:   supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C delete:   network numbers appear as one routing table entry. delete:   delete:   The guidelines that can be derived from the Supernetting proposal are: delete:   delete:   A) Service providers should reserve blocks of class C network numbers from delete:   their allocation for each organisations requesting class C network numbers. delete:   delete:   B) The size of these blocks should always be a power of 2. delete:   delete:   C) The numbers in these blocks should be contiguous. delete:   delete:   D) The blocks should start on bit boundaries. delete:   (ie powers of 2, AND multiples of the block size) delete:   delete:   E) The blocks reserved for an organisation should be sufficient for a delete:   reasonable expected growth over the next few years. delete:   delete:   F) Multi-homed organizations may obtain address space from one of their delete:   providers, the RIPE NCC, or the global NIC, as is appropriate to their delete:   network configuration. These organisations are strongly encouraged to delete:   contact the RIPE NCC for guidance. delete:   delete:   delete:   delete:   If you have any questions concerning this, please do not hesitate to delete:   call or mail us at [email protected] delete:  the RIPE Policy Development Process: insert: 

insert: 

Nick Hilliard, Geoff Huston insert: 

insert: 

insert:  insert:  insert: 

insert: 

insert: 

RIPE NCC Internet Numbers Registration Procedures Autonomous System (AS) Number Assignment Policies

RIPE Documents Search

ripe-072

State:

Obsoleted

Updated by:

ripe-104 , ripe-136 , ripe-140 , ripe-159 , ripe-185 , ripe-234 , ripe-245 , ripe-263 , ripe-288 , ripe-301 , ripe-302 , ripe-324 , ripe-368 , ripe-387 , ripe-389 , ripe-405 , ripe-411 , ripe-424 , ripe-441 , ripe-448 , ripe-449 , ripe-463 , ripe-471 , ripe-484 , ripe-492 , ripe-496 , ripe-498 , ripe-509 , ripe-515 , ripe-524 , ripe-525 , ripe-527 , ripe-528 , ripe-530 , ripe-553 , ripe-577 , ripe-579 , ripe-581 , ripe-582 , ripe-592 , ripe-595 , ripe-599 , ripe-604 , ripe-606 , ripe-621 , ripe-622 , ripe-623 , ripe-628 , ripe-632 , ripe-634 , ripe-638 , ripe-643 , ripe-648 , ripe-649 , ripe-654 , ripe-667 , ripe-679 , ripe-680 , ripe-689 , ripe-695 , ripe-708 , ripe-709 , ripe-720 , ripe-725 , ripe-730 , ripe-733 , ripe-758

Updates:

ripe-065

Authors:

M.Terpstra

Date:

October 1992

Download

File:
ASCII | 5.0KB

Changes to RIPE NCC Internet Numbers Registration Procedures

insert: `<strong>` Abstract delete: `<br />` delete: `<br />` delete: `<br />` insert: `</strong>` insert: `</h3>`

insert: `<strong>` Contents insert: `</strong>` insert: `</h3>`

insert: `<a name="Definition">` insert: `</a>` 1.0 Definition insert: `</h3>`

insert: `<a name="AssignmentCriteria">` insert: `</a>` 2.0 Assignment Criteria insert: `</h3>`

insert: `<strong>` insert: `<a name="Returning">` insert: `</a>` 3.0 Returning AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Transferring">` insert: `</a>` 4.0 Transferring AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="ASnumbers">` insert: `</a>` 5.0 32-bit AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Registration">` insert: `</a>` 6.0 Registration insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="References">` insert: `</a>` 7.0 References insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Attribution">` insert: `</a>` 8.0 Attribution insert: `</strong>` insert: `</h3>`

RIPE Documents Search

ripe-072

Changes to RIPE NCC Internet Numbers Registration Procedures

insert: <strong> Abstract delete: <br /> delete: <br /> delete: <br /> insert: </strong> insert: </h3>

insert: <strong> Contents insert: </strong> insert: </h3>

insert: <a name="Definition"> insert: </a> 1.0 Definition insert: </h3>

insert: <a name="AssignmentCriteria"> insert: </a> 2.0 Assignment Criteria insert: </h3>

insert: <strong> insert: <a name="Returning"> insert: </a> 3.0 Returning AS Numbers insert: </strong> insert: </h3>

insert: <strong> insert: <a name="Transferring"> insert: </a> 4.0 Transferring AS Numbers insert: </strong> insert: </h3>

insert: <strong> insert: <a name="ASnumbers"> insert: </a> 5.0 32-bit AS Numbers insert: </strong> insert: </h3>

insert: <strong> insert: <a name="Registration"> insert: </a> 6.0 Registration insert: </strong> insert: </h3>

insert: <strong> insert: <a name="References"> insert: </a> 7.0 References insert: </strong> insert: </h3>

insert: <strong> insert: <a name="Attribution"> insert: </a> 8.0 Attribution insert: </strong> insert: </h3>

RIPE Documents Search

ripe-072

insert: `<strong>` Abstract delete: `<br />` delete: `<br />` delete: `<br />` insert: `</strong>` insert: `</h3>`

insert: `<strong>` Contents insert: `</strong>` insert: `</h3>`

insert: `<a name="Definition">` insert: `</a>` 1.0 Definition insert: `</h3>`

insert: `<a name="AssignmentCriteria">` insert: `</a>` 2.0 Assignment Criteria insert: `</h3>`

insert: `<strong>` insert: `<a name="Returning">` insert: `</a>` 3.0 Returning AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Transferring">` insert: `</a>` 4.0 Transferring AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="ASnumbers">` insert: `</a>` 5.0 32-bit AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Registration">` insert: `</a>` 6.0 Registration insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="References">` insert: `</a>` 7.0 References insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Attribution">` insert: `</a>` 8.0 Attribution insert: `</strong>` insert: `</h3>`