This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 - Geolocation concerns
- Previous message (by thread): [address-policy-wg] IPv6 - Using RIPE acquired prefix in other regions
- Next message (by thread): [address-policy-wg] IPv6 - Geolocation concerns
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michalak, Damian
v-Damian.Michalak at lionbridge.com
Mon Jan 31 17:10:14 CET 2022
Hi there,
This is a follow-up question to the older thread ("IPv6 - Using RIPE acquired prefix in other regions")
Situation:
I have acquired /32 IPv6 prefix from RIPE NCC. Prefix is registered for country: DE.
I'm going to create /48 subnets and advertise them from various locations all around the globe.
Question:
Do I have to be concerned about geo-location issues? For example someone in US opening Google and getting Google.de?
If so - what's the best way to address this?
P.S. That's certainly a concern in IPv4 - I do advertise in US a subnet of a bigger supernet (registered in Poland) and Apple.com thinks I'm in Poland.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20220131/3dd268e6/attachment.html>
- Previous message (by thread): [address-policy-wg] IPv6 - Using RIPE acquired prefix in other regions
- Next message (by thread): [address-policy-wg] IPv6 - Geolocation concerns
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]