[sig-policy]Combining
I would like to submit the following proposal for feedback and
discussion in the SIG policy forum. As this is my first proposal sent
into APNIC please let me know if this is not the proper format.
Regards,
Dawn Martin
UUNet - IP Planning & Policy Analyst
v886-4796
(703)886-4797
dawn.martin at mci dot com
Summary
This proposal would provide multi-account ISPs with a plan to simplify their
procedures by combining their accounts while maintaining APNIC's current
operational requirements.
Background
The structure of many companies networks span more than one country and each
of these companies must open multiple accounts with APNIC to provide their
network with IP addresses. The problem with this is that many of these
networks are managed by the same people who have to access different
information for each account. Account payments come due at different times
and cause additional processing expense both to the ISP and to APNIC.
The idea of this was known as an ISP confederation but was dissolved in 1998
due to the policy framework not having vital APNIC procedures integrated
into it.
Motivation
Putting this proposal into policy would allow a member to manage their
accounts as a single resource. This would reduce billing complexity as well
as implement a single set of guidelines to be set for their entire network.
Multiple allocations would continue, as this is integral for routing
purposes.
Current Status (including other RIRs)
ARIN has a similar policy in place: Ratified Policy 2001-6: Multiple
Discrete Networks -- Single Maintainer ID
RIPE: Does not have a policy in place for this at this time.
Proposal
4.1 When applying for additional address space from an RIR for new networks
or additional space for existing networks the organization must show greater
than 50% utilization for the last block granted by the RIR and their
allocations as a whole.
4.2 The organization must not allocate additional space to a discrete
network unless all the blocks allocated to that network show utilization
greater than 80% individually and as a whole.
4.3 The organization must not allocate a CIDR block larger than the current
minimum assignment size of the RIR (currently /20 for APNIC region) to a new
network.
4.4 The organization must not allocate an additional CIDR block larger than
the current minimum assignment size of the RIR (currently /20 for APNIC's
region) to an existing network, unless previous growth rates for that
network indicate that it is likely to utilize a larger CIDR block before the
time the organization will be requesting an additional block from the RIR.
4.5 When allocating a block larger than the minimum assignment size to an
existing network the ISP should use the smallest allocation possible out of
a larger reserved block. This requirement is to reduce the number of routes
the ISP will announce from that autonomous system.
4.6 The ISP must follow guidelines of RFC 2050 (or its replacement) and the
policy of the granting RIR for allocations that are assigned or allocated to
downstream networks. This includes record keeping of allocation requests and
network utilization documents for audits by the RIR.
4.7 ISPs with 'multiple accounts' should request that this policy apply to
them, their existing allocations be merged, and that additional allocations
will fall under this policy.
4.8 The ISP must record allocations or assignments down to the current RIR
bit boundary and record them in an approved RIR public database.
4.9 The ISP must keep detailed records of how it has allocated space to each
discrete network. This should include the block allocated, any reserved
blocks, and date of allocation/reservation. The discrete network allocation
information should also be present in a public database.
4.10 An assignment window will be assigned to the ISP and will need to be
followed for their entire network. Second opinion requests will need to be
sent to APNIC for review. This is to include blocks of addresses that are
assigned to new or existing pools within the ISPs network.
Fees
The IP addresses from all combined resources would be taken into account
when assessing the membership tier for the organization upon the renewal of
their membership.
Implementation
If this proposal is implemented this policy would go into affect three
months after approval by the APNIC community.
References:
http://www.arin.net/policy/2001_6.html
http://www.ripe.net/ripe/wg/lir/lir-actions.html