JPNIC's contributions to the Internet community can be
made, with the support of JPNIC members.
○This document is invalid due to expiration.
Please note that this document merely serves as a reference to the
original document in Japanese, and all statements in the document will
take no real effect, including the that on the copyright.
It should also be noted that parts of the documents indicated in
Japanese characters may not be legible under the non-Japanese
environment.
-------------------------------------------------------------------------------
| Copyright notice for JPNIC open documents |
| |
| All documents contained herein are open documents provided by the |
| Japan Network Information Center (JPNIC) and are copyrighted, and all |
| rights are reserved by JPNIC. |
| |
| Any individual or institution is able to receive the documents from JPNIC, |
| upon payment of the delivery cost and handling fee. |
| |
| Permission is granted to any individual or institution to adapt, reproduce,|
| |
| or redistribute these documents, provided that this copyright notice is |
| retained. |
| |
| Japan Network Information Center |
| Fuundo Bldg. 1F, 1-2 Kanda-Ogawamachi, |
| Chiyoda-ku, Tokyo 101-0052, Japan |
-------------------------------------------------------------------------------
Policies for Address Space Management in JPNIC
Japan Network Information Center
Superceded on: 22 October 1999
Valid till : 31 December 2000
＊Outline of this document＊
This document is valid from 29 January 2000.
This document summarizes the policies for IP address assignment and
allocation in JPNIC.
Please read this document thoroughly first, and then read the series
of other JPNIC documents on address assignment.
＊Contents＊
0. Outline of this document
0.1 Configuration of this document
1. Introduction
2. Scope
3. Hierarchy of address space distribution
4. Definitions
4.1 Internet Registry (IR)
4.1.1 Regional Internet Registry (RIR)
4.1.2 National Internet Registry (NIR)
4.1.3 Local Internet Registry (LIR)
4.2 JPNIC members
4.3 Allocated and assigned address space
4.3.1 Allocation
4.3.2 Assignment
5. Goals of address space management
5.1 Goals
5.1.1 Uniqueness
5.1.2 Registration
5.1.3 Aggregation
5.1.4 Conservation
5.1.5 Fairness
5.2 Conflict of goals
6. Policy environment
6.1 Routability not guaranteed
6.2 Unpredictable growth rates
6.3 Collective responsibility
6.3.1 Appropriate customer agreements
6.3.2 Good faith
6.4 Impartiality
6.5 Varying levels of expertise
6.6 IP address not to be considered as property
6.7 Stockpiling discouraged
6.8 Evaluations to be based on efficient technologies
6.9 Minimum allocation size
6.10 Basic documentation
6.11 Confidentiality
7. Policies for allocations and assignments
7.1 Consistent address space management policies
7.2 Leasing of address space
7.3 Processing of requests dependent on correct documentation
7.4 Security and confidentiality
7.4.1 Access control for registration of information
7.5 Equitable processing of requests
7.6 General requirements for allocations
7.7 Slow start mechanism for first allocations
7.7.1 Exceptions to slow start
7.8 Criteria for subsequent allocations
7.8.1 No guarantee of contiguous allocations
7.9 Assignment window for JPNIC members
7.10 JPNIC members to use up allocations
7.10.1 Special circumstances - large assignments
7.11 Reservations not supported
7.12 Provider aggregatable addresses encouraged
7.12.1 Source of provider-independent address space assignment
7.13 Renumbering to promote aggregation
7.14 Private address
7.15 Estimation of assignment address usage
7.16 Organizations seeking address space from multiple IRs
7.17 Registration requirements
7.17.1 Updating registration details
7.17.2 Registering contact persons
7.18 Responsibility to maintain in-addr.arpa resource record
7.19 Validity of allocations and assignments
7.20 Transfer of address space
7.21 Effect of mergers and acquisitions of JPNIC members on allocation
7.22 Closure of members
8. Specific cases
8.1 Static assignment
8.1.1 Static dialup connections
8.1.2 Cable network
8.1.3 Virtual host
8.2 IP unnumbered
9. Acknowledgements
0. Outline of this document
This document describes JPNIC's policies on the allocation and
assignment of IP address (hereinafter "address").
Please read this document before reading other JPNIC documents
relating to address assignment.
This document does not describe address assignment request procedures
in detail. For details on each procedure, refer to the following
documents:
"IP Address Allocation/Return Request Process (For JPNIC Member)"
"IP Address Assignment Report Process (For JPNIC Member's Network)"
"IP Address Assignment Report Process (For User's Network)"
"JPNIC Evaluation Procedure for IP Address Assignment"
"IP Address Renumbering Application Process(For JPNIC Member's Network)"
"IP Address Renumbering Application Process(For User's Network)"
"IP Address Return Application Process"
The contents of this document are valid till the date specified at the
beginning of the document. After the "Valid till" date, refer to the
Revised Version of the document.
This document describes the situation of address management and
assignment as of September 1999, so the word "current" in this
document refers to September 1999.
When reading this document or any other related document, be sure to
check the "Valid till" date for validity.
0.1 Configuration of this document
This document is configured as follows:
・ Chapter 1 "Introduction"
Describes the purpose of JPNIC policies.
・ Chapter 2 "Scope"
Describes the extent covered by the descriptions and explanations in
this document.
・ Chapter 3 "Hierarchy of address space distribution"
Describes the hierarchical structure of address space distribution in
the Internet community.
・ Chapter 4 "Definitions"
Defines terms used in this document.
・ Chapter 5 "Goals of address space management"
Describes the goals of address space management.
・ Chapter 6 "Policy environment"
Describes various environment factors taken into consideration in
developing JPNIC policies.
・ Chapter 7 "Policies for allocations and assignments"
Describes JPNIC policies for allocations and assignments.
・ Chapter 8 "Specific cases"
Describes special cases of allocation and assignment.
1. Introduction
The Japan Network Information Center (hereinafter "JPNIC") is a
non-profit Regional Internet Registry that operates in Japan as a
confederation member under the authority of the Asia-Pacific Network
Information Center (APNIC).
As such, it is the organization responsible for distributing public
Internet address space and for developing and implementing policies
for the management of that distribution.
The policies described in this document have been developed by the
Internet community in the Asia-Pacific Region and Japan to be
implemented by JPNIC and all other Internet Registries functioning in
Japan.
Internet Registries operate in a self-regulating environment at
present, and the aim of these policies is to provide a clear framework
for the continued existence of that environment.
This document is written referring to the following document issued by
APNIC. The APNIC document is the upper-level document of this
document, and describes address space management policies for the
whole Asia-Pacific region, which all Internet registries including
JPNIC and JPNIC members should follow. Therefore, when the APNIC
document is modified in the future, this document will be changed
accordingly.
"Policies for address space management in the Asia-Pacific Region"
(http://www.apnic.net/drafts/ipv4policy-draftfinal.html)
2. Scope
This document describes policies for the responsible management of
global and public IPv4 address space for JPNIC and its members.
Specifically, this document focuses on the goals, assumptions and
policies relating to the allocation and assignment of address space.
In the past, address space was allocated by classes such as "Class A",
"Class B" or "Class C". However, since the introduction of Classless
Inter Domain Routing (CIDR) technologies, address space has been
allocated by prefixes such as [/19] or [/21].
This document deals only with issues relating to classless address
allocation and assignment.
3. Hierarchy of address space distribution
IP address is distributed in accordance with the hierarchical
structure described in RFC2050 (originally described in RFC 1466),
represented simply in Fig. 1.
+--------+
| IANA |
+--------+
|
+-----------+-----------+...........+.............+
| | | : :
+--------+ +--------+ +--------+ +..........+ +..........+
| ARIN | |RIPE NCC| | APNIC | : Potential future RIRs :
+--------+ +--------+ +--------+ +..........+ +..........+
|
+-----------+--+--------+
| | |
+------+ +-------+ |
| NIR | | JPNIC | | National Internet
+------+ +-------+ | Registries
| | (NIR) |
+------+--+ | |
| | | |
+------+ | +------+ +------+ Local Internet
| LIR | | | LIR | | LIR | Registries
+------+ | +------+ +------+
| | | |
+-----+ | | |
| | | | |
| | | | |
+----+ +----+ +----+ +----+ +----+
| EU | | EU | | EU | | EU | | EU | End-users
+----+ +----+ +----+ +----+ +----+
Fig. 1
In this hierarchy, IANA allocates address space to APNIC, to be
redistributed throughout the Asia-Pacific region. APNIC allocates
address space to JPNIC, which is one of the NIRs. JPNIC then allocates
address space to local Internet Registries (LIR) in Japan and also
delegates to them the authority to make assignments and allocations.
LIR assigns address space to its members and customers under the
guidance of JPNIC and in accordance with the policies and procedures
described in this document.
4. Definitions
The following terms and their definitions are of particular importance
to the understanding of the goals, environment and policies described
in this document.
4.1 Internet Registry (IR)
An Internet Registry (IR) is an organization that is responsible for
distributing IP address space to its members or customers and for
registering those distributions. IRs are classified according to their
primary function and territorial scope, within the hierarchical
structure depicted in Fig. 1 shown above.
The term IR includes APNIC and other Regional Internet Registries
(RIRs), JPNIC and other National Internet Registries (NIRs) and Local
Internet Registries (LIRs).
4.1.1 Regional Internet Registry (RIR)
Regional Internet Registries (RIRs) were established under the
authority of IANA to serve and represent large geographical regions.
The primary role of RIRs is to manage and distribute address space
within their respective regions.
Currently, there are three RIRs: APNIC, RIPE NCC and ARIN. Additional
RIRs may be established in the future, but the total number of RIRs is
expected to remain relatively small.
4.1.2 National Internet Registry (NIR)
A national Internet Registry (NIR) is an IR that primarily allocates
address space to its members (LIR), which are generally Internet
Service Providers (ISPs) organized at a national level.
Although the NIR is comprised of ISPs, NIRs themselves do not operate
as ISPs. NIRs are expected to maintain neutrality with respect to the
interests of their constituent ISPs.
JPNIC acts as an NIR.
4.1.3 Local Internet Registry (LIR)
A Local Internet Registry (LIR) is an IR that primarily assigns address space
to the users of the network services that it provides. LIRs are generally ISPs;
their customers are other ISPs and possibly end-users.
JPNIC members are LIRs.
4.2 JPNIC members
The term "JPNIC member" in this document refers to those who are
delegated by JPNIC the authority to assign addresses.
4.3 Allocated and assigned address space
For the purposes of understanding the address space policies of JPNIC,
it is important to make a clear distinction between the terms
"allocation" and "assignment".
4.3.1 Allocation
"Allocation" means to distribute address space to an IR for the
purpose of redistribution.
4.3.2 Assignment
"Assignment" means that an IR distributes a part of or all the
allocated address spaces to end users for the purpose of usage in the
end user's network. This address space is also called assigned address
space when the IR uses it for its own network. These address spaces
include addresses pooled to be used for dynamic assignment of dialup
connections, etc.
Assigned address space is used only for the specific purpose declared
by an end user and should not be sub-allocated or sub-assigned.
5. Goals of address space management
5.1 Goals
The goals described here have been formulated by the Internet
community and reflect the mutual interests of all members of that
community in ensuring that the Internet is able to function and grow
to the maximum extent possible.
It is JPNIC's primary duty, as a custodian of a public resource, to
ensure that these goals are met within Japan. JPNIC wishes to do this
by providing guidance and leadership for JPNIC members, so that they
can develop and implement responsible policies and practices.
Every JPNIC member should take responsibility and ensure that these
goals are met within the scope of their activities.
5.1.1 Uniqueness
Every assigned and allocated address space must guarantee uniqueness,
worldwide.
This is an absolute requirement for ensuring that every public host on
the Internet can be uniquely identified.
5.1.2 Registration
Assignment and allocation of Internet address space should be
registered in a disclosed registry database, which is accessible to
all members of the Internet community.
This is necessary to ensure uniqueness and to provide reference
information used to solve Internet problems encountered by people at
all levels including RIRs, IRs and end users.
It also reflects the idea in the Internet community that all
custodians of public resources, such as public address space, should
be identifiable.
5.1.3 Aggregation
Wherever possible, address space should be distributed in a
hierarchical manner, according to the topology of network
infrastructure.
This is necessary to permit the aggregation of routing information and
limit the expansion of Internet routing tables.
5.1.4 Conservation
To maximize the lifetime of the limited Internet address space
resource, addresses must be distributed according to the amount
actually needed and on the basis of immediate use.
Therefore, stockpiling of address space and making reservations for
customers must be avoided.
Conservation also implies efficiency. Therefore, all users of address
space should adopt techniques such as Variable Length Subnet Masking
(VLSM) and appropriate technologies, which ensure that address space
is not used wastefully.
5.1.5 Fairness
All policies and practices relating to the use of public address space
should apply fairly and equitably to all existing and potential
members of the Internet community, regardless of their location,
nationality, size or any other factor.
5.2 Conflict of goals
The goals of conservation and aggregation of address space often
conflict with each other.
Moreover, the description of "5.1 Goals" may occasionally be in
conflict with the interests of individual IRs and end users.
Therefore, IRs evaluating requests for allocation and assignment of
address space must carefully analyze all relevant considerations and
must seek to balance the needs of the applicant with the needs of the
Internet community as a whole.
The policies described in this document are intended to help IRs
balance these needs in a consistent and equitable manner. Full
documentation of, and transparency within, the decision-making process
must also be maintained in order to achieve this objective.
6. Policy environment
Apart from the goals described in "5. Goals of address space
management", other factors such as the expectations of the Internet
community, the current administrative structures, and technological
constraints all form an operating environment that shapes JPNIC
policies.
Changes in the environment may happen quickly or in unpredictable ways.
One important role for JPNIC, with respect to its members, is to
monitor any changes in the environment and communicate any
implications the changes may have for JPNIC policy.
This section describes the factors in the current operating
environment that have been most important in determining current JPNIC
policies.
6.1 Routability not guaranteed
Routability of address space can not be guaranteed.
The reason for this is that transit providers worldwide implement
route filtering based on prefix length in order to reduce the number
of globally advertised routes.
From this point of view, provider-independent address is likely to
have the lowest routability on the Internet.
Therefore, JPNIC policy should encourage users seeking provider
aggregatable address space to request it from providers, rather than
requesting provider-independent address assignments from JPNIC or
APNIC directly.
6.2 Unpredictable growth rates
Early strategies for distributing address space did not anticipate the
explosive growth of the Internet and the consequent problems of
scalability that arose both in the amount of address space available
and the routing of that address space.
JPNIC recognizes the fact that policies and procedures for the
management of address space should take into account past experience
and seek to anticipate problems that may arise in the future.
6.3 Collective responsibility
JPNIC recognizes that it shares with its members and their customers a
collective responsibility to ensure a manageable and scalable growth
of the Internet.
JPNIC recognizes that it must take a leading role in encouraging and
assisting its members to develop policies and practices of address
space management and to make decisions consistent with the goals
described in "5. Goals for address space management".
6.3.1 Appropriate customer agreements
IRs should implement appropriate agreements that are consistent with
the goals and policies described in this document, with their members
and customers.
6.3.2 Good faith
The relationship between JPNIC and JPNIC members should be based on an
implicit trust that the information, network plans and other
documentation provided by them are genuine and accurate.
6.4 Impartiality
JPNIC represents the interests of the Internet community in general
and the Internet community of Japan in particular.
JPNIC applies its policies fairly and equitably with respect to all
JPNIC members, regardless of the size or geographic location of the
organization, or any other factor.
6.5 Varying levels of expertise
The staff of IRs and end users have varying levels of experience and expertise.
JPNIC implements its policies equally for all members, and allows for
levels of assistance and monitoring appropriate to each member.
This assistance and monitoring is intended to ensure a consistent
approach to address space management throughout the Internet community
of Japan.
6.6 IP addresses not to be considered as property
It is contrary to the stated goals and is not in the interests of the
Internet community as a whole for address space to be considered as
property.
JPNIC policies will reflect this recognition and encourage all members
of the Internet community to regard address space as a scarce, shared
resource that should only be distributed responsibly and according to
demonstrated need.
More specifically, as portability of address space is detrimental to
the goals of aggregation and efficiency, JPNIC policies should require
JPNIC members to provide services to their customers based on the
understanding that address space is "leased" rather than "owned".
6.7 Stockpiling discouraged
Stockpiling of addresses is detrimental to the goals of conservation
and fairness.
JPNIC policies should discourage stockpiling and encourage efficient
distribution of address space on the basis of immediate demonstrated
need.
6.8 Evaluations to be based on efficient technologies
If appropriate technologies exist to allow the efficient, hierarchical
distribution of address space in particular situations, then end-users
should adopt those technologies in accordance with current best
practice.
Organizations that are not planning to use the most efficient
technologies must re-consider their usage of the technology thoroughly
and provide justification for their difficulty in usage.
Issues of administrative convenience are not sufficient to justify the
use of inefficient technologies. However, JPNIC policies acknowledge
that factors such as the scale and complexity of networks and the need
for operational stability can justifiably delay the deployment of
efficient technologies.
JPNIC will cooperate with its members and the broader Internet
community to define and develop current best practice recommendations
relating to Internet addressing.
6.9 Minimum allocation size
The goals of aggregation and conservation will often conflict.
As a consequence, it will be necessary to set a minimum size of
address space from the point of view of conservation and practical
size from the point of view of aggregation for allocation of address
space.
The address space size considered as practical for the global Internet
at present is /19 (8,192 addresses), however, JPNIC adopts a smaller
size of /22 (1,024 addresses) as the minimum allocation size and
reserves /19 including /22 for its members. Members may advertise this
/19 on the global Internet for a while.
However, it is considered that practical address space size will
change according to evolving technological and administrative
conditions, therefore, this measure may be altered from time to time
according to changes in the situation.
6.10 Basic documentation
In order to properly evaluate requests for addresses, JPNIC members
are asked to submit detailed documentation related to relevant
networks.
Such documentation may include network-engineering plans, subnetting
plans, descriptions of network topology and descriptions of network
routing plans.
All documentation should conform to a consistent criterion and any
estimates and predictions that are documented must be realistic and
justifiable.
6.11 Confidentiality
JPNIC members must analyze information about the activities of
organizations and individuals seeking address space and such
information may be highly confidential in nature.
Therefore, JPNIC shall apply and reinforce methods of protecting the
confidentiality of the information of members, business of their
customers and individuals, and provide service in a way that reflects
their trust in the members and customers.
7. Policies for allocations and assignments
As was emphasized in "1. Introduction", JPNIC policies are based on
APNIC policies, which are a consensus of opinion in the Internet
community and the whole Asia-Pacific Region.
JPNIC's role is to identify and disseminate these policies. JPNIC does
not seek to dictate policy decisions to its members, but rather to
provide a model for consistent and responsible practice throughout
Japan.
7.1 Consistent address space management policies
JPNIC members should adopt policies that are consistent with the
policies formulated by the Internet community, as described in this
document.
7.2 Leasing of address space
JPNIC will allocate IP addresses based on the idea of "leasing", with
such leases to be of specific limited duration (normally one year).
Lease conditions are applied at the time of entering or renewing the
lease. This is based on JPNIC policy related to allocation and
assignment of resources.
It is possible to renew a lease, when the following two conditions are met:
(a) The original basis of the allocation remains valid, and
(b) Registration requirements relating to that allocation have been
fulfilled at the time of renewal.
When a lease is renewed, the new lease will be governed by the
applicable resource allocation policies and lease renewal policy at
the time of renewal.
Changes in the conditions of leases will be subject to a certain
defined period of notice, except in exceptional circumstances
recognized by a consensus of JPNIC members.
7.3 Processing of requests dependent on correct documentation
JPNIC will only process requests that have been completely and properly documented.
If the documentation contains errors or omissions, JPNIC will advise
the applicant of this as soon as possible. JPNIC may also request
further information or clarification of relevant issues that are not
made clear in the initial documentation.
JPNIC will then proceed to process the request as soon as the
applicant has made a satisfactory response to JPNIC's questions. This
is the same when there are no omissions or errors in the
documentation.
JPNIC must consistently make every effort to maintain a reliable level
of service when processing requests.
7.4 Security and confidentiality
JPNIC will maintain systems and practices that protect the
confidentiality of all information relating to the commercial and
infrastructure operations of all members and their customers. All
JPNIC staff or agents are employed based upon explicit conditions of
confidentiality.
7.4.1 Access control for registration of information
JPNIC plans to provide access control mechanisms in the
database. However, it is the responsibility of JPNIC members and end
users to utilize such mechanisms.
7.5 Equitable processing of requests
JPNIC deals with all requests strictly in the order in which it
receives the proper documentation.
All members are to be treated equitably, regardless of geography, size
or any other consideration, JPNIC will not in any circumstance provide
for special treatment or make exceptions to the standard order of
request processing.
JPNIC will seek to process all requests within a consistent time and
will maintain a request ticketing system to assist with the efficient
management of requests.
7.6 General requirements for allocations
All requests to JPNIC for allocations of address space must be
supported by documentation that describes the network infrastructure
of JPNIC members making the request and the intended usage of the
address space requested.
JPNIC processes the request based on the documentation, all address
spaces currently held by the JPNIC member and assignment history in
the past.
7.7 Slow start mechanism for first allocations
JPNIC will apply a slow start mechanism for all new JPNIC members.
The first allocation that JPNIC applies will be of the size shown in
"6.9 Minimum allocation size".
The slow start policy is used by many other IRs apart from JPNIC to
prevent the possibility of large blocks of addresses allocated by RIRs
and NIRs remaining unassigned.
JPNIC will implement this slow start mechanism in a consistent and
fair manner for every JPNIC member, and will apply the same principles
and standards to every applicant for address space.
7.7.1 Exceptions to slow start
In exceptional circumstances, the JPNIC member may receive a greater
initial allocation than the regulated size. This may happen if the
member can provide sufficient detailed substantiating documentation
showing that the member's immediate need for network addresses exceeds
the standard size of slow start allocation.
Such documentation may include documents indicating that the member
needs to have addresses for a network immediately such as for receipt
of purchase of equipment, purchase orders, and signed project
contracts.
7.8 Criteria for subsequent allocations
JPNIC members may request subsequent allocation if necessary after
receiving the first allocation.
All subsequent allocations will depend on the evaluation of the JPNIC
member's past allocation result, address space usage plan, assignment
result and assignment ratio and the degree of compliance with JPNIC
policies.
The assignment ratio is the ratio of space actually assigned for
allocations that JPNIC has received in the past.
JPNIC will evaluate these and carry out subsequent allocations of
address space to the JPNIC member.
Then, the size of address space to be allocated will be determined
considering the actual assignment results for the member in the past.
7.8.1 No guarantee of contiguous allocations
JPNIC will attempt to make subsequent allocations of address space
contiguous with previous allocations.
However, because it can not reserve address space, JPNIC can not
guarantee that contiguous allocations will be possible in any case.
7.9 Assignment window for JPNIC members
In order to assist JPNIC members in understanding JPNIC policies and
[5. Goals of address space management] and to act in compliance with
them, JPNIC will apply a mechanism called an "assignment window".
An assignment window refers to the maximum number of addresses that a
JPNIC member can assign without seeking allocation from JPNIC. When a
JPNIC member wishes to make an assignment that exceeds its assignment
window, the member must first submit an assignment evaluation request
to JPNIC before assignment.
All new JPNIC members will start with an assignment window of zero,
meaning that all proposed assignments must first be approved by JPNIC.
JPNIC will regularly assess the proficiency of the staff of each JPNIC
member in making allocations or assignment evaluation requests
efficiently, and reinvestigate the size of the assignment window. As
the proficiency of the JPNIC member staff increases, JPNIC will raise
the size of the assignment window.
The maximum size of the assignment window for JPNIC members is /19
(8,192 addresses).
If, due to the training of new staff or other relevant circumstances,
the proficiency of the staff of a JPNIC member should not meet the
standards required by JPNIC, then JPNIC may temporarily reduce the
assignment window of the JPNIC member.
7.10 JPNIC members to use up allocations
JPNIC will not make a new allocation to a JPNIC member if more than
eighty percent of the total address space from all allocations held by
that JPNIC member is currently unassigned.
7.10.1 Special circumstances - large assignments
If more than eighty percent of the total address space from all
allocations held by a JPNIC member is currently unassigned, but the
JPNIC member needs to make a single assignment that is larger than the
amount of space remaining, then it may request a new allocation from
JPNIC.
7.11 Reservations not supported
When a JPNIC member wishes to assign address space for customers, it
must make the assignments from any address space it currently
holds. When evaluating an allocation request, JPNIC will consider
space reserved by the JPNIC member for other customers as unassigned
address space.
7.12 Provider aggregatable addresses encouraged
JPNIC makes all allocations as "provider aggregatable" (hereinafter
"PA"), on the understanding that assignments should be made on a lease
basis.
In the interests of the goal of aggregation, JPNIC policy requires
JPNIC members to enter into agreements with their users and customers
specifying that the end-user will hold those assignments only for as
long as the end-user remains a customer of that JPNIC member.
PA assignments require that if the end-user changes service providers,
they should return the space assigned to them by the first JPNIC
member, obtain an assignment from a new JPNIC member and renumber into
that JPNIC member's address block.
There will be cases where usage of address space independently from a
provider (provider-independent, hereinafter "PI") is applicable,
however, all requests for PI address space should be justifiable on
strong technological rather than administrative grounds.
7.12.1 Source of provider-independent address space assignment
Only APNIC is authorized to make PI assignments, in the Asia-Pacific Region.
Organizations that need PI and can show justification for it may
either request their address space assignment from APNIC via JPNIC or
seek the address space directly from APNIC.
7.13 Renumbering to promote aggregation
End users who hold multiple non-aggregatable prefixes should replace
PA address space with single aggregatable prefixes and return those
addresses.
7.14 Private address space
JPNIC encourages the use of private address space for addressing
networks that will either be operated behind a firewall or not be
connected to the Internet.
7.15 Estimation of assignment address usage
Requests for assignments must be supported by usage estimates based on
needs occurring immediately after assignment and projected future
needs. The estimate should be verified by extremely reliable
standards. The estimates should be made for the following periods:
within three months, within six months and within one year.
Assignments will be based on the estimate that 25% of the address
space will be used within 6 months and 50% of them will be used within
1 year.
7.16 Organizations seeking address space from multiple IRs
JPNIC policy requires that organizations obtain their address space
from only one IR at a time.
In the event that an organization is requesting address space from
multiple IRs, the organization making the request must declare all the
address space it currently holds, regardless of the source of the
assignment.
Furthermore, organizations making concurrent requests to more than one
IR must declare the details of all those requests.
However, in certain circumstances (for example, where an organization
is multi-homed) strong technical reasons may make it appropriate for
an organization to receive address space from more than one provider.
For the purposes of this section, a parent organization and its
subsidiaries will generally be considered to be a single organization.
Exceptions may arise in cases where the parts of the organization are
corporations and maintain fully independent network infrastructures,
and are routed under different autonomous system numbers, or otherwise
demonstrate a justified need to obtain address space from more than
one IR.
7.17 Registration requirements
At the time of making assignment of an address, JPNIC members must
properly register all information related to the assignment in the
JPNIC whois database.
At the time of making allocation, JPNIC must properly register all
information related to the allocation in the whois database of APNIC,
which is the upper-level organization.
The information in the whois database is necessary for Internet
troubleshooting and provides for a level of reliability and
transparency that is of benefit to the entire Internet community.
7.17.1 Updating registration details
JPNIC members must update the JPNIC whois database when any of the
registration information is changed.
It is the responsibility of members to maintain up-to-date
registration information, however, members may formally delegate this
responsibility to the end users as a condition of the original
assignment.
7.17.2 Registering contact persons
Registration of contact persons is a vital part of responsible address
space management.
The administrative contact must be someone who represents the
organization.
The technical contact need not be physically located at the site of
the network, but must be the person who is responsible for the
day-today operation of the network.
7.18 Responsibility to maintain an in-addr.arpa resource record
JPNIC members should maintain an in-addr.arpa resource record related
to the network of the customer for assignments smaller than /24.
7.19 Validity of allocations and assignments
All allocations or assignments of address space are valid only while
the standard used for allocation or assignment is valid.
If an allocation or assignment is made for a specific purpose and the
purpose no longer exists, then the allocation or assignment is no
longer valid.
If it is found that allocation or assignment is made based on false or
incomplete information, such allocation or assignment is no longer
valid. In this case, the addresses must be returned to the appropriate
IR.
7.20 Transfer of address space
Sale or unauthorized transfer of address space is not permitted. Such
transfer is regarded as invalid.
The organization holding the address space through such transfer must
return the addresses to the appropriate IR.
7.21 Effect of mergers and acquisitions of JPNIC members on allocation
After mergers, sales or acquisitions of JPNIC members, JPNIC will
check the state of all allocations held by the new organization (if
there are multiple organizations, multiple relevant organizations),
and it will consider the actual effect on the infrastructure of the
relevant organization accordingly.
In cases where more than two infrastructures of JPNIC members are
merged as the actual effect of mergers, sales and acquisitions, JPNIC
will not allocate addresses continuously to both networks
respectively. In this case, the membership contracts of the JPNIC
members included become invalid.
In this case, JPNIC requests the complete disclosure of the
information of address space held by all relevant JPNIC members when
it checks the state of allocation. If such disclosure does not take
place, allocation is considered invalid and JPNIC requests the return
of such addresses.
7.22 Closure of members
If a JPNIC member ceases to function as an IR, all of its unassigned
address space should be returned to JPNIC. Furthermore, it is the
responsibility of the member (or any liquidator or administrator
appointed to wind up the member's business) to advise all of its
customers of the closure and encourage them to make arrangements to
renumber into address space from a new JPNIC member. The new JPNIC
member should then notify the IR of the new arrangements so that the
previous assignment can be returned to the pool of unassigned address
space.
8. Specific cases
The policies described in this section relate to specific types of
allocations and assignments and are based on current best practice
relating to the deployment of current technologies.
8.1 Static assignment
JPNIC policy strongly discourages the static assignment of IP
addresses for each service.
All plans for future static assignments should be justified on
specific, detailed technological grounds.
Issues of administrative convenience will not be sufficient to justify
such assignments.
In evaluating such static address assignment requests, it should be
investigated whether dynamic assignment of addresses is actually
applicable to the relevant network of the applicant.
8.1.1 Static dialup connections
JPNIC policy strongly discourages assignments based on the use of
addresses by static dialup methods.
Users planning such assignments must first investigate whether it is
technically feasible to use dynamic assignment technology.
Dynamic address assignment methods are normally applicable to dialup.
8.1.2 Cable network
Cable based infrastructures represent an exception to this policy.
JPNIC policy recognizes that although dynamic technologies such as
DHCP can be employed, the high availability demanded by customers
means that often no significant saving of IP addresses will result.
8.1.3 Virtual host
Recent developments in some protocols such as HTTP 1.1 have eliminated
the need for one-to-one mapping of virtual hosts. JPNIC policy
strongly encourages any organization considering the use of virtual
hosts to implement systems that are compatible with current versions
of these protocols.
8.2 IP unnumbered The use of [IP unnumbered] is encouraged when a
customer has no multi-home connection but has only a single
connection, routes statically and uses routers and software compatible
with "IP unnumbered".
This configuration allows IP processing on a serial interface without
the need to assign an explicit IP address for point-to-point links.
Not only does this meet the conservation goal, but also on an
operational level it helps to minimize the size of the routing table
inside the ISP and therefore, assists in scaleable network growth.
9. Acknowledgements
We would like to express our gratitude to APNIC who have given us
valuable comments for the creation of this document.
End of document
＊Related documents＊
"IP Address Allocation/Return Request Process (For JPNIC Member)"
http://www.nic.ad.jp/en/regist/ip/translation/e-ip-addr-alloc-process.html
"IP Address Assignment Report Process (For JPNIC Member's Network)"
http://www.nic.ad.jp/en/regist/ip/translation/e-ip-addr-assign-infra-process.html
"IP Address Assignment Report Process (For User's Network)"
http://www.nic.ad.jp/en/regist/ip/translation/e-ip-addr-assign-user-process.html
"JPNIC Evaluation Procedure for IP Address Assignment"
http://www.nic.ad.jp/en/regist/ip/translation/e-ip-addr-evaluation-process.html
"IP Address Renumbering Application Process (For JPNIC Member's Network)"
http://www.nic.ad.jp/en/regist/ip/translation/e-ip-addr-renumber-infra-process.html
"IP Address Renumbering Application Process (For User's Network)"
http://www.nic.ad.jp/en/regist/ip/translation/e-ip-addr-renumber-user-process.html
"IP Address Return Application Process"
http://www.nic.ad.jp/en/regist/ip/translation/e-ip-addr-return-form.html
"Policies for address space management in the Asia-Pacific Region"
http://www.apnic.net/drafts/ipv4policy-draftfinal.html
