[arin-ppml] IPv6 Transfers (was :Draft Policy ARIN-2018-1: Allow Inter-regional ASN Transfers
chevykilla.14 at gmail.com
Sat Feb 3 18:10:25 EST 2018
I’ve been trying to leave group for a while, but I’ve been unsuccessful thus far, can someone assist?
Chevaughn F.D Brown
Youth Member of Parliament
St Catherine West Central
National Youth Parliament Jamaica
Chairman| Old Harbour CDC Youth Council
Parish Coordinator| National Youth Parliament Jamaica
Public Relations Officer| Old Harbour CDC
Caribbean Youth Environment Network
Mobile: 1 876 472 9054
Email: Chevybrown at live.com
This email and any attachments are confidential, may be subject to the provisions of the Official Secrets Act and must not be disclosed to or used by anyone other than the intended recipient. Unauthorized use, disclosure, distribution or copying is prohibited and may be unlawful.
If you are not the intended recipient, please notify the sender and then delete this email. This email is sent over a public network and its completeness or accuracy cannot be guaranteed. You should carry out your own virus check before opening attachments. We do not accept liability for any loss or damage caused by software viruses.
> On Feb 3, 2018, at 1:38 PM, Job Snijders <job at ntt.net> wrote:
> On Sat, Feb 03, 2018 at 10:17:02AM -0800, Scott Leibrand wrote:
>>> On Feb 3, 2018, at 5:12 AM, hostmaster at uneedus.com wrote:
>>> 1) A company is relocating its headquarters from a location served
>>> by an RIR, to another location served by a different RIR, and wants
>>> everything in their new home region.
>>> 2) A company decides to buy another company with few assets, but
>>> holds a 16 bit ASN in another RIR region. They then want to bring
>>> that ASN back to ARIN so they can add it to their registration plan.
>>> This is similar to M&A of companies with IPv4 addresses as assets,
>>> since they can not get a 16 bit ASN directly from ARIN.
>>> 3) They have so much equipment scattered around the world with the
>>> old ASN, that they do not want to renumber just because their
>>> headquarters moved to a region served by a different RIR. If the
>>> region moved to is ARIN, in most cases they can save money by
>>> putting the moved ASN on their registration plan with their address
>>> In any case, if ARIN allows transfers, it is highly unlikely that
>>> that policy would ever be applied to anything other than a 16 bit
>>> ASN as there are plenty of 32 bit ASN's available in all regions.
>> All three scenarios apply equally to 16 and 32 bit ASNs. If it’s
>> easier for everyone involved to transfer an ASN between RIRs along
>> with any IPv4 resources, there’s no reason to renumber (which requires
>> cooperation from BGP peers).
> I'd like to emphasize that renumbering ASNs can be a very cumbersome and
> expensive venture (be it a 16-bit or 32-bit ASN). There are notable
> public examples of M&As where the integration and renumbering of related
> ASNs took years.
> Just because there is no shortage of 32-bit ASNs in another region
> doesn't imply I'd be willing to absorb the cost of renumbering an ASN.
> Kind 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