[sig-policy] prop-118: No need policy in APNIC region returned to author

  • To: "sig-policy" <sig-policy@apnic.net>
  • Subject: [sig-policy] prop-118: No need policy in APNIC region returned to author
  • From: "chku" <chku@twnic.net.tw>
  • Date: Mon, 18 Sep 2017 15:44:52 +0800 (CST)
  • Delivered-to: sig-policy@clove.apnic.net
  • 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: <https://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
  • List-unsubscribe: <https://mailman.apnic.net/mailman/options/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
  • Reply-to: chku <chku@twnic.net.tw>

    • Dear colleagues
      
      Version 1 of prop-118: No need policy in APNIC region, did not reach 
      consensus at the APNIC 44 Open Policy Meeting.
      
      The Policy SIG Chairs returned the proposal to the author for further
      consideration and invited him to submit an amended version based on the 
      community's feedback.
      
      Proposal details, including the full text of the proposal, history, and
      links to previous versions are available at:
      
          https://www.apnic.net/community/policy/proposals/prop-118/
      
      
      Regards
      
      Sumon, Bertrand, Ching-Heng
      Policy SIG Chairs
      
      
      -------------------------------------------------------
      
      prop-118-v001: No need policy in APNIC region
      
      -------------------------------------------------------
      
      Proposer:       David Hilario
                      d.hilario@laruscloudservice.net
      
      
      1. Problem statement
      -------------------------------------------------------
      
      Whenever a transfer of IPv4 is taking place within the APNIC region, the
      recipient needs to demonstrate the "need" for the IPv4 space they intend
      to transfer.
      
      Companies transferring IPv4 space to their pool do this in ordcer to
      enable further growth in their network, since the space is not coming
      from the free public pool, regular policies that are intended to protect
      the limited pool of IPv4 space can be removed in transfers.
      
      
      2. Objective of policy change
      -------------------------------------------------------
      
      Simplify transfer of IPv4 space between resource holders.
      Ease some administration on APNIC staff.
      
      
      3. Situation in other regions
      -------------------------------------------------------
      
      RIPE region has an all around no need policy in IPv4, even for first
      allocation, transfers do not require the recipient to demonstrate their
      intended use of the resources .
      
      ARIN, need base for both transfers and resources issued by ARIN.
      
      AFRINIC, need based policy on transfers (not active yet) and resource
      request from AFRINIC based on needs.
      
      LACNIC, no transfers, need based request.
      
      Out of all these RIR, only ARIN and RIPE NCC have inter-RIR transfer
      policies,  ARIN has made clear in the past that the "no need" policy
      from the RIPE region would break inter-RIR transfers from ARIN to RIPE
      region.
      
      
      4. Proposed policy solution
      -------------------------------------------------------
      
      Simply copy the RIPE policy to solve the ARIN transfer incompatibility:
      
       - APNIC shall accept all transfers of Internet number resources to its
         service region, provided that they comply with the policies relating
         to transfers within its service region.
      
       - For transfers from RIR regions that require the receiving region to
         have needs-based policies, recipients must provide a plan to the
         APNIC for the use of at least 50% of the transferred resources within
         5 years.
      
      source:
          https://www.ripe.net/publications/docs/ripe-644
      
      
      5. Advantages / Disadvantages
      -------------------------------------------------------
      
      Advantages:
      
       - Harmonisation with RIPE region.
       - Makes transfer simpler and smoother within APNIC and between APNIC
         and RIPE.
       - maintains a compatibility with ARIN.
       - Removes the uncertainty that a transfer may be rejected based on
         potentially badly documented needs.
       - Lowers the overall administrative burden on APNIC staff.
      
      Disadvantages:
      
      none.
      
      
      6. Impact on resource holders
      -------------------------------------------------------
      None
      
      
      7. References
      -------------------------------------------------------
      
      Hello Chairs
      
      I have prepared an email for the mailing list regarding the outcome of 
      prop-118.
      
      Please review it and send to the mailing list.
      
      Regards,
      
      Adam and George
      --
      
      ###DRAFT###
      
      Dear colleagues
      
      Version 1 of prop-118: No need policy in APNIC region, did not reach 
      consensus at the APNIC 44 Open Policy Meeting.
      
      The Policy SIG Chairs returned the proposal to the author for further
      consideration and invited him to submit an amended version based on the 
      community's feedback.
      
      Proposal details, including the full text of the proposal, history, and
      links to previous versions are available at:
      
          https://www.apnic.net/community/policy/proposals/prop-118/
      
      
      Regards
      
      Sumon, Bertrand, Ching-Heng
      Policy SIG Chairs
      
      
      -------------------------------------------------------
      
      prop-118-v001: No need policy in APNIC region
      
      -------------------------------------------------------
      
      Proposer:       David Hilario
                      d.hilario@laruscloudservice.net
      
      
      1. Problem statement
      -------------------------------------------------------
      
      Whenever a transfer of IPv4 is taking place within the APNIC region, the
      recipient needs to demonstrate the "need" for the IPv4 space they intend
      to transfer.
      
      Companies transferring IPv4 space to their pool do this in ordcer to
      enable further growth in their network, since the space is not coming
      from the free public pool, regular policies that are intended to protect
      the limited pool of IPv4 space can be removed in transfers.
      
      
      2. Objective of policy change
      -------------------------------------------------------
      
      Simplify transfer of IPv4 space between resource holders.
      Ease some administration on APNIC staff.
      
      
      3. Situation in other regions
      -------------------------------------------------------
      
      RIPE region has an all around no need policy in IPv4, even for first
      allocation, transfers do not require the recipient to demonstrate their
      intended use of the resources .
      
      ARIN, need base for both transfers and resources issued by ARIN.
      
      AFRINIC, need based policy on transfers (not active yet) and resource
      request from AFRINIC based on needs.
      
      LACNIC, no transfers, need based request.
      
      Out of all these RIR, only ARIN and RIPE NCC have inter-RIR transfer
      policies,  ARIN has made clear in the past that the "no need" policy
      from the RIPE region would break inter-RIR transfers from ARIN to RIPE
      region.
      
      
      4. Proposed policy solution
      -------------------------------------------------------
      
      Simply copy the RIPE policy to solve the ARIN transfer incompatibility:
      
       - APNIC shall accept all transfers of Internet number resources to its
         service region, provided that they comply with the policies relating
         to transfers within its service region.
      
       - For transfers from RIR regions that require the receiving region to
         have needs-based policies, recipients must provide a plan to the
         APNIC for the use of at least 50% of the transferred resources within
         5 years.
      
      source:
          https://www.ripe.net/publications/docs/ripe-644
      
      
      5. Advantages / Disadvantages
      -------------------------------------------------------
      
      Advantages:
      
       - Harmonisation with RIPE region.
       - Makes transfer simpler and smoother within APNIC and between APNIC
         and RIPE.
       - maintains a compatibility with ARIN.
       - Removes the uncertainty that a transfer may be rejected based on
         potentially badly documented needs.
       - Lowers the overall administrative burden on APNIC staff.
      
      Disadvantages:
      
      none.
      
      
      6. Impact on resource holders
      -------------------------------------------------------
      None
      
      
      7. References
      -------------------------------------------------------
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      _______________________________________________
      Sig-policy-chair mailing list
      Sig-policy-chair@apnic.net
      https://mailman.apnic.net/mailman/listinfo/sig-policy-chair