CurrentDRAFT STANDARDLegacy stream

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
RFC1542
Published
October 1993
Authors
W. Wimer
Status
DRAFT STANDARD
Stream
Legacy
Area
Pages
23
Also known as
Obsoletes:
RFC 1532
Updates:
RFC 951

Topics

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/1542-clarifications-and-extensions-for-the-bootstrap-protocol