Re: IPv6 Geolocation per /64

2025-02-19 Thread Peter 'PMc' Much
On Tue, Feb 18, 2025 at 07:20:26PM -0500, Michael Richardson wrote: ! There is also https://www.rfc-editor.org/info/rfc9632. ! ! This document specifies how to augment the Routing Policy Specification ! Language (RPSL) inetnum: class to refer specifically to geofeed ! comma-separated values

Re: IPv6 Geolocation per /64

2025-02-18 Thread Peter 'PMc' Much
On Tue, Feb 18, 2025 at 09:48:02PM +, Andrew Pavlin wrote: ! Think about it. Who _has_ to know your physical/geographical address and its associated Internet address block to provide you with Internet service? Your ISP! Question: is an ISP legally oblidged to divulge their customer's locations

Re: IPv6 Geolocation per /64

2025-02-18 Thread Michael Richardson
There is also https://www.rfc-editor.org/info/rfc9632. This document specifies how to augment the Routing Policy Specification Language (RPSL) inetnum: class to refer specifically to geofeed comma-separated values (CSV) data files and describes an optional scheme that uses the Resource Pub

RE: IPv6 Geolocation per /64

2025-02-18 Thread Marc
> > > There's also a freely available service and API at https://ip-api.com > > you may find useful. > > I am a bit freaked out by the fact that both MaxMind (IPv6) and ip-api > (IPv4) were spot on with their reported locations a few minutes ago. We > are talking about two "hits" within a 10km ra

Re: IPv6 Geolocation per /64

2025-02-18 Thread Ralph Seichter via bind-users
* Rick Dicaire: > There's also a freely available service and API at https://ip-api.com > you may find useful. I am a bit freaked out by the fact that both MaxMind (IPv6) and ip-api (IPv4) were spot on with their reported locations a few minutes ago. We are talking about two "hits" within a 10km

Re: IPv6 Geolocation per /64

2025-02-18 Thread Andrew Pavlin
#x27;PMc' Much Sent: Tuesday, February 18, 2025 4:10:56 PM To: Michael De Roover Cc: bind-users@lists.isc.org Subject: Re: IPv6 Geolocation per /64 On Tue, Feb 18, 2025 at 08:48:15PM +0100, Michael De Roover wrote: ! Hi all, ! ! > It may be inside DNS, or it may be elsewhere, I do not know

Re: IPv6 Geolocation per /64

2025-02-18 Thread Michael De Roover
On Tuesday, February 18, 2025 9:38:58 PM CET Peter 'PMc' Much wrote: > Yes, that is the point. If they have such a service, then somehow > they must get to that information. > And there is only one source in the world from where they can > originally get my address, which is - me. > Then they make

Re: IPv6 Geolocation per /64

2025-02-18 Thread Michael De Roover
On Tuesday, February 18, 2025 9:59:42 PM CET you wrote: > Yes, certainly. But let me have You consider a certain problem with > such approach: there are still a few reluctant people in the world, > people who indeed seem to not enjoy receiving advertisment spam all > day and all night long. > > No

Re: IPv6 Geolocation per /64

2025-02-18 Thread Michael De Roover
On Tuesday, February 18, 2025 10:06:35 PM CET Peter 'PMc' Much wrote: > On Tue, Feb 18, 2025 at 09:51:51PM +0100, Michael De Roover wrote: > ! On Tuesday, February 18, 2025 9:38:58 PM CET Peter 'PMc' Much wrote: > ! > Then they make a business of selling my own information back to me - > ! > and I

Re: IPv6 Geolocation per /64

2025-02-18 Thread Peter 'PMc' Much
On Tue, Feb 18, 2025 at 08:48:15PM +0100, Michael De Roover wrote: ! Hi all, ! ! > It may be inside DNS, or it may be elsewhere, I do not know. There ! > is a DNS "LOC" record, but that doesn't seem to be used anymore. It ! > seems to be something else. But what, and where? ! I find it a shame tha

Re: IPv6 Geolocation per /64

2025-02-18 Thread Peter 'PMc' Much
On Tue, Feb 18, 2025 at 09:51:51PM +0100, Michael De Roover wrote: ! On Tuesday, February 18, 2025 9:38:58 PM CET Peter 'PMc' Much wrote: ! > Then they make a business of selling my own information back to me - ! > and I would like to know how they do that. ! ! Hehe.. about that... It may not be

Re: IPv6 Geolocation per /64

2025-02-18 Thread Peter 'PMc' Much
On Tue, Feb 18, 2025 at 08:04:28PM +0100, Marco Moock wrote: ! Am 18.02.2025 um 18:50:31 Uhr schrieb Peter 'PMc' Much: ! ! > Consideration: ! >Since every /64 in IPv6 carries it's own distinct geolocation info, ! >there must be somewhere a database of -quick average- 2^64 = ! >18446744

Re: IPv6 Geolocation per /64

2025-02-18 Thread Michael De Roover
On Tuesday, February 18, 2025 8:48:15 PM CET Michael De Roover wrote: > I find it a shame that this record is no longer in use. GeoIP is anything > but accurate, and GPS data is not reasonable to request from servers. Not > like you can just hook up a GPS receiver to a VPS. Even from individual > u

Re: IPv6 Geolocation per /64

2025-02-18 Thread Michael De Roover
Hi all, > It may be inside DNS, or it may be elsewhere, I do not know. There > is a DNS "LOC" record, but that doesn't seem to be used anymore. It > seems to be something else. But what, and where? I find it a shame that this record is no longer in use. GeoIP is anything but accurate, and GPS dat

Re: IPv6 Geolocation per /64

2025-02-18 Thread Rick Dicaire
On Tue, Feb 18, 2025 at 2:04 PM Marco Moock wrote: > I can't help you with that, although Maxmind has such a service. > https://www.maxmind.com/en/locate-my-ip-address > There's also a freely available service and API at https://ip-api.com you may find useful. -- Visit https://lists.isc.org/mai

Re: IPv6 Geolocation per /64

2025-02-18 Thread Marco Moock
Am 18.02.2025 um 18:50:31 Uhr schrieb Peter 'PMc' Much: > Consideration: >Since every /64 in IPv6 carries it's own distinct geolocation info, >there must be somewhere a database of -quick average- 2^64 = >18446744073709551616 records. Much less. Only 2000::/3 is GUA and only a small a