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