From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: [PATCH] location-importer.in: delete 6to4 IPv6 space as well
Date: Sat, 16 Jan 2021 19:05:33 +0100 [thread overview]
Message-ID: <0fdbd9d4-83c6-8567-a093-a5c571f55835@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
2002::/16 is an anycast prefix for 6to4 scenarios, as specified in RFC
3068. We currently process an announcement from Hurricane Electric for
it, and since it is an anycast network, multiple entities across the
world announce it as well.
Thereof, it does not make sense to include it in the database - as of
today, we do not have a country for it, either.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
src/python/location-importer.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/python/location-importer.in b/src/python/location-importer.in
index a4be445..1a025bb 100644
--- a/src/python/location-importer.in
+++ b/src/python/location-importer.in
@@ -768,8 +768,9 @@ class CLI(object):
-- DELETE link local address space
DELETE FROM announcements WHERE family(network) = 4 AND network <<= '169.254.0.0/16';
- -- DELETE IPv6 to IPv4 (6to4) address space
+ -- DELETE IPv6 to IPv4 (6to4) address space (RFC 3068)
DELETE FROM announcements WHERE family(network) = 4 AND network <<= '192.88.99.0/24';
+ DELETE FROM announcements WHERE family(network) = 6 AND network <<= '2002::/16';
-- DELETE multicast and reserved address space
DELETE FROM announcements WHERE family(network) = 4 AND network <<= '224.0.0.0/4';
--
2.26.2
next reply other threads:[~2021-01-16 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 18:05 Peter Müller [this message]
2021-01-25 21:30 ` 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=0fdbd9d4-83c6-8567-a093-a5c571f55835@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