RFC 4390: Dynamic Host Configuration Protocol (DHCP) over InfiniBand
In plain English — editorial summary, not part of the RFC
IP over Infiniband (IPoIB) link-layer address is 20 octets long. This is larger than the 16 octets reserved for the hardware address in a Dynamic Host Configuration Protocol/Bootstrap Protocol (DHCP/BOOTP) message. The above inequality imposes restrictions on the use of the DHCP message fields when used over an IPoIB network. This document describes the use of DHCP message fields when implementing DHCP over IPoIB. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4390
- Published
- April 2006
- Authors
- V. Kashyap
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3942Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) OptionsCurrent
November 2004
- RFC 3442The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4Current
December 2002
- RFC 5970DHCPv6 Options for Network BootCurrent
September 2010
- RFC 2132DHCP Options and BOOTP Vendor ExtensionsUpdated
March 1997
- RFC 1534Interoperation Between DHCP and BOOTPCurrent
October 1993
- RFC 1533DHCP Options and BOOTP Vendor ExtensionsObsoleted
October 1993
- RFC 7484Finding the Authoritative Registration Data (RDAP) ServiceObsoleted
March 2015
- RFC 8521Registration Data Access Protocol (RDAP) Object TaggingCurrent
November 2018
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?