<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 12/10/2019 13:58, William Herrin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP-guGVrj3DMO2K4xqxXmNXbBPsNrXyCYV=b8+3jwsNO4_J2Nw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Oct 12, 2019 at 6:29
AM <<a href="mailto:hostmaster@uneedus.com"
moz-do-not-send="true">hostmaster@uneedus.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I agree. The only reason
for this transfer thing was the shortage of IPv4 <br>
addresses and 16 bit ASN numbers. There is no shortage of
IPv6 addresses <br>
or 32 bit ASN.<br>
<br>
Therefore, I agree that IPv6 transfers and 32 bit ASN
transfers should not <br>
be permitted, even for M&A.<br>
</blockquote>
<div><br>
</div>
<div>I have almost exactly the opposite opinion. No shortage
means no cause to game the system. No gaming of the system
means the transfer is requested for reasonable, pragmatic
causes. Like avoiding renumbering pain. Why should this be
prevented?</div>
</div>
</div>
</blockquote>
<p>Because this is not a strong enough reason to allow IPV6 and
32-bit ASN be moved from one region to another. Although there are
costs to do renumbering this is part of the business and anyone in
such situation must be prepared to do so.</p>
<p>The type of scenario that is being proposed here is not something
that happens so frequently, in some cases may be very specific and
is not very productive to change such an important thing like
allowing IPv6 and 32-bits ASN to be moved between regions with the
impacts it causes in the whole global registering system just to
accomplish the need of a few which have workable plausible option
available. Therefore the need of a few cannot overcome the
interest of the whole system. <br>
If there was a shortage of a IPv6 or 32-bit ASN that would be a
more strong reason, but the reality is there isn't. The option
available is renumbering.<br>
</p>
<blockquote type="cite"
cite="mid:CAP-guGVrj3DMO2K4xqxXmNXbBPsNrXyCYV=b8+3jwsNO4_J2Nw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<br>
<div><br>
</div>
<div> </div>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>William Herrin</div>
<div><a href="mailto:bill@herrin.us" target="_blank"
moz-do-not-send="true">bill@herrin.us</a></div>
<div><a href="https://bill.herrin.us/" target="_blank"
moz-do-not-send="true">https://bill.herrin.us/</a><br>
</div>
</div>
</div>
</div>
<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>