metasystema.org
UpdatedDRAFT STANDARDIETF stream

RFC 2131: Dynamic Host Configuration Protocol

Still current, but amended. Parts of this document are changed or extended by RFC 3396, RFC 4361, RFC 5494, RFC 6842. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC2131
Published
March 1997
Authors
R. Droms
Status
DRAFT STANDARD
Stream
IETF
Area
int
Pages
45
Also known as
—
Obsoletes:
RFC 1541
Updated by:
RFC 3396, RFC 4361, RFC 5494, RFC 6842

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 1531 (1993)
  2. RFC 1541 (1993)
  3. RFC 2131 (1997)

Read the full history of Dynamic Host Configuration Protocol →

Referenced by

4 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/2131-dynamic-host-configuration-protocol