[address-policy-wg] IPv6 - Geolocation concerns

Generally speaking, the best way to deal with geolocation issues when subdelegating is to make sure that you create INET6NUM objects for your various subnets that include, at minimum, the country from which you expect to advertise them from. WHOIS serves as ground-floor data for most geo databases, so absent other signal, that’s a very good first step.

-C

> On Jan 31, 2022, at 8:10 AM, Michalak, Damian <v-Damian.Michalak at lionbridge.com> wrote:
> 
> 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 <http://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 <http://apple.com/> thinks I’m in Poland.
>  
> Thanks
>  
> -- 
> 
> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ <https://mailman.ripe.net/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20220131/b9d56da7/attachment.html>