<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 22, 2017 at 4:10 PM, Owen DeLong <span dir="ltr"><<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
> On Aug 18, 2017, at 05:14 , David Huberman <<a href="mailto:daveid@panix.com">daveid@panix.com</a>> wrote:<br>
><br>
> I am a US-based company and I operate a network on multiple continents.<br>
><br>
> I need to be able to move space from my home RIR of ARIN to other regions as I expand my network overseas.<br>
><br>
> The current policy that has been in effect for many years allows me to operate my network properly -- using ARIN blocks in ARIN, APNIC blocks in APNIC, and RIPE blocks in RIPE. The policy is predictable and I can plan network growth around it.<br>
><br>
> If this proposal passes, it will shut off transfers between ARIN and APNIC. This will hurt my business's finances. We purchased addresses in the ARIN region wth the intention of moving them to APNIC in the future. We did so because the size blocks we needed were not available in the APNIC region. So now we are talking about hurting my business for ... what reason? How do network operations benefit from this proposal?<br>
<br>
Currently, there are certain registries that are operating like roach motels for IP addresses. KR-NIC, CN-NIC are examples.<br></blockquote><div><br></div><div>There is no evidence that this presents anything more than a theoretical problem, in fact I went and looked at APNICs transfer logs;</div><div><br></div><div><a href="https://www.apnic.net/manage-ip/manage-resources/transfer-resources/transfer-logs/">https://www.apnic.net/manage-ip/manage-resources/transfer-resources/transfer-logs/</a><br></div><div>or</div><div><a href="http://ftp.apnic.net/transfers/apnic/">http://ftp.apnic.net/transfers/apnic/</a><br></div><div><br></div><div>I found out of 281 transfers from ARIN to APNIC, there were 2 to KR and 15 to CN, and the 2 to KR were /22s and all the transfers to CN appear to be cloud providers from the best I can tell. There were also another 22 transfers from APNIC to ARIN, for a total of 303 transfers between APNIC and ARIN. </div><div><br></div><div>You want to break 94% of the transfers between APNIC and ARIN because you don't like 6% of them. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
AfriNIC is discussing a similar proposal and a similar proposal was discussed in LACNIC.<br></blockquote><div><br></div><div>Help me understand this, we are going to break transfers to APNIC in hopes that ArfNIC and LACNIC won't pass a policy? Please explain how you expect that to work. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
It is hoped that by implementing this policy it will put pressure on those registries to be more cooperative with the global community in allowing bi-directional transfers.<br>
<br>
That is how it helps network operations. Admittedly, it’s a short-term pain for a longer term gain, but that is the intent.<br></blockquote><div><br></div><div>In my opinion the cure you propose is fare worse than the disease you seek to remedy. This policy will seriously damage what seems like a mostly well functioning system, primarily to influence a decision that is independent of the result.</div><div><br></div><div>I cannot support this policy.</div><div><br></div><div>Thanks.</div><div> </div></div>-- <br><div class="gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div>
</div></div>