RFC 1532: Clarifications and Extensions for the Bootstrap Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1542.
Current version: RFC 1542 — Clarifications and Extensions for the Bootstrap Protocol
In plain English — editorial summary, not part of the RFC
Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1532
- Published
- October 1993
- Authors
- W. Wimer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 22
- Also known as
- —
Topics
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.
- RFC 1533DHCP Options and BOOTP Vendor ExtensionsObsoleted
October 1993
- RFC 1531Dynamic Host Configuration ProtocolObsoleted
October 1993
- RFC 1534Interoperation Between DHCP and BOOTPCurrent
October 1993
- RFC 1526Assignment of System Identifiers for TUBA/CLNP HostsCurrent
September 1993
- RFC 1547Requirements for an Internet Standard Point-to-Point ProtocolCurrent
December 1993
- RFC 1548The Point-to-Point Protocol (PPP)Obsoleted
December 1993
- RFC 1549PPP in HDLC FramingObsoleted
December 1993
- RFC 1552The PPP Internetworking Packet Exchange Control Protocol (IPXCP)Current
December 1993
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?