Using EAP keying material to derive keys for DHCP Authentication
draft-salowey-dhc-eapkey-3118-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Joseph A. Salowey , Richard Pruss | ||
| Last updated | 2008-07-06 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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:
Abstract
This memo describes a mechanism to use keying material derived from the extensible authentication protocol (EAP) to derive cryptographic keys for authentication of the Dynamic Host Configuration Protocol (DHCP). Keys are derived from the EAP extended master session key (EMSK) and are used in a new DHCP authentication option based on the DHCP delayed authentication option defined in RFC 3118.
Authors
Joseph A. Salowey
Richard Pruss
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)