WG Action: RECHARTER: Extensible Authentication Protocol (eap)

The IESG <iesg-secretary@ietf.org> Wed, 16 June 2004 16:37 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18190 for <ietf-announce-archive@ietf.org>; Wed, 16 Jun 2004 12:37:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BadQE-0005aG-Of for ietf-announce-archive@ietf.org; Wed, 16 Jun 2004 12:37:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bad5L-00023m-00 for ietf-announce-archive@ietf.org; Wed, 16 Jun 2004 12:16:24 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BaclE-0006KD-00; Wed, 16 Jun 2004 11:55:36 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by mx2.foretec.com with esmtp (Exim 4.24) id 1Baccb-0004mg-P8; Wed, 16 Jun 2004 11:46:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BacRM-0006M6-9a; Wed, 16 Jun 2004 11:35:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BabsO-0002iA-4A for ietf-announce@megatron.ietf.org; Wed, 16 Jun 2004 10:58:56 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03177; Wed, 16 Jun 2004 10:58:52 -0400 (EDT)
Message-Id: <200406161458.KAA03177@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Date: Wed, 16 Jun 2004 10:58:52 -0400
X-Mailman-Approved-At: Wed, 16 Jun 2004 11:35:02 -0400
Cc: Jari Arkko <Jari.Arkko@ericsson.com>, eap@frascone.com, Bernard Aboba <aboba@internaut.com>
Subject: WG Action: RECHARTER: Extensible Authentication Protocol (eap)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The charter of the Extensible Authentication Protocol (eap) working group 
in the Internet Area of the IETF has been updated. For additional information, 
please contact the Area Directors or the working group Chairs.

Extensible Authentication Protocol (eap)
========================================

Current Status: Active Working Group

Chair(s):
Bernard Aboba <aboba@internaut.com>
Jari Arkko <Jari.Arkko@ericsson.com>

Internet Area Director(s):
Thomas Narten <narten@us.ibm.com>
Margaret Wasserman <margaret@thingmagic.com>

Internet Area Advisor:
Margaret Wasserman <margaret@thingmagic.com>

Technical Advisor(s):
William Arbaugh <waa@dsl.cis.upenn.edu>

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 3748 published  
Done    EAP state machine document submitted for publication as an Informational RFC  
Sep 04 EAP Keying Framework document submitted for publication as an Informational RFC  
Oct 04 EAP Network Selection Problem Definition document submitted as an Informational RFC  




_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce