[arin-ppml] Draft Policy ARIN-2019-10: Inter-RIR M&A - Seeking Community Comments

[hostmaster at uneedus.com]

I did find the RIPE-682 document, and I do see that RIPE allows IPv6 
transfers.

However, I still do not think this is a good idea for ARIN.  It adds an 
extra level of complexity to both the reverse DNS zone and PKI. 
Therefore, I am still opposed to allowing IPv6 RIR transfers from ARIN 
blocks.

In a practical sense, a organization that has moved from region to region 
is going to end up with renumbering, unless they intend to pick up the 
whole network at once and move it, incurring the downtime of a move of 
physical equipment from region to region.  If an org intends to move to a 
different region, I see no reason they cannot renumber during their move 
to a new IPv6 block provided by their intended RIR.

Of course, shortages do not allow this to happen in the IPv4 or 16 bit ASN 
world, and these shortages are the main reason that such transfers were 
allowed in the first place.

Albert Erdmann
Network Administrator
Paradise On Line Inc.


On Mon, 15 Jul 2019, JORDI PALET MARTINEZ via ARIN-PPML wrote:

> Hi Albert,
>
> I think you looked at the wrong RIPE documents. Unless I got it wrong, the right document is RIPE-682, and it clearly states that IPv6 can also be transferred (both intra and inter-RIR).
>
> I've a similar policy proposal in LACNIC and APNIC, and working as well for submitting in a few days a similar one to AFRINIC.
>
> Regards,
> Jordi
> @jordipalet
>
>
>
> El 15/7/19 20:52, "arin-ppml-bounces at arin.net en nombre de hostmaster at uneedus.com" <arin-ppml-bounces at arin.net en nombre de hostmaster at uneedus.com> escribió:
>
>    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: https://www.arin.net/participate/policy/drafts/2019_10/
>    >  2.NRPM Version 2019.2 - 10 July 2019 can be found here: https://www.arin.net/participate/policy/nrpm/
>    >  3.The Specific section of the NRPM affected by this policy can be found here: https://www.arin.net/participate/policy/nrpm/#8-2-mergers-acquisitions-and-re
>    > organizations
>    > 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
>    >
>    > Kerrie
>    >
>    >
>    >
>    >
>    >
>    >
>    >
>    >
>    >_______________________________________________
>    ARIN-PPML
>    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:
>    https://lists.arin.net/mailman/listinfo/arin-ppml
>    Please contact info at arin.net if you experience any issues.
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
>
>
>
> _______________________________________________
> ARIN-PPML
> 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:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>