ObsoletedPROPOSED STANDARDLegacy stream

RFC 1541: Dynamic Host Configuration Protocol

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2131.

Current document in this lineage: RFC 2131 — Dynamic Host Configuration Protocol

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 TCP/IP 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
RFC1541
Published
October 1993
Authors
R. Droms
Status
PROPOSED STANDARD
Stream
Legacy
Area
—
Pages
39
Also known as
—
Obsoletes:
RFC 1531
Obsoleted by:
RFC 2131

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

One later RFC formally updates or obsoletes 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/1541-dynamic-host-configuration-protocol