|
apnic-094-v003.txt |
|
apnic-094-v004.txt |
|
|
——————————————————————- |
|
——————————————————————- |
|
|
APNIC Document identity |
|
APNIC Document identity |
|
|
|
|
|
|
|
Title: Policies for Autonomous System number management in |
|
Title: Policies for Autonomous System number management in |
|
|
the Asia Pacific region |
|
the Asia Pacific region |
|
|
|
|
|
|
|
Short title: asn-policy |
|
Short title: asn-policy |
|
|
Document ref: APNIC-94 |
|
Document ref: APNIC-94 |
|
|
|
Version: 003 |
|
Version: 004 |
|
|
Date of original publication: 19 November 2002 |
|
Date of original publication: 19 November 2002 |
|
|
|
Date of this version: 1 January 2007 |
|
Date of this version: 16 February 2009 |
|
|
Review scheduled: n/a |
|
Review scheduled: n/a |
|
|
Obsoletes: Previous versions |
|
Obsoletes: Previous versions |
|
|
Status: Obsolete |
|
Status: Obsolete |
|
|
Comments: n/a |
|
Comments: n/a |
|
|
——————————————————————– |
|
——————————————————————– |
|
|
|
|
|
|
|
Policies for Autonomous System number management |
|
Policies for Autonomous System number management |
|
|
in the Asia Pacific region |
|
in the Asia Pacific region |
|
|
|
|
|
|
|
About this document |
|
About this document |
|
|
|
|
|
|
|
skipping to change at line 115 |
|
skipping to change at line 115 |
|
|
Autonomous Systems. Exterior routing protocols such as the |
|
Autonomous Systems. Exterior routing protocols such as the |
|
|
Border Gateway Protocol (BGP) requires ASNs to exchange |
|
Border Gateway Protocol (BGP) requires ASNs to exchange |
|
|
information between networks. |
|
information between networks. |
|
|
|
|
|
|
|
– Two-byte only AS numbers are AS numbers in the range: |
|
– Two-byte only AS numbers are AS numbers in the range: |
|
|
|
|
|
|
|
0 – 65535 |
|
0 – 65535 |
|
|
|
|
|
|
|
– Four-byte only AS numbers are AS numbers in the range: |
|
– Four-byte only AS numbers are AS numbers in the range: |
|
|
|
|
|
|
|
|
1.0 – 65535.65535 (decimal range 65,536 – 4,294,967,295) |
|
65,536 – 4,294,967,295 |
|
|
|
|
|
|
|
|
– Four-byte AS numbers are AS numbers in the range: |
|
– Four-byte AS numbers are all AS numbers in the range: |
|
|
|
|
|
|
|
|
0.0 – 65535.65535 (decimal range 0 – 4,294,967,295) |
|
0 – 4,294,967,295 |
|
|
|
|
|
|
|
3.3 aut-num object |
|
3.3 aut-num object |
|
|
|
|
|
|
|
An aut-num object is an object in the Whois database used to |
|
An aut-num object is an object in the Whois database used to |
|
|
register ASN assignment details. For the purposes of this |
|
register ASN assignment details. For the purposes of this |
|
|
document, aut-num object also refers to the ASN registration |
|
document, aut-num object also refers to the ASN registration |
|
|
objects in NIR databases. |
|
objects in NIR databases. |
|
|
|
|
|
|
|
3.4 Multihomed |
|
3.4 Multihomed |
|
|
|
|
|
|
|
|
|
|
|
|
skipping to change at line 240 |
|
skipping to change at line 240 |
|
|
|
|
|
|
|
6.3 Timetable for moving from two-byte only AS numbers to four-byte AS |
|
6.3 Timetable for moving from two-byte only AS numbers to four-byte AS |
|
|
numbers |
|
numbers |
|
|
|
|
|
|
|
Commencing 1 January 2007, APNIC will process applications that |
|
Commencing 1 January 2007, APNIC will process applications that |
|
|
specifically request four-byte only AS numbers and assign such AS |
|
specifically request four-byte only AS numbers and assign such AS |
|
|
numbers as requested by the applicant. In the absence of any |
|
numbers as requested by the applicant. In the absence of any |
|
|
specific request for a four-byte only AS number, a two-byte only |
|
specific request for a four-byte only AS number, a two-byte only |
|
|
AS number will be assigned. |
|
AS number will be assigned. |
|
|
|
|
|
|
|
|
|
|
Commencing 1 July 2009, APNIC will process applications that |
|
|
|
|
specifically request a two-byte only AS numbers and assign such AS |
|
|
|
|
numbers as requested by the applicant if the applicant can |
|
|
|
|
demonstrate that a four-byte only AS number is unsuitable. In the |
|
|
|
|
absence of demonstrated need for a two-byte only AS number, a |
|
|
|
|
four-byte only AS number will be assigned. |
|
|
|
|
|
|
|
Commencing 1 January 2009, APNIC will process applications that |
|
Commencing 1 January 2009, APNIC will process applications that |
|
|
specifically request two-byte only AS numbers and assign such AS |
|
specifically request two-byte only AS numbers and assign such AS |
|
|
numbers as requested by the applicant. In the absence of any |
|
numbers as requested by the applicant. In the absence of any |
|
|
specific request for a two-byte only AS number, a four-byte only AS |
|
specific request for a two-byte only AS number, a four-byte only AS |
|
|
number will be assigned. |
|
number will be assigned. |
|
|
|
|
|
|
|
Commencing 1 January 2010, APNIC will cease to make any |
|
Commencing 1 January 2010, APNIC will cease to make any |
|
|
distinction between two-byte only AS numbers and four-byte only AS |
|
distinction between two-byte only AS numbers and four-byte only AS |
|
|
numbers, and will operate AS number assignments from an |
|
numbers, and will operate AS number assignments from an |
|
|
undifferentiated four-byte AS number pool. |
|
undifferentiated four-byte AS number pool. |
|
|
|
|
|
|
End of changes. 6 change blocks. |
|
5 lines changed or deleted |
|
12 lines changed or added |
|
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |