<html><head></head><body>IMO, 2-byte ASNs should simply be retired and not reallocated. "Solving the technical problem", as described in your email, is actually ensuring the perpetuation of a different technical problem.<br>
It's the same sort of thing as the IPv4 vs IPv6 --transition, but this time ARIN has an opportunity to at least avoid being part of the problem, even if it can't really be part of the "solution".<br>
Let's please not prolong this problem, too... even in central Canada, known for a paucity of upstream carriers, it's now commercially feasible to work around the 2-byte technical limitations.<br>
<br>
-Adam<br>
<br><br><div class="gmail_quote">On April 3, 2016 12:59:37 PM CDT, Andrew Dul <andrew.dul@quark.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hello,<br /><br />I am starting a new thread in PPML, as a follow up to the ARIN <br />suggestion and consultation which recently started regarding creating a <br />2-byte ASN waiting list.<br /><br />The original suggestion is here:<br /><br /><a href="https://www.arin.net/participate/acsp/suggestions/2016-04.html">https://www.arin.net/participate/acsp/suggestions/2016-04.html</a><br /><br />ARIN opened a consultation on this suggestion on the arin-consult <br />mailing-list. This thread starts here for those who are not subscribed <br />to arin-consult.<br /><br /><a href="http://lists.arin.net/pipermail/arin-consult/2016-March/000713.html">http://lists.arin.net/pipermail/arin-consult/2016-March/000713.html</a><br /><br /><a href="http://lists.arin.net/pipermail/arin-consult/2016-April/000722.html">http://lists.arin.net/pipermail/arin-consult/2016-April/000722.html</a><br /><br />As the thread evolved it has been suggested that this issue should be <br
/>resolved via the policy development process rather than through a <br />suggestion.<br /><br />There are a number of questions that have been raised by this thread. I <br />am copying them here to continue the discussion on PPML.<br /><br />===<br /><br />Working problem statement: ARIN will receive 2-byte ASNs as returns <br />over time, and these ASNs have perceived or additional value to<br />organizations compared to 4-byte ASNs. How should ARIN allocate these <br />2-byte ASNs?<br /><br />===<br /><br />Should they be given to the next requester, regardless of technical need <br />for a 2-byte ASN? (What are the technical qualifications we should use <br />if there is a specific technical need? e.g. provides transit to more <br />than 1 ASN?)<br /><br />If there is really a technical need for 2-byte ASNs, shouldn't we <br />attempt to build an inventory of 2-byte ASNs?<br /><br />Should returns be held in reserve?<br /><br />Should ARIN hold them for some period of
time
before reallocating them?<br /><br />Should they be put up for auction to qualified organizations?<br /><br />Should they be given to the 1st organization on a wait-list for 2-byte <br />ASNs?<br /><br />Would an organization looking for a 2-byte ASN have the option to <br />receive a 4-byte ASN in the interim? If they did would they have to <br />return it?<br /><br />Should the waiting list be closed to organizations that already have a <br />2-byte ASNs?<br /><br />I and the AC would appreciate your comments on these questions so that <br />we can start to build a draft policy that best matches with what the <br />community would like to see implemented by ARIN.<br /><br />Thanks,<br />Andrew<br /><br /><br /><br /><hr /><br />PPML<br />You are receiving this message because you are subscribed to<br />the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br />Unsubscribe or manage your mailing list subscription at:<br /><a
href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br />Please contact info@arin.net if you experience any issues.<br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>