From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: ASNs without AS name information (LACNIC and JPNIC)
Date: Mon, 17 Jan 2022 09:09:57 +0000 [thread overview]
Message-ID: <666CB5D5-A340-4DEB-AB59-84E9B3D2F252@ipfire.org> (raw)
In-Reply-To: <ba81384c-6b2c-2a69-65ad-2cd49f77f72e@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Hello,
> On 16 Jan 2022, at 22:16, nusenu <nusenu-lists(a)riseup.net> wrote:
>
>>> Both AS lack an "aut-num" object in JPNIC, which is why there is no parseable information
>>> for them at hand in there. Not sure where RIPEstat gets their description from...
>>>
>>> Anyways, ARIN, LACNIC and a better approach to missing data is on my list for next week.
>>> I'll see what we can to then.
>> AS names (the holder's name) shown on RIPEstat come from the CIDR report
>> https://www.cidr-report.org/as2.0/
>> according to RIPE NCC's reply.
>> Maybe this is a one for all solution.
>
> Since you apparently don't like this data source
Apparently?
> and I always thought RIPEstat has pretty good data quality:
> Would you mind sharing your opinion on this?
I do not see the good data quality here. Some have proper names, others are called something like "XO-AS15”, or “CMCS”, or “AS17054”. This isn’t great.
Arguably, this is better than nothing and I wouldn’t mind using the description wherever we don’t have anything better, but it isn’t first choice.
@Peter: Do you want to look into extracting information from this?
-Michael
>
> kind regards,
> nusenu
> --
> https://nusenu.github.io
next prev parent reply other threads:[~2022-01-17 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 22:46 nusenu
2021-09-18 15:59 ` Peter Müller
2021-09-25 12:41 ` Peter Müller
2021-09-26 20:27 ` nusenu
2021-12-05 9:09 ` nusenu
2021-12-09 22:10 ` Peter Müller
2021-12-10 9:51 ` nusenu
2022-01-16 22:16 ` nusenu
2022-01-17 9:09 ` Michael Tremer [this message]
2022-01-18 21:10 ` Peter Müller
2022-01-19 8:17 ` Michael Tremer
2022-01-19 21:17 ` nusenu
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=666CB5D5-A340-4DEB-AB59-84E9B3D2F252@ipfire.org \
--to=michael.tremer@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