Hi, TL;DR: this will be an issue in some cases but not in others.
I know that this is the issue for some geoblocks, that is the original reason why we[1] requested multiple IPv6 prefixes from the RIPE NCC. To clarify, the issue is when this information is fetched from one of the delegation files available on ftp.ripe.net (and equivalents from other RIRs). Though I believe this workaround no longer works as I seem to recall the policy changing and requiring this to match the jurisdiction of the legal entity (or natural person) of the LIR. I think most geoip info is based on what the "country" attribute is set to in the inet(6)num object, but sadly this varies a lot and it is often difficult to know before you run into an issue. [1]: a LIR that I represent towards the NCC although this email is just sent in my personal capacity. -Cynthia On Mon, Jan 31, 2022 at 5:10 PM Michalak, Damian <[email protected]> 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? > > 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 > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/address-policy-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/address-policy-wg
