[sig-policy] New Policy Proposal : prop-119-v001: Temporary transfers

    • To: "sig-policy at apnic dot net" <sig-policy at apnic dot net>
    • Subject: [sig-policy] New Policy Proposal : prop-119-v001: Temporary transfers
    • From: Sumon Ahmed Sabir <sumon at fiberathome dot net>
    • Date: Fri, 26 May 2017 04:12:13 +0000
    • Delivered-to: sig-policy at mailman dot apnic dot 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>
      • Dear SIG members,

        The proposal "prop-119-v001: Temporary transfers" has been sent to the
        Policy SIG for review.

        It will be presented at the Open Policy Meeting at APNIC 44 in Taichung,
        Taiwan on Thursday, 14 September 2017.

        We invite you to review and comment on the 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
        express your views on the proposal:

          - Do you support or oppose this proposal?
          - Does this proposal solve a problem you are experiencing? If so,
            tell the community about your situation.
          - Do you see any disadvantages in this proposal?
          - Is there anything in the proposal that is not clear?
          - What changes could be made to this proposal to make it more

        Information about this proposal is available at:



        Sumon, Bertrand, Ching-Heng


        prop-119-v001: Temporary transfers


        Proposer:       David Hilario
                        d.hilario at laruscloudservice dot net

        1. Problem statement

        It is currently not possible for an organisation to receive a temporary
        transfer under the current policy framework. Some organisations do not
        want to have address space registered as assignments or sub-allocations,
        but would rather have the address space registered as "ALLOCATED PA".

        2. Objective of policy change

        Create a possibility for temporary transfers that would allow
        organisations to have resources directly registered under them while
        they are the custodians of these resources on the Internet. While also
        guaranteeing that the offering party will under the APNIC policy be able
        to recover the resources once the “lease” time has expired unless
        specifically renewed.

        3. Situation in other regions

        RIPE region has a concept of temporary transfers in their policies. This
        concept is not found in the other RIRs for the moment.

        4. Proposed policy solution

        Adding to section "8.2.1. Conditions on the space to be transferred" the
        following paragraphs: It must be specified if the transfer is a
        permanent or temporary transfer.

        A temporary transfer must have an end date, upon the end date the
        resources will be transferred back to the same origin account or its
        successor in the event of merger and acquisitions, unless the transfer
        is specifically prolonged and confirmed by both parties.

        If the source account does no longer exist and has no successor, the
        space will then be returned to the origin RIR for the space. Temporary
        transfers cannot be further transferred.

        5. Advantages / Disadvantages

        Gives a greater flexibility in how LIRs manage and distribute their free
        pool. Enables organisation to receive address space in the way they

        These transfers would be treated and appear as regular transfers, only
        APNIC the offering and receiving party will be aware of their temporary

        Organisations receiving such space, if they further assign it, must make
        be ready to renumber/revoke space from their customers and services then
        the lease expires, this is no different than a sub-allocation and
        implies the same limitations.

        6. Impact on resource holders

        7. References