|
apnic-086-v003.txt |
|
apnic-086-v004.txt |
|
|
——————————————————————- |
|
——————————————————————- |
|
|
APNIC Document identity |
|
APNIC Document identity |
|
|
|
|
|
|
|
Title: Policies for IPv4 address space management in the Asia |
|
Title: Policies for IPv4 address space management in the Asia |
|
|
Pacific region |
|
Pacific region |
|
|
|
|
|
|
|
Short title: add-manage-policy |
|
Short title: add-manage-policy |
|
|
Document ref: APNIC-086 |
|
Document ref: APNIC-086 |
|
|
|
Version: 003 |
|
Version: 004 |
|
|
Date of original publication: 21 December 2001 |
|
Date of original publication: 21 December 2001 |
|
|
|
Date of this version: 29 November 2002 |
|
Date of this version: 19 March 2004 |
|
|
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 IPv4 address space management in the Asia Pacific region |
|
Policies for IPv4 address space management in the Asia Pacific region |
|
|
|
|
|
|
|
About this document |
|
About this document |
|
|
——————- |
|
——————- |
|
|
|
|
|
|
|
skipping to change at line 263 |
|
skipping to change at line 263 |
|
|
4.1.3 Local Internet Registry (LIR) |
|
4.1.3 Local Internet Registry (LIR) |
|
|
|
|
|
|
|
A Local Internet Registry (LIR) is generally an Internet |
|
A Local Internet Registry (LIR) is generally an Internet |
|
|
Service Provider (ISP), and may assign address space to its own |
|
Service Provider (ISP), and may assign address space to its own |
|
|
network infrastructure and to users of its network services. |
|
network infrastructure and to users of its network services. |
|
|
LIR customers may be other “downstream” ISPs, which further |
|
LIR customers may be other “downstream” ISPs, which further |
|
|
assign address space to their own customers. |
|
assign address space to their own customers. |
|
|
|
|
|
|
|
4.2 Internet Exchange Point |
|
4.2 Internet Exchange Point |
|
|
|
|
|
|
|
|
An Internet Exchange Point (IXP) is a physical network |
|
An Internet Exchange Point (IX or IXP) is a layer 1 and layer |
|
|
infrastructure operated to facilitate the exchange of Internet |
|
2 network structure that interconnects three or more |
|
|
traffic between independent ISPs. The number of ISPs connected |
|
Autonomous Systems (AS) for the purpose of Internet traffic |
|
|
should be at least three and there must be a clear and open |
|
interchange. |
|
|
policy for others to join. An IXP is generally not considered |
|
|
|
|
as an IR, but rather as an end user of address space. |
|
|
|
|
|
|
|
|
|
4.3 Address space |
|
4.3 Address space |
|
|
|
|
|
|
|
In this document, address space means public IPv4 address |
|
In this document, address space means public IPv4 address |
|
|
ranges, excluding multicast addresses and private addresses |
|
ranges, excluding multicast addresses and private addresses |
|
|
defined by RFC1918. |
|
defined by RFC1918. |
|
|
|
|
|
|
|
4.4 Allocated and Assigned address space |
|
4.4 Allocated and Assigned address space |
|
|
|
|
|
|
|
For the purposes of understanding APNIC address space policies, |
|
For the purposes of understanding APNIC address space policies, |
|
|
|
|
|
|
|
skipping to change at line 953 |
|
skipping to change at line 951 |
|
|
terms must demonstrate that they are able to use 25 percent |
|
terms must demonstrate that they are able to use 25 percent |
|
|
of the requested assignment immediately and 50 percent within |
|
of the requested assignment immediately and 50 percent within |
|
|
one year. |
|
one year. |
|
|
|
|
|
|
|
There is no minimum assignment size for portable assignments |
|
There is no minimum assignment size for portable assignments |
|
|
made under these terms. |
|
made under these terms. |
|
|
|
|
|
|
|
11.2 Internet Exchange Points |
|
11.2 Internet Exchange Points |
|
|
|
|
|
|
|
Internet Exchange Points are eligible to receive a portable |
|
Internet Exchange Points are eligible to receive a portable |
|
|
|
assignment from APNIC for use on their IXP transit LAN. |
|
assignment from APNIC to be used exclusively to connect the |
|
|
|
|
IXP participant devices to the Exchange Point. |
|
|
A special condition of all assignments made under these terms |
|
|
|
|
is that the IXP must not announce the address space to the |
|
|
|
|
global Internet routing table. |
|
|
|
|
|
|
|
|
|
The minimum assignment made under these terms is /24. |
|
The minimum assignment made under these terms is /24. |
|
|
|
|
|
|
|
|
|
|
Global routability of the portable assignment is left to the |
|
|
|
|
discretion of the IXP and its participants. |
|
|
|
|
|
|
|
11.3 Critical infrastructure |
|
11.3 Critical infrastructure |
|
|
|
|
|
|
|
The following critical infrastructure networks, if operating |
|
The following critical infrastructure networks, if operating |
|
|
in the Asia Pacific region, are eligible to receive a |
|
in the Asia Pacific region, are eligible to receive a |
|
|
portable assignment: |
|
portable assignment: |
|
|
|
|
|
|
|
* root domain name system (DNS) server; |
|
* root domain name system (DNS) server; |
|
|
* global top level domain (gTLD) nameservers; |
|
* global top level domain (gTLD) nameservers; |
|
|
* country code TLD (ccTLDs) nameservers; |
|
* country code TLD (ccTLDs) nameservers; |
|
|
* IANA; |
|
* IANA; |
|
|
|
|
|
|
End of changes. 5 change blocks. |
|
13 lines changed or deleted |
|
11 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/ |