But how does my application access it?
DHCP is not something that an application layer program should be allowed to
perform. It is a security issue. For good reason performing DHCP operations
requires privileges beyond mere network connectivity on Windows.
That is why configuring application programs from DHCP never caught on.
-----Original Message-----
From: John Schnizlein [mailto:jschnizl(_at_)cisco(_dot_)com]
Sent: Sunday, April 22, 2007 6:41 PM
To: David W. Hankins
Cc: GEOPRIV WG; ietf(_at_)ietf(_dot_)org
Subject: Re: [Geopriv] Confirmation of GEOPRIV IETF 68
Working Group Hums
The reason that DHCP is appropriate for information about the
location of the host is that the scope of DHCP administration
usually does match the local network to which the host is
attached. Location is local information.
John
On Apr 20, 2007, at 3:38 PM, David W. Hankins wrote:
The point is that the ISO L(x) is not what one considers
when judging
wether or not a certain configuration value "would make a good band
name. I mean DHCP option."
What we (strive to) consider instead is the administrative scope of
the configuration information, and wether it matches common and
practical use of DHCP.
On Apr 19, 2007, at 7:47 PM, David W. Hankins wrote:
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.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf