Implementation Report

The IESG has approved the following documents:

  1. Dynamic Host Configuration Protocol
    draft-ietf-dhc-dhcp-09.txt
  2. DHCP Options and BOOTP Vendor Extensions
    draft-ietf-dhc-options-1533update-06.txt
  3. Interoperation Between DHCP and BOOTP
    rfc1534
  4. Clarifications and Extensions for the Bootstrap Protocol
    rfc1542

as Draft Standards. These documents are the product of the Dynamic Host Configuration Working Group. The IESG contact persons are Frank Kastenholz and Jeffrey Burgan.

Included below is a list of information about several DHCP implementations, in support if the requirement for independent, interoperable implementations before acceptance of the protocol specification as a Draft Standard. The list is only a partial list of available implementation; I can try to twist some arms to get a longer list if it is needed.

The implementations have been tested for interoperability at four DHCP bake-offs and at recent Connectathons. Here is a summary of the DHCP bakeoffs:

  • Seattle, WA - 10/23/93
  • Chelmsford, MA - 1/19/94
  • Toronto, Ontario, Canada - 7/21/94
    • Sun, WIDE, Microsoft, FTP Software, Competitive Automation, SGI, HP
  • Cupertino, CA - 6/15/95
    • Apple, Competitive Automation, FTP Software, HP, Microsoft, SGI, Shiva, TGV

Note: The DHCP implementors define 'implementation' of a specific option to mean that the option can be inserted into a DHCP message by a server, and extracted from the message by a client. There is no requirement that there actually be an application program that actually uses every option. In particular, many of the "legacy" options from BOOTP have been carried forward for backward compatibility, even though it is not likely that any DHCP client will make use of, e.g., the IEN 116 name servers option.

- Ralph


Name of Implementation: Cisco MultiNet v4.0 (DHCP server is a component part).
Organisation: cisco Systems
Implemented Features:
Full client-server interaction: Yes
(DISCOVER, OFFER, REQUEST, ACK)
DHCPINFORM: Yes
All RFC1533update options (Y/N): Yes
BOOTP client interoperability: Yes
BOOTP server interoperability: Not Applicable
Platforms: OpenVMS
Lineage of DHCP Server Code: TGV/Cisco
Lineage of DHCP Client Code: Not Applicable.
Location of Source Code: Proprietary.
Point of Contact: Ken Key
Claimed Interoperability: Cisco (no INFORM), FTP Software (including INFORM),
Sun (Including INFORM), Microsoft (no INFORM), SGI (no INFORM), Competitive
Automation (Including INFORM), Shiva (not sure of INFORM), Apple (no INFORM).


Name of Implementation: Cisco DNS/DCHP Manager v1.0.
Organisation: cisco Systems
Implemented Features:
Full client-server interaction: Yes.
(DISCOVER, OFFER, REQUEST, ACK)
DHCPINFORM: Yes.
All RFC1533update options (Y/N): Yes.
BOOTP client interoperability: Yes.
BOOTP server interoperability: Not Applicable.
Platforms: Solaris, HP-UX, AIX.
Lineage of DHCP Server Code: TGV/Cisco.
Lineage of DHCP Client Code: Not Applicable.
Location of Source Code: proprietary.
Point of Contact:
Claimed Interoperability: Cisco, Microsoft, Apple.

Note: this product is based on the same core code-base as the above MultiNet for OpenVMS. The port of the DHCP server to the UNIX platforms was not at the HP-Cupertino DHCP bake-off that I brought the VMS server to, so I'm being conservative in not claiming the same interoperabity. The protocol engine is the same code.


Name of Implementation: Cisco TCP/IP for Windows Suite 100 v2.0 (DHCP client)
Organisation: cisco Systems
Implemented Features:
Full client-server interaction: Yes.
(DISCOVER, OFFER, REQUEST, ACK)
DHCPINFORM: No.
All RFC1533update options (Y/N): No.
BOOTP client interoperability: Not Applicable.
BOOTP server interoperability: Yes.
Platforms: Microsoft Windows v3.1, v3.11, 95
Lineage of DHCP Server Code: Not Applicable.
Lineage of DHCP Client Code: TGV/Cisco.
Location of Source Code: proprietary.
Point of Contact: Ken Key
Claimed Interoperability: FTP Software, Sun, Microsoft, Competive Automation,
SGI, Hewlett-Packard, ISC (and whoever else was at the 1996 connectathon;
I wasn't there and the fellow that did the testing is not available right now).


Name of Implementation: JOIN
Organisation: Competitive Automation
Implemented Features:
Full client-server interaction:
(DISCOVER, OFFER, REQUEST, ACK) Yes
DHCPINFORM: Yes
All RFC1533update options (Y/N): Y
BOOTP client interoperability: Yes
BOOTP server interoperability: No
Platforms: SunOS4.1.x, SunOS5.x, Digital Unix, HP-UX9, HP-UX10
Lineage of DHCP Server Code: Original
Lineage of DHCP Client Code: Original
Location of Source Code: Not avalaible
Point of Contact: Rob Stevens robs@join.com
Claimed Interoperability: SUN Solarnet, FTP, HP, TGV/Cisco, Microsoft,
(DISCOVER, OFFER, REQUEST, ACK)
DHCPINFORM: No.
All RFC1533update options (Y/N): No.
BOOTP client interoperability: Not Applicable.
BOOTP server interoperability: Yes.
Platforms: Microsoft Windows v3.1, v3.11, 95
Lineage of DHCP Server Code: Not Applicable.
Lineage of DHCP Client Code: TGV/Cisco.
Location of Source Code: proprietary.
Point of Contact: Ken Key
Claimed Interoperability: FTP Software, Sun, Microsoft, Competive Automation,
SGI, Hewlett-Packard, ISC (and whoever else was at the 1996 connectathon;
I wasn't there and the fellow that did the testing is not available right now).


Name of Implementation: JOIN
Organisation: Competitive Automation
Implemented Features:
Full client-server interaction:
(DISCOVER, OFFER, REQUEST, ACK) Yes
DHCPINFORM: Yes
All RFC1533update options (Y/N): Y
BOOTP client interoperability: Yes
BOOTP server interoperability: No
Platforms: SunOS4.1.x, SunOS5.x, Digital Unix, HP-UX9, HP-UX10
Lineage of DHCP Server Code: Original
Lineage of DHCP Client Code: Original
Location of Source Code: Not avalaible
Point of Contact: Rob Stevens robs@join.com
Claimed Interoperability: SUN Solarnet, FTP, HP, TGV/Cisco, Microsoft,
Computer Associates, OS/2


Name of Implementation: OS/2 DHCP server & OS/2 DHCP Client
Organisation: IBM Corporation
Implemented Features:
Full client-server interaction: YES
(DISCOVER, OFFER, REQUEST, ACK)
DHCPINFORM: YES
All RFC1533update options (Y/N):Server (YES), client (Yes) with user exits
BOOTP client interoperability: BOOTP Clients can be served by DHCP server.
BOOTP server interoperability: N/A
Platforms: OS/2 WARP Version 3, 3.5 SMP,4
Lineage of DHCP Server Code: IBM Corporation
Lineage of DHCP Client Code: IBM Corporation
Location of Source Code: Not Available
Point of Contact: Pratik Gupta
Claimed Interoperability: The implementations tested at Connectathon 96.