From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Question regarding delta between "delegated-ripencc-extended-latest" and Whois output
Date: Mon, 29 Jun 2020 17:30:51 +0000 [thread overview]
Message-ID: <c572f87e-46af-21c6-79ba-bd3ac64684ea@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Dear RIPE DB mailing list people,
we, the IPFire development team, just bumped across an IP address somewhere
in the 51.15.0.0/17 network (no abuse, we were just curious :-) ).
While the RIPE Whois server returned "NL" as the country of that subnet [1],
the "delegated-ripencc-extended-latest" file available at ftp.ripe.net [2] only
contains 51.15.0.0/16, which points to "FR".
Since the first one result contains the correct country code of that IP network,
I would like to ask why "delegated-ripencc-extended-latest" does not include
subnets like this, and where the Whois server fetches his answer from.
Did we miss something? Is there another or a better way of fetching precise
subnet data from RIPE? It would be great if someone could point us into the
right direction. :-)
Thanks, and best regards,
Peter Müller
[1] Relevant snippet of the Whois server output:
> inetnum: 51.15.0.0 - 51.15.63.255
> [...]
> country: NL
> [...]
[2] https://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-extended-latest,
relevant snippet of this file:
> ripencc|FR|ipv4|51.15.0.0|65536|19930901|assigned|925547da-35fb-4346-b464-aadff095c6ea
next reply other threads:[~2020-06-29 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 17:30 Peter Müller [this message]
2020-06-29 19:07 ` [db-wg] " Nick Hilliard
2020-06-29 19:54 ` Peter Müller
2020-06-29 20:21 ` Nick Hilliard
2020-06-29 20:52 ` Leo Vegoda
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=c572f87e-46af-21c6-79ba-bd3ac64684ea@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