Re: [Geopriv] draft-ietf-geopriv-rfc3825bis

From: Bernard Aboba ^lt;bernard_aboba@hotmail.com>
Date: Tue Aug 10 2010 - 17:33:37 EDT

Marc Linsner said:

"You might want to go back and figure out why this text was removed and suggest that it's put back in, or modified and put back in."

[BA] I've opened Ticket #38 on this. Some questions on the original text:

a. Is the text referring to use of the DHCP option or inclusion of the option format in other standards such as 11k?
11k allows the station knowledge of the location of the AP or itself, depending on the query. My impression was that
3825bis wasn't meant to update 11k though, right?

b. Assuming that we are talking about the DHCP option, would there be an assumption that the AP is acting as a
DHCP relay, or that RADIUS attributes (such as NAS-Identifier or NAS-IP-Adress) were being passed to the DHCP
server? Otherwise, it wasn't clear to me how the DHCP server would be made aware of the location of the AP, so
that it could respond appropriately.

c. Assuming that the DHCP server is returning the AP location, why would additional mechanisms like GPS or a
list of APs close to the client be needed? If the host had GPS shouldn't it use that instead? Would the list of
APs be used for triangulation?

 " Wireless hosts can utilize this option to gain knowledge of the
    location of the radio access point used during host configuration,
    but would need some more exotic mechanisms, maybe GPS, or maybe a
    future DHCP option, which includes a list of geo-locations like that
    defined here, containing the locations of the radio access points
    that are close to the client"

                                               

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
Received on Tue, 10 Aug 2010 14:33:37 -0700

This archive was generated by hypermail 2.1.8 : Tue Aug 10 2010 - 17:33:49 EDT