| blob | b20b5aa9f866adcc6e1bfed8116acfd7d6a902c3 |
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
8 body {
12 }
16 }
25 }
29 }
33 }
39 }
44 }
50 }
54 /* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
56 /* This is the key. */
60 }
64 }
67 /* The span will display just on :hover state. */
75 }
92 /* RFC-2629 <spanx>s and <artwork>s. */
100 }
101 pre {
104 }
115 /* RFC-2629 <texttable>s. */
119 }
122 th {
125 }
132 }
139 }
141 </head>
142 <body>
143 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
144 <table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
149 </table></td></tr></table>
154 <p>This document describes a collection of reference material
155 to which ISC DHCP has been implemented as well as a more
156 complete listing of references for DHCP and DHCPv6 protocols.
157 </p>
161 Consortium, Inc. ("ISC")
162 </p>
163 <p>Permission to use, copy, modify, and distribute this software for
164 any purpose with or without fee is hereby granted, provided that the
165 above copyright notice and this permission notice appear in all
166 copies.
167 </p>
169 WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
170 MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR
171 ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
172 WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
173 ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
174 OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
179 Introduction<br />
180 <br />
182 Definition: Reference Implementation<br />
183 <br />
185 Low Layer References<br />
187 Ethernet Protocol References<br />
189 Token Ring Protocol References<br />
191 FDDI Protocol References<br />
195 Unicast Datagram Protocol References<br />
196 <br />
198 BOOTP Protocol References<br />
199 <br />
201 DHCPv4 Protocol References<br />
203 DHCPv4 Protocol<br />
205 Core Protocol References<br />
207 DHCPv4 Option References<br />
209 Relay Agent Information Option Options<br />
211 Dynamic DNS Updates References<br />
213 Experimental: Failover References<br />
215 DHCP Procedures<br />
216 <br />
218 DHCPv6 Protocol References<br />
220 DHCPv6 Protocol References<br />
222 DHCPv6 Options References<br />
223 <br />
225 References<br />
227 Published DHCPv4 References<br />
229 Published Common (DHCPv4/DHCPv6) References<br />
231 Published DHCPv6 References<br />
232 <br />
234 Authors' Addresses<br />
235 </p>
239 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
241 Introduction</h3>
243 <p>As a little historical anecdote, ISC DHCP once packaged all the
244 relevant RFCs and standards documents along with the software
245 package. Until one day when a voice was heard from one of the
246 many fine institutions that build and distribute this software...
247 they took issue with the IETF's copyright on the RFC's. It
248 seems the IETF's copyrights don't allow modification of RFC's
249 (except for translation purposes).
250 </p>
251 <p>Our main purpose in providing the RFCs is to aid in
252 documentation, but since RFCs are now available widely from many
253 points of distribution on the Internet, there is no real need to
254 provide the documents themselves. So, this document has been
255 created in their stead, to list the various IETF RFCs one might
256 want to read, and to comment on how well (or poorly) we have
257 managed to implement them.
258 </p>
260 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
262 Definition: Reference Implementation</h3>
264 <p>ISC DHCP, much like its other cousins in ISC software, is
265 self-described as a 'Reference Implementation.' There has been
266 a great deal of confusion about this term. Some people seem to
267 think that this term applies to any software that once passed
268 a piece of reference material on its way to market (but may do
269 quite a lot of things that aren't described in any reference, or
270 may choose to ignore the reference it saw entirely). Other folks
271 get confused by the word 'reference' and understand that to mean
272 that there is some special status applied to the software - that
273 the software itself is the reference by which all other software
274 is measured. Something along the lines of being "The DHCP
275 Protocol's Reference Clock," it is supposed.
276 </p>
277 <p>The truth is actually quite a lot simpler. Reference
278 implementations are software packages which were written
279 to behave precisely as appears in reference material. They
280 are written "to match reference."
281 </p>
282 <p>If the software has a behaviour that manifests itself
283 externally (whether it be something as simple as the 'wire
284 format' or something higher level, such as a complicated
285 behaviour that arises from multiple message exchanges), that
286 behaviour must be found in a reference document.
287 </p>
288 <p>Anything else is a bug, the only question is whether the
289 bug is in reference or software (failing to implement the
290 reference).
291 </p>
292 <p>This means:
293 </p>
294 <p>
295 </p>
297 <li>To produce new externally-visible behaviour, one must first
298 provide a reference.
299 </li>
300 <li>Before changing externally visible behaviour to work around
301 simple incompatibilities in any other implementation, one must
302 first provide a reference.
303 </li>
304 </ul><p>
306 </p>
307 <p>That is the lofty goal, at any rate. It's well understood that,
308 especially because the ISC DHCP Software package has not always been
309 held to this standard (but not entirely due to it), there are many
310 non-referenced behaviours within ISC DHCP.
311 </p>
312 <p>The primary goal of reference implementation is to prove the
313 reference material. If the reference material is good, then you
314 should be able to sit down and write a program that implements the
315 reference, to the word, and come to an implementation that
316 is distinguishable from others in the details, but not in the
317 facts of operating the protocol. This means that there is no
318 need for 'special knowledge' to work around arcane problems that
319 were left undocumented. No secret handshakes need to be learned
320 to be imparted with the necessary "real documentation".
321 </p>
322 <p>Also, by accepting only reference as the guidebook for ISC
323 DHCP's software implementation, anyone who can make an impact on
324 the color texture or form of that reference has a (somewhat
325 indirect) voice in ISC DHCP's software design. As the IETF RFC's
326 have been selected as the source of reference, that means everyone
327 on the Internet with the will to participate has a say.
328 </p>
330 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
332 Low Layer References</h3>
335 'Ethernet' framing, Token Ring, and FDDI. In order to bridge the
336 gap there between these physical and DHCP layers, it must also
337 implement IP and UDP framing.
338 </p>
339 <p>The reason for this stems from Unix systems' handling of BSD
340 sockets (the general way one might engage in transmission of UDP
341 packets) on unconfigured interfaces, or even the handling of
342 broadcast addressing on configured interfaces.
343 </p>
344 <p>There are a few things that DHCP servers, relays, and clients all
345 need to do in order to speak the DHCP protocol in strict compliance
346 with <a class='info' href='#RFC2131'>[RFC2131]<span> (</span><span class='info'>Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a>.
348 </p>
351 IP:255.255.255.255 LinkLayer:Broadcast on an unconfigured (no IP
352 address yet) interface.
353 </li>
354 <li>Receive a UDP packet from IP:remote-system LinkLayer:remote-system,
355 destined to IP:255.255.255.255 LinkLayer:Broadcast, again on an
356 unconfigured interface.
357 </li>
358 <li>Transmit a UDP packet from IP:Self, Ethernet:Self, destined to
359 IP:remote-system LinkLayer:remote-system, without transmitting a
360 single ARP.
361 </li>
362 <li>And of course the simple case, a regular IP unicast that is
363 routed via the usual means (so it may be direct to a local system,
364 with ARP providing the glue, or it may be to a remote system via
365 one or more routers as normal). In this case, the interfaces are
366 always configured.
367 </li>
368 </ol>
370 <p>The above isn't as simple as it sounds on a regular BSD socket.
371 Many unix implementations will transmit broadcasts not to
373 subnet). Such packets are not received by several known DHCP client
374 implementations - and it's not their fault, <a class='info' href='#RFC2131'>[RFC2131]<span> (</span><span class='info'>Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a>
375 very explicitly demands that these packets' IP destination
376 addresses be set to 255.255.255.255.
377 </p>
379 modern unixes...so long as the interface is configured. When there
380 is no IPv4 address on the interface, things become much more murky.
381 </p>
382 <p>So, for this convoluted and unfortunate state of affairs in the
383 unix systems of the day ISC DHCP was manufactured, in order to do
384 what it needs not only to implement the reference but to interoperate
385 with other implementations, the software must create some form of
386 raw socket to operate on.
387 </p>
388 <p>What it actually does is create, for each interface detected on
389 the system, a Berkeley Packet Filter socket (or equivalent), and
390 program it with a filter that brings in only DHCP packets. A
391 "fallback" UDP Berkeley socket is generally also created, a single
392 one no matter how many interfaces. Should the software need to
393 transmit a contrived packet to the local network the packet is
394 formed piece by piece and transmitted via the BPF socket. Hence
395 the need to implement many forms of Link Layer framing and above.
396 The software gets away with not having to implement IP routing
397 tables as well by simply utilizing the aforementioned 'fallback'
398 UDP socket when unicasting between two configured systems is
399 needed.
400 </p>
401 <p>Modern unixes have opened up some facilities that diminish how
402 much of this sort of nefarious kludgery is necessary, but have not
403 found the state of affairs absolutely resolved. In particular,
404 one might now unicast without ARP by inserting an entry into the
405 ARP cache prior to transmitting. Unconfigured interfaces remain
406 the sticking point, however...on virtually no modern unixes is
407 it possible to receive broadcast packets unless a local IPv4
408 address has been configured, unless it is done with raw sockets.
409 </p>
411 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
413 Ethernet Protocol References</h3>
416 of IEEE 802.2. No good reference of this framing is known to exist
417 at this time, but it is vaguely described in <a class='info' href='#RFC0894'>[RFC0894]<span> (</span><span class='info'>Hornig, C., “Standard for the transmission of IP datagrams over Ethernet networks,” April 1984.</span><span>)</span></a>
418 see the section titled "Packet format"), and
419 the following URL is also thought to be useful.
420 </p>
421 <p><a href='http://en.wikipedia.org/wiki/DIX_Ethernet'>http://en.wikipedia.org/wiki/DIX_Ethernet</a>
422 </p>
424 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
426 Token Ring Protocol References</h3>
429 DHCP.
430 </p>
432 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
434 FDDI Protocol References</h3>
436 <p><a class='info' href='#RFC1188'>[RFC1188]<span> (</span><span class='info'>Katz, D., “Proposed Standard for the Transmission of IP Datagrams over FDDI Networks,” October 1990.</span><span>)</span></a> is the most helpful
437 reference ISC DHCP has used to form FDDI packets.
438 </p>
440 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
444 <p><a class='info' href='#RFC0760'>RFC760<span> (</span><span class='info'>Postel, J., “DoD standard Internet Protocol,” January 1980.</span><span>)</span></a> [RFC0760] fundamentally defines the
445 bare IPv4 protocol which ISC DHCP implements.
446 </p>
448 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
450 Unicast Datagram Protocol References</h3>
452 <p><a class='info' href='#RFC0768'>RFC768<span> (</span><span class='info'>Postel, J., “User Datagram Protocol,” August 1980.</span><span>)</span></a> [RFC0768] defines the User Datagram
453 Protocol that ultimately carries the DHCP or BOOTP protocol. The
455 ports are irrelevant.
456 </p>
458 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
460 BOOTP Protocol References</h3>
462 <p>The DHCP Protocol is strange among protocols in that it is
463 grafted over the top of another protocol - BOOTP (but we don't
465 and DHCP share UDP packet formats - DHCP is merely a conventional
466 use of both BOOTP header fields and the trailing 'options' space.
467 </p>
468 <p>The ISC DHCP server supports BOOTP clients conforming to
469 <a class='info' href='#RFC0951'>RFC951<span> (</span><span class='info'>Croft, B. and J. Gilmore, “Bootstrap Protocol,” September 1985.</span><span>)</span></a> [RFC0951] and <a class='info' href='#RFC1542'>RFC1542<span> (</span><span class='info'>Wimer, W., “Clarifications and Extensions for the Bootstrap Protocol,” October 1993.</span><span>)</span></a> [RFC1542].
470 </p>
472 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
474 DHCPv4 Protocol References</h3>
477 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
479 DHCPv4 Protocol</h3>
482 following collection of references of what ISC DHCP terms "The
483 DHCPv4 Protocol".
484 </p>
486 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
488 Core Protocol References</h3>
490 <p><a class='info' href='#RFC2131'>RFC2131<span> (</span><span class='info'>Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a> [RFC2131] defines the protocol format
491 and procedures. ISC DHCP is not known to diverge from this document
492 in any way. There are, however, a few points on which different
493 implementations have arisen out of vagueries in the document.
494 DHCP Clients exist which, at one time, present themselves as using
495 a Client Identifier Option which is equal to the client's hardware
496 address. Later, the client transmits DHCP packets with no Client
497 Identifier Option present - essentially identifying themselves using
498 the hardware address. Some DHCP Servers have been developed which
499 identify this client as a single client. ISC has interpreted
500 RFC2131 to indicate that these clients must be treated as two
501 separate entities (and hence two, separate addresses). Client
502 behaviour (Embedded Windows products) has developed that relies on
503 the former implementation, and hence is incompatible with the
504 latter. Also, RFC2131 demands explicitly that some header fields
505 be zeroed upon certain message types. The ISC DHCP Server instead
506 copies many of these fields from the packet received from the client
507 or relay, which may not be zero. It is not known if there is a good
508 reason for this that has not been documented.
509 </p>
510 <p><a class='info' href='#RFC2132'>RFC2132<span> (</span><span class='info'>Alexander, S. and R. Droms, “DHCP Options and BOOTP Vendor Extensions,” March 1997.</span><span>)</span></a> [RFC2132] defines the initial set of
511 DHCP Options and provides a great deal of guidance on how to go about
512 formatting and processing options. The document unfortunately
513 waffles to a great extent about the NULL termination of DHCP Options,
514 and some DHCP Clients (Windows 95) have been implemented that rely
515 upon DHCP Options containing text strings to be NULL-terminated (or
516 else they crash). So, ISC DHCP detects if clients null-terminate the
517 host-name option and, if so, null terminates any text options it
518 transmits to the client. It also removes NULL termination from any
519 known text option it receives prior to any other processing.
520 </p>
522 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
524 DHCPv4 Option References</h3>
526 <p><a class='info' href='#RFC2241'>RFC2241<span> (</span><span class='info'>Provan, D., “DHCP Options for Novell Directory Services,” November 1997.</span><span>)</span></a> [RFC2241] defines options for
527 Novell Directory Services.
528 </p>
529 <p><a class='info' href='#RFC2242'>RFC2242<span> (</span><span class='info'>Droms, R. and K. Fong, “NetWare/IP Domain Name and Information,” November 1997.</span><span>)</span></a> [RFC2242] defines an encapsulated
530 option space for NWIP configuration.
531 </p>
532 <p><a class='info' href='#RFC2485'>RFC2485<span> (</span><span class='info'>Drach, S., “DHCP Option for The Open Group's User Authentication Protocol,” January 1999.</span><span>)</span></a> [RFC2485] defines the Open Group's
533 UAP option.
534 </p>
535 <p><a class='info' href='#RFC2610'>RFC2610<span> (</span><span class='info'>Perkins, C. and E. Guttman, “DHCP Options for Service Location Protocol,” June 1999.</span><span>)</span></a> [RFC2610] defines options for
536 the Service Location Protocol (SLP).
537 </p>
538 <p><a class='info' href='#RFC2937'>RFC2937<span> (</span><span class='info'>Smith, C., “The Name Service Search Option for DHCP,” September 2000.</span><span>)</span></a> [RFC2937] defines the Name Service
539 Search Option (not to be confused with the domain-search option).
540 The Name Service Search Option allows eg nsswitch.conf to be
541 reconfigured via dhcp. The ISC DHCP server implements this option,
542 and the ISC DHCP client is compatible...but does not by default
543 install this option's value. One would need to make their relevant
544 dhclient-script process this option in a way that is suitable for
545 the system.
546 </p>
547 <p><a class='info' href='#RFC3004'>RFC3004<span> (</span><span class='info'>Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A., Beser, B., and J. Privat, “The User Class Option for DHCP,” November 2000.</span><span>)</span></a> [RFC3004] defines the User-Class
548 option. Note carefully that ISC DHCP currently does not implement
549 to this reference, but has (inexplicably) selected an incompatible
550 format: a plain text string.
551 </p>
552 <p><a class='info' href='#RFC3011'>RFC3011<span> (</span><span class='info'>Waters, G., “The IPv4 Subnet Selection Option for DHCP,” November 2000.</span><span>)</span></a> [RFC3011] defines the Subnet-Selection
553 plain DHCPv4 option. Do not confuse this option with the relay agent
554 "link selection" sub-option, although their behaviour is
555 similar.
556 </p>
557 <p><a class='info' href='#RFC3396'>RFC3396<span> (</span><span class='info'>Lemon, T. and S. Cheshire, “Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4),” November 2002.</span><span>)</span></a> [RFC3396] documents both how long
558 options may be encoded in DHCPv4 packets, and also how multiple
559 instances of the same option code within a DHCPv4 packet will be
560 decoded by receivers.
561 </p>
562 <p><a class='info' href='#RFC3397'>RFC3397<span> (</span><span class='info'>Aboba, B. and S. Cheshire, “Dynamic Host Configuration Protocol (DHCP) Domain Search Option,” November 2002.</span><span>)</span></a> [RFC3397] documents the Domain-Search
563 Option, which allows the configuration of the /etc/resolv.conf
564 'search' parameter in a way that is <a class='info' href='#RFC1035'>RFC1035<span> (</span><span class='info'>Mockapetris, P., “Domain names - implementation and specification,” November 1987.</span><span>)</span></a> [RFC1035] wire format compatible (in fact, it uses the RFC1035 wire
565 format). ISC DHCP has both client and server support, and supports
566 RFC1035 name compression.
567 </p>
568 <p><a class='info' href='#RFC3679'>RFC3679<span> (</span><span class='info'>Droms, R., “Unused Dynamic Host Configuration Protocol (DHCP) Option Codes,” January 2004.</span><span>)</span></a> [RFC3679] documents a number of
569 options that were documented earlier in history, but were not
570 made use of.
571 </p>
572 <p><a class='info' href='#RFC3925'>RFC3925<span> (</span><span class='info'>Littlefield, J., “Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4),” October 2004.</span><span>)</span></a> [RFC3925] documents a pair of
573 Enterprise-ID delimited option spaces for vendors to use in order
574 to inform servers of their "vendor class" (sort of like 'uname'
575 or 'who and what am I'), and a means to deliver vendor-specific
576 and vendor-documented option codes and values.
577 </p>
578 <p><a class='info' href='#RFC3942'>RFC3942<span> (</span><span class='info'>Volz, B., “Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options,” November 2004.</span><span>)</span></a> [RFC3942] redefined the 'site local'
579 option space.
580 </p>
581 <p><a class='info' href='#RFC4280'>[RFC4280]<span> (</span><span class='info'>Chowdhury, K., Yegani, P., and L. Madour, “Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers,” November 2005.</span><span>)</span></a> defines two BCMS server options
582 for each protocol family.
583 </p>
584 <p><a class='info' href='#RFC4388'>RFC4388<span> (</span><span class='info'>Woundy, R. and K. Kinnear, “Dynamic Host Configuration Protocol (DHCP) Leasequery,” February 2006.</span><span>)</span></a> [RFC4388] defined the DHCPv4
585 LEASEQUERY message type and a number of suitable response messages,
586 for the purpose of sharing information about DHCP served addresses
587 and clients.
588 </p>
590 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
592 Relay Agent Information Option Options</h3>
594 <p><a class='info' href='#RFC3046'>RFC3046<span> (</span><span class='info'>Patrick, M., “DHCP Relay Agent Information Option,” January 2001.</span><span>)</span></a> [RFC3046] defines the Relay Agent
595 Information Option and provides a number of sub-option
596 definitions.
597 </p>
598 <p><a class='info' href='#RFC3256'>RFC3256<span> (</span><span class='info'>Jones, D. and R. Woundy, “The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option,” April 2002.</span><span>)</span></a> [RFC3256] defines the DOCSIS Device
599 Class sub-option.
600 </p>
601 <p><a class='info' href='#RFC3527'>RFC3527<span> (</span><span class='info'>Kinnear, K., Stapp, M., Johnson, R., and J. Kumarasamy, “Link Selection sub-option for the Relay Agent Information Option for DHCPv4,” April 2003.</span><span>)</span></a> [RFC3527] defines the Link Selection
602 sub-option.
603 </p>
605 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
607 Dynamic DNS Updates References</h3>
609 <p>The collection of documents that describe the standards-based
610 method to update dns names of DHCP clients starts most easily
611 with <a class='info' href='#RFC4703'>RFC4703<span> (</span><span class='info'>Stapp, M. and B. Volz, “Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients,” October 2006.</span><span>)</span></a> [RFC4703] to define the overall
612 architecture, travels through RFCs <a class='info' href='#RFC4702'>4702<span> (</span><span class='info'>Stapp, M., Volz, B., and Y. Rekhter, “The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option,” October 2006.</span><span>)</span></a> [RFC4702]
613 and <a class='info' href='#RFC4704'>4704<span> (</span><span class='info'>Volz, B., “The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option,” October 2006.</span><span>)</span></a> [RFC4704] to describe the DHCPv4 and
614 DHCPv6 FQDN options (to carry the client name), and ends up at
615 <a class='info' href='#RFC4701'>RFC4701<span> (</span><span class='info'>Stapp, M., Lemon, T., and A. Gustafsson, “A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR),” October 2006.</span><span>)</span></a> [RFC4701] which describes the DHCID
616 RR used in DNS to perform a kind of atomic locking.
617 </p>
618 <p>ISC DHCP adopted early versions of these documents, and has not
619 yet synchronized with the final standards versions.
620 </p>
622 result is that it is always set zero, and is ignored if set.
623 </p>
624 <p>For RFC4701, which is used to match client identities with names
625 in the DNS as part of name conflict resolution. Note that ISC DHCP's
626 implementation of DHCIDs vary wildly from this specification.
627 First, ISC DHCP uses a TXT record in which the contents are stored
628 in hexadecimal. Second, there is a flaw in the selection of the
629 'Identifier Type', which results in a completely different value
630 being selected than was defined in an older revision of this
631 document...also this field is one byte prior to hexadecimal
632 encoding rather than two. Third, ISC DHCP does not use a digest
633 type code. Rather, all values for such TXT records are reached
634 via an MD5 sum. In short, nothing is compatible, but the
635 principle of the TXT record is the same as the standard DHCID
636 record. However, for DHCPv6 FQDN, we do use DHCID type code '2',
637 as no other value really makes sense in our context.
638 </p>
640 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
642 Experimental: Failover References</h3>
644 <p>The Failover Protocol defines means by which two DHCP Servers
645 can share all the relevant information about leases granted to
646 DHCP clients on given networks, so that one of the two servers may
647 fail and be survived by a server that can act responsibly.
648 </p>
650 time this document was edited, and the authors no longer show any
651 interest in fielding comments or improving the document.
652 </p>
653 <p>The status of this protocol is very unsure, but ISC's
654 implementation of it has proven stable and suitable for use in
655 sizable production environments.
656 </p>
657 <p><a class='info' href='#draft-failover'>draft-ietf-dhc-failover-12.txt<span> (</span><span class='info'>Droms, R., “DHCP Failover Protocol,” March 2003.</span><span>)</span></a> [draft‑failover]
658 describes the Failover Protocol. In addition to what is described
659 in this document, ISC DHCP has elected to make some experimental
660 changes that may be revoked in a future version of ISC DHCP (if the
661 draft authors do not adopt the new behaviour). Specifically, ISC
662 DHCP's POOLREQ behaviour differs substantially from what is
663 documented in the draft, and the server also implements a form of
664 'MAC Address Affinity' which is not described in the failover
665 document. The full nature of these changes have been described on
666 the IETF DHC WG mailing list (which has archives), and also in ISC
667 DHCP's manual pages. Also note that although this document
668 references a RECOVER-WAIT state, it does not document a protocol
669 number assignment for this state. As a consequence, ISC DHCP has
670 elected to use the value 254.
671 </p>
672 <p> An optimization described in the failover protocol draft
673 is included since 4.2.0a1. It permits a DHCP server
674 operating in communications-interrupted state to 'rewind' a
675 lease to the state most recently transmitted to its peer,
676 greatly increasing a server's endurance in
677 communications-interrupted. This is supported using a new
678 'rewind state' record on the dhcpd.leases entry for each
679 lease.
681 </p>
682 <p><a class='info' href='#RFC3074'>[RFC3074]<span> (</span><span class='info'>Volz, B., Gonczi, S., Lemon, T., and R. Stevens, “DHC Load Balancing Algorithm,” February 2001.</span><span>)</span></a> describes the Load Balancing
683 Algorithm (LBA) that ISC DHCP uses in concert with the Failover
684 protocol. Note that versions 3.0.* are known to misimplement the
685 hash algorithm (it will only use the low 4 bits of every byte of
686 the hash bucket array).
687 </p>
689 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
691 DHCP Procedures</h3>
693 <p><a class='info' href='#RFC2939'>[RFC2939]<span> (</span><span class='info'>Droms, R., “Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types,” September 2000.</span><span>)</span></a> explains how to go about
694 obtaining a new DHCP Option code assignment.
695 </p>
697 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
699 DHCPv6 Protocol References</h3>
702 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
704 DHCPv6 Protocol References</h3>
706 <p>For now there is only one document that specifies the base
707 of the DHCPv6 protocol (there have been no updates yet),
708 <a class='info' href='#RFC3315'>[RFC3315]<span> (</span><span class='info'>Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, “Dynamic Host Configuration Protocol for IPv6 (DHCPv6),” July 2003.</span><span>)</span></a>.
709 </p>
711 and client support only IA_NA. While the server does support multiple
712 IA_NAs within one packet from the client, our client only supports
713 sending one. There is no relay support.
714 </p>
715 <p>DHCPv6 introduces some new and uncomfortable ideas to the common
716 software library.
717 </p>
718 <p>
719 </p>
721 <li>Options sometimes may appear multiple times. The common
722 library used to treat all appearance of multiple options as
723 specified in RFC2131 - to be concatenated. DHCPv6 options
724 may sometimes appear multiple times (such as with IA_NA or
725 IAADDR), but often must not. As of 4.2.1-P1, multiple IA_NA, IA_PD
726 or IA_TA are not supported.
727 </li>
728 <li>The same option space appears in DHCPv6 packets multiple times.
729 If the packet was got via a relay, then the client's packet is
730 stored to an option within the relay's packet...if there were two
731 relays, this recurses. At each of these steps, the root "DHCPv6
732 option space" is used. Further, a client packet may contain an
733 IA_NA, which may contain an IAADDR - but really, in an abstract
734 sense, this is again re-encapsulation of the DHCPv6 option space
735 beneath options it also contains.
736 </li>
737 </ol><p>
739 </p>
740 <p>Precisely how to correctly support the above conundrums has not
741 quite yet been settled, so support is incomplete.
742 </p>
743 <p><a class='info' href='#RFC5453'>[RFC5453]<span> (</span><span class='info'>Krishnan, S., “Reserved IPv6 Interface Identifiers,” February 2009.</span><span>)</span></a> creates a registry at IANA to reserve
744 interface identifiers and specifies a starting set. These IIDs should
745 not be used when constructing addresses to avoid possible conflicts.
746 </p>
748 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
750 DHCPv6 Options References</h3>
752 <p><a class='info' href='#RFC3319'>[RFC3319]<span> (</span><span class='info'>Schulzrinne, H. and B. Volz, “Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers,” July 2003.</span><span>)</span></a> defines the SIP server
753 options for DHCPv6.
754 </p>
755 <p><a class='info' href='#RFC3646'>[RFC3646]<span> (</span><span class='info'>Droms, R., “DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6),” December 2003.</span><span>)</span></a> documents the DHCPv6
756 name-servers and domain-search options.
757 </p>
758 <p><a class='info' href='#RFC3633'>[RFC3633]<span> (</span><span class='info'>Troan, O. and R. Droms, “IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6,” December 2003.</span><span>)</span></a> documents the Identity
759 Association Prefix Delegation for DHCPv6, which is included
760 here for protocol wire reference, but which is not supported
761 by ISC DHCP.
762 </p>
763 <p><a class='info' href='#RFC3898'>[RFC3898]<span> (</span><span class='info'>Kalusivalingam, V., “Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6),” October 2004.</span><span>)</span></a> documents four NIS options
764 for delivering NIS servers and domain information in DHCPv6.
765 </p>
766 <p><a class='info' href='#RFC4075'>[RFC4075]<span> (</span><span class='info'>Kalusivalingam, V., “Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6,” May 2005.</span><span>)</span></a> defines the DHCPv6 SNTP
767 Servers option.
768 </p>
769 <p><a class='info' href='#RFC4242'>[RFC4242]<span> (</span><span class='info'>Venaas, S., Chown, T., and B. Volz, “Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6),” November 2005.</span><span>)</span></a> defines the Information
770 Refresh Time option, which advises DHCPv6 Information-Request
771 clients to return for updated information.
772 </p>
773 <p><a class='info' href='#RFC4280'>[RFC4280]<span> (</span><span class='info'>Chowdhury, K., Yegani, P., and L. Madour, “Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers,” November 2005.</span><span>)</span></a> defines two BCMS server options
774 for each protocol family.
775 </p>
776 <p><a class='info' href='#RFC4580'>[RFC4580]<span> (</span><span class='info'>Volz, B., “Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option,” June 2006.</span><span>)</span></a> defines a DHCPv6
777 subscriber-id option, which is similar in principle to the DHCPv4
778 relay agent option of the same name.
779 </p>
780 <p><a class='info' href='#RFC4649'>[RFC4649]<span> (</span><span class='info'>Volz, B., “Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option,” August 2006.</span><span>)</span></a> defines a DHCPv6 remote-id
781 option, which is similar in principle to the DHCPv4 relay agent
782 remote-id.
783 </p>
785 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
787 References</h3>
790 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
794 <td class="author-text">Postel, J., “<a href="http://tools.ietf.org/html/rfc760">DoD standard Internet Protocol</a>,” RFC 760, January 1980 (<a href="http://www.rfc-editor.org/rfc/rfc760.txt">TXT</a>).</td></tr>
796 <td class="author-text">Postel, J., “<a href="http://tools.ietf.org/html/rfc768">User Datagram Protocol</a>,” STD 6, RFC 768, August 1980 (<a href="http://www.rfc-editor.org/rfc/rfc768.txt">TXT</a>).</td></tr>
798 <td class="author-text">Hornig, C., “<a href="http://tools.ietf.org/html/rfc894">Standard for the transmission of IP datagrams over Ethernet networks</a>,” STD 41, RFC 894, April 1984 (<a href="http://www.rfc-editor.org/rfc/rfc894.txt">TXT</a>).</td></tr>
800 <td class="author-text">Croft, B. and J. Gilmore, “<a href="http://tools.ietf.org/html/rfc951">Bootstrap Protocol</a>,” RFC 951, September 1985 (<a href="http://www.rfc-editor.org/rfc/rfc951.txt">TXT</a>).</td></tr>
802 <td class="author-text">Mockapetris, P., “<a href="http://tools.ietf.org/html/rfc1035">Domain names - implementation and specification</a>,” STD 13, RFC 1035, November 1987 (<a href="http://www.rfc-editor.org/rfc/rfc1035.txt">TXT</a>).</td></tr>
804 <td class="author-text"><a href="mailto:dkatz@merit.edu">Katz, D.</a>, “<a href="http://tools.ietf.org/html/rfc1188">Proposed Standard for the Transmission of IP Datagrams over FDDI Networks</a>,” RFC 1188, October 1990 (<a href="http://www.rfc-editor.org/rfc/rfc1188.txt">TXT</a>).</td></tr>
806 <td class="author-text"><a href="mailto:Walter.Wimer@CMU.EDU">Wimer, W.</a>, “<a href="http://tools.ietf.org/html/rfc1542">Clarifications and Extensions for the Bootstrap Protocol</a>,” RFC 1542, October 1993 (<a href="http://www.rfc-editor.org/rfc/rfc1542.txt">TXT</a>).</td></tr>
808 <td class="author-text"><a href="mailto:droms@bucknell.edu">Droms, R.</a>, “<a href="http://tools.ietf.org/html/rfc2131">Dynamic Host Configuration Protocol</a>,” RFC 2131, March 1997 (<a href="http://www.rfc-editor.org/rfc/rfc2131.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2131.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2131.xml">XML</a>).</td></tr>
810 <td class="author-text"><a href="mailto:sca@engr.sgi.com">Alexander, S.</a> and <a href="mailto:droms@bucknell.edu">R. Droms</a>, “<a href="http://tools.ietf.org/html/rfc2132">DHCP Options and BOOTP Vendor Extensions</a>,” RFC 2132, March 1997 (<a href="http://www.rfc-editor.org/rfc/rfc2132.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2132.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2132.xml">XML</a>).</td></tr>
812 <td class="author-text"><a href="mailto:donp@Novell.Com">Provan, D.</a>, “<a href="http://tools.ietf.org/html/rfc2241">DHCP Options for Novell Directory Services</a>,” RFC 2241, November 1997 (<a href="http://www.rfc-editor.org/rfc/rfc2241.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2241.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2241.xml">XML</a>).</td></tr>
814 <td class="author-text"><a href="mailto:droms@bucknell.edu">Droms, R.</a> and <a href="mailto:kfong@novell.com">K. Fong</a>, “<a href="http://tools.ietf.org/html/rfc2242">NetWare/IP Domain Name and Information</a>,” RFC 2242, November 1997 (<a href="http://www.rfc-editor.org/rfc/rfc2242.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2242.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2242.xml">XML</a>).</td></tr>
816 <td class="author-text"><a href="mailto:drach@sun.com">Drach, S.</a>, “<a href="http://tools.ietf.org/html/rfc2485">DHCP Option for The Open Group's User Authentication Protocol</a>,” RFC 2485, January 1999 (<a href="http://www.rfc-editor.org/rfc/rfc2485.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2485.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2485.xml">XML</a>).</td></tr>
818 <td class="author-text"><a href="mailto:rtroll@corp.home.net">Troll, R.</a>, “<a href="http://tools.ietf.org/html/rfc2563">DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients</a>,” RFC 2563, May 1999 (<a href="http://www.rfc-editor.org/rfc/rfc2563.txt">TXT</a>).</td></tr>
820 <td class="author-text"><a href="mailto:Charles.Perkins@Sun.Com">Perkins, C.</a> and <a href="mailto:Erik.Guttman@Sun.Com">E. Guttman</a>, “<a href="http://tools.ietf.org/html/rfc2610">DHCP Options for Service Location Protocol</a>,” RFC 2610, June 1999 (<a href="http://www.rfc-editor.org/rfc/rfc2610.txt">TXT</a>).</td></tr>
822 <td class="author-text">Fujisawa, K., “<a href="http://tools.ietf.org/html/rfc2855">DHCP for IEEE 1394</a>,” RFC 2855, June 2000 (<a href="http://www.rfc-editor.org/rfc/rfc2855.txt">TXT</a>).</td></tr>
824 <td class="author-text">Smith, C., “<a href="http://tools.ietf.org/html/rfc2937">The Name Service Search Option for DHCP</a>,” RFC 2937, September 2000 (<a href="http://www.rfc-editor.org/rfc/rfc2937.txt">TXT</a>).</td></tr>
826 <td class="author-text">Droms, R., “<a href="http://tools.ietf.org/html/rfc2939">Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types</a>,” BCP 43, RFC 2939, September 2000 (<a href="http://www.rfc-editor.org/rfc/rfc2939.txt">TXT</a>).</td></tr>
828 <td class="author-text">Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A., Beser, B., and J. Privat, “<a href="http://tools.ietf.org/html/rfc3004">The User Class Option for DHCP</a>,” RFC 3004, November 2000 (<a href="http://www.rfc-editor.org/rfc/rfc3004.txt">TXT</a>).</td></tr>
830 <td class="author-text">Waters, G., “<a href="http://tools.ietf.org/html/rfc3011">The IPv4 Subnet Selection Option for DHCP</a>,” RFC 3011, November 2000 (<a href="http://www.rfc-editor.org/rfc/rfc3011.txt">TXT</a>).</td></tr>
832 <td class="author-text">Patrick, M., “<a href="http://tools.ietf.org/html/rfc3046">DHCP Relay Agent Information Option</a>,” RFC 3046, January 2001 (<a href="http://www.rfc-editor.org/rfc/rfc3046.txt">TXT</a>).</td></tr>
834 <td class="author-text">Volz, B., Gonczi, S., Lemon, T., and R. Stevens, “<a href="http://tools.ietf.org/html/rfc3074">DHC Load Balancing Algorithm</a>,” RFC 3074, February 2001 (<a href="http://www.rfc-editor.org/rfc/rfc3074.txt">TXT</a>).</td></tr>
836 <td class="author-text">Droms, R. and W. Arbaugh, “<a href="http://tools.ietf.org/html/rfc3118">Authentication for DHCP Messages</a>,” RFC 3118, June 2001 (<a href="http://www.rfc-editor.org/rfc/rfc3118.txt">TXT</a>).</td></tr>
838 <td class="author-text">T'Joens, Y., Hublet, C., and P. De Schrijver, “<a href="http://tools.ietf.org/html/rfc3203">DHCP reconfigure extension</a>,” RFC 3203, December 2001 (<a href="http://www.rfc-editor.org/rfc/rfc3203.txt">TXT</a>).</td></tr>
840 <td class="author-text">Jones, D. and R. Woundy, “<a href="http://tools.ietf.org/html/rfc3256">The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option</a>,” RFC 3256, April 2002 (<a href="http://www.rfc-editor.org/rfc/rfc3256.txt">TXT</a>).</td></tr>
842 <td class="author-text">Schulzrinne, H., “<a href="http://tools.ietf.org/html/rfc3361">Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers</a>,” RFC 3361, August 2002 (<a href="http://www.rfc-editor.org/rfc/rfc3361.txt">TXT</a>).</td></tr>
844 <td class="author-text">Lemon, T. and S. Cheshire, “<a href="http://tools.ietf.org/html/rfc3396">Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)</a>,” RFC 3396, November 2002 (<a href="http://www.rfc-editor.org/rfc/rfc3396.txt">TXT</a>).</td></tr>
846 <td class="author-text">Aboba, B. and S. Cheshire, “<a href="http://tools.ietf.org/html/rfc3397">Dynamic Host Configuration Protocol (DHCP) Domain Search Option</a>,” RFC 3397, November 2002 (<a href="http://www.rfc-editor.org/rfc/rfc3397.txt">TXT</a>).</td></tr>
848 <td class="author-text">Lemon, T., Cheshire, S., and B. Volz, “<a href="http://tools.ietf.org/html/rfc3442">The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4</a>,” RFC 3442, December 2002 (<a href="http://www.rfc-editor.org/rfc/rfc3442.txt">TXT</a>).</td></tr>
850 <td class="author-text">Patel, B., Aboba, B., Kelly, S., and V. Gupta, “<a href="http://tools.ietf.org/html/rfc3456">Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode</a>,” RFC 3456, January 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3456.txt">TXT</a>).</td></tr>
852 <td class="author-text">Beser, B. and P. Duffy, “<a href="http://tools.ietf.org/html/rfc3495">Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration</a>,” RFC 3495, March 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3495.txt">TXT</a>).</td></tr>
854 <td class="author-text">Kinnear, K., Stapp, M., Johnson, R., and J. Kumarasamy, “<a href="http://tools.ietf.org/html/rfc3527">Link Selection sub-option for the Relay Agent Information Option for DHCPv4</a>,” RFC 3527, April 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3527.txt">TXT</a>).</td></tr>
856 <td class="author-text">Duffy, P., “<a href="http://tools.ietf.org/html/rfc3594">PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option</a>,” RFC 3594, September 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3594.txt">TXT</a>).</td></tr>
858 <td class="author-text">Luehrs, K., Woundy, R., Bevilacqua, J., and N. Davoust, “<a href="http://tools.ietf.org/html/rfc3634">Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) Option</a>,” RFC 3634, December 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3634.txt">TXT</a>).</td></tr>
860 <td class="author-text">Droms, R., “<a href="http://tools.ietf.org/html/rfc3679">Unused Dynamic Host Configuration Protocol (DHCP) Option Codes</a>,” RFC 3679, January 2004 (<a href="http://www.rfc-editor.org/rfc/rfc3679.txt">TXT</a>).</td></tr>
862 <td class="author-text">Polk, J., Schnizlein, J., and M. Linsner, “<a href="http://tools.ietf.org/html/rfc3825">Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information</a>,” RFC 3825, July 2004 (<a href="http://www.rfc-editor.org/rfc/rfc3825.txt">TXT</a>).</td></tr>
864 <td class="author-text">Littlefield, J., “<a href="http://tools.ietf.org/html/rfc3925">Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)</a>,” RFC 3925, October 2004 (<a href="http://www.rfc-editor.org/rfc/rfc3925.txt">TXT</a>).</td></tr>
866 <td class="author-text">Volz, B., “<a href="http://tools.ietf.org/html/rfc3942">Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options</a>,” RFC 3942, November 2004 (<a href="http://www.rfc-editor.org/rfc/rfc3942.txt">TXT</a>).</td></tr>
868 <td class="author-text">Johnson, R., Palaniappan, T., and M. Stapp, “<a href="http://tools.ietf.org/html/rfc3993">Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option</a>,” RFC 3993, March 2005 (<a href="http://www.rfc-editor.org/rfc/rfc3993.txt">TXT</a>).</td></tr>
870 <td class="author-text">Droms, R. and J. Schnizlein, “<a href="http://tools.ietf.org/html/rfc4014">Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option</a>,” RFC 4014, February 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4014.txt">TXT</a>).</td></tr>
872 <td class="author-text">Stapp, M. and T. Lemon, “<a href="http://tools.ietf.org/html/rfc4030">The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option</a>,” RFC 4030, March 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4030.txt">TXT</a>).</td></tr>
874 <td class="author-text">Park, S., Kim, P., and B. Volz, “<a href="http://tools.ietf.org/html/rfc4039">Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)</a>,” RFC 4039, March 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4039.txt">TXT</a>).</td></tr>
876 <td class="author-text">Monia, C., Tseng, J., and K. Gibbons, “<a href="http://tools.ietf.org/html/rfc4174">The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name Service</a>,” RFC 4174, September 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4174.txt">TXT</a>).</td></tr>
878 <td class="author-text">Stapp, M., Johnson, R., and T. Palaniappan, “<a href="http://tools.ietf.org/html/rfc4243">Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option</a>,” RFC 4243, December 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4243.txt">TXT</a>).</td></tr>
880 <td class="author-text">Lemon, T. and B. Sommerfeld, “<a href="http://tools.ietf.org/html/rfc4361">Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)</a>,” RFC 4361, February 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4361.txt">TXT</a>).</td></tr>
882 <td class="author-text">Woundy, R. and K. Kinnear, “<a href="http://tools.ietf.org/html/rfc4388">Dynamic Host Configuration Protocol (DHCP) Leasequery</a>,” RFC 4388, February 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4388.txt">TXT</a>).</td></tr>
884 <td class="author-text">Kashyap, V., “<a href="http://tools.ietf.org/html/rfc4390">Dynamic Host Configuration Protocol (DHCP) over InfiniBand</a>,” RFC 4390, April 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4390.txt">TXT</a>).</td></tr>
886 <td class="author-text">Aboba, B., Carlson, J., and S. Cheshire, “<a href="http://tools.ietf.org/html/rfc4436">Detecting Network Attachment in IPv4 (DNAv4)</a>,” RFC 4436, March 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4436.txt">TXT</a>).</td></tr>
888 <td class="author-text">Stapp, M., Lemon, T., and A. Gustafsson, “<a href="http://tools.ietf.org/html/rfc4701">A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)</a>,” RFC 4701, October 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4701.txt">TXT</a>).</td></tr>
890 <td class="author-text">Stapp, M., Volz, B., and Y. Rekhter, “<a href="http://tools.ietf.org/html/rfc4702">The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option</a>,” RFC 4702, October 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4702.txt">TXT</a>).</td></tr>
892 <td class="author-text">Stapp, M. and B. Volz, “<a href="http://tools.ietf.org/html/rfc4703">Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients</a>,” RFC 4703, October 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4703.txt">TXT</a>).</td></tr>
894 <td class="author-text">Kinnear, K., Normoyle, M., and M. Stapp, “<a href="http://tools.ietf.org/html/rfc5010">The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption</a>,” RFC 5010, September 2007 (<a href="http://www.rfc-editor.org/rfc/rfc5010.txt">TXT</a>).</td></tr>
896 <td class="author-text">Hankins, D., “<a href="http://tools.ietf.org/html/rfc5071">Dynamic Host Configuration Protocol Options Used by PXELINUX</a>,” RFC 5071, December 2007 (<a href="http://www.rfc-editor.org/rfc/rfc5071.txt">TXT</a>).</td></tr>
898 <td class="author-text">Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp, “<a href="http://tools.ietf.org/html/rfc5107">DHCP Server Identifier Override Suboption</a>,” RFC 5107, February 2008 (<a href="http://www.rfc-editor.org/rfc/rfc5107.txt">TXT</a>).</td></tr>
900 <td class="author-text">Morand, L., Yegin, A., Kumar, S., and S. Madanapalli, “<a href="http://tools.ietf.org/html/rfc5192">DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents</a>,” RFC 5192, May 2008 (<a href="http://www.rfc-editor.org/rfc/rfc5192.txt">TXT</a>).</td></tr>
902 <td class="author-text">Schulzrinne, H., Polk, J., and H. Tschofenig, “<a href="http://tools.ietf.org/html/rfc5223">Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)</a>,” RFC 5223, August 2008 (<a href="http://www.rfc-editor.org/rfc/rfc5223.txt">TXT</a>).</td></tr>
904 <td class="author-text">Johnson, R., “<a href="http://tools.ietf.org/html/rfc5859">TFTP Server Address Option for DHCPv4</a>,” RFC 5859, June 2010 (<a href="http://www.rfc-editor.org/rfc/rfc5859.txt">TXT</a>).</td></tr>
906 <td class="author-text">Townsley, W. and O. Troan, “<a href="http://tools.ietf.org/html/rfc5969">IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification</a>,” RFC 5969, August 2010 (<a href="http://www.rfc-editor.org/rfc/rfc5969.txt">TXT</a>).</td></tr>
908 <td class="author-text">Droms, R., “<a href="https://www.isc.org/sw/dhcp/drafts/draft-ietf-dhc-failover-12.txt">DHCP Failover Protocol</a>,” March 2003.</td></tr>
909 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-dhcpv4-relay-encapsulation">[I-D.ietf-dhc-dhcpv4-relay-encapsulation]</a></td>
910 <td class="author-text">Lemon, T. and H. Deng, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-relay-encapsulation-00">Relay Agent Encapsulation for DHCPv4</a>,” draft-ietf-dhc-dhcpv4-relay-encapsulation-00 (work in progress), October 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv4-relay-encapsulation-00.txt">TXT</a>).</td></tr>
911 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-dhcpv4-bulk-leasequery">[I-D.ietf-dhc-dhcpv4-bulk-leasequery]</a></td>
912 <td class="author-text">Kinnear, K., Volz, B., Russell, N., Stapp, M., Rao, D., Joshi, B., and P. Kurapati, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-bulk-leasequery-03">Bulk DHCPv4 Lease Query</a>,” draft-ietf-dhc-dhcpv4-bulk-leasequery-03 (work in progress), October 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv4-bulk-leasequery-03.txt">TXT</a>).</td></tr>
913 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-leasequery-by-remote-id">[I-D.ietf-dhc-leasequery-by-remote-id]</a></td>
914 <td class="author-text">Kurapati, P. and B. Joshi, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-leasequery-by-remote-id-09">DHCPv4 lease query by Relay Agent Remote ID</a>,” draft-ietf-dhc-leasequery-by-remote-id-09 (work in progress), December 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-leasequery-by-remote-id-09.txt">TXT</a>).</td></tr>
915 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-relay-id-suboption">[I-D.ietf-dhc-relay-id-suboption]</a></td>
916 <td class="author-text">Stapp, M., “<a href="http://tools.ietf.org/html/draft-ietf-dhc-relay-id-suboption-07">The DHCPv4 Relay Agent Identifier Suboption</a>,” draft-ietf-dhc-relay-id-suboption-07 (work in progress), July 2009 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-id-suboption-07.txt">TXT</a>).</td></tr>
917 <tr><td class="author-text" valign="top"><a name="I-D.ietf-mip6-hiopt">[I-D.ietf-mip6-hiopt]</a></td>
918 <td class="author-text">Jang, H., Yegin, A., Chowdhury, K., and J. Choi, “<a href="http://tools.ietf.org/html/draft-ietf-mip6-hiopt-17">DHCP Options for Home Information Discovery in MIPv6</a>,” draft-ietf-mip6-hiopt-17 (work in progress), May 2008 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-17.txt">TXT</a>).</td></tr>
919 </table>
922 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
926 <td class="author-text">Chowdhury, K., Yegani, P., and L. Madour, “<a href="http://tools.ietf.org/html/rfc4280">Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers</a>,” RFC 4280, November 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4280.txt">TXT</a>).</td></tr>
928 <td class="author-text">Chown, T., Venaas, S., and C. Strauf, “<a href="http://tools.ietf.org/html/rfc4477">Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues</a>,” RFC 4477, May 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4477.txt">TXT</a>).</td></tr>
930 <td class="author-text">Johnston, M. and S. Venaas, “<a href="http://tools.ietf.org/html/rfc4578">Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE)</a>,” RFC 4578, November 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4578.txt">TXT</a>).</td></tr>
932 <td class="author-text">Schulzrinne, H., “<a href="http://tools.ietf.org/html/rfc4776">Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information</a>,” RFC 4776, November 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4776.txt">TXT</a>).</td></tr>
934 <td class="author-text">Lear, E. and P. Eggert, “<a href="http://tools.ietf.org/html/rfc4833">Timezone Options for DHCP</a>,” RFC 4833, April 2007 (<a href="http://www.rfc-editor.org/rfc/rfc4833.txt">TXT</a>).</td></tr>
936 <td class="author-text">Calhoun, P., “<a href="http://tools.ietf.org/html/rfc5417">Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP Option</a>,” RFC 5417, March 2009 (<a href="http://www.rfc-editor.org/rfc/rfc5417.txt">TXT</a>).</td></tr>
938 <td class="author-text">Bajko, G. and S. Das, “<a href="http://tools.ietf.org/html/rfc5678">Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) Discovery</a>,” RFC 5678, December 2009 (<a href="http://www.rfc-editor.org/rfc/rfc5678.txt">TXT</a>).</td></tr>
940 <td class="author-text">Gayraud, R. and B. Lourdelet, “<a href="http://tools.ietf.org/html/rfc5908">Network Time Protocol (NTP) Server Option for DHCPv6</a>,” RFC 5908, June 2010 (<a href="http://www.rfc-editor.org/rfc/rfc5908.txt">TXT</a>).</td></tr>
942 <td class="author-text">Huth, T., Freimann, J., Zimmer, V., and D. Thaler, “<a href="http://tools.ietf.org/html/rfc5970">DHCPv6 Options for Network Boot</a>,” RFC 5970, September 2010 (<a href="http://www.rfc-editor.org/rfc/rfc5970.txt">TXT</a>).</td></tr>
944 <td class="author-text">Thomson, M. and J. Winterbottom, “<a href="http://tools.ietf.org/html/rfc5986">Discovering the Local Location Information Server (LIS)</a>,” RFC 5986, September 2010 (<a href="http://www.rfc-editor.org/rfc/rfc5986.txt">TXT</a>).</td></tr>
945 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-vpn-option">[I-D.ietf-dhc-vpn-option]</a></td>
946 <td class="author-text">Kinnear, K., Johnson, R., and M. Stapp, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-vpn-option-12">Virtual Subnet Selection Options for DHCPv4 and DHCPv6</a>,” draft-ietf-dhc-vpn-option-12 (work in progress), October 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-vpn-option-12.txt">TXT</a>).</td></tr>
947 </table>
950 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
954 <td class="author-text">Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, “<a href="http://tools.ietf.org/html/rfc3315">Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 3315, July 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3315.txt">TXT</a>).</td></tr>
956 <td class="author-text">Schulzrinne, H. and B. Volz, “<a href="http://tools.ietf.org/html/rfc3319">Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers</a>,” RFC 3319, July 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3319.txt">TXT</a>).</td></tr>
958 <td class="author-text">Troan, O. and R. Droms, “<a href="http://tools.ietf.org/html/rfc3633">IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6</a>,” RFC 3633, December 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3633.txt">TXT</a>).</td></tr>
960 <td class="author-text">Droms, R., “<a href="http://tools.ietf.org/html/rfc3646">DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 3646, December 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3646.txt">TXT</a>).</td></tr>
962 <td class="author-text">Droms, R., “<a href="http://tools.ietf.org/html/rfc3736">Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6</a>,” RFC 3736, April 2004 (<a href="http://www.rfc-editor.org/rfc/rfc3736.txt">TXT</a>).</td></tr>
964 <td class="author-text">Kalusivalingam, V., “<a href="http://tools.ietf.org/html/rfc3898">Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 3898, October 2004 (<a href="http://www.rfc-editor.org/rfc/rfc3898.txt">TXT</a>).</td></tr>
966 <td class="author-text">Kalusivalingam, V., “<a href="http://tools.ietf.org/html/rfc4075">Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6</a>,” RFC 4075, May 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4075.txt">TXT</a>).</td></tr>
968 <td class="author-text">Chown, T., Venaas, S., and A. Vijayabhaskar, “<a href="http://tools.ietf.org/html/rfc4076">Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 4076, May 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4076.txt">TXT</a>).</td></tr>
970 <td class="author-text">Venaas, S., Chown, T., and B. Volz, “<a href="http://tools.ietf.org/html/rfc4242">Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 4242, November 2005 (<a href="http://www.rfc-editor.org/rfc/rfc4242.txt">TXT</a>).</td></tr>
972 <td class="author-text">Volz, B., “<a href="http://tools.ietf.org/html/rfc4580">Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option</a>,” RFC 4580, June 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4580.txt">TXT</a>).</td></tr>
974 <td class="author-text">Volz, B., “<a href="http://tools.ietf.org/html/rfc4649">Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option</a>,” RFC 4649, August 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4649.txt">TXT</a>).</td></tr>
976 <td class="author-text">Volz, B., “<a href="http://tools.ietf.org/html/rfc4704">The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option</a>,” RFC 4704, October 2006 (<a href="http://www.rfc-editor.org/rfc/rfc4704.txt">TXT</a>).</td></tr>
978 <td class="author-text">Zeng, S., Volz, B., Kinnear, K., and J. Brzozowski, “<a href="http://tools.ietf.org/html/rfc4994">DHCPv6 Relay Agent Echo Request Option</a>,” RFC 4994, September 2007 (<a href="http://www.rfc-editor.org/rfc/rfc4994.txt">TXT</a>).</td></tr>
980 <td class="author-text">Brzozowski, J., Kinnear, K., Volz, B., and S. Zeng, “<a href="http://tools.ietf.org/html/rfc5007">DHCPv6 Leasequery</a>,” RFC 5007, September 2007 (<a href="http://www.rfc-editor.org/rfc/rfc5007.txt">TXT</a>).</td></tr>
982 <td class="author-text">Krishnan, S., “<a href="http://tools.ietf.org/html/rfc5453">Reserved IPv6 Interface Identifiers</a>,” RFC 5453, February 2009 (<a href="http://www.rfc-editor.org/rfc/rfc5453.txt">TXT</a>).</td></tr>
984 <td class="author-text">Stapp, M., “<a href="http://tools.ietf.org/html/rfc5460">DHCPv6 Bulk Leasequery</a>,” RFC 5460, February 2009 (<a href="http://www.rfc-editor.org/rfc/rfc5460.txt">TXT</a>).</td></tr>
985 <tr><td class="author-text" valign="top"><a name="I-D.ietf-mif-dhcpv6-route-option">[I-D.ietf-mif-dhcpv6-route-option]</a></td>
986 <td class="author-text">Dec, W., Mrugalski, T., Sun, T., and B. Sarikaya, “<a href="http://tools.ietf.org/html/draft-ietf-mif-dhcpv6-route-option-03">DHCPv6 Route Options</a>,” draft-ietf-mif-dhcpv6-route-option-03 (work in progress), September 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-mif-dhcpv6-route-option-03.txt">TXT</a>).</td></tr>
987 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-dhcpv6-ldra">[I-D.ietf-dhc-dhcpv6-ldra]</a></td>
988 <td class="author-text">Miles, D., Ooghe, S., Dec, W., Krishnan, S., and A. Kavanagh, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-ldra-03">Lightweight DHCPv6 Relay Agent</a>,” draft-ietf-dhc-dhcpv6-ldra-03 (work in progress), October 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-ldra-03.txt">TXT</a>).</td></tr>
989 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-dhcpv6-relay-supplied-options">[I-D.ietf-dhc-dhcpv6-relay-supplied-options]</a></td>
990 <td class="author-text">Lemon, T. and W. Wu, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-relay-supplied-options-09">Relay-Supplied DHCP Options</a>,” draft-ietf-dhc-dhcpv6-relay-supplied-options-09 (work in progress), September 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-relay-supplied-options-09.txt">TXT</a>).</td></tr>
991 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-pd-exclude">[I-D.ietf-dhc-pd-exclude]</a></td>
992 <td class="author-text">Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-pd-exclude-01">Prefix Exclude Option for DHCPv6-based Prefix Delegation</a>,” draft-ietf-dhc-pd-exclude-01 (work in progress), January 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-pd-exclude-01.txt">TXT</a>).</td></tr>
993 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-secure-dhcpv6">[I-D.ietf-dhc-secure-dhcpv6]</a></td>
994 <td class="author-text">Jiang, S., “<a href="http://tools.ietf.org/html/draft-ietf-dhc-secure-dhcpv6-02">Secure DHCPv6 Using CGAs</a>,” draft-ietf-dhc-secure-dhcpv6-02 (work in progress), December 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-secure-dhcpv6-02.txt">TXT</a>).</td></tr>
995 <tr><td class="author-text" valign="top"><a name="I-D.ietf-mext-nemo-pd">[I-D.ietf-mext-nemo-pd]</a></td>
996 <td class="author-text">Droms, R., Thubert, P., Dupont, F., Haddad, W., and C. Bernardos, “<a href="http://tools.ietf.org/html/draft-ietf-mext-nemo-pd-07">DHCPv6 Prefix Delegation for NEMO</a>,” draft-ietf-mext-nemo-pd-07 (work in progress), December 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-pd-07.txt">TXT</a>).</td></tr>
997 <tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-duid-uuid">[I-D.ietf-dhc-duid-uuid]</a></td>
998 <td class="author-text">Narten, T. and J. Johnson, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-duid-uuid-03">Definition of the UUID-based DHCPv6 Unique Identifier (DUID-UUID)</a>,” draft-ietf-dhc-duid-uuid-03 (work in progress), February 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-duid-uuid-03.txt">TXT</a>).</td></tr>
999 <tr><td class="author-text" valign="top"><a name="I-D.ietf-softwire-ds-lite-tunnel-option">[I-D.ietf-softwire-ds-lite-tunnel-option]</a></td>
1000 <td class="author-text">Hankins, D. and T. Mrugalski, “<a href="http://tools.ietf.org/html/draft-ietf-softwire-ds-lite-tunnel-option-10">Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual- Stack Lite</a>,” draft-ietf-softwire-ds-lite-tunnel-option-10 (work in progress), March 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-softwire-ds-lite-tunnel-option-10.txt">TXT</a>).</td></tr>
1001 <tr><td class="author-text" valign="top"><a name="I-D.ietf-mif-dns-server-selection">[I-D.ietf-mif-dns-server-selection]</a></td>
1002 <td class="author-text">Savolainen, T. and J. Kato, “<a href="http://tools.ietf.org/html/draft-ietf-mif-dns-server-selection-01">Improved DNS Server Selection for Multi-Homed Nodes</a>,” draft-ietf-mif-dns-server-selection-01 (work in progress), March 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-mif-dns-server-selection-01.txt">TXT</a>).</td></tr>
1003 <tr><td class="author-text" valign="top"><a name="I-D.ietf-geopriv-rfc3825bis">[I-D.ietf-geopriv-rfc3825bis]</a></td>
1004 <td class="author-text">Polk, J., Linsner, M., Thomson, M., and B. Aboba, “<a href="http://tools.ietf.org/html/draft-ietf-geopriv-rfc3825bis-17">Dynamic Host Configuration Protocol Options for Coordinate-based Location Configuration Information</a>,” draft-ietf-geopriv-rfc3825bis-17 (work in progress), February 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-geopriv-rfc3825bis-17.txt">TXT</a>).</td></tr>
1005 <tr><td class="author-text" valign="top"><a name="draft-addr-params">[draft-addr-params]</a></td>
1006 <td class="author-text">Mrugalski, T., “<a href="http://klub.com.pl/dhcpv6/doc/draft-mrugalski-addropts-XX-2007-04-17.txt">Address Parameters Option for DHCPv6</a>,” April 2007.</td></tr>
1007 </table>
1010 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
1017 Inc.</td></tr>
1027 Inc.</td></tr>
1035 <td class="author-text"><a href="mailto:Tomasz_Mrugalski@isc.org">Tomasz_Mrugalski@isc.org</a></td></tr>
1036 </table>
1037 </body></html>