This document fits within the GEOPRIV architecture as defined by RFC 3693.
Generally, location information is transmitted from the DHCP server to
the DHCP client. Under limited special circumstances, a DHCP client may
want to inform the DHCP server of its current location, e.g., to
facilitate system management of wireless end systems equipped with
location measurement equipment such as GPS. Thus, clients MAY implement
the transmission of location information to the server. Unlike the
server-to-client transmission, this poses unique privacy concerns since
the client has no way to express its detailed privacy preferences to the
server. For example, clients may not want the server to use location
information for anything but system management and emergency calling
purposes. To limit the privacy exposure, all client-provided location
information has an implied privacy policy that only allows usage by the
receiving administrative domain. It MUST NOT be forwarded to other
administrative domains.
Old location information MUST be discarded when updated by a client in a
subsequent transaction, when the lease is released by the client, or the
lease expires.
The DHCP MUST use the unicast DHCPINFORM request for this purpose. In
general, the client MUST NOT broadcast or multicast location
information.
Implementations MUST allow clients to be configured so that they do not
send location information to the server and SHOULD operate on an opt-in
basis, i.e., in a default configuration, no location information is
transmitted to the server.