RE: [SECMECH] Desire to standardize some specific EAP mechanisms
"Salowey, Joe" <jsalowey@cisco.com> Fri, 15 July 2005 05:04 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtINV-0006Ha-Gx; Fri, 15 Jul 2005 01:04:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtINU-0006Fy-2e for secmech@megatron.ietf.org; Fri, 15 Jul 2005 01:04:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09529 for <secmech@ietf.org>; Fri, 15 Jul 2005 01:04:46 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtIqD-0008A7-Q8 for secmech@ietf.org; Fri, 15 Jul 2005 01:34:31 -0400
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 14 Jul 2005 22:04:37 -0700
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 j6F54ZVX009136; Thu, 14 Jul 2005 22:04:35 -0700 (PDT)
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
Subject: RE: [SECMECH] Desire to standardize some specific EAP mechanisms
Date: Thu, 14 Jul 2005 22:09:01 -0700
Message-ID: <7210B31550AC934A8637D6619739CE69058234E4@e2k-sea-xch2.sea-alpha.cisco.com>
Thread-Topic: [SECMECH] Desire to standardize some specific EAP mechanisms
Thread-Index: AcWIvs3YZxMeWxAtS5imR58m5Cv80wAOohcA
From: "Salowey, Joe" <jsalowey@cisco.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, secmech@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: quoted-printable
Cc:
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
I think this could be a reasonable approach, although I would like to see the work of standardizing specific mechanisms and work to generalize methods start in parallel. As far as mechanisms go I think it is relatively important to get a revision of EAP-TLS into the standards track. Through the use of TLS you can cover X.509 and pre-shared key credentials. I think there is also interest in the EAP community to standardize additional pre-shared key mechanisms (EAP-PSK, EAP-PAX) and tunneled methods (PEAP, TTLS, EAP-FAST). Joe _______________________________________________ SECMECH mailing list SECMECH@lists.ietf.org https://www1.ietf.org/mailman/listinfo/secmech
- [SECMECH] Desire to standardize some specific EAP… Sam Hartman
- RE: [SECMECH] Desire to standardize some specific… Salowey, Joe
- Re: [SECMECH] Desire to standardize some specific… T. Charles Clancy