<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 11, 2016, at 15:24 , John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Apr 11, 2016, at 5:53 PM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:
<div class="">
<blockquote type="cite" class="">
<div class="">
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<blockquote type="cite" class="">
<div class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class="">Just to be clear, you feel that ARIN registry policy which rapidly depletes the </div>
<div class="">lower range of 4-byte ASNs would be technically sound and facilitate fair and </div>
<div class="">impartial number resource administration? </div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
No. I believe that ARIN registry policy which ignores any previous distinction</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
between ASNs ≤65535 and ASNs ≥65536 is harmful. I believe that a policy which</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
makes no distinction and hands them out as if they were a single pool of 32-bit</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
numbers is in the best interests of the community.</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
Alas, within the scope of ARIN’s mission, the best interests of the community are</div>
<div class="">met by registry policy which is technically sound and facilitates fair and impartial </div>
<div class="">number resource administration (hence the reason I asked you to elaborate on</div>
<div class="">those aspects, if any were applicable to your position.)</div>
<div class=""><br class="">
<blockquote type="cite" class="">
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
At some point there will no longer be available ASNs ≤65535. So be it. That</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
date should neither be accelerated nor decelerated by ARIN policy.</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
<blockquote type="cite" class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class="">It would be helpful if you could explain how in some detail, given that there </div>
<div class="">appears to be sufficient number of lower range 4-byte ASNs for those who </div>
<div class="">require such for their operations, and further that the supply appears to be</div>
<div class="">sufficient for quite some time (potentially till there is greater acceptance </div>
<div class="">and far fewer hurdles with the use of higher range 4-byte ASNs…)</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
So far, I haven’t seen so much a requirement as a convenience request for those</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
lower numbers.</div>
</blockquote>
<div class=""><br class="">
</div>
Understood, however, we have folks who have expressed that higher-range </div>
<div class="">4-byte ASN’s pose additional technical challenges to their operations, so that </div>
<div class="">remains an active point of discussion.</div>
<div class=""><br class="">
</div>
<div class="">If ARIN were to issue AS numbers strictly from smallest to largest, is it your</div>
<div class="">belief that those who feel they need lower-range AS numbers should engage</div>
<div class="">in an NRPM 8.3 transfer to obtain such? (or would you also want policy change</div>
<div class="">to prohibit that as an option?)</div></div></div></blockquote><div><br class=""></div></div>I’m not making any suggestions about the order in which ARIN issues AS Numbers.<div class=""><br class=""></div><div class="">I’m simply suggesting that we stop treating AS Numbers as anything other than a single</div><div class="">collective pool of 32 bit integers from which ARIN issues them.</div><div class=""><br class=""></div><div class="">High to low, low to high, or random order is fine with me. However, the community adopted</div><div class="">a policy that said ARIN is to treat them as a single pool of 32-bit identifiers and so long</div><div class="">as we continue to ask questions like this in the application process, it’s pretty clear that</div><div class="">policy isn’t being followed.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""></div></body></html>