[ppml] Proposed Policy: 4-Byte AS Number Policy Proposal

Andrew Dul andrew.dul at quark.net
Mon Dec 12 12:23:01 EST 2005


This is proposed as a temporary policy, which to me means that if the policy is approved at some point it will automatically be removed from the NPRM on 1/1/2010.  Which means we will then only have the current AS number policy.  Does everyone feel that the current text will then be sufficient in a 4 byte world?  Or do we need additional text to deal with the new issues in a 4-byte world?

Andrew


***************************
NRPM 
***************************

5. AS Numbers

There are a limited number of available Autonomous System Numbers (AS Numbers), therefore, it is important to determine which sites require unique AS Numbers and which do not. Sites that do not require a unique AS Number should use one or more of the AS Numbers reserved for private use. Those numbers are: 64512 through 65535.

In order to be assigned an AS Number, each requesting organization must provide ARIN with verification that it has one of the following:

   1. A unique routing policy (its policy differs from its border gateway peers)
   2. A multihomed site.

AS Numbers are issued based on current need. An organization should request an AS Number only when it is already multihomed or will immediately become multihomed. Details regarding requirements, fees, and applying for an AS Number can be found on the Guidelines for AS Numbers page.

*******************


>  
>  Policy Proposal Name:
>  
>           4-Byte AS Number Policy Proposal
>  
>  Author: Geoff Huston
>  
>  
>  Policy Term:
>  
>           Temporary (1 January 2007 - 1 January 2010)
>  
>  Policy Statement:
>  
>           This policy proposal nominates 3 dates for changes to the
>           current AS Number allocation policy for the registry:
>  
>           On 1 January 2007 the registry will process applications that
>           specifically request 4-byte only AS Numbers and allocate such
>           AS Numbers as requested by the applicant. In the absence of
>           any specific request for a 4-byte only AS Number, a 2-byte
>           only AS Number will be allocated by the registry.
>  
>           On 1 January 2009 the registry will process applications that
>           specifically request 2-byte only AS Numbers and allocate such
>           AS Numbers as requested by the applicant. In the absence of
>           any specific request for a 2-byte only AS Number, a 4-byte
>           only AS Number will be allocated by the registry.
>  
>           On 1 January 2010 the registry will cease to make any
>           distinction between 2-byte only AS Numbers and 4-byte only AS
>           Numbers, and will operate AS number allocations from an
>           undifferentiated 4-byte AS Number allocation pool.
>  
>           Nomenclature
>  
>           It is proposed to identify 4-byte AS Numbers using a syntax of
>           <high order 16 bit value in decimal>:<low order 16 bit value
>           in decimal>. Accordingly, a 4-byte AS number of value 65546
>           (decimal) would be identified as "1:10".
>  
>           Terminology
>  
>           "2-byte only AS Numbers" refers to AS numbers in the range 0 -
>           65535
>  
>           "4-byte only AS Numbers" refers to AS Numbers in the range 1:0
>           - 65535:65535 (decimal range 65,536 - 4,294,967,295)
>  
>           "4-byte AS Numbers" refers to AS Numbers in the range 0:0 -
>           65535:65535 (decimal range 0 - 4,294,967,295)
>  



More information about the ARIN-PPML mailing list