network location = Orlando?
Reported by: |
paitken@… |
Owned by: |
nkukich@… |
Priority:
|
trivial
|
Milestone:
|
ietf-087
|
Component:
|
incoming
|
Keywords:
|
|
Cc:
|
|
My Current Location:
|
|
My MAC Address:
|
|
My OS:
|
|
I connected my cellphone to the .1x network; it picked up my location as
Orlando, Florida and set my time to that TZ :-(
Facebook checkin suggested many Orlando locations as being close bye.
P.
Change history (3)
Component: |
incoming →
other
|
Owner: |
changed from llynch@… to nkukich@…
|
Status: |
new →
assigned
|
Component: |
other →
incoming
|
Priority: |
tbd →
trivial
|
Resolution: |
→ not broken
|
Status: |
assigned →
closed
|
Milestone: |
ietf-87 →
ietf-087
|
The issue we have with the geolocation services is two-fold in that the data used to Geolocate an advertised network is collected intermittently, and that it is viewed as an aggregate. It's the same problem we see at NANOG and ICANN (and really any network that advertises public space and moves around). We've had limited success with communicating our hardware addresses to the Skyhook service in advance of an event (I did this with NANOG), and with attempting to alert other GL providers like Google.
So yes, it is going to show you as being in Orlando, and it's probably going to show you as being in Berlin while we are in Vancouver this fall. It's been an ongoing process with the providers and at this point, no resolution exists. We are working on a solution in which we start advertising our IP space well in advance of the meeting using a Linux box that pushes traffic occasionally (just advertising doesn't work/the services require traffic to update GL), but this solution is still just on paper.
Sorry for any trouble this has caused.
Replying to paitken@…: