|
apnic-resource-policies.txt |
|
apnic-resource-policies_draft.txt |
|
|
———————————————————————– |
|
———————————————————————– |
|
|
APNIC Document identity |
|
APNIC Document identity |
|
|
|
|
|
|
|
Title: APNIC Internet Number Resource Policies |
|
Title: APNIC Internet Number Resource Policies |
|
|
|
|
|
|
|
Short title: apnic-resource-policies |
|
Short title: apnic-resource-policies |
|
|
Document ref: APNIC-127 |
|
Document ref: APNIC-127 |
|
|
|
Version: 004 |
|
Version: 005 |
|
|
Date of original publication: 5 March 2015 |
|
Date of original publication: 5 March 2015 |
|
|
|
Date of this version: 4 August 2017 |
|
Date of this version: xx November 2017 |
|
|
Review scheduled: n/a |
|
Review scheduled: n/a |
|
|
|
Obsoletes: apnic-127-v003 |
|
Obsoletes: apnic-127-v004 |
|
|
Status: Active |
|
Status: Draft |
|
|
Comments: Implements prop-117. |
|
Comments: Implements prop-116, prop-121, and |
|
|
|
|
prop-122. |
|
|
———————————————————————- |
|
———————————————————————- |
|
|
|
|
|
|
|
Table of Contents |
|
Table of Contents |
|
|
—————– |
|
—————– |
|
|
|
|
|
|
|
Part 1: Policy Environment |
|
Part 1: Policy Environment |
|
|
————————– |
|
————————– |
|
|
|
|
|
|
|
1.0. Introduction |
|
1.0. Introduction |
|
|
1.1. Scope |
|
1.1. Scope |
|
|
|
|
|
|
|
skipping to change at line 157 ¶ |
|
skipping to change at line 158 ¶ |
|
|
6.2.1. IPv4 for LIRs |
|
6.2.1. IPv4 for LIRs |
|
|
6.2.2. IPv4 for multihoming |
|
6.2.2. IPv4 for multihoming |
|
|
6.2.3. IPv4 for critical infrastructure |
|
6.2.3. IPv4 for critical infrastructure |
|
|
6.2.4. IPv4 for Internet Exchange Points |
|
6.2.4. IPv4 for Internet Exchange Points |
|
|
|
|
|
|
|
7.0. Subsequent IPv4 delegations |
|
7.0. Subsequent IPv4 delegations |
|
|
7.1. Prior delegations to be used first |
|
7.1. Prior delegations to be used first |
|
|
7.2. Special circumstances – large delegations |
|
7.2. Special circumstances – large delegations |
|
|
|
|
|
|
|
8.0. IPv4 Transfers |
|
8.0. IPv4 Transfers |
|
|
|
8.1. Transfers of IPv4 addresses between APNIC account holders |
|
8.1. IPv4 transfers within the APNIC region |
|
|
8.1.1. Conditions on the space to be transferred |
|
8.1.1. Conditions on the space to be transferred |
|
|
8.1.2. Conditions on source of the transfer |
|
8.1.2. Conditions on source of the transfer |
|
|
8.1.3. Conditions on recipient of the transfer |
|
8.1.3. Conditions on recipient of the transfer |
|
|
8.2. Inter-RIR IPv4 address transfers |
|
8.2. Inter-RIR IPv4 address transfers |
|
|
8.2.1. Conditions on the space to be transferred |
|
8.2.1. Conditions on the space to be transferred |
|
|
8.2.2. Conditions on the source of the transfer |
|
8.2.2. Conditions on the source of the transfer |
|
|
8.2.3. Conditions on the recipient of the transfer |
|
8.2.3. Conditions on the recipient of the transfer |
|
|
8.3. Transfer of Historical Internet resources |
|
8.3. Transfer of Historical Internet resources |
|
|
8.3.1. Transfer procedure |
|
8.3.1. Transfer procedure |
|
|
8.3.2. Policies applicable to transferred Historical resources |
|
8.3.2. Policies applicable to transferred Historical resources |
|
|
|
|
|
|
|
skipping to change at line 1586 ¶ |
|
skipping to change at line 1587 ¶ |
|
|
—————————————– |
|
—————————————– |
|
|
The current minimum delegation size for IPv4 is a /24 (256 |
|
The current minimum delegation size for IPv4 is a /24 (256 |
|
|
addresses). |
|
addresses). |
|
|
|
|
|
|
|
Since Friday, 15 April 2011, each APNIC account holder is only |
|
Since Friday, 15 April 2011, each APNIC account holder is only |
|
|
eligible to receive IPv4 address delegations totalling a maximum /22 |
|
eligible to receive IPv4 address delegations totalling a maximum /22 |
|
|
from the APNIC 103/8 IPv4 address pool. |
|
from the APNIC 103/8 IPv4 address pool. |
|
|
|
|
|
|
|
On Tuesday, 27 May 2014, each APNIC account holder became eligible |
|
On Tuesday, 27 May 2014, each APNIC account holder became eligible |
|
|
to receive additional delegations up to a maximum of /22 address |
|
to receive additional delegations up to a maximum of /22 address |
|
|
|
space from the APNIC non-103/8 IPv4 address pool. |
|
space from the APNIC non-103/8 Recovered IPv4 address pool. |
|
|
|
|
|
|
|
|
|
Note: Resources may not always be available from the recovered |
|
|
|
|
(non-103/8) address pool. APNIC has created a waiting list for those |
|
|
|
|
IPv4 requests that cannot be fulfilled. These requests are fulfilled |
|
|
|
|
in order of request, as space becomes available. |
|
|
|
|
|
|
|
To receive delegations from either of these pools, they must |
|
To receive delegations from either of these pools, they must |
|
|
demonstrate their eligibility by meeting the criteria specified |
|
demonstrate their eligibility by meeting the criteria specified |
|
|
below. |
|
below. |
|
|
|
|
|
|
|
6.1.1. Additional allocation rounds |
|
6.1.1. Additional allocation rounds |
|
|
———————————– |
|
———————————– |
|
|
Recovered 103/8 address space returned to APNIC will be added to |
|
Recovered 103/8 address space returned to APNIC will be added to |
|
|
the 103/8 IPv4 address pool. Recovered non-103/8 address space |
|
the 103/8 IPv4 address pool. Recovered non-103/8 address space |
|
|
or addresses allocated to APNIC from the ‘IANA Recovered IPv4 |
|
or addresses allocated to APNIC from the ‘IANA Recovered IPv4 |
|
|
|
|
|
|
|
skipping to change at line 1705 ¶ |
|
skipping to change at line 1711 ¶ |
|
|
needs to make a single delegation that is larger than the amount of |
|
needs to make a single delegation that is larger than the amount of |
|
|
space it has remaining. |
|
space it has remaining. |
|
|
|
|
|
|
|
8.0. IPv4 Transfers |
|
8.0. IPv4 Transfers |
|
|
——————- |
|
——————- |
|
|
IPv4 addresses may be transferred in accordance with the following |
|
IPv4 addresses may be transferred in accordance with the following |
|
|
policies. APNIC does not recognize transfers outside this policy and |
|
policies. APNIC does not recognize transfers outside this policy and |
|
|
require organizations holding such transfers to return them to the |
|
require organizations holding such transfers to return them to the |
|
|
appropriate IR. |
|
appropriate IR. |
|
|
|
|
|
|
|
|
|
|
The goal of the APNIC transfer policy is to help distribute IPv4 |
|
|
|
|
addresses from those who no longer need the addresses, to organizations |
|
|
|
|
that need the addresses, but cannot obtain them from the free pool. |
|
|
|
|
|
|
|
|
|
Resources are exceptions to this requirement. |
|
|
|
|
|
|
|
APNIC recognizes there will be situations where IPv4 resources may be |
|
APNIC recognizes there will be situations where IPv4 resources may be |
|
|
transferred between: |
|
transferred between: |
|
|
– Current APNIC account holders |
|
– Current APNIC account holders |
|
|
– Current APNIC account holders and organizations in other RIR regions |
|
– Current APNIC account holders and organizations in other RIR regions |
|
|
– Holders of Historical IPv4 addresses without an APNIC account to |
|
– Holders of Historical IPv4 addresses without an APNIC account to |
|
|
current APNIC Members |
|
current APNIC Members |
|
|
– Organizations through a merger, acquisition, or takeover. |
|
– Organizations through a merger, acquisition, or takeover. |
|
|
|
|
|
|
|
|
|
|
Addresses delegated from the 103/8 free pool cannot be transferred for a |
|
|
|
|
minimum of five years after the original delegation. |
|
|
|
|
|
|
|
|
|
During that time, if the reason for the original request is no |
|
|
|
|
longer valid, the resources must be returned to APNIC as required in |
|
|
|
|
Section 4.0. Resource License of this document. |
|
|
|
|
|
|
|
The policies in this document ensure that all transfers of IPv4 address |
|
The policies in this document ensure that all transfers of IPv4 address |
|
|
space are accurately reflected in the APNIC Whois Database. This ensures |
|
space are accurately reflected in the APNIC Whois Database. This ensures |
|
|
the integrity of the network and an accurate description of the current |
|
the integrity of the network and an accurate description of the current |
|
|
state of address distribution. |
|
state of address distribution. |
|
|
|
|
|
|
|
APNIC will maintain a public log of all transfers made under this |
|
APNIC will maintain a public log of all transfers made under this |
|
|
policy. |
|
policy. |
|
|
|
|
|
|
|
|
8.1. Transfers of IPv4 addresses between APNIC account holders |
|
8.1. IPv4 transfers within the APNIC region |
|
|
————————————————————– |
|
——————————————- |
|
|
APNIC will process and record IPv4 address transfer requests between |
|
APNIC will process and record IPv4 address transfer requests between |
|
|
current APNIC account holders subject to the following conditions. |
|
current APNIC account holders subject to the following conditions. |
|
|
|
|
|
|
|
8.1.1. Conditions on the space to be transferred |
|
8.1.1. Conditions on the space to be transferred |
|
|
———————————————— |
|
———————————————— |
|
|
The minimum transfer size is a /24. |
|
The minimum transfer size is a /24. |
|
|
The address block must be: |
|
The address block must be: |
|
|
– In the range of addresses administered by APNIC |
|
– In the range of addresses administered by APNIC |
|
|
– Allocated or assigned to a current APNIC account holder |
|
– Allocated or assigned to a current APNIC account holder |
|
|
– The address block will be subject to all current APNIC |
|
– The address block will be subject to all current APNIC |
|
|
policies from the time of transfer. |
|
policies from the time of transfer. |
|
|
|
|
|
– Addresses delegated from the 103/8 free pool cannot be |
|
|
|
|
transferred for a minimum of five years after the original |
|
|
|
|
delegation. |
|
|
|
|
|
|
|
8.1.2. Conditions on source of the transfer |
|
8.1.2. Conditions on source of the transfer |
|
|
——————————————- |
|
——————————————- |
|
|
The source entity must be the currently registered holder of the |
|
The source entity must be the currently registered holder of the |
|
|
IPv4 address resources, and not be involved in any dispute as to |
|
IPv4 address resources, and not be involved in any dispute as to |
|
|
the status of those resources. |
|
the status of those resources. |
|
|
|
|
|
|
|
8.1.3. Conditions on recipient of the transfer |
|
8.1.3. Conditions on recipient of the transfer |
|
|
———————————————- |
|
———————————————- |
|
|
The recipient entity will be subject to current APNIC policies. |
|
The recipient entity will be subject to current APNIC policies. |
|
|
|
|
|
|
|
skipping to change at line 1759 ¶ |
|
skipping to change at line 1784 ¶ |
|
|
Recipients that already hold IPv4 resources must: |
|
Recipients that already hold IPv4 resources must: |
|
|
|
|
|
|
|
– Demonstrate a detailed plan for the use of the transferred |
|
– Demonstrate a detailed plan for the use of the transferred |
|
|
resource within 24 months, |
|
resource within 24 months, |
|
|
– Show past usage rate, and |
|
– Show past usage rate, and |
|
|
– Provide evidence of compliance with APNIC policies with |
|
– Provide evidence of compliance with APNIC policies with |
|
|
respect to past delegations. |
|
respect to past delegations. |
|
|
|
|
|
|
|
8.2. Inter-RIR IPv4 address transfers |
|
8.2. Inter-RIR IPv4 address transfers |
|
|
————————————- |
|
————————————- |
|
|
|
APNIC will recognize inter-RIR IPv4 address transfers only when the |
|
APNIC will process and record inter-RIR IPv4 address transfers only |
|
|
counterpart RIR has an inter-RIR transfer policy that permits the |
|
when the counterpart RIR has an inter-RIR transfer policy that |
|
|
transfer of address space between APNIC and its own region. |
|
permits the transfer of address space between APNIC and its own region. |
|
|
|
|
|
|
|
APNIC will process and record IPv4 address transfer requests between |
|
APNIC will process and record IPv4 address transfer requests between |
|
|
current APNIC account holders and organizations in other RIR regions |
|
current APNIC account holders and organizations in other RIR regions |
|
|
subject to the following conditions. |
|
subject to the following conditions. |
|
|
|
|
|
|
|
8.2.1. Conditions on the space to be transferred |
|
8.2.1. Conditions on the space to be transferred |
|
|
———————————————— |
|
———————————————— |
|
|
The minimum transfer size is a /24. |
|
The minimum transfer size is a /24. |
|
|
|
|
|
|
|
The IPv4 address space to be transferred should be under the |
|
The IPv4 address space to be transferred should be under the |
|
|
management of the RIR at which the transfer source holds an |
|
management of the RIR at which the transfer source holds an |
|
|
account and the authentic holder of the space should match with |
|
account and the authentic holder of the space should match with |
|
|
the source without any disputes. |
|
the source without any disputes. |
|
|
|
|
|
|
|
|
|
|
Some RIRs, including APNIC, have restrictions against the |
|
|
|
|
transfer of certain address blocks. APNIC policy does not allow |
|
|
|
|
the transfer of addresses delegated from the 103/8 free pool |
|
|
|
|
to be transferred for a minimum of five years after the original |
|
|
|
|
delegation. |
|
|
|
|
|
|
|
8.2.2. Conditions on the source of the transfer |
|
8.2.2. Conditions on the source of the transfer |
|
|
———————————————– |
|
———————————————– |
|
|
The conditions on the source of the transfer will be defined by |
|
The conditions on the source of the transfer will be defined by |
|
|
the RIR where the source organization holds an account. This |
|
the RIR where the source organization holds an account. This |
|
|
means: |
|
means: |
|
|
|
|
|
|
|
– For transfers from an APNIC source, the source entity must be |
|
– For transfers from an APNIC source, the source entity must be |
|
|
the currently registered holder of the IPv4 address |
|
the currently registered holder of the IPv4 address |
|
|
resources, and not be involved in any dispute as to the |
|
resources, and not be involved in any dispute as to the |
|
|
status of those resources. |
|
status of those resources. |
|
|
– Where the source is in another region, the conditions on the |
|
– Where the source is in another region, the conditions on the |
|
|
|
source as defined in the counterpart RIR’s transfer policy at |
|
source as defined in the counterpart RIR’s transfer policy at |
|
|
the time of the transfer will apply. |
|
the time of the transfer will apply. |
|
|
|
|
|
|
|
8.2.3. Conditions on the recipient of the transfer |
|
8.2.3. Conditions on the recipient of the transfer |
|
|
————————————————– |
|
————————————————– |
|
|
The conditions on the recipient of the transfer will be defined |
|
The conditions on the recipient of the transfer will be defined |
|
|
by the RIR where the recipient organization holds an account. |
|
by the RIR where the recipient organization holds an account. |
|
|
This means: |
|
This means: |
|
|
|
|
|
|
|
– For transfers to an APNIC recipient, the conditions defined |
|
– For transfers to an APNIC recipient, the conditions defined |
|
|
in Section 8.1.3. will apply. |
|
in Section 8.1.3. will apply. |
|
|
– Where the recipient is in another region, the conditions on |
|
– Where the recipient is in another region, the conditions on |
|
|
the recipient as defined in the counterpart RIR’s transfer |
|
the recipient as defined in the counterpart RIR’s transfer |
|
|
policy at the time of the transfer will apply. |
|
policy at the time of the transfer will apply. |
|
|
|
|
|
|
|
8.3. Transfer of Historical Internet resources |
|
8.3. Transfer of Historical Internet resources |
|
|
———————————————- |
|
———————————————- |
|
|
|
APNIC will recognize the transfer of Historical IPv4 resources as |
|
APNIC will process and record the transfer of Historical IPv4 |
|
|
defined in Section 2.5.2. |
|
resources as defined in Section 2.5.2. |
|
|
|
|
|
|
|
If Historical resources are transferred to an APNIC Member, there is |
|
If Historical resources are transferred to an APNIC Member, there is |
|
|
the option to make the transfer under the conditions described in |
|
the option to make the transfer under the conditions described in |
|
|
this policy. Transfers of Internet resources to current APNIC |
|
this policy. Transfers of Internet resources to current APNIC |
|
|
account holders are purely optional. |
|
account holders are purely optional. |
|
|
|
|
|
|
|
8.3.1. Transfer procedure |
|
8.3.1. Transfer procedure |
|
|
————————- |
|
————————- |
|
|
All transfers of Historical Internet resources to current APNIC |
|
All transfers of Historical Internet resources to current APNIC |
|
|
Member account holders made under this policy are recognized and |
|
Member account holders made under this policy are recognized and |
|
|
|
|
|
|
|
skipping to change at line 1845 ¶ |
|
skipping to change at line 1876 ¶ |
|
|
particular, future address requests from the account holder must |
|
particular, future address requests from the account holder must |
|
|
document the use of transferred resources as a part of their |
|
document the use of transferred resources as a part of their |
|
|
current resource holdings. |
|
current resource holdings. |
|
|
|
|
|
|
|
If the historical Internet resources are not held under a |
|
If the historical Internet resources are not held under a |
|
|
current APNIC account, the recipient entity must verify they are |
|
current APNIC account, the recipient entity must verify they are |
|
|
the legitimate holder of the Internet resources. |
|
the legitimate holder of the Internet resources. |
|
|
|
|
|
|
|
8.4. Mergers & acquisitions |
|
8.4. Mergers & acquisitions |
|
|
————————— |
|
————————— |
|
|
|
APNIC will recognize the transfer of IPv4 resources as the result of |
|
APNIC will process and record the transfer of IPv4 resources as the |
|
|
merger or acquisition. |
|
result of merger or acquisition. |
|
|
|
|
|
|
|
|
|
Addresses delegated from the 103/8 free pool cannot be transferred |
|
|
|
|
for a minimum of five years after the original delegation. |
|
|
|
|
|
|
|
8.4.1. Updating registration details |
|
8.4.1. Updating registration details |
|
|
———————————— |
|
———————————— |
|
|
If an organization changes ownership (due to a merger, sale, or |
|
If an organization changes ownership (due to a merger, sale, or |
|
|
takeover), then the new entity must register any changes to its |
|
takeover), then the new entity must register any changes to its |
|
|
network usage and contact personnel. If the effect of the |
|
network usage and contact personnel. If the effect of the |
|
|
ownership change is that the name changes, then the organization |
|
ownership change is that the name changes, then the organization |
|
|
must provide relevant legal documentation supporting the name |
|
must provide relevant legal documentation supporting the name |
|
|
change. |
|
change. |
|
|
|
|
|
|
|
|
|
|
|
|
skipping to change at line 1946 ¶ |
|
skipping to change at line 1980 ¶ |
|
|
If an APNIC Member wishes to receive an initial allocation or |
|
If an APNIC Member wishes to receive an initial allocation or |
|
|
assignment larger than the sizes described above, the Member |
|
assignment larger than the sizes described above, the Member |
|
|
will need to apply under the alternative criteria described |
|
will need to apply under the alternative criteria described |
|
|
in Section 9.2.2. and Section 10.1 below. |
|
in Section 9.2.2. and Section 10.1 below. |
|
|
|
|
|
|
|
9.2.2. Account holders without existing IPv4 space |
|
9.2.2. Account holders without existing IPv4 space |
|
|
————————————————– |
|
————————————————– |
|
|
To qualify for an initial allocation of IPv6 address space, an |
|
To qualify for an initial allocation of IPv6 address space, an |
|
|
organization must: |
|
organization must: |
|
|
|
|
|
|
|
|
1. Be an LIR |
|
1. Be an LIR |
|
|
2. Not be an end site |
|
2. Not be an end site |
|
|
3. Plan to provide IPv6 connectivity to organizations to which |
|
3. Plan, within two years, to provide IPv6 connectivity to |
|
|
it will make assignments. |
|
other organizations/end-users to which it will make |
|
|
4. Meet one of the two following criteria: |
|
assignments. |
|
|
– Have a plan for making at least 200 assignments to other |
|
|
|
|
organizations within two years, or |
|
The allocation size, in case an address block bigger than the |
|
|
– Be an existing LIR with IPv4 allocations from APNIC or an |
|
default one (as indicated in 9.2.1.) is requested, will be based |
|
|
NIR, which will make IPv6 assignments or sub-allocations to |
|
on the number of users, the extent of the organization’s |
|
|
other organizations and announce the allocation in the |
|
infrastructure, the hierarchical and geographical structuring of |
|
|
inter- domain routing system within two years. |
|
the organization, the segmentation of infrastructure for |
|
|
|
|
security and the planned longevity of the allocation. |
|
|
|
|
|
|
|
Private networks (those not connected to the public Internet) |
|
Private networks (those not connected to the public Internet) |
|
|
may also be eligible for an IPv6 address space allocation |
|
may also be eligible for an IPv6 address space allocation |
|
|
provided they meet equivalent criteria to those listed above. |
|
provided they meet equivalent criteria to those listed above. |
|
|
|
|
|
|
|
9.3. Subsequent IPv6 allocations |
|
9.3. Subsequent IPv6 allocations |
|
|
——————————– |
|
——————————– |
|
|
Organizations that hold an existing IPv6 allocation may receive a |
|
Organizations that hold an existing IPv6 allocation may receive a |
|
|
subsequent allocation in accordance with the following policies. |
|
subsequent allocation in accordance with the following policies. |
|
|
|
|
|
|
|
|
|
|
|
|
skipping to change at line 2014 ¶ |
|
skipping to change at line 2049 ¶ |
|
|
be considered a valid technical or other reason, see “APNIC |
|
be considered a valid technical or other reason, see “APNIC |
|
|
guidelines for IPv6 allocation and assignment requests”. |
|
guidelines for IPv6 allocation and assignment requests”. |
|
|
|
|
|
|
|
http://www.apnic.net/criteria/ipv6-guidelines |
|
http://www.apnic.net/criteria/ipv6-guidelines |
|
|
|
|
|
|
|
9.3.4. Size of subsequent allocation |
|
9.3.4. Size of subsequent allocation |
|
|
———————————— |
|
———————————— |
|
|
When an organization has achieved an acceptable utilization for |
|
When an organization has achieved an acceptable utilization for |
|
|
its allocated address space, it is immediately eligible to |
|
its allocated address space, it is immediately eligible to |
|
|
obtain an additional allocation that results in a doubling of |
|
obtain an additional allocation that results in a doubling of |
|
|
|
the address space allocated to it. Where possible, except where |
|
the address space allocated to it. |
|
|
separate disaggregated ranges are requested for multiple |
|
|
|
|
discreet networks, the allocation will be made from an adjacent |
|
Where possible, except where separate disaggregated ranges are |
|
|
address block, meaning that its existing allocation is extended |
|
requested for multiple discrete networks, the allocation will be |
|
|
by one bit to the left. |
|
made from an adjacent address block, meaning that its existing |
|
|
|
|
allocation is extended by one bit to the left. |
|
|
|
|
|
|
|
If an organization needs more address space, it must provide |
|
If an organization needs more address space, it must provide |
|
|
|
documentation justifying its requirements for a two-year period. |
|
documentation justifying its new requirements. The allocation |
|
|
The allocation made will be based on this requirement. |
|
size, will be based on the new needs (the number of users, the |
|
|
|
|
extent of the organization’s infrastructure, the hierarchical |
|
|
|
|
and geographical structuring of the organization, the |
|
|
|
|
segmentation of infrastructure for security and the planned |
|
|
|
|
longevity of the allocation). |
|
|
|
|
|
|
|
10.0. IPv6 assignments |
|
10.0. IPv6 assignments |
|
|
———————- |
|
———————- |
|
|
APNIC Members that have been delegated an IPv4 address block from APNIC, |
|
APNIC Members that have been delegated an IPv4 address block from APNIC, |
|
|
but have no IPv6 space, can qualify for an appropriately sized IPv6 |
|
but have no IPv6 space, can qualify for an appropriately sized IPv6 |
|
|
block under the matching IPv6 policy. For example, a Member that has |
|
block under the matching IPv6 policy. For example, a Member that has |
|
|
received an IPv4 IXP assignment will be eligible to receive an IPv6 IXP |
|
received an IPv4 IXP assignment will be eligible to receive an IPv6 IXP |
|
|
assignment. |
|
assignment. |
|
|
|
|
|
|
|
10.1. Criteria for IPv6 Assignments |
|
10.1. Criteria for IPv6 Assignments |
|
|
|
|
|
|
| End of changes. 17 change blocks. |
|
36 lines changed or deleted |
|
76 lines changed or added |
|
|
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |