Concluded WG Extensible Authentication Protocol (eap)
Note: The data for concluded WGs is occasionally incorrect.
|WG||Name||Extensible Authentication Protocol|
|Area||Internet Area (int)|
|Additional resources||Additional EAP Web Page|
|Personnel||Chair||Dr. Bernard D. Aboba|
|Area Director||Jari Arkko|
|Tech Advisors||Charles Clancy, William A. Arbaugh|
Final 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:
- IANA considerations for EAP.
- Type space extension to support an expanded Type space.
- EAP usage model.
- Threat model and security requirements.
- Documentation of interaction between EAP and other layers.
- Resolution of interoperability issues.
- EAP state machine.
- EAP keying framework.
- 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.
|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|