APNIC Home

diff_apnic-094-v002

 apnic-094-v001.txt  apnic-094-v002.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-094 Document ref: APNIC-094
Version: 001 Version: 002
Date of original publication: 19 November 2002 Date of original publication: 19 November 2002
Date of this version: 19 November 2002 Date of this version: 9 February 2004
Review scheduled: n/a Review scheduled: n/a
Obsoletes: n/a Obsoletes: n/a
Status: Obsolete Status: Obsolete
Comments: AS policy previously described Comments: AS policy previously described
in APNIC-076 in APNIC-076
——————————————————————– ——————————————————————–
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
——————- ——————-
This document contains policies relating to requesting, assigning, and This document contains policies relating to requesting, assigning, and
skipping to change at line 105 skipping to change at line 105
3.1 Autonomous System (AS) 3.1 Autonomous System (AS)
An Autonomous System (AS) is a connected group of one or more An Autonomous System (AS) is a connected group of one or more
IP prefixes run by one or more network operators under a single IP prefixes run by one or more network operators under a single
and clearly defined routing policy. and clearly defined routing policy.
3.2 Autonomous System Number (ASN) 3.2 Autonomous System Number (ASN)
An Autonomous System Number (ASN) is a unique two-byte number An Autonomous System Number (ASN) is a unique two-byte number
associated with an AS. The ASN is used an identifier to allow associated with an AS. The ASN is used an identifier to allow
the AS to exchange dynamic routing information with other ASes. the AS to exchange dynamic routing information with other
Exterior routing protocols such as the Border Gateway Protocol Autonomous Systems. Exterior routing protocols such as the
(BGP) requires ASNs to exchange information between networks. Border Gateway Protocol (BGP) requires ASNs to exchange
information between networks.
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
A multi-homed AS is one which is connected to more than one A multihomed AS is one which is connected to more than one
other AS. other AS. An AS also qualifies as multihomed if it is connected
to a public Internet Exchange Point.
3.5 Routing policy 3.5 Routing policy
The routing policy of an AS is a description of how network The routing policy of an AS is a description of how network
prefixes are exchanged between that AS and other ASes. prefixes are exchanged between that AS and other Autonomous
Systems.
4 Policy environment 4 Policy environment
————————– ————————–
In addition to the general goals and environmental considerations In addition to the general goals and environmental considerations
described in APNIC-086 Policies for IPv4 address space management in described in APNIC-086 Policies for IPv4 address space management in
the Asia Pacific region, the following issues are specific factors in the Asia Pacific region, the following issues are specific factors in
determining ASN policy. determining ASN policy.
4.1 Resource ownership 4.1 Resource ownership
skipping to change at line 148 skipping to change at line 151
Neither assignment nor registration confers ownership of Neither assignment nor registration confers ownership of
resources. Organisations that use ASNs are considered resources. Organisations that use ASNs are considered
“custodians” rather than “owners” of the resource, and are not “custodians” rather than “owners” of the resource, and are not
entitled to sell or otherwise transfer that resource to other entitled to sell or otherwise transfer that resource to other
parties. parties.
4.2 Routing considerations 4.2 Routing considerations
Responsible management of ASNs is necessary to help limit the Responsible management of ASNs is necessary to help limit the
expansion of global routing tables. Aggregating contiguous IP expansion of global routing tables. Aggregating contiguous IP
address prefixes within single ASes helps to minimise the address prefixes within single Autonomous Systems helps to
number of routes announced to the global Internet. minimise the number of routes announced to the global Internet.
Part 2: Policies for ASN management Part 2: Policies for ASN management
_____________________________________________________________________ _____________________________________________________________________
5 Eligibility for ASN assignment 5 Eligibility for ASN assignment
————————————– ————————————–
An organisation is eligible for an ASN assignment if it: An organisation is eligible for an ASN assignment if it:
a. is multihomed; and a. is multihomed; and
skipping to change at line 271 skipping to change at line 274
—————————– —————————–
In addition to the eligibility guidelines described in section 5.1, In addition to the eligibility guidelines described in section 5.1,
APNIC may publish other guidelines relating to ASNs, including: APNIC may publish other guidelines relating to ASNs, including:
a. further descriptions of evaluation procedures; a. further descriptions of evaluation procedures;
b. summaries of the best current practices that organisations b. summaries of the best current practices that organisations
requesting ASNs will generally be expected to adopt; and requesting ASNs will generally be expected to adopt; and
c. other information that may assist organisations to request c. other information that may assist organisations to request
ASNs. ASNs.
Any guidelines published will be developed within the APNIC community, Any guidelines published will be developed within the APNIC community,
and will be consistent with the goals and policies described in this and will be consistent with the goals and policies described in this
document. document.
 End of changes. 7 change blocks.
17 lines changed or deleted 20 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/