> > * Do I run the risk of being blacklisted for this practice?
>
> Risk? Blacklisted where?
>
> The risk of another ISP filtering your traffic for this is very low, almost
> certainly to the right of the decimal, but not mathematically zero to
> infinite decimal places. As I mentioned before, th
> I see a lot of replies about the legality. As mentioned I have legitimate
> reasons for doing this. I plan on serving customers in country.
> Your “legitimate” reason is to avoid someone else’s restrictions on the
> content they own. You are intentionally falsifying data to keep the owner of
On Apr 22, 2021, at 7:58 PM, nanoguser100 via NANOG wrote:
>
> I see a lot of replies about the legality. As mentioned I have legitimate
> reasons for doing this. I plan on serving customers in country.
Your “legitimate” reason is to avoid someone else’s restrictions on the content
they own.
The RIPE Database offers the “geoloc:” attribute on ORGANISATION and
INET(6)NUM objects that may or may not be used as an additional source of
information by these providers.
https://www.ripe.net/manage-ips-and-asns/db/tools/geolocation-in-the-ripe-database
https://labs.ripe.net/author/denis/geolo
On 4/22/2021 9:30 AM, Tom Beecher wrote:
While I agree with the overall sentiment of your message, I am curious ;
have there been any instances where an internet provider has been found
liable (criminally or civilly) for willfully misrepresenting IP
geolocation information?
How could there be
When an RIR asserts geo in Whois, it's derived from the organisational
data, but usually/often then self asserted. It was asserted by the
delegate, during registration.
When an RIR asserts geo in organisational data, it's self-asserted
through a filter of things like Dunn & Bradstreet and company
I see a lot of replies about the legality. As mentioned I have legitimate
reasons for doing this. I plan on serving customers in country.
My questions really are:
* Is most geo data simply derived from self reporting?
* Do these vendors have verification mechanisms?
* Going to the Estonia\German
Brian Turnbow via NANOG writes:
> If the address space is unassigned I'm not sure as it is not listed in the
> file of allocations that contains the country , but I would guess NL as the
> RIPE country of record.
I seem to remember they use ZZ for unknown geographical area.
jaap
On Apr 22, 2021, at 10:23 AM, Matthew Petach wrote:
> On Thu, Apr 22, 2021 at 7:12 AM nanoguser100 via NANOG
> wrote:
>> William,
>>
>> The plan is to carve out a /24 for "Estonia" and have special servers on it.
>> This would be the same /24 I'd have to use if I were to put a legitimate
>>
On 4/22/21 16:55, Brian Turnbow wrote:
AFAIK Ripe does not set a default, it is up to the LIR.
You can assign geoloc to orgs ans assignments
Ripe publishes a list of all allocations made to the provider and lists their
country of record.
If the address space is unassigned I'm not sure as it
>
> Question - if a country is not assigned to an allocation or sub-assignment,
> what does it default to within the RIPE region?
>
> In the AFRINIC region, for example, it would be MU (Mauritius), as that is
> where AFRINIC are located.
AFAIK Ripe does not set a default, it is up to the LIR.
Yo
I sincerely doubt that any actual *law* could be enforced against an ISP
which is a legal entity in one location, yet has multiple discrete /23 or
/24 blocks and without any obfuscation choose to announce them from
multiple different geographic locations. Configurations where an AS has
multiple isl
On Wed, Apr 21, 2021 at 12:21:26PM -0700, William Herrin wrote:
> a legal requirement that it be located in [Atlantis]
A legal requirement of whom? Undoubtedly the requirement is made of
provider of this theoretical service doing the restricting. Is that
"legal requirement" satisfied by asking a
On Thu, Apr 22, 2021 at 7:12 AM nanoguser100 via NANOG
wrote:
> William,
>
> The plan is to carve out a /24 for "Estonia" and have special servers on
> it. This would be the same /24 I'd have to use if I were to put a
> legitimate POP there. This also means I don't conflict with the real
> Germ
On 4/22/21 15:57, Brian Turnbow via NANOG wrote:
So to extend this further, you assign a class of IPs to a customer and
register it to them in the RIPE database.
Do you assign it to the customers address, in Estonia , or use the DC Address
which is in Germany?
Which could be the basis of
William,
The plan is to carve out a /24 for "Estonia" and have special servers on it.
This would be the same /24 I'd have to use if I were to put a legitimate POP
there. This also means I don't conflict with the real Germany.
I am just worried about violating the 'rules' of these providers an
Hi,
>>If the endpoint (e.g. web server) is physically located in Germany and
>>you're helping a client misrepresent that it's located in Estonia in
>>order to evade a legal requirement that it be located in Estonia then
>>you've made yourself a party to criminal fraud.
>While I agree with the ov
>
> If the endpoint (e.g. web server) is physically located in Germany and
> you're helping a client misrepresent that it's located in Estonia in
> order to evade a legal requirement that it be located in Estonia then
> you've made yourself a party to criminal fraud.
>
While I agree with the overa
On Wed, Apr 21, 2021 at 11:58 AM nanoguser100 via NANOG wrote:
> I wanted to get the communities' opinion on this.
>
> Increasingly I have run into 'niche needs' where a client has a few users in
> a country we don't have a POP, say Estonia. This is 'mainly' for
> localization but also in some
19 matches
Mail list logo
