ObsoletedLegacy stream

RFC 1048: BOOTP vendor information extensions

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1084, RFC 1395, RFC 1497, RFC 1533.

Current document in this lineage: RFC 2132DHCP Options and BOOTP Vendor Extensions

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

This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought.

Document record

Document ID
RFC1048
Published
February 1988
Authors
P.A. Prindeville
Status
UNKNOWN
Stream
Legacy
Area
Pages
7
Also known as

Standards lineage

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

  1. RFC 1048 (1988)
  2. RFC 1084 (1988)
  3. RFC 1395 (1993)
  4. RFC 1497 (1993)
  5. RFC 1533 (1993)
  6. RFC 2132 (1997)

Read the full history of DHCP Options and BOOTP Vendor Extensions

Referenced by

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

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/1048-bootp-vendor-information-extensions