Browse Prior Art Database

Dynamic Host Configuration Protocol (RFC2131)

IP.com Disclosure Number: IPCOM000002686D
Original Publication Date: 1997-Mar-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 45 page(s) / 61K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Droms: AUTHOR

Related Documents

10.17487/RFC2131: DOI

Abstract

The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCPIP network. DHCP is based on the Bootstrap Protocol (BOOTP), adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 3% of the total text.

Network Working Group R. Droms Request for Comments: 2131 Bucknell University Obsoletes: 1541 March 1997 Category: Standards Track

Dynamic Host Configuration Protocol

Status of this memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Abstract

The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCPIP network. DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the capability of automatic allocation of reusable network addresses and additional configuration options [19]. DHCP captures the behavior of BOOTP relay agents [7, 21], and DHCP participants can interoperate with BOOTP participants [9].

Table of Contents

1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 Changes to RFC1541. . . . . . . . . . . . . . . . . . . . . . 3 1.2 Related Work. . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Problem definition and issues . . . . . . . . . . . . . . . . 4 1.4 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 5 1.5 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.6 Design goals. . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Protocol Summary. . . . . . . . . . . . . . . . . . . . . . . 8 2.1 Configuration parameters repository . . . . . . . . . . . . . 11 2.2 Dynamic allocation of network addresses . . . . . . . . . . . 12 3. The Client-Server Protocol. . . . . . . . . . . . . . . . . . 13 3.1 Client-server interaction - allocating a network address. . . 13 3.2 Client-server interaction - reusing a previously allocated network address . . . . . . . . . . . . . . . . . . . . . . . 17 3.3 Interpretation and representation of time values. . . . . . . 20 3.4 Obtaining parameters with externally configured network address . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.5 Client parameters in DHCP . . . . . . . . . . . . . . . . . . 21 3.6 Use of DHCP in clients with multiple interfaces . . . . . . . 22 3.7 When clients should use DHCP. . . . . . . . . . . . . . . . . 22 4. Specification of the DHCP client-server protocol. . . . . . . 22

Droms Standards Track [Page 1]

RFC 2131 Dynamic Host Configuration Protocol March 1997

4.1 Constructing and sending DHCP messages. . . . . . . . . . . . 22 4.2 DHCP server administrative controls . . . . . . . . . . . . . 25 4.3 DHCP server behavior. . . . . . . . . . . . . . . . . . . . . 26 4.4 DHCP client behavior. . . . . . . . . . . . . . . . . . . . . 34 5. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . .42 6. References . . . . . . . . . . . . . . . . . . . . . . . . . .42 7. Security Considerations. . . . . . . . . . . . . . . . . . . .43 8. Author’s Address . . . . . ....

Processing...
Loading...