Switch isc urls from http to https and correct sw to services or software

for new web site as appropirate.

1 files changed, 252 insertions, 252 deletions

diff --git a/doc/References.txt b/doc/References.txt
index 8e656efe..7e9e1ed3 100644
--- a/doc/References.txt
+++ b/doc/References.txt
@@ -3,15 +3,15 @@
 
 ISC-DHCP-REFERENCES                                           D. Hankins
                                                                      ISC
-                                                             August 2006
+                                                                May 2007
 
 
                      ISC DHCP References Collection
 
-
 Copyright Notice
 
-   Copyright (c) 2006-2007 by Internet Systems Consortium, Inc. ("ISC")
+   Copyright (c) 2006-2007,2009 by Internet Systems Consortium, Inc.
+   ("ISC")
 
    Permission to use, copy, modify, and distribute this software for any
    purpose with or without fee is hereby granted, provided that the
@@ -54,7 +54,7 @@ Abstract
 
 Hankins                                                         [Page 1]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
 Table of Contents
@@ -79,7 +79,7 @@ Table of Contents
      5.3.  DHCP Option References . . . . . . . . . . . . . . . . . .  8
        5.3.1.  Relay Agent Information Option Options . . . . . . . . 10
        5.3.2.  Dynamic DNS Updates References . . . . . . . . . . . . 10
-       5.3.3.  Experimental: Failover References  . . . . . . . . . . 10
+       5.3.3.  Experimental: Failover References  . . . . . . . . . . 11
      5.4.  DHCP Procedures  . . . . . . . . . . . . . . . . . . . . . 11
 
    6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
@@ -110,7 +110,7 @@ Table of Contents
 
 Hankins                                                         [Page 2]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
 1.  Introduction
@@ -166,7 +166,7 @@ Hankins                                                         [Page 2]
 
 Hankins                                                         [Page 3]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
    o  To produce new externally-visible behaviour, one must first
@@ -213,7 +213,7 @@ Hankins                                                         [Page 3]
 
    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 RFC2131 [8].
+   with RFC2131 [RFC2131].
 
    1.  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
@@ -222,7 +222,7 @@ Hankins                                                         [Page 3]
 
 Hankins                                                         [Page 4]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
        address yet) interface.
@@ -245,8 +245,9 @@ Hankins                                                         [Page 4]
    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, RFC2131 [8] very explicitly demands that
-   these packets' IP destination addresses be set to 255.255.255.255.
+   - and it's not their fault, RFC2131 [RFC2131] very explicitly demands
+   that these packets' IP destination addresses be set to
+   255.255.255.255.
 
    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
@@ -272,15 +273,15 @@ Hankins                                                         [Page 4]
 
    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, one might
 
 
 
 Hankins                                                         [Page 5]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
+   the state of affairs absolutely absolved.  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 it possible to
@@ -291,9 +292,9 @@ Hankins                                                         [Page 5]
 
    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 RFC894 [3] (see the section
-   titled "Packet format"), and the following URL is also thought to be
-   useful.
+   this time, but it is vaguely described in RFC894 [RFC0894] (see the
+   section titled "Packet format"), and the following URL is also
+   thought to be useful.
 
    http://en.wikipedia.org/wiki/DIX
 
@@ -303,19 +304,19 @@ Hankins                                                         [Page 5]
 
 3.3.  FDDI Protocol References
 
-   RFC1188 [6] is the most helpful reference ISC DHCP has used to form
-   FDDI packets.
+   RFC1188 [RFC1188] is the most helpful reference ISC DHCP has used to
+   form FDDI packets.
 
 3.4.  Internet Protocol Version 4 References
 
-   RFC760 [1] fundamentally defines the bare IPv4 protocol which ISC
-   DHCP implements.
+   RFC760 [RFC0760] fundamentally defines the bare IPv4 protocol which
+   ISC DHCP implements.
 
 3.5.  Unicast Datagram Protocol References
 
