for new web site as appropirate.
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
ISC DHCP, more information about ISC Support Contracts can be found at
the following URL:
- http://www.isc.org/sw/support/
+ https://www.isc.org/services/support/
Please understand that we may not respond to support inquiries unless
you have a support contract. ISC will continue its practice of always
This assumes that it's the dhcp server you're debugging, and
that the core file is in dhcpd.core.
-Please see http://www.isc.org/sw/dhcp/ for details on how to subscribe
+Please see https://www.isc.org/software/dhcp/ for details on how to subscribe
to the ISC DHCP mailing lists.
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#include "dhcpd.h"
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
-.\" $Id: dhclient-script.8,v 1.11 2006/02/24 23:16:27 dhankins Exp $
+.\" $Id: dhclient-script.8,v 1.12 2009/07/23 18:52:19 sar Exp $
.\"
.TH dhclient-script 8
.SH NAME
by Ted Lemon in cooperation with Vixie
Enterprises. To learn more about Internet Systems Consortium,
see
-.B http://www.isc.org.
+.B https://www.isc.org.
To learn more about Vixie
Enterprises, see
.B http://www.vix.com.
-.\" $Id: dhclient.8,v 1.31 2009/05/27 20:11:38 pselkirk Exp $
+.\" $Id: dhclient.8,v 1.32 2009/07/23 18:52:19 sar Exp $
.\"
.\" Copyright (c) 2004,2007-2008 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" Support and other services are available for ISC products - see
-.\" http://www.isc.org for more information.
+.\" https://www.isc.org for more information.
.\"
.TH dhclient 8
.SH NAME
by Ted Lemon in cooperation with Vixie
Enterprises. To learn more about Internet Systems Consortium,
see
-.B http://www.isc.org
+.B https://www.isc.org
To learn more about Vixie
Enterprises, see
.B http://www.vix.com.
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This code is based on the original client state machine that was
* written by Elliot Poger. The code has been extensively hacked on
static const char copyright[] = "Copyright 2004-2009 Internet Systems Consortium.";
static const char arr [] = "All rights reserved.";
static const char message [] = "Internet Systems Consortium DHCP Client";
-static const char url [] = "For info, please visit http://www.isc.org/sw/dhcp/";
+static const char url [] = "For info, please visit https://www.isc.org/software/dhcp/";
u_int16_t local_port = 0;
u_int16_t remote_port = 0;
-.\" $Id: dhclient.conf.5,v 1.24 2009/03/13 21:41:45 dhankins Exp $
+.\" $Id: dhclient.conf.5,v 1.25 2009/07/23 18:52:19 sar Exp $
.\"
.\" Copyright (c) 2004,2007 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Software Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Software Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
under a contract with Vixie Labs. Funding
for this project was provided by Internet Systems Consortium.
Information about Internet Systems Consortium can be found at
-.B http://www.isc.org.
+.B https://www.isc.org.
-.\" $Id: dhclient.leases.5,v 1.4 2005/03/17 20:14:56 dhankins Exp $
+.\" $Id: dhclient.leases.5,v 1.5 2009/07/23 18:52:19 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1997-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie
.\" Enterprises. To learn more about Internet Systems Consortium,
-.\" see ``http://www.isc.org/isc''. To learn more about Vixie
+.\" see ``https://www.isc.org/''. To learn more about Vixie
.\" Enterprises, see ``http://www.vix.com''.
.\"
-.\" $Id: dhclient.leases.5,v 1.4 2005/03/17 20:14:56 dhankins Exp $
+.\" $Id: dhclient.leases.5,v 1.5 2009/07/23 18:52:19 sar Exp $
.\"
.TH dhclient.leases 5
.SH NAME
under a contract with Vixie Labs. Funding
for this project was provided by Internet Systems Consortium.
Information about Internet Systems Consortium can be found at
-.B http://www.isc.org.
+.B https://www.isc.org.
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software was contributed to Internet Systems Consortium
* by Archie Cobbs.
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon, as part of a project for Nominum, Inc. To learn more
- * about Internet Systems Consortium, see http://www.isc.org/. To
+ * about Internet Systems Consortium, see https://www.isc.org/. To
* learn more about Nominum, Inc., see ``http://www.nominum.com''.
*/
-.\" $Id: dhcp-eval.5,v 1.28 2009/07/06 23:29:51 dhankins Exp $
+.\" $Id: dhcp-eval.5,v 1.29 2009/07/23 18:52:19 sar Exp $
.\"
.\" Copyright (c) 2004,2007 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.TH dhcp-eval 5
Lemon under a contract with Vixie Labs. Funding for
this project was provided through Internet Systems Consortium.
Information about Internet Systems Consortium can be found at
-.B http://www.isc.org.
+.B https://www.isc.org.
-.\" $Id: dhcp-options.5,v 1.43 2008/11/21 13:59:56 jreed Exp $
+.\" $Id: dhcp-options.5,v 1.44 2009/07/23 18:52:19 sar Exp $
.\"
.\" Copyright (c) 2004-2008 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.TH dhcpd-options 5
Lemon under a contract with Vixie Labs. Funding for
this project was provided through Internet Systems Consortium.
Information about Internet Systems Consortium can be found at
-.B http://www.isc.org.
+.B https://www.isc.org.
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software was written for Internet Systems Consortium
* by Eric James Negaard, <lmdejn@lmd.ericsson.se>. To learn more about
- * Internet Systems Consortium, see ``http://www.isc.org''.
+ * Internet Systems Consortium, see ``https://www.isc.org''.
*
* Joost Mulders has also done considerable work in debugging the DLPI API
* support on Solaris and getting this code to work properly on a variety
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Nominum, Inc., see
+ * ``https://www.isc.org/''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#include "dhcpd.h"
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This code was originally contributed by Archie Cobbs, and is still
* very similar to that contribution, although the packet checksum code
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#include "dhcpd.h"
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software was contributed to Internet Systems Consortium
* by Brian Murrell.
.\"
.\" Project: DHCP
.\" File: dhcpctl.3
-.\" RCSId: $Id: dhcpctl.3,v 1.6 2008/11/19 01:25:13 sar Exp $
+.\" RCSId: $Id: dhcpctl.3,v 1.7 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 2000-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" Description: dhcpctl man page.
.\"
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
-/* $Id: dhcpctl.h,v 1.16 2005/03/17 20:15:03 dhankins Exp $
+/* $Id: dhcpctl.h,v 1.17 2009/07/23 18:52:20 sar Exp $
Subroutines providing general support for objects. */
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
-.\" $Id: omshell.1,v 1.4 2006/07/13 00:52:10 dhankins Exp $
+.\" $Id: omshell.1,v 1.5 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 2001-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.TH omshell 1
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
all: References.txt References.html
<!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="Fri, 13 Apr 2007 18:37:11 +0000">
+<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.30 (http://xml.resource.org/)">
-<style type='text/css'>
-<!--
- body {
- font-family: verdana, charcoal, helvetica, arial, sans-serif;
- margin: 2em;
- font-size: small ; color: #000000 ; background-color: #ffffff ; }
- .title { color: #990000; font-size: x-large ;
- font-weight: bold; text-align: right;
- font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
- background-color: transparent; }
- .filename { color: #666666; font-size: 18px; line-height: 28px;
- font-weight: bold; text-align: right;
- font-family: helvetica, arial, sans-serif;
- background-color: transparent; }
- td.rfcbug { background-color: #000000 ; width: 30px ; height: 30px ;
- text-align: justify; vertical-align: middle ; padding-top: 2px ; }
- td.rfcbug span.RFC { color: #666666; font-weight: bold; text-decoration: none;
- background-color: #000000 ;
- font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
- font-size: x-small ; }
- td.rfcbug span.hotText { color: #ffffff; font-weight: normal; text-decoration: none;
- text-align: center ;
- font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
- font-size: x-small ; background-color: #000000; }
- /* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
- div#counter{margin-top: 100px}
-
- a.info{
- position:relative; /*this is the key*/
- z-index:24;
- text-decoration:none}
-
- a.info:hover{z-index:25; background-color:#990000 ; color: #ffffff ;}
-
- a.info span{display: none}
-
- a.info:hover span.info{ /*the span will display just on :hover state*/
- display:block;
- position:absolute;
- font-size: smaller ;
- top:2em; left:2em; width:15em;
- padding: 2px ;
- border:1px solid #333333;
- background-color:#eeeeee; color:#990000;
- text-align: left ;}
-
- A { font-weight: bold; }
- A:link { color: #990000; background-color: transparent ; }
- A:visited { color: #333333; background-color: transparent ; }
- A:active { color: #333333; background-color: transparent ; }
-
- p { margin-left: 2em; margin-right: 2em; }
- p.copyright { font-size: x-small ; }
- p.toc { font-size: small ; font-weight: bold ; margin-left: 3em ;}
- table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
- td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
-
- span.emph { font-style: italic; }
- span.strong { font-weight: bold; }
- span.verb, span.vbare { font-family: "Courier New", Courier, monospace ; }
-
- span.vemph { font-style: italic; font-family: "Courier New", Courier, monospace ; }
- span.vstrong { font-weight: bold; font-family: "Courier New", Courier, monospace ; }
- span.vdeluxe { font-weight: bold; font-style: italic; font-family: "Courier New", Courier, monospace ; }
-
- ol.text { margin-left: 2em; margin-right: 2em; }
- ul.text { margin-left: 2em; margin-right: 2em; }
- li { margin-left: 3em; }
-
- pre { margin-left: 3em; color: #333333; background-color: transparent;
- font-family: "Courier New", Courier, monospace ; font-size: small ;
- text-align: left;
+<meta name="generator" content="xml2rfc v1.33 (http://xml.resource.org/)">
+<style type='text/css'><!--
+ body {
+ font-family: verdana, charcoal, helvetica, arial, sans-serif;
+ font-size: small; color: #000; background-color: #FFF;
+ margin: 2em;
+ }
+ h1, h2, h3, h4, h5, h6 {
+ font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
+ font-weight: bold; font-style: normal;
+ }
+ h1 { color: #900; background-color: transparent; text-align: right; }
+ h3 { color: #333; background-color: transparent; }
+
+ td.RFCbug {
+ font-size: x-small; text-decoration: none;
+ width: 30px; height: 30px; padding-top: 2px;
+ text-align: justify; vertical-align: middle;
+ background-color: #000;
+ }
+ td.RFCbug span.RFC {
+ font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
+ font-weight: bold; color: #666;
+ }
+ td.RFCbug span.hotText {
+ font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
+ font-weight: normal; text-align: center; color: #FFF;
+ }
+
+ table.TOCbug { width: 30px; height: 15px; }
+ td.TOCbug {
+ text-align: center; width: 30px; height: 15px;
+ color: #FFF; background-color: #900;
+ }
+ td.TOCbug a {
+ font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
+ font-weight: bold; font-size: x-small; text-decoration: none;
+ color: #FFF; background-color: transparent;
}
- h3 { color: #333333; font-size: medium ;
- font-family: helvetica, arial, sans-serif ;
- background-color: transparent; }
- h4 { font-size: small; font-family: helvetica, arial, sans-serif ; }
-
- table.bug { width: 30px ; height: 15px ; }
- td.bug { color: #ffffff ; background-color: #990000 ;
- text-align: center ; width: 30px ; height: 15px ;
- }
- td.bug A.link2 { color: #ffffff ; font-weight: bold;
- text-decoration: none;
- font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
- font-size: x-small ; background-color: transparent }
-
- td.header { color: #ffffff; font-size: x-small ;
- font-family: arial, helvetica, sans-serif; vertical-align: top;
- background-color: #666666 ; width: 33% ; }
- td.author { font-weight: bold; margin-left: 4em; font-size: x-small ; }
- td.author-text { font-size: x-small; }
- table.full { vertical-align: top ; border-collapse: collapse ;
- border-style: solid solid solid solid ;
- border-color: black black black black ;
- font-size: small ; text-align: center ; }
- table.headers, table.none { vertical-align: top ; border-collapse: collapse ;
- border-style: none;
- font-size: small ; text-align: center ; }
- table.full th { font-weight: bold ;
- border-style: solid ;
- border-color: black black black black ; }
- table.headers th { font-weight: bold ;
- border-style: none none solid none;
- border-color: black black black black ; }
- table.none th { font-weight: bold ;
- border-style: none; }
- table.full td {
- border-style: solid solid solid solid ;
- border-color: #333333 #333333 #333333 #333333 ; }
- table.headers td, table.none td { border-style: none; }
-
- hr { height: 1px }
--->
-</style>
+ td.header {
+ font-family: arial, helvetica, sans-serif; font-size: x-small;
+ vertical-align: top; width: 33%;
+ color: #FFF; background-color: #666;
+ }
+ td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
+ td.author-text { font-size: x-small; }
+
+ /* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
+ a.info {
+ /* This is the key. */
+ position: relative;
+ z-index: 24;
+ text-decoration: none;
+ }
+ a.info:hover {
+ z-index: 25;
+ color: #FFF; background-color: #900;
+ }
+ a.info span { display: none; }
+ a.info:hover span.info {
+ /* The span will display just on :hover state. */
+ display: block;
+ position: absolute;
+ font-size: smaller;
+ top: 2em; left: -5em; width: 15em;
+ padding: 2px; border: 1px solid #333;
+ color: #900; background-color: #EEE;
+ text-align: left;
+ }
+
+ a { font-weight: bold; }
+ a:link { color: #900; background-color: transparent; }
+ a:visited { color: #633; background-color: transparent; }
+ a:active { color: #633; background-color: transparent; }
+
+ p { margin-left: 2em; margin-right: 2em; }
+ p.copyright { font-size: x-small; }
+ p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
+ table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
+ td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
+
+ ol.text { margin-left: 2em; margin-right: 2em; }
+ ul.text { margin-left: 2em; margin-right: 2em; }
+ li { margin-left: 3em; }
+
+ /* RFC-2629 <spanx>s and <artwork>s. */
+ em { font-style: italic; }
+ strong { font-weight: bold; }
+ dfn { font-weight: bold; font-style: normal; }
+ cite { font-weight: normal; font-style: normal; }
+ tt { color: #036; }
+ tt, pre, pre dfn, pre em, pre cite, pre span {
+ font-family: "Courier New", Courier, monospace; font-size: small;
+ }
+ pre {
+ text-align: left; padding: 4px;
+ color: #000; background-color: #CCC;
+ }
+ pre dfn { color: #900; }
+ pre em { color: #66F; background-color: #FFC; font-weight: normal; }
+ pre .key { color: #33C; font-weight: bold; }
+ pre .id { color: #900; }
+ pre .str { color: #000; background-color: #CFF; }
+ pre .val { color: #066; }
+ pre .rep { color: #909; }
+ pre .oth { color: #000; background-color: #FCF; }
+ pre .err { background-color: #FCC; }
+
+ /* RFC-2629 <texttable>s. */
+ table.all, table.full, table.headers, table.none {
+ font-size: small; text-align: center; border-width: 2px;
+ vertical-align: top; border-collapse: collapse;
+ }
+ table.all, table.full { border-style: solid; border-color: black; }
+ table.headers, table.none { border-style: none; }
+ th {
+ font-weight: bold; border-color: black;
+ border-width: 2px 2px 3px 2px;
+ }
+ table.all th, table.full th { border-style: solid; }
+ table.headers th { border-style: none none solid none; }
+ table.none th { border-style: none; }
+ table.all td {
+ border-style: solid; border-color: #333;
+ border-width: 1px 2px;
+ }
+ table.full td, table.headers td, table.none td { border-style: none; }
+
+ hr { height: 1px; }
+ hr.insert {
+ width: 80%; border-style: none; border-width: 0;
+ color: #CCC; background-color: #CCC;
+ }
+--></style>
</head>
<body>
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
+<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">ISC</td></tr>
-<tr><td class="header"> </td><td class="header">August 2006</td></tr>
+<tr><td class="header"> </td><td class="header">May 2007</td></tr>
</table></td></tr></table>
-<div align="right"><span class="title"><br />ISC DHCP References Collection</span></div>
+<h1><br />ISC DHCP References Collection</h1>
<h3>Copyright Notice</h3>
-<p>Copyright (c) 2006-2007 by Internet Systems Consortium, Inc.
+<p>Copyright (c) 2006-2007,2009 by Internet Systems Consortium, Inc.
("ISC")
</p>
<p>Permission to use, copy, modify, and distribute this software for
<br clear="all" />
<a name="anchor1"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.1"></a><h3>1. Introduction</h3>
+<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.1"></a><h3>1.
+Introduction</h3>
<p>As a little historical anecdote, ISC DHCP once packaged all the
relevant RFCs and standards documents along with the software
managed to implement them.
</p>
<a name="anchor2"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.2"></a><h3>2. Definition: Reference Implementation</h3>
+<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.2"></a><h3>2.
+Definition: Reference Implementation</h3>
<p>ISC DHCP, much like its other cousins in ISC software, is
self-described as a 'Reference Implementation.' There has been
on the Internet with the will to participate has a say.
</p>
<a name="anchor3"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.3"></a><h3>3. Low Layer References</h3>
+<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.3"></a><h3>3.
+Low Layer References</h3>
<p>It may surprise you to realize that ISC DHCP implements 802.1
'Ethernet' framing, Token Ring, and FDDI. In order to bridge the
</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> [8].
+ 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>
<ol class="text">
<li>Transmit a UDP packet from IP:0.0.0.0 Ethernet:Self, destined to
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> [8] very explicitly demands that these packets' IP
+ 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.
</p>
<p>Receiving packets sent to 255.255.255.255 isn't a problem on most
address has been configured, unless it is done with raw sockets.
</p>
<a name="anchor4"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.3.1"></a><h3>3.1. Ethernet Protocol References</h3>
+<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.3.1"></a><h3>3.1.
+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> [3] (see the section titled "Packet format"), and
+ 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
the following URL is also thought to be useful.
</p>
<p>http://en.wikipedia.org/wiki/DIX
</p>
<a name="anchor5"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.3.2"></a><h3>3.2. Token Ring Protocol References</h3>
+<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.3.2"></a><h3>3.2.
+Token Ring Protocol References</h3>
<p>IEEE 802.5 defines the Token Ring framing format used by ISC
DHCP.
</p>
<a name="anchor6"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.3.3"></a><h3>3.3. FDDI Protocol References</h3>
+<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.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> [6] 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> [RFC1188] is the most helpful
reference ISC DHCP has used to form FDDI packets.
</p>
<a name="anchor7"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.3.4"></a><h3>3.4. Internet Protocol Version 4 References</h3>
+<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.3.4"></a><h3>3.4.
+Internet Protocol Version 4 References</h3>
-<p><a class="info" href="#RFC0760">RFC760<span> (</span><span class="info">Postel, J., “DoD standard Internet Protocol,” January 1980.</span><span>)</span></a> [1] fundamentally defines the
+<p><a class='info' href='#RFC0760'>RFC760<span> (</span><span class='info'>Postel, J., “DoD standard Internet Protocol,” January 1980.</span><span>)</span></a> [RFC0760] fundamentally defines the
bare IPv4 protocol which ISC DHCP implements.
</p>
<a name="anchor8"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.3.5"></a><h3>3.5. Unicast Datagram Protocol References</h3>
+<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.3.5"></a><h3>3.5.
+Unicast Datagram Protocol References</h3>
-<p><a class="info" href="#RFC0768">RFC768<span> (</span><span class="info">Postel, J., “User Datagram Protocol,” August 1980.</span><span>)</span></a> [2] defines the User Datagram
+<p><a class='info' href='#RFC0768'>RFC768<span> (</span><span class='info'>Postel, J., “User Datagram Protocol,” August 1980.</span><span>)</span></a> [RFC0768] defines the User Datagram
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.
</p>
<a name="anchor9"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.4"></a><h3>4. BOOTP Protocol References</h3>
+<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.4"></a><h3>4.
+BOOTP Protocol References</h3>
<p>The DHCP Protocol is strange among protocols in that it is
grafted over the top of another protocol - BOOTP (but we don't
use of both BOOTP header fields and the trailing 'options' space.
</p>
<p>The ISC DHCP server supports BOOTP clients conforming to
- <a class="info" href="#RFC0951">RFC951<span> (</span><span class="info">Croft, B. and J. Gilmore, “Bootstrap Protocol,” September 1985.</span><span>)</span></a> [4] and <a class="info" href="#RFC1542">RFC1542<span> (</span><span class="info">Wimer, W., “Clarifications and Extensions for the Bootstrap Protocol,” October 1993.</span><span>)</span></a> [7].
+ <a class='info' href='#RFC0951'>RFC951<span> (</span><span class='info'>Croft, B. and J. Gilmore, “Bootstrap Protocol,” September 1985.</span><span>)</span></a> [RFC0951] and <a class='info' href='#RFC1542'>RFC1542<span> (</span><span class='info'>Wimer, W., “Clarifications and Extensions for the Bootstrap Protocol,” October 1993.</span><span>)</span></a> [RFC1542].
</p>
<a name="anchor10"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5"></a><h3>5. DHCP Protocol References</h3>
+<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>
<a name="anchor11"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.1"></a><h3>5.1. DHCPv4 Protocol</h3>
+<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.1"></a><h3>5.1.
+DHCPv4 Protocol</h3>
<p>"The DHCP[v4] Protocol" is not defined in a single document. The
following collection of references of what ISC DHCP terms "The
DHCPv4 Protocol".
</p>
<a name="anchor12"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.1.1"></a><h3>5.1.1. Core Protocol References</h3>
+<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.1.1"></a><h3>5.1.1.
+Core Protocol References</h3>
-<p><a class="info" href="#RFC2131">RFC2131<span> (</span><span class="info">Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a> [8] defines the protocol format
+<p><a class='info' href='#RFC2131'>RFC2131<span> (</span><span class='info'>Droms, R., “Dynamic Host Configuration Protocol,” March 1997.</span><span>)</span></a> [RFC2131] defines the protocol format
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.
or relay, which may not be zero. It is not known if there is a good
reason for this that has not been documented.
</p>
-<p><a class="info" href="#RFC2132">RFC2132<span> (</span><span class="info">Alexander, S. and R. Droms, “DHCP Options and BOOTP Vendor Extensions,” March 1997.</span><span>)</span></a> [9] defines the initial set of
+<p><a class='info' href='#RFC2132'>RFC2132<span> (</span><span class='info'>Alexander, S. and R. Droms, “DHCP Options and BOOTP Vendor Extensions,” March 1997.</span><span>)</span></a> [RFC2132] defines the initial set of
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,
known text option it receives prior to any other processing.
</p>
<a name="anchor13"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.2"></a><h3>5.2. DHCPv6 Protocol References</h3>
+<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> [21].
+ 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
quite yet been settled, so support is incomplete.
</p>
<a name="anchor14"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.3"></a><h3>5.3. DHCP Option References</h3>
+<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>
-<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> [10] defines options for
+<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.
</p>
-<p><a class="info" href="#RFC2242">RFC2242<span> (</span><span class="info">Droms, R. and K. Fong, “NetWare/IP Domain Name and Information,” November 1997.</span><span>)</span></a> [11] defines an encapsulated
+<p><a class='info' href='#RFC2242'>RFC2242<span> (</span><span class='info'>Droms, R. and K. Fong, “NetWare/IP Domain Name and Information,” November 1997.</span><span>)</span></a> [RFC2242] defines an encapsulated
option space for NWIP configuration.
</p>
-<p><a class="info" href="#RFC2485">RFC2485<span> (</span><span class="info">Drach, S., “DHCP Option for The Open Group's User Authentication Protocol,” January 1999.</span><span>)</span></a> [12] defines the Open Group's
+<p><a class='info' href='#RFC2485'>RFC2485<span> (</span><span class='info'>Drach, S., “DHCP Option for The Open Group's User Authentication Protocol,” January 1999.</span><span>)</span></a> [RFC2485] defines the Open Group's
UAP option.
</p>
-<p><a class="info" href="#RFC2610">RFC2610<span> (</span><span class="info">Perkins, C. and E. Guttman, “DHCP Options for Service Location Protocol,” June 1999.</span><span>)</span></a> [13] defines options for
+<p><a class='info' href='#RFC2610'>RFC2610<span> (</span><span class='info'>Perkins, C. and E. Guttman, “DHCP Options for Service Location Protocol,” June 1999.</span><span>)</span></a> [RFC2610] defines options for
the Service Location Protocol (SLP).
</p>
-<p><a class="info" href="#RFC2937">RFC2937<span> (</span><span class="info">Smith, C., “The Name Service Search Option for DHCP,” September 2000.</span><span>)</span></a> [14] defines the Name Service
+<p><a class='info' href='#RFC2937'>RFC2937<span> (</span><span class='info'>Smith, C., “The Name Service Search Option for DHCP,” September 2000.</span><span>)</span></a> [RFC2937] defines the Name Service
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,
dhclient-script process this option in a way that is suitable for
the system.
</p>
-<p><a class="info" href="#RFC3004">RFC3004<span> (</span><span class="info">Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A., Beser, B., and J. Privat, “The User Class Option for DHCP,” November 2000.</span><span>)</span></a> [16] defines the User-Class
+<p><a class='info' href='#RFC3004'>RFC3004<span> (</span><span class='info'>Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A., Beser, B., and J. Privat, “The User Class Option for DHCP,” November 2000.</span><span>)</span></a> [RFC3004] defines the User-Class
option. Note carefully that ISC DHCP currently does not implement
to this reference, but has (inexplicably) selected an incompatible
format: a plain text string.
</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> [17] defines the Subnet-Selection
+<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> [22] defines the SIP server
+<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.
</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> [23] documents both how long
+<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
instances of the same option code within a DHCPv4 packet will be
decoded by receivers.
</p>
-<p><a class="info" href="#RFC3397">RFC3397<span> (</span><span class="info">Aboba, B. and S. Cheshire, “Dynamic Host Configuration Protocol (DHCP) Domain Search Option,” November 2002.</span><span>)</span></a> [24] documents the Domain-Search
+<p><a class='info' href='#RFC3397'>RFC3397<span> (</span><span class='info'>Aboba, B. and S. Cheshire, “Dynamic Host Configuration Protocol (DHCP) Domain Search Option,” November 2002.</span><span>)</span></a> [RFC3397] documents the Domain-Search
Option, which allows the configuration of the /etc/resolv.conf
- 'search' parameter in a way that is <a class="info" href="#RFC1035">RFC1035<span> (</span><span class="info">Mockapetris, P., “Domain names - implementation and specification,” November 1987.</span><span>)</span></a> [5] wire format compatible (in fact, it uses the RFC1035 wire
+ 'search' parameter in a way that is <a class='info' href='#RFC1035'>RFC1035<span> (</span><span class='info'>Mockapetris, P., “Domain names - implementation and specification,” November 1987.</span><span>)</span></a> [RFC1035] wire format compatible (in fact, it uses the RFC1035 wire
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> [27] documents the DHCPv6
+<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> [26] documents the Identity
+<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> [28] documents a number of
+<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> [29] documents four NIS options
+<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> [30] documents a pair of
+<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'
or 'who and what am I'), and a means to deliver vendor-specific
and vendor-documented option codes and values.
</p>
-<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> [31] redefined the 'site local'
+<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> [32] defines the DHCPv6 SNTP
+<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> [33] defines the Information
+<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> [34] defines two BCMS server
+<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>
-<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> [35] defined the DHCPv4
+<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> [36] defines a DHCPv6
+<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> [37] defines a DHCPv6 remote-id
+<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 />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.3.1"></a><h3>5.3.1. Relay Agent Information Option Options</h3>
+<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.
+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> [18] defines the Relay Agent
+<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
Information Option and provides a number of sub-option
definitions.
</p>
-<p><a class="info" href="#RFC3256">RFC3256<span> (</span><span class="info">Jones, D. and R. Woundy, “The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option,” April 2002.</span><span>)</span></a> [20] defines the DOCSIS Device
+<p><a class='info' href='#RFC3256'>RFC3256<span> (</span><span class='info'>Jones, D. and R. Woundy, “The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option,” April 2002.</span><span>)</span></a> [RFC3256] defines the DOCSIS Device
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> [25] defines the Link Selection
+<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.
</p>
<a name="anchor16"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.3.2"></a><h3>5.3.2. Dynamic DNS Updates References</h3>
+<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.
+Dynamic DNS Updates References</h3>
<p>The collection of documents that describe the standards-based
method to update dns names of DHCP clients starts most easily
- with <a class="info" href="#RFC4703">RFC4703<span> (</span><span class="info">Stapp, M. and B. Volz, “Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients,” October 2006.</span><span>)</span></a> [40] to define the overall
- architecture, travels through RFCs <a class="info" href="#RFC4702">4702<span> (</span><span class="info">Stapp, M., Volz, B., and Y. Rekhter, “The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option,” October 2006.</span><span>)</span></a> [39]
- and <a class="info" href="#RFC4704">4704<span> (</span><span class="info">Volz, B., “The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option,” October 2006.</span><span>)</span></a> [41] to describe the DHCPv4 and
+ with <a class='info' href='#RFC4703'>RFC4703<span> (</span><span class='info'>Stapp, M. and B. Volz, “Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients,” October 2006.</span><span>)</span></a> [RFC4703] to define the overall
+ architecture, travels through RFCs <a class='info' href='#RFC4702'>4702<span> (</span><span class='info'>Stapp, M., Volz, B., and Y. Rekhter, “The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option,” October 2006.</span><span>)</span></a> [RFC4702]
+ and <a class='info' href='#RFC4704'>4704<span> (</span><span class='info'>Volz, B., “The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option,” October 2006.</span><span>)</span></a> [RFC4704] to describe the DHCPv4 and
DHCPv6 FQDN options (to carry the client name), and ends up at
- <a class="info" href="#RFC4701">RFC4701<span> (</span><span class="info">Stapp, M., Lemon, T., and A. Gustafsson, “A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR),” October 2006.</span><span>)</span></a> [38] which describes the DHCID
+ <a class='info' href='#RFC4701'>RFC4701<span> (</span><span class='info'>Stapp, M., Lemon, T., and A. Gustafsson, “A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR),” October 2006.</span><span>)</span></a> [RFC4701] which describes the DHCID
RR used in DNS to perform a kind of atomic locking.
</p>
<p>ISC DHCP adoped early versions of these documents, and has not
as no other value really makes sense in our context.
</p>
<a name="anchor17"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.3.3"></a><h3>5.3.3. Experimental: Failover References</h3>
+<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.
+Experimental: Failover References</h3>
<p>The Failover Protocol defines a means by which two DHCP Servers
can share all the relevant information about leases granted to
implementation of it has proven stable and suitable for use in
sizable production environments.
</p>
-<p><a class="info" href="#draft-failover">draft-ietf-dhc-failover-12.txt<span> (</span><span class="info">Droms, R., “DHCP Failover Protocol,” March 2003.</span><span>)</span></a> [42]
+<p><a class='info' href='#draft-failover'>draft-ietf-dhc-failover-12.txt<span> (</span><span class='info'>Droms, R., “DHCP Failover Protocol,” March 2003.</span><span>)</span></a> [draft‑failover]
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
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> [19] describes the Load Balancing
+<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
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 />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
-<a name="rfc.section.5.4"></a><h3>5.4. DHCP Procedures</h3>
+<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.
+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> [15] 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> [RFC2939] explains how to go about
obtaining a new DHCP Option code assignment.
</p>
<a name="rfc.references1"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
+<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>
<table width="99%" border="0">
-<tr><td class="author-text" valign="top"><a name="RFC0760">[1]</a></td>
-<td class="author-text">Postel, J., “<a href="ftp://ftp.isi.edu/in-notes/rfc760.txt">DoD standard Internet Protocol</a>,” RFC 760, January 1980.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC0768">[2]</a></td>
-<td class="author-text">Postel, J., “<a href="ftp://ftp.isi.edu/in-notes/rfc768.txt">User Datagram Protocol</a>,” STD 6, RFC 768, August 1980.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC0894">[3]</a></td>
-<td class="author-text">Hornig, C., “<a href="ftp://ftp.isi.edu/in-notes/rfc894.txt">Standard for the transmission of IP datagrams over Ethernet networks</a>,” STD 41, RFC 894, April 1984.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC0951">[4]</a></td>
-<td class="author-text">Croft, B. and J. Gilmore, “<a href="ftp://ftp.isi.edu/in-notes/rfc951.txt">Bootstrap Protocol</a>,” RFC 951, September 1985.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC1035">[5]</a></td>
-<td class="author-text">Mockapetris, P., “<a href="ftp://ftp.isi.edu/in-notes/rfc1035.txt">Domain names - implementation and specification</a>,” STD 13, RFC 1035, November 1987.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC1188">[6]</a></td>
-<td class="author-text"><a href="mailto:dkatz@merit.edu">Katz, D.</a>, “<a href="ftp://ftp.isi.edu/in-notes/rfc1188.txt">Proposed Standard for the Transmission of IP Datagrams over FDDI Networks</a>,” RFC 1188, October 1990.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC1542">[7]</a></td>
-<td class="author-text"><a href="mailto:Walter.Wimer@CMU.EDU">Wimer, W.</a>, “<a href="ftp://ftp.isi.edu/in-notes/rfc1542.txt">Clarifications and Extensions for the Bootstrap Protocol</a>,” RFC 1542, October 1993.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC2131">[8]</a></td>
-<td class="author-text"><a href="mailto:droms@bucknell.edu">Droms, R.</a>, “<a href="
ftp://ftp.isi.edu/in-notes/rfc2131.txt">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>
-<tr><td class="author-text" valign="top"><a name="RFC2132">[9]</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="
ftp://ftp.isi.edu/in-notes/rfc2132.txt">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>
-<tr><td class="author-text" valign="top"><a name="RFC2241">[10]</a></td>
-<td class="author-text"><a href="mailto:donp@Novell.Com">Provan, D.</a>, “<a href="
ftp://ftp.isi.edu/in-notes/rfc2241.txt">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>
-<tr><td class="author-text" valign="top"><a name="RFC2242">[11]</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="
ftp://ftp.isi.edu/in-notes/rfc2242.txt">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>
-<tr><td class="author-text" valign="top"><a name="RFC2485">[12]</a></td>
-<td class="author-text"><a href="mailto:drach@sun.com">Drach, S.</a>, “<a href="
ftp://ftp.isi.edu/in-notes/rfc2485.txt">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>
-<tr><td class="author-text" valign="top"><a name="RFC2610">[13]</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="ftp://ftp.isi.edu/in-notes/rfc2610.txt">DHCP Options for Service Location Protocol</a>,” RFC 2610, June 1999.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC2937">[14]</a></td>
-<td class="author-text">Smith, C., “<a href="ftp://ftp.isi.edu/in-notes/rfc2937.txt">The Name Service Search Option for DHCP</a>,” RFC 2937, September 2000.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC2939">[15]</a></td>
-<td class="author-text">Droms, R., “<a href="ftp://ftp.isi.edu/in-notes/rfc2939.txt">Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types</a>,” BCP 43, RFC 2939, September 2000.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3004">[16]</a></td>
-<td class="author-text">Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A., Beser, B., and J. Privat, “<a href="ftp://ftp.isi.edu/in-notes/rfc3004.txt">The User Class Option for DHCP</a>,” RFC 3004, November 2000.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3011">[17]</a></td>
-<td class="author-text">Waters, G., “<a href="ftp://ftp.isi.edu/in-notes/rfc3011.txt">The IPv4 Subnet Selection Option for DHCP</a>,” RFC 3011, November 2000.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3046">[18]</a></td>
-<td class="author-text">Patrick, M., “<a href="ftp://ftp.isi.edu/in-notes/rfc3046.txt">DHCP Relay Agent Information Option</a>,” RFC 3046, January 2001.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3074">[19]</a></td>
-<td class="author-text">Volz, B., Gonczi, S., Lemon, T., and R. Stevens, “<a href="ftp://ftp.isi.edu/in-notes/rfc3074.txt">DHC Load Balancing Algorithm</a>,” RFC 3074, February 2001.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3256">[20]</a></td>
-<td class="author-text">Jones, D. and R. Woundy, “<a href="ftp://ftp.isi.edu/in-notes/rfc3256.txt">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.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3315">[21]</a></td>
-<td class="author-text">Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, “<a href="ftp://ftp.isi.edu/in-notes/rfc3315.txt">Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 3315, July 2003.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3319">[22]</a></td>
-<td class="author-text">Schulzrinne, H. and B. Volz, “<a href="ftp://ftp.isi.edu/in-notes/rfc3319.txt">Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers</a>,” RFC 3319, July 2003.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3396">[23]</a></td>
-<td class="author-text">Lemon, T. and S. Cheshire, “<a href="ftp://ftp.isi.edu/in-notes/rfc3396.txt">Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)</a>,” RFC 3396, November 2002.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3397">[24]</a></td>
-<td class="author-text">Aboba, B. and S. Cheshire, “<a href="ftp://ftp.isi.edu/in-notes/rfc3397.txt">Dynamic Host Configuration Protocol (DHCP) Domain Search Option</a>,” RFC 3397, November 2002.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3527">[25]</a></td>
-<td class="author-text">Kinnear, K., Stapp, M., Johnson, R., and J. Kumarasamy, “<a href="ftp://ftp.isi.edu/in-notes/rfc3527.txt">Link Selection sub-option for the Relay Agent Information Option for DHCPv4</a>,” RFC 3527, April 2003.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3633">[26]</a></td>
-<td class="author-text">Troan, O. and R. Droms, “<a href="ftp://ftp.isi.edu/in-notes/rfc3633.txt">IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6</a>,” RFC 3633, December 2003.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3646">[27]</a></td>
-<td class="author-text">Droms, R., “<a href="ftp://ftp.isi.edu/in-notes/rfc3646.txt">DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 3646, December 2003.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3679">[28]</a></td>
-<td class="author-text">Droms, R., “<a href="ftp://ftp.isi.edu/in-notes/rfc3679.txt">Unused Dynamic Host Configuration Protocol (DHCP) Option Codes</a>,” RFC 3679, January 2004.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3898">[29]</a></td>
-<td class="author-text">Kalusivalingam, V., “<a href="ftp://ftp.isi.edu/in-notes/rfc3898.txt">Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 3898, October 2004.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3925">[30]</a></td>
-<td class="author-text">Littlefield, J., “<a href="ftp://ftp.isi.edu/in-notes/rfc3925.txt">Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)</a>,” RFC 3925, October 2004.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC3942">[31]</a></td>
-<td class="author-text">Volz, B., “<a href="ftp://ftp.isi.edu/in-notes/rfc3942.txt">Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options</a>,” RFC 3942, November 2004.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4075">[32]</a></td>
-<td class="author-text">Kalusivalingam, V., “<a href="ftp://ftp.isi.edu/in-notes/rfc4075.txt">Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6</a>,” RFC 4075, May 2005.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4242">[33]</a></td>
-<td class="author-text">Venaas, S., Chown, T., and B. Volz, “<a href="ftp://ftp.isi.edu/in-notes/rfc4242.txt">Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)</a>,” RFC 4242, November 2005.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4280">[34]</a></td>
-<td class="author-text">Chowdhury, K., Yegani, P., and L. Madour, “<a href="ftp://ftp.isi.edu/in-notes/rfc4280.txt">Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers</a>,” RFC 4280, November 2005.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4388">[35]</a></td>
-<td class="author-text">Woundy, R. and K. Kinnear, “<a href="ftp://ftp.isi.edu/in-notes/rfc4388.txt">Dynamic Host Configuration Protocol (DHCP) Leasequery</a>,” RFC 4388, February 2006.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4580">[36]</a></td>
-<td class="author-text">Volz, B., “<a href="ftp://ftp.isi.edu/in-notes/rfc4580.txt">Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option</a>,” RFC 4580, June 2006.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4649">[37]</a></td>
-<td class="author-text">Volz, B., “<a href="ftp://ftp.isi.edu/in-notes/rfc4649.txt">Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option</a>,” RFC 4649, August 2006.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4701">[38]</a></td>
-<td class="author-text">Stapp, M., Lemon, T., and A. Gustafsson, “<a href="ftp://ftp.isi.edu/in-notes/rfc4701.txt">A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)</a>,” RFC 4701, October 2006.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4702">[39]</a></td>
-<td class="author-text">Stapp, M., Volz, B., and Y. Rekhter, “<a href="ftp://ftp.isi.edu/in-notes/rfc4702.txt">The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option</a>,” RFC 4702, October 2006.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4703">[40]</a></td>
-<td class="author-text">Stapp, M. and B. Volz, “<a href="ftp://ftp.isi.edu/in-notes/rfc4703.txt">Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients</a>,” RFC 4703, October 2006.</td></tr>
-<tr><td class="author-text" valign="top"><a name="RFC4704">[41]</a></td>
-<td class="author-text">Volz, B., “<a href="ftp://ftp.isi.edu/in-notes/rfc4704.txt">The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option</a>,” RFC 4704, October 2006.</td></tr>
-<tr><td class="author-text" valign="top"><a name="draft-failover">[42]</a></td>
-<td class="author-text">Droms, R., “<a href="http://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="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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
+<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>
</table>
<a name="rfc.authors"></a><br /><hr />
-<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2"> TOC </a></td></tr></table>
+<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>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="author-text"> </td>
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
Hankins [Page 1]
\f
- ISC DHCP References Collection August 2006
+ ISC DHCP References Collection May 2007
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
Hankins [Page 2]
\f
- ISC DHCP References Collection August 2006
+ ISC DHCP References Collection May 2007
1. Introduction
Hankins [Page 3]
\f
- ISC DHCP References Collection August 2006
+ ISC DHCP References Collection May 2007
o To produce new externally-visible behaviour, one must first
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
Hankins [Page 4]
\f
- ISC DHCP References Collection August 2006
+ ISC DHCP References Collection May 2007
address yet) interface.
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
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]
\f
- 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
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
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
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]
\f
- ISC DHCP References Collection August 2006
+ ISC DHCP References Collection May 2007
5. DHCP Protocol References
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]
\f
- 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
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
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]
\f
- 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]
\f
- 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.
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]
\f
- 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.
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]
\f
- 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]
\f
- 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]
\f
- 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]
\f
- ISC DHCP References Collection August 2006
+ ISC DHCP References Collection May 2007
+
+
+ [draft-failover]
+ Droms, R., "DHCP Failover Protocol", March 2003.
Author's Address
-
-
-
-
<?xml version='1.0' ?>
-<!-- $Id: References.xml,v 1.3 2007/05/19 19:16:25 dhankins Exp $ -->
+<!-- $Id: References.xml,v 1.4 2009/07/23 18:52:20 sar Exp $ -->
<?rfc private="ISC-DHCP-REFERENCES" ?>
<date month="May" year="2007"/>
<note title="Copyright Notice">
- <t>Copyright (c) 2006-2007 by Internet Systems Consortium, Inc.
+ <t>Copyright (c) 2006-2007,2009 by Internet Systems Consortium, Inc.
("ISC")</t>
<t>Permission to use, copy, modify, and distribute this software for
for the purpose of sharing information about DHCP served addresses
and clients.</t>
- <t><xref target="RFC4580">RFC4580></xref> defines a DHCPv6
+ <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>
<date month='March' year='2003'/>
</front>
- <format type="TXT" octets="312151" target="http://www.isc.org/sw/dhcp/drafts/draft-ietf-dhc-failover-12.txt"/>
+ <format type="TXT" octets="312151" target="https://www.isc.org/sw/dhcp/drafts/draft-ietf-dhc-failover-12.txt"/>
</reference>
</references>
</back>
-.\" $Id: dhclient-script.8,v 1.2 2005/03/17 20:15:04 dhankins Exp $
+.\" $Id: dhclient-script.8,v 1.3 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
Vixie Enterprises ¤È¶¨ÎϤ·¤Æ Internet Systems Consortium ¤Î¤¿¤á¤Ë
½ñ¤¤Þ¤·¤¿¡£
Internet Systems Consortium ¤Ë¤Ä¤¤¤Æ¤è¤ê¾Ü¤·¤¯¤Ï¡¢
-.B http://www.isc.org
+.B https://www.isc.org
¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
Vixie Enterprises ¤Ë¤Ä¤¤¤Æ¤è¤ê¾Ü¤·¤¯¤Ï¡¢
.B http://www.vix.com
-.\" $Id: dhclient.8,v 1.2 2005/03/17 20:15:05 dhankins Exp $
+.\" $Id: dhclient.8,v 1.3 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" Portions copyright (c) 2000 David E. O'Brien.
.\" All rights reserved.
Vixie Enterprises ¤È¶¨ÎϤ·¤Æ Internet Systems Consortium ¤Î¤¿¤á¤Ë
½ñ¤¤Þ¤·¤¿¡£
Internet Systems Consortium ¤Ë¤Ä¤¤¤Æ¤è¤ê¾Ü¤·¤¯¤Ï¡¢
-.B http://www.isc.org
+.B https://www.isc.org
¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
Vixie Enterprises ¤Ë¤Ä¤¤¤Æ¤è¤ê¾Ü¤·¤¯¤Ï¡¢
.B http://www.vix.com
-.\" $Id: dhclient.conf.5,v 1.2 2005/03/17 20:15:05 dhankins Exp $
+.\" $Id: dhclient.conf.5,v 1.3 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
¤Ï Vixie Labs ¤È¤Î·ÀÌó¤Î¤â¤È¤Ç Ted Lemon ¤¬½ñ¤¤Þ¤·¤¿¡£
ËÜ¥×¥í¥¸¥§¥¯¥È¤Î´ð¶â¤Ï Internet Systems Consortium ¤¬Ä󶡤·¤Þ¤·¤¿¡£
Internet Systems Consortium ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢
-.B http://www.isc.org
+.B https://www.isc.org
¤Ë¤¢¤ê¤Þ¤¹¡£
-.\" $Id: dhclient.leases.5,v 1.2 2005/03/17 20:15:05 dhankins Exp $
+.\" $Id: dhclient.leases.5,v 1.3 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1997-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie
.\" Enterprises. To learn more about Internet Systems Consortium,
-.\" see ``http://www.isc.org/isc''. To learn more about Vixie
+.\" see ``https://www.isc.org/''. To learn more about Vixie
.\" Enterprises, see ``http://www.vix.com''.
.\"
.\"
¤Ï¡¢Vixie Labs ¤È¤Î·ÀÌó¤Î¤â¤È¤Ç¡¢Ted Lemon ¤¬µ½Ò¤·¤Þ¤·¤¿¡£
ËÜ¥×¥í¥¸¥§¥¯¥È¤Î»ñ¶â¤Ï¡¢Internet Systems Consortium ¤¬Ä󶡤·¤Þ¤·¤¿¡£
Internet Systems Consortium ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢
-.B http://www.isc.org
+.B https://www.isc.org
¤Ë¤¢¤ê¤Þ¤¹¡£
-.\" $Id: dhcp-eval.5,v 1.3 2007/01/29 10:25:55 shane Exp $
+.\" $Id: dhcp-eval.5,v 1.4 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\" $FreeBSD: doc/ja_JP.eucJP/man/man5/dhcp-eval.5,v 1.2 2002/05/23 04:17:13 horikawa Exp $
¤Ï¡¢Vixie Labs ¤È¤Î·ÀÌó¤Î¤â¤È¤Ç¡¢Ted Lemon ¤¬µ½Ò¤·¤Þ¤·¤¿¡£
ËÜ¥×¥í¥¸¥§¥¯¥È¤Î»ñ¶â¤Ï¡¢Internet Systems Consortium ¤¬Ä󶡤·¤Þ¤·¤¿¡£
Internet Systems Consortium ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢
-.B http://www.isc.org
+.B https://www.isc.org
¤Ë¤¢¤ê¤Þ¤¹¡£
-.\" $Id: dhcp-options.5,v 1.2 2005/03/17 20:15:06 dhankins Exp $
+.\" $Id: dhcp-options.5,v 1.3 2009/07/23 18:52:20 sar Exp $
.\"
.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
.\" Copyright (c) 1996-2003 by Internet Software Consortium
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
¤Ï¡¢Vixie Labs ¤È¤Î·ÀÌó¤Î¤â¤È¤Ç¡¢Ted Lemon ¤¬µ½Ò¤·¤Þ¤·¤¿¡£
ËÜ¥×¥í¥¸¥§¥¯¥È¤Î»ñ¶â¤Ï¡¢Internet Systems Consortium ¤¬Ä󶡤·¤Þ¤·¤¿¡£
Internet Systems Consortium ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢
-.B http://www.isc.org
+.B https://www.isc.org
¤Ë¤¢¤ê¤Þ¤¹¡£
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/*
*/
#if !defined(LINT) && !defined(CODECENTER)
-static const char rcsid[] = "$Id: base64.c,v 1.2 2005/03/17 20:15:06 dhankins Exp $";
+static const char rcsid[] = "$Id: base64.c,v 1.3 2009/07/23 18:52:20 sar Exp $";
#endif /* not lint */
#include <sys/types.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef HEADER_MD5_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#include <stdio.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#include <stdlib.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/*
- * $Id: nameser.h,v 1.5 2005/03/17 20:15:10 dhankins Exp $
+ * $Id: nameser.h,v 1.6 2009/07/23 18:52:20 sar Exp $
*/
#ifndef _ARPA_NAMESER_H_
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software was written for RadioMail Corporation by Ted Lemon
* under a contract with Vixie Enterprises. Further modifications have
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#define int8_t char
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon, as part of a project for Nominum, Inc. To learn more
- * about Internet Systems Consortium, see http://www.isc.org/. To
+ * about Internet Systems Consortium, see https://www.isc.org/. To
* learn more about Nominum, Inc., see ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises. To learn more
- * about Internet Systems Consortium, see ``http://www.isc.org''.
+ * about Internet Systems Consortium, see ``https://www.isc.org''.
* To learn more about Vixie Enterprises, see ``http://www.vix.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef ISC_BOOLEAN_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef ISC_INT_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef ISC_LANG_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef ISC_LIST_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef ISC_RESULT_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef ISC_TYPES_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef MINIRES_H
#define MINIRES_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/*
- * $Id: res_update.h,v 1.4 2005/03/17 20:15:15 dhankins Exp $
+ * $Id: res_update.h,v 1.5 2009/07/23 18:52:20 sar Exp $
*/
#ifndef __RES_UPDATE_H
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/*
* @(#)resolv.h 8.1 (Berkeley) 6/2/93
- * $Id: resolv.h,v 1.6 2008/01/24 02:43:05 each Exp $
+ * $Id: resolv.h,v 1.7 2009/07/23 18:52:20 sar Exp $
*/
#ifndef _RESOLV_H_
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/*
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon, as part of a project for Nominum, Inc. To learn more
- * about Internet Systems Consortium, see http://www.isc.org/. To
+ * about Internet Systems Consortium, see https://www.isc.org/. To
* learn more about Nominum, Inc., see ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef lint
-static const char rcsid[] = "$Id: ns_date.c,v 1.6 2007/09/05 17:32:10 dhankins Exp $";
+static const char rcsid[] = "$Id: ns_date.c,v 1.7 2009/07/23 18:52:20 sar Exp $";
#endif
/* Import. */
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef lint
-static const char rcsid[] = "$Id: ns_name.c,v 1.3 2009/07/22 21:58:14 dhankins Exp $";
+static const char rcsid[] = "$Id: ns_name.c,v 1.4 2009/07/23 18:52:20 sar Exp $";
#endif
#include <sys/types.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef lint
-static const char rcsid[] = "$Id: ns_parse.c,v 1.3 2005/03/17 20:15:17 dhankins Exp $";
+static const char rcsid[] = "$Id: ns_parse.c,v 1.4 2009/07/23 18:52:20 sar Exp $";
#endif
/* Import. */
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef lint
-static const char rcsid[] = "$Id: ns_samedomain.c,v 1.4 2005/03/17 20:15:18 dhankins Exp $";
+static const char rcsid[] = "$Id: ns_samedomain.c,v 1.5 2009/07/23 18:52:20 sar Exp $";
#endif
#include <sys/types.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef lint
-static const char rcsid[] = "$Id: ns_sign.c,v 1.6 2005/03/17 20:15:18 dhankins Exp $";
+static const char rcsid[] = "$Id: ns_sign.c,v 1.7 2009/07/23 18:52:20 sar Exp $";
#endif
#if defined (TRACING)
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#ifndef lint
-static const char rcsid[] = "$Id: ns_verify.c,v 1.9 2007/09/05 17:32:10 dhankins Exp $";
+static const char rcsid[] = "$Id: ns_verify.c,v 1.10 2009/07/23 18:52:20 sar Exp $";
#endif
/* Import. */
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#if defined(LIBC_SCCS) && !defined(lint)
static const char sccsid[] = "@(#)res_comp.c 8.1 (Berkeley) 6/4/93";
-static const char rcsid[] = "$Id: res_comp.c,v 1.3 2005/03/17 20:15:18 dhankins Exp $";
+static const char rcsid[] = "$Id: res_comp.c,v 1.4 2009/07/23 18:52:20 sar Exp $";
#endif /* LIBC_SCCS and not lint */
#include <sys/types.h>
#if !defined(lint) && !defined(SABER)
-static const char rcsid[] = "$Id: res_findzonecut.c,v 1.16 2005/03/17 20:15:18 dhankins Exp $";
+static const char rcsid[] = "$Id: res_findzonecut.c,v 1.17 2009/07/23 18:52:20 sar Exp $";
#endif /* not lint */
/*
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/* Import. */
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#if defined(LIBC_SCCS) && !defined(lint)
static const char sccsid[] = "@(#)res_init.c 8.1 (Berkeley) 6/7/93";
-static const char rcsid[] = "$Id: res_init.c,v 1.11 2008/02/28 21:21:56 dhankins Exp $";
+static const char rcsid[] = "$Id: res_init.c,v 1.12 2009/07/23 18:52:20 sar Exp $";
#endif /* LIBC_SCCS and not lint */
#include <sys/types.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#if defined(LIBC_SCCS) && !defined(lint)
static const char sccsid[] = "@(#)res_mkquery.c 8.1 (Berkeley) 6/4/93";
-static const char rcsid[] = "$Id: res_mkquery.c,v 1.6 2007/06/29 22:12:30 dhankins Exp $";
+static const char rcsid[] = "$Id: res_mkquery.c,v 1.7 2009/07/23 18:52:20 sar Exp $";
#endif /* LIBC_SCCS and not lint */
#include <sys/types.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/*
*/
#if !defined(lint) && !defined(SABER)
-static const char rcsid[] = "$Id: res_mkupdate.c,v 1.14 2008/11/03 21:51:44 dhankins Exp $";
+static const char rcsid[] = "$Id: res_mkupdate.c,v 1.15 2009/07/23 18:52:20 sar Exp $";
#endif /* not lint */
#include <sys/types.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#if defined(LIBC_SCCS) && !defined(lint)
static const char sccsid[] = "@(#)res_query.c 8.1 (Berkeley) 6/4/93";
-static const char rcsid[] = "$Id: res_query.c,v 1.9 2008/02/28 21:21:56 dhankins Exp $";
+static const char rcsid[] = "$Id: res_query.c,v 1.10 2009/07/23 18:52:20 sar Exp $";
#endif /* LIBC_SCCS and not lint */
#include <sys/types.h>
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#if defined(LIBC_SCCS) && !defined(lint)
static const char sccsid[] = "@(#)res_send.c 8.1 (Berkeley) 6/4/93";
-static const char rcsid[] = "$Id: res_send.c,v 1.11 2008/01/23 22:49:54 marka Exp $";
+static const char rcsid[] = "$Id: res_send.c,v 1.12 2009/07/23 18:52:20 sar Exp $";
#endif /* LIBC_SCCS and not lint */
/*
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
#include <sys/types.h>
#if !defined(lint) && !defined(SABER)
-static const char rcsid[] = "$Id: res_update.c,v 1.15 2007/09/05 17:32:10 dhankins Exp $";
+static const char rcsid[] = "$Id: res_update.c,v 1.16 2009/07/23 18:52:21 sar Exp $";
#endif /* not lint */
/*
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*/
/*
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software was written for RadioMail Corporation by Ted Lemon
* under a contract with Vixie Enterprises. Further modifications have
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon, as part of a project for Nominum, Inc. To learn more
- * about Internet Systems Consortium, see http://www.isc.org/. To
+ * about Internet Systems Consortium, see https://www.isc.org/. To
* learn more about Nominum, Inc., see ``http://www.nominum.com''.
*/
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.TH omapi 3
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon, as part of a project for Nominum, Inc. To learn more
- * about Internet Systems Consortium, see http://www.isc.org/. To
+ * about Internet Systems Consortium, see https://www.isc.org/. To
* learn more about Nominum, Inc., see ``http://www.nominum.com''.
*/
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie
.\" Enterprises. To learn more about Internet Systems Consortium,
-.\" see ``http://www.isc.org/isc''. To learn more about Vixie
+.\" see ``https://www.isc.org/''. To learn more about Vixie
.\" Enterprises, see ``http://www.vix.com''.
.\"
-.\" $Id: dhcrelay.8,v 1.15 2008/06/13 00:55:53 each Exp $
+.\" $Id: dhcrelay.8,v 1.16 2009/07/23 18:52:21 sar Exp $
.\"
.TH dhcrelay 8
.SH NAME
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
static const char message[] =
"Internet Systems Consortium DHCP Relay Agent";
static const char url[] =
-"For info, please visit http://www.isc.org/sw/dhcp/";
+"For info, please visit https://www.isc.org/software/dhcp/";
#ifdef DHCPv6
#define DHCRELAY_USAGE \
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
#
CATMANPAGES = dhcpd.cat8 dhcpd.conf.cat5 dhcpd.leases.cat5
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been donated to Internet Systems Consortium
* by Damien Neil of Nominum, Inc.
*
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Nominum, Inc., see
+ * ``https://www.isc.org/''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
-.\" $Id: dhcpd.8,v 1.29 2008/07/17 06:17:57 each Exp $
+.\" $Id: dhcpd.8,v 1.30 2009/07/23 18:52:21 sar Exp $
.\"
.TH dhcpd 8
.SH NAME
Funding for this project was provided by Internet Systems
Consortium. Version 3 of the DHCP server was funded by Nominum, Inc.
Information about Internet Systems Consortium is available at
-.B http://www.isc.org/\fR.
+.B https://www.isc.org/\fR.
Information about Nominum can be found at \fBhttp://www.nominum.com/\fR.
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
static const char arr [] = "All rights reserved.";
static const char message [] = "Internet Systems Consortium DHCP Server";
static const char url [] =
-"For info, please visit http://www.isc.org/sw/dhcp/";
+"For info, please visit https://www.isc.org/software/dhcp/";
#include "dhcpd.h"
#include <omapip/omapip_p.h>
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
-.\" $Id: dhcpd.conf.5,v 1.104 2009/06/17 22:08:42 dhankins Exp $
+.\" $Id: dhcpd.conf.5,v 1.105 2009/07/23 18:52:21 sar Exp $
.\"
.TH dhcpd.conf 5
.SH NAME
under a contract with Vixie Labs. Funding
for this project was provided by Internet Systems Consortium.
Information about Internet Systems Consortium can be found at
-.B http://www.isc.org.
+.B https://www.isc.org.
.\" 950 Charter Street
.\" Redwood City, CA 94063
.\" <info@isc.org>
-.\" http://www.isc.org/
+.\" https://www.isc.org/
.\"
.\" This software has been written for Internet Systems Consortium
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
.\" To learn more about Internet Systems Consortium, see
-.\" ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+.\" ``https://www.isc.org/''. To learn more about Vixie Enterprises,
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
-.\" $Id: dhcpd.leases.5,v 1.13 2009/01/22 21:22:42 dhankins Exp $
+.\" $Id: dhcpd.leases.5,v 1.14 2009/07/23 18:52:21 sar Exp $
.\"
.TH dhcpd.leases 5
.SH NAME
under a contract with Vixie Labs. Funding
for this project was provided by Internet Systems Consortium.
Information about Internet Systems Consortium can be found at:
-.B http://www.isc.org/
+.B https://www.isc.org/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
* 950 Charter Street
* Redwood City, CA 94063
* <info@isc.org>
- * http://www.isc.org/
+ * https://www.isc.org/
*
* This software has been written for Internet Systems Consortium
* by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
* To learn more about Internet Systems Consortium, see
- * ``http://www.isc.org/''. To learn more about Vixie Enterprises,
+ * ``https://www.isc.org/''. To learn more about Vixie Enterprises,
* see ``http://www.vix.com''. To learn more about Nominum, Inc., see
* ``http://www.nominum.com''.
*/
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
package dhcp_client;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
# 950 Charter Street
# Redwood City, CA 94063
# <info@isc.org>
-# http://www.isc.org/
+# https://www.isc.org/
use strict;
use English;
projects / thirdparty / dhcp.git / commitdiff
