mirror of
https://gitlab.isc.org/isc-projects/dhcp
synced 2025-08-31 14:25:41 +00:00
- Documentation cleanup
[ISC-Bugs #23326] Updated References document, several man page updates
This commit is contained in:
Tomek Mrugalski
18
README
18
README
@@ -46,7 +46,8 @@ client and relay subdirectories. The README file (this file) includes
|
||||
late-breaking operational and system-specific information that you
|
||||
should read even if you don't want to read the manual pages, and that
|
||||
you should *certainly* read if you run into trouble. Internet
|
||||
standards relating to the DHCP protocol are stored in the doc
|
||||
standards relating to the DHCP protocol are listed in the References
|
||||
document that is available in html, txt and xml formats in doc/
|
||||
subdirectory. You will have the best luck reading the manual pages if
|
||||
you build this software and then install it, although you can read
|
||||
them directly out of the distribution if you need to.
|
||||
@@ -112,10 +113,9 @@ If you wish to run the DHCP Distribution on Linux, please see the
|
||||
Linux-specific notes later in this document. If you wish to run on an
|
||||
SCO release, please see the SCO-specific notes later in this document.
|
||||
You particularly need to read these notes if you intend to support
|
||||
Windows 95 clients. If you are running a version of FreeBSD prior to
|
||||
2.2, please read the note on FreeBSD. If you are running HP-UX or
|
||||
Ultrix, please read the notes for those operating systems below. If
|
||||
you are running NeXTSTEP, please see the notes on NeXTSTEP below.
|
||||
Windows 95 clients. If you are running HP-UX or Ultrix, please read the
|
||||
notes for those operating systems below. If you are running NeXTSTEP,
|
||||
please see the notes on NeXTSTEP below.
|
||||
|
||||
If you start dhcpd and get a message, "no free bpf", that means you
|
||||
need to configure the Berkeley Packet Filter into your operating
|
||||
@@ -564,10 +564,10 @@ has been resolved, then we're still working on it.
|
||||
|
||||
PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES! Fetch the latest
|
||||
release and see if the bug is still in that version of the software,
|
||||
and if it's not, _then_ report it. ISC release versions always have
|
||||
three numbers, for example: 1.2.3. The 'major release' is 1 here,
|
||||
the 'minor release' is 2, and the 'maintenance release' is 3. ISC
|
||||
will accept bug reports against the most recent two major.minor
|
||||
and if it is still present, _then_ report it. ISC release versions
|
||||
always have three numbers, for example: 1.2.3. The 'major release' is
|
||||
1 here, the 'minor release' is 2, and the 'maintenance release' is 3.
|
||||
ISC will accept bug reports against the most recent two major.minor
|
||||
releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior.
|
||||
|
||||
PLEASE take a moment to determine where the ISC DHCP distribution
|
||||
|
||||
3
RELNOTES
3
RELNOTES
@@ -156,6 +156,9 @@ work on other platforms. Please report any problems and suggested fixes to
|
||||
case of the default router information being changed without the address
|
||||
being changed.
|
||||
|
||||
- Documentation cleanup
|
||||
[ISC-Bugs #23326] Updated References document, several man page updates
|
||||
|
||||
Changes since 4.2.0
|
||||
|
||||
- Documentation cleanup covering multiple tickets
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
.\" $Id: dhcp-options.5,v 1.49 2010/07/20 21:09:14 dhankins Exp $
|
||||
.\" $Id: dhcp-options.5,v 1.50 2011/05/20 13:48:32 tomasz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
|
||||
.\" Copyright (c) 1996-2003 by Internet Software Consortium
|
||||
@@ -1451,9 +1451,7 @@ configured.
|
||||
.RS 0.25i
|
||||
.PP
|
||||
The \fBrapid-commit\fR option is a zero-length option that clients use
|
||||
to indicate their desire to enter into rapid-commit with the server. This
|
||||
option is not supported by the client at this time, and is digested by
|
||||
the server when present, so should not be configured.
|
||||
to indicate their desire to enter into rapid-commit with the server.
|
||||
.RE
|
||||
.PP
|
||||
.B option \fBdhcp6.vendor-opts\fR \fIstring\fR\fB;\fR
|
||||
@@ -1589,6 +1587,13 @@ The \fBnis-domain-name\fR option specifies the NIS domain name the client is
|
||||
expected to use, and is related to the \fBnis-servers\fR option.
|
||||
.RE
|
||||
.PP
|
||||
.B option \fBdhcp6.nis-domain-name\fR \fIdomain-name\fR\fB;\fR
|
||||
.RS 0.25i
|
||||
.PP
|
||||
The \fBdhcp6.nis-domain-name\fR option specfies NIS domain name the
|
||||
client is expected to use, and is related to \fBdhcp6.nis-servers\fR option.
|
||||
.RE
|
||||
.PP
|
||||
.B option \fBnisp-domain-name\fR \fIdomain-list\fR\fB;\fR
|
||||
.RS 0.25i
|
||||
.PP
|
||||
@@ -1596,6 +1601,13 @@ The \fBnisp-domain-name\fR option specifies the NIS+ domain name the client
|
||||
is expected to use, and is related to the \fBnisp-servers\fR option.
|
||||
.RE
|
||||
.PP
|
||||
.B option \fBdhcp6.nisp-domain-name\fR \fIdomain-name\fR\fB;\fR
|
||||
.RS 0.25i
|
||||
.PP
|
||||
The \fBdhcp6.nis-domain-name\fR option specfies NIS+ domain name the
|
||||
client is expected to use, and is related to \fBdhcp6.nisp-servers\fR option.
|
||||
.RE
|
||||
.PP
|
||||
.B option
|
||||
.B dhcp6.sntp-servers
|
||||
.I ip6-address \fR[\fB,
|
||||
|
||||
@@ -331,6 +331,11 @@ static struct option dhcpv6_options[] = {
|
||||
{ "relay-msg", "X", &dhcpv6_universe, 9, 1 },
|
||||
|
||||
/* Option code 10 is curiously unassigned. */
|
||||
/*
|
||||
* In draft-ietf-dhc-dhcpv6-25 there were two OPTION_CLIENT_MSG and
|
||||
* OPTION_SERVER_MSG options. They were eventually unified as
|
||||
* OPTION_RELAY_MSG, hence no option with value of 10.
|
||||
*/
|
||||
#if 0
|
||||
/* XXX: missing suitable atoms for the auth option. We may want
|
||||
* to 'virtually encapsulate' this option a la the fqdn option
|
||||
|
||||
@@ -1,10 +1,9 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html lang="en"><head><title>ISC-DHCP-REFERENCES: ISC DHCP References Collection</title>
|
||||
<meta http-equiv="Expires" content="Thu, 23 Jul 2009 00:21:33 +0000">
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||||
<meta name="description" content="ISC DHCP References Collection">
|
||||
<meta name="keywords" content="ISC, DHCP, Reference Implementation">
|
||||
<meta name="generator" content="xml2rfc v1.33 (http://xml.resource.org/)">
|
||||
<meta name="generator" content="xml2rfc v1.36 (http://xml.resource.org/)">
|
||||
<style type='text/css'><!--
|
||||
body {
|
||||
font-family: verdana, charcoal, helvetica, arial, sans-serif;
|
||||
@@ -144,15 +143,22 @@
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
|
||||
<tr><td class="header">ISC-DHCP-REFERENCES</td><td class="header">D. Hankins</td></tr>
|
||||
<tr><td class="header"> </td><td class="header">T. Mrugalski</td></tr>
|
||||
<tr><td class="header"> </td><td class="header">ISC</td></tr>
|
||||
<tr><td class="header"> </td><td class="header">May 2007</td></tr>
|
||||
<tr><td class="header"> </td><td class="header">May 20, 2011</td></tr>
|
||||
</table></td></tr></table>
|
||||
<h1><br />ISC DHCP References Collection</h1>
|
||||
|
||||
<h3>Abstract</h3>
|
||||
|
||||
<p>This document describes a collection of reference material
|
||||
to which ISC DHCP has been implemented as well as a more
|
||||
complete listing of references for DHCP and DHCPv6 protocols.
|
||||
</p>
|
||||
<h3>Copyright Notice</h3>
|
||||
|
||||
<p>Copyright (c) 2006-2007,2009 by Internet Systems Consortium, Inc.
|
||||
("ISC")
|
||||
<p>Copyright (c) 2006-2007,2009,2011 by Internet Systems
|
||||
Consortium, Inc. ("ISC")
|
||||
</p>
|
||||
<p>Permission to use, copy, modify, and distribute this software for
|
||||
any purpose with or without fee is hereby granted, provided that the
|
||||
@@ -166,11 +172,6 @@
|
||||
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
|
||||
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
|
||||
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
||||
</p>
|
||||
<h3>Abstract</h3>
|
||||
|
||||
<p>This document describes a collection of Reference material that
|
||||
ISC DHCP has been implemented to.
|
||||
</p><a name="toc"></a><br /><hr />
|
||||
<h3>Table of Contents</h3>
|
||||
<p class="toc">
|
||||
@@ -197,29 +198,40 @@ Unicast Datagram Protocol References<br />
|
||||
BOOTP Protocol References<br />
|
||||
<br />
|
||||
<a href="#anchor10">5.</a>
|
||||
DHCP Protocol References<br />
|
||||
DHCPv4 Protocol References<br />
|
||||
<a href="#anchor11">5.1.</a>
|
||||
DHCPv4 Protocol<br />
|
||||
<a href="#anchor12">5.1.1.</a>
|
||||
Core Protocol References<br />
|
||||
<a href="#anchor13">5.2.</a>
|
||||
DHCPv6 Protocol References<br />
|
||||
<a href="#anchor14">5.3.</a>
|
||||
DHCP Option References<br />
|
||||
<a href="#anchor15">5.3.1.</a>
|
||||
DHCPv4 Option References<br />
|
||||
<a href="#anchor14">5.2.1.</a>
|
||||
Relay Agent Information Option Options<br />
|
||||
<a href="#anchor16">5.3.2.</a>
|
||||
<a href="#anchor15">5.2.2.</a>
|
||||
Dynamic DNS Updates References<br />
|
||||
<a href="#anchor17">5.3.3.</a>
|
||||
<a href="#anchor16">5.2.3.</a>
|
||||
Experimental: Failover References<br />
|
||||
<a href="#anchor18">5.4.</a>
|
||||
<a href="#anchor17">5.3.</a>
|
||||
DHCP Procedures<br />
|
||||
<br />
|
||||
<a href="#rfc.references1">6.</a>
|
||||
<a href="#anchor18">6.</a>
|
||||
DHCPv6 Protocol References<br />
|
||||
<a href="#anchor19">6.1.</a>
|
||||
DHCPv6 Protocol References<br />
|
||||
<a href="#anchor20">6.2.</a>
|
||||
DHCPv6 Options References<br />
|
||||
<br />
|
||||
<a href="#rfc.references1">7.</a>
|
||||
References<br />
|
||||
<a href="#rfc.references1">7.1.</a>
|
||||
Published DHCPv4 References<br />
|
||||
<a href="#rfc.references2">7.2.</a>
|
||||
Published Common (DHCPv4/DHCPv6) References<br />
|
||||
<a href="#rfc.references3">7.3.</a>
|
||||
Published DHCPv6 References<br />
|
||||
<br />
|
||||
<a href="#rfc.authors">§</a>
|
||||
Author's Address<br />
|
||||
Authors' Addresses<br />
|
||||
</p>
|
||||
<br clear="all" />
|
||||
|
||||
@@ -279,6 +291,8 @@ Definition: Reference Implementation</h3>
|
||||
</p>
|
||||
<p>This means:
|
||||
</p>
|
||||
<p>
|
||||
</p>
|
||||
<ul class="text">
|
||||
<li>To produce new externally-visible behaviour, one must first
|
||||
provide a reference.
|
||||
@@ -287,7 +301,9 @@ Definition: Reference Implementation</h3>
|
||||
simple incompatibilities in any other implementation, one must
|
||||
first provide a reference.
|
||||
</li>
|
||||
</ul>
|
||||
</ul><p>
|
||||
|
||||
</p>
|
||||
<p>That is the lofty goal, at any rate. It's well understood that,
|
||||
especially because the ISC DHCP Software package has not always been
|
||||
held to this standard (but not entirely due to it), there are many
|
||||
@@ -327,8 +343,9 @@ Low Layer References</h3>
|
||||
</p>
|
||||
<p>There are a few things that DHCP servers, relays, and clients all
|
||||
need to do in order to speak the DHCP protocol in strict compliance
|
||||
with <a class='info' href='#RFC2131'>RFC2131<span> (</span><span class='info'>Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a> [RFC2131].
|
||||
</p>
|
||||
with <a class='info' href='#RFC2131'>[RFC2131]<span> (</span><span class='info'>Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a>.
|
||||
|
||||
</p>
|
||||
<ol class="text">
|
||||
<li>Transmit a UDP packet from IP:0.0.0.0 Ethernet:Self, destined to
|
||||
IP:255.255.255.255 LinkLayer:Broadcast on an unconfigured (no IP
|
||||
@@ -338,7 +355,7 @@ Low Layer References</h3>
|
||||
destined to IP:255.255.255.255 LinkLayer:Broadcast, again on an
|
||||
unconfigured interface.
|
||||
</li>
|
||||
<li>Transmit a UDP packet from IP:Self, Ethernet:Seelf, destined to
|
||||
<li>Transmit a UDP packet from IP:Self, Ethernet:Self, destined to
|
||||
IP:remote-system LinkLayer:remote-system, without transmitting a
|
||||
single ARP.
|
||||
</li>
|
||||
@@ -349,12 +366,14 @@ Low Layer References</h3>
|
||||
always configured.
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<p>The above isn't as simple as it sounds on a regular BSD socket.
|
||||
Many unix implementations will transmit broadcasts not to
|
||||
255.255.255.255, but to x.y.z.255 (where x.y.z is the system's local
|
||||
subnet). Such packets are not received by several known DHCP client
|
||||
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> [RFC2131] very explicitly demands that these packets' IP
|
||||
destination addresses be set to 255.255.255.255.
|
||||
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>
|
||||
very explicitly demands that these packets' IP destination
|
||||
addresses be set to 255.255.255.255.
|
||||
</p>
|
||||
<p>Receiving packets sent to 255.255.255.255 isn't a problem on most
|
||||
modern unixes...so long as the interface is configured. When there
|
||||
@@ -376,12 +395,12 @@ Low Layer References</h3>
|
||||
the need to implement many forms of Link Layer framing and above.
|
||||
The software gets away with not having to implement IP routing
|
||||
tables as well by simply utilizing the aforementioned 'fallback'
|
||||
UDP socket when unicasting between two configured systems is the
|
||||
need.
|
||||
UDP socket when unicasting between two configured systems is
|
||||
needed.
|
||||
</p>
|
||||
<p>Modern unixes have opened up some facilities that diminish how
|
||||
much of this sort of nefarious kludgery is necessary, but have not
|
||||
found the state of affairs absolutely absolved. In particular,
|
||||
found the state of affairs absolutely resolved. In particular,
|
||||
one might now unicast without ARP by inserting an entry into the
|
||||
ARP cache prior to transmitting. Unconfigured interfaces remain
|
||||
the sticking point, however...on virtually no modern unixes is
|
||||
@@ -395,10 +414,11 @@ Ethernet Protocol References</h3>
|
||||
|
||||
<p>ISC DHCP Implements Ethernet Version 2 ("DIX"), which is a variant
|
||||
of IEEE 802.2. No good reference of this framing is known to exist
|
||||
at this time, but it is vaguely described in <a class='info' href='#RFC0894'>RFC894<span> (</span><span class='info'>Hornig, C., “Standard for the transmission of IP datagrams over Ethernet networks,” April 1984.</span><span>)</span></a> [RFC0894] (see the section titled "Packet format"), and
|
||||
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>
|
||||
see the section titled "Packet format"), and
|
||||
the following URL is also thought to be useful.
|
||||
</p>
|
||||
<p>http://en.wikipedia.org/wiki/DIX
|
||||
<p><a href='http://en.wikipedia.org/wiki/DIX_Ethernet'>http://en.wikipedia.org/wiki/DIX_Ethernet</a>
|
||||
</p>
|
||||
<a name="anchor5"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
@@ -413,7 +433,7 @@ Token Ring Protocol References</h3>
|
||||
<a name="rfc.section.3.3"></a><h3>3.3.
|
||||
FDDI Protocol References</h3>
|
||||
|
||||
<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> [RFC1188] is the most helpful
|
||||
<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
|
||||
reference ISC DHCP has used to form FDDI packets.
|
||||
</p>
|
||||
<a name="anchor7"></a><br /><hr />
|
||||
@@ -451,7 +471,7 @@ BOOTP Protocol References</h3>
|
||||
<a name="anchor10"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.5"></a><h3>5.
|
||||
DHCP Protocol References</h3>
|
||||
DHCPv4 Protocol References</h3>
|
||||
|
||||
<a name="anchor11"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
@@ -501,46 +521,7 @@ Core Protocol References</h3>
|
||||
<a name="anchor13"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.5.2"></a><h3>5.2.
|
||||
DHCPv6 Protocol References</h3>
|
||||
|
||||
<p>For now there is only one document that specifies the DHCPv6
|
||||
protocol (there have been no updates yet), <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> [RFC3315].
|
||||
</p>
|
||||
<p>Support for DHCPv6 was added first in version 4.0.0. The server
|
||||
and client support only IA_NA. While the server does support multiple
|
||||
IA_NAs within one packet from the client, our client only supports
|
||||
sending one. There is no relay support.
|
||||
</p>
|
||||
<p>DHCPv6 introduces some new and uncomfortable ideas to the common
|
||||
software library.
|
||||
</p>
|
||||
<ol class="text">
|
||||
<li>Options of zero length are normal in DHCPv6. Currently, all
|
||||
ISC DHCP software treats zero-length options as errors.
|
||||
</li>
|
||||
<li>Options sometimes may appear multiple times. The common
|
||||
library used to treat all appearance of multiple options as
|
||||
specified in RFC2131 - to be concatenated. DHCPv6 options
|
||||
may sometimes appear multiple times (such as with IA_NA or
|
||||
IAADDR), but often must not.
|
||||
</li>
|
||||
<li>The same option space appears in DHCPv6 packets multiple times.
|
||||
If the packet was got via a relay, then the client's packet is
|
||||
stored to an option within the relay's packet...if there were two
|
||||
relays, this recurses. At each of these steps, the root "DHCPv6
|
||||
option space" is used. Further, a client packet may contain an
|
||||
IA_NA, which may contain an IAADDR - but really, in an abstract
|
||||
sense, this is again re-encapsulation of the DHCPv6 option space
|
||||
beneath options it also contains.
|
||||
</li>
|
||||
</ol>
|
||||
<p>Precisely how to correctly support the above conundrums has not
|
||||
quite yet been settled, so support is incomplete.
|
||||
</p>
|
||||
<a name="anchor14"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.5.3"></a><h3>5.3.
|
||||
DHCP Option References</h3>
|
||||
DHCPv4 Option References</h3>
|
||||
|
||||
<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
|
||||
Novell Directory Services.
|
||||
@@ -570,10 +551,8 @@ DHCP Option References</h3>
|
||||
</p>
|
||||
<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
|
||||
plain DHCPv4 option. Do not confuse this option with the relay agent
|
||||
"link selection" sub-option, although their behaviour is similar.
|
||||
</p>
|
||||
<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> [RFC3319] defines the SIP server
|
||||
options for DHCPv6.
|
||||
"link selection" sub-option, although their behaviour is
|
||||
similar.
|
||||
</p>
|
||||
<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
|
||||
options may be encoded in DHCPv4 packets, and also how multiple
|
||||
@@ -586,20 +565,10 @@ DHCP Option References</h3>
|
||||
format). ISC DHCP has both client and server support, and supports
|
||||
RFC1035 name compression.
|
||||
</p>
|
||||
<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> [RFC3646] documents the DHCPv6
|
||||
name-servers and domain-search options.
|
||||
</p>
|
||||
<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> [RFC3633] documents the Identity
|
||||
Association Prefix Delegation, which is included here for protocol
|
||||
wire reference, but which is not supported by ISC DHCP.
|
||||
</p>
|
||||
<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
|
||||
options that were documented earlier in history, but were not
|
||||
made use of.
|
||||
</p>
|
||||
<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> [RFC3898] documents four NIS options
|
||||
for delivering NIS servers and domain information in DHCPv6.
|
||||
</p>
|
||||
<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
|
||||
Enterprise-ID delimited option spaces for vendors to use in order
|
||||
to inform servers of their "vendor class" (sort of like 'uname'
|
||||
@@ -609,32 +578,17 @@ DHCP Option References</h3>
|
||||
<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'
|
||||
option space.
|
||||
</p>
|
||||
<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> [RFC4075] defines the DHCPv6 SNTP
|
||||
Servers option.
|
||||
</p>
|
||||
<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> [RFC4242] defines the Information
|
||||
Refresh Time option, which advises DHCPv6 Information-Request
|
||||
clients to return for updated information.
|
||||
</p>
|
||||
<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> [RFC4280] defines two BCMS server
|
||||
options.
|
||||
<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
|
||||
for each protocol family.
|
||||
</p>
|
||||
<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
|
||||
LEASEQUERY message type and a number of suitable response messages,
|
||||
for the purpose of sharing information about DHCP served addresses
|
||||
and clients.
|
||||
</p>
|
||||
<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> [RFC4580] defines a DHCPv6
|
||||
subscriber-id option, which is similar in principle to the DHCPv4
|
||||
relay agent option of the same name.
|
||||
</p>
|
||||
<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> [RFC4649] defines a DHCPv6 remote-id
|
||||
option, which is similar in principle to the DHCPv4 relay agent
|
||||
remote-id.
|
||||
</p>
|
||||
<a name="anchor15"></a><br /><hr />
|
||||
<a name="anchor14"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.5.3.1"></a><h3>5.3.1.
|
||||
<a name="rfc.section.5.2.1"></a><h3>5.2.1.
|
||||
Relay Agent Information Option Options</h3>
|
||||
|
||||
<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
|
||||
@@ -645,11 +599,11 @@ Relay Agent Information Option Options</h3>
|
||||
Class sub-option.
|
||||
</p>
|
||||
<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
|
||||
sub-option.
|
||||
sub-option.
|
||||
</p>
|
||||
<a name="anchor16"></a><br /><hr />
|
||||
<a name="anchor15"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.5.3.2"></a><h3>5.3.2.
|
||||
<a name="rfc.section.5.2.2"></a><h3>5.2.2.
|
||||
Dynamic DNS Updates References</h3>
|
||||
|
||||
<p>The collection of documents that describe the standards-based
|
||||
@@ -682,18 +636,18 @@ Dynamic DNS Updates References</h3>
|
||||
record. However, for DHCPv6 FQDN, we do use DHCID type code '2',
|
||||
as no other value really makes sense in our context.
|
||||
</p>
|
||||
<a name="anchor17"></a><br /><hr />
|
||||
<a name="anchor16"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.5.3.3"></a><h3>5.3.3.
|
||||
<a name="rfc.section.5.2.3"></a><h3>5.2.3.
|
||||
Experimental: Failover References</h3>
|
||||
|
||||
<p>The Failover Protocol defines a means by which two DHCP Servers
|
||||
<p>The Failover Protocol defines means by which two DHCP Servers
|
||||
can share all the relevant information about leases granted to
|
||||
DHCP clients on given networks, so that one of the two servers may
|
||||
fail and be survived by a server that can act responsibly.
|
||||
</p>
|
||||
<p>Unfortunately it has been quite some years since the last time
|
||||
this document was edited, and the authors no longer show any
|
||||
<p>Unfortunately it has been quite some years (2003) since the last
|
||||
time this document was edited, and the authors no longer show any
|
||||
interest in fielding comments or improving the document.
|
||||
</p>
|
||||
<p>The status of this protocol is very unsure, but ISC's
|
||||
@@ -715,113 +669,340 @@ Experimental: Failover References</h3>
|
||||
number assignment for this state. As a consequence, ISC DHCP has
|
||||
elected to use the value 254.
|
||||
</p>
|
||||
<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> [RFC3074] describes the Load Balancing
|
||||
<p> An optimization described in the failover protocol draft
|
||||
is included since 4.2.0a1. It permits a DHCP server
|
||||
operating in communications-interrupted state to 'rewind' a
|
||||
lease to the state most recently transmitted to its peer,
|
||||
greatly increasing a server's endurance in
|
||||
communications-interrupted. This is supported using a new
|
||||
'rewind state' record on the dhcpd.leases entry for each
|
||||
lease.
|
||||
|
||||
</p>
|
||||
<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
|
||||
Algorithm (LBA) that ISC DHCP uses in concert with the Failover
|
||||
protocol. Note that versions 3.0.* are known to misimplement the
|
||||
hash algorithm (it will only use the low 4 bits of every byte of
|
||||
the hash bucket array).
|
||||
</p>
|
||||
<a name="anchor18"></a><br /><hr />
|
||||
<a name="anchor17"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.5.4"></a><h3>5.4.
|
||||
<a name="rfc.section.5.3"></a><h3>5.3.
|
||||
DHCP Procedures</h3>
|
||||
|
||||
<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> [RFC2939] explains how to go about
|
||||
<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
|
||||
obtaining a new DHCP Option code assignment.
|
||||
</p>
|
||||
<a name="anchor18"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.6"></a><h3>6.
|
||||
DHCPv6 Protocol References</h3>
|
||||
|
||||
<a name="anchor19"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.6.1"></a><h3>6.1.
|
||||
DHCPv6 Protocol References</h3>
|
||||
|
||||
<p>For now there is only one document that specifies the base
|
||||
of the DHCPv6 protocol (there have been no updates yet),
|
||||
<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>.
|
||||
</p>
|
||||
<p>Support for DHCPv6 was first added in version 4.0.0. The server
|
||||
and client support only IA_NA. While the server does support multiple
|
||||
IA_NAs within one packet from the client, our client only supports
|
||||
sending one. There is no relay support.
|
||||
</p>
|
||||
<p>DHCPv6 introduces some new and uncomfortable ideas to the common
|
||||
software library.
|
||||
</p>
|
||||
<p>
|
||||
</p>
|
||||
<ol class="text">
|
||||
<li>Options sometimes may appear multiple times. The common
|
||||
library used to treat all appearance of multiple options as
|
||||
specified in RFC2131 - to be concatenated. DHCPv6 options
|
||||
may sometimes appear multiple times (such as with IA_NA or
|
||||
IAADDR), but often must not. As of 4.2.1-P1, multiple IA_NA, IA_PD
|
||||
or IA_TA are not supported.
|
||||
</li>
|
||||
<li>The same option space appears in DHCPv6 packets multiple times.
|
||||
If the packet was got via a relay, then the client's packet is
|
||||
stored to an option within the relay's packet...if there were two
|
||||
relays, this recurses. At each of these steps, the root "DHCPv6
|
||||
option space" is used. Further, a client packet may contain an
|
||||
IA_NA, which may contain an IAADDR - but really, in an abstract
|
||||
sense, this is again re-encapsulation of the DHCPv6 option space
|
||||
beneath options it also contains.
|
||||
</li>
|
||||
</ol><p>
|
||||
|
||||
</p>
|
||||
<p>Precisely how to correctly support the above conundrums has not
|
||||
quite yet been settled, so support is incomplete.
|
||||
</p>
|
||||
<a name="anchor20"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.6.2"></a><h3>6.2.
|
||||
DHCPv6 Options References</h3>
|
||||
|
||||
<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
|
||||
options for DHCPv6.
|
||||
</p>
|
||||
<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
|
||||
name-servers and domain-search options.
|
||||
</p>
|
||||
<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
|
||||
Association Prefix Delegation for DHCPv6, which is included
|
||||
here for protocol wire reference, but which is not supported
|
||||
by ISC DHCP.
|
||||
</p>
|
||||
<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
|
||||
for delivering NIS servers and domain information in DHCPv6.
|
||||
</p>
|
||||
<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
|
||||
Servers option.
|
||||
</p>
|
||||
<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
|
||||
Refresh Time option, which advises DHCPv6 Information-Request
|
||||
clients to return for updated information.
|
||||
</p>
|
||||
<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
|
||||
for each protocol family.
|
||||
</p>
|
||||
<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
|
||||
subscriber-id option, which is similar in principle to the DHCPv4
|
||||
relay agent option of the same name.
|
||||
</p>
|
||||
<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
|
||||
option, which is similar in principle to the DHCPv4 relay agent
|
||||
remote-id.
|
||||
</p>
|
||||
<a name="rfc.references"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<a name="rfc.section.7"></a><h3>7.
|
||||
References</h3>
|
||||
|
||||
<a name="rfc.references1"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<h3>6. References</h3>
|
||||
<h3>7.1. Published DHCPv4 References</h3>
|
||||
<table width="99%" border="0">
|
||||
<tr><td class="author-text" valign="top"><a name="RFC0760">[RFC0760]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc760.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC0768">[RFC0768]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc768.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC0894">[RFC0894]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc894.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC0951">[RFC0951]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc951.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC1035">[RFC1035]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc1035.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC1188">[RFC1188]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc1188.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC1542">[RFC1542]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc1542.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2131">[RFC2131]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/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>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2132">[RFC2132]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/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>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2241">[RFC2241]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/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>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2242">[RFC2242]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/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>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2485">[RFC2485]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/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>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2563">[RFC2563]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2610">[RFC2610]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc2610.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2855">[RFC2855]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2937">[RFC2937]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc2937.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC2939">[RFC2939]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc2939.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3004">[RFC3004]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3004.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3011">[RFC3011]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3011.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3046">[RFC3046]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3046.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3074">[RFC3074]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3074.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3118">[RFC3118]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3203">[RFC3203]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3256">[RFC3256]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3256.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3315">[RFC3315]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3315.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3319">[RFC3319]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3319.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3361">[RFC3361]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3396">[RFC3396]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3396.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3397">[RFC3397]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3397.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3442">[RFC3442]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3456">[RFC3456]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3495">[RFC3495]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3527">[RFC3527]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3527.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3633">[RFC3633]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3633.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3646">[RFC3646]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3646.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3594">[RFC3594]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3634">[RFC3634]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3679">[RFC3679]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3679.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3898">[RFC3898]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3898.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3825">[RFC3825]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3925">[RFC3925]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3925.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3942">[RFC3942]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc3942.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4075">[RFC4075]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4075.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4242">[RFC4242]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4242.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4280">[RFC4280]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4280.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3993">[RFC3993]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4014">[RFC4014]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4030">[RFC4030]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4039">[RFC4039]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4174">[RFC4174]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4243">[RFC4243]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4361">[RFC4361]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4388">[RFC4388]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4388.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4580">[RFC4580]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4580.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4649">[RFC4649]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4649.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4390">[RFC4390]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4436">[RFC4436]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4701">[RFC4701]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4701.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4702">[RFC4702]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4702.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4703">[RFC4703]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4703.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4704">[RFC4704]</a></td>
|
||||
<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="ftp://ftp.isi.edu/in-notes/rfc4704.txt">TXT</a>).</td></tr>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5010">[RFC5010]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5071">[RFC5071]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5107">[RFC5107]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5192">[RFC5192]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5223">[RFC5223]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5859">[RFC5859]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5969">[RFC5969]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="draft-failover">[draft-failover]</a></td>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-mip6-hiopt">[I-D.ietf-mip6-hiopt]</a></td>
|
||||
<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>
|
||||
</table>
|
||||
|
||||
<a name="rfc.references2"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<h3>7.2. Published Common (DHCPv4/DHCPv6) References</h3>
|
||||
<table width="99%" border="0">
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4280">[RFC4280]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4477">[RFC4477]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4578">[RFC4578]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4776">[RFC4776]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4833">[RFC4833]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5417">[RFC5417]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5678">[RFC5678]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5908">[RFC5908]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5970">[RFC5970]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5986">[RFC5986]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-vpn-option">[I-D.ietf-dhc-vpn-option]</a></td>
|
||||
<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>
|
||||
</table>
|
||||
|
||||
<a name="rfc.references3"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<h3>7.3. Published DHCPv6 References</h3>
|
||||
<table width="99%" border="0">
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3315">[RFC3315]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3319">[RFC3319]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3633">[RFC3633]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3646">[RFC3646]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3736">[RFC3736]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC3898">[RFC3898]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4075">[RFC4075]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4076">[RFC4076]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4242">[RFC4242]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4580">[RFC4580]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4649">[RFC4649]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4704">[RFC4704]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC4994">[RFC4994]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5007">[RFC5007]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="RFC5460">[RFC5460]</a></td>
|
||||
<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>
|
||||
<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>
|
||||
<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-01">DHCPv6 Route Option</a>,” draft-ietf-mif-dhcpv6-route-option-01 (work in progress), March 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-mif-dhcpv6-route-option-01.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-dhcpv6-ldra">[I-D.ietf-dhc-dhcpv6-ldra]</a></td>
|
||||
<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>
|
||||
<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>
|
||||
<td class="author-text">Lemon, T. and W. Wu, “<a href="http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-relay-supplied-options-06">Relay-Supplied DHCP Options</a>,” draft-ietf-dhc-dhcpv6-relay-supplied-options-06 (work in progress), May 2011 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-relay-supplied-options-06.txt">TXT</a>).</td></tr>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-pd-exclude">[I-D.ietf-dhc-pd-exclude]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-secure-dhcpv6">[I-D.ietf-dhc-secure-dhcpv6]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-mext-nemo-pd">[I-D.ietf-mext-nemo-pd]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-dhc-duid-uuid">[I-D.ietf-dhc-duid-uuid]</a></td>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="I-D.ietf-geopriv-rfc3825bis">[I-D.ietf-geopriv-rfc3825bis]</a></td>
|
||||
<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>
|
||||
<tr><td class="author-text" valign="top"><a name="draft-addr-params">[draft-addr-params]</a></td>
|
||||
<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>
|
||||
</table>
|
||||
|
||||
<a name="rfc.authors"></a><br /><hr />
|
||||
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
||||
<h3>Author's Address</h3>
|
||||
<h3>Authors' Addresses</h3>
|
||||
<table width="99%" border="0" cellpadding="0" cellspacing="0">
|
||||
<tr><td class="author-text"> </td>
|
||||
<td class="author-text">David W. Hankins</td></tr>
|
||||
@@ -832,9 +1013,19 @@ DHCP Procedures</h3>
|
||||
<td class="author-text">950 Charter Street</td></tr>
|
||||
<tr><td class="author-text"> </td>
|
||||
<td class="author-text">Redwood City, CA 94063</td></tr>
|
||||
<tr cellpadding="3"><td> </td><td> </td></tr>
|
||||
<tr><td class="author-text"> </td>
|
||||
<td class="author-text">Tomasz Mrugalski</td></tr>
|
||||
<tr><td class="author-text"> </td>
|
||||
<td class="author-text">Internet Systems Consortium,
|
||||
Inc.</td></tr>
|
||||
<tr><td class="author-text"> </td>
|
||||
<td class="author-text">950 Charter Street</td></tr>
|
||||
<tr><td class="author-text"> </td>
|
||||
<td class="author-text">Redwood City, CA 94063</td></tr>
|
||||
<tr><td class="author" align="right">Phone: </td>
|
||||
<td class="author-text">+1 650 423 1300</td></tr>
|
||||
<td class="author-text">+1 650 423 1345</td></tr>
|
||||
<tr><td class="author" align="right">Email: </td>
|
||||
<td class="author-text"><a href="mailto:David_Hankins@isc.org">David_Hankins@isc.org</a></td></tr>
|
||||
<td class="author-text"><a href="mailto:Tomasz_Mrugalski@isc.org">Tomasz_Mrugalski@isc.org</a></td></tr>
|
||||
</table>
|
||||
</body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -1,6 +1,6 @@
|
||||
<?xml version='1.0' ?>
|
||||
|
||||
<!-- $Id: References.xml,v 1.4 2009/07/23 18:52:20 sar Exp $ -->
|
||||
<!-- $Id: References.xml,v 1.5 2011/05/20 13:48:33 tomasz Exp $ -->
|
||||
|
||||
<?rfc private="ISC-DHCP-REFERENCES" ?>
|
||||
|
||||
@@ -9,6 +9,7 @@
|
||||
<?rfc compact="yes"?>
|
||||
<?rfc subcompact="no"?>
|
||||
<?rfc tocompact="no"?>
|
||||
<?rfc symrefs="yes"?>
|
||||
|
||||
<!DOCTYPE rfc SYSTEM 'rfc2629bis.dtd' [
|
||||
<!ENTITY rfc760 PUBLIC ''
|
||||
@@ -77,8 +78,8 @@
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4075.xml'>
|
||||
<!ENTITY rfc4242 PUBLIC ''
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4242.xml'>
|
||||
<!ENTITY rfc4280 PUBLIC ''
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4280.xml'>
|
||||
<!ENTITY rfc4361 PUBLIC ''
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4361.xml'>
|
||||
<!ENTITY rfc4388 PUBLIC ''
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4388.xml'>
|
||||
<!ENTITY rfc4580 PUBLIC ''
|
||||
@@ -91,9 +92,9 @@
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4702.xml'>
|
||||
<!ENTITY rfc4703 PUBLIC ''
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4703.xml'>
|
||||
<!ENTITY rfc4704 PUBLIC ''
|
||||
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4704.xml'>
|
||||
]>
|
||||
]>
|
||||
|
||||
|
||||
|
||||
<rfc ipr="none">
|
||||
<front>
|
||||
@@ -111,17 +112,42 @@
|
||||
<region>CA</region>
|
||||
<code>94063</code>
|
||||
</postal>
|
||||
|
||||
<phone>+1 650 423 1300</phone>
|
||||
<email>David_Hankins@isc.org</email>
|
||||
</address>
|
||||
</author>
|
||||
|
||||
<date month="May" year="2007"/>
|
||||
<author initials="T." surname="Mrugalski" fullname="Tomasz Mrugalski">
|
||||
<organization abbrev="ISC">Internet Systems Consortium,
|
||||
Inc.
|
||||
</organization>
|
||||
|
||||
<address>
|
||||
<postal>
|
||||
<street>950 Charter Street</street>
|
||||
<city>Redwood City</city>
|
||||
<region>CA</region>
|
||||
<code>94063</code>
|
||||
</postal>
|
||||
|
||||
<phone>+1 650 423 1345</phone>
|
||||
<email>Tomasz_Mrugalski@isc.org</email>
|
||||
</address>
|
||||
</author>
|
||||
|
||||
<date day="20" month="May" year="2011"/>
|
||||
|
||||
<keyword>ISC</keyword>
|
||||
<keyword>DHCP</keyword>
|
||||
<keyword>Reference Implementation</keyword>
|
||||
|
||||
<abstract>
|
||||
<t>This document describes a collection of reference material
|
||||
to which ISC DHCP has been implemented as well as a more
|
||||
complete listing of references for DHCP and DHCPv6 protocols.</t>
|
||||
</abstract>
|
||||
|
||||
<note title="Copyright Notice">
|
||||
<t>Copyright (c) 2006-2007,2009 by Internet Systems Consortium, Inc.
|
||||
("ISC")</t>
|
||||
<t>Copyright (c) 2006-2007,2009,2011 by Internet Systems
|
||||
Consortium, Inc. ("ISC")</t>
|
||||
|
||||
<t>Permission to use, copy, modify, and distribute this software for
|
||||
any purpose with or without fee is hereby granted, provided that the
|
||||
@@ -137,14 +163,6 @@
|
||||
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</t>
|
||||
</note>
|
||||
|
||||
<keyword>ISC</keyword>
|
||||
<keyword>DHCP</keyword>
|
||||
<keyword>Reference Implementation</keyword>
|
||||
|
||||
<abstract>
|
||||
<t>This document describes a collection of Reference material that
|
||||
ISC DHCP has been implemented to.</t>
|
||||
</abstract>
|
||||
</front>
|
||||
|
||||
<middle>
|
||||
@@ -197,6 +215,7 @@
|
||||
|
||||
<t>This means:</t>
|
||||
|
||||
<t>
|
||||
<list style="symbols">
|
||||
<t>To produce new externally-visible behaviour, one must first
|
||||
provide a reference.</t>
|
||||
@@ -205,6 +224,7 @@
|
||||
simple incompatibilities in any other implementation, one must
|
||||
first provide a reference.</t>
|
||||
</list>
|
||||
</t>
|
||||
|
||||
<t>That is the lofty goal, at any rate. It's well understood that,
|
||||
especially because the ISC DHCP Software package has not always been
|
||||
@@ -242,7 +262,7 @@
|
||||
|
||||
<t>There are a few things that DHCP servers, relays, and clients all
|
||||
need to do in order to speak the DHCP protocol in strict compliance
|
||||
with <xref target="RFC2131">RFC2131</xref>.</t>
|
||||
with <xref target="RFC2131"/>.
|
||||
|
||||
<list style="numbers">
|
||||
<t>Transmit a UDP packet from IP:0.0.0.0 Ethernet:Self, destined to
|
||||
@@ -253,7 +273,7 @@
|
||||
destined to IP:255.255.255.255 LinkLayer:Broadcast, again on an
|
||||
unconfigured interface.</t>
|
||||
|
||||
<t>Transmit a UDP packet from IP:Self, Ethernet:Seelf, destined to
|
||||
<t>Transmit a UDP packet from IP:Self, Ethernet:Self, destined to
|
||||
IP:remote-system LinkLayer:remote-system, without transmitting a
|
||||
single ARP.</t>
|
||||
|
||||
@@ -262,15 +282,15 @@
|
||||
with ARP providing the glue, or it may be to a remote system via
|
||||
one or more routers as normal). In this case, the interfaces are
|
||||
always configured.</t>
|
||||
</list>
|
||||
</list></t>
|
||||
|
||||
<t>The above isn't as simple as it sounds on a regular BSD socket.
|
||||
Many unix implementations will transmit broadcasts not to
|
||||
255.255.255.255, but to x.y.z.255 (where x.y.z is the system's local
|
||||
subnet). Such packets are not received by several known DHCP client
|
||||
implementations - and it's not their fault, <xref target="RFC2131">
|
||||
RFC2131</xref> very explicitly demands that these packets' IP
|
||||
destination addresses be set to 255.255.255.255.</t>
|
||||
implementations - and it's not their fault, <xref target="RFC2131"/>
|
||||
very explicitly demands that these packets' IP destination
|
||||
addresses be set to 255.255.255.255.</t>
|
||||
|
||||
<t>Receiving packets sent to 255.255.255.255 isn't a problem on most
|
||||
modern unixes...so long as the interface is configured. When there
|
||||
@@ -292,12 +312,12 @@
|
||||
the need to implement many forms of Link Layer framing and above.
|
||||
The software gets away with not having to implement IP routing
|
||||
tables as well by simply utilizing the aforementioned 'fallback'
|
||||
UDP socket when unicasting between two configured systems is the
|
||||
need.</t>
|
||||
UDP socket when unicasting between two configured systems is
|
||||
needed.</t>
|
||||
|
||||
<t>Modern unixes have opened up some facilities that diminish how
|
||||
much of this sort of nefarious kludgery is necessary, but have not
|
||||
found the state of affairs absolutely absolved. In particular,
|
||||
found the state of affairs absolutely resolved. In particular,
|
||||
one might now unicast without ARP by inserting an entry into the
|
||||
ARP cache prior to transmitting. Unconfigured interfaces remain
|
||||
the sticking point, however...on virtually no modern unixes is
|
||||
@@ -307,11 +327,11 @@
|
||||
<section title="Ethernet Protocol References">
|
||||
<t>ISC DHCP Implements Ethernet Version 2 ("DIX"), which is a variant
|
||||
of IEEE 802.2. No good reference of this framing is known to exist
|
||||
at this time, but it is vaguely described in <xref target="RFC0894">
|
||||
RFC894</xref> (see the section titled "Packet format"), and
|
||||
at this time, but it is vaguely described in <xref target="RFC0894"/>
|
||||
see the section titled "Packet format"), and
|
||||
the following URL is also thought to be useful.</t>
|
||||
|
||||
<t>http://en.wikipedia.org/wiki/DIX</t>
|
||||
<t><eref target="http://en.wikipedia.org/wiki/DIX_Ethernet">http://en.wikipedia.org/wiki/DIX_Ethernet</eref></t>
|
||||
</section>
|
||||
|
||||
<section title="Token Ring Protocol References">
|
||||
@@ -320,7 +340,7 @@
|
||||
</section>
|
||||
|
||||
<section title="FDDI Protocol References">
|
||||
<t><xref target="RFC1188">RFC1188</xref> is the most helpful
|
||||
<t><xref target="RFC1188"/> is the most helpful
|
||||
reference ISC DHCP has used to form FDDI packets.</t>
|
||||
</section>
|
||||
|
||||
@@ -349,13 +369,13 @@
|
||||
RFC1542</xref>.</t>
|
||||
</section>
|
||||
|
||||
<section title="DHCP Protocol References">
|
||||
<section title="DHCPv4 Protocol References">
|
||||
<section title="DHCPv4 Protocol">
|
||||
<t>"The DHCP[v4] Protocol" is not defined in a single document. The
|
||||
following collection of references of what ISC DHCP terms "The
|
||||
DHCPv4 Protocol".</t>
|
||||
|
||||
<section title="Core Protocol References">
|
||||
<section title="Core Protocol References">
|
||||
<t><xref target="RFC2131">RFC2131</xref> defines the protocol format
|
||||
and procedures. ISC DHCP is not known to diverge from this document
|
||||
in any way. There are, however, a few points on which different
|
||||
@@ -386,47 +406,10 @@
|
||||
host-name option and, if so, null terminates any text options it
|
||||
transmits to the client. It also removes NULL termination from any
|
||||
known text option it receives prior to any other processing.</t>
|
||||
</section>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section title="DHCPv6 Protocol References">
|
||||
<t>For now there is only one document that specifies the DHCPv6
|
||||
protocol (there have been no updates yet), <xref target="RFC3315">
|
||||
RFC3315</xref>.</t>
|
||||
|
||||
<t>Support for DHCPv6 was added first in version 4.0.0. The server
|
||||
and client support only IA_NA. While the server does support multiple
|
||||
IA_NAs within one packet from the client, our client only supports
|
||||
sending one. There is no relay support.</t>
|
||||
|
||||
<t>DHCPv6 introduces some new and uncomfortable ideas to the common
|
||||
software library.</t>
|
||||
|
||||
<list style="numbers">
|
||||
<t>Options of zero length are normal in DHCPv6. Currently, all
|
||||
ISC DHCP software treats zero-length options as errors.</t>
|
||||
|
||||
<t>Options sometimes may appear multiple times. The common
|
||||
library used to treat all appearance of multiple options as
|
||||
specified in RFC2131 - to be concatenated. DHCPv6 options
|
||||
may sometimes appear multiple times (such as with IA_NA or
|
||||
IAADDR), but often must not.</t>
|
||||
|
||||
<t>The same option space appears in DHCPv6 packets multiple times.
|
||||
If the packet was got via a relay, then the client's packet is
|
||||
stored to an option within the relay's packet...if there were two
|
||||
relays, this recurses. At each of these steps, the root "DHCPv6
|
||||
option space" is used. Further, a client packet may contain an
|
||||
IA_NA, which may contain an IAADDR - but really, in an abstract
|
||||
sense, this is again re-encapsulation of the DHCPv6 option space
|
||||
beneath options it also contains.</t>
|
||||
</list>
|
||||
|
||||
<t>Precisely how to correctly support the above conundrums has not
|
||||
quite yet been settled, so support is incomplete.</t>
|
||||
</section>
|
||||
|
||||
<section title="DHCP Option References">
|
||||
<section title="DHCPv4 Option References">
|
||||
<t><xref target="RFC2241">RFC2241</xref> defines options for
|
||||
Novell Directory Services.</t>
|
||||
|
||||
@@ -455,10 +438,8 @@
|
||||
|
||||
<t><xref target="RFC3011">RFC3011</xref> defines the Subnet-Selection
|
||||
plain DHCPv4 option. Do not confuse this option with the relay agent
|
||||
"link selection" sub-option, although their behaviour is similar.</t>
|
||||
|
||||
<t><xref target="RFC3319">RFC3319</xref> defines the SIP server
|
||||
options for DHCPv6.</t>
|
||||
"link selection" sub-option, although their behaviour is
|
||||
similar.</t>
|
||||
|
||||
<t><xref target="RFC3396">RFC3396</xref> documents both how long
|
||||
options may be encoded in DHCPv4 packets, and also how multiple
|
||||
@@ -472,20 +453,10 @@
|
||||
format). ISC DHCP has both client and server support, and supports
|
||||
RFC1035 name compression.</t>
|
||||
|
||||
<t><xref target="RFC3646">RFC3646</xref> documents the DHCPv6
|
||||
name-servers and domain-search options.</t>
|
||||
|
||||
<t><xref target="RFC3633">RFC3633</xref> documents the Identity
|
||||
Association Prefix Delegation, which is included here for protocol
|
||||
wire reference, but which is not supported by ISC DHCP.</t>
|
||||
|
||||
<t><xref target="RFC3679">RFC3679</xref> documents a number of
|
||||
options that were documented earlier in history, but were not
|
||||
made use of.</t>
|
||||
|
||||
<t><xref target="RFC3898">RFC3898</xref> documents four NIS options
|
||||
for delivering NIS servers and domain information in DHCPv6.</t>
|
||||
|
||||
<t><xref target="RFC3925">RFC3925</xref> documents a pair of
|
||||
Enterprise-ID delimited option spaces for vendors to use in order
|
||||
to inform servers of their "vendor class" (sort of like 'uname'
|
||||
@@ -495,30 +466,15 @@
|
||||
<t><xref target="RFC3942">RFC3942</xref> redefined the 'site local'
|
||||
option space.</t>
|
||||
|
||||
<t><xref target="RFC4075">RFC4075</xref> defines the DHCPv6 SNTP
|
||||
Servers option.</t>
|
||||
|
||||
<t><xref target="RFC4242">RFC4242</xref> defines the Information
|
||||
Refresh Time option, which advises DHCPv6 Information-Request
|
||||
clients to return for updated information.</t>
|
||||
|
||||
<t><xref target="RFC4280">RFC4280</xref> defines two BCMS server
|
||||
options.</t>
|
||||
<t><xref target="RFC4280" /> defines two BCMS server options
|
||||
for each protocol family.</t>
|
||||
|
||||
<t><xref target="RFC4388">RFC4388</xref> defined the DHCPv4
|
||||
LEASEQUERY message type and a number of suitable response messages,
|
||||
for the purpose of sharing information about DHCP served addresses
|
||||
and clients.</t>
|
||||
|
||||
<t><xref target="RFC4580">RFC4580</xref> defines a DHCPv6
|
||||
subscriber-id option, which is similar in principle to the DHCPv4
|
||||
relay agent option of the same name.</t>
|
||||
|
||||
<t><xref target="RFC4649">RFC4649</xref> defines a DHCPv6 remote-id
|
||||
option, which is similar in principle to the DHCPv4 relay agent
|
||||
remote-id.</t>
|
||||
|
||||
<section title="Relay Agent Information Option Options">
|
||||
<section title="Relay Agent Information Option Options">
|
||||
<t><xref target="RFC3046">RFC3046</xref> defines the Relay Agent
|
||||
Information Option and provides a number of sub-option
|
||||
definitions.</t>
|
||||
@@ -527,8 +483,9 @@
|
||||
Class sub-option.</t>
|
||||
|
||||
<t><xref target="RFC3527">RFC3527</xref> defines the Link Selection
|
||||
sub-option.</t>
|
||||
</section>
|
||||
sub-option.</t>
|
||||
</section>
|
||||
|
||||
|
||||
<section title="Dynamic DNS Updates References">
|
||||
<t>The collection of documents that describe the standards-based
|
||||
@@ -563,13 +520,13 @@
|
||||
</section>
|
||||
|
||||
<section title="Experimental: Failover References">
|
||||
<t>The Failover Protocol defines a means by which two DHCP Servers
|
||||
<t>The Failover Protocol defines means by which two DHCP Servers
|
||||
can share all the relevant information about leases granted to
|
||||
DHCP clients on given networks, so that one of the two servers may
|
||||
fail and be survived by a server that can act responsibly.</t>
|
||||
|
||||
<t>Unfortunately it has been quite some years since the last time
|
||||
this document was edited, and the authors no longer show any
|
||||
<t>Unfortunately it has been quite some years (2003) since the last
|
||||
time this document was edited, and the authors no longer show any
|
||||
interest in fielding comments or improving the document.</t>
|
||||
|
||||
<t>The status of this protocol is very unsure, but ISC's
|
||||
@@ -591,7 +548,17 @@
|
||||
number assignment for this state. As a consequence, ISC DHCP has
|
||||
elected to use the value 254.</t>
|
||||
|
||||
<t><xref target="RFC3074">RFC3074</xref> describes the Load Balancing
|
||||
<t> An optimization described in the failover protocol draft
|
||||
is included since 4.2.0a1. It permits a DHCP server
|
||||
operating in communications-interrupted state to 'rewind' a
|
||||
lease to the state most recently transmitted to its peer,
|
||||
greatly increasing a server's endurance in
|
||||
communications-interrupted. This is supported using a new
|
||||
'rewind state' record on the dhcpd.leases entry for each
|
||||
lease.
|
||||
</t>
|
||||
|
||||
<t><xref target="RFC3074" /> describes the Load Balancing
|
||||
Algorithm (LBA) that ISC DHCP uses in concert with the Failover
|
||||
protocol. Note that versions 3.0.* are known to misimplement the
|
||||
hash algorithm (it will only use the low 4 bits of every byte of
|
||||
@@ -600,14 +567,91 @@
|
||||
</section>
|
||||
|
||||
<section title="DHCP Procedures">
|
||||
<t><xref target="RFC2939">RFC2939</xref> explains how to go about
|
||||
<t><xref target="RFC2939" /> explains how to go about
|
||||
obtaining a new DHCP Option code assignment.</t>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
|
||||
<section title="DHCPv6 Protocol References">
|
||||
|
||||
<section title="DHCPv6 Protocol References">
|
||||
<t>For now there is only one document that specifies the base
|
||||
of the DHCPv6 protocol (there have been no updates yet),
|
||||
<xref target="RFC3315"/>.</t>
|
||||
|
||||
<t>Support for DHCPv6 was first added in version 4.0.0. The server
|
||||
and client support only IA_NA. While the server does support multiple
|
||||
IA_NAs within one packet from the client, our client only supports
|
||||
sending one. There is no relay support.</t>
|
||||
|
||||
<t>DHCPv6 introduces some new and uncomfortable ideas to the common
|
||||
software library.</t>
|
||||
|
||||
<t>
|
||||
<list style="numbers">
|
||||
<t>Options sometimes may appear multiple times. The common
|
||||
library used to treat all appearance of multiple options as
|
||||
specified in RFC2131 - to be concatenated. DHCPv6 options
|
||||
may sometimes appear multiple times (such as with IA_NA or
|
||||
IAADDR), but often must not. As of 4.2.1-P1, multiple IA_NA, IA_PD
|
||||
or IA_TA are not supported.</t>
|
||||
|
||||
<t>The same option space appears in DHCPv6 packets multiple times.
|
||||
If the packet was got via a relay, then the client's packet is
|
||||
stored to an option within the relay's packet...if there were two
|
||||
relays, this recurses. At each of these steps, the root "DHCPv6
|
||||
option space" is used. Further, a client packet may contain an
|
||||
IA_NA, which may contain an IAADDR - but really, in an abstract
|
||||
sense, this is again re-encapsulation of the DHCPv6 option space
|
||||
beneath options it also contains.</t>
|
||||
</list>
|
||||
</t>
|
||||
|
||||
<t>Precisely how to correctly support the above conundrums has not
|
||||
quite yet been settled, so support is incomplete.</t>
|
||||
</section>
|
||||
|
||||
<section title="DHCPv6 Options References">
|
||||
<t><xref target="RFC3319"/> defines the SIP server
|
||||
options for DHCPv6.</t>
|
||||
|
||||
<t><xref target="RFC3646"/> documents the DHCPv6
|
||||
name-servers and domain-search options.</t>
|
||||
|
||||
<t><xref target="RFC3633"/> documents the Identity
|
||||
Association Prefix Delegation for DHCPv6, which is included
|
||||
here for protocol wire reference, but which is not supported
|
||||
by ISC DHCP.</t>
|
||||
|
||||
<t><xref target="RFC3898"/> documents four NIS options
|
||||
for delivering NIS servers and domain information in DHCPv6.</t>
|
||||
|
||||
<t><xref target="RFC4075"/> defines the DHCPv6 SNTP
|
||||
Servers option.</t>
|
||||
|
||||
<t><xref target="RFC4242"/> defines the Information
|
||||
Refresh Time option, which advises DHCPv6 Information-Request
|
||||
clients to return for updated information.</t>
|
||||
|
||||
<t><xref target="RFC4280"/> defines two BCMS server options
|
||||
for each protocol family.</t>
|
||||
|
||||
<t><xref target="RFC4580"/> defines a DHCPv6
|
||||
subscriber-id option, which is similar in principle to the DHCPv4
|
||||
relay agent option of the same name.</t>
|
||||
|
||||
<t><xref target="RFC4649"/> defines a DHCPv6 remote-id
|
||||
option, which is similar in principle to the DHCPv4 relay agent
|
||||
remote-id.</t>
|
||||
|
||||
</section>
|
||||
</section>
|
||||
|
||||
</middle>
|
||||
|
||||
<back>
|
||||
<references>
|
||||
<references title="Published DHCPv4 References">
|
||||
&rfc760;
|
||||
&rfc768;
|
||||
&rfc894;
|
||||
@@ -620,49 +664,125 @@
|
||||
&rfc2241;
|
||||
&rfc2242;
|
||||
&rfc2485;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.2563'?>
|
||||
&rfc2610;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.2855'?>
|
||||
&rfc2937;
|
||||
&rfc2939;
|
||||
&rfc3004;
|
||||
&rfc3011;
|
||||
&rfc3046;
|
||||
&rfc3074;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3118'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3203'?>
|
||||
&rfc3256;
|
||||
&rfc3315;
|
||||
&rfc3319;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3361'?>
|
||||
&rfc3396;
|
||||
&rfc3397;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3442'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3456'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3495'?>
|
||||
&rfc3527;
|
||||
&rfc3633;
|
||||
&rfc3646;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3594'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3634'?>
|
||||
&rfc3679;
|
||||
&rfc3898;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3825'?>
|
||||
&rfc3925;
|
||||
&rfc3942;
|
||||
&rfc4075;
|
||||
&rfc4242;
|
||||
&rfc4280;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3993'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4014'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4030'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4039'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4174'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4243'?>
|
||||
&rfc4361;
|
||||
&rfc4388;
|
||||
&rfc4580;
|
||||
&rfc4649;
|
||||
&rfc4701;
|
||||
&rfc4702;
|
||||
&rfc4703;
|
||||
&rfc4704;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4390'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4436'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4701'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4702'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4703'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5010'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5071'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5107'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5192'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5223'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5859'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5969'?>
|
||||
|
||||
<reference anchor='draft-failover'>
|
||||
<front>
|
||||
<title>DHCP Failover Protocol</title>
|
||||
|
||||
<author initials='R.' surname='Droms' fullname='Ralph Droms'>
|
||||
<organization abbrev='Cisco'>Cisco Systems</organization>
|
||||
</author>
|
||||
|
||||
<date month='March' year='2003'/>
|
||||
</front>
|
||||
<format type="TXT" octets="312151" target="https://www.isc.org/sw/dhcp/drafts/draft-ietf-dhc-failover-12.txt"/>
|
||||
</reference>
|
||||
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-dhcpv4-relay-encapsulation-00.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-dhcpv4-bulk-leasequery-03.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-leasequery-by-remote-id-09.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-relay-id-suboption-07.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-mip6-hiopt-17.xml'?>
|
||||
|
||||
</references>
|
||||
|
||||
<references title="Published Common (DHCPv4/DHCPv6) References">
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4280'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4477'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4578'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4776'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4833'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5417'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5678'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5908'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5970'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5986'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-vpn-option-12.xml'?>
|
||||
|
||||
</references>
|
||||
|
||||
<references title="Published DHCPv6 References">
|
||||
|
||||
&rfc3315;
|
||||
&rfc3319;
|
||||
&rfc3633;
|
||||
&rfc3646;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.3736'?>
|
||||
&rfc3898;
|
||||
&rfc4075;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4076'?>
|
||||
&rfc4242;
|
||||
&rfc4580;
|
||||
&rfc4649;
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4704'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.4994'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5007'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml/reference.RFC.5460'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-mif-dhcpv6-route-option'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dhc-dhcpv6-ldra'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dhc-dhcpv6-relay-supplied-options'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-pd-exclude-01.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-secure-dhcpv6-02.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-mext-nemo-pd'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-dhc-duid-uuid-03.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-softwire-ds-lite-tunnel-option-10.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-mif-dns-server-selection-01.xml'?>
|
||||
<?rfc include='http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-geopriv-rfc3825bis-17.xml'?>
|
||||
|
||||
<reference anchor='draft-addr-params'>
|
||||
<front>
|
||||
<title>Address Parameters Option for DHCPv6</title>
|
||||
<author initials='T.' surname='Mrugalski' fullname='Mrugalski'>
|
||||
<organization abbrev='Cisco'>Gdansk University of Technology</organization>
|
||||
</author>
|
||||
<date month='April' year='2007'/>
|
||||
</front>
|
||||
<format type="TXT" target="http://klub.com.pl/dhcpv6/doc/draft-mrugalski-addropts-XX-2007-04-17.txt"/>
|
||||
</reference>
|
||||
|
||||
</references>
|
||||
</back>
|
||||
</rfc>
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@
|
||||
.\" Support and other services are available for ISC products - see
|
||||
.\" https://www.isc.org for more information or to learn more about ISC.
|
||||
.\"
|
||||
.\" $Id: dhcpd.8,v 1.34 2011/04/15 21:58:12 sar Exp $
|
||||
.\" $Id: dhcpd.8,v 1.35 2011/05/20 13:48:33 tomasz Exp $
|
||||
.\"
|
||||
.TH dhcpd 8
|
||||
.SH NAME
|
||||
@@ -190,11 +190,11 @@ possible, and listen for DHCP broadcasts on each interface.
|
||||
.SH COMMAND LINE OPTIONS
|
||||
.TP
|
||||
.BI \-4
|
||||
Run as a DHCP server. This cannot be combined with \fB\-6\fR.
|
||||
Run as a DHCP server. This is the default and cannot be combined with
|
||||
\fB\-6\fR.
|
||||
.TP
|
||||
.BI \-6
|
||||
Run as a DHCPv6 server. This is the default and cannot be combined
|
||||
with \fB\-4\fR.
|
||||
Run as a DHCPv6 server. This cannot be combined with \fB\-4\fR.
|
||||
.TP
|
||||
.BI \-p \ port
|
||||
The udp port number on which
|
||||
|
||||
Reference in New Issue
Block a user