[SECMECH] EMU BOF Summary

"Salowey, Joe" <jsalowey@cisco.com> Fri, 11 November 2005 19:21 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaeSw-00005x-Bw; Fri, 11 Nov 2005 14:21:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaeSu-00005U-Nb for secmech@megatron.ietf.org; Fri, 11 Nov 2005 14:21:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29308 for <secmech@ietf.org>; Fri, 11 Nov 2005 14:21:06 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EaejN-0001zY-EH for secmech@ietf.org; Fri, 11 Nov 2005 14:38:38 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 11 Nov 2005 11:21:26 -0800
X-IronPort-AV: i="3.99,119,1131350400"; d="scan'208"; a="674076440:sNHT28404424"
Received: from E2K-SEA-XCH2.sea-alpha.cisco.com (e2k-sea-xch2.cisco.com [10.93.132.68]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jABJLNZC020518; Fri, 11 Nov 2005 11:21:24 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Nov 2005 11:27:04 -0800
Message-ID: <7210B31550AC934A8637D6619739CE690638754B@e2k-sea-xch2.sea-alpha.cisco.com>
Thread-Topic: EMU BOF Summary
Thread-Index: AcXm9RrDz7/qizTQRQmdw+HVwWP30g==
From: "Salowey, Joe" <jsalowey@cisco.com>
To: <secmech@ietf.org>, <saag@mit.edu>, <eap@frascone.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [SECMECH] EMU BOF Summary
X-BeenThere: secmech@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security mechanisms BOF <secmech.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/secmech>, <mailto:secmech-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/secmech>
List-Post: <mailto:secmech@lists.ietf.org>
List-Help: <mailto:secmech-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/secmech>, <mailto:secmech-request@lists.ietf.org?subject=subscribe>
Sender: secmech-bounces@lists.ietf.org
Errors-To: secmech-bounces@lists.ietf.org

EAP Method Update (EMU) BOF
Thursday, November 10, 2005
9:00 - 11:00 AM

This was a continuation of the SECMECH BOF from last IETF, but it
focused on the EAP method standardization work item.  The goal of the
BOF was to determine if there was interest to work on the
standardization of a small number of EAP methods.  There were
presentations on requirements for EAP methods and different types of
methods.  We had a discussion on the different types of credentials and
authentication infrastructures that methods can support.  In the end we
reached consensus to create a working group to look at three things: 

(1) an update of EAP-TLS for certificate-based infrastructure 
(2) a method based on strong shared secrets
(3) a method based on using existing password infrastructure such as AAA
servers password databases

It would be better if some of these requirements could be combined into
one mechanism, however it was brought up that this may not be possible
to do and still maintain compact mechanism implementations that are
usable in constrained environments.  After these work items are done it
will be possible to add additional items to the working group charter to
work on additional methods.  The meeting concluded with presentations on
several EAP method drafts.



 

_______________________________________________
SECMECH mailing list
SECMECH@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/secmech