Update to the EAP Applicability Statement for ABFAB
draft-winter-abfab-eapapplicability-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-01-17 (latest revision 2012-07-16) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
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-winter-abfab-eapapplicability-02.txt
https://www.ietf.org/archive/id/draft-winter-abfab-eapapplicability-02.txt
Abstract
This document updates the EAP applicability statement from RFC3748 to reflect recent usage of the EAP protocol in application oriented use cases proposed in ABFAB
Authors
Stefan Winter
(stefan.winter@restena.lu)
Joseph Salowey
(jsalowey@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)