Re: [sig-policy] prop-119: Temporary transfers, to be discussed at APNIC 44 Polic y SIG
Hi Hossain and Hiroki,
Thank you for the question,
Yes the agreement between the offering party and receiving party would
need to have an end date for the transfer for the transfer to be
defined as and handled as temporary.
Duration of the transfer is up to the offering and receiving party.
For the rest, it should be treated like any other transfer request no
difference.
Regards,
David Hilario
IP Manager
Larus Cloud Service Limited
p: +852 29888918 m: +359 89 764 1784
f: +852 29888068
a: Flat B5, 11/F, TML Tower, No.3 Hoi Shing Road, Tsuen Wan, HKSAR
w: laruscloudservice.net
e: d.hilario@laruscloudservice.net
On 10 September 2017 at 10:09, Jahangir Hossain <jahangir@parween.net> wrote:
> In the policy it only says "A temporary transfer must have an end date".
> What about the end date ? Who will define the end ? Is it define by
> requester who are interest to temporary transfer resource to receiver ?
>
>
>
>
> Regards / Jahangir
>
> On Wed, Aug 9, 2017 at 12:16 PM, chku <chku@twnic.net.tw> wrote:
>>
>> Dear SIG members
>>
>> The proposal "prop-119: Temporary transfers" was sent to the Policy SIG
>> Mailing list in May 2017.
>>
>> It will be presented at the Open Policy Meeting at APNIC 44 which will
>> be held in Taichung, Taiwan on Wednesday and Thursday, 14 & 15 September
>> 2017.
>>
>> Information about the proposal is available from:
>>
>> http://www.apnic.net/policy/proposals/prop-119
>>
>> You are encouraged to express your views on the proposal:
>>
>> - Do you support or oppose the proposal?
>> - 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 effective?
>>
>> Please find the text of the proposal below.
>>
>> Kind Regards,
>>
>> Sumon, Ching-Heng, Bertrand
>> APNIC Policy SIG Chairs
>>
>>
>> ------------------------------------------------------------------------
>>
>> prop-119-v001: Temporary transfers
>>
>> ------------------------------------------------------------------------
>>
>> Proposer: David Hilario
>> d.hilario@laruscloudservice.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
>> ------------------------------------------------------------------------
>>
>> Advantages:
>> Gives a greater flexibility in how LIRs manage and distribute their free
>> pool. Enables organisation to receive address space in the way they
>> intend.
>>
>> Disadvantages:
>> These transfers would be treated and appear as regular transfers, only
>> APNIC the offering and receiving party will be aware of their temporary
>> nature.
>>
>> 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
>> ------------------------------------------------------------------------
>> none
>>
>>
>> 7. References
>> -------------
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Sig-policy-chair mailing list
>> Sig-policy-chair@apnic.net
>> https://mailman.apnic.net/mailman/listinfo/sig-policy-chair
>>
>> * sig-policy: APNIC SIG on resource management policy
>> *
>> _______________________________________________
>> sig-policy mailing list
>> sig-policy@lists.apnic.net
>> https://mailman.apnic.net/mailman/listinfo/sig-policy
>
>
>
>
> --
>
>
> * sig-policy: APNIC SIG on resource management policy
> *
> _______________________________________________
> sig-policy mailing list
> sig-policy@lists.apnic.net
> https://mailman.apnic.net/mailman/listinfo/sig-policy