Skip to main content

Bootstrapping RFC3118 Delayed DHCP Authentication Using EAP-based Network Access Authentication

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Hannes Tschofenig , Alper E. Yegin , Dan Forsberg
Last updated 2008-07-14
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The DHCP authentication extension (RFC 3118) cannot be widely deployed due to lack of a key agreement protocol. This document outlines how EAP-based network access authentication mechanisms can be used to establish bootstrap keying material that can be used to subsequently use RFC 3118 security.


Hannes Tschofenig
Alper E. Yegin
Dan Forsberg

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)