Re: [Geopriv] Confirmation of GEOPRIV IETF 68 Working Group Hums

On Thu, Apr 19, 2007 at 03:38:40PM -0700, Hallam-Baker, Phillip wrote:
> DHCP is a layer 3 technology that talks directly to layer 2.
DHCP is a technology that dynamically configures hosts.

If a host has a configuration knob that might reasonably and
properly be set by the systems administrator or the network you
are presently attached to, then it is reasonable and proper to
configure it via DHCP.

DHCP would be the wrong tool to configure how, in what frequency,
or in what manner an application would directly contact a specific
remotely administered service, such as a distant web server.  DNS
would be the correct tool for that sort of job, having as it does
a global reach, and fate sharing.


If GEOPRIV is truthfully a global service the client communicates
with directly without the local network operator's involvement,
then I think it should be configured by whatever global distribution
means is reasonable.

My impression is that GEOPRIV is a service that is provided by
the local network to which the client is attached, and as such
under the purview of that network's operator and DHCP, but I admit
to not following it very closely.

-- 
David W. Hankins        "If you don't do it right the first time,
Software Engineer               you'll just have to do it again."
Internet Systems Consortium, Inc.       -- Jack T. Hankins

pgpfHn26VYdcZ.pgp
Description: PGP signature

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf