RFC 1534: Interoperation Between DHCP and BOOTP
In plain English — editorial summary, not part of the RFC
DHCP provides a superset of the functions provided by BOOTP. This document describes the interactions between DHCP and BOOTP network participants. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1534
- Published
- October 1993
- Authors
- R. Droms
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2132DHCP Options and BOOTP Vendor ExtensionsUpdated
March 1997
- RFC 1533DHCP Options and BOOTP Vendor ExtensionsObsoleted
October 1993
- RFC 2939Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesCurrent
September 2000
- RFC 3203DHCP reconfigure extensionUpdated
December 2001
- RFC 3679Unused Dynamic Host Configuration Protocol (DHCP) Option CodesUpdated
January 2004
- RFC 3942Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) OptionsCurrent
November 2004
- RFC 2462IPv6 Stateless Address AutoconfigurationObsoleted
December 1998
- RFC 2491IPv6 over Non-Broadcast Multiple Access (NBMA) networksUpdated
January 1999
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?