Extensible Authentication Protocol (eap)
----------------------------------------

 Charter
 Last Modified: 2006-03-30

 Current Status: Active Working Group

 Chair(s):
     Bernard Aboba  <Bernard_Aboba@hotmail.com>

 Internet Area Director(s):
     Jari Arkko  <jari.arkko@piuha.net>
     Mark Townsley  <townsley@cisco.com>

 Internet Area Advisor:
     Jari Arkko  <jari.arkko@piuha.net>

 Technical Advisor(s):
     William Arbaugh  <waa@dsl.cis.upenn.edu>
     Charles Clancy  <clancy@ltsnet.net>

 Mailing Lists: 
     General Discussion:eap@frascone.com
     To Subscribe:      eap-request@frascone.com
         In Body:       subscribe in Subject line
     Archive:           http://mail.frascone.com/pipermail/eap/

Description of 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.

 Goals and Milestones:

   Done         RFC 2284bis submitted for publication as a Proposed Standard 

   Done         RFC 3748 published 

   Done         EAP state machine document submitted for publication as an 
                Informational RFC 

   Sep 2004       EAP Keying Framework document submitted for publication as an 
                Informational RFC 

   Oct 2004       EAP Network Selection Problem Definition document submitted as 
                an Informational RFC 


 Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Oct 2003 Jun 2006   <draft-ietf-eap-keying-14.txt>
                Extensible Authentication Protocol (EAP) Key Management 
                Framework 

Jan 2004 May 2006   <draft-ietf-eap-netsel-problem-04.txt>
                Network Discovery and Selection Problem 

 Request For Comments:

  RFC   Stat Published     Title
------- -- ----------- ------------------------------------
RFC3748Standard  Jun 2004    Extensible Authentication Protocol (EAP) 

RFC4137 I    Aug 2005    State Machines for Extensible Authentication Protocol 
                       (EAP) Peer and Authenticator