RFC 3118: Authentication for DHCP Messages
In plain English — editorial summary, not part of the RFC
This document defines a new Dynamic Host Configuration Protocol (DHCP) option through which authorization tickets can be easily generated and newly attached hosts with proper authorization can be automatically configured from an authenticated DHCP server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3118
- Published
- June 2001
- Authors
- R. Droms; W. Arbaugh
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3046DHCP Relay Agent Information OptionUpdated
January 2001
- RFC 3011The IPv4 Subnet Selection Option for DHCPCurrent
November 2000
- RFC 3004The User Class Option for DHCPCurrent
November 2000
- RFC 3256The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-optionCurrent
April 2002
- RFC 2937The Name Service Search Option for DHCPCurrent
September 2000
- RFC 2855DHCP for IEEE 1394Current
June 2000
- RFC 3442The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4Current
December 2002
- RFC 3495Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client ConfigurationCurrent
March 2003
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?