<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body style="background-color: rgb(255, 255, 255); color: rgb(0, 0,
0); font-family: Tahoma; font-size: 16px;" bgcolor="#FFFFFF"
text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 9/Aug/16 14:58, Geert Jan de Groot
wrote:<br>
<br>
</div>
<blockquote style="border-left: 2px solid #009900 !important;
border-right: 2px solid #009900 !important; padding: 0px 15px 0px
15px; margin: 8px 2px; color: rgb(0, 0, 0) !important; color:
rgb(0, 0, 0) !important; background-color: null !important; color:
null !important;"
cite="mid:e95508eb-7985-c5be-8c98-fef7a840a852@xs4all.nl"
type="cite"> <br>
<br>
For the AfNOG meetings, for a few years we have tried to use
32-bit ASNs
<br>
to showcase that it "just works". Actually, in a few cases we've
caused
<br>
hardship on our local host because software had to be updated.
<br>
In many cases, the local host actually gratefully made these
changes
<br>
to accomedate our 32-bit ASNs. A public thanks to the various
<br>
hosts for doing this work.
<br>
<br>
As you can see, time is running out as the 16-bit pool is now gone
<br>
at IANA. AfriNIC still have a limited supply but it won't last.
<br>
If you have not updated your equipment and procedures for 32-bit
ASNs then you are living on borrowed time and things may get
interesting soon.
<br>
<br>
You may want to check up on this, if you haven't so far.
<br>
</blockquote>
<br>
I would say that we've been doing a lot of peering and turning up
customer circuits in the region, and in the past 24 months, we've
come across a ton of 32-bit ASN's in either context, and haven't had
any issues or exceptions turning those up.<br>
<br>
So I think there has been great improvement in this area... a lot
more than IPv6 and DNSSEC implementations, anyway.<br>
<br>
Mark.<br>
</body>
</html>