public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
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: Sat, 10 Jul 2021 22:17:05 +0200	[thread overview]
Message-ID: <5d567f46-6b08-51d5-a96e-1cbd83907284@ipfire.org> (raw)
In-Reply-To: <c70d4288-17b2-5c5c-8f0e-d65bb906ac32@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

Hello nusenu,

>> 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. 

just a quick follow-up on this.

Yesterday, we released libloc 0.9.7 (see https://source.ipfire.org/releases/libloc/ for its source .tar.gz),
which contains the ARIN AS names change you mentioned initially. Also, generated databases are now significantly
more accurate for IP space being part of Amazon AWS, which we mostly returned "US" before.

All location databases and their corresponding database.txt dumps generated after Fri, 9 Jul 2021 23:10:48 UTC
should now include AS names for ARIN space. Just thought you might want to know. :-)

Please drop us a line here in case of any questions, bugs, or comments.

Thanks, and best regards,
Peter Müller

  reply	other threads:[~2021-07-10 20:17 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
2021-07-10 20:17       ` Peter Müller [this message]
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=5d567f46-6b08-51d5-a96e-1cbd83907284@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