<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Elvis, dear colleagues,<br>
<br>
We are happy to provide you with the data you requested.<br>
<br>
In the last 12 months, about 18% (414 out of 2291) of the requests
were for 16-bit ASNs. Currently we have enough 16-bit ASNs in our
free pool, but it should be noted that the return of unused ASNs
is the only source to add such ASNs to our pool.<br>
<br>
Once an ASN has been returned to RIPE NCC, the only reason to keep
it in our quarantine pool for longer than 6 months is that the ASN
is still visible in the routing system. We currently have just
over 200 16-bit ASNs in regular quarantine, mainly thanks to our
project to clean up unused ASNs.<br>
<br>
It is correct that we still assign 16-bit ASNs when they are
specifically requested. Although the ASN policy states that since
"2010 the RIPE NCC will cease to make any distinction", it was
decided in 2010 to keep the option to request for 16-bit ASNs
[1][2]<br>
Neither IANA nor other RIRs make this distinction between 16-bit
and 32-bit ASNs any more.<br>
<br>
I hope you found this information useful, especially in terms of
how to achieve more responsible ASN management.<br>
<br>
Kind regards,<br>
Marco Schmidt<br>
Manager Registration Services<br>
RIPE NCC<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-679#ASnumbers">https://www.ripe.net/publications/docs/ripe-679#ASnumbers</a><br>
[2]
<a class="moz-txt-link-freetext" href="https://www.ripe.net/ripe/mail/archives/address-policy-wg/2010-January/004977.html">https://www.ripe.net/ripe/mail/archives/address-policy-wg/2010-January/004977.html</a><br>
<br>
</p>
<div class="moz-cite-prefix">On 12/06/2023 12:46, Elvis Daniel Velea
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJZHz-qN4DrQ5cO_=2zkHHm6HtT0mQFWfs0D6a8uK6eASgFaKQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<div dir="auto">Hi Nick,</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jun 12, 2023 at
00:25 Nick Hilliard <<a href="mailto:nick@foobar.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">nick@foobar.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Elvis
Daniel Velea wrote on 11/06/2023 10:06:<br>
> If someone could tell me why a 32bit ASN can not be
used today (even <br>
> with 10 years old equipment), I’d appreciate it.<br>
<br>
there's plenty of kit out there which still doesn't
support BGP Large <br>
Communities, particularly mikrotik routeros which only
released an <br>
initial production implementation at around the beginning
of 2022.<br>
<br>
Nick</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">thanks for that. I’m surprised to hear this,
but heh, manufacturers can be slow sometimes… very slow :(</div>
<div dir="auto"><br>
</div>
<div dir="auto">It may, then, matter to some if an ASN is
16bit or not. I know that the NCC had at some point (maybe
still do) assigned 16bit ASNs upon request. Curious to see
some stats, if possible:</div>
<div dir="auto">- how many requests come in for 16bit a
year? how many are those of the total ASN requests?</div>
<div dir="auto">- how many 16bit ASNs are still in the pool
and how many come back to the free pool every year?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Just trying to see how many years until
16bit ASNs could only be issued by the NCC only if
returned.</div>
<div dir="auto"><br>
</div>
<div dir="auto">On another note, I believe that there were a
lot of 16bit ASNs in quarantine because of references in
various objects (mostly as-sets if I recall correctly).
Can you tell us, Marco, how many of those ASNs are
quarantined and why aren’t these removed out of quarantine
and assigned?</div>
<div dir="auto"><br>
</div>
<div dir="auto">elvis</div>
<div dir="auto"><br>
</div>
</div>
</div>
</div>
<span class="gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">This message was sent from a
mobile device. Some typos may be possible. </div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>