RFC 2855: DHCP for IEEE 1394
In plain English — editorial summary, not part of the RFC
This memo describes specific usage of some fields of DHCP (Dynamic Host Configuration Protocol) messages. IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. Since 1394 uses a different link-layer addressing method than conventional IEEE802/Ethernet, the usage of some fields must be clarified to achieve interoperability. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2855
- Published
- June 2000
- Authors
- K. Fujisawa
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2937The Name Service Search Option for DHCPCurrent
September 2000
- RFC 3004The User Class Option for DHCPCurrent
November 2000
- RFC 3011The IPv4 Subnet Selection Option for DHCPCurrent
November 2000
- RFC 3046DHCP Relay Agent Information OptionUpdated
January 2001
- RFC 2610DHCP Options for Service Location ProtocolCurrent
June 1999
- RFC 3118Authentication for DHCP MessagesCurrent
June 2001
- RFC 2563DHCP Option to Disable Stateless Auto-Configuration in IPv4 ClientsUpdated
May 1999
- RFC 2485DHCP Option for The Open Group's User Authentication ProtocolCurrent
January 1999
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?