APNIC Home

diff_apnic-094-v007

 apnic-094-v006.txt   apnic-094-v007.txt 
———————————————————————– ———————————————————————–
APNIC Document identity APNIC Document identity
Title: Policies for Autonomous System number management Title: Policies for Autonomous System number management
in the Asia Pacific region in the Asia Pacific region
Short title: asn-policy Short title: asn-policy
Document ref: APNIC-094 Document ref: APNIC-094
Version: 006 Version: 007
Date of original publication: 19 November 2002 Date of original publication: 19 November 2002
Date of this version: 8 November 2010 Date of this version: 16 April 2014
Review scheduled: n/a Review scheduled: n/a
Obsoletes: Previous versions Obsoletes: Previous versions
Status: Obsolete Status: Obsolete
Comments: AS policy previously described in Comments: Obsoleted by apnic-127
APNIC-076 ——————————————————————–
Policies for Autonomous System number management in the Asia Policies for Autonomous System number management in the Asia
Pacific region 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
registering AS numbers in the Asia Pacific region. registering AS numbers in the Asia Pacific region.
skipping to change at line 158 skipping to change at line 158
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
The Internet community regards ASNs as a public resource that The Internet community regards ASNs as a public resource that
should only be distributed according to demonstrated need. Neither should only be distributed according to demonstrated need. Neither
assignment nor registration confers ownership of resources. assignment nor registration confers ownership of resources.
Organizations that use ASNs are considered “custodians” rather than Organizations that use ASNs are considered “custodians” rather than
“owners” of the resource, and are not entitled to sell or otherwise “owners” of the resource, and are not entitled to sell or otherwise
transfer that resource to other parties. transfer that resource to other parties other than in accordance
with the APNIC transfer, merger, acquisition, and takeover policy.
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 Autonomous Systems helps to address prefixes within single Autonomous Systems helps to
minimize the number of routes announced to the global Internet. minimize the number of routes announced to the global Internet.
Part 2: Policies for ASN management Part 2: Policies for ASN management
_______________________________________________________________________ _______________________________________________________________________
skipping to change at line 290 skipping to change at line 291
for each ASN assigned. for each ASN assigned.
The registered administrative contact (‘admin-c’) is the person The registered administrative contact (‘admin-c’) is the person
responsible for the ASN and should generally be someone who is responsible for the ASN and should generally be someone who is
physically located at the site of the AS. physically located at the site of the AS.
The technical contact (‘tech-c’) need not be physically located The technical contact (‘tech-c’) need not be physically located
at the site of the AS, but must be a person who is responsible at the site of the AS, but must be a person who is responsible
for the day-to-day operation of that AS. for the day-to-day operation of that AS.
In addition, it is mandatory to register an Incident Report Team (IRT) In addition, it is mandatory to register an Incident Report Team
object for each AS number record in the APNIC Whois Database. (IRT) object for each AS number record in the APNIC Whois Database.
7.2 Registering routing policy 7.2 Registering routing policy
APNIC recommends that the routing policy of the AS is registered APNIC recommends that the routing policy of the AS is registered
for each ASN assigned. for each ASN assigned.
7.3 Updating registration details 7.3 Updating registration details
Organizations responsible for ASNs should update the aut-num Organizations responsible for ASNs should update the aut-num
object in the appropriate database if any of the registration object in the appropriate database if any of the registration
 End of changes. 6 change blocks. 
7 lines changed or deleted 9 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/