[arin-tech-discuss] SWIP and GeoIP

[Andy Newton]

Brian,

For what it is worth, Google has a proposal implemented by a handful for
network operators called GeoFeeds. They are currently attempting to have
this adopted by the IETF GEOPRIV working group so that it is an RFC. Their
current document is here:
http://tools.ietf.org/html/draft-google-self-published-geofeeds-02

At present, reporting of the geofeeds is very manual and adhoc, but their
hope is to have a standardized way for discovery of these feeds (ideas are
documented in their draft).

Andy Newton,
Chief Engineer, ARIN

On 11/22/13 10:50 AM, "Brian Rak" <brak at gameservers.com> wrote:

>So, for lack of a better option we've taken the step of creating an
>ORGID for each location, and assigning subnets to that.  We'll have to
>wait and see how it works out...
>
>On 10/8/2013 10:41 AM, Brian Rak wrote:
>> We have a customer who operates VPN services with us.  They have their
>> own ARIN OrgID, and we would like to be able to reassign all their IP
>> addresses to that organization (so that they can receive any abuse
>> reports directly, rather then having to relay them).
>>
>> They have reported to us that various GeoIP providers are using the
>> location of the ARIN contact to determine where an IP is located. The
>> customer would very much prefer that the location of the IPs match the
>> datacenter's location, rather then the customer's location.
>>
>> Does anyone have suggestions for handling this properly?  Looking at
>> the data returned by WHOIS, it seems the only way they're going to be
>> able to specify a location is by creating a separate organization and
>> contact for each datacenter.  Is that the best solution here?
>> _______________________________________________
>> arin-tech-discuss mailing list
>> arin-tech-discuss at arin.net
>> http://lists.arin.net/mailman/listinfo/arin-tech-discuss
>
>_______________________________________________
>arin-tech-discuss mailing list
>arin-tech-discuss at arin.net
>http://lists.arin.net/mailman/listinfo/arin-tech-discuss
>