<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I fully agree with the comments on below message.<br>
</p>
<p>Fine IPv4 and 16 bit ASN transfers but not to IPv6.<br>
</p>
<p>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.<br>
</p>
<p>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 processed normally.<br>
</p>
<p>Fernando<br>
</p>
<div class="moz-cite-prefix">On 15/07/2019 15:51,
<a class="moz-txt-link-abbreviated" href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.LRH.2.21.1907151434560.3508@bigone.uneedus.com">The
only problem I have with this policy is that allows IPv6
transfers.
<br>
<br>
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.
<br>
<br>
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.
<br>
<br>
If the proposal applies only to IPv4 and 16 bit ASN's, I have no
problem, otherwise I am opposed.
<br>
<br>
Albert Erdmann
<br>
Network Administrator
<br>
Paradise On Line Inc.
<br>
<br>
On Mon, 15 Jul 2019, Kerrie Vassall-Richards wrote:
<br>
<br>
<blockquote type="cite">
<br>
Good day everyone,
<br>
<br>
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
<br>
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
<br>
int I would like to hear from the community if it is thoght the
policy is:
<br>
<br>
* Enabling Fair and Impartial Number Resource Administration
<br>
* Technically Sound
<br>
* Supported by the Community
<br>
1.Draft Policy ARIN-2019-10 is below and can be found at:
<a class="moz-txt-link-freetext" href="https://www.arin.net/participate/policy/drafts/2019_10/">https://www.arin.net/participate/policy/drafts/2019_10/</a>
<br>
2.NRPM Version 2019.2 - 10 July 2019 can be found here:
<a class="moz-txt-link-freetext" href="https://www.arin.net/participate/policy/nrpm/">https://www.arin.net/participate/policy/nrpm/</a>
<br>
3.The Specific section of the NRPM affected by this policy can
be found here:
<a class="moz-txt-link-freetext" href="https://www.arin.net/participate/policy/nrpm/#8-2-mergers-acquisitions-and-re">https://www.arin.net/participate/policy/nrpm/#8-2-mergers-acquisitions-and-re</a><br>
organizations
<br>
As a reminder please see the problem and the policy statements
<br>
Problem Statement:
<br>
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.
<br>
Policy Statement:
<br>
*Add to section 8.2:*
<br>
<br>
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.
<br>
I look forward to hearing more from everyone on this policy. <br>
Warm regards
<br>
<br>
Kerrie
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</body>
</html>