public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Cc: Spencer Norton <spencer.norton@norvi.tech>,
	Accounts <accounts@Norvitech.co.uk>
Subject: Re: [PATCH] importer: Filter non-global geofeed and RIR umbrella networks
Date: Tue, 20 Oct 2026 13:18:17 GMT	[thread overview]
Message-ID: <179250229752.3956232.3@ipfire.org> (raw)
In-Reply-To: <LV9PR18MB92761524DE329304D48F17E83EF6992@LV9PR18MB927615.namprd18.prod.outlook.com>

Hello Spencer,

thank you very much for this patch, and for the very thorough analysis. It has
been merged into the master branch:

  https://git.ipfire.org/?p=location/libloc.git;a=commit;h=6274fb37b8d63c9820720bb613418d8bc8a265ee

I have changed one thing on top of it, which is the fourth point: 2001::/23
has been set aside for protocol assignments, but not all of them are
unroutable. Some are being announced on purpose, like 2001:4:112::/48 of
AS112, which would have lost its AS number, and also 2001:3::/32 (AMT),
2001:20::/28 (ORCHIDv2) and 2001:30::/28 (Drone Remote ID). Therefore, we now
only drop Teredo (2001::/32), the benchmarking range (2001:2::/48) and ORCHID
(2001:10::/28) out of that block:

  https://git.ipfire.org/?p=location/libloc.git;a=commit;h=b8dd752c6fb89875b057fec5c832d3cc668f8de4

The changes will be in the database once the importer has run with them, and
I will close bug #13934 after that.

Best,
-Michael


  reply	other threads:[~2026-10-20 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18  3:17 Spencer Norton
2026-10-20 13:18 ` Michael Tremer [this message]
2026-10-20 15:45   ` Spencer Norton

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=179250229752.3956232.3@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=accounts@Norvitech.co.uk \
    --cc=location@lists.ipfire.org \
    --cc=spencer.norton@norvi.tech \
    /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