Extensible Authentication Protocol (eap) Concluded WG

Note: The data for concluded WGs is occasionally incorrect.

WG Name Extensible Authentication Protocol
Acronym eap
Area Internet Area (int)
State Concluded
Charter charter-ietf-eap-01 Approved
Dependencies Document dependency graph (SVG)
Additional URLs Additional EAP Web Page
Personnel Chair Bernard Aboba
Area Director Jari Arkko
Tech Advisors Charles Clancy
William Arbaugh
Mailing list Address eap@frascone.com
To subscribe eap-request@frascone.com
Archive http://mail.frascone.com/pipermail/eap/

Charter for Working Group


The EAP working group will restrict itself to the following work items
in order to fully document and improve the interoperability of the
existing EAP protocol:

1. IANA considerations for EAP.
2. Type space extension to support an expanded Type space.
3. EAP usage model.
4. Threat model and security requirements.
5. Documentation of interaction between EAP and other layers.
6. Resolution of interoperability issues.
7. EAP state machine.
8. EAP keying framework.
9. EAP network selection problem definition

Items 1-6 were included within RFC 3748. Items 7-9 will be handled
as separate documents.

While the EAP WG is not currently chartered to standardize EAP
methods, with the publication of RFC 3748, the EAP WG will
assume responsibility for review of EAP methods requesting
a Type code allocation, as specified in the IANA considerations
section of RFC 3748.

When the current work items are completed, the WG may be
rechartered, or a new WG may be formed to standardize methods.

Milestones

Date Milestone
Done EAP Network Selection Problem Definition document submitted as an Informational RFC
Done EAP Keying Framework document submitted for publication as an Informational RFC
Done EAP state machine document submitted for publication as an Informational RFC
Done RFC 3748 published
Done RFC 2284bis submitted for publication as a Proposed Standard