Hi, since when does ftp://ftp.arin.net/info/asn.txt contain dotted AS numbers? Where is the new formatting documented, asn.h ? It just broke a scriptology we use to generate AS lookups for 'offline' customers (please don't ask :) ). $ head -2 asn.txt [asn.txt] 2007-09-19 02:45:00Z $ tail -7 asn.txt [reformatted some whitespace here] 44032-64511 IANA-RSVD IANA-IP-ARIN (Abuse) 64512-65535 IANA-RSVD2 IANA-IP-ARIN (Abuse) 6.0 B6 WM110-ARIN (Tech) 6.1 ASN4-TELUS AAT-ARIN (Abuse), FTS1-ARIN (Tech), TBOTP-ARIN (Tech) 6.3 H6 KML9-ARIN (Tech) 6.5 ISC-32AS ISCAT-ARIN (Abuse), JDA87-ARIN (Tech) 6.6 BLUEFIN-TRADING HOSTM912-ARIN (Abuse) "Your search - AS number 6.5 ISC32-AS - did not match any documents. " Thanks, andreas -- Andreas Ott K6OTT andreas@naund.org
Andreas Ott wrote:
Hi,
since when does ftp://ftp.arin.net/info/asn.txt contain dotted AS numbers? Where is the new formatting documented, asn.h ?
It just broke a scriptology we use to generate AS lookups for 'offline' customers (please don't ask :) ).
http://www.google.co.uk/search?q=32+bit+asn J -- COO Entanet International T: 0870 770 9580 W: http://www.enta.net/ L: http://tinyurl.com/3bxqez
Andreas Ott wrote:
Hi,
since when does ftp://ftp.arin.net/info/asn.txt contain dotted AS numbers? Where is the new formatting documented, asn.h ?
http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as-representation...
6.0 B6 WM110-ARIN (Tech) 6.1 ASN4-TELUS AAT-ARIN (Abuse), FTS1-ARIN (Tech), TBOTP-ARIN (Tech) 6.3 H6 KML9-ARIN (Tech) 6.5 ISC-32AS ISCAT-ARIN (Abuse), JDA87-ARIN (Tech) 6.6 BLUEFIN-TRADING HOSTM912-ARIN (Abuse)
"Your search - AS number 6.5 ISC32-AS - did not match any documents. "
Fwiw, the ARIN website search function does understand asdot notation. -Kevin
[stripped hostmaster@arin.net from CC] Andreas Ott wrote:
Hi,
since when does ftp://ftp.arin.net/info/asn.txt contain dotted AS numbers? Where is the new formatting documented, asn.h ?
Since 32bit ASN's came out. People have been warned about this and it has been discussed already a number of times on NANOG. Also see RFC4893 :) BTW, my parser scripts just convert them to 32bit numbers, as that is what they are, nothing more, nothing less. Greets, Jeroen
[hostmaster@arin.net dropped from cc list, to avoid a potential flurry of pointless new tickets.] On 19-Sep-2007, at 1417, Andreas Ott wrote:
since when does ftp://ftp.arin.net/info/asn.txt contain dotted AS numbers?
Good question, for the reason you noted below (breaking scripts). If I was to guess I'd say it happened shortly after ARIN assigned their first 32-bit AS number.
Where is the new formatting documented, asn.h ?
http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as- representation-04.txt contains pertinent words, but I imagine it's not strictly accurate to call that documentation for ARIN's presentation format decisions (although maybe it is, to all intents and purposes, since I seem to think that George's draft mainly seeks to document practice that the RIRs have already agreed on, between themselves).
It just broke a scriptology we use to generate AS lookups for 'offline' customers (please don't ask :) ).
Joe
Joe Abley wrote:
On 19-Sep-2007, at 1417, Andreas Ott wrote:
since when does ftp://ftp.arin.net/info/asn.txt contain dotted AS numbers?
When I prepared my talk for the February NANOG meeting, there were 3 of them in the file. This must have happened between 1/1 and late January. (1/1 being the day they started handing out ASN32's).
Good question, for the reason you noted below (breaking scripts). If I was to guess I'd say it happened shortly after ARIN assigned their first 32-bit AS number.
Where is the new formatting documented, asn.h ?
http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as-representation... contains pertinent words, but I imagine it's not strictly accurate to call that documentation for ARIN's presentation format decisions (although maybe it is, to all intents and purposes, since I seem to think that George's draft mainly seeks to document practice that the RIRs have already agreed on, between themselves).
The draft Enke Chen draft/RFC proposing to extend the ASN space to 32 bits says nothing about the format. The first idea was to use X:Y, but this lead to confusion with community strings. X.Y didn't so this was informally used. Early 2006, proposals in all 5 regions asking the RIRs to start handing out ASN32 as of 1/1/2007. When implementation work started (summer of 2006), this document was submitted to describe the current practice. As this was the only document describing the format, this is what the RIRs started to use. Henk -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ # Lawyer: "Now sir, I'm sure you are an intelligent and honest man--" # Witness: "Thank you. If I weren't under oath, I'd return the compliment."
participants (6)
-
Andreas Ott -
Henk Uijterwaal -
James Blessing -
Jeroen Massar -
Joe Abley -
Kevin Loch