From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: location@lists.ipfire.org Subject: Re: ASNs without AS name information (LACNIC and JPNIC) Date: Sat, 18 Sep 2021 15:59:45 +0000 Message-ID: In-Reply-To: <21158eeb-b531-471c-4fe0-94cde6470139@riseup.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1736322390146321980==" List-Id: --===============1736322390146321980== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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)?=20 I have not yet looked at JPNIC in detail. If they provide a feed similar to R= IPE, 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 missi= ng AS names, where we would have this RIR covered. Personally, I would consider this the last option, but I do= n'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 countr= y 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=C3=BCller --===============1736322390146321980==--