Protected EAP Protocol (PEAP) Version 2
draft-josefsson-pppext-eap-tls-eap-10
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2004-10-21 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
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) | ||
https://www.ietf.org/archive/id/draft-josefsson-pppext-eap-tls-eap-10.txt
Abstract
The Extensible Authentication Protocol (EAP) provides support for multiple authentication methods. This document defines the Protected Extensible Authentication Protocol (PEAP) Version 2, which provides an encrypted and authenticated tunnel based on transport layer security (TLS) that encapsulates EAP authentication mechanisms. PEAPv2 uses TLS to protect against rogue authenticators, protect against various attacks on the confidentiality and integrity of the inner EAP method exchange and provide EAP peer identity privacy. PEAPv2 also provides support for chaining multiple EAP mechanisms, cryptographic binding between authentications performed by inner EAP mechanisms and the tunnel, exchange of arbitrary parameters (TLVs), and fragmentation and reassembly.
Authors
Ashwin Palekar
(ashwinp@microsoft.com)
Simon Josefsson
(simon@josefsson.org)
Daniel Simon
(dansimon@microsoft.com)
Glen Zorn
(glenzorn@hotmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)