From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: ASNs without AS name information (LACNIC and JPNIC)
Date: Sat, 18 Sep 2021 15:59:45 +0000 [thread overview]
Message-ID: <a065209d-f523-85a2-390e-747d4f47eb56@ipfire.org> (raw)
In-Reply-To: <21158eeb-b531-471c-4fe0-94cde6470139@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
Hi nusenu,
thanks for getting in touch again.
> Are there plans to add AS names for these regions as well or will this not improve in the near future (before 2022)?
I have not yet looked at JPNIC in detail. If they provide a feed similar to RIPE, AFRINIC, or APNIC, integrating
it should be done pretty quickly. (Same goes for TWNIC and KRNIC, since I am not sure whether their information
is mirrored back to APNIC...)
LACNIC is - well - tedious. Perhaps we are going to scrape RIPEstat for missing AS names, where we would have
this RIR covered. Personally, I would consider this the last option, but I don't think they will allow us to fetch
the complete information from their servers.
(This remains a task for ARIN as well, since we are still missing some country information for suballocations there.)
Having a lot of other ${dayjob}-related things on my plate, I cannot give you an ETA for all of this. Let's hope
it won't become 2022. :-)
Sorry for this rather vague answer.
Thanks, and best regards,
Peter Müller
next prev parent reply other threads:[~2021-09-18 15:59 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 [this message]
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
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=a065209d-f523-85a2-390e-747d4f47eb56@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