<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></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 3, 2016, at 11:52 , Ron Grant <<a href="mailto:rgrant@skywaywest.com" class="">rgrant@skywaywest.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
The biggest technical problem with 4-byte ASNs that I'm aware of
comes when propagating BGP communities - AFAIK even with extended
communities, you can't specify two 4-byte ASNs in a single
community.<br class="">
<br class="">
This can be worked around when using communities for direct peering
arrangements, as one side of the equation is static - but at a
Public Exchange point, it can be problematic, because who knows who
might want to connect or not connect to whom.<br class=""></div></div></blockquote><div><br class=""></div><div>This can be worked around in extended communities using a pair of communities (one type 0x42 and one type 0x02).</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">Recently we ran into this problem when requesting an ASN for the
Vancouver Internet Exchange (VANIX) - we were told there were no
2-byte ASNs left, so we went back to the drawing board to see how we
could run our Route Server with a 4-byte ASN, and after wrestling
with the problem for a few weeks, went back to ARIN
and...joy!...someone had returned a 2-byte, which we obtained for
the RS.<br class=""></div></div></blockquote><div><br class=""></div>So you’ve perpetuated the problem rather than finding a solution.</div><div><br class=""></div><div>I suppose that’s one way to go.</div><div><br class=""></div><div>Really, for an RS, you don’t need two ASNs in the community as you already have one of them in the peer-as route property, so all you care about is the advertise-to ASNs. This could be handled with an extended community of type “Destination AS specific” where the “Global Administrator” field is set to the destination AS.</div><div><br class=""></div><div>If you care about tagging the AS that fed the route to the route server, that can be done with an additional extended community of type “Origin AS Specific” where the “Global Administrator” field is set to the advertising AS.</div><div><br class=""></div><div>You would then have 16 bits with which other information could also be encoded into each of those communities if you so choose.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">IMO any future returned 2-byte ASNs should be reserved for critical
infrastructure or special need, but I'd love to find a solution to
the communities issue that made 2-byte ASNs "not special" anymore.<br class=""></div></div></blockquote><div><br class=""></div>This is already a solved problem IMHO.</div><div><br class=""></div><div>Owen</div><div><br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
<br class="">
<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 2016-04-03 11:36 AM, Adam Thompson
wrote:<br class="">
</div>
<blockquote cite="mid:4CFD1C3E-CAA7-45A1-9784-CBC9A1E29800@athompso.net" type="cite" class="">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 class="">
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 class="">
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 class="">
<br class="">
-Adam<br class="">
<br class="">
<br class="">
<div class="gmail_quote">On April 3, 2016 12:59:37 PM CDT, Andrew
Dul <a class="moz-txt-link-rfc2396E" href="mailto:andrew.dul@quark.net"><andrew.dul@quark.net></a> 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,
I am starting a new thread in PPML, as a follow up to the ARIN
suggestion and consultation which recently started regarding creating a
2-byte ASN waiting list.
The original suggestion is here:
<a moz-do-not-send="true" href="https://www.arin.net/participate/acsp/suggestions/2016-04.html" class="">https://www.arin.net/participate/acsp/suggestions/2016-04.html</a>
ARIN opened a consultation on this suggestion on the arin-consult
mailing-list. This thread starts here for those who are not subscribed
to arin-consult.
<a moz-do-not-send="true" href="http://lists.arin.net/pipermail/arin-consult/2016-March/000713.html" class="">http://lists.arin.net/pipermail/arin-consult/2016-March/000713.html</a>
<a moz-do-not-send="true" href="http://lists.arin.net/pipermail/arin-consult/2016-April/000722.html" class="">http://lists.arin.net/pipermail/arin-consult/2016-April/000722.html</a>
As the thread evolved it has been suggested that this issue should be
resolved via the policy development process rather than through a
suggestion.
There are a number of questions that have been raised by this thread. I
am copying them here to continue the discussion on PPML.
===
Working problem statement: ARIN will receive 2-byte ASNs as returns
over time, and these ASNs have perceived or additional value to
organizations compared to 4-byte ASNs. How should ARIN allocate these
2-byte ASNs?
===
Should they be given to the next requester, regardless of technical need
for a 2-byte ASN? (What are the technical qualifications we should use
if there is a specific technical need? e.g. provides transit to more
than 1 ASN?)
If there is really a technical need for 2-byte ASNs, shouldn't we
attempt to build an inventory of 2-byte ASNs?
Should returns be held in reserve?
Should ARIN hold them for some period of
time
before reallocating them?
Should they be put up for auction to qualified organizations?
Should they be given to the 1st organization on a wait-list for 2-byte
ASNs?
Would an organization looking for a 2-byte ASN have the option to
receive a 4-byte ASN in the interim? If they did would they have to
return it?
Should the waiting list be closed to organizations that already have a
2-byte ASNs?
I and the AC would appreciate your comments on these questions so that
we can start to build a draft policy that best matches with what the
community would like to see implemented by ARIN.
Thanks,
Andrew
<hr class="">
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 moz-do-not-send="true" href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://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></div>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre wrap="" class="">_______________________________________________
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="http://lists.arin.net/mailman/listinfo/arin-ppml">http://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>
<pre class="moz-signature" cols="72">--
Ron Grant Managed DSL/Cable/Wireless/Fibre
Skyway West Business Internet Internet and Private Networking
<a class="moz-txt-link-abbreviated" href="mailto:rgrant@skywaywest.com">rgrant@skywaywest.com</a> Bonding and Fail Over Solutions
cell: 604-737-2113 Virtual Data Centre and Private Clouds
direct: 604-484-5263 <a class="moz-txt-link-freetext" href="http://www.skywaywest.com/">http://www.skywaywest.com</a>
Sales, Support and Billing <a class="moz-txt-link-freetext" href="http://www.skywaywest.com/contact-us.htm">http://www.skywaywest.com/contact-us.htm</a>
<a href="http://ca.linkedin.com/in/obiron" class="">ca.linkedin.com/in/obiron</a>
</pre></div>_______________________________________________<br class="">PPML<br class="">You are receiving this message because you are subscribed to<br class="">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">Please contact info@arin.net if you experience any issues.</div></blockquote></div><br class=""></body></html>