[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: "Bertrand Cherrier" <b.cherrier@micrologic.nc>
  • Date: Mon, 17 Sep 2018 18:39:56 +1100
  • Delivered-to: sig-policy@clove.apnic.net
  • Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=micrologic.nc; s=mail; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:To:From; bh=iiINCaRCRzBouCP6WskHj9vFbxf4r8bz9to5O+iBaWU=; b=anQdoG+okGTRZNXTfsWh2+zXXzfjW63MKBudrWbhfghIUj55r1fiXgFg5vbAyN4mIRQ1oJT9Op1Qes2bklZaS+R3Ng/vE4ttxT61G+hSaXFzhp/Znzcf0NJuWg7EHSQfYbhQ3TK7W+BZaOP/rK9mybjHgWPzS/X4fBBPNx0nhOc=;
  • 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>

    • Dear colleagues

      Version 2 of prop-118: No need policy in APNIC region, did not reach
      consensus at the APNIC 46 Open Policy Meeting.

      The Policy SIG Chairs returned the proposal to the author for further discussion with the community and invited the author 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:



      Sumon, Bertrand, Ching-Heng
      Policy SIG Chairs

      prop-118-v002: No need policy in APNIC region

      Proposer: Heng Lu

      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, increase database accuracy.

      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

      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.

      • When transferring Internet number resources to another RIR, the APNIC
        will follow the transfer policies that apply within its own service region.
        The APNIC will also comply with the commitments imposed by the receiving
        RIR in order to facilitate the transfer.

      5. Advantages / Disadvantages


      • 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.



      6. Impact on resource holders


      7. References



      Bertrand Cherrier
      Administration Systèmes - R&D
      Micro Logic Systems
      Tél : +687 24 99 24
      VoIP : 65 24 99 24
      SAV : +687 36 67 76 (58F/min)