From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: ASNs without AS name information (LACNIC and JPNIC)
Date: Wed, 19 Jan 2022 08:17:53 +0000 [thread overview]
Message-ID: <04F7129C-AA45-4A36-87E0-B355E8E332DB@ipfire.org> (raw)
In-Reply-To: <fbb35e19-b74c-e5d9-78a0-21e37be2b9d7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]
Hello,
> On 18 Jan 2022, at 21:10, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello nusenu,
> hello Michael,
>
>> Since you apparently don't like this data source
>> and I always thought RIPEstat has pretty good data quality:
>> Would you mind sharing your opinion on this?
>
> sorry for not replying on this sooner. Actually, I do not like or dislike RIPEstat; I just did
> not have sufficient time to made myself an educated opinion on this.
>
> At the moment, things are quite packed on my end, but that will hopefully over at the beginning
> of February. So, this is not forgotten or silently discarded, but just a very tardy reply due
> to my "load average"...
>
>> @Peter: Do you want to look into extracting information from this?
>
> Yes.
>
> Without looking at the amount of queries we'd probably need to do: Do you think this makes sense
> while running the location-importer, or should this become a dedicated script, which we can run
> in the background all the time, so it won't slow down the daily generation of the actual database.
>
> In case of the latter, we could actually do some scraping on the ARIN AS names, too. Since we keep
> track of their source, this should not be too hard, and if we get some more human-readable names
> for some of them, it might be worth the effort.
I thought we were talking about parsing an HTML table. That should not be a process that is either complicated nor something I would call scraping.
Scraping is what I would consider sending one request per piece of information you would want to obtain and this is always a bad idea. It is slow, it has a lot of overhead on our side and of course on the server side - this is not what a good citizen of the internet would do. So I would be against this. Most places have this excluded in their t&cs for exactly this reason.
-Michael
>
> Thanks, and best regards,
> Peter Müller
next prev parent reply other threads:[~2022-01-19 8:17 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
2022-01-18 21:10 ` Peter Müller
2022-01-19 8:17 ` Michael Tremer [this message]
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=04F7129C-AA45-4A36-87E0-B355E8E332DB@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