[arin-ppml] Draft Policy ARIN-2019-10: Inter-RIR M&A - Seeking Community Comments
fhfrediani at gmail.com
Mon Jul 15 15:37:50 EDT 2019
I fully agree with the comments on below message.
Fine IPv4 and 16 bit ASN transfers but not to IPv6.
Some people justify that it is to avoid renumbering, but I don't
consider a strong enough reason to allow IPv6 transfers. Renumbering is
part of the business whenever necessary and not something impossible to
achieve. Therefore the cost of allowing IPv6 transfers is higher than to
renumber in my view.
However I don't really see a need of this policy to exist. If an
organization buys or merges with another inside or outside the RIR
region it then has the power to request a normal Inter-RIR transfer
according to current policy from both RIRs which should be justified and
On 15/07/2019 15:51, hostmaster at uneedus.com wrote:
> The only problem I have with this policy is that allows IPv6 transfers.
> I have no problem with IPv4 and 16 bit ASN transfers because they are
> both scarce resources. However, I do not think we should start down
> the road of allowing IPv6 RIR transfers. If they are operating in a
> portion of the world under another RIR, let them get their IPv6
> resources from the new RIR blocks. While I have no problem giving them
> a period of time with both blocks to move their IPv6 resources to
> blocks controlled by the new RIR, I do not think we should start down
> that path with IPv6 for the first time. Movement of IPv6 is nowhere as
> hard as IPv4 with its constrained CIDR routing. IPv6 is easy, every
> LAN gets a /64.
> I did a bit of checking and RIPE, normally the most liberal of the
> RIR's does not permit IPv6 transfers, and I think it should stay that
> way. It appears that all the other RIR's do not as well. Afrinic has
> a proposal to allow it, but it has not been adopted.
> If the proposal applies only to IPv4 and 16 bit ASN's, I have no
> problem, otherwise I am opposed.
> Albert Erdmann
> Network Administrator
> Paradise On Line Inc.
> On Mon, 15 Jul 2019, Kerrie Vassall-Richards wrote:
>> Good day everyone,
>> I am seeking community input on Draft Policy ARIN-2019-10: Inter-RIR
>> M&A since the last post on this policy on May 21, 2019 there has not
>> been any conversat
>> ion around it. As primary shepherd I need to have a good sense of the
>> direction that the community wants to take in regards to this policy.
>> As a starting po
>> int I would like to hear from the community if it is thoght the
>> policy is:
>> * Enabling Fair and Impartial Number Resource Administration
>> * Technically Sound
>> * Supported by the Community
>> 1.Draft Policy ARIN-2019-10 is below and can be found at:
>> 2.NRPM Version 2019.2 - 10 July 2019 can be found here:
>> 3.The Specific section of the NRPM affected by this policy can be
>> found here:
>> As a reminder please see the problem and the policy statements
>> Problem Statement:
>> Merger, acquisition, or reorganization activity sometimes results in
>> a restructuring where company resources, the management of number
>> resources, or the use of number resources are concentrated outside
>> the ARIN service region. In this case it may be desirable for the
>> current legal entity or a legal entity that is a parent, child or
>> sister to move the servicing of the number resources to a different RIR.
>> Policy Statement:
>> *Add to section 8.2:*
>> When merger, acquisition, or reorganization activity results in
>> surviving legal entity that is incorporated outside the ARIN service
>> region, or focused outside the ARIN service region, or is merging
>> with an organization that already has a relationship with another
>> RIR, then resources may be moved to another RIR in accordance with
>> the receiving RIR’s policies.
>> I look forward to hearing more from everyone on this policy.
>> Warm regards
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML