Hi Laurent,
"...country attribute at inetnum level despite RIPE NCC has spent the last 20
years telling people they cannot rely on that attribute for IP location)."
This is the confusion - It is only the country values in the extended delegated
stats file, consistent, taken from the 'country' at
;
>> > When in the need to contact the GeoIP aggregators (MaxMind and others.)
>> > asking correction of some wrong data, I have to show some concrete
>> > information such as traceroute + registration re-assignment record.
>> > Geodeed if/when widely adop
ave to show some concrete
> information such as traceroute + registration re-assignment record. Geodeed
> if/when widely adopted may be the solution. In the meantime the "country:"
> attribute in INET(6)NUM object is helpful.
> >
> > Best regards
> > Éric
> >
&
the solution. In the meantime the "country:"
> attribute in INET(6)NUM object is helpful.
>
> Best regards
> Éric
>
> -Original Message-
> From: db-wg On Behalf Of denis walker via db-wg
> Sent: Wednesday, March 8, 2023 3:52 AM
> To: Leo Vegoda
> Cc: RIPE
Original Message-
From: db-wg On Behalf Of denis walker via db-wg
Sent: Wednesday, March 8, 2023 3:52 AM
To: Leo Vegoda
Cc: RIPE Database WG ; Havard Eidnes ; George
Michaelson
Subject: Re: [db-wg] country codes in the RIPE Database (was: ORGANISATION
country code)
CAUTION: This emai
Hi Denis,
On Tue, 7 Mar 2023 at 18:52, denis walker wrote:
> From my perspective as an analyst it's getting interesting now... Yes
> we can consider it as a complex problem needing a complex
> solution...but are either really complex? Maybe it is the environment
> that is complex and not this spe
Hi Randy
On Wed, 8 Mar 2023 at 03:11, Randy Bush wrote:
>
> > I suggest that this is not just a localized decision of the db-wg, but
> > has global implications.
>
> +1, and this aside from the idea having other fatal flaws, as discussed
> here before.
Can you please be a little more specific? W
Hi Leo
>From my perspective as an analyst it's getting interesting now... Yes
we can consider it as a complex problem needing a complex
solution...but are either really complex? Maybe it is the environment
that is complex and not this specific problem or solution.
On Wed, 8 Mar 2023 at 01:29, Leo
> I suggest that this is not just a localized decision of the db-wg, but
> has global implications.
+1, and this aside from the idea having other fatal flaws, as discussed
here before.
randy
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options
Hi Denis,
On Tue, 7 Mar 2023 at 16:20, denis walker wrote:
> > On Tue, 7 Mar 2023 at 14:29, George Michaelson via db-wg
> > wrote:
> >
> > [...]
> >
> > > I don't necessarily disagree with you about the risks here, but I
> > > suggest that the decision to deprecate or alter behavior with this
>
Hi Leo
On Tue, 7 Mar 2023 at 23:51, Leo Vegoda wrote:
>
> Hi,
>
> I strongly support what George has written.
>
> On Tue, 7 Mar 2023 at 14:29, George Michaelson via db-wg
> wrote:
>
> [...]
>
> > I don't necessarily disagree with you about the risks here, but I
> > suggest that the decision to
Hi George
Thanks for your comments. Of course global context is important in
these situations and I appreciate you raising this issue.
It says in the file:
https://ftp.ripe.net/pub/stats/ripencc/RIR-Statistics-Exchange-Format.txt
3.3 Record format:
...
cc= ISO 3166 2-letter count
Hi,
I strongly support what George has written.
On Tue, 7 Mar 2023 at 14:29, George Michaelson via db-wg wrote:
[...]
> I don't necessarily disagree with you about the risks here, but I
> suggest that the decision to deprecate or alter behavior with this
> field is not something which a single
I suggest that this is not just a localized decision of the db-wg, but
has global implications. You are discussing a field whose value is
interpreted both directly from WHOIS and RDAP, and less directly from
delegated files in the registry system across all the RIR. Your
consumers are my consumers,
HI Cynthia
On Thu, 2 Mar 2023 at 17:43, Cynthia Revström via db-wg wrote:
>
> Hi db-wg,
>
> I just want to start out by saying that I support efforts to try to better
> understand and document this.
> What I don't (currently) support is changing DB policy (policy in the form of
> RIPE documents
Dear RIPE DBWG,
...comments below, inline, please!
Le jeudi 26 janvier 2023, Ángel González Berdasco via db-wg
a écrit :
> 26-01-2023 17:46 +0100, Sylvain Baya wrote:
> > Le mardi 24 janvier 2023, denis walker via db-wg a
> > écrit :
> > > Colleagues
> > >
> > > [...]
> > >
> > > Most people s
Hi db-wg,
I just want to start out by saying that I support efforts to try to better
understand and document this.
What I don't (currently) support is changing DB policy (policy in the form
of RIPE documents or policy enforced by the RIPE DB software), especially
before we really know much about t
Dear RIPE DB-WG,
Hoping that this email finds you in good health!
Please see my comments below, inline...
Thanks.
Le lundi 20 février 2023, Leo Vegoda via db-wg a écrit :
>
> > [...]
> >
> > With clear explanations sent to all resource holders and/or maintainers
> of
> > the resource objects,
Hi Denis,
[...]
On Tue, 21 Feb 2023 at 05:42, denis walker wrote:
> On Mon, 20 Feb 2023 at 16:37, Leo Vegoda wrote:
> > My concern is that lots of users will not be aware of the change, or
> > not have the resources to adapt to it in a timely fashion. So, if any
> > change is made, it ought to
Hi Leo
On Mon, 20 Feb 2023 at 16:37, Leo Vegoda wrote:
>
> On Mon, 20 Feb 2023 at 07:25, denis walker wrote:
> > On Mon, 20 Feb 2023 at 15:58, Leo Vegoda wrote:
>
> [...]
>
> > > Setting semantics aside... I don't know whether changing definitions —
> > > and adding a missing definition is a de
On Mon, 20 Feb 2023 at 07:25, denis walker wrote:
> On Mon, 20 Feb 2023 at 15:58, Leo Vegoda wrote:
[...]
> > Setting semantics aside... I don't know whether changing definitions —
> > and adding a missing definition is a de facto change — would improve
> > things or make them worse. What resea
Hi Leo
On Mon, 20 Feb 2023 at 15:58, Leo Vegoda wrote:
>
> On Thu, 26 Jan 2023 at 07:18, denis walker wrote:
>
> [...]
>
> > This is exactly what I said. In the quoted para above I said "the
> > country codes have a well defined meaning", which you agree with. Then
> > I said "but when entered b
On Thu, 26 Jan 2023 at 07:18, denis walker wrote:
[...]
> This is exactly what I said. In the quoted para above I said "the
> country codes have a well defined meaning", which you agree with. Then
> I said "but when entered by users no one knows what it's purpose is.".
> Another way of saying no
Dear RIPE DBWG,
...comment below, please.
Le jeudi 26 janvier 2023, Ángel González Berdasco via db-wg
a écrit :
>
> >
> > >
> > > [...]
> > >
>
>
> I'm afraid even with detailed documentation available some people won't
> read them and make up their own meaning for the attributes. But there's
>
26-01-2023 17:46 +0100, Sylvain Baya wrote:
> Le mardi 24 janvier 2023, denis walker via db-wg a
> écrit :
> > Colleagues
> >
> > [...]
> >
> > Most people seem to assume it can be reliably used for geolocation
> > purposes. That would be the most obvious use case for this
> > attribute.
> > Ent
denis walker wrote:
> > What we are missing is a meaning for the application of these codes in
> > the context of the RIPE database.
>
> This is exactly what I said. In the quoted para above I said "the
> country codes have a well defined meaning", which you agree with. Then
> I said "but when ent
Dear RIPE DBWG,
Hope this email finds you in good health!
Please see my comment below, inline...
Le mardi 24 janvier 2023, denis walker via db-wg a écrit :
> Colleagues
>
> [...]
>
> Most people seem to assume it can be reliably used for geolocation
> purposes. That would be the most obvious us
Hi Leo
On Thu, 26 Jan 2023 at 13:48, Leo Vegoda wrote:
>
> On Thu, 26 Jan 2023 at 03:55, denis walker via db-wg wrote:
> >
> > Hi Ed
> >
> > Thanks for the explanation. But as I explained to Cynthia, "org-name:"
> > and "country:" are very different attributes. The org-name is just a
> > free te
On Thu, 26 Jan 2023 at 03:55, denis walker via db-wg wrote:
>
> Hi Ed
>
> Thanks for the explanation. But as I explained to Cynthia, "org-name:"
> and "country:" are very different attributes. The org-name is just a
> free text label by which an organisation is known. Whatever label is
> specified
Hi Ed
Thanks for the explanation. But as I explained to Cynthia, "org-name:"
and "country:" are very different attributes. The org-name is just a
free text label by which an organisation is known. Whatever label is
specified, people know what its purpose is, even if the value is not
verified by th
Hi Denis,
> On 24 Jan 2023, at 17:19, denis walker via db-wg wrote:
>
> Colleagues
>
> Following on from Havard's comments below I would like to expand the
> discussion to consider the general use of country codes in the RIPE
> Database. As I tend to write long emails that many people don't rea
Colleagues
Following on from Havard's comments below I would like to expand the
discussion to consider the general use of country codes in the RIPE
Database. As I tend to write long emails that many people don't read,
I'll summarise my main points first then expand on the details for
those who wan
32 matches
Mail list logo
