Supported format for Client Identifier.
David W. Hankins
dhankins at isc.org
Tue Jun 16 21:39:13 UTC 2009
On Tue, Jun 16, 2009 at 06:09:29PM +0530, pat wrote:
> What is the format of the Client Identifier option supported by the ISC DHCP
As described in RFC 2131, ISC DHCP's server treats the client
identifier option as an 'opaque key, not to be interpreted', it makes
no attempt to consume subcontents. RFC 4361 does not update this
You may safely use quotations from _War & Peace_ as your client
identifier (barring packet size limitations). ISC dhcpd won't mind.
> Since RFC4361 supersedes RFC2132, is it safe to ask Redback to implement it
> using the format specified in RFC 4361?
The short answer is that it is safe.
But you should think about your migration plan (a pure ops issue), and
you should know that the DHCP server may have a slightly altered
performance profile (it will need to perform extra malloc/free calls
than it normally would have).
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the dhcp-users