Gap analysis on the EAP keying hierarchy
draft-vidya-eap-keying-gap-analysis-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vidya Narayanan , Lakshminath R. Dondeti | ||
| Last updated | 2006-10-25 | ||
| 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
The extensible authentication protocol (EAP) keying framework [1] leaves out guidelines for using the extended master session key (EMSK) for future discussion and specification. While the keying framework does provide guidance for EAP master session key (MSK) usage, some SDOs use that key in a non-compliant manner. This document provides a description and analysis of MSK and EMSK usage and provides an outline for a discussion on these topics.
Authors
Vidya Narayanan
Lakshminath R. Dondeti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)