RFC 4578: Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE)
In plain English — editorial summary, not part of the RFC
We define Dynamic Host Configuration Protocol (DHCP) options being used by Preboot eXecution Environment (PXE) and Extensible Firmware Interface (EFI) clients to uniquely identify booting client machines and their pre-OS runtime environment so that the DHCP and/or PXE boot server can return the correct OS bootstrap image (or pre-boot application) name and server to the client. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4578
- Published
- November 2006
- Authors
- M. Johnston; S. Venaas
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4580Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID OptionCurrent
June 2006
- RFC 4584Extension to Sockets API for Mobile IPv6Current
July 2006
- RFC 4592The Role of Wildcards in the Domain Name SystemCurrent
July 2006
- RFC 4604Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific MulticastCurrent
August 2006
- RFC 4605Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")Current
August 2006
- RFC 4541Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping SwitchesCurrent
May 2006
- RFC 4620IPv6 Node Information QueriesCurrent
August 2006
- RFC 4635HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm IdentifiersObsoleted
August 2006
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?