RFC 1497: BOOTP Vendor Information Extensions
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1533.
Current document in this lineage: RFC 2132 — DHCP Options and BOOTP Vendor Extensions
In plain English — editorial summary, not part of the RFC
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP).
Document record
- Document ID
- RFC1497
- Published
- August 1993
- Authors
- J. Reynolds
- Status
- DRAFT STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Read the full history of DHCP Options and BOOTP Vendor Extensions →
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 2880Internet Fax T.30 Feature MappingCurrent
August 2000
- RFC 2938Identifying Composite Media FeaturesCurrent
September 2000
- RFC 4390Dynamic Host Configuration Protocol (DHCP) over InfiniBandCurrent
April 2006
- RFC 5970DHCPv6 Options for Network BootCurrent
September 2010
- RFC 8819YANG Module TagsCurrent
January 2021
- RFC 9019A Firmware Update Architecture for Internet of ThingsCurrent
April 2021
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?