From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: incorporation state of ARIN's asn.txt / LACNIC AS name data
Date: Sun, 27 Jun 2021 20:13:16 +0000 [thread overview]
Message-ID: <c70d4288-17b2-5c5c-8f0e-d65bb906ac32@ipfire.org> (raw)
In-Reply-To: <20cbf1a1-1c08-b610-e6a8-519545e168ec@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]
Hi nusenu,
thanks for your response.
> out of curiosity: I haven't understood your differentiation between "human-readable" and "technical" AS names.
> Would you mind elaborating on your definitions of human-readable AS names?
I certainly don't mind, and it's not an accurate definition either. If I may pick an arbitrary example from the
ARIN asn.txt file:
> 7843 TWC-7843-BB IPADD1-ARIN (Abuse), IPADD1-ARIN (Admin), IPADD1-ARIN (Tech)
So, for AS7843, "TWC-7843-BB" is the name this file supplies to us - which is not very telling. The description
field of the corresponding organisation handle is ("Charter Communications Inc"), but we lack that information
for ARIN and LACNIC space.
This is why I consider asn.txt to contain "technical" names, which are not necessarily suitable for end-user
consumption - although some companies, such as DigitalOcean, do a better job to put meaningful strings in there.
On the second thought, however, this again boils down to a missing full dump of the ARIN database...
> with regards to LACNIC: Maybe their bulk whois data is something you find useful? (I didn't use it myself)
Thanks for the hint, I was unaware of that possibility. Skimming through the terms of conditions, however, I
somehow doubt this would be suitable, as we
(a) are going to redistribute the data in some way, which LACNIC ToS forbid (based on my humble understanding)
(b) are probably not going to snail mail anything from Europe to Uruguay :-)
@Michael: That is, of course, unless your opinion differs. ;-)
ARIN offers a similar channel (https://www.arin.net/reference/research/bulkwhois/). We would get organisation
handle names from there as well, but it seems to miss country information for suballocations, too (say an AOL
dial-up block assigned to LATAM or similar).
So, at the moment, I see this kind of ambivalent...
> Do you have a rough estimate on when this next version will be released?
We are not making any guarantees on that front. I am currently short on spare time, but would expect this
to be released within the next couple of weeks.
Thanks, and best regards,
Peter Müller
next prev parent reply other threads:[~2021-06-27 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 17:07 incorporation state of ARIN's asn.txt nusenu
2021-06-26 19:46 ` Peter Müller
2021-06-27 10:14 ` incorporation state of ARIN's asn.txt / LACNIC AS name data nusenu
2021-06-27 20:13 ` Peter Müller [this message]
2021-07-10 20:17 ` Peter Müller
2021-07-10 21:46 ` nusenu
2021-07-14 16:43 ` Michael Tremer
2021-07-14 21:03 ` nusenu
2021-07-15 15:49 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c70d4288-17b2-5c5c-8f0e-d65bb906ac32@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=location@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox