Your IP address could not be determined at this time.

Draft Policies and Proposals

Policy 2001-6: Multiple Discrete Networks - Single Maintainer ID
Policy Proposal Evaluation Status: Author
Adopted - NRPM Section 4.5  
Discussion Tracking
Mailing List:
Formal introduction on PPML on 28 September 2001
Public Policy Mailing List
ARIN Public Policy Meeting: ARIN VII
ARIN VIII
ARIN Advisory Council: 30 October 2001
09 November 2001
ARIN Board of Trustees: 11 December 2001
22 January 2002
Revisions Implementation
None 2002 

Proposal

Organizations with multiple discrete networks desiring to request new or additional address space under a single maintainer ID must meet the following criteria:

  • The organization shall be a single entity, and not a consortium of smaller independent entities.
  • The organization must have been previously granted address space by an RIR. This policy does not apply to organizations with only legacy address space.
  • The organization must have multiple (at least two) discrete multi-homed networks.
  • The organization must have compelling criteria for creating discrete networks.
  • The organization must show greater than 50% utilization of the last block of address space granted to them by the RIR.
  • The organization must show greater than 50% utilization of all previously allocated address space.
  • The organization must not allocate additional space to discrete network unless all the blocks allocated to that network show utilization greater than 80% individually and as a whole.
  • The organization must apply for this policy to be applied to its existing account.

Some organizations have requirements for multiple discrete networks that need individual address allocations. Discrete networks must often have separate unique globally routable address space and will often grow at different rates. In order for organizations with multiple discrete networks to request additional address space under a single maintainer ID, the organization must use the following criteria:

  • The organization should be a single entity, and not a consortium of smaller independent entities.
  • This policy applies only to organizations that have been previously granted address space by an RIR. This policy does not apply to organizations with only legacy address space.
  • The organization must have multiple (at least two) discrete multi-homed networks.
  • The organization must have compelling criteria for creating discrete networks. Examples:
    • regulatory restrictions for data transmission
    • geographic distance and diversity between networks
    • autonomous multi-homed discrete networks
  • The organization must apply for this policy to be applied to their account.

These organizations must adhere to the following guidelines when requesting additional address space:

  • 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.
  • 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.
  • The organization must not allocate a CIDR block larger than the current minimum assignment size of the RIR (currently /20 for ARIN) to a new network.
  • The organization must not allocate an additional CIDR block larger than the current minimum assignment size of the RIR (currently /20 for ARIN) 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.
  • When allocating a block larger than the minimum assignment size to an existing network the organization should use the smallest allocation possible out of a larger reserved block. This requirement is to reduce the number of routes the organization will announce from that autonomous system.
  • The organization 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.
  • Organizations with 'multiple maintainers' should request that this policy apply to their accounts, their existing allocations be merged, and that additional allocations will fall under this policy.
  • The organization must record allocations or assignments down to the current RIR bit boundary (currently /29 for ARIN) and record them in an approved RIR public database.
  • The organization 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 (Example: routing registry, RWhois, or SWIP).

 

Advanced Search

Relevant Links