>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".
>It actually came up a few time from larger networks who tend to want>that, it is a form of long term leasing for them, they want the>resources into their registry out of convenience but also due to>internal procedures, they for example only want to commit for a 5 year>period while preparing their IPv6 and then return the space.>>The do not want to receive a sub-allocation or assignment, as it needs>to be part of their LIR/registry for them to be able to count it into>the network inventory and use the address.>>Some organisation have strict policies against use of external IP space.
>The policy came to be as we have had several large companies actually>asking for such type of transfers.>>It is already a possibility in the RIPE region to do such transfers.>>It is really to cover a corner case where organisations are not able>or interested in receiving the IP space in form of assignments or>sub-allocations, but need them to be part of their own registry for>full control of the space and only for a pre-set amount of time.
>If it is not registered to your LIR in your registry, you cannot send>APNIC DB in the first place, but the space from your LIR that has>issued the space to you, your LIR decides how to register it and which>maintainers will be on it, you are not in full control.>>And ultimately for the ones using RPKI, it needs to be under their>control to issue ROAs in MyAPNIC and not rely on any other parties for>their own IP management.
Hi,On Aug 23, 2017 1:42 AM, "David Huberman" <david.huberman at oracle dot com> wrote:Hello,I oppose this proposal as written.I do not believe this policy proposal benefits network operations.All your resources would be under your APNIC account, you are in full control for everything from Database registration, RPKI and reverse DNS.There is some advantages to network operation, it is not purely administrative.Ibelieve it is intended to further the goals of the policy proposer and the company he owns/works at, which exists to earn money from the sale and leasing of IP address blocks (per their website).From a business point of view, this policy came as a reaction to requests from customers, yes.Policies are there to accommodate the distribution and operation of the various parties operating in the region.Some see a benefit in having a system like this in place, attacking the policy based on our company's services is a bit odd at best.Some organization's are not willing to buy IPv4 space as a form of permanent transfer, they do not believe in IPv4 remaining the dominant protocol for the years to come but do need some IPs for some expansion and projects that they can later simply return back, other giant internet organizations with too much money don't care and are currently buying up everything on offer.This proposal would help leveling that field a bit.If the policy proposal has shed light on some deficiencies in the Membership Agreement (found at: https://www.apnic.net/about-apnic/corporate-documents/ ), then I suggest it would be helpful for the policy proposer to work with APNIC staff and/or the EC, rather than through the Policy SIG.documents/membership/ membership-agreement/ I really don't follow your logic here.Thank you,DavidDavid Huberman | Principal Program Manager
Oracle Cloud
1501 4th Ave #1800Seattle, WA 98101USA
* sig-policy: APNIC SIG on resource management policy *
_______________________________________________
sig-policy mailing list
sig-policy at lists dot apnic dot net
https://mailman.apnic.net/mailman/listinfo/sig-policy Regards,David Hilario
* sig-policy: APNIC SIG on resource management policy *
_______________________________________________
sig-policy mailing list
sig-policy at lists dot apnic dot net
https://mailman.apnic.net/mailman/listinfo/sig-policy