Re: [100attendees] Incorrect GeoIP for IETF network addresses

[Michal Krsek <[e-mail]>]

Hi,

>>
>>> For BSSID: the MAC-to-coordinates mappings dont deserve much 
>>> consideration IMHO, as it's not IP.
>>
>> Sorry for my shortcut:
>>
>> BSSID is not on IP level, 
>
> BSSID - Basic Service Set ID, is a 48bit value, very much similar to 
> MAC addresses.  On an AP you have a 48bit BSSID, a 48bit MAC on the 
> WiFi interface and a 48bit MAC on its Ethernet interface.  The 3 are 
> distinct.  One would need to map the three to coordinates. Some map 
> just the BSSID, or just the Network Name, often known as ESSID which 
> is yet another value.  Sometime the Network Name is hidden, you want 
> it hidden, cant reveal.
>
> All these things are not IP.

they are not, but you can tell (over IP) to the client that GeoIP 
resolution based on underlying information is not producing relevant 
information.

Those clients DO IP communication with some GeoIP vendors.

Or, do we still need to work on human interraction, e.g. bringing GeoIP 
people to the bar, order them a few drinks and give them (under the 
table) small piece of dirty paper that shows them BSSID of "mobile APs" 
? Imagine that every car has AP functionality. GeoIP people will become 
permanently drunk.

Micahl