[sig-policy]Call for comments: [prop-013-v001] Proposal to allow LIRs to

  • To: sig-policy-chair at apnic dot net, <sig-policy at apnic dot net>
  • Subject: [sig-policy]Call for comments: [prop-013-v001] Proposal to allow LIRs to managemultiple discreet networks under a single APNIC membership
  • From: Anne Lord <anne at apnic dot net>
  • Date: Thu, 9 Oct 2003 12:05:10 +1000 (EST)
  • List-archive: <http://www.apnic.net/mailing-lists/sig-policy/>
  • List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
  • List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
  • List-post: <mailto:sig-policy@lists.apnic.net>
  • List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>,<mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
  • List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>,<mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
  • Sender: sig-policy-admin@lists.apnic.net
      The Secretariat has received the following proposal from Dawn Martin
      for consideration and discussion at the next APNIC meeting in Kuala 
      Lumpur, Malaysia, 18-27 February 2004 (held in conjunction with APRICOT).
      (Please note, this proposal is updated version of the proposal posted 
      to this list earlier this week)
      Feedback and comment on this proposal from readers of this list
      is warmly invited.
      The proposal and other APNIC policy proposals can be found at:
      We look forward to your comments!
      Best wishes,
      APNIC Secretariat
      [prop-013-v001] Proposal to allow LIRs to manage multiple 
      discreet networks under a single APNIC membership.
      Version 1.0
      Proposed by: Dawn Martin
      Date: October 8 2003
      This proposal would provide LIRs with multiple APNIC membership accounts
      with a plan to simplify their procedures by combining their membership 
      accounts while maintaining APNIC's current operational requirements.
      The structure of many companies networks span more than one country and
      each of these companies must open multiple memberships 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 membership. Membership payments 
      become due at different times and cause additional processing expense 
      both to the LIR 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.
      Putting this proposal into policy would allow a member to manage their
      membership 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.
      LACNIC: Does not have a policy in place for this type of network at this
      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 issue additional IP address space to a 
      discrete network unless all the blocks sub-allocated to that network show
      utilization greater than 80% individually and as a whole.
      4.3 The organization must not sub-allocate a CIDR block larger than the
      current minimum allocation size of the RIR (currently /20 for APNIC region)
      to a new network.
      4.4 The organization must not sub-allocate an additional CIDR block larger
      than the current minimum allocation 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 sub-allocating a block larger than the minimum allocation size to
      an existing network the LIR should use the smallest allocation possible out
      of a larger reserved block. This requirement is to reduce the number of
      routes the LIR will announce from that autonomous system.
      4.6 The LIR must follow guidelines of RFC 2050 (or its replacement) and the
      policy of the granting RIR for allocations that are assigned or
      sub-allocated to downstream networks. This includes record keeping of IP
      address requests and network utilization documents for audits by the RIR.
      4.7 LIRs with 'multiple membership 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 LIR must record sub-allocations or assignments down to the current
      RIR bit boundary and record them in an approved RIR public database.
      4.9 The LIR must keep detailed records of how it has sub-allocated space to
      each discrete network. This should include the block sub-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 LIR 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 LIRs network.
      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.
      If this proposal is implemented this policy would go into effect three
      months after approval by the APNIC community.