[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Wg-ipv6-guide] Guideline draft status on 1/23 (version 0.2)
Dear all,
Below is the current status of the guideline document. At first you
can see only the part changed from last version. After that I attached
the whole document.
The section changed from last version
------------------
6.1 (*) Assignment address space size
A single site may be assigned /48 in general case as the policy says.
Examples are as follows;
- Residential subscribers, connecting through on-demand or
always-on connections such as through ADSL/CATV, should
receive a /48.
- Even in the case where /64 or /128 seems to approproate initially
as the case of single PC or mobile phones, LIRs still can assign
/48 when future growth is anticipated.
- When justified LIRs can assign larger address space than a /48.
(see 8.Second Opinion Request)
7. (*) Initial allocation criteria
According to current IPv6 policy, to qualify for an initial allocation
of IPv6 address space, an organization must meet the criteria stated in
policy clause 5.1.1.
There are some points to consider when the organization wishes to receive
IPv6 addresses other than those criteria, which are as follows;
- An end site should receive IPv6 address from LIR(s) under current
policy, because there is no portable address assignment policy
in IPv6.
- An LIR is encouraged to aggregate multiple /48s which will be
assigned to other organizations into /32 (or shorter where
an LIR receives multiple /32s). The reason to aggregate is based
on "Policy clause 3.4".
- An organization must provide a 'plan' to make at least 200 /48
assignments, but is not necessarily required to 'commit' 200.
RIR/NIR regards the exisitence of a 'plan' to provide IPv6 services
or its readiness to commence, not the feasibility.
- For example an ISP which has more than 200 customers can meet
this criteria (d) if it plans to provide them with IPv6
connectivity service.
- sub-allocations to downstream ISPs are taken into account as
"to be assigned /48".
e.g) The following case meets the initial allocation criteria
of 200*/48.
Plan within the next two years:
/44 sub-allocation (= 16*/48 assignments)
assignments to POPs 20*/48
assignments to "sites" 170*/48
-----------------------------------------
total 206*/48 > 200*/48
- Each static (or dynamic) IP address assignment for its customers
can be considered as a /48 assignment.
- Existing IPv4 infrastructure/customers can also be taken into
consideration.
- For example, if a CATV provider has 4,000 IP static connection
customers in IPv4 and 5%(200) of them are expected to subscribe
IPv6 service connection, then, it this provider meets the criteria.
- This is not only restricted to the cases where they assign multiple
static IP in IPv4. Even if LIRs assign a single static IP in IPv4,
it's up to the ISP to assign /48 to these customers.
-------------------------------------
7.1(*) Use of existing IPv4 infrastructure
LIRs can justify their requested initial allocation size by the number
of their existing IPv4 users as well as the extent of their IPv4
network infrastructure.
>From this perspective LIRs are likely to be eligible for an initial
allocation criteria in case they;
- meet the current IPv4 allocation criteria AND
- receive the current IPv4 allocation as an LIR AND
- plan to tranfer the existing IPv4 infrastructure
or customers to IPv6
Note: this is just to provide an idea, and not guarantee the initial
allocation
However LIRs are still requested to provide their IPv6-ready equipment
information to ensure their plan for IPv6 services.
----------------------------------------
7.2 (*) Documentation required
When LIRs request their initial IPv6 address allocation to RIR/NIR,
LIRs are requested to provide designated request form as well as the
following information.
- Network diagram
- Network equipment information. This is to ensure LIR has a plan to
implement IPv6 ready infrastructure.
- Approximate deployment date.
- Service plan (Web hosting, Access service, etc)
-------------------------------------------
7.2.a (*) Supplementary Document
When requesting an initial allocation to RIR/NIR, model/Vendor name of
LIR's network equipment is not mandatory but there may be a case that
RIR/NIR asks those information if LIRs require a plenty of pool address
such as CATV/ADSL operator.
------------------------------------------------------------------------
End of the part changed.
----------------------
(Below is the whole draft)
--------------------------
APNIC guidelines for IPv6 allocation and assignment requests
(Version 0.2 : 20040123)
About this document
These guidelines are intended to complement the document Policies for
IPv6 address space management in the Asia Pacific region, which provides
for APNIC to publish guidelines relating to specific request evaluation
requirements and best current practice issues.
These guidelines will be updated from time to time, in consultation with
the Asia Pacific and global Internet communities, to ensure that they
remain appropriate to the current addressing environment.
Table of contents
1. Introduction
These guidelines are developed within the APNIC community, and are
consistent with the goals and policies applicable to IPv6 address
space management. They are intended to assist organisations
requesting IPv6 address space only.
Nothing in these guidelines should be considered to replace or modify
any of the specific policies defined in other APNIC documents.
2. Scope
This document applies to the management of global IPv6 public address
space in the Asia Pacific region.
Where practical, the guidelines in this document are expressed in
relation to types of connectivity, rather than to specific
technologies.
This document does not apply to IPv4, Multicast, or 'Unique local IPv6
unicast address, or Autonomous System numbers. It should be read in
conjunction with other APNIC documents, particularly APNIC-089
"IPv6 Address Allocation and Assignment Policy"
3. Additional guidance
These guidelines are not intended to be exhaustive. Additional
guidance and examples are available from the help information
available for each APNIC request form and in FAQs and other
information on the APNIC web site:
Resource Guides
http://www.apnic.net/services
APNIC FAQs
http://www.apnic.net/info/faq
4. Goals of address space management
In this document, all reference to the goals of address space
management refer to the goals described in Policies for IPv6
address space management in the Asia Pacific region, namely:
* uniqueness;
* registration;
* aggregation;
* conservation;
* fairness; and
* Minimized Overhead.
5. Application of guidelines
This document is primarily intended to guide ISPs when making
assignments to their customers or requesting address space from
APNIC. The issues discussed in this document reflect many of the
considerations used by APNIC in evaluating requests for initial allocations
and subsequent allocations.
It is intended that NIRs will either adopt these or similar
guidelines for their own members.
6. Definition of a 'site'
An end site is defined as an end user who has a business relationship,
i.e. has a contract, with a service provider. The end user (the end
site) cannot re-assign IP addresses to other organization out of its
assigned IP address space.
The number of sites is counted in accordance with the number of
contracts. Each 'end site' is eligible to receive /48 assignment in
general case.
For example;
(Single site)
-A home(corporate) user who has a single contract with a service
provider.
-A home(corporate) user who has multiple devices to connect the
internet, but has only one contract with a service provider.
(Multiple sites)
- A home (corporate) user who has multiple contracts with a service
provider.
- A home (corporate) user who has multiple separate networks, and they
are not connected each other because each network has different
management policy, even if they are in the same place. (-note- In
this case this user is considered to have multiple contract with (a)
service provider(s).
- A merged company which used to be defferent companies.
6.1 (*) Assignment address space size
A single site may be assigned /48 in general case as the policy says.
Examples are as follows;
- Residential subscribers, connecting through on-demand or
always-on connections such as through ADSL/CATV, should
receive a /48.
- Even in the case where /64 or /128 seems to approproate initially
as the case of single PC or mobile phones, LIRs still can assign
/48 when future growth is anticipated.
- When justified LIRs can assign larger address space than a /48.
(see 8.Second Opinion Request)
7. (*) Initial allocation criteria
According to current IPv6 policy, to qualify for an initial allocation
of IPv6 address space, an organization must meet the criteria stated in
policy clause 5.1.1.
There are some points to consider when the organization wishes to receive
IPv6 addresses other than those criteria, which are as follows;
- An end site should receive IPv6 address from LIR(s) under current
policy, because there is no portable address assignment policy
in IPv6.
- An LIR is encouraged to aggregate multiple /48s which will be
assigned to other organizations into /32 (or shorter where
an LIR receives multiple /32s). The reason to aggregate is based
on "Policy clause 3.4".
- An organization must provide a 'plan' to make at least 200 /48
assignments, but is not necessarily required to 'commit' 200.
RIR/NIR regards the exisitence of a 'plan' to provide IPv6 services
or its readiness to commence, not the feasibility.
- For example an ISP which has more than 200 customers can meet
this criteria (d) if it plans to provide them with IPv6
connectivity service.
- sub-allocations to downstream ISPs are taken into account as
"to be assigned /48".
e.g) The following case meets the initial allocation criteria
of 200*/48.
Plan within the next two years:
/44 sub-allocation (= 16*/48 assignments)
assignments to POPs 20*/48
assignments to "sites" 170*/48
-----------------------------------------
total 206*/48 > 200*/48
- Each static (or dynamic) IP address assignment for its customers
can be considered as a /48 assignment.
- Existing IPv4 infrastructure/customers can also be taken into
consideration.
- For example, if a CATV provider has 4,000 IP static connection
customers in IPv4 and 5%(200) of them are expected to subscribe
IPv6 service connection, then, it this provider meets the criteria.
- This is not only restricted to the cases where they assign multiple
static IP in IPv4. Even if LIRs assign a single static IP in IPv4,
it's up to the ISP to assign /48 to these customers.
7.1(*) Use of existing IPv4 infrastructure
LIRs can justify their requested initial allocation size by the number
of their existing IPv4 users as well as the extent of their IPv4
network infrastructure.
>From this perspective LIRs are likely to be eligible for an initial
allocation criteria in case they;
- meet the current IPv4 allocation criteria AND
- receive the current IPv4 allocation as an LIR AND
- plan to tranfer the existing IPv4 infrastructure
or customers to IPv6
Note: this is just to provide an idea, and not guarantee the initial
allocation
However LIRs are still requested to provide their IPv6-ready equipment
information to ensure their plan for IPv6 services.
7.2 (*) Documentation required
When LIRs request their initial IPv6 address allocation to RIR/NIR,
LIRs are requested to provide designated request form as well as the
following information.
- Network diagram
- Network equipment information. This is to ensure LIR has a plan to
implement IPv6 ready infrastructure.
- Approximate deployment date.
- Service plan (Web hosting, Access service, etc)
7.2.a (*) Supplementary Document
When requesting an initial allocation to RIR/NIR, model/Vendor name of
LIR's network equipment is not mandatory but there may be a case that
RIR/NIR asks those information if LIRs require a plenty of pool address
such as CATV/ADSL operator.
7.2.1 Examples
Following is the example of the documentation required. These are
for reference for the ISPs.
- ADSL/Cable providers
+ Network diagram
+ CMTS information (Quantity, model name)
+ Approximate deployment date
+ The number of existing (or projected) customers
- mobile phone operators, GPRS
+ Network diagram
+ Network equipment information
+ Approximate deployment date
+ The number of existing (or projected) customers
- transit providers
+ Network diagram
+ Network equipment information
+ Approximate deployment date
+ The number of existing (or projected) customers
- multi-national enterprises
- educational institutions
+ Network diagram
+ Network equipment information
+ Approximate deployment date
+ The number of organizations to which LIRs assign /48s
7.3 Closed networks
APNIC will allocate global IPv6 address space to organization which
network is reachable or not reachable from global IPv6 Internet, if
its organization meets the conditions stated in current IPv6 policy,
[5.1.1 Initial allocation criteria], since it does not require global
route advertisement.
For example organizations below are likely to meet 5.1.1(c) in
the current IPv6 policy despite they are closed networks.
Therefore if they meet other criteria listed in 5.1.1, they are
eligible to obtain IPv6 addresses.
- An ISP which provides IPv6 services to other organization (company
or individual) but its network is closed within its ISP or
restricted ISPs such as peering partners.
- A large company who provides IPv6 connectivity to its group
companies or subsidiaries and its network is closed within itself.
7.4 NAT
RFC1631 describes Network Address Translation (NAT). NAT makes consume
fewer public IP address thereby assisting the goal of conservation.
However many drawbacks have been cited with the use of NAT, and the
goal of conservation is less important compared to IPv4, so that
APNIC policies do not require any ISP or Internet user to employ
Network Address Translation (NAT), as current IPv4 address policies
do not either.
8. Second opinion requests
When one single end site requires shorter prefix than /48 (e.g. /47 ,
/46...)for 2 years requirement, or it requires additional /48(s) after
its initial assignment, LIRs must follow Second opinion request
process prior to the assignment.
8.1 Documentation required
In addition to the designated request form, LIRs are requested to
provide RIRs/NIRs with the detailed network information as below;
8.1.1 Sub-Allocations
RIRs/NIRs do not require a Second Opinion Request for
sub-allocations to downstream ISPs. (Please see [9.
Subsequent allocations].) Nevertheless when LIRs are unsure how
much address space to sub-allocate, LIRs are recommended to ask
RIRs/NIRs for advice.
8.1.2 Assignments
LIRs must justify why multiple /48s are needed per single end site
by the following documentation but not limited to these.
- Network diagram
- Network equipment information
- Full details to justify multiple /48 assignments to an end-site
(e.g. the number of clients (PCs or other NW equipments) or
other information which LIRs think can justify multiple /48s)
9. Subsequent allocations
- An example of a typical ISP.
(1) 1st subsequent allocation
A typical ISP receives /32 that is 65,536 * /48s as an initial
allocation.
If this ISP allocates or assigns 7,132 * /48s to it's customers and
its POPs, this ISP has a right of the 1st subsequent allocation.
7,132 is from the HD-Ratio table ( Policy : Appendix A )
Example
assignments to POPs 326 * /48
assignments to end sites 6,500 * /48
assignments through downstream ISP 306 * /48
------------------------------------------------
total 7,132 * /48s
(2) Subsequent allocation (Example of the 2nd subsequent allocation)
This ISP receives additional /32 from an adjacent address block as
the second allocation. Now, this ISP has one /31 address block.
If this ISP allocates or assigns 12,417 * /48s including the
previous 7,132 * /48s to it's customers and its POPs, this ISP has a
right of the 2nd subsequent allocation.
12,417 is from the HD-Ratio table ( Policy : Appendix A )
- Utilization in case of Sub-allocation
Utilization is calculated based on the number of /48 assignments
which are registered in the registry database(*) including
/48 assignments through downstream ISPs. It is not based on the size
of sub-allocations to the downstream ISPs.
(*) needed clarified definition.
If a sub-allocation is made to a down stream ISP, but assignments
are not registered in the database, it will not considered utilized.
e.g.) /40 sub-allocation is made to a downstream ISP. 2*/48 is
assigned from this block. In this case, 2*/48 is considered as
utilized, not /40(256*/48).
So, LIRs should carefully consider and justify the sub-allocation
size'.
<note> In IPv4, Sub-allocations to downstream ISPs are considered as
assignment.
- RIRs/NIRs do not request to LIRs for a Second Opinion Requests (SOR)
for sub-allocations to downstream ISPs.
<note> In IPv4, To prevent LIRs from making unrealistic
sub-allocations, RIRs/NIRs have a policy requesting for an SOR,
so that RIRs/NIRs can see the details of the allocations.
- RIRs temporarily reserve 8 * /32 adjacent address blocks for each
organization. This space is worth /29. But unless each organization
obtains additional allocation, these spaces can be allocated to other
organizations based on the Space Allocation System.
http://xxx.xxx.apnic.net
--------------------------------------
9.1 Application of the HD ratio
(Merged into 9.)
--------------------------------------
10. Requesting a reverse delegation
- Responsibility of delegation
- When RIR allocates to LIR,
- Reserve lookup must be delegated to LIR.
- When LIR assigns to end site,
- Reserve lookup must be delegated to end site upon end site's
request.
- When LIR allocates to it's downstream ISP,
- Reserve lookup must be delegated to LIR.
- When downstream ISP assigns to end site
- Reserve lookup must be delegated from downstream ISP to end
site upon end site's request. It means it is downstream ISP
or end site's responsibility.
- Registration of each host
- Each host is recommended to be registered to the authorized DNS
server which is defined above.
-------------------------(under discussion)-------------
- Registration of each host
- It is not compulsory nor recomended because it's too hard to
register all addresses of all nodes without using stateless
autoconfiguration.
- Temporary addresses defined in RFC3041
- It is not compulsory nor recomended. The reason is same as
Registratoin of each host.
-------------------------(under discussion)----------
- Minimum size
- Minimum size of reverse delegation is /48.
- ip6.int. / ip6.arpa
- ip6.int is now deprecated for all organizations.
- Shifting from ip6.int. to ip6.arpa. is appreciated for all
organizations.
- If it is impossible to shift, the organization are requested to
have both environment.
11. Database registrations
- Definition of Database
In this policy, "database" means the Whois Databases of RIRs and NIRs.
At present, APNIC, RIPE-NCC, ARIN and LACNIC have databases.
These databases are accessible by not only RIRs but also any end site
on the IPv4 Internet.
- The organization responsible for registration
(1) Allocation
Each RIR is responsible for registering initial and subsequent
allocation information in a database. Typical example is the /32
or /31 allocations to ISPs.
(2) Assignment
(a) When an organization that is holding an address allocation
makes assignments, this organization is responsible for
registering the assignment. Typical example of this organization
is ISP.
(b) When an organization makes an assignment through downstream
ISP, this organization is responsible for registering the
assignment.
So, LIRs need some rules or contracts between downstream ISPs in
order to receive assignment information.
- Items to be registered
http://www.apnic.net/db/ref/attributes/attributes-inet6num.html
- Deadline of the registration
As soon as possible after allocating or assigning.
- Registration grater then /48
For example, the organization which has assigned /47 have to register
the /47 block in the database.
- Updating of the database
When some information is updated in the database, the organization
which has assigned it is responsible for updating the database.
----------------------------------------------------------------------
End of document
