1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2<html lang="en"><head><title>ISC-DHCP-REFERENCES: ISC DHCP References Collection</title> 3<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 4<meta name="description" content="ISC DHCP References Collection"> 5<meta name="keywords" content="ISC, DHCP, Reference Implementation"> 6<meta name="generator" content="xml2rfc v1.36 (http://xml.resource.org/)"> 7<style type='text/css'><!-- 8 body { 9 font-family: verdana, charcoal, helvetica, arial, sans-serif; 10 font-size: small; color: #000; background-color: #FFF; 11 margin: 2em; 12 } 13 h1, h2, h3, h4, h5, h6 { 14 font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif; 15 font-weight: bold; font-style: normal; 16 } 17 h1 { color: #900; background-color: transparent; text-align: right; } 18 h3 { color: #333; background-color: transparent; } 19 20 td.RFCbug { 21 font-size: x-small; text-decoration: none; 22 width: 30px; height: 30px; padding-top: 2px; 23 text-align: justify; vertical-align: middle; 24 background-color: #000; 25 } 26 td.RFCbug span.RFC { 27 font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif; 28 font-weight: bold; color: #666; 29 } 30 td.RFCbug span.hotText { 31 font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif; 32 font-weight: normal; text-align: center; color: #FFF; 33 } 34 35 table.TOCbug { width: 30px; height: 15px; } 36 td.TOCbug { 37 text-align: center; width: 30px; height: 15px; 38 color: #FFF; background-color: #900; 39 } 40 td.TOCbug a { 41 font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif; 42 font-weight: bold; font-size: x-small; text-decoration: none; 43 color: #FFF; background-color: transparent; 44 } 45 46 td.header { 47 font-family: arial, helvetica, sans-serif; font-size: x-small; 48 vertical-align: top; width: 33%; 49 color: #FFF; background-color: #666; 50 } 51 td.author { font-weight: bold; font-size: x-small; margin-left: 4em; } 52 td.author-text { font-size: x-small; } 53 54 /* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */ 55 a.info { 56 /* This is the key. */ 57 position: relative; 58 z-index: 24; 59 text-decoration: none; 60 } 61 a.info:hover { 62 z-index: 25; 63 color: #FFF; background-color: #900; 64 } 65 a.info span { display: none; } 66 a.info:hover span.info { 67 /* The span will display just on :hover state. */ 68 display: block; 69 position: absolute; 70 font-size: smaller; 71 top: 2em; left: -5em; width: 15em; 72 padding: 2px; border: 1px solid #333; 73 color: #900; background-color: #EEE; 74 text-align: left; 75 } 76 77 a { font-weight: bold; } 78 a:link { color: #900; background-color: transparent; } 79 a:visited { color: #633; background-color: transparent; } 80 a:active { color: #633; background-color: transparent; } 81 82 p { margin-left: 2em; margin-right: 2em; } 83 p.copyright { font-size: x-small; } 84 p.toc { font-size: small; font-weight: bold; margin-left: 3em; } 85 table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; } 86 td.toc { font-size: small; font-weight: bold; vertical-align: text-top; } 87 88 ol.text { margin-left: 2em; margin-right: 2em; } 89 ul.text { margin-left: 2em; margin-right: 2em; } 90 li { margin-left: 3em; } 91 92 /* RFC-2629 <spanx>s and <artwork>s. */ 93 em { font-style: italic; } 94 strong { font-weight: bold; } 95 dfn { font-weight: bold; font-style: normal; } 96 cite { font-weight: normal; font-style: normal; } 97 tt { color: #036; } 98 tt, pre, pre dfn, pre em, pre cite, pre span { 99 font-family: "Courier New", Courier, monospace; font-size: small; 100 } 101 pre { 102 text-align: left; padding: 4px; 103 color: #000; background-color: #CCC; 104 } 105 pre dfn { color: #900; } 106 pre em { color: #66F; background-color: #FFC; font-weight: normal; } 107 pre .key { color: #33C; font-weight: bold; } 108 pre .id { color: #900; } 109 pre .str { color: #000; background-color: #CFF; } 110 pre .val { color: #066; } 111 pre .rep { color: #909; } 112 pre .oth { color: #000; background-color: #FCF; } 113 pre .err { background-color: #FCC; } 114 115 /* RFC-2629 <texttable>s. */ 116 table.all, table.full, table.headers, table.none { 117 font-size: small; text-align: center; border-width: 2px; 118 vertical-align: top; border-collapse: collapse; 119 } 120 table.all, table.full { border-style: solid; border-color: black; } 121 table.headers, table.none { border-style: none; } 122 th { 123 font-weight: bold; border-color: black; 124 border-width: 2px 2px 3px 2px; 125 } 126 table.all th, table.full th { border-style: solid; } 127 table.headers th { border-style: none none solid none; } 128 table.none th { border-style: none; } 129 table.all td { 130 border-style: solid; border-color: #333; 131 border-width: 1px 2px; 132 } 133 table.full td, table.headers td, table.none td { border-style: none; } 134 135 hr { height: 1px; } 136 hr.insert { 137 width: 80%; border-style: none; border-width: 0; 138 color: #CCC; background-color: #CCC; 139 } 140--></style> 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"> 145<tr><td class="header">ISC-DHCP-REFERENCES</td><td class="header">D. Hankins</td></tr> 146<tr><td class="header"> </td><td class="header">T. Mrugalski</td></tr> 147<tr><td class="header"> </td><td class="header">ISC</td></tr> 148<tr><td class="header"> </td><td class="header">January 04, 2012</td></tr> 149</table></td></tr></table> 150<h1><br />ISC DHCP References Collection</h1> 151 152<h3>Abstract</h3> 153 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> 158<h3>Copyright Notice</h3> 159 160<p>Copyright (C) 2006-2022 Internet Systems 161 Consortium, Inc. ("ISC") 162</p> 163<p> This Source Code Form is subject to the terms of the Mozilla Public 164License, v. 2.0. If a copy of the MPL was not distributed with this 165file, You can obtain one at http://mozilla.org/MPL/2.0/. 166</p> 167<p>THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES 168 WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 169 MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR 170 ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 171 WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 172 ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT 173 OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 174</p><a name="toc"></a><br /><hr /> 175<h3>Table of Contents</h3> 176<p class="toc"> 177<a href="#anchor1">1.</a> 178Introduction<br /> 179<br /> 180<a href="#anchor2">2.</a> 181Definition: Reference Implementation<br /> 182<br /> 183<a href="#anchor3">3.</a> 184Low Layer References<br /> 185 <a href="#anchor4">3.1.</a> 186Ethernet Protocol References<br /> 187 <a href="#anchor5">3.2.</a> 188Token Ring Protocol References<br /> 189 <a href="#anchor6">3.3.</a> 190FDDI Protocol References<br /> 191 <a href="#anchor7">3.4.</a> 192Internet Protocol Version 4 References<br /> 193 <a href="#anchor8">3.5.</a> 194Unicast Datagram Protocol References<br /> 195<br /> 196<a href="#anchor9">4.</a> 197BOOTP Protocol References<br /> 198<br /> 199<a href="#anchor10">5.</a> 200DHCPv4 Protocol References<br /> 201 <a href="#anchor11">5.1.</a> 202DHCPv4 Protocol<br /> 203 <a href="#anchor12">5.1.1.</a> 204Core Protocol References<br /> 205 <a href="#anchor13">5.2.</a> 206DHCPv4 Option References<br /> 207 <a href="#anchor14">5.2.1.</a> 208Relay Agent Information Option Options<br /> 209 <a href="#anchor15">5.2.2.</a> 210Dynamic DNS Updates References<br /> 211 <a href="#anchor16">5.2.3.</a> 212Experimental: Failover References<br /> 213 <a href="#anchor17">5.3.</a> 214DHCP Procedures<br /> 215<br /> 216<a href="#anchor18">6.</a> 217DHCPv6 Protocol References<br /> 218 <a href="#anchor19">6.1.</a> 219DHCPv6 Protocol References<br /> 220 <a href="#anchor20">6.2.</a> 221DHCPv6 Options References<br /> 222<br /> 223<a href="#rfc.references1">7.</a> 224References<br /> 225 <a href="#rfc.references1">7.1.</a> 226Published DHCPv4 References<br /> 227 <a href="#rfc.references2">7.2.</a> 228Published Common (DHCPv4/DHCPv6) References<br /> 229 <a href="#rfc.references3">7.3.</a> 230Published DHCPv6 References<br /> 231<br /> 232<a href="#rfc.authors">§</a> 233Authors' Addresses<br /> 234</p> 235<br clear="all" /> 236 237<a name="anchor1"></a><br /><hr /> 238<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 239<a name="rfc.section.1"></a><h3>1. 240Introduction</h3> 241 242<p>As a little historical anecdote, ISC DHCP once packaged all the 243 relevant RFCs and standards documents along with the software 244 package. Until one day when a voice was heard from one of the 245 many fine institutions that build and distribute this software... 246 they took issue with the IETF's copyright on the RFC's. It 247 seems the IETF's copyrights don't allow modification of RFC's 248 (except for translation purposes). 249</p> 250<p>Our main purpose in providing the RFCs is to aid in 251 documentation, but since RFCs are now available widely from many 252 points of distribution on the Internet, there is no real need to 253 provide the documents themselves. So, this document has been 254 created in their stead, to list the various IETF RFCs one might 255 want to read, and to comment on how well (or poorly) we have 256 managed to implement them. 257</p> 258<a name="anchor2"></a><br /><hr /> 259<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 260<a name="rfc.section.2"></a><h3>2. 261Definition: Reference Implementation</h3> 262 263<p>ISC DHCP, much like its other cousins in ISC software, is 264 self-described as a 'Reference Implementation.' There has been 265 a great deal of confusion about this term. Some people seem to 266 think that this term applies to any software that once passed 267 a piece of reference material on its way to market (but may do 268 quite a lot of things that aren't described in any reference, or 269 may choose to ignore the reference it saw entirely). Other folks 270 get confused by the word 'reference' and understand that to mean 271 that there is some special status applied to the software - that 272 the software itself is the reference by which all other software 273 is measured. Something along the lines of being "The DHCP 274 Protocol's Reference Clock," it is supposed. 275</p> 276<p>The truth is actually quite a lot simpler. Reference 277 implementations are software packages which were written 278 to behave precisely as appears in reference material. They 279 are written "to match reference." 280</p> 281<p>If the software has a behaviour that manifests itself 282 externally (whether it be something as simple as the 'wire 283 format' or something higher level, such as a complicated 284 behaviour that arises from multiple message exchanges), that 285 behaviour must be found in a reference document. 286</p> 287<p>Anything else is a bug, the only question is whether the 288 bug is in reference or software (failing to implement the 289 reference). 290</p> 291<p>This means: 292</p> 293<p> 294 </p> 295<ul class="text"> 296<li>To produce new externally-visible behaviour, one must first 297 provide a reference. 298</li> 299<li>Before changing externally visible behaviour to work around 300 simple incompatibilities in any other implementation, one must 301 first provide a reference. 302</li> 303</ul><p> 304 305</p> 306<p>That is the lofty goal, at any rate. It's well understood that, 307 especially because the ISC DHCP Software package has not always been 308 held to this standard (but not entirely due to it), there are many 309 non-referenced behaviours within ISC DHCP. 310</p> 311<p>The primary goal of reference implementation is to prove the 312 reference material. If the reference material is good, then you 313 should be able to sit down and write a program that implements the 314 reference, to the word, and come to an implementation that 315 is distinguishable from others in the details, but not in the 316 facts of operating the protocol. This means that there is no 317 need for 'special knowledge' to work around arcane problems that 318 were left undocumented. No secret handshakes need to be learned 319 to be imparted with the necessary "real documentation". 320</p> 321<p>Also, by accepting only reference as the guidebook for ISC 322 DHCP's software implementation, anyone who can make an impact on 323 the color texture or form of that reference has a (somewhat 324 indirect) voice in ISC DHCP's software design. As the IETF RFC's 325 have been selected as the source of reference, that means everyone 326 on the Internet with the will to participate has a say. 327</p> 328<a name="anchor3"></a><br /><hr /> 329<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 330<a name="rfc.section.3"></a><h3>3. 331Low Layer References</h3> 332 333<p>It may surprise you to realize that ISC DHCP implements 802.1 334 'Ethernet' framing, Token Ring, and FDDI. In order to bridge the 335 gap there between these physical and DHCP layers, it must also 336 implement IP and UDP framing. 337</p> 338<p>The reason for this stems from Unix systems' handling of BSD 339 sockets (the general way one might engage in transmission of UDP 340 packets) on unconfigured interfaces, or even the handling of 341 broadcast addressing on configured interfaces. 342</p> 343<p>There are a few things that DHCP servers, relays, and clients all 344 need to do in order to speak the DHCP protocol in strict compliance 345 with <a class='info' href='#RFC2131'>[RFC2131]<span> (</span><span class='info'>Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a>. 346 347 </p> 348<ol class="text"> 349<li>Transmit a UDP packet from IP:0.0.0.0 Ethernet:Self, destined to 350 IP:255.255.255.255 LinkLayer:Broadcast on an unconfigured (no IP 351 address yet) interface. 352</li> 353<li>Receive a UDP packet from IP:remote-system LinkLayer:remote-system, 354 destined to IP:255.255.255.255 LinkLayer:Broadcast, again on an 355 unconfigured interface. 356</li> 357<li>Transmit a UDP packet from IP:Self, Ethernet:Self, destined to 358 IP:remote-system LinkLayer:remote-system, without transmitting a 359 single ARP. 360</li> 361<li>And of course the simple case, a regular IP unicast that is 362 routed via the usual means (so it may be direct to a local system, 363 with ARP providing the glue, or it may be to a remote system via 364 one or more routers as normal). In this case, the interfaces are 365 always configured. 366</li> 367</ol> 368 369<p>The above isn't as simple as it sounds on a regular BSD socket. 370 Many unix implementations will transmit broadcasts not to 371 255.255.255.255, but to x.y.z.255 (where x.y.z is the system's local 372 subnet). Such packets are not received by several known DHCP client 373 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> 374 very explicitly demands that these packets' IP destination 375 addresses be set to 255.255.255.255. 376</p> 377<p>Receiving packets sent to 255.255.255.255 isn't a problem on most 378 modern unixes...so long as the interface is configured. When there 379 is no IPv4 address on the interface, things become much more murky. 380</p> 381<p>So, for this convoluted and unfortunate state of affairs in the 382 unix systems of the day ISC DHCP was manufactured, in order to do 383 what it needs not only to implement the reference but to interoperate 384 with other implementations, the software must create some form of 385 raw socket to operate on. 386</p> 387<p>What it actually does is create, for each interface detected on 388 the system, a Berkeley Packet Filter socket (or equivalent), and 389 program it with a filter that brings in only DHCP packets. A 390 "fallback" UDP Berkeley socket is generally also created, a single 391 one no matter how many interfaces. Should the software need to 392 transmit a contrived packet to the local network the packet is 393 formed piece by piece and transmitted via the BPF socket. Hence 394 the need to implement many forms of Link Layer framing and above. 395 The software gets away with not having to implement IP routing 396 tables as well by simply utilizing the aforementioned 'fallback' 397 UDP socket when unicasting between two configured systems is 398 needed. 399</p> 400<p>Modern unixes have opened up some facilities that diminish how 401 much of this sort of nefarious kludgery is necessary, but have not 402 found the state of affairs absolutely resolved. In particular, 403 one might now unicast without ARP by inserting an entry into the 404 ARP cache prior to transmitting. Unconfigured interfaces remain 405 the sticking point, however...on virtually no modern unixes is 406 it possible to receive broadcast packets unless a local IPv4 407 address has been configured, unless it is done with raw sockets. 408</p> 409<a name="anchor4"></a><br /><hr /> 410<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 411<a name="rfc.section.3.1"></a><h3>3.1. 412Ethernet Protocol References</h3> 413 414<p>ISC DHCP Implements Ethernet Version 2 ("DIX"), which is a variant 415 of IEEE 802.2. No good reference of this framing is known to exist 416 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> 417 see the section titled "Packet format"), and 418 the following URL is also thought to be useful. 419</p> 420<p><a href='http://en.wikipedia.org/wiki/DIX_Ethernet'>http://en.wikipedia.org/wiki/DIX_Ethernet</a> 421</p> 422<a name="anchor5"></a><br /><hr /> 423<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 424<a name="rfc.section.3.2"></a><h3>3.2. 425Token Ring Protocol References</h3> 426 427<p>IEEE 802.5 defines the Token Ring framing format used by ISC 428 DHCP. 429</p> 430<a name="anchor6"></a><br /><hr /> 431<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 432<a name="rfc.section.3.3"></a><h3>3.3. 433FDDI Protocol References</h3> 434 435<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 436 reference ISC DHCP has used to form FDDI packets. 437</p> 438<a name="anchor7"></a><br /><hr /> 439<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 440<a name="rfc.section.3.4"></a><h3>3.4. 441Internet Protocol Version 4 References</h3> 442 443<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 444 bare IPv4 protocol which ISC DHCP implements. 445</p> 446<a name="anchor8"></a><br /><hr /> 447<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 448<a name="rfc.section.3.5"></a><h3>3.5. 449Unicast Datagram Protocol References</h3> 450 451<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 452 Protocol that ultimately carries the DHCP or BOOTP protocol. The 453 destination DHCP server port is 67, the client port is 68. Source 454 ports are irrelevant. 455</p> 456<a name="anchor9"></a><br /><hr /> 457<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 458<a name="rfc.section.4"></a><h3>4. 459BOOTP Protocol References</h3> 460 461<p>The DHCP Protocol is strange among protocols in that it is 462 grafted over the top of another protocol - BOOTP (but we don't 463 call it "DHCP over BOOTP" like we do, say "TCP over IP"). BOOTP 464 and DHCP share UDP packet formats - DHCP is merely a conventional 465 use of both BOOTP header fields and the trailing 'options' space. 466</p> 467<p>The ISC DHCP server supports BOOTP clients conforming to 468 <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]. 469</p> 470<a name="anchor10"></a><br /><hr /> 471<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 472<a name="rfc.section.5"></a><h3>5. 473DHCPv4 Protocol References</h3> 474 475<a name="anchor11"></a><br /><hr /> 476<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 477<a name="rfc.section.5.1"></a><h3>5.1. 478DHCPv4 Protocol</h3> 479 480<p>"The DHCP[v4] Protocol" is not defined in a single document. The 481 following collection of references of what ISC DHCP terms "The 482 DHCPv4 Protocol". 483</p> 484<a name="anchor12"></a><br /><hr /> 485<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 486<a name="rfc.section.5.1.1"></a><h3>5.1.1. 487Core Protocol References</h3> 488 489<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 490 and procedures. ISC DHCP is not known to diverge from this document 491 in any way. There are, however, a few points on which different 492 implementations have arisen out of vagueries in the document. 493 DHCP Clients exist which, at one time, present themselves as using 494 a Client Identifier Option which is equal to the client's hardware 495 address. Later, the client transmits DHCP packets with no Client 496 Identifier Option present - essentially identifying themselves using 497 the hardware address. Some DHCP Servers have been developed which 498 identify this client as a single client. ISC has interpreted 499 RFC2131 to indicate that these clients must be treated as two 500 separate entities (and hence two, separate addresses). Client 501 behaviour (Embedded Windows products) has developed that relies on 502 the former implementation, and hence is incompatible with the 503 latter. Also, RFC2131 demands explicitly that some header fields 504 be zeroed upon certain message types. The ISC DHCP Server instead 505 copies many of these fields from the packet received from the client 506 or relay, which may not be zero. It is not known if there is a good 507 reason for this that has not been documented. 508</p> 509<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 510 DHCP Options and provides a great deal of guidance on how to go about 511 formatting and processing options. The document unfortunately 512 waffles to a great extent about the NULL termination of DHCP Options, 513 and some DHCP Clients (Windows 95) have been implemented that rely 514 upon DHCP Options containing text strings to be NULL-terminated (or 515 else they crash). So, ISC DHCP detects if clients null-terminate the 516 host-name option and, if so, null terminates any text options it 517 transmits to the client. It also removes NULL termination from any 518 known text option it receives prior to any other processing. 519</p> 520<a name="anchor13"></a><br /><hr /> 521<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 522<a name="rfc.section.5.2"></a><h3>5.2. 523DHCPv4 Option References</h3> 524 525<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 526 Novell Directory Services. 527</p> 528<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 529 option space for NWIP configuration. 530</p> 531<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 532 UAP option. 533</p> 534<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 535 the Service Location Protocol (SLP). 536</p> 537<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 538 Search Option (not to be confused with the domain-search option). 539 The Name Service Search Option allows eg nsswitch.conf to be 540 reconfigured via dhcp. The ISC DHCP server implements this option, 541 and the ISC DHCP client is compatible...but does not by default 542 install this option's value. One would need to make their relevant 543 dhclient-script process this option in a way that is suitable for 544 the system. 545</p> 546<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 547 option. Note carefully that ISC DHCP currently does not implement 548 to this reference, but has (inexplicably) selected an incompatible 549 format: a plain text string. 550</p> 551<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 552 plain DHCPv4 option. Do not confuse this option with the relay agent 553 "link selection" sub-option, although their behaviour is 554 similar. 555</p> 556<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 557 options may be encoded in DHCPv4 packets, and also how multiple 558 instances of the same option code within a DHCPv4 packet will be 559 decoded by receivers. 560</p> 561<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 562 Option, which allows the configuration of the /etc/resolv.conf 563 '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 564 format). ISC DHCP has both client and server support, and supports 565 RFC1035 name compression. 566</p> 567<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 568 options that were documented earlier in history, but were not 569 made use of. 570</p> 571<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 572 Enterprise-ID delimited option spaces for vendors to use in order 573 to inform servers of their "vendor class" (sort of like 'uname' 574 or 'who and what am I'), and a means to deliver vendor-specific 575 and vendor-documented option codes and values. 576</p> 577<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' 578 option space. 579</p> 580<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 581 for each protocol family. 582</p> 583<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 584 LEASEQUERY message type and a number of suitable response messages, 585 for the purpose of sharing information about DHCP served addresses 586 and clients. 587</p> 588<a name="anchor14"></a><br /><hr /> 589<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 590<a name="rfc.section.5.2.1"></a><h3>5.2.1. 591Relay Agent Information Option Options</h3> 592 593<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 594 Information Option and provides a number of sub-option 595 definitions. 596</p> 597<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 598 Class sub-option. 599</p> 600<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 601 sub-option. 602</p> 603<a name="anchor15"></a><br /><hr /> 604<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 605<a name="rfc.section.5.2.2"></a><h3>5.2.2. 606Dynamic DNS Updates References</h3> 607 608<p>The collection of documents that describe the standards-based 609 method to update dns names of DHCP clients starts most easily 610 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 611 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] 612 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 613 DHCPv6 FQDN options (to carry the client name), and ends up at 614 <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 615 RR used in DNS to perform a kind of atomic locking. 616</p> 617<p>ISC DHCP adopted early versions of these documents, and has not 618 yet synchronized with the final standards versions. 619</p> 620<p>For RFCs 4702 and 4704, the 'N' bit is not yet supported. The 621 result is that it is always set zero, and is ignored if set. 622</p> 623<p>For RFC4701, which is used to match client identities with names 624 in the DNS as part of name conflict resolution. Note that ISC DHCP's 625 implementation of DHCIDs vary wildly from this specification. 626 First, ISC DHCP uses a TXT record in which the contents are stored 627 in hexadecimal. Second, there is a flaw in the selection of the 628 'Identifier Type', which results in a completely different value 629 being selected than was defined in an older revision of this 630 document...also this field is one byte prior to hexadecimal 631 encoding rather than two. Third, ISC DHCP does not use a digest 632 type code. Rather, all values for such TXT records are reached 633 via an MD5 sum. In short, nothing is compatible, but the 634 principle of the TXT record is the same as the standard DHCID 635 record. However, for DHCPv6 FQDN, we do use DHCID type code '2', 636 as no other value really makes sense in our context. 637</p> 638<a name="anchor16"></a><br /><hr /> 639<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 640<a name="rfc.section.5.2.3"></a><h3>5.2.3. 641Experimental: Failover References</h3> 642 643<p>The Failover Protocol defines means by which two DHCP Servers 644 can share all the relevant information about leases granted to 645 DHCP clients on given networks, so that one of the two servers may 646 fail and be survived by a server that can act responsibly. 647</p> 648<p>Unfortunately it has been quite some years (2003) since the last 649 time this document was edited, and the authors no longer show any 650 interest in fielding comments or improving the document. 651</p> 652<p>The status of this protocol is very unsure, but ISC's 653 implementation of it has proven stable and suitable for use in 654 sizable production environments. 655</p> 656<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] 657 describes the Failover Protocol. In addition to what is described 658 in this document, ISC DHCP has elected to make some experimental 659 changes that may be revoked in a future version of ISC DHCP (if the 660 draft authors do not adopt the new behaviour). Specifically, ISC 661 DHCP's POOLREQ behaviour differs substantially from what is 662 documented in the draft, and the server also implements a form of 663 'MAC Address Affinity' which is not described in the failover 664 document. The full nature of these changes have been described on 665 the IETF DHC WG mailing list (which has archives), and also in ISC 666 DHCP's manual pages. Also note that although this document 667 references a RECOVER-WAIT state, it does not document a protocol 668 number assignment for this state. As a consequence, ISC DHCP has 669 elected to use the value 254. 670</p> 671<p> An optimization described in the failover protocol draft 672 is included since 4.2.0a1. It permits a DHCP server 673 operating in communications-interrupted state to 'rewind' a 674 lease to the state most recently transmitted to its peer, 675 greatly increasing a server's endurance in 676 communications-interrupted. This is supported using a new 677 'rewind state' record on the dhcpd.leases entry for each 678 lease. 679 680</p> 681<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 682 Algorithm (LBA) that ISC DHCP uses in concert with the Failover 683 protocol. Note that versions 3.0.* are known to misimplement the 684 hash algorithm (it will only use the low 4 bits of every byte of 685 the hash bucket array). 686</p> 687<a name="anchor17"></a><br /><hr /> 688<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 689<a name="rfc.section.5.3"></a><h3>5.3. 690DHCP Procedures</h3> 691 692<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 693 obtaining a new DHCP Option code assignment. 694</p> 695<a name="anchor18"></a><br /><hr /> 696<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 697<a name="rfc.section.6"></a><h3>6. 698DHCPv6 Protocol References</h3> 699 700<a name="anchor19"></a><br /><hr /> 701<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 702<a name="rfc.section.6.1"></a><h3>6.1. 703DHCPv6 Protocol References</h3> 704 705<p>For now there is only one document that specifies the base 706 of the DHCPv6 protocol (there have been no updates yet), 707 <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>. 708</p> 709<p>Support for DHCPv6 was first added in version 4.0.0. The server 710 and client support only IA_NA. While the server does support multiple 711 IA_NAs within one packet from the client, our client only supports 712 sending one. There is no relay support. 713</p> 714<p>DHCPv6 introduces some new and uncomfortable ideas to the common 715 software library. 716</p> 717<p> 718 </p> 719<ol class="text"> 720<li>Options sometimes may appear multiple times. The common 721 library used to treat all appearance of multiple options as 722 specified in RFC2131 - to be concatenated. DHCPv6 options 723 may sometimes appear multiple times (such as with IA_NA or 724 IAADDR), but often must not. As of 4.2.1-P1, multiple IA_NA, IA_PD 725 or IA_TA are not supported. 726</li> 727<li>The same option space appears in DHCPv6 packets multiple times. 728 If the packet was got via a relay, then the client's packet is 729 stored to an option within the relay's packet...if there were two 730 relays, this recurses. At each of these steps, the root "DHCPv6 731 option space" is used. Further, a client packet may contain an 732 IA_NA, which may contain an IAADDR - but really, in an abstract 733 sense, this is again re-encapsulation of the DHCPv6 option space 734 beneath options it also contains. 735</li> 736</ol><p> 737 738</p> 739<p>Precisely how to correctly support the above conundrums has not 740 quite yet been settled, so support is incomplete. 741</p> 742<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 743 interface identifiers and specifies a starting set. These IIDs should 744 not be used when constructing addresses to avoid possible conflicts. 745</p> 746<a name="anchor20"></a><br /><hr /> 747<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 748<a name="rfc.section.6.2"></a><h3>6.2. 749DHCPv6 Options References</h3> 750 751<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 752 options for DHCPv6. 753</p> 754<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 755 name-servers and domain-search options. 756</p> 757<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 758 Association Prefix Delegation for DHCPv6, which is included 759 here for protocol wire reference, but which is not supported 760 by ISC DHCP. 761</p> 762<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 763 for delivering NIS servers and domain information in DHCPv6. 764</p> 765<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 766 Servers option. 767</p> 768<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 769 Refresh Time option, which advises DHCPv6 Information-Request 770 clients to return for updated information. 771</p> 772<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 773 for each protocol family. 774</p> 775<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 776 subscriber-id option, which is similar in principle to the DHCPv4 777 relay agent option of the same name. 778</p> 779<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 780 option, which is similar in principle to the DHCPv4 relay agent 781 remote-id. 782</p> 783<a name="rfc.references"></a><br /><hr /> 784<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 785<a name="rfc.section.7"></a><h3>7. 786References</h3> 787 788<a name="rfc.references1"></a><br /><hr /> 789<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 790<h3>7.1. Published DHCPv4 References</h3> 791<table width="99%" border="0"> 792<tr><td class="author-text" valign="top"><a name="RFC0760">[RFC0760]</a></td> 793<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> 794<tr><td class="author-text" valign="top"><a name="RFC0768">[RFC0768]</a></td> 795<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> 796<tr><td class="author-text" valign="top"><a name="RFC0894">[RFC0894]</a></td> 797<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> 798<tr><td class="author-text" valign="top"><a name="RFC0951">[RFC0951]</a></td> 799<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> 800<tr><td class="author-text" valign="top"><a name="RFC1035">[RFC1035]</a></td> 801<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> 802<tr><td class="author-text" valign="top"><a name="RFC1188">[RFC1188]</a></td> 803<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> 804<tr><td class="author-text" valign="top"><a name="RFC1542">[RFC1542]</a></td> 805<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> 806<tr><td class="author-text" valign="top"><a name="RFC2131">[RFC2131]</a></td> 807<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> 808<tr><td class="author-text" valign="top"><a name="RFC2132">[RFC2132]</a></td> 809<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> 810<tr><td class="author-text" valign="top"><a name="RFC2241">[RFC2241]</a></td> 811<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> 812<tr><td class="author-text" valign="top"><a name="RFC2242">[RFC2242]</a></td> 813<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> 814<tr><td class="author-text" valign="top"><a name="RFC2485">[RFC2485]</a></td> 815<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> 816<tr><td class="author-text" valign="top"><a name="RFC2563">[RFC2563]</a></td> 817<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> 818<tr><td class="author-text" valign="top"><a name="RFC2610">[RFC2610]</a></td> 819<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> 820<tr><td class="author-text" valign="top"><a name="RFC2855">[RFC2855]</a></td> 821<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> 822<tr><td class="author-text" valign="top"><a name="RFC2937">[RFC2937]</a></td> 823<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> 824<tr><td class="author-text" valign="top"><a name="RFC2939">[RFC2939]</a></td> 825<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> 826<tr><td class="author-text" valign="top"><a name="RFC3004">[RFC3004]</a></td> 827<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> 828<tr><td class="author-text" valign="top"><a name="RFC3011">[RFC3011]</a></td> 829<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> 830<tr><td class="author-text" valign="top"><a name="RFC3046">[RFC3046]</a></td> 831<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> 832<tr><td class="author-text" valign="top"><a name="RFC3074">[RFC3074]</a></td> 833<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> 834<tr><td class="author-text" valign="top"><a name="RFC3118">[RFC3118]</a></td> 835<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> 836<tr><td class="author-text" valign="top"><a name="RFC3203">[RFC3203]</a></td> 837<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> 838<tr><td class="author-text" valign="top"><a name="RFC3256">[RFC3256]</a></td> 839<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> 840<tr><td class="author-text" valign="top"><a name="RFC3361">[RFC3361]</a></td> 841<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> 842<tr><td class="author-text" valign="top"><a name="RFC3396">[RFC3396]</a></td> 843<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> 844<tr><td class="author-text" valign="top"><a name="RFC3397">[RFC3397]</a></td> 845<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> 846<tr><td class="author-text" valign="top"><a name="RFC3442">[RFC3442]</a></td> 847<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> 848<tr><td class="author-text" valign="top"><a name="RFC3456">[RFC3456]</a></td> 849<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> 850<tr><td class="author-text" valign="top"><a name="RFC3495">[RFC3495]</a></td> 851<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> 852<tr><td class="author-text" valign="top"><a name="RFC3527">[RFC3527]</a></td> 853<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> 854<tr><td class="author-text" valign="top"><a name="RFC3594">[RFC3594]</a></td> 855<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> 856<tr><td class="author-text" valign="top"><a name="RFC3634">[RFC3634]</a></td> 857<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> 858<tr><td class="author-text" valign="top"><a name="RFC3679">[RFC3679]</a></td> 859<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> 860<tr><td class="author-text" valign="top"><a name="RFC3825">[RFC3825]</a></td> 861<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> 862<tr><td class="author-text" valign="top"><a name="RFC3925">[RFC3925]</a></td> 863<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> 864<tr><td class="author-text" valign="top"><a name="RFC3942">[RFC3942]</a></td> 865<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> 866<tr><td class="author-text" valign="top"><a name="RFC3993">[RFC3993]</a></td> 867<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> 868<tr><td class="author-text" valign="top"><a name="RFC4014">[RFC4014]</a></td> 869<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> 870<tr><td class="author-text" valign="top"><a name="RFC4030">[RFC4030]</a></td> 871<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> 872<tr><td class="author-text" valign="top"><a name="RFC4039">[RFC4039]</a></td> 873<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> 874<tr><td class="author-text" valign="top"><a name="RFC4174">[RFC4174]</a></td> 875<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> 876<tr><td class="author-text" valign="top"><a name="RFC4243">[RFC4243]</a></td> 877<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> 878<tr><td class="author-text" valign="top"><a name="RFC4361">[RFC4361]</a></td> 879<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> 880<tr><td class="author-text" valign="top"><a name="RFC4388">[RFC4388]</a></td> 881<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> 882<tr><td class="author-text" valign="top"><a name="RFC4390">[RFC4390]</a></td> 883<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> 884<tr><td class="author-text" valign="top"><a name="RFC4436">[RFC4436]</a></td> 885<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> 886<tr><td class="author-text" valign="top"><a name="RFC4701">[RFC4701]</a></td> 887<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> 888<tr><td class="author-text" valign="top"><a name="RFC4702">[RFC4702]</a></td> 889<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> 890<tr><td class="author-text" valign="top"><a name="RFC4703">[RFC4703]</a></td> 891<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> 892<tr><td class="author-text" valign="top"><a name="RFC5010">[RFC5010]</a></td> 893<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> 894<tr><td class="author-text" valign="top"><a name="RFC5071">[RFC5071]</a></td> 895<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> 896<tr><td class="author-text" valign="top"><a name="RFC5107">[RFC5107]</a></td> 897<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> 898<tr><td class="author-text" valign="top"><a name="RFC5192">[RFC5192]</a></td> 899<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> 900<tr><td class="author-text" valign="top"><a name="RFC5223">[RFC5223]</a></td> 901<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> 902<tr><td class="author-text" valign="top"><a name="RFC5859">[RFC5859]</a></td> 903<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> 904<tr><td class="author-text" valign="top"><a name="RFC5969">[RFC5969]</a></td> 905<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> 906<tr><td class="author-text" valign="top"><a name="draft-failover">[draft-failover]</a></td> 907<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> 908<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> 909<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> 910<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> 911<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> 912<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> 913<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> 914<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> 915<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> 916<tr><td class="author-text" valign="top"><a name="I-D.ietf-mip6-hiopt">[I-D.ietf-mip6-hiopt]</a></td> 917<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> 918</table> 919 920<a name="rfc.references2"></a><br /><hr /> 921<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 922<h3>7.2. Published Common (DHCPv4/DHCPv6) References</h3> 923<table width="99%" border="0"> 924<tr><td class="author-text" valign="top"><a name="RFC4280">[RFC4280]</a></td> 925<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> 926<tr><td class="author-text" valign="top"><a name="RFC4477">[RFC4477]</a></td> 927<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> 928<tr><td class="author-text" valign="top"><a name="RFC4578">[RFC4578]</a></td> 929<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> 930<tr><td class="author-text" valign="top"><a name="RFC4776">[RFC4776]</a></td> 931<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> 932<tr><td class="author-text" valign="top"><a name="RFC4833">[RFC4833]</a></td> 933<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> 934<tr><td class="author-text" valign="top"><a name="RFC5417">[RFC5417]</a></td> 935<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> 936<tr><td class="author-text" valign="top"><a name="RFC5678">[RFC5678]</a></td> 937<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> 938<tr><td class="author-text" valign="top"><a name="RFC5908">[RFC5908]</a></td> 939<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> 940<tr><td class="author-text" valign="top"><a name="RFC5970">[RFC5970]</a></td> 941<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> 942<tr><td class="author-text" valign="top"><a name="RFC5986">[RFC5986]</a></td> 943<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> 944<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-vpn-option">[I-D.ietf-dhc-vpn-option]</a></td> 945<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> 946</table> 947 948<a name="rfc.references3"></a><br /><hr /> 949<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 950<h3>7.3. Published DHCPv6 References</h3> 951<table width="99%" border="0"> 952<tr><td class="author-text" valign="top"><a name="RFC3315">[RFC3315]</a></td> 953<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> 954<tr><td class="author-text" valign="top"><a name="RFC3319">[RFC3319]</a></td> 955<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> 956<tr><td class="author-text" valign="top"><a name="RFC3633">[RFC3633]</a></td> 957<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> 958<tr><td class="author-text" valign="top"><a name="RFC3646">[RFC3646]</a></td> 959<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> 960<tr><td class="author-text" valign="top"><a name="RFC3736">[RFC3736]</a></td> 961<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> 962<tr><td class="author-text" valign="top"><a name="RFC3898">[RFC3898]</a></td> 963<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> 964<tr><td class="author-text" valign="top"><a name="RFC4075">[RFC4075]</a></td> 965<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> 966<tr><td class="author-text" valign="top"><a name="RFC4076">[RFC4076]</a></td> 967<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> 968<tr><td class="author-text" valign="top"><a name="RFC4242">[RFC4242]</a></td> 969<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> 970<tr><td class="author-text" valign="top"><a name="RFC4580">[RFC4580]</a></td> 971<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> 972<tr><td class="author-text" valign="top"><a name="RFC4649">[RFC4649]</a></td> 973<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> 974<tr><td class="author-text" valign="top"><a name="RFC4704">[RFC4704]</a></td> 975<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> 976<tr><td class="author-text" valign="top"><a name="RFC4994">[RFC4994]</a></td> 977<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> 978<tr><td class="author-text" valign="top"><a name="RFC5007">[RFC5007]</a></td> 979<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> 980<tr><td class="author-text" valign="top"><a name="RFC5453">[RFC5453]</a></td> 981<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> 982<tr><td class="author-text" valign="top"><a name="RFC5460">[RFC5460]</a></td> 983<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> 984<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> 985<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> 986<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-dhcpv6-ldra">[I-D.ietf-dhc-dhcpv6-ldra]</a></td> 987<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> 988<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> 989<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> 990<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-pd-exclude">[I-D.ietf-dhc-pd-exclude]</a></td> 991<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> 992<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-secure-dhcpv6">[I-D.ietf-dhc-secure-dhcpv6]</a></td> 993<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> 994<tr><td class="author-text" valign="top"><a name="I-D.ietf-mext-nemo-pd">[I-D.ietf-mext-nemo-pd]</a></td> 995<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> 996<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-duid-uuid">[I-D.ietf-dhc-duid-uuid]</a></td> 997<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> 998<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> 999<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> 1000<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> 1001<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> 1002<tr><td class="author-text" valign="top"><a name="I-D.ietf-geopriv-rfc3825bis">[I-D.ietf-geopriv-rfc3825bis]</a></td> 1003<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> 1004<tr><td class="author-text" valign="top"><a name="draft-addr-params">[draft-addr-params]</a></td> 1005<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> 1006</table> 1007 1008<a name="rfc.authors"></a><br /><hr /> 1009<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 1010<h3>Authors' Addresses</h3> 1011<table width="99%" border="0" cellpadding="0" cellspacing="0"> 1012<tr><td class="author-text"> </td> 1013<td class="author-text">David W. Hankins</td></tr> 1014<tr><td class="author-text"> </td> 1015<td class="author-text">Internet Systems Consortium, 1016 Inc.</td></tr> 1017<tr><td class="author-text"> </td> 1018<td class="author-text">PO Box 360</td></tr> 1019<tr><td class="author-text"> </td> 1020<td class="author-text">Newmarket, NH 03857 USA</td></tr> 1021<tr cellpadding="3"><td> </td><td> </td></tr> 1022<tr><td class="author-text"> </td> 1023<td class="author-text">Tomasz Mrugalski</td></tr> 1024<tr><td class="author-text"> </td> 1025<td class="author-text">Internet Systems Consortium, 1026 Inc.</td></tr> 1027<tr><td class="author-text"> </td> 1028<td class="author-text">PO Box 360</td></tr> 1029<tr><td class="author-text"> </td> 1030<td class="author-text">Newmarket, NH 03857 USA</td></tr> 1031<tr><td class="author" align="right">Phone: </td> 1032<td class="author-text">+1 650 423 1345</td></tr> 1033<tr><td class="author" align="right">Email: </td> 1034<td class="author-text"><a href="mailto:Tomasz_Mrugalski@isc.org">Tomasz_Mrugalski@isc.org</a></td></tr> 1035</table> 1036</body></html> 1037