-   RFC768 [2] defines the User Datagram Protocol that ultimately carries
-   the DHCP or BOOTP protocol.  The destination DHCP server port is 67,
-   the client port is 68.  Source ports are irrelevant.
+   RFC768 [RFC0768] defines the User Datagram Protocol that ultimately
+   carries the DHCP or BOOTP protocol.  The destination DHCP server port
+   is 67, the client port is 68.  Source ports are irrelevant.
 
 
 4.  BOOTP Protocol References
@@ -326,15 +327,14 @@ Hankins                                                         [Page 5]
    packet formats - DHCP is merely a conventional use of both BOOTP
    header fields and the trailing 'options' space.
 
-   The ISC DHCP server supports BOOTP clients conforming to RFC951 [4]
-   and RFC1542 [7].
-
+   The ISC DHCP server supports BOOTP clients conforming to RFC951
+   [RFC0951] and RFC1542 [RFC1542].
 
 
 
 Hankins                                                         [Page 6]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
 5.  DHCP Protocol References
@@ -347,52 +347,53 @@ Hankins                                                         [Page 6]
 
 5.1.1.  Core Protocol References
 
-   RFC2131 [8] 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 implementations have arisen
-   out of vagueries in the document.  DHCP Clients exist which, at one
-   time, present themselves as using a Client Identifier Option which is
-   equal to the client's hardware address.  Later, the client transmits
-   DHCP packets with no Client Identifier Option present - essentially
-   identifying themselves using the hardware address.  Some DHCP Servers
-   have been developed which identify this client as a single client.
-   ISC has interpreted RFC2131 to indicate that these clients must be
-   treated as two separate entities (and hence two, separate addresses).
-   Client behaviour (Embedded Windows products) has developed that
-   relies on the former implementation, and hence is incompatible with
-   the latter.  Also, RFC2131 demands explicitly that some header fields
-   be zeroed upon certain message types.  The ISC DHCP Server instead
-   copies many of these fields from the packet received from the client
-   or relay, which may not be zero.  It is not known if there is a good
-   reason for this that has not been documented.
-
-   RFC2132 [9] defines the initial set of DHCP Options and provides a
-   great deal of guidance on how to go about formatting and processing
-   options.  The document unfortunately waffles to a great extent about
-   the NULL termination of DHCP Options, and some DHCP Clients (Windows
-   95) have been implemented that rely upon DHCP Options containing text
-   strings to be NULL-terminated (or else they crash).  So, ISC DHCP
-   detects if clients null-terminate the 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.
+   RFC2131 [RFC2131] 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 implementations have
+   arisen out of vagueries in the document.  DHCP Clients exist which,
+   at one time, present themselves as using a Client Identifier Option
+   which is equal to the client's hardware address.  Later, the client
+   transmits DHCP packets with no Client Identifier Option present -
+   essentially identifying themselves using the hardware address.  Some
+   DHCP Servers have been developed which identify this client as a
+   single client.  ISC has interpreted RFC2131 to indicate that these
+   clients must be treated as two separate entities (and hence two,
+   separate addresses).  Client behaviour (Embedded Windows products)
+   has developed that relies on the former implementation, and hence is
+   incompatible with the latter.  Also, RFC2131 demands explicitly that
+   some header fields be zeroed upon certain message types.  The ISC
+   DHCP Server instead copies many of these fields from the packet
+   received from the client or relay, which may not be zero.  It is not
+   known if there is a good reason for this that has not been
+   documented.
+
+   RFC2132 [RFC2132] defines the initial set of DHCP Options and
+   provides a great deal of guidance on how to go about formatting and
+   processing options.  The document unfortunately waffles to a great
+   extent about the NULL termination of DHCP Options, and some DHCP
+   Clients (Windows 95) have been implemented that rely upon DHCP
+   Options containing text strings to be NULL-terminated (or else they
+   crash).  So, ISC DHCP detects if clients null-terminate the 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.
 
 5.2.  DHCPv6 Protocol References
 
    For now there is only one document that specifies the DHCPv6 protocol
-   (there have been no updates yet), RFC3315 [21].
+   (there have been no updates yet), RFC3315 [RFC3315].
 
    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
 
 
 
 Hankins                                                         [Page 7]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
+   IA_NAs within one packet from the client, our client only supports
    sending one.  There is no relay support.
 
    DHCPv6 introduces some new and uncomfortable ideas to the common
@@ -421,16 +422,17 @@ Hankins                                                         [Page 7]
 
 5.3.  DHCP Option References
 
-   RFC2241 [10] defines options for Novell Directory Services.
+   RFC2241 [RFC2241] defines options for Novell Directory Services.
 
-   RFC2242 [11] defines an encapsulated option space for NWIP
+   RFC2242 [RFC2242] defines an encapsulated option space for NWIP
    configuration.
 
-   RFC2485 [12] defines the Open Group's UAP option.
+   RFC2485 [RFC2485] defines the Open Group's UAP option.
 
-   RFC2610 [13] defines options for the Service Location Protocol (SLP).
+   RFC2610 [RFC2610] defines options for the Service Location Protocol
+   (SLP).
 
-   RFC2937 [14] defines the Name Service Search Option (not to be
+   RFC2937 [RFC2937] defines the Name Service Search Option (not to be
    confused with the domain-search option).  The Name Service Search
    Option allows eg nsswitch.conf to be reconfigured via dhcp.  The ISC
    DHCP server implements this option, and the ISC DHCP client is
@@ -438,96 +440,100 @@ Hankins                                                         [Page 7]
    One would need to make their relevant dhclient-script process this
    option in a way that is suitable for the system.
 
-   RFC3004 [16] defines the User-Class option.  Note carefully that ISC
-   DHCP currently does not implement to this reference, but has
-   (inexplicably) selected an incompatible format: a plain text string.
+   RFC3004 [RFC3004] defines the User-Class option.  Note carefully that
 
 
 
 Hankins                                                         [Page 8]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
+
 
+   ISC DHCP currently does not implement to this reference, but has
+   (inexplicably) selected an incompatible format: a plain text string.
 
-   RFC3011 [17] defines the Subnet-Selection plain DHCPv4 option.  Do
-   not confuse this option with the relay agent "link selection" sub-
+   RFC3011 [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.
 
-   RFC3319 [22] defines the SIP server options for DHCPv6.
+   RFC3319 [RFC3319] defines the SIP server options for DHCPv6.
 
-   RFC3396 [23] documents both how long options may be encoded in DHCPv4
-   packets, and also how multiple instances of the same option code
-   within a DHCPv4 packet will be decoded by receivers.
+   RFC3396 [RFC3396] documents both how long options may be encoded in
+   DHCPv4 packets, and also how multiple instances of the same option
+   code within a DHCPv4 packet will be decoded by receivers.
 
-   RFC3397 [24] documents the Domain-Search Option, which allows the
-   configuration of the /etc/resolv.conf 'search' parameter in a way
-   that is RFC1035 [5] wire format compatible (in fact, it uses the
-   RFC1035 wire format).  ISC DHCP has both client and server support,
-   and supports RFC1035 name compression.
+   RFC3397 [RFC3397] documents the Domain-Search Option, which allows
+   the configuration of the /etc/resolv.conf 'search' parameter in a way
+   that is RFC1035 [RFC1035] wire format compatible (in fact, it uses
+   the RFC1035 wire format).  ISC DHCP has both client and server
+   support, and supports RFC1035 name compression.
 
-   RFC3646 [27] documents the DHCPv6 name-servers and domain-search
+   RFC3646 [RFC3646] documents the DHCPv6 name-servers and domain-search
    options.
 
-   RFC3633 [26] documents the Identity Association Prefix Delegation,
-   which is included here for protocol wire reference, but which is not
-   supported by ISC DHCP.
+   RFC3633 [RFC3633] documents the Identity Association Prefix
+   Delegation, which is included here for protocol wire reference, but
+   which is not supported by ISC DHCP.
 
-   RFC3679 [28] documents a number of options that were documented
+   RFC3679 [RFC3679] documents a number of options that were documented
    earlier in history, but were not made use of.
 
-   RFC3898 [29] documents four NIS options for delivering NIS servers
-   and domain information in DHCPv6.
+   RFC3898 [RFC3898] documents four NIS options for delivering NIS
+   servers and domain information in DHCPv6.
 
-   RFC3925 [30] documents a pair of Enterprise-ID delimited option
+   RFC3925 [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' or 'who and what am I'), and a means to
    deliver vendor-specific and vendor-documented option codes and
    values.
 
-   RFC3942 [31] redefined the 'site local' option space.
+   RFC3942 [RFC3942] redefined the 'site local' option space.
 
-   RFC4075 [32] defines the DHCPv6 SNTP Servers option.
+   RFC4075 [RFC4075] defines the DHCPv6 SNTP Servers option.
 
-   RFC4242 [33] defines the Information Refresh Time option, which
+   RFC4242 [RFC4242] defines the Information Refresh Time option, which
    advises DHCPv6 Information-Request clients to return for updated
    information.
 
-   RFC4280 [34] defines two BCMS server options.
+   RFC4280 [RFC4280] defines two BCMS server options.
 
-   RFC4388 [35] 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.
 
 
 
 Hankins                                                         [Page 9]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
-   RFC4580> [36] defines a DHCPv6 subscriber-id option, which is similar
-   in principle to the DHCPv4 relay agent option of the same name.
+   RFC4388 [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.
 
-   RFC4649 [37] defines a DHCPv6 remote-id option, which is similar in
-   principle to the DHCPv4 relay agent remote-id.
+   RFC4580 [RFC4580] defines a DHCPv6 subscriber-id option, which is
+   similar in principle to the DHCPv4 relay agent option of the same
+   name.
+
+   RFC4649 [RFC4649] defines a DHCPv6 remote-id option, which is similar
+   in principle to the DHCPv4 relay agent remote-id.
 
 5.3.1.  Relay Agent Information Option Options
 
-   RFC3046 [18] defines the Relay Agent Information Option and provides
-   a number of sub-option definitions.
+   RFC3046 [RFC3046] defines the Relay Agent Information Option and
+   provides a number of sub-option definitions.
 
-   RFC3256 [20] defines the DOCSIS Device Class sub-option.
+   RFC3256 [RFC3256] defines the DOCSIS Device Class sub-option.
 
-   RFC3527 [25] defines the Link Selection sub-option.
+   RFC3527 [RFC3527] defines the Link Selection sub-option.
 
 5.3.2.  Dynamic DNS Updates References
 
    The collection of documents that describe the standards-based method
    to update dns names of DHCP clients starts most easily with RFC4703
-   [40] to define the overall architecture, travels through RFCs 4702
-   [39] and 4704 [41] to describe the DHCPv4 and DHCPv6 FQDN options (to
-   carry the client name), and ends up at RFC4701 [38] which describes
-   the DHCID RR used in DNS to perform a kind of atomic locking.
+   [RFC4703] to define the overall architecture, travels through RFCs
+   4702 [RFC4702] and 4704 [RFC4704] to describe the DHCPv4 and DHCPv6
+   FQDN options (to carry the client name), and ends up at RFC4701
+   [RFC4701] which describes the DHCID RR used in DNS to perform a kind
+   of atomic locking.
 
    ISC DHCP adoped early versions of these documents, and has not yet
    synched up with the final standards versions.
@@ -547,20 +553,20 @@ Hankins                                                         [Page 9]
    Rather, all values for such TXT records are reached via an MD5 sum.
    In short, nothing is compatible, but the principle of the TXT record
    is the same as the standard DHCID record.  However, for DHCPv6 FQDN,
-   we do use DHCID type code '2', as no other value really makes sense
-   in our context.
-
-5.3.3.  Experimental: Failover References
-
-   The Failover Protocol defines a means by which two DHCP Servers can
 
 
 
 Hankins                                                        [Page 10]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
+   we do use DHCID type code '2', as no other value really makes sense
+   in our context.
+
+5.3.3.  Experimental: Failover References
+
+   The Failover Protocol defines a 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.
@@ -573,216 +579,214 @@ Hankins                                                        [Page 10]
    of it has proven stable and suitable for use in sizable production
    environments.
 
-   draft-ietf-dhc-failover-12.txt [42] describes the Failover Protocol.
-   In addition to what is described in this document, ISC DHCP has
-   elected to make some experimental changes that may be revoked in a
-   future version of ISC DHCP (if the draft authors do not adopt the new
-   behaviour).  Specifically, ISC DHCP's POOLREQ behaviour differs
-   substantially from what is documented in the draft, and the server
-   also implements a form of 'MAC Address Affinity' which is not
-   described in the failover document.  The full nature of these changes
-   have been described on the IETF DHC WG mailing list (which has
-   archives), and also in ISC DHCP's manual pages.  Also note that
+   draft-ietf-dhc-failover-12.txt [draft-failover] describes the
+   Failover Protocol.  In addition to what is described in this
+   document, ISC DHCP has elected to make some experimental changes that
+   may be revoked in a future version of ISC DHCP (if the draft authors
+   do not adopt the new behaviour).  Specifically, ISC DHCP's POOLREQ
+   behaviour differs substantially from what is documented in the draft,
+   and the server also implements a form of 'MAC Address Affinity' which
+   is not described in the failover document.  The full nature of these
+   changes have been described on the IETF DHC WG mailing list (which
+   has archives), and also in ISC DHCP's manual pages.  Also note that
    although this document references a RECOVER-WAIT state, it does not
    document a protocol number assignment for this state.  As a
    consequence, ISC DHCP has elected to use the value 254.
 
-   RFC3074 [19] 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).
+   RFC3074 [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 the hash bucket array).
 
 5.4.  DHCP Procedures
 
-   RFC2939 [15] explains how to go about obtaining a new DHCP Option
-   code assignment.
-
-6.  References
+   RFC2939 [RFC2939] explains how to go about obtaining a new DHCP
+   Option code assignment.
 
-   [1]   Postel, J., "DoD standard Internet Protocol", RFC 760,
-         January 1980.
 
-   [2]   Postel, J., "User Datagram Protocol", STD 6, RFC 768,
-         August 1980.
+6.  References
 
-   [3]   Hornig, C., "Standard for the transmission of IP datagrams over
-         Ethernet networks", STD 41, RFC 894, April 1984.
+   [RFC0760]  Postel, J., "DoD standard Internet Protocol", RFC 760,
+              January 1980.
 
-   [4]   Croft, B. and J. Gilmore, "Bootstrap Protocol", RFC 951,
 
 
 
 Hankins                                                        [Page 11]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
 
 
-         September 1985.
+   [RFC0768]  Postel, J., "User Datagram Protocol", STD 6, RFC 768,
+              August 1980.
 
-   [5]   Mockapetris, P., "Domain names - implementation and
-         specification", STD 13, RFC 1035, November 1987.
+   [RFC0894]  Hornig, C., "Standard for the transmission of IP datagrams
+              over Ethernet networks", STD 41, RFC 894, April 1984.
 
-   [6]   Katz, D., "Proposed Standard for the Transmission of IP
-         Datagrams over FDDI Networks", RFC 1188, October 1990.
+   [RFC0951]  Croft, B. and J. Gilmore, "Bootstrap Protocol", RFC 951,
+              September 1985.
 
-   [7]   Wimer, W., "Clarifications and Extensions for the Bootstrap
-         Protocol", RFC 1542, October 1993.
+   [RFC1035]  Mockapetris, P., "Domain names - implementation and
+              specification", STD 13, RFC 1035, November 1987.
 
-   [8]   Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
-         March 1997.
+   [RFC1188]  Katz, D., "Proposed Standard for the Transmission of IP
+              Datagrams over FDDI Networks", RFC 1188, October 1990.
 
-   [9]   Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
-         Extensions", RFC 2132, March 1997.
+   [RFC1542]  Wimer, W., "Clarifications and Extensions for the
+              Bootstrap Protocol", RFC 1542, October 1993.
 
-   [10]  Provan, D., "DHCP Options for Novell Directory Services",
-         RFC 2241, November 1997.
+   [RFC2131]  Droms, R., "Dynamic Host Configuration Protocol",
+              RFC 2131, March 1997.
 
-   [11]  Droms, R. and K. Fong, "NetWare/IP Domain Name and
-         Information", RFC 2242, November 1997.
+   [RFC2132]  Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
+              Extensions", RFC 2132, March 1997.
 
-   [12]  Drach, S., "DHCP Option for The Open Group's User
-         Authentication Protocol", RFC 2485, January 1999.
+   [RFC2241]  Provan, D., "DHCP Options for Novell Directory Services",
+              RFC 2241, November 1997.
 
-   [13]  Perkins, C. and E. Guttman, "DHCP Options for Service Location
-         Protocol", RFC 2610, June 1999.
+   [RFC2242]  Droms, R. and K. Fong, "NetWare/IP Domain Name and
+              Information", RFC 2242, November 1997.
 
-   [14]  Smith, C., "The Name Service Search Option for DHCP", RFC 2937,
-         September 2000.
+   [RFC2485]  Drach, S., "DHCP Option for The Open Group's User
+              Authentication Protocol", RFC 2485, January 1999.
 
-   [15]  Droms, R., "Procedures and IANA Guidelines for Definition of
-         New DHCP Options and Message Types", BCP 43, RFC 2939,
-         September 2000.
+   [RFC2610]  Perkins, C. and E. Guttman, "DHCP Options for Service
+              Location Protocol", RFC 2610, June 1999.
 
-   [16]  Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A.,
-         Beser, B., and J. Privat, "The User Class Option for DHCP",
-         RFC 3004, November 2000.
+   [RFC2937]  Smith, C., "The Name Service Search Option for DHCP",
+              RFC 2937, September 2000.
 
-   [17]  Waters, G., "The IPv4 Subnet Selection Option for DHCP",
-         RFC 3011, November 2000.
+   [RFC2939]  Droms, R., "Procedures and IANA Guidelines for Definition
+              of New DHCP Options and Message Types", BCP 43, RFC 2939,
+              September 2000.
 
-   [18]  Patrick, M., "DHCP Relay Agent Information Option", RFC 3046,
-         January 2001.
+   [RFC3004]  Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis,
+              A., Beser, B., and J. Privat, "The User Class Option for
+              DHCP", RFC 3004, November 2000.
 
-   [19]  Volz, B., Gonczi, S., Lemon, T., and R. Stevens, "DHC Load
-         Balancing Algorithm", RFC 3074, February 2001.
+   [RFC3011]  Waters, G., "The IPv4 Subnet Selection Option for DHCP",
 
 
 
 Hankins                                                        [Page 12]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
+
 
+              RFC 3011, November 2000.
 
-   [20]  Jones, D. and R. Woundy, "The DOCSIS (Data-Over-Cable Service
-         Interface Specifications) Device Class DHCP (Dynamic Host
-         Configuration Protocol) Relay Agent Information Sub-option",
-         RFC 3256, April 2002.
+   [RFC3046]  Patrick, M., "DHCP Relay Agent Information Option",
+              RFC 3046, January 2001.
 
-   [21]  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.
-         Carney, "Dynamic Host Configuration Protocol for IPv6
-         (DHCPv6)", RFC 3315, July 2003.
+   [RFC3074]  Volz, B., Gonczi, S., Lemon, T., and R. Stevens, "DHC Load
+              Balancing Algorithm", RFC 3074, February 2001.
 
-   [22]  Schulzrinne, H. and B. Volz, "Dynamic Host Configuration
-         Protocol (DHCPv6) Options for Session Initiation Protocol (SIP)
-         Servers", RFC 3319, July 2003.
+   [RFC3256]  Jones, D. and R. Woundy, "The DOCSIS (Data-Over-Cable
+              Service Interface Specifications) Device Class DHCP
+              (Dynamic Host Configuration Protocol) Relay Agent
+              Information Sub-option", RFC 3256, April 2002.
 
-   [23]  Lemon, T. and S. Cheshire, "Encoding Long Options in the
-         Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396,
-         November 2002.
+   [RFC3315]  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
+              and M. Carney, "Dynamic Host Configuration Protocol for
+              IPv6 (DHCPv6)", RFC 3315, July 2003.
 
-   [24]  Aboba, B. and S. Cheshire, "Dynamic Host Configuration Protocol
-         (DHCP) Domain Search Option", RFC 3397, November 2002.
+   [RFC3319]  Schulzrinne, H. and B. Volz, "Dynamic Host Configuration
+              Protocol (DHCPv6) Options for Session Initiation Protocol
+              (SIP) Servers", RFC 3319, July 2003.
 
-   [25]  Kinnear, K., Stapp, M., Johnson, R., and J. Kumarasamy, "Link
-         Selection sub-option for the Relay Agent Information Option for
-         DHCPv4", RFC 3527, April 2003.
+   [RFC3396]  Lemon, T. and S. Cheshire, "Encoding Long Options in the
+              Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396,
+              November 2002.
 
-   [26]  Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host
-         Configuration Protocol (DHCP) version 6", RFC 3633,
-         December 2003.
+   [RFC3397]  Aboba, B. and S. Cheshire, "Dynamic Host Configuration
+              Protocol (DHCP) Domain Search Option", RFC 3397,
+              November 2002.
 
-   [27]  Droms, R., "DNS Configuration options for Dynamic Host
-         Configuration Protocol for IPv6 (DHCPv6)", RFC 3646,
-         December 2003.
+   [RFC3527]  Kinnear, K., Stapp, M., Johnson, R., and J. Kumarasamy,
+              "Link Selection sub-option for the Relay Agent Information
+              Option for DHCPv4", RFC 3527, April 2003.
 
-   [28]  Droms, R., "Unused Dynamic Host Configuration Protocol (DHCP)
-         Option Codes", RFC 3679, January 2004.
+   [RFC3633]  Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
+              Host Configuration Protocol (DHCP) version 6", RFC 3633,
+              December 2003.
 
-   [29]  Kalusivalingam, V., "Network Information Service (NIS)
-         Configuration Options for Dynamic Host Configuration Protocol
-         for IPv6 (DHCPv6)", RFC 3898, October 2004.
+   [RFC3646]  Droms, R., "DNS Configuration options for Dynamic Host
+              Configuration Protocol for IPv6 (DHCPv6)", RFC 3646,
+              December 2003.
 
-   [30]  Littlefield, J., "Vendor-Identifying Vendor Options for Dynamic
-         Host Configuration Protocol version 4 (DHCPv4)", RFC 3925,
-         October 2004.
+   [RFC3679]  Droms, R., "Unused Dynamic Host Configuration Protocol
+              (DHCP) Option Codes", RFC 3679, January 2004.
 
-   [31]  Volz, B., "Reclassifying Dynamic Host Configuration Protocol
-         version 4 (DHCPv4) Options", RFC 3942, November 2004.
+   [RFC3898]  Kalusivalingam, V., "Network Information Service (NIS)
+              Configuration Options for Dynamic Host Configuration
+              Protocol for IPv6 (DHCPv6)", RFC 3898, October 2004.
 
-   [32]  Kalusivalingam, V., "Simple Network Time Protocol (SNTP)
-         Configuration Option for DHCPv6", RFC 4075, May 2005.
 
 
 
 Hankins                                                        [Page 13]
 
-                     ISC DHCP References Collection          August 2006
-
-
-   [33]  Venaas, S., Chown, T., and B. Volz, "Information Refresh Time
-         Option for Dynamic Host Configuration Protocol for IPv6
-         (DHCPv6)", RFC 4242, November 2005.
-
-   [34]  Chowdhury, K., Yegani, P., and L. Madour, "Dynamic Host
-         Configuration Protocol (DHCP) Options for Broadcast and
-         Multicast Control Servers", RFC 4280, November 2005.
-
-   [35]  Woundy, R. and K. Kinnear, "Dynamic Host Configuration Protocol
-         (DHCP) Leasequery", RFC 4388, February 2006.
-
-   [36]  Volz, B., "Dynamic Host Configuration Protocol for IPv6
-         (DHCPv6) Relay Agent Subscriber-ID Option", RFC 4580,
-         June 2006.
-
-   [37]  Volz, B., "Dynamic Host Configuration Protocol for IPv6
-         (DHCPv6) Relay Agent Remote-ID Option", RFC 4649, August 2006.
+                     ISC DHCP References Collection             May 2007
 
-   [38]  Stapp, M., Lemon, T., and A. Gustafsson, "A DNS Resource Record
-         (RR) for Encoding Dynamic Host Configuration Protocol (DHCP)
-         Information (DHCID RR)", RFC 4701, October 2006.
-
-   [39]  Stapp, M., Volz, B., and Y. Rekhter, "The Dynamic Host
-         Configuration Protocol (DHCP) Client Fully Qualified Domain
-         Name (FQDN) Option", RFC 4702, October 2006.
-
-   [40]  Stapp, M. and B. Volz, "Resolution of Fully Qualified Domain
-         Name (FQDN) Conflicts among Dynamic Host Configuration Protocol
-         (DHCP) Clients", RFC 4703, October 2006.
-
-   [41]  Volz, B., "The Dynamic Host Configuration Protocol for IPv6
-         (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option",
-         RFC 4704, October 2006.
-
-   [42]  Droms, R., "DHCP Failover Protocol", March 2003.
 
+   [RFC3925]  Littlefield, J., "Vendor-Identifying Vendor Options for
+              Dynamic Host Configuration Protocol version 4 (DHCPv4)",
+              RFC 3925, October 2004.
 
+   [RFC3942]  Volz, B., "Reclassifying Dynamic Host Configuration
+              Protocol version 4 (DHCPv4) Options", RFC 3942,
+              November 2004.
 
+   [RFC4075]  Kalusivalingam, V., "Simple Network Time Protocol (SNTP)
+              Configuration Option for DHCPv6", RFC 4075, May 2005.
 
+   [RFC4242]  Venaas, S., Chown, T., and B. Volz, "Information Refresh
+              Time Option for Dynamic Host Configuration Protocol for
+              IPv6 (DHCPv6)", RFC 4242, November 2005.
 
+   [RFC4280]  Chowdhury, K., Yegani, P., and L. Madour, "Dynamic Host
+              Configuration Protocol (DHCP) Options for Broadcast and
+              Multicast Control Servers", RFC 4280, November 2005.
 
+   [RFC4388]  Woundy, R. and K. Kinnear, "Dynamic Host Configuration
+              Protocol (DHCP) Leasequery", RFC 4388, February 2006.
 
+   [RFC4580]  Volz, B., "Dynamic Host Configuration Protocol for IPv6
+              (DHCPv6) Relay Agent Subscriber-ID Option", RFC 4580,
+              June 2006.
 
+   [RFC4649]  Volz, B., "Dynamic Host Configuration Protocol for IPv6
+              (DHCPv6) Relay Agent Remote-ID Option", RFC 4649,
+              August 2006.
 
+   [RFC4701]  Stapp, M., Lemon, T., and A. Gustafsson, "A DNS Resource
+              Record (RR) for Encoding Dynamic Host Configuration
+              Protocol (DHCP) Information (DHCID RR)", RFC 4701,
+              October 2006.
 
+   [RFC4702]  Stapp, M., Volz, B., and Y. Rekhter, "The Dynamic Host
+              Configuration Protocol (DHCP) Client Fully Qualified
+              Domain Name (FQDN) Option", RFC 4702, October 2006.
 
+   [RFC4703]  Stapp, M. and B. Volz, "Resolution of Fully Qualified
+              Domain Name (FQDN) Conflicts among Dynamic Host
+              Configuration Protocol (DHCP) Clients", RFC 4703,
+              October 2006.
 
+   [RFC4704]  Volz, B., "The Dynamic Host Configuration Protocol for
+              IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN)
+              Option", RFC 4704, October 2006.
 
 
 
 
 Hankins                                                        [Page 14]
 
-                     ISC DHCP References Collection          August 2006
+                     ISC DHCP References Collection             May 2007
+
+
+   [draft-failover]
+              Droms, R., "DHCP Failover Protocol", March 2003.
 
 
 Author's Address
@@ -832,9 +836,5 @@ Author's Address
 
 
 
-
-
-
-
 Hankins                                                        [Page 15]