Protected EAP TLV
draft-salowey-eap-protectedtlv-02

Document Type Expired Internet-Draft (individual)
Last updated 2003-07-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-salowey-eap-protectedtlv-02.txt

Abstract

EAP type-length-value (TLV) message types provide a mechanism for encapsulating additional information in an EAP conversation. In some cases it is useful to cryptographically protect this information to maintain the integrity and/or privacy of the communication. This document defines a TLV type that uses message authentication to maintain the integrity of the data, encryption to protect the privacy of the data and sequence numbers to protect replays or re-sequencing of the data. Although protected TLVs must be chained after an authentication mechanism that generates key material the protection mechanism is independent of any particular authentication mechanism.

Authors

Joseph Salowey (jsalowey@cisco.com)

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