Re: [sig-policy] prop-057-v002: New version

  • To: <sig-policy at lists dot apnic dot net>
  • Subject: Re: [sig-policy] prop-057-v002: New version
  • From: "Jason Bailey" <jason.bailey at staff.westnet dot com dot au>
  • Date: Mon, 18 Feb 2008 11:37:10 +0900
  • Delivered-to: sig-policy at mailman dot apnic dot net
  • In-reply-to: <47B42EFD.6030808 at psg dot com>
  • List-archive: <http://mailman.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>
  • References: <47B42EFD.6030808@psg.com>
  • Thread-index: AchvAkSNOzCVmrj5QbyB6dOwmJsNqwC1MnBQ
  • Thread-topic: [sig-policy] prop-057-v002: New version
    • 
      It should assumed that any organisation with an IPv4 allocation also
      requires an IPv6 allocation, if only to ensure connectivity for existing
      IPv4 hosts as IPv6 becomes ubiquitous.
      
      Requiring a detailed plan for assignments seems rather redundant.
      
      
      Regards,
      Jason
      ____________________________________
      
      Jason Bailey
      IP Services
      Westnet
      
      
      -----Original Message-----
      From: sig-policy-bounces at lists dot apnic dot net
      [mailto:sig-policy-bounces at lists dot apnic dot net] On Behalf Of Randy Bush
      Sent: Thursday, 14 February 2008 9:07 PM
      To: sig-policy at lists dot apnic dot net
      Subject: [sig-policy] prop-057-v002: New version
      
      Dear SIG members
      
      The 'Proposal to change IPv6 initial allocation criteria' has been
      revised by the authors in response to community feedback on the Policy
      SIG mailing list. Changes have been made to sections 1 and 4 of the
      proposal.
      
      This new version of the proposal will be presented during the Policy SIG
      sessions at APNIC 25 in Taipei, Taiwan, 25-29 February 2008.
      
      The proposal's history can be found at:
      
            http://www.apnic.net/policy/proposals/prop-057-v002.html
      
      We invite you to review and comment on the revised proposal on the
      mailing list before the meeting.
      
      The comment period on the mailing list before an APNIC meeting is an
      important part of the policy development process. We encourage you to:
      
            - Ask the proposer questions if anything in the proposal is
              unclear
            - Point out advantages and disadvantages you see in the proposal
            - State whether you support or oppose the proposal
      
      Mailing list discussions will be taken into account when the proposal is
      discussed at the upcoming APNIC meeting. So please make sure you have
      your say.
      
      APNIC Policy SIG Chairs
      Toshiyuki Hosaka
      Randy Bush
      Jian Zhang
      
      
      ________________________________________________________________________
      
      prop-057-v002: Proposal to change IPv6 initial allocation criteria
      ________________________________________________________________________
      
      
      Authors:     Toshiyuki Hosaka, JPNIC
                    <hosaka at nic dot ad dot jp>
      
                    Izumi Okutani, JPNIC
                    <izumi at nic dot ad dot jp>
      
      Version:     2
      
      Date:        14 February 2008
      
      
      1. Introduction
      ---------------
      
      This proposal is intended to enable current LIRs with existing IPv4
      allocations to receive the IPv6 allocation they need, yet maintain the
      criteria which is still effective for organizations without
      IPv4 address allocations.
      
      It seeks to remove barrier from current IPv6 initial allocation criteria
      by adding one condition which enables current LIRs with IPv4 allocations
      to receive IPv6 initial allocations without a plan for making 200
      assignments.
      
      
      2. Summary of the current problem
      ---------------------------------
      
      Current IPv6 policy requires LIRs to provide a plan for 200 assignments
      before they can qualify for an initial allocation of
      IPv6 address space.
      
      Some JPNIC members have pointed out that having a fixed number of
      planned assignments in this criteria makes it feel like an obligation
      that must be met. Therefore, it is becoming a barrier preventing LIRs
      from requesting IPv6 allocations.
      
      As the exhaustion of the IPv4 free pool approaches and IPv6 adoption is
      promoted, the plan for 200 assignments is an unnecessary barrier to IPv6
      allocation requests that should be removed.
      
      
      3. Situation in other RIRs
      -----------------------
      
      All RIRs except APNIC no longer require a mandatory plan for 200
      assignments.
      
      The current IPv6 initial allocation criteria (in relation to assignment
      requirements) in each region are below:
      
      
           - ARIN
      
               ...be an existing, known ISP in the ARIN region or have a plan
               for making at least 200 /48 assignments to other organizations
               within five years.
      
           - AfriNIC
      
               ...show a reasonable plan for making /48 IPv6 assignments to
               end sites in the AfriNIC region within twelve months. The LIR
               should also plan to announce the allocation as a single
               aggregated block in the inter-domain routing system within
               twelve months.
      
           - LACNIC
      
               ...Offer IPv6 services to clients or entities owns/related
               (including departments and/or sites) physically located within
               the region  covered by LACNIC within a period not longer than
               24 months.
      
           - RIPE NCC
      
               ...have a plan for making sub-allocations to other
      organisations
               and/or End Site assignments within two years.
      
      
      4.   Details of the proposal
      ----------------------------
      
      It is proposed that criteria d. in section 5.1.1. 'Initial allocation
      criteria' be changed from:
      
           - Have a plan for making at least 200 assignments to other
             organizations within two years.
      
      To:
      
           - Have a plan for making at least 200 assignments to other
            organizations within two years, OR;
      
           - Be an existing LIR with IPv4 allocations from an RIR/NIR which
             makes IPv6 assignments and/or sub-allocations to other
             organizations and announces the allocation in the inter-domain
             routing system within two years.
      
      
      5.   Advantages and disadvantages of the proposal
      -------------------------------------------------
      
      Advantages:
      
           - The criteria will allow the intended target of IPv6
             allocations -- LIRs with IPv4 allocations -- to request and
             receive an allocation more easily.
      
           - The criteria will be consistent with all the other RIRs who
             do not make the 200 assignment requirement a mandatory
             condition.
      
      
      Disadvantages:
      
           - None.
      
      
      6.   Effect on APNIC members
      ----------------------------
      
      APNIC members that have received IPv4 allocations can more easily
      request an IPv6 address allocation.
      
      
      7.   Effect on NIRs
      -------------------
      
      NIRs are expected to adopt this policy.
      
      randy, for the {chair}
      *              sig-policy:  APNIC SIG on resource management policy
      *
      _______________________________________________
      sig-policy mailing list
      sig-policy at lists dot apnic dot net
      http://mailman.apnic.net/mailman/listinfo/sig-policy