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

"Glen Zorn \(gwz\)" <gwz@cisco.com> Tue, 14 August 2007 17:19 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 1IL03a-0003pZ-LM; Tue, 14 Aug 2007 13:19:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IL03Y-0003iu-IS for emu@ietf.org; Tue, 14 Aug 2007 13:19:48 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IL03X-0004QH-Uo for emu@ietf.org; Tue, 14 Aug 2007 13:19:48 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 14 Aug 2007 10:19:47 -0700
X-IronPort-AV: i="4.19,260,1183359600"; d="scan'208,217"; a="13401791:sNHT53425650"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7EHJlRc025296; Tue, 14 Aug 2007 10:19:47 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l7EHJjiX019815; Tue, 14 Aug 2007 17:19:46 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Aug 2007 10:19:15 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Emu] Crypto-binding in TTLS-v0
Date: Tue, 14 Aug 2007 10:15:12 -0700
Message-ID: <4C0FAAC489C8B74F96BEAD85EAEB262504C8A9DB@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Emu] Crypto-binding in TTLS-v0
Thread-Index: AcfektHlqYJtCHKQTmWGDfbawFh6qAAA9ps9
References: <46C16AE9.6080208@qualcomm.com> <0D22E3C1A7D7A843B12BF8C6F0A40758024045E0@MCHP7IDA.ww002.siemens.net> <A6398B0DB62A474C82F61554EE937287039C8187@proton.jnpr.net> <46C1DC96.7020607@deployingradius.com>
From: "Glen Zorn (gwz)" <gwz@cisco.com>
To: Alan DeKok <aland@deployingradius.com>, Stephen Hanna <shanna@juniper.net>
X-OriginalArrivalTime: 14 Aug 2007 17:19:15.0327 (UTC) FILETIME=[3D4D90F0:01C7DE97]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3835; t=1187111987; x=1187975987; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=gwz@cisco.com; z=From:=20=22Glen=20Zorn=20\(gwz\)=22=20<gwz@cisco.com> |Subject:=20RE=3A=20[Emu]=20Crypto-binding=20in=20TTLS-v0 |Sender:=20; bh=GcNSdNUXf46j03HqkH2q/G3APCiDMvGrbwlmiAYUZCg=; b=Oz0ZnsuTMZgp/KrxF4mSkJ9v6ECGgHq1ASe5bvYgBO344E4l791058+8DEi8wa8zwfEJEpDf P514LWpAu1DyJwTUdgQwMe0IhxJ/VDr5lQFbnRZLha9XeUOifLWOqdHE;
Authentication-Results: sj-dkim-2; header.From=gwz@cisco.com; dkim=pass (sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: 1.8 (+)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: emu@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============0399332146=="
Errors-To: emu-bounces@ietf.org

Stephen Hanna wrote:
> 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.

  I think this document should be published.  It's widely used, and
deserves documentation in the IETF process.
 
gwz> I agree, no matter what the outcome of our discussions here may be.

> 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. 
 
gwz > I thought that the new method had already been defined by a design team?
 
> The results of a hum were
> inconclusive and it was agreed to take this discussion
> to the email list.

  I am in favor of EAP-TTLSv0 + new AVP's.
 
gwz> Ditto. 
 
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www1.ietf.org/mailman/listinfo/emu