RE: [Emu] Crypto-binding in TTLS-v0

"Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com> Tue, 14 August 2007 18:18 UTC

Return-path: <emu-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IL0yC-0006hT-9I; Tue, 14 Aug 2007 14:18:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IL0yA-0006YF-W4 for emu@ietf.org; Tue, 14 Aug 2007 14:18:19 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IL0yA-0005pi-AY for emu@ietf.org; Tue, 14 Aug 2007 14:18:18 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 14 Aug 2007 11:18:18 -0700
X-IronPort-AV: i="4.19,260,1183359600"; d="scan'208"; a="392183349:sNHT59283434"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7EIIHU8018046; Tue, 14 Aug 2007 11:18:17 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7EIICW3019882; Tue, 14 Aug 2007 18:18:17 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Aug 2007 11:18:15 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Emu] Crypto-binding in TTLS-v0
Date: Tue, 14 Aug 2007 11:18:18 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5044ECE60@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <A6398B0DB62A474C82F61554EE937287039C8187@proton.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Emu] Crypto-binding in TTLS-v0
Thread-Index: AcfeT8Y0UGe2oNj9QRu8QvymHLxLgQAEWTNwAABh35AABVLdYAAHrKSQ
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Stephen Hanna <shanna@juniper.net>, "Tschofenig, Hannes" <hannes.tschofenig@nsn.com>, Lakshminath Dondeti <ldondeti@qualcomm.com>, emu@ietf.org
X-OriginalArrivalTime: 14 Aug 2007 18:18:15.0500 (UTC) FILETIME=[7B6918C0:01C7DE9F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4174; t=1187115497; x=1187979497; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jsalowey@cisco.com; z=From:=20=22Joseph=20Salowey=20\(jsalowey\)=22=20<jsalowey@cisco.com> |Subject:=20RE=3A=20[Emu]=20Crypto-binding=20in=20TTLS-v0 |Sender:=20; bh=MER+DeQCymteNmQ57k2bPnEW3G4KCFxb8NsynGbbaw8=; b=MJfYjqz1RKhDiy0bZm+VV1uhQ194OCnu6Rs8Bi79UpSoDLmhSmSlF7Uph/sBiI6xJUFVWPFP nLEbe9R2jnl6RaieCsDhj2MyRIzIl2xBjoUp38RJs0fMOtKc6sLUiVuK2HDDU+SGyYilOdK1tU uwHjDprkaVOdH2a5pd04ErchI=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc:
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
Errors-To: emu-bounces@ietf.org

Inline below: 

> -----Original Message-----
> From: Stephen Hanna [mailto:shanna@juniper.net] 
> Sent: Tuesday, August 14, 2007 6:53 AM
> To: Tschofenig, Hannes; Lakshminath Dondeti; emu@ietf.org
> Subject: RE: [Emu] Crypto-binding in TTLS-v0
> 
> Perhaps a little clarification or correction is in order here.
> 
> draft-funk-eap-ttls-v0-01.txt describes EAP-TTLSv0 as it has 
> been implemented by vendors and adopted by other SDOs. We 
> plan to submit this for RFC status as part of the ongoing 
> effort to document popular EAP methods as RFCs.
> 
 > As I described in my presentation at EMU in Chicago, we are 
> working on an Internet-Draft that describes a few AVPs for 
> use with EAP-TTLSv0 that allow it to address all the 
> requirements the EMU WG has laid out for a strong 
> password-based method.
> I expect to have this Internet-Draft ready in the next week or two.
> 
[Joe] good.

> As to your question about whether EAP-TTLSv0 is a chartered 
> work item for the EMU WG, that may depend in part on how the 
> WG decides to address the work item to deliver a strong 
> password-based method. At the EMU WG in Chicago, there were 
> two proposals: my proposal to use EAP-TTLSv0 with these new 
> AVPs and another proposal to define a new EAP method 
> especially for this purpose. The results of a hum were 
> inconclusive and it was agreed to take this discussion to the 
> email list.
> 
[Joe] Yes, there were at least two hums that need to be validated on the list.  I'll get those notes out today. 

> If the WG decides to use EAP-TTLSv0 to address the work item 
> related to delivering a strong password-based method, then I 
> think that EAP-TTLSv0 and the new AVPs would not be work 
> items for the EMU WG but the work item would instead be the 
> creation of a profile showing how to use EAP-TTLSv0 and the 
> new AVPs to provide a strong password-based method.
> 
[Joe] Maybe, but it is possible that a profile will not meet the charter item.  Also, it seems that  the AVPs that form a protocol that solves the problems of password authentication, password change, internationalization, etc. could be considered to be within the scope of the working group charter.   

> Joe, is that consistent with your current thinking?
> 
> Thanks,
> 
> Steve
> 
> -----Original Message-----
> From: Tschofenig, Hannes [mailto:hannes.tschofenig@nsn.com]
> Sent: Tuesday, August 14, 2007 7:03 AM
> To: Lakshminath Dondeti; emu@ietf.org
> Subject: AW: [Emu] Crypto-binding in TTLS-v0
> 
> Crypto-binding: Yes (my opinion)
> 
> Sam also suggested to add channel bindings and to address 
> internalization support in a proper way. 
> 
> Regarding your other question: No. EAP-TTLS is not a charter 
> item since the work on password-based protocols currently 
> does not include tunneled EAP protocols. This was discussed 
> during the meeting. 
> 
> It was also mentioned that the fans of EAP-TTLS would like to 
> publish their EAP-TTLSv0 as is -- without any modifications. 
> 
> Ciao
> Hannes
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Lakshminath Dondeti [mailto:ldondeti@qualcomm.com]
> > Gesendet: Dienstag, 14. August 2007 10:42
> > An: emu@ietf.org
> > Betreff: [Emu] Crypto-binding in TTLS-v0
> > 
> > This probably has been asked before, but I will ask it in a 
> different
> > context: as we try to standardize EAP-TTLS in EMU (is this  
> a charter 
> > item, Joe?) is there a plan to support cryto-binding in TTLS-v0?
> > 
> > My opinion: well, yeah! :)
> > 
> > regards,
> > Lakshminath
> > 
> > _______________________________________________
> > Emu mailing list
> > Emu@ietf.org
> > https://www1.ietf.org/mailman/listinfo/emu
> > 
> 
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www1.ietf.org/mailman/listinfo/emu
> 
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www1.ietf.org/mailman/listinfo/emu
> 

_______________________________________________
Emu mailing list
Emu@ietf.org
https://www1.ietf.org/mailman/listinfo/emu