From mailman-bounces@core3.amsl.com  Fri Feb  1 05:38:40 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1702228DE7B
	for <ietfarch-emu-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wCz6Q2mtDJdk for <ietfarch-emu-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:37:50 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A8E228C86C
	for <emu-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:11:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: emu-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.13213.1201871002.31733.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:03:22 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/emu/emu-archive%40megatron.ietf.org
From mailman-bounces@core3.amsl.com  Fri Feb  1 05:40:50 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB10528C876
	for <ietfarch-emu-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:37:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SZppwBl5ZNIo for <ietfarch-emu-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:37:17 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C5038295908
	for <emu-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:11:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: emu-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.13213.1201871001.31726.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:03:21 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/emu/emu-archive%40megatron.ietf.org
From emu-bounces@ietf.org  Fri Feb  8 09:25:49 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4E2C28C3CA;
	Fri,  8 Feb 2008 09:25:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5
	tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=1,
	RCVD_IN_DNSWL_LOW=-1]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id igWaw9UKrU26; Fri,  8 Feb 2008 09:25:49 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A7C728C396;
	Fri,  8 Feb 2008 09:25:49 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F410D28C38E
	for <emu@core3.amsl.com>; Fri,  8 Feb 2008 09:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RHSye-Q0wZTT for <emu@core3.amsl.com>;
	Fri,  8 Feb 2008 09:25:47 -0800 (PST)
Received: from mail.wrs.com (mail.windriver.com [147.11.1.11])
	by core3.amsl.com (Postfix) with ESMTP id 4B1AA28C386
	for <emu@ietf.org>; Fri,  8 Feb 2008 09:25:47 -0800 (PST)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144])
	by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m18HRGIm007676
	for <emu@ietf.org>; Fri, 8 Feb 2008 09:27:16 -0800 (PST)
Received: from ala-mail02.corp.ad.wrs.com ([147.11.57.56]) by
	ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 8 Feb 2008 09:27:16 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 8 Feb 2008 09:27:15 -0800
Message-ID: <37B62E0F71C9E14B9859FADB1FC3E3E1925F8F@ala-mail02.corp.ad.wrs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Funk SBR and PEAPv1
Thread-Index: Achqd9lLtAjxZ4odTHqt73K9KVGlhw==
From: "Yakan, Medhat" <medhat.yakan@windriver.com>
To: <emu@ietf.org>
X-OriginalArrivalTime: 08 Feb 2008 17:27:16.0596 (UTC)
	FILETIME=[D9B0E340:01C86A77]
Subject: [Emu] Funk SBR and PEAPv1
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1926226286=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1926226286==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86A77.D99FA2E9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86A77.D99FA2E9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I hope this is an appropriate forum to ask this question.
Does anyone know which draft Funk/Juniper uses for their implementation
of PEAPv1 in their SBR product. Also is
"draft-josefsson-pppext-eap-tls-eap-05.txt" considered the defacto draft
for PEAPv1?
Thanks
Medhat

------_=_NextPart_001_01C86A77.D99FA2E9
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D043432317-08022008>I hope =
this is an=20
appropriate forum to ask this question.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D043432317-08022008>Does =
anyone know=20
which draft Funk/Juniper uses for their implementation of PEAPv1 in =
their SBR=20
product. Also is "draft-josefsson-pppext-eap-tls-eap-05.txt" considered =
the=20
defacto draft for PEAPv1?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D043432317-08022008>Thanks</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D043432317-08022008>Medhat</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C86A77.D99FA2E9--

--===============1926226286==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu

--===============1926226286==--


From emu-bounces@ietf.org  Fri Feb  8 15:22:28 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1C9928C70A;
	Fri,  8 Feb 2008 15:22:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[AWL=0.353,
	BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R4TECnauPPw1; Fri,  8 Feb 2008 15:22:27 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C27128C67C;
	Fri,  8 Feb 2008 15:22:25 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D027428C613
	for <emu@core3.amsl.com>; Fri,  8 Feb 2008 15:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hWLP3f8wY3VK for <emu@core3.amsl.com>;
	Fri,  8 Feb 2008 15:22:24 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174])
	by core3.amsl.com (Postfix) with ESMTP id DA79028C65B
	for <emu@ietf.org>; Fri,  8 Feb 2008 15:21:47 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1])
	by colo.trepanning.net (Postfix) with ESMTP id E8FE51FA620B;
	Fri,  8 Feb 2008 15:23:16 -0800 (PST)
Received: from 216.31.249.246
	(SquirrelMail authenticated user dharkins@lounge.org)
	by www.trepanning.net with HTTP; Fri, 8 Feb 2008 15:23:16 -0800 (PST)
Message-ID: <27382.216.31.249.246.1202512996.squirrel@www.trepanning.net>
Date: Fri, 8 Feb 2008 15:23:16 -0800 (PST)
From: "Dan Harkins" <dharkins@lounge.org>
To: emu@ietf.org, eap@frascone.com
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Subject: [Emu] new I-D on password-authenticated EAP method
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org


  Hello,

  There's a new I-D in the Internet-Drafts database called
draft-harkins-emu-eap-pwd-00.txt. It describes a new method
for authentication using only a password. It provides resistance
to active attack, passive attack, and dictionary attack. It
also provides forward secrecy and an authenticated key (not just
a shared key between authenticated entities).

  Please take a look and send comments to the authors.

  regards,

  Dan.



_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Tue Feb 12 08:11:41 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 44FD628C356;
	Tue, 12 Feb 2008 08:11:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.518
X-Spam-Level: 
X-Spam-Status: No, score=-0.518 tagged_above=-999 required=5
	tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0f-51r+7qDgI; Tue, 12 Feb 2008 08:11:39 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1D9628C1EC;
	Tue, 12 Feb 2008 08:11:39 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 59EC728C1EA
	for <emu@core3.amsl.com>; Tue, 12 Feb 2008 08:11:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dX-YJV5d19+C for <emu@core3.amsl.com>;
	Tue, 12 Feb 2008 08:11:36 -0800 (PST)
Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.190])
	by core3.amsl.com (Postfix) with ESMTP id BCA3128C1EC
	for <emu@ietf.org>; Tue, 12 Feb 2008 08:11:36 -0800 (PST)
Received: by rv-out-0910.google.com with SMTP id l15so3389412rvb.49
	for <emu@ietf.org>; Tue, 12 Feb 2008 08:13:01 -0800 (PST)
Received: by 10.141.49.6 with SMTP id b6mr1039291rvk.223.1202832781160;
	Tue, 12 Feb 2008 08:13:01 -0800 (PST)
Received: by 10.141.168.3 with HTTP; Tue, 12 Feb 2008 08:13:01 -0800 (PST)
Message-ID: <5bfe7a820802120813p5a0d9d94h3c69b737f64681c0@mail.gmail.com>
Date: Tue, 12 Feb 2008 08:13:01 -0800
From: "Dorothy Stanley" <dstanley1389@gmail.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50535EAE9@xmb-sjc-225.amer.cisco.com>
MIME-Version: 1.0
References: <AC1CFD94F59A264488DC2BEC3E890DE50535EAE9@xmb-sjc-225.amer.cisco.com>
Cc: emu@ietf.org
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1368838129=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

--===============1368838129==
Content-Type: multipart/alternative; 
	boundary="----=_Part_9970_7337774.1202832781155"

------=_Part_9970_7337774.1202832781155
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Joe,

I have 3 comments, listed below.

Thanks,

Dorothy Stanley
---------------------------

1. 3rd list item:

- A mechanism to support extensible communication within a TLS protected
tunnel that meets RFC 3748 and RFC 4017 requirements. This mechanism
must support channel bindings in order to meet RFC 4962 requirements and
it must provide cryptographic algorithm agility. This mechanism will
support meeting the requirements of an enhanced TLS mechanism, a
password based authentication mechanism, and additional inner
authentication mechanisms.

In the last sentence, "support meeting the requirements of" is somewhat
vague.
What does "support" really mean here? Requirements on the WG in the charter?
requirements of specific methods?

Suggest changing from:

"This mechanism will
support meeting the requirements of an enhanced TLS mechanism, a
password based authentication mechanism, and additional inner
authentication mechanisms."

to

"This mechanism will
provide an enhanced TLS mechanism, a
password based authentication mechanism, and additional inner
authentication mechanisms."

2. List item 5
- A mechanism meeting RFC 3748 and RFC 4017 requirements that makes use
of existing password databases such as AAA databases.  This item will be
based on the tunnel method work item.

Suggest changing the last sentence from

"This item will be
based on the tunnel method work item."

to

"This item may be
based on the tunnel method work item."

This change enables the group to use the tunnelled method to satisfy the
requirement, but does not
eliminate the possibility of using a separate protocol, and maintains a
valid charter in either case.


3. First sentence under "Description"

Suggest changing from

"The Extensible Authentication Protocol (EAP) [RFC 3748] is a network
access authentication framework used in the PPP, 802.11, 802.16, VPN,
PANA, and in some functions in 3G networks."

to

The Extensible Authentication Protocol (EAP) [RFC 3748] is a network
access authentication framework used in the PPP,  IEEE 802.11 and IEEE
802.16
networks, VPNs, PANA, and in some functions in 3G networks."

---------end-of-comments--------------------

On Feb 4, 2008 9:12 PM, Joseph Salowey (jsalowey) <jsalowey@cisco.com>
wrote:

> Below is a revised charter update based on the discussion on the list.
> I have left the password based method item as a tunnel method because
> this represents the consensus the working group has reached.  I also
> believe the working group will have to focus on the tunnel method
> related items for the near term to make progress.  This does not mean
> that we cannot work on additional methods as working group items in the
> future.
>
> Please review the charter update and post any issues you have with the
> carter.  Please also indicate if you have reviewed the proposed charter
> and have no issues.  It is difficult to judge working group consensus
> unless there are sufficient responses.
>
> Thanks,
>
> Joe
>
> Description of Working Group:
> The Extensible Authentication Protocol (EAP) [RFC 3748] is a network
> access authentication framework used in the PPP, 802.11, 802.16, VPN,
> PANA, and in some functions in 3G networks. EAP itself is a simple
> protocol and actual authentication happens in EAP methods.
>
> Over 40 different EAP methods exist. Most of these methods are
> proprietary methods and only a few methods are documented in RFCs. The
> lack of documented, open specifications is a deployment and
> interoperability problem. In addition, none of the EAP methods in the
> standards track implement features such as key derivation that are
> required for many modern applications. This poses a problem for, among
> other things, the selection of a mandatory to implement EAP method in
> new network access technologies. For example, no standards track methods
> meet new requirements such as those posed in RFC 4017, which documents
> IEEE 802.11 requirements for EAP methods.
>
> This group is chartered to work on the following types of mechanisms to
> meet RFC 3748 and RFC 4017 requirements:
>
> - An update to RFC 2716 to bring EAP-TLS into standards track, clarify
> specification, interoperability, and implementation issues gathered over
> the years, and update the document to meet the requirements of RFC 3748,
> RFC 4017, and EAP keying framework documents. Backwards compatibility
> with RFC 2716 is a requirement.
>
> - A mechanism based on strong shared secrets that meets RFC 3748 and RFC
> 4017 requirements. This mechanism should strive to be simple and compact
> for implementation in resource constrained environments.
>
> - A mechanism to support extensible communication within a TLS protected
> tunnel that meets RFC 3748 and RFC 4017 requirements. This mechanism
> must support channel bindings in order to meet RFC 4962 requirements and
> it must provide cryptographic algorithm agility. This mechanism will
> support meeting the requirements of an enhanced TLS mechanism, a
> password based authentication mechanism, and additional inner
> authentication mechanisms.
>
> - Enable a TLS-based EAP method to support channel bindings. So as to
> enable RFC 2716bis to focus solely on clarifications to the existing
> protocol, this effort will be handled in a separate document.  This item
> will not generate a new method, rather it will enhance EAP-TLS or the
> TLS based tunnel method work item.
>
> - A mechanism meeting RFC 3748 and RFC 4017 requirements that makes use
> of existing password databases such as AAA databases.  This item will be
> based on the tunnel method work item.
>
> Goals and Milestones:
> Done            Form design team to work on strong shared secret
> mechanism
> Done            Submit 2716bis I-D
> Done            Submit first draft of shared secret mechanism I-D
> Done            Form password based mechanism design team
> Done            Submit 2716bis draft to IESG for Proposed Standard
> Done    Submit Strong Shared Secret Mechanism to IESG
> Apr 2008        Submit Tunnel and Password Method requirements first
> draft
> Jul 2008        Send Tunnel and Password Method requirements to IESG
> Oct 2008        Submit Tunnel Method first draft
> Nov 2008    Submit TLS based method channel binding first draft
> Nov 2008        Submit Password Method first draft
> Feb 2009        Send Tunnel Method to IESG
> Apr 2009        Send TLS based method channel binding to IESG
> Apr 2009        Send Password based method to IESG
>
>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>

------=_Part_9970_7337774.1202832781155
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Joe,<br><br>I have 3 comments, listed below.<br><br>Thanks,<br><br>Dorothy Stanley<br>---------------------------<br><br>1. 3rd list item:<br><br>- A mechanism to support extensible communication within a TLS protected<br>
tunnel that meets RFC 3748 and RFC 4017 requirements. This mechanism<br>must support channel bindings in order to meet RFC 4962 requirements and<br>it must provide cryptographic algorithm agility. This mechanism will<br>support meeting the requirements of an enhanced TLS mechanism, a<br>
password based authentication mechanism, and additional inner<br>authentication mechanisms.<br><br>In the last sentence, &quot;support meeting the requirements of&quot; is somewhat vague.<br>What does &quot;support&quot; really mean here? Requirements on the WG in the charter? requirements of specific methods?<br>
<br>Suggest changing from:<br><br>&quot;This mechanism will<br>
support meeting the requirements of an enhanced TLS mechanism, a<br>
password based authentication mechanism, and additional inner<br>
authentication mechanisms.&quot;<br><br>to<br><br>&quot;This mechanism will<br>provide an enhanced TLS mechanism, a<br>
password based authentication mechanism, and additional inner<br>
authentication mechanisms.&quot;<br><br>2. List item 5<br>- A mechanism meeting RFC 3748 and RFC 4017 requirements that makes use<br>of existing password databases such as AAA databases. &nbsp;This item will be<br>based on the tunnel method work item.<br>
<br>Suggest changing the last sentence from<br><br>&quot;This item will be<br>
based on the tunnel method work item.&quot;<br><br>to<br><br>&quot;This item may be<br>
based on the tunnel method work item.&quot;<br><br>This change enables the group to use the tunnelled method to satisfy the requirement, but does not<br>eliminate the possibility of using a separate protocol, and maintains a valid charter in either case.<br>
<br><br>3. First sentence under &quot;Description&quot;<br><br>Suggest changing from<br><br>&quot;The Extensible Authentication Protocol (EAP) [RFC 3748] is a network<br>access authentication framework used in the PPP, 802.11, 802.16, VPN,<br>
PANA, and in some functions in 3G networks.&quot;<br><br>to<br><br>The Extensible Authentication Protocol (EAP) [RFC 3748] is a network<br>access authentication framework used in the PPP,&nbsp; IEEE 802.11 and IEEE 802.16<br>networks, VPNs, PANA, and in some functions in 3G networks.&quot;<br>
<br>---------end-of-comments--------------------<br><br><div class="gmail_quote">On Feb 4, 2008 9:12 PM, Joseph Salowey (jsalowey) &lt;<a href="mailto:jsalowey@cisco.com">jsalowey@cisco.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Below is a revised charter update based on the discussion on the list.<br>I have left the password based method item as a tunnel method because<br>this represents the consensus the working group has reached. &nbsp;I also<br>believe the working group will have to focus on the tunnel method<br>
related items for the near term to make progress. &nbsp;This does not mean<br>that we cannot work on additional methods as working group items in the<br>future.<br><br>Please review the charter update and post any issues you have with the<br>
carter. &nbsp;Please also indicate if you have reviewed the proposed charter<br>and have no issues. &nbsp;It is difficult to judge working group consensus<br>unless there are sufficient responses.<br><br>Thanks,<br><br>Joe<br><br>Description of Working Group:<br>
The Extensible Authentication Protocol (EAP) [RFC 3748] is a network<br>access authentication framework used in the PPP, 802.11, 802.16, VPN,<br>PANA, and in some functions in 3G networks. EAP itself is a simple<br>protocol and actual authentication happens in EAP methods.<br>
<br>Over 40 different EAP methods exist. Most of these methods are<br>proprietary methods and only a few methods are documented in RFCs. The<br>lack of documented, open specifications is a deployment and<br>interoperability problem. In addition, none of the EAP methods in the<br>
standards track implement features such as key derivation that are<br>required for many modern applications. This poses a problem for, among<br>other things, the selection of a mandatory to implement EAP method in<br>new network access technologies. For example, no standards track methods<br>
meet new requirements such as those posed in RFC 4017, which documents<br>IEEE 802.11 requirements for EAP methods.<br><br>This group is chartered to work on the following types of mechanisms to<br>meet RFC 3748 and RFC 4017 requirements:<br>
<br>- An update to RFC 2716 to bring EAP-TLS into standards track, clarify<br>specification, interoperability, and implementation issues gathered over<br>the years, and update the document to meet the requirements of RFC 3748,<br>
RFC 4017, and EAP keying framework documents. Backwards compatibility<br>with RFC 2716 is a requirement.<br><br>- A mechanism based on strong shared secrets that meets RFC 3748 and RFC<br>4017 requirements. This mechanism should strive to be simple and compact<br>
for implementation in resource constrained environments.<br><br>- A mechanism to support extensible communication within a TLS protected<br>tunnel that meets RFC 3748 and RFC 4017 requirements. This mechanism<br>must support channel bindings in order to meet RFC 4962 requirements and<br>
it must provide cryptographic algorithm agility. This mechanism will<br>support meeting the requirements of an enhanced TLS mechanism, a<br>password based authentication mechanism, and additional inner<br>authentication mechanisms.<br>
<br>- Enable a TLS-based EAP method to support channel bindings. So as to<br>enable RFC 2716bis to focus solely on clarifications to the existing<br>protocol, this effort will be handled in a separate document. &nbsp;This item<br>
will not generate a new method, rather it will enhance EAP-TLS or the<br>TLS based tunnel method work item.<br><br>- A mechanism meeting RFC 3748 and RFC 4017 requirements that makes use<br>of existing password databases such as AAA databases. &nbsp;This item will be<br>
based on the tunnel method work item.<br><br>Goals and Milestones:<br>Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Form design team to work on strong shared secret<br>mechanism<br>Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submit 2716bis I-D<br>Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submit first draft of shared secret mechanism I-D<br>
Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Form password based mechanism design team<br>Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submit 2716bis draft to IESG for Proposed Standard<br>Done &nbsp; &nbsp;Submit Strong Shared Secret Mechanism to IESG<br>Apr 2008 &nbsp; &nbsp; &nbsp; &nbsp;Submit Tunnel and Password Method requirements first<br>
draft<br>Jul 2008 &nbsp; &nbsp; &nbsp; &nbsp;Send Tunnel and Password Method requirements to IESG<br>Oct 2008 &nbsp; &nbsp; &nbsp; &nbsp;Submit Tunnel Method first draft<br>Nov 2008 &nbsp; &nbsp;Submit TLS based method channel binding first draft<br>Nov 2008 &nbsp; &nbsp; &nbsp; &nbsp;Submit Password Method first draft<br>
Feb 2009 &nbsp; &nbsp; &nbsp; &nbsp;Send Tunnel Method to IESG<br>Apr 2009 &nbsp; &nbsp; &nbsp; &nbsp;Send TLS based method channel binding to IESG<br>Apr 2009 &nbsp; &nbsp; &nbsp; &nbsp;Send Password based method to IESG<br><br><br><br>_______________________________________________<br>
Emu mailing list<br><a href="mailto:Emu@ietf.org">Emu@ietf.org</a><br><a href="http://www.ietf.org/mailman/listinfo/emu" target="_blank">http://www.ietf.org/mailman/listinfo/emu</a><br></blockquote></div><br>

------=_Part_9970_7337774.1202832781155--

--===============1368838129==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu

--===============1368838129==--


From emu-bounces@ietf.org  Tue Feb 12 15:03:11 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BCFC28C3E3;
	Tue, 12 Feb 2008 15:03:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.359
X-Spam-Level: 
X-Spam-Status: No, score=-3.359 tagged_above=-999 required=5
	tests=[AWL=-2.922, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Yza+rKIaAM-8; Tue, 12 Feb 2008 15:03:09 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC8893A6E8F;
	Tue, 12 Feb 2008 15:03:09 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B27F63A6E8D
	for <emu@core3.amsl.com>; Tue, 12 Feb 2008 15:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Os0QEeGtou1F for <emu@core3.amsl.com>;
	Tue, 12 Feb 2008 15:03:07 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 567233A6E8F
	for <emu@ietf.org>; Tue, 12 Feb 2008 15:03:07 -0800 (PST)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 12 Feb 2008 15:04:30 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m1CN4UK1029259; 
	Tue, 12 Feb 2008 15:04:30 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1CN4TJQ004489;
	Tue, 12 Feb 2008 23:04:30 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, 12 Feb 2008 15:04:29 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 12 Feb 2008 15:05:12 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE505449836@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <5bfe7a820802120813p5a0d9d94h3c69b737f64681c0@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] EMU charter revision
Thread-Index: Achtkif80Jlv+qf9QveVfDvU/3gmCgALCVyA
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Dorothy Stanley" <dstanley1389@gmail.com>
X-OriginalArrivalTime: 12 Feb 2008 23:04:29.0690 (UTC)
	FILETIME=[9F3505A0:01C86DCB]
Authentication-Results: sj-dkim-4; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: emu@ietf.org
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Hi Dorothy,

Thanks for reviewing the charter.  I agree with your comments 1 and 3.
With regard to 2 the working group has already made the decision to use
a tunnel method for this item.  I believe that the proposal Dan recently
submitted is addressing a different set of requirements than this item
intends.  In the case of the current charter item it cannot be assumed
that the server has access to the raw password or even a consistent
transform of the password in order to interact with legacy databases.
Dan will be able to present his ideas in Philadelphia and we can
determine if there is working group interest in pursuing a method of
this type. 

Cheers,

Joe

> -----Original Message-----
> From: Dorothy Stanley [mailto:dstanley1389@gmail.com] 
> Sent: Tuesday, February 12, 2008 8:13 AM
> To: Joseph Salowey (jsalowey)
> Cc: emu@ietf.org
> Subject: Re: [Emu] EMU charter revision
> 
> Hi Joe,
> 
> I have 3 comments, listed below.
> 
> Thanks,
> 
> Dorothy Stanley
> ---------------------------
> 
> 1. 3rd list item:
> 
> - A mechanism to support extensible communication within a 
> TLS protected tunnel that meets RFC 3748 and RFC 4017 
> requirements. This mechanism must support channel bindings in 
> order to meet RFC 4962 requirements and it must provide 
> cryptographic algorithm agility. This mechanism will support 
> meeting the requirements of an enhanced TLS mechanism, a 
> password based authentication mechanism, and additional inner 
> authentication mechanisms.
> 
> In the last sentence, "support meeting the requirements of" 
> is somewhat vague.
> What does "support" really mean here? Requirements on the WG 
> in the charter? requirements of specific methods?
> 
> Suggest changing from:
> 
> "This mechanism will
> support meeting the requirements of an enhanced TLS 
> mechanism, a password based authentication mechanism, and 
> additional inner authentication mechanisms."
> 
> to
> 
> "This mechanism will
> provide an enhanced TLS mechanism, a
> password based authentication mechanism, and additional inner 
> authentication mechanisms."
> 
> 2. List item 5
> - A mechanism meeting RFC 3748 and RFC 4017 requirements that 
> makes use of existing password databases such as AAA 
> databases.  This item will be based on the tunnel method work item.
> 
> Suggest changing the last sentence from
> 
> "This item will be
> based on the tunnel method work item."
> 
> to
> 
> "This item may be
> based on the tunnel method work item."
> 
> This change enables the group to use the tunnelled method to 
> satisfy the requirement, but does not eliminate the 
> possibility of using a separate protocol, and maintains a 
> valid charter in either case.
> 
> 
> 3. First sentence under "Description"
> 
> Suggest changing from
> 
> "The Extensible Authentication Protocol (EAP) [RFC 3748] is a 
> network access authentication framework used in the PPP, 
> 802.11, 802.16, VPN, PANA, and in some functions in 3G networks."
> 
> to
> 
> The Extensible Authentication Protocol (EAP) [RFC 3748] is a 
> network access authentication framework used in the PPP,  
> IEEE 802.11 and IEEE 802.16 networks, VPNs, PANA, and in some 
> functions in 3G networks."
> 
> ---------end-of-comments--------------------
> 
> 
> On Feb 4, 2008 9:12 PM, Joseph Salowey (jsalowey) 
> <jsalowey@cisco.com> wrote:
> 
> 
> 	Below is a revised charter update based on the 
> discussion on the list.
> 	I have left the password based method item as a tunnel 
> method because
> 	this represents the consensus the working group has 
> reached.  I also
> 	believe the working group will have to focus on the 
> tunnel method
> 	related items for the near term to make progress.  This 
> does not mean
> 	that we cannot work on additional methods as working 
> group items in the
> 	future.
> 	
> 	Please review the charter update and post any issues 
> you have with the
> 	carter.  Please also indicate if you have reviewed the 
> proposed charter
> 	and have no issues.  It is difficult to judge working 
> group consensus
> 	unless there are sufficient responses.
> 	
> 	Thanks,
> 	
> 	Joe
> 	
> 	Description of Working Group:
> 	The Extensible Authentication Protocol (EAP) [RFC 3748] 
> is a network
> 	access authentication framework used in the PPP, 
> 802.11, 802.16, VPN,
> 	PANA, and in some functions in 3G networks. EAP itself 
> is a simple
> 	protocol and actual authentication happens in EAP methods.
> 	
> 	Over 40 different EAP methods exist. Most of these methods are
> 	proprietary methods and only a few methods are 
> documented in RFCs. The
> 	lack of documented, open specifications is a deployment and
> 	interoperability problem. In addition, none of the EAP 
> methods in the
> 	standards track implement features such as key 
> derivation that are
> 	required for many modern applications. This poses a 
> problem for, among
> 	other things, the selection of a mandatory to implement 
> EAP method in
> 	new network access technologies. For example, no 
> standards track methods
> 	meet new requirements such as those posed in RFC 4017, 
> which documents
> 	IEEE 802.11 requirements for EAP methods.
> 	
> 	This group is chartered to work on the following types 
> of mechanisms to
> 	meet RFC 3748 and RFC 4017 requirements:
> 	
> 	- An update to RFC 2716 to bring EAP-TLS into standards 
> track, clarify
> 	specification, interoperability, and implementation 
> issues gathered over
> 	the years, and update the document to meet the 
> requirements of RFC 3748,
> 	RFC 4017, and EAP keying framework documents. Backwards 
> compatibility
> 	with RFC 2716 is a requirement.
> 	
> 	- A mechanism based on strong shared secrets that meets 
> RFC 3748 and RFC
> 	4017 requirements. This mechanism should strive to be 
> simple and compact
> 	for implementation in resource constrained environments.
> 	
> 	- A mechanism to support extensible communication 
> within a TLS protected
> 	tunnel that meets RFC 3748 and RFC 4017 requirements. 
> This mechanism
> 	must support channel bindings in order to meet RFC 4962 
> requirements and
> 	it must provide cryptographic algorithm agility. This 
> mechanism will
> 	support meeting the requirements of an enhanced TLS mechanism, a
> 	password based authentication mechanism, and additional inner
> 	authentication mechanisms.
> 	
> 	- Enable a TLS-based EAP method to support channel 
> bindings. So as to
> 	enable RFC 2716bis to focus solely on clarifications to 
> the existing
> 	protocol, this effort will be handled in a separate 
> document.  This item
> 	will not generate a new method, rather it will enhance 
> EAP-TLS or the
> 	TLS based tunnel method work item.
> 	
> 	- A mechanism meeting RFC 3748 and RFC 4017 
> requirements that makes use
> 	of existing password databases such as AAA databases.  
> This item will be
> 	based on the tunnel method work item.
> 	
> 	Goals and Milestones:
> 	Done            Form design team to work on strong shared secret
> 	mechanism
> 	Done            Submit 2716bis I-D
> 	Done            Submit first draft of shared secret 
> mechanism I-D
> 	Done            Form password based mechanism design team
> 	Done            Submit 2716bis draft to IESG for 
> Proposed Standard
> 	Done    Submit Strong Shared Secret Mechanism to IESG
> 	Apr 2008        Submit Tunnel and Password Method 
> requirements first
> 	draft
> 	Jul 2008        Send Tunnel and Password Method 
> requirements to IESG
> 	Oct 2008        Submit Tunnel Method first draft
> 	Nov 2008    Submit TLS based method channel binding first draft
> 	Nov 2008        Submit Password Method first draft
> 	Feb 2009        Send Tunnel Method to IESG
> 	Apr 2009        Send TLS based method channel binding to IESG
> 	Apr 2009        Send Password based method to IESG
> 	
> 	
> 	
> 	_______________________________________________
> 	Emu mailing list
> 	Emu@ietf.org
> 	http://www.ietf.org/mailman/listinfo/emu
> 	
> 
> 
> 
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Thu Feb 14 08:51:34 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A70F3A70B2;
	Thu, 14 Feb 2008 08:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level: 
X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5
	tests=[AWL=-2.572, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id a3pM55fSUtjR; Thu, 14 Feb 2008 08:51:33 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D13B3A7096;
	Thu, 14 Feb 2008 08:51:33 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF5333A709A
	for <emu@core3.amsl.com>; Thu, 14 Feb 2008 08:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sn4Vk92fhc7i for <emu@core3.amsl.com>;
	Thu, 14 Feb 2008 08:51:31 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id BE4113A7087
	for <emu@ietf.org>; Thu, 14 Feb 2008 08:51:29 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 14 Feb 2008 08:52:51 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1EGqoMH016794; 
	Thu, 14 Feb 2008 08:52:50 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m1EGqiPx008486;
	Thu, 14 Feb 2008 16:52:49 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Feb 2008 08:52:47 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 14 Feb 2008 08:53:30 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE505449F11@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <001701c86f15$d5b75f60$81261e20$@fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eap] new eap method
Thread-Index: AchvFdUCiRxkUfJORj6o5q91K3LsaAAE5eRg
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Vamsi Krishna Gondi" <gondi@ensiie.fr>, <emu@ietf.org>
X-OriginalArrivalTime: 14 Feb 2008 16:52:47.0062 (UTC)
	FILETIME=[06A18F60:01C86F2A]
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: hokey-chairs@tools.ietf.org
Subject: Re: [Emu] [eap] new eap method
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Hi Gondi, 

I think proposals on handover are better evaluated in the HOKEY
(Handover Keying) working group, which is currently working in this
problem space.   

Cheers,

Joe

> -----Original Message-----
> From: Vamsi Krishna Gondi [mailto:gondi@ensiie.fr] 
> Sent: Thursday, February 14, 2008 6:28 AM
> To: eap@frascone.com
> Subject: [eap] new eap method
> 
> Dear All,
> 
>  
> 
> I am currently working on new EAP method for roaming and 
> handover support. I want to propose my work as draft and 
> present in IETF 71 WG meeting. If anyone can please let me 
> know about the relevance of my work regarding this WG or can 
> you please propose any another WG for EAP methods.
> 
>  
> 
> Thanking you,
> 
> Gondi.
> 
> 
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Tue Feb 19 11:14:07 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D521F3A6AF5;
	Tue, 19 Feb 2008 11:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.744
X-Spam-Level: 
X-Spam-Status: No, score=-2.744 tagged_above=-999 required=5
	tests=[AWL=-2.307, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id l6+U7NAm0yfL; Tue, 19 Feb 2008 11:14:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C99A628C38D;
	Tue, 19 Feb 2008 11:14:03 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 982A628C38D
	for <emu@core3.amsl.com>; Tue, 19 Feb 2008 11:14:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s6MW-BHbTG0a for <emu@core3.amsl.com>;
	Tue, 19 Feb 2008 11:14:01 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id C07783A6996
	for <emu@ietf.org>; Tue, 19 Feb 2008 11:14:00 -0800 (PST)
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-6.cisco.com with ESMTP; 19 Feb 2008 11:13:58 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id m1JJDwoQ028429
	for <emu@ietf.org>; Tue, 19 Feb 2008 11:13:58 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1JJDvJg006605
	for <emu@ietf.org>; Tue, 19 Feb 2008 19:13:58 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, 19 Feb 2008 11:13:57 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Feb 2008 11:14:42 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: EMU charter revision
Thread-Index: AchntbzKn+eyM5+SQUmVlu0CjWYhAQLbDypg
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
X-OriginalArrivalTime: 19 Feb 2008 19:13:57.0758 (UTC)
	FILETIME=[939FF1E0:01C8732B]
Authentication-Results: sj-dkim-7; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

The response to the charter revision has been underwhelming.  I am a bit
concerned that we do not have enough participation to complete the
tunnel method work (most of the recent discussion has been about other
methods).  

I would like to get an idea of the number working group members that
approve of working on the tunnel method items and are able to
participate in the development of requirements and specifications as
contributors and/or reviewers.  

Please respond to this message and state whether you approve of the
current charter revision and what capacity you would be willing to
contribute towards tunneled method development: contributor, reviewer or
not able to contribute.  

I have submitted an internet draft attempt at an outline of requirements
for tunneled methods
(http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
txt) that I hope can provided a starting point for discussions on the
list and in the Philadelphia meeting.  

Thanks,

Joe

> -----Original Message-----
> From: Joseph Salowey (jsalowey) 
> Sent: Monday, February 04, 2008 9:13 PM
> To: emu@ietf.org
> Subject: EMU charter revision
> 
> Below is a revised charter update based on the discussion on 
> the list.  I have left the password based method item as a 
> tunnel method because this represents the consensus the 
> working group has reached.  I also believe the working group 
> will have to focus on the tunnel method related items for the 
> near term to make progress.  This does not mean that we 
> cannot work on additional methods as working group items in 
> the future.   
> 
> Please review the charter update and post any issues you have 
> with the carter.  Please also indicate if you have reviewed 
> the proposed charter and have no issues.  It is difficult to 
> judge working group consensus unless there are sufficient responses. 
> 
> Thanks,
> 
> Joe
> 
> Description of Working Group:
> The Extensible Authentication Protocol (EAP) [RFC 3748] is a 
> network access authentication framework used in the PPP, 
> 802.11, 802.16, VPN, PANA, and in some functions in 3G 
> networks. EAP itself is a simple protocol and actual 
> authentication happens in EAP methods.
> 
> Over 40 different EAP methods exist. Most of these methods 
> are proprietary methods and only a few methods are documented 
> in RFCs. The lack of documented, open specifications is a 
> deployment and interoperability problem. In addition, none of 
> the EAP methods in the standards track implement features 
> such as key derivation that are required for many modern 
> applications. This poses a problem for, among other things, 
> the selection of a mandatory to implement EAP method in new 
> network access technologies. For example, no standards track 
> methods meet new requirements such as those posed in RFC 
> 4017, which documents IEEE 802.11 requirements for EAP methods.
> 
> This group is chartered to work on the following types of 
> mechanisms to meet RFC 3748 and RFC 4017 requirements:
> 
> - An update to RFC 2716 to bring EAP-TLS into standards 
> track, clarify specification, interoperability, and 
> implementation issues gathered over the years, and update the 
> document to meet the requirements of RFC 3748, RFC 4017, and 
> EAP keying framework documents. Backwards compatibility with 
> RFC 2716 is a requirement.
> 
> - A mechanism based on strong shared secrets that meets RFC 
> 3748 and RFC 4017 requirements. This mechanism should strive 
> to be simple and compact for implementation in resource 
> constrained environments.
> 
> - A mechanism to support extensible communication within a 
> TLS protected tunnel that meets RFC 3748 and RFC 4017 
> requirements. This mechanism must support channel bindings in 
> order to meet RFC 4962 requirements and it must provide 
> cryptographic algorithm agility. This mechanism will support 
> meeting the requirements of an enhanced TLS mechanism, a 
> password based authentication mechanism, and additional inner 
> authentication mechanisms.
> 
> - Enable a TLS-based EAP method to support channel bindings. 
> So as to enable RFC 2716bis to focus solely on clarifications 
> to the existing protocol, this effort will be handled in a 
> separate document.  This item will not generate a new method, 
> rather it will enhance EAP-TLS or the TLS based tunnel method 
> work item.  
> 
> - A mechanism meeting RFC 3748 and RFC 4017 requirements that 
> makes use of existing password databases such as AAA 
> databases.  This item will be based on the tunnel method work item.
> 
> Goals and Milestones:
> Done	  	Form design team to work on strong shared 
> secret mechanism
> Done	  	Submit 2716bis I-D
> Done	  	Submit first draft of shared secret mechanism I-D
> Done	  	Form password based mechanism design team
> Done		Submit 2716bis draft to IESG for Proposed Standard
> Done   	Submit Strong Shared Secret Mechanism to IESG
> Apr 2008 	Submit Tunnel and Password Method requirements 
> first draft
> Jul 2008 	Send Tunnel and Password Method requirements to IESG
> Oct 2008 	Submit Tunnel Method first draft
> Nov 2008    Submit TLS based method channel binding first draft
> Nov 2008 	Submit Password Method first draft
> Feb 2009	Send Tunnel Method to IESG
> Apr 2009	Send TLS based method channel binding to IESG
> Apr 2009	Send Password based method to IESG
> 
> 
> 
> 
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Tue Feb 19 11:41:34 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1ED3D3A679C;
	Tue, 19 Feb 2008 11:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.518
X-Spam-Level: 
X-Spam-Status: No, score=-3.518 tagged_above=-999 required=5
	tests=[AWL=-3.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id E5e5yPGurB5J; Tue, 19 Feb 2008 11:41:33 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F262F28C653;
	Tue, 19 Feb 2008 11:41:32 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 261983A68A2
	for <emu@core3.amsl.com>; Tue, 19 Feb 2008 11:41:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id A0-BJhJqaYGa for <emu@core3.amsl.com>;
	Tue, 19 Feb 2008 11:41:29 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id C138B28C653
	for <emu@ietf.org>; Tue, 19 Feb 2008 11:41:28 -0800 (PST)
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 19 Feb 2008 14:41:25 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1JJfPGo003398
	for <emu@ietf.org>; Tue, 19 Feb 2008 14:41:25 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m1JJf5Wb013461
	for <emu@ietf.org>; Tue, 19 Feb 2008 19:41:25 GMT
Received: from xmb-rtp-212.amer.cisco.com ([64.102.31.111]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Feb 2008 14:41:12 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Feb 2008 14:42:45 -0500
Message-ID: <9958B444368E884DBB215F3FEF36F5B7064C0B7D@xmb-rtp-212.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] EMU charter revision
Thread-Index: AchntbzKn+eyM5+SQUmVlu0CjWYhAQLbDypgAANiCdA=
References: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
From: "Hao Zhou (hzhou)" <hzhou@cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
X-OriginalArrivalTime: 19 Feb 2008 19:41:12.0537 (UTC)
	FILETIME=[62076C90:01C8732F]
Authentication-Results: rtp-dkim-2; header.From=hzhou@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Joe:

I approve the current charter revision and am willing to contribute to
the tunnel method. 

> -----Original Message-----
> From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On 
> Behalf Of Joseph Salowey (jsalowey)
> Sent: Tuesday, February 19, 2008 2:15 PM
> To: Joseph Salowey (jsalowey); emu@ietf.org
> Subject: Re: [Emu] EMU charter revision
> 
> The response to the charter revision has been underwhelming.  
> I am a bit concerned that we do not have enough participation 
> to complete the tunnel method work (most of the recent 
> discussion has been about other methods).  
> 
> I would like to get an idea of the number working group 
> members that approve of working on the tunnel method items 
> and are able to participate in the development of 
> requirements and specifications as contributors and/or reviewers.  
> 
> Please respond to this message and state whether you approve 
> of the current charter revision and what capacity you would 
> be willing to contribute towards tunneled method development: 
> contributor, reviewer or not able to contribute.  
> 
> I have submitted an internet draft attempt at an outline of 
> requirements for tunneled methods 
> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunn
> el-req-00.
> txt) that I hope can provided a starting point for 
> discussions on the list and in the Philadelphia meeting.  
> 
> Thanks,
> 
> Joe
> 
> > -----Original Message-----
> > From: Joseph Salowey (jsalowey)
> > Sent: Monday, February 04, 2008 9:13 PM
> > To: emu@ietf.org
> > Subject: EMU charter revision
> > 
> > Below is a revised charter update based on the discussion 
> on the list.  
> > I have left the password based method item as a tunnel 
> method because 
> > this represents the consensus the working group has 
> reached.  I also 
> > believe the working group will have to focus on the tunnel method 
> > related items for the near term to make progress.  This 
> does not mean 
> > that we cannot work on additional methods as working group items in
> > the future.   
> > 
> > Please review the charter update and post any issues you 
> have with the 
> > carter.  Please also indicate if you have reviewed the proposed 
> > charter and have no issues.  It is difficult to judge working group 
> > consensus unless there are sufficient responses.
> > 
> > Thanks,
> > 
> > Joe
> > 
> > Description of Working Group:
> > The Extensible Authentication Protocol (EAP) [RFC 3748] is 
> a network 
> > access authentication framework used in the PPP, 802.11, 
> 802.16, VPN, 
> > PANA, and in some functions in 3G networks. EAP itself is a simple 
> > protocol and actual authentication happens in EAP methods.
> > 
> > Over 40 different EAP methods exist. Most of these methods are 
> > proprietary methods and only a few methods are documented 
> in RFCs. The 
> > lack of documented, open specifications is a deployment and 
> > interoperability problem. In addition, none of the EAP 
> methods in the 
> > standards track implement features such as key derivation that are 
> > required for many modern applications. This poses a problem 
> for, among 
> > other things, the selection of a mandatory to implement EAP 
> method in 
> > new network access technologies. For example, no standards track 
> > methods meet new requirements such as those posed in RFC 
> 4017, which 
> > documents IEEE 802.11 requirements for EAP methods.
> > 
> > This group is chartered to work on the following types of 
> mechanisms 
> > to meet RFC 3748 and RFC 4017 requirements:
> > 
> > - An update to RFC 2716 to bring EAP-TLS into standards 
> track, clarify 
> > specification, interoperability, and implementation issues gathered 
> > over the years, and update the document to meet the requirements of 
> > RFC 3748, RFC 4017, and EAP keying framework documents. Backwards 
> > compatibility with RFC 2716 is a requirement.
> > 
> > - A mechanism based on strong shared secrets that meets RFC
> > 3748 and RFC 4017 requirements. This mechanism should strive to be 
> > simple and compact for implementation in resource constrained 
> > environments.
> > 
> > - A mechanism to support extensible communication within a TLS 
> > protected tunnel that meets RFC 3748 and RFC 4017 
> requirements. This 
> > mechanism must support channel bindings in order to meet RFC 4962 
> > requirements and it must provide cryptographic algorithm 
> agility. This 
> > mechanism will support meeting the requirements of an enhanced TLS 
> > mechanism, a password based authentication mechanism, and 
> additional 
> > inner authentication mechanisms.
> > 
> > - Enable a TLS-based EAP method to support channel bindings. 
> > So as to enable RFC 2716bis to focus solely on 
> clarifications to the 
> > existing protocol, this effort will be handled in a 
> separate document.  
> > This item will not generate a new method, rather it will enhance 
> > EAP-TLS or the TLS based tunnel method work item.
> > 
> > - A mechanism meeting RFC 3748 and RFC 4017 requirements that makes 
> > use of existing password databases such as AAA databases.  
> This item 
> > will be based on the tunnel method work item.
> > 
> > Goals and Milestones:
> > Done	  	Form design team to work on strong shared 
> > secret mechanism
> > Done	  	Submit 2716bis I-D
> > Done	  	Submit first draft of shared secret 
> mechanism I-D
> > Done	  	Form password based mechanism design team
> > Done		Submit 2716bis draft to IESG for 
> Proposed Standard
> > Done   	Submit Strong Shared Secret Mechanism to IESG
> > Apr 2008 	Submit Tunnel and Password Method requirements 
> > first draft
> > Jul 2008 	Send Tunnel and Password Method requirements to IESG
> > Oct 2008 	Submit Tunnel Method first draft
> > Nov 2008    Submit TLS based method channel binding first draft
> > Nov 2008 	Submit Password Method first draft
> > Feb 2009	Send Tunnel Method to IESG
> > Apr 2009	Send TLS based method channel binding to IESG
> > Apr 2009	Send Password based method to IESG
> > 
> > 
> > 
> > 
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
> 
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Tue Feb 19 13:56:06 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB67428C644;
	Tue, 19 Feb 2008 13:56:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.093
X-Spam-Level: 
X-Spam-Status: No, score=-1.093 tagged_above=-999 required=5
	tests=[AWL=-0.656, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PAq485DUl6uc; Tue, 19 Feb 2008 13:56:05 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E465628C395;
	Tue, 19 Feb 2008 13:56:05 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0BFDE28C395
	for <emu@core3.amsl.com>; Tue, 19 Feb 2008 13:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lqCZ9iIIvOYa for <emu@core3.amsl.com>;
	Tue, 19 Feb 2008 13:56:04 -0800 (PST)
Received: from deployingradius.com (www.deployingradius.com [216.240.42.17])
	by core3.amsl.com (Postfix) with ESMTP id 403EE3A694C
	for <emu@ietf.org>; Tue, 19 Feb 2008 13:56:04 -0800 (PST)
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net
	[82.67.71.238])
	by deployingradius.com (Postfix) with ESMTP id 59E35A704E;
	Tue, 19 Feb 2008 13:55:56 -0800 (PST)
Message-ID: <47BB4FBD.2000805@deployingradius.com>
Date: Tue, 19 Feb 2008 22:53:01 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
X-Enigmail-Version: 0.95.0
Cc: emu@ietf.org
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Joseph Salowey (jsalowey) wrote:
> Please respond to this message and state whether you approve of the
> current charter revision and what capacity you would be willing to
> contribute towards tunneled method development: contributor, reviewer or
> not able to contribute.  

  I approve of the charter revision, and can contribute to the tunneled
method development as a reviewer, possibly as a contributor.

  Alan DeKok.
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Tue Feb 19 16:52:58 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD9C328C0FE;
	Tue, 19 Feb 2008 16:52:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.806
X-Spam-Level: 
X-Spam-Status: No, score=-1.806 tagged_above=-999 required=5
	tests=[AWL=-1.369, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FqKohyk82PEt; Tue, 19 Feb 2008 16:52:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0A263A6955;
	Tue, 19 Feb 2008 16:52:57 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BF523A6955
	for <emu@core3.amsl.com>; Tue, 19 Feb 2008 16:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YvXxVT7S-5-R for <emu@core3.amsl.com>;
	Tue, 19 Feb 2008 16:52:56 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163])
	by core3.amsl.com (Postfix) with ESMTP id 1C5A13A68E3
	for <emu@ietf.org>; Tue, 19 Feb 2008 16:52:56 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob105.postini.com
	([64.18.6.12]) with SMTP; Tue, 19 Feb 2008 16:52:49 PST
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 19 Feb 2008 16:52:28 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Feb 2008 19:50:59 -0500
Message-ID: <A6398B0DB62A474C82F61554EE93728704C7EC21@proton.jnpr.net>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] EMU charter revision
Thread-Index: AchntbzKn+eyM5+SQUmVlu0CjWYhAQLbDypgAA30NdA=
References: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
From: "Stephen Hanna" <shanna@juniper.net>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>,
	<emu@ietf.org>
X-OriginalArrivalTime: 20 Feb 2008 00:52:28.0646 (UTC)
	FILETIME=[DDDB8060:01C8735A]
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

I approve of the current charter revision and would be willing to
contribute towards tunneled method development as a contributor.

Thanks,

Steve Hanna

-----Original Message-----
From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On Behalf Of
Joseph Salowey (jsalowey)
Sent: Tuesday, February 19, 2008 2:15 PM
To: Joseph Salowey (jsalowey); emu@ietf.org
Subject: Re: [Emu] EMU charter revision

The response to the charter revision has been underwhelming.  I am a bit
concerned that we do not have enough participation to complete the
tunnel method work (most of the recent discussion has been about other
methods).  

I would like to get an idea of the number working group members that
approve of working on the tunnel method items and are able to
participate in the development of requirements and specifications as
contributors and/or reviewers.  

Please respond to this message and state whether you approve of the
current charter revision and what capacity you would be willing to
contribute towards tunneled method development: contributor, reviewer or
not able to contribute.  

I have submitted an internet draft attempt at an outline of requirements
for tunneled methods
(http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
txt) that I hope can provided a starting point for discussions on the
list and in the Philadelphia meeting.  

Thanks,

Joe

> -----Original Message-----
> From: Joseph Salowey (jsalowey) 
> Sent: Monday, February 04, 2008 9:13 PM
> To: emu@ietf.org
> Subject: EMU charter revision
> 
> Below is a revised charter update based on the discussion on 
> the list.  I have left the password based method item as a 
> tunnel method because this represents the consensus the 
> working group has reached.  I also believe the working group 
> will have to focus on the tunnel method related items for the 
> near term to make progress.  This does not mean that we 
> cannot work on additional methods as working group items in 
> the future.   
> 
> Please review the charter update and post any issues you have 
> with the carter.  Please also indicate if you have reviewed 
> the proposed charter and have no issues.  It is difficult to 
> judge working group consensus unless there are sufficient responses. 
> 
> Thanks,
> 
> Joe
> 
> Description of Working Group:
> The Extensible Authentication Protocol (EAP) [RFC 3748] is a 
> network access authentication framework used in the PPP, 
> 802.11, 802.16, VPN, PANA, and in some functions in 3G 
> networks. EAP itself is a simple protocol and actual 
> authentication happens in EAP methods.
> 
> Over 40 different EAP methods exist. Most of these methods 
> are proprietary methods and only a few methods are documented 
> in RFCs. The lack of documented, open specifications is a 
> deployment and interoperability problem. In addition, none of 
> the EAP methods in the standards track implement features 
> such as key derivation that are required for many modern 
> applications. This poses a problem for, among other things, 
> the selection of a mandatory to implement EAP method in new 
> network access technologies. For example, no standards track 
> methods meet new requirements such as those posed in RFC 
> 4017, which documents IEEE 802.11 requirements for EAP methods.
> 
> This group is chartered to work on the following types of 
> mechanisms to meet RFC 3748 and RFC 4017 requirements:
> 
> - An update to RFC 2716 to bring EAP-TLS into standards 
> track, clarify specification, interoperability, and 
> implementation issues gathered over the years, and update the 
> document to meet the requirements of RFC 3748, RFC 4017, and 
> EAP keying framework documents. Backwards compatibility with 
> RFC 2716 is a requirement.
> 
> - A mechanism based on strong shared secrets that meets RFC 
> 3748 and RFC 4017 requirements. This mechanism should strive 
> to be simple and compact for implementation in resource 
> constrained environments.
> 
> - A mechanism to support extensible communication within a 
> TLS protected tunnel that meets RFC 3748 and RFC 4017 
> requirements. This mechanism must support channel bindings in 
> order to meet RFC 4962 requirements and it must provide 
> cryptographic algorithm agility. This mechanism will support 
> meeting the requirements of an enhanced TLS mechanism, a 
> password based authentication mechanism, and additional inner 
> authentication mechanisms.
> 
> - Enable a TLS-based EAP method to support channel bindings. 
> So as to enable RFC 2716bis to focus solely on clarifications 
> to the existing protocol, this effort will be handled in a 
> separate document.  This item will not generate a new method, 
> rather it will enhance EAP-TLS or the TLS based tunnel method 
> work item.  
> 
> - A mechanism meeting RFC 3748 and RFC 4017 requirements that 
> makes use of existing password databases such as AAA 
> databases.  This item will be based on the tunnel method work item.
> 
> Goals and Milestones:
> Done	  	Form design team to work on strong shared 
> secret mechanism
> Done	  	Submit 2716bis I-D
> Done	  	Submit first draft of shared secret mechanism I-D
> Done	  	Form password based mechanism design team
> Done		Submit 2716bis draft to IESG for Proposed Standard
> Done   	Submit Strong Shared Secret Mechanism to IESG
> Apr 2008 	Submit Tunnel and Password Method requirements 
> first draft
> Jul 2008 	Send Tunnel and Password Method requirements to IESG
> Oct 2008 	Submit Tunnel Method first draft
> Nov 2008    Submit TLS based method channel binding first draft
> Nov 2008 	Submit Password Method first draft
> Feb 2009	Send Tunnel Method to IESG
> Apr 2009	Send TLS based method channel binding to IESG
> Apr 2009	Send Password based method to IESG
> 
> 
> 
> 
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Tue Feb 19 19:56:14 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 97BBE28C3D1;
	Tue, 19 Feb 2008 19:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.889
X-Spam-Level: 
X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5
	tests=[AWL=-0.452, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e-HubLey4NAv; Tue, 19 Feb 2008 19:56:13 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9ACB13A6B75;
	Tue, 19 Feb 2008 19:56:13 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BDA23A6B75
	for <emu@core3.amsl.com>; Tue, 19 Feb 2008 19:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OWARCJINzAcn for <emu@core3.amsl.com>;
	Tue, 19 Feb 2008 19:56:11 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174])
	by core3.amsl.com (Postfix) with ESMTP id 1B62C3A67A9
	for <emu@ietf.org>; Tue, 19 Feb 2008 19:56:11 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1])
	by colo.trepanning.net (Postfix) with ESMTP id 5D86A1FA6215;
	Tue, 19 Feb 2008 19:56:08 -0800 (PST)
Received: from 69.12.173.8
	(SquirrelMail authenticated user dharkins@lounge.org)
	by www.trepanning.net with HTTP;
	Tue, 19 Feb 2008 19:56:08 -0800 (PST)
Message-ID: <3341.69.12.173.8.1203479768.squirrel@www.trepanning.net>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
Date: Tue, 19 Feb 2008 19:56:08 -0800 (PST)
From: "Dan Harkins" <dharkins@lounge.org>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Cc: emu@ietf.org
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org


  Hi Joe,

  I do NOT approve of the current charter revision, specifically the
change that says the password-based method can only be via the
tunneled method. I do approve of the inclusion of tunneled methods
in the charter though and would be willing to contribute as a
reviewer.

  regards,

  Dan.

On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:
> The response to the charter revision has been underwhelming.  I am a bit
> concerned that we do not have enough participation to complete the
> tunnel method work (most of the recent discussion has been about other
> methods).
>
> I would like to get an idea of the number working group members that
> approve of working on the tunnel method items and are able to
> participate in the development of requirements and specifications as
> contributors and/or reviewers.
>
> Please respond to this message and state whether you approve of the
> current charter revision and what capacity you would be willing to
> contribute towards tunneled method development: contributor, reviewer or
> not able to contribute.
>
> I have submitted an internet draft attempt at an outline of requirements
> for tunneled methods
> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
> txt) that I hope can provided a starting point for discussions on the
> list and in the Philadelphia meeting.
>
> Thanks,
>
> Joe
>
>> -----Original Message-----
>> From: Joseph Salowey (jsalowey)
>> Sent: Monday, February 04, 2008 9:13 PM
>> To: emu@ietf.org
>> Subject: EMU charter revision
>>
>> Below is a revised charter update based on the discussion on
>> the list.  I have left the password based method item as a
>> tunnel method because this represents the consensus the
>> working group has reached.  I also believe the working group
>> will have to focus on the tunnel method related items for the
>> near term to make progress.  This does not mean that we
>> cannot work on additional methods as working group items in
>> the future.
>>
>> Please review the charter update and post any issues you have
>> with the carter.  Please also indicate if you have reviewed
>> the proposed charter and have no issues.  It is difficult to
>> judge working group consensus unless there are sufficient responses.
>>
>> Thanks,
>>
>> Joe
>>
>> Description of Working Group:
>> The Extensible Authentication Protocol (EAP) [RFC 3748] is a
>> network access authentication framework used in the PPP,
>> 802.11, 802.16, VPN, PANA, and in some functions in 3G
>> networks. EAP itself is a simple protocol and actual
>> authentication happens in EAP methods.
>>
>> Over 40 different EAP methods exist. Most of these methods
>> are proprietary methods and only a few methods are documented
>> in RFCs. The lack of documented, open specifications is a
>> deployment and interoperability problem. In addition, none of
>> the EAP methods in the standards track implement features
>> such as key derivation that are required for many modern
>> applications. This poses a problem for, among other things,
>> the selection of a mandatory to implement EAP method in new
>> network access technologies. For example, no standards track
>> methods meet new requirements such as those posed in RFC
>> 4017, which documents IEEE 802.11 requirements for EAP methods.
>>
>> This group is chartered to work on the following types of
>> mechanisms to meet RFC 3748 and RFC 4017 requirements:
>>
>> - An update to RFC 2716 to bring EAP-TLS into standards
>> track, clarify specification, interoperability, and
>> implementation issues gathered over the years, and update the
>> document to meet the requirements of RFC 3748, RFC 4017, and
>> EAP keying framework documents. Backwards compatibility with
>> RFC 2716 is a requirement.
>>
>> - A mechanism based on strong shared secrets that meets RFC
>> 3748 and RFC 4017 requirements. This mechanism should strive
>> to be simple and compact for implementation in resource
>> constrained environments.
>>
>> - A mechanism to support extensible communication within a
>> TLS protected tunnel that meets RFC 3748 and RFC 4017
>> requirements. This mechanism must support channel bindings in
>> order to meet RFC 4962 requirements and it must provide
>> cryptographic algorithm agility. This mechanism will support
>> meeting the requirements of an enhanced TLS mechanism, a
>> password based authentication mechanism, and additional inner
>> authentication mechanisms.
>>
>> - Enable a TLS-based EAP method to support channel bindings.
>> So as to enable RFC 2716bis to focus solely on clarifications
>> to the existing protocol, this effort will be handled in a
>> separate document.  This item will not generate a new method,
>> rather it will enhance EAP-TLS or the TLS based tunnel method
>> work item.
>>
>> - A mechanism meeting RFC 3748 and RFC 4017 requirements that
>> makes use of existing password databases such as AAA
>> databases.  This item will be based on the tunnel method work item.
>>
>> Goals and Milestones:
>> Done	  	Form design team to work on strong shared
>> secret mechanism
>> Done	  	Submit 2716bis I-D
>> Done	  	Submit first draft of shared secret mechanism I-D
>> Done	  	Form password based mechanism design team
>> Done		Submit 2716bis draft to IESG for Proposed Standard
>> Done   	Submit Strong Shared Secret Mechanism to IESG
>> Apr 2008 	Submit Tunnel and Password Method requirements
>> first draft
>> Jul 2008 	Send Tunnel and Password Method requirements to IESG
>> Oct 2008 	Submit Tunnel Method first draft
>> Nov 2008    Submit TLS based method channel binding first draft
>> Nov 2008 	Submit Password Method first draft
>> Feb 2009	Send Tunnel Method to IESG
>> Apr 2009	Send TLS based method channel binding to IESG
>> Apr 2009	Send Password based method to IESG
>>
>>
>>
>>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>


_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Thu Feb 21 11:31:19 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 153A228C216;
	Thu, 21 Feb 2008 11:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5
	tests=[AWL=-2.152, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id N3IkqrMamoCu; Thu, 21 Feb 2008 11:31:18 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 541AF3A6D04;
	Thu, 21 Feb 2008 11:31:18 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80EBA3A6CEF
	for <emu@core3.amsl.com>; Thu, 21 Feb 2008 11:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BVidMRuutlB7 for <emu@core3.amsl.com>;
	Thu, 21 Feb 2008 11:31:15 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id D1F6D3A6CF9
	for <emu@ietf.org>; Thu, 21 Feb 2008 11:31:15 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 21 Feb 2008 11:31:12 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1LJVC1e021129
	for <emu@ietf.org>; Thu, 21 Feb 2008 11:31:12 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1LJVCp4008271
	for <emu@ietf.org>; Thu, 21 Feb 2008 19:31:12 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Feb 2008 11:31:11 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 21 Feb 2008 11:31:57 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE505518F1E@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft Agenda for IETF-71
Thread-Index: Ach0wGu43dxcGe+nQcSR7g3JyZRhGg==
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: <emu@ietf.org>
X-OriginalArrivalTime: 21 Feb 2008 19:31:12.0061 (UTC)
	FILETIME=[50F18ED0:01C874C0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=725; t=1203622272; x=1204486272;
	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@ci
	sco.com> |Subject:=20Draft=20Agenda=20for=20IETF-71
	|Sender:=20; bh=UzkaeoENpb3WJwtlXRihZahG9EECjPVAsGXMmJsA1D4=;
	b=UKz/25sl2FlXaj21o9q/caVhyd761Nd7BBpwylYGG2oNSRgTCyTOnJiZaY
	VUCMI6LAE1UnEB9lefqJR5Q545JLOayXvoeP5mp25mnKuAJLO66s39UzDlfs
	7CYSs/at2Wd5b/t2LeftiDPw/xzw8RbghTBwQdfoFWEsjLLSQ9djE=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: [Emu] Draft Agenda for IETF-71
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Draft meeting agenda is attached below, let me know if you have any
additions or corrections.

Thanks,

Joe

EMU Agenda
IETF 71
THURSDAY, March 13, 2008 
0900-1130 Morning Session I
---------------------------------------------
+ Administrivia (5 min)
 - agenda, blue sheets, note takers

+ Document Staus (5 min)
 - EAP-TLS  - draft-simon-emu-rfc2716bis-13.txt
 - EAP-GPSK - draft-ietf-emu-eap-gpsk-08.txt

+ Charter Revision Status (15 min)

+ Tunnel Method Requirements (90 min)
 - draft-salowey-emu-eaptunnel-req-00.txt

+ Channel Bindings (20 min)
 - draft-clancy-emu-chbind-00.txt
 - draft-clancy-emu-aaapay-00.txt

+ Password only Mechanism (15 min)
 - draft-harkins-emu-eap-pwd-00.txt
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Thu Feb 21 11:35:36 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4276D3A6B73;
	Thu, 21 Feb 2008 11:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.567
X-Spam-Level: 
X-Spam-Status: No, score=-0.567 tagged_above=-999 required=5
	tests=[AWL=-0.130, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NudXbFBH4xul; Thu, 21 Feb 2008 11:35:35 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 967833A6CFE;
	Thu, 21 Feb 2008 11:35:35 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9E0423A6A26
	for <emu@core3.amsl.com>; Thu, 21 Feb 2008 11:35:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sRf3-C+8QZKP for <emu@core3.amsl.com>;
	Thu, 21 Feb 2008 11:35:29 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id DB38A3A6CFA
	for <emu@ietf.org>; Thu, 21 Feb 2008 11:35:28 -0800 (PST)
Received: (qmail invoked by alias); 21 Feb 2008 19:35:24 -0000
Received: from proxy1-nsn.nsn-inter.net (EHLO [217.115.75.229])
	[217.115.75.229]
	by mail.gmx.net (mp024) with SMTP; 21 Feb 2008 20:35:24 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19ZOc8diwlZjd+89PbTDNRUJaikQ/Bq+RnzdDzJlo
	SoWmtJ6kdLH9Tk
Message-ID: <47BDD27B.9060806@gmx.net>
Date: Thu, 21 Feb 2008 21:35:23 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE505518F1E@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE505518F1E@xmb-sjc-225.amer.cisco.com>
X-Y-GMX-Trusted: 0
Cc: emu@ietf.org
Subject: Re: [Emu] Draft Agenda for IETF-71
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Hannes.Tschofenig@gmx.net
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org


> + Channel Bindings (20 min)
>  - draft-clancy-emu-chbind-00.txt
>  - draft-clancy-emu-aaapay-00.txt
>
>   
I haven't seen these documents and I cannot find them either

do you have pointers to them?


_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Thu Feb 21 11:39:06 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5D5A3A6D09;
	Thu, 21 Feb 2008 11:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level: 
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5
	tests=[AWL=-2.007, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KmMSCmg5IvEI; Thu, 21 Feb 2008 11:39:06 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AF293A6CF8;
	Thu, 21 Feb 2008 11:39:06 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BCDA3A6A2B
	for <emu@core3.amsl.com>; Thu, 21 Feb 2008 11:39:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LQmVeF51zyDJ for <emu@core3.amsl.com>;
	Thu, 21 Feb 2008 11:39:03 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id C56E93A6C7F
	for <emu@ietf.org>; Thu, 21 Feb 2008 11:39:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.25,387,1199692800"; 
   d="scan'208";a="6675154"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 21 Feb 2008 11:38:56 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1LJcukK001015; 
	Thu, 21 Feb 2008 11:38:56 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1LJcjpS015767;
	Thu, 21 Feb 2008 19:38:55 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Feb 2008 11:38:54 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 21 Feb 2008 11:39:39 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE505518F2E@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <47BDD27B.9060806@gmx.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Draft Agenda for IETF-71
Thread-Index: Ach0wPiHI0pXiZ39RNu19BLrbPIEgQAAFOSw
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: <Hannes.Tschofenig@gmx.net>
X-OriginalArrivalTime: 21 Feb 2008 19:38:55.0155 (UTC)
	FILETIME=[64F81830:01C874C1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=685; t=1203622736; x=1204486736;
	c=relaxed/simple; s=sjdkim2002;
	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@ci
	sco.com>
	|Subject:=20RE=3A=20[Emu]=20Draft=20Agenda=20for=20IETF-71
	|Sender:=20; bh=PzqApo6r5+/JTgNMXoHnr09trfsiMPMlca8OMGQ6OEc=;
	b=QNjxU2uQFCDK4N9HsUOJxUpP5AGado0DHdtfUnAQitNxayliQjYWJMnYYq
	Qz5P82ic0rQHV/eAW0tlDzIom+1s+XYnDyy9oMhj2OFrVHm4YxEs+Ed63eei
	gkhn6cZFHl;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: emu@ietf.org
Subject: Re: [Emu] Draft Agenda for IETF-71
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

They were submitted by email due to the tool issues earlier this week
and have not shown up yet.  A pointer will be sent to the list when they
are available.  

Cheers,

Joe

> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net] 
> Sent: Thursday, February 21, 2008 11:35 AM
> To: Joseph Salowey (jsalowey)
> Cc: emu@ietf.org
> Subject: Re: [Emu] Draft Agenda for IETF-71
> 
> 
> > + Channel Bindings (20 min)
> >  - draft-clancy-emu-chbind-00.txt
> >  - draft-clancy-emu-aaapay-00.txt
> >
> >   
> I haven't seen these documents and I cannot find them either
> 
> do you have pointers to them?
> 
> 
> 
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Thu Feb 21 11:54:15 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 36E0028C6D0;
	Thu, 21 Feb 2008 11:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.575
X-Spam-Level: 
X-Spam-Status: No, score=-0.575 tagged_above=-999 required=5
	tests=[AWL=-1.138, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id baW-2gxYAGwR; Thu, 21 Feb 2008 11:54:14 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABDC928C30E;
	Thu, 21 Feb 2008 11:54:13 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3021F28C5EA
	for <emu@core3.amsl.com>; Thu, 21 Feb 2008 11:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tS59JPMS5Dzf for <emu@core3.amsl.com>;
	Thu, 21 Feb 2008 11:54:10 -0800 (PST)
Received: from blu139-omc3-s23.blu139.hotmail.com
	(blu139-omc3-s23.blu139.hotmail.com [65.55.175.223])
	by core3.amsl.com (Postfix) with ESMTP id 1B59728C30E
	for <emu@ietf.org>; Thu, 21 Feb 2008 11:54:10 -0800 (PST)
Received: from BLU137-W34 ([65.55.162.188]) by
	blu139-omc3-s23.blu139.hotmail.com with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 21 Feb 2008 11:54:06 -0800
Message-ID: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
X-Originating-IP: [71.37.11.7]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <emu@ietf.org>
Date: Thu, 21 Feb 2008 11:54:06 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 21 Feb 2008 19:54:06.0758 (UTC)
	FILETIME=[8453AC60:01C874C3]
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1169966219=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

--===============1169966219==
Content-Type: multipart/alternative;
	boundary="_5c8fb0a4-fe01-4315-9723-9136f1d8f521_"

--_5c8fb0a4-fe01-4315-9723-9136f1d8f521_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


I also do NOT approve of the current charter revision, for several reasons:

a.  The Charter text contains statements that are no longer true.  For exam=
ple:
"Most of these methods are proprietary methods and only a few methods=20
are documented in RFCs."

The following EAP methods are now documented in RFCs:

EAP-TLS (RFC 2716)
EAP-SIM (RFC 4186)
EAP-AKA (RFC 4187)
EAP-PAX (RFC 4746)
EAP-SAKE (RFC 4763)
EAP-PSK (RFC 4764)
EAP-POTP (RFC 4793)
EAP-FAST (RFC 4851)
EAP-IKEv2 (RFC 5106)

9 methods claiming to satify RFC 4017 critieria is more than a "few".=20

b. The Charter requires support for Channel Bindings without doing the
preparatory work to define how Channel Bindings works.  Either the
requirement should be removed, or a work item should be added to=20
better define the approach to Channel Bindings.=20

c. The text on tunnel methods does not provide enough guidance to avoid
potentially fruitless arguments.  So far, the EMU WG has not been able
to come to consensus on selection of one of the existing tunneling
protocols, and efforts to design "yet another" tunneling protocol=20
haven't gotten very far either.  I'd like to see more specific=20
language that would make it clear that work on improving existing
tunneling protocols is within scope, and also that the EMU WG,
if it cannot come to consensus on a single protocol, can proceed to=20
work on one or more protocols with significant support. =20

d. Password-based methods.  While I can understand the desire to limit the
number of charter items, I do agree with Dan that work on weak-password
methods is important.  With some of the IPR obstacles likely to fall by
the wayside in coming years, it is time for the IETF to re-visit its policy
on inclusion of "zero knowledge" algorithms within standards track document=
s.=20
Dan Harkins said:

" Hi Joe,

  I do NOT approve of the current charter revision, specifically the
change that says the password-based method can only be via the
tunneled method. I do approve of the inclusion of tunneled methods
in the charter though and would be willing to contribute as a
reviewer.

  regards,

  Dan."
On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:
> The response to the charter revision has been underwhelming.  I am a bit
> concerned that we do not have enough participation to complete the
> tunnel method work (most of the recent discussion has been about other
> methods).
>
> I would like to get an idea of the number working group members that
> approve of working on the tunnel method items and are able to
> participate in the development of requirements and specifications as
> contributors and/or reviewers.
>
> Please respond to this message and state whether you approve of the
> current charter revision and what capacity you would be willing to
> contribute towards tunneled method development: contributor, reviewer or
> not able to contribute.
>
> I have submitted an internet draft attempt at an outline of requirements
> for tunneled methods
> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
> txt) that I hope can provided a starting point for discussions on the
> list and in the Philadelphia meeting.
>
> Thanks,
>
> Joe

--_5c8fb0a4-fe01-4315-9723-9136f1d8f521_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
I also do NOT approve of the current charter revision, for several reasons:=
<br><br>a.&nbsp; The Charter text contains statements that are no longer tr=
ue.&nbsp; For example:<br><pre>"Most of these methods are proprietary metho=
ds and only a few methods <br>are documented in RFCs."<br><br>The following=
 EAP methods are now documented in RFCs:<br><br>EAP-TLS (RFC 2716)<br>EAP-S=
IM (RFC 4186)<br>EAP-AKA (RFC 4187)<br>EAP-PAX (RFC 4746)<br>EAP-SAKE (RFC =
4763)<br>EAP-PSK (RFC 4764)<br>EAP-POTP (RFC 4793)<br>EAP-FAST (RFC 4851)<b=
r>EAP-IKEv2 (RFC 5106)<br><br>9 methods claiming to satify RFC 4017 critier=
ia is more than a "few". <br><br>b. The Charter requires support for Channe=
l Bindings without doing the<br>preparatory work to define how Channel Bind=
ings works.  Either the<br>requirement should be removed, or a work item sh=
ould be added to <br>better define the approach to Channel Bindings. <br><b=
r>c. The text on tunnel methods does not provide enough guidance to avoid<b=
r>potentially fruitless arguments.  So far, the EMU WG has not been able<br=
>to come to consensus on selection of one of the existing tunneling<br>prot=
ocols, and efforts to design "yet another" tunneling protocol <br>haven't g=
otten very far either.  I'd like to see more specific <br>language that wou=
ld make it clear that work on improving existing<br>tunneling protocols is =
within scope, and also that the EMU WG,<br>if it cannot come to consensus o=
n a single protocol, can proceed to <br>work on one or more protocols with =
significant support.  <br><br>d. Password-based methods.  While I can under=
stand the desire to limit the<br>number of charter items, I do agree with D=
an that work on weak-password<br>methods is important.  With some of the IP=
R obstacles likely to fall by<br>the wayside in coming years, it is time fo=
r the IETF to re-visit its policy<br>on inclusion of "zero knowledge" algor=
ithms within standards track documents. <br></pre>Dan Harkins said:<br><br>=
" Hi Joe,<br><pre><br>  I do NOT approve of the current charter revision, s=
pecifically the<br>change that says the password-based method can only be v=
ia the<br>tunneled method. I do approve of the inclusion of tunneled method=
s<br>in the charter though and would be willing to contribute as a<br>revie=
wer.<br><br>  regards,<br><br>  Dan."<br></pre><pre>On Tue, February 19, 20=
08 11:14 am, Joseph Salowey (jsalowey) wrote:<br>&gt; The response to the c=
harter revision has been underwhelming.  I am a bit<br>&gt; concerned that =
we do not have enough participation to complete the<br>&gt; tunnel method w=
ork (most of the recent discussion has been about other<br>&gt; methods).<b=
r>&gt;<br>&gt; I would like to get an idea of the number working group memb=
ers that<br>&gt; approve of working on the tunnel method items and are able=
 to<br>&gt; participate in the development of requirements and specificatio=
ns as<br>&gt; contributors and/or reviewers.<br>&gt;<br>&gt; Please respond=
 to this message and state whether you approve of the<br>&gt; current chart=
er revision and what capacity you would be willing to<br>&gt; contribute to=
wards tunneled method development: contributor, reviewer or<br>&gt; not abl=
e to contribute.<br>&gt;<br>&gt; I have submitted an internet draft attempt=
 at an outline of requirements<br>&gt; for tunneled methods<br>&gt; (<a rel=
=3D"nofollow" href=3D"http://www.ietf.org/internet-drafts/draft-salowey-emu=
-eaptunnel-req-00">http://www.ietf.org/internet-drafts/draft-salowey-emu-ea=
ptunnel-req-00</a>.<br>&gt; txt) that I hope can provided a starting point =
for discussions on the<br>&gt; list and in the Philadelphia meeting.<br>&gt=
;<br>&gt; Thanks,<br>&gt;<br>&gt; Joe</pre><br></body>
</html>=

--_5c8fb0a4-fe01-4315-9723-9136f1d8f521_--

--===============1169966219==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu

--===============1169966219==--


From emu-bounces@ietf.org  Fri Feb 22 06:35:08 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A81728C32E;
	Fri, 22 Feb 2008 06:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.516
X-Spam-Level: 
X-Spam-Status: No, score=-0.516 tagged_above=-999 required=5
	tests=[AWL=-1.079, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Fiwo5cLpK+bW; Fri, 22 Feb 2008 06:35:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F30423A6C6A;
	Fri, 22 Feb 2008 06:35:06 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 756B13A6C6A
	for <emu@core3.amsl.com>; Fri, 22 Feb 2008 06:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gsgM5P79AqSy for <emu@core3.amsl.com>;
	Fri, 22 Feb 2008 06:35:05 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net
	[217.115.75.234])
	by core3.amsl.com (Postfix) with ESMTP id D33A33A6B7B
	for <emu@ietf.org>; Fri, 22 Feb 2008 06:35:04 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56])
	by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	m1MEYuEu006994
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 22 Feb 2008 15:34:56 +0100
Received: from demuexc023.nsn-intra.net (webmail.nsn-intra.net [10.150.128.36])
	by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id m1MEYuSt027484; Fri, 22 Feb 2008 15:34:56 +0100
Received: from DEMUEXC012.nsn-intra.net ([10.150.128.23]) by
	demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 22 Feb 2008 15:34:56 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 22 Feb 2008 15:34:56 +0100
Message-ID: <5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
In-Reply-To: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] EMU Charter revision
Thread-Index: Ach0w4ubAa4S3fx9TNulQUAhMvNK6wAYjXLQ
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Bernard Aboba" <bernard_aboba@hotmail.com>, <emu@ietf.org>
X-OriginalArrivalTime: 22 Feb 2008 14:34:56.0177 (UTC)
	FILETIME=[181AAA10:01C87560]
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0476674649=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0476674649==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C87560.18225F26"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C87560.18225F26
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Bernard,
=20
a question your excitment regarding strong password based EAP method.=20
=20
Why do you think they are useful? There are other ways (and they are
deployed already) that can accomplish the same result without going
along the SRP & co track.=20
Is it because you expect performance improvements or because the
crypto-mechanisms look nicer?=20
=20
I cannot quite understand the motivation.=20
=20
Ciao
Hannes

________________________________

	Von: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] Im
Auftrag von ext Bernard Aboba
	Gesendet: Donnerstag, 21. Februar 2008 21:54
	An: emu@ietf.org
	Betreff: Re: [Emu] EMU Charter revision
=09
=09
	I also do NOT approve of the current charter revision, for
several reasons:
=09
	a.  The Charter text contains statements that are no longer
true.  For example:
=09
	"Most of these methods are proprietary methods and only a few
methods=20
	are documented in RFCs."
=09
	The following EAP methods are now documented in RFCs:
=09
	EAP-TLS (RFC 2716)
	EAP-SIM (RFC 4186)
	EAP-AKA (RFC 4187)
	EAP-PAX (RFC 4746)
	EAP-SAKE (RFC 4763)
	EAP-PSK (RFC 4764)
	EAP-POTP (RFC 4793)
	EAP-FAST (RFC 4851)
	EAP-IKEv2 (RFC 5106)
=09
	9 methods claiming to satify RFC 4017 critieria is more than a
"few".=20
=09
	b. The Charter requires support for Channel Bindings without
doing the
	preparatory work to define how Channel Bindings works.  Either
the
	requirement should be removed, or a work item should be added to

	better define the approach to Channel Bindings.=20
=09
	c. The text on tunnel methods does not provide enough guidance
to avoid
	potentially fruitless arguments.  So far, the EMU WG has not
been able
	to come to consensus on selection of one of the existing
tunneling
	protocols, and efforts to design "yet another" tunneling
protocol=20
	haven't gotten very far either.  I'd like to see more specific=20
	language that would make it clear that work on improving
existing
	tunneling protocols is within scope, and also that the EMU WG,
	if it cannot come to consensus on a single protocol, can proceed
to=20
	work on one or more protocols with significant support. =20
=09
	d. Password-based methods.  While I can understand the desire to
limit the
	number of charter items, I do agree with Dan that work on
weak-password
	methods is important.  With some of the IPR obstacles likely to
fall by
	the wayside in coming years, it is time for the IETF to re-visit
its policy
	on inclusion of "zero knowledge" algorithms within standards
track documents.=20
	Dan Harkins said:
=09
	" Hi Joe,
=09
=09
	  I do NOT approve of the current charter revision, specifically
the
	change that says the password-based method can only be via the
	tunneled method. I do approve of the inclusion of tunneled
methods
	in the charter though and would be willing to contribute as a
	reviewer.
=09
	  regards,
=09
	  Dan."
	On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey)
wrote:
	> The response to the charter revision has been underwhelming.
I am a bit
	> concerned that we do not have enough participation to complete
the
	> tunnel method work (most of the recent discussion has been
about other
	> methods).
	>
	> I would like to get an idea of the number working group
members that
	> approve of working on the tunnel method items and are able to
	> participate in the development of requirements and
specifications as
	> contributors and/or reviewers.
	>
	> Please respond to this message and state whether you approve
of the
	> current charter revision and what capacity you would be
willing to
	> contribute towards tunneled method development: contributor,
reviewer or
	> not able to contribute.
	>
	> I have submitted an internet draft attempt at an outline of
requirements
	> for tunneled methods
	>
(http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
	> txt) that I hope can provided a starting point for discussions
on the
	> list and in the Philadelphia meeting.
	>
	> Thanks,
	>
	> Joe



------_=_NextPart_001_01C87560.18225F26
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE>.hmmessage P {
	PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: =
0px; PADDING-TOP: 0px
}
BODY.hmmessage {
	FONT-SIZE: 10pt; FONT-FAMILY: Tahoma
}
</STYLE>

<META content=3D"MSHTML 6.00.5730.13" name=3DGENERATOR></HEAD>
<BODY class=3Dhmmessage>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff>Hi Bernard,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff>a question your excitment regarding strong password =
based EAP=20
method. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff>Why do you think they are useful? There are other ways =
(and they=20
are deployed already)&nbsp;that can accomplish the same result without =
going=20
along the SRP &amp; co track. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff>Is it because you expect performance improvements or =
because the=20
crypto-mechanisms look nicer? </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff>I cannot quite understand the motivation. =
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D900193707-22022008><FONT =
face=3DArial=20
color=3D#0000ff>Ciao<BR>Hannes</FONT></SPAN></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma><B>Von:</B> emu-bounces@ietf.org=20
  [mailto:emu-bounces@ietf.org] <B>Im Auftrag von </B>ext Bernard=20
  Aboba<BR><B>Gesendet:</B> Donnerstag, 21. Februar 2008 =
21:54<BR><B>An:</B>=20
  emu@ietf.org<BR><B>Betreff:</B> Re: [Emu] EMU Charter=20
  revision<BR></FONT><BR></DIV>
  <DIV></DIV>I also do NOT approve of the current charter revision, for =
several=20
  reasons:<BR><BR>a.&nbsp; The Charter text contains statements that are =
no=20
  longer true.&nbsp; For example:<BR><PRE>"Most of these methods are =
proprietary methods and only a few methods <BR>are documented in =
RFCs."<BR><BR>The following EAP methods are now documented in =
RFCs:<BR><BR>EAP-TLS (RFC 2716)<BR>EAP-SIM (RFC 4186)<BR>EAP-AKA (RFC =
4187)<BR>EAP-PAX (RFC 4746)<BR>EAP-SAKE (RFC 4763)<BR>EAP-PSK (RFC =
4764)<BR>EAP-POTP (RFC 4793)<BR>EAP-FAST (RFC 4851)<BR>EAP-IKEv2 (RFC =
5106)<BR><BR>9 methods claiming to satify RFC 4017 critieria is more =
than a "few". <BR><BR>b. The Charter requires support for Channel =
Bindings without doing the<BR>preparatory work to define how Channel =
Bindings works.  Either the<BR>requirement should be removed, or a work =
item should be added to <BR>better define the approach to Channel =
Bindings. <BR><BR>c. The text on tunnel methods does not provide enough =
guidance to avoid<BR>potentially fruitless arguments.  So far, the EMU =
WG has not been able<BR>to come to consensus on selection of one of the =
existing tunneling<BR>protocols, and efforts to design "yet another" =
tunneling protocol <BR>haven't gotten very far either.  I'd like to see =
more specific <BR>language that would make it clear that work on =
improving existing<BR>tunneling protocols is within scope, and also that =
the EMU WG,<BR>if it cannot come to consensus on a single protocol, can =
proceed to <BR>work on one or more protocols with significant support.  =
<BR><BR>d. Password-based methods.  While I can understand the desire to =
limit the<BR>number of charter items, I do agree with Dan that work on =
weak-password<BR>methods is important.  With some of the IPR obstacles =
likely to fall by<BR>the wayside in coming years, it is time for the =
IETF to re-visit its policy<BR>on inclusion of "zero knowledge" =
algorithms within standards track documents. <BR></PRE>Dan=20
  Harkins said:<BR><BR>" Hi Joe,<BR><PRE><BR>  I do NOT approve of the =
current charter revision, specifically the<BR>change that says the =
password-based method can only be via the<BR>tunneled method. I do =
approve of the inclusion of tunneled methods<BR>in the charter though =
and would be willing to contribute as a<BR>reviewer.<BR><BR>  =
regards,<BR><BR>  Dan."<BR></PRE><PRE>On Tue, February 19, 2008 11:14 =
am, Joseph Salowey (jsalowey) wrote:<BR>&gt; The response to the charter =
revision has been underwhelming.  I am a bit<BR>&gt; concerned that we =
do not have enough participation to complete the<BR>&gt; tunnel method =
work (most of the recent discussion has been about other<BR>&gt; =
methods).<BR>&gt;<BR>&gt; I would like to get an idea of the number =
working group members that<BR>&gt; approve of working on the tunnel =
method items and are able to<BR>&gt; participate in the development of =
requirements and specifications as<BR>&gt; contributors and/or =
reviewers.<BR>&gt;<BR>&gt; Please respond to this message and state =
whether you approve of the<BR>&gt; current charter revision and what =
capacity you would be willing to<BR>&gt; contribute towards tunneled =
method development: contributor, reviewer or<BR>&gt; not able to =
contribute.<BR>&gt;<BR>&gt; I have submitted an internet draft attempt =
at an outline of requirements<BR>&gt; for tunneled methods<BR>&gt; (<A =
href=3D"http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-r=
eq-00" =
rel=3Dnofollow>http://www.ietf.org/internet-drafts/draft-salowey-emu-eapt=
unnel-req-00</A>.<BR>&gt; txt) that I hope can provided a starting point =
for discussions on the<BR>&gt; list and in the Philadelphia =
meeting.<BR>&gt;<BR>&gt; Thanks,<BR>&gt;<BR>&gt; =
Joe</PRE><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C87560.18225F26--

--===============0476674649==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu

--===============0476674649==--


From emu-bounces@ietf.org  Fri Feb 22 08:25:29 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E91028C3F4;
	Fri, 22 Feb 2008 08:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.293
X-Spam-Level: 
X-Spam-Status: No, score=0.293 tagged_above=-999 required=5 tests=[AWL=-0.270,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BL9S-xxzoMNv; Fri, 22 Feb 2008 08:25:27 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 13CB53A6A40;
	Fri, 22 Feb 2008 08:25:20 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A9B728C23B
	for <emu@core3.amsl.com>; Fri, 22 Feb 2008 08:25:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ShnltLwXVxV2 for <emu@core3.amsl.com>;
	Fri, 22 Feb 2008 08:25:17 -0800 (PST)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235])
	by core3.amsl.com (Postfix) with ESMTP id 67FED28CB19
	for <emu@ietf.org>; Fri, 22 Feb 2008 08:24:58 -0800 (PST)
Received: by wx-out-0506.google.com with SMTP id s8so432700wxc.31
	for <emu@ietf.org>; Fri, 22 Feb 2008 08:24:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=liAXYASoi38Q50Wcv+hbAixSkGu0Nk5wYLazsGg8n6c=;
	b=AWb156+VkHEsUxWjM7mE6WjeA1CaCpqfKomEdcMPNeRiRH0qm4W8DDiK+M6XOkmhJ1vEZQryHj+dh1LiNJjcbStp7Gaj3U9I8p2hcapLiS8b9xc1BUPasxxXzqL5wdB4VN/bL/ZJHMiLp+/oFJZMcNmiV9hhFogWI+YLQpeDSVo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=tb51ypRl1eW/YlOOUxJbqhAzgvOSABbOw269H96yCzc6UYtXNPyfyHsP+Z8/kH5IMOf9KzyM1ZwQvPrMqYHAmAugQG1vMsmwXYjsyU9JnLzKUespHNH5V6Uyll+pXwQsjjYsDLyfr2nzY21P+m9rq9AG5pak6Dy4lzYIkoJH6Ro=
Received: by 10.141.116.16 with SMTP id t16mr118315rvm.60.1203697492637;
	Fri, 22 Feb 2008 08:24:52 -0800 (PST)
Received: by 10.141.186.14 with HTTP; Fri, 22 Feb 2008 08:24:52 -0800 (PST)
Message-ID: <5bfe7a820802220824h6393e269nb280164b5411f6b4@mail.gmail.com>
Date: Fri, 22 Feb 2008 08:24:52 -0800
From: "Dorothy Stanley" <dstanley1389@gmail.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
MIME-Version: 1.0
References: <AC1CFD94F59A264488DC2BEC3E890DE5054A86C5@xmb-sjc-225.amer.cisco.com>
Cc: emu@ietf.org
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0911675369=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

--===============0911675369==
Content-Type: multipart/alternative; 
	boundary="----=_Part_1330_14221562.1203697492633"

------=_Part_1330_14221562.1203697492633
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Joe,

I do not approve of the charter revision; the charter should not prohibit
the group
from using a non-tunneled method for the password-based method.
My previous mail gave a suggested charter text change.

I can participate as a reviewer.

Thanks,

Dorothy Stanley


On Tue, Feb 19, 2008 at 11:14 AM, Joseph Salowey (jsalowey) <
jsalowey@cisco.com> wrote:

> The response to the charter revision has been underwhelming.  I am a bit
> concerned that we do not have enough participation to complete the
> tunnel method work (most of the recent discussion has been about other
> methods).
>
> I would like to get an idea of the number working group members that
> approve of working on the tunnel method items and are able to
> participate in the development of requirements and specifications as
> contributors and/or reviewers.
>
> Please respond to this message and state whether you approve of the
> current charter revision and what capacity you would be willing to
> contribute towards tunneled method development: contributor, reviewer or
> not able to contribute.
>
> I have submitted an internet draft attempt at an outline of requirements
> for tunneled methods
> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
> txt<http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.txt>)
> that I hope can provided a starting point for discussions on the
> list and in the Philadelphia meeting.
>
> Thanks,
>
> Joe
>
> > -----Original Message-----
> > From: Joseph Salowey (jsalowey)
> > Sent: Monday, February 04, 2008 9:13 PM
> > To: emu@ietf.org
> > Subject: EMU charter revision
> >
> > Below is a revised charter update based on the discussion on
> > the list.  I have left the password based method item as a
> > tunnel method because this represents the consensus the
> > working group has reached.  I also believe the working group
> > will have to focus on the tunnel method related items for the
> > near term to make progress.  This does not mean that we
> > cannot work on additional methods as working group items in
> > the future.
> >
> > Please review the charter update and post any issues you have
> > with the carter.  Please also indicate if you have reviewed
> > the proposed charter and have no issues.  It is difficult to
> > judge working group consensus unless there are sufficient responses.
> >
> > Thanks,
> >
> > Joe
> >
> > Description of Working Group:
> > The Extensible Authentication Protocol (EAP) [RFC 3748] is a
> > network access authentication framework used in the PPP,
> > 802.11, 802.16, VPN, PANA, and in some functions in 3G
> > networks. EAP itself is a simple protocol and actual
> > authentication happens in EAP methods.
> >
> > Over 40 different EAP methods exist. Most of these methods
> > are proprietary methods and only a few methods are documented
> > in RFCs. The lack of documented, open specifications is a
> > deployment and interoperability problem. In addition, none of
> > the EAP methods in the standards track implement features
> > such as key derivation that are required for many modern
> > applications. This poses a problem for, among other things,
> > the selection of a mandatory to implement EAP method in new
> > network access technologies. For example, no standards track
> > methods meet new requirements such as those posed in RFC
> > 4017, which documents IEEE 802.11 requirements for EAP methods.
> >
> > This group is chartered to work on the following types of
> > mechanisms to meet RFC 3748 and RFC 4017 requirements:
> >
> > - An update to RFC 2716 to bring EAP-TLS into standards
> > track, clarify specification, interoperability, and
> > implementation issues gathered over the years, and update the
> > document to meet the requirements of RFC 3748, RFC 4017, and
> > EAP keying framework documents. Backwards compatibility with
> > RFC 2716 is a requirement.
> >
> > - A mechanism based on strong shared secrets that meets RFC
> > 3748 and RFC 4017 requirements. This mechanism should strive
> > to be simple and compact for implementation in resource
> > constrained environments.
> >
> > - A mechanism to support extensible communication within a
> > TLS protected tunnel that meets RFC 3748 and RFC 4017
> > requirements. This mechanism must support channel bindings in
> > order to meet RFC 4962 requirements and it must provide
> > cryptographic algorithm agility. This mechanism will support
> > meeting the requirements of an enhanced TLS mechanism, a
> > password based authentication mechanism, and additional inner
> > authentication mechanisms.
> >
> > - Enable a TLS-based EAP method to support channel bindings.
> > So as to enable RFC 2716bis to focus solely on clarifications
> > to the existing protocol, this effort will be handled in a
> > separate document.  This item will not generate a new method,
> > rather it will enhance EAP-TLS or the TLS based tunnel method
> > work item.
> >
> > - A mechanism meeting RFC 3748 and RFC 4017 requirements that
> > makes use of existing password databases such as AAA
> > databases.  This item will be based on the tunnel method work item.
> >
> > Goals and Milestones:
> > Done          Form design team to work on strong shared
> > secret mechanism
> > Done          Submit 2716bis I-D
> > Done          Submit first draft of shared secret mechanism I-D
> > Done          Form password based mechanism design team
> > Done          Submit 2716bis draft to IESG for Proposed Standard
> > Done          Submit Strong Shared Secret Mechanism to IESG
> > Apr 2008      Submit Tunnel and Password Method requirements
> > first draft
> > Jul 2008      Send Tunnel and Password Method requirements to IESG
> > Oct 2008      Submit Tunnel Method first draft
> > Nov 2008    Submit TLS based method channel binding first draft
> > Nov 2008      Submit Password Method first draft
> > Feb 2009      Send Tunnel Method to IESG
> > Apr 2009      Send TLS based method channel binding to IESG
> > Apr 2009      Send Password based method to IESG
> >
> >
> >
> >
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>

------=_Part_1330_14221562.1203697492633
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Joe,<br><br>I do not approve of the charter revision; the charter should not prohibit the group<br>from using a non-tunneled method for the password-based method. <br>My previous mail gave a suggested charter text change. <br>
<br>I can participate as a reviewer.<br><br>Thanks,<br><br>Dorothy Stanley<br><br><br><div class="gmail_quote">On Tue, Feb 19, 2008 at 11:14 AM, Joseph Salowey (jsalowey) &lt;<a href="mailto:jsalowey@cisco.com">jsalowey@cisco.com</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The response to the charter revision has been underwhelming. &nbsp;I am a bit<br>
concerned that we do not have enough participation to complete the<br>
tunnel method work (most of the recent discussion has been about other<br>
methods).<br>
<br>
I would like to get an idea of the number working group members that<br>
approve of working on the tunnel method items and are able to<br>
participate in the development of requirements and specifications as<br>
contributors and/or reviewers.<br>
<br>
Please respond to this message and state whether you approve of the<br>
current charter revision and what capacity you would be willing to<br>
contribute towards tunneled method development: contributor, reviewer or<br>
not able to contribute.<br>
<br>
I have submitted an internet draft attempt at an outline of requirements<br>
for tunneled methods<br>
(<a href="http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.txt" target="_blank">http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.<br>
txt</a>) that I hope can provided a starting point for discussions on the<br>
list and in the Philadelphia meeting.<br>
<br>
Thanks,<br>
<br>
Joe<br>
<div><div></div><div class="Wj3C7c"><br>
&gt; -----Original Message-----<br>
&gt; From: Joseph Salowey (jsalowey)<br>
&gt; Sent: Monday, February 04, 2008 9:13 PM<br>
&gt; To: <a href="mailto:emu@ietf.org">emu@ietf.org</a><br>
&gt; Subject: EMU charter revision<br>
&gt;<br>
&gt; Below is a revised charter update based on the discussion on<br>
&gt; the list. &nbsp;I have left the password based method item as a<br>
&gt; tunnel method because this represents the consensus the<br>
&gt; working group has reached. &nbsp;I also believe the working group<br>
&gt; will have to focus on the tunnel method related items for the<br>
&gt; near term to make progress. &nbsp;This does not mean that we<br>
&gt; cannot work on additional methods as working group items in<br>
&gt; the future.<br>
&gt;<br>
&gt; Please review the charter update and post any issues you have<br>
&gt; with the carter. &nbsp;Please also indicate if you have reviewed<br>
&gt; the proposed charter and have no issues. &nbsp;It is difficult to<br>
&gt; judge working group consensus unless there are sufficient responses.<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; Joe<br>
&gt;<br>
&gt; Description of Working Group:<br>
&gt; The Extensible Authentication Protocol (EAP) [RFC 3748] is a<br>
&gt; network access authentication framework used in the PPP,<br>
&gt; 802.11, 802.16, VPN, PANA, and in some functions in 3G<br>
&gt; networks. EAP itself is a simple protocol and actual<br>
&gt; authentication happens in EAP methods.<br>
&gt;<br>
&gt; Over 40 different EAP methods exist. Most of these methods<br>
&gt; are proprietary methods and only a few methods are documented<br>
&gt; in RFCs. The lack of documented, open specifications is a<br>
&gt; deployment and interoperability problem. In addition, none of<br>
&gt; the EAP methods in the standards track implement features<br>
&gt; such as key derivation that are required for many modern<br>
&gt; applications. This poses a problem for, among other things,<br>
&gt; the selection of a mandatory to implement EAP method in new<br>
&gt; network access technologies. For example, no standards track<br>
&gt; methods meet new requirements such as those posed in RFC<br>
&gt; 4017, which documents IEEE 802.11 requirements for EAP methods.<br>
&gt;<br>
&gt; This group is chartered to work on the following types of<br>
&gt; mechanisms to meet RFC 3748 and RFC 4017 requirements:<br>
&gt;<br>
&gt; - An update to RFC 2716 to bring EAP-TLS into standards<br>
&gt; track, clarify specification, interoperability, and<br>
&gt; implementation issues gathered over the years, and update the<br>
&gt; document to meet the requirements of RFC 3748, RFC 4017, and<br>
&gt; EAP keying framework documents. Backwards compatibility with<br>
&gt; RFC 2716 is a requirement.<br>
&gt;<br>
&gt; - A mechanism based on strong shared secrets that meets RFC<br>
&gt; 3748 and RFC 4017 requirements. This mechanism should strive<br>
&gt; to be simple and compact for implementation in resource<br>
&gt; constrained environments.<br>
&gt;<br>
&gt; - A mechanism to support extensible communication within a<br>
&gt; TLS protected tunnel that meets RFC 3748 and RFC 4017<br>
&gt; requirements. This mechanism must support channel bindings in<br>
&gt; order to meet RFC 4962 requirements and it must provide<br>
&gt; cryptographic algorithm agility. This mechanism will support<br>
&gt; meeting the requirements of an enhanced TLS mechanism, a<br>
&gt; password based authentication mechanism, and additional inner<br>
&gt; authentication mechanisms.<br>
&gt;<br>
&gt; - Enable a TLS-based EAP method to support channel bindings.<br>
&gt; So as to enable RFC 2716bis to focus solely on clarifications<br>
&gt; to the existing protocol, this effort will be handled in a<br>
&gt; separate document. &nbsp;This item will not generate a new method,<br>
&gt; rather it will enhance EAP-TLS or the TLS based tunnel method<br>
&gt; work item.<br>
&gt;<br>
&gt; - A mechanism meeting RFC 3748 and RFC 4017 requirements that<br>
&gt; makes use of existing password databases such as AAA<br>
&gt; databases. &nbsp;This item will be based on the tunnel method work item.<br>
&gt;<br>
&gt; Goals and Milestones:<br>
&gt; Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Form design team to work on strong shared<br>
&gt; secret mechanism<br>
&gt; Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submit 2716bis I-D<br>
&gt; Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submit first draft of shared secret mechanism I-D<br>
&gt; Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Form password based mechanism design team<br>
&gt; Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submit 2716bis draft to IESG for Proposed Standard<br>
&gt; Done &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submit Strong Shared Secret Mechanism to IESG<br>
&gt; Apr 2008 &nbsp; &nbsp; &nbsp;Submit Tunnel and Password Method requirements<br>
&gt; first draft<br>
&gt; Jul 2008 &nbsp; &nbsp; &nbsp;Send Tunnel and Password Method requirements to IESG<br>
&gt; Oct 2008 &nbsp; &nbsp; &nbsp;Submit Tunnel Method first draft<br>
&gt; Nov 2008 &nbsp; &nbsp;Submit TLS based method channel binding first draft<br>
&gt; Nov 2008 &nbsp; &nbsp; &nbsp;Submit Password Method first draft<br>
&gt; Feb 2009 &nbsp; &nbsp; &nbsp;Send Tunnel Method to IESG<br>
&gt; Apr 2009 &nbsp; &nbsp; &nbsp;Send TLS based method channel binding to IESG<br>
&gt; Apr 2009 &nbsp; &nbsp; &nbsp;Send Password based method to IESG<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
Emu mailing list<br>
<a href="mailto:Emu@ietf.org">Emu@ietf.org</a><br>
<a href="http://www.ietf.org/mailman/listinfo/emu" target="_blank">http://www.ietf.org/mailman/listinfo/emu</a><br>
</div></div></blockquote></div><br>

------=_Part_1330_14221562.1203697492633--

--===============0911675369==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu

--===============0911675369==--


From emu-bounces@ietf.org  Fri Feb 22 10:22:54 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 319FB28C3C2;
	Fri, 22 Feb 2008 10:22:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.879
X-Spam-Level: 
X-Spam-Status: No, score=-0.879 tagged_above=-999 required=5
	tests=[AWL=-0.442, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rl6TYSUJHgQX; Fri, 22 Feb 2008 10:22:53 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D17293A6C47;
	Fri, 22 Feb 2008 10:22:52 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B154F3A6CA7
	for <emu@core3.amsl.com>; Fri, 22 Feb 2008 10:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VAf3C+wHS93l for <emu@core3.amsl.com>;
	Fri, 22 Feb 2008 10:22:49 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174])
	by core3.amsl.com (Postfix) with ESMTP id 38E0828C33F
	for <emu@ietf.org>; Fri, 22 Feb 2008 10:22:23 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1])
	by colo.trepanning.net (Postfix) with ESMTP id 491561FA6217;
	Fri, 22 Feb 2008 10:22:19 -0800 (PST)
Received: from 216.31.249.246
	(SquirrelMail authenticated user dharkins@lounge.org)
	by www.trepanning.net with HTTP;
	Fri, 22 Feb 2008 10:22:19 -0800 (PST)
Message-ID: <22167.216.31.249.246.1203704539.squirrel@www.trepanning.net>
In-Reply-To: <5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
	<5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
Date: Fri, 22 Feb 2008 10:22:19 -0800 (PST)
From: "Dan Harkins" <dharkins@lounge.org>
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Cc: ext Bernard Aboba <bernard_aboba@hotmail.com>, emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org


  Hi Hannes,

  What are these methods? And is their security completely based
on an assumption that the one deploying this method is following
some strict regime (e.g. no weak passwords)?

  regards,

  Dan.

On Fri, February 22, 2008 6:34 am, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
> Hi Bernard,
>
> a question your excitment regarding strong password based EAP method.
>
> Why do you think they are useful? There are other ways (and they are
> deployed already) that can accomplish the same result without going
> along the SRP & co track.
> Is it because you expect performance improvements or because the
> crypto-mechanisms look nicer?
>
> I cannot quite understand the motivation.
>
> Ciao
> Hannes
>
> ________________________________
>
> 	Von: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] Im
> Auftrag von ext Bernard Aboba
> 	Gesendet: Donnerstag, 21. Februar 2008 21:54
> 	An: emu@ietf.org
> 	Betreff: Re: [Emu] EMU Charter revision
>
>
> 	I also do NOT approve of the current charter revision, for
> several reasons:
>
> 	a.  The Charter text contains statements that are no longer
> true.  For example:
>
> 	"Most of these methods are proprietary methods and only a few
> methods
> 	are documented in RFCs."
>
> 	The following EAP methods are now documented in RFCs:
>
> 	EAP-TLS (RFC 2716)
> 	EAP-SIM (RFC 4186)
> 	EAP-AKA (RFC 4187)
> 	EAP-PAX (RFC 4746)
> 	EAP-SAKE (RFC 4763)
> 	EAP-PSK (RFC 4764)
> 	EAP-POTP (RFC 4793)
> 	EAP-FAST (RFC 4851)
> 	EAP-IKEv2 (RFC 5106)
>
> 	9 methods claiming to satify RFC 4017 critieria is more than a
> "few".
>
> 	b. The Charter requires support for Channel Bindings without
> doing the
> 	preparatory work to define how Channel Bindings works.  Either
> the
> 	requirement should be removed, or a work item should be added to
>
> 	better define the approach to Channel Bindings.
>
> 	c. The text on tunnel methods does not provide enough guidance
> to avoid
> 	potentially fruitless arguments.  So far, the EMU WG has not
> been able
> 	to come to consensus on selection of one of the existing
> tunneling
> 	protocols, and efforts to design "yet another" tunneling
> protocol
> 	haven't gotten very far either.  I'd like to see more specific
> 	language that would make it clear that work on improving
> existing
> 	tunneling protocols is within scope, and also that the EMU WG,
> 	if it cannot come to consensus on a single protocol, can proceed
> to
> 	work on one or more protocols with significant support.
>
> 	d. Password-based methods.  While I can understand the desire to
> limit the
> 	number of charter items, I do agree with Dan that work on
> weak-password
> 	methods is important.  With some of the IPR obstacles likely to
> fall by
> 	the wayside in coming years, it is time for the IETF to re-visit
> its policy
> 	on inclusion of "zero knowledge" algorithms within standards
> track documents.
> 	Dan Harkins said:
>
> 	" Hi Joe,
>
>
> 	  I do NOT approve of the current charter revision, specifically
> the
> 	change that says the password-based method can only be via the
> 	tunneled method. I do approve of the inclusion of tunneled
> methods
> 	in the charter though and would be willing to contribute as a
> 	reviewer.
>
> 	  regards,
>
> 	  Dan."
> 	On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey)
> wrote:
> 	> The response to the charter revision has been underwhelming.
> I am a bit
> 	> concerned that we do not have enough participation to complete
> the
> 	> tunnel method work (most of the recent discussion has been
> about other
> 	> methods).
> 	>
> 	> I would like to get an idea of the number working group
> members that
> 	> approve of working on the tunnel method items and are able to
> 	> participate in the development of requirements and
> specifications as
> 	> contributors and/or reviewers.
> 	>
> 	> Please respond to this message and state whether you approve
> of the
> 	> current charter revision and what capacity you would be
> willing to
> 	> contribute towards tunneled method development: contributor,
> reviewer or
> 	> not able to contribute.
> 	>
> 	> I have submitted an internet draft attempt at an outline of
> requirements
> 	> for tunneled methods
> 	>
> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
> 	> txt) that I hope can provided a starting point for discussions
> on the
> 	> list and in the Philadelphia meeting.
> 	>
> 	> Thanks,
> 	>
> 	> Joe
>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>


_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Fri Feb 22 11:14:22 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B04EE28C472;
	Fri, 22 Feb 2008 11:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.552
X-Spam-Level: 
X-Spam-Status: No, score=-0.552 tagged_above=-999 required=5
	tests=[AWL=-0.115, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y16oXeIfdZVc; Fri, 22 Feb 2008 11:14:21 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB06C28C3EF;
	Fri, 22 Feb 2008 11:14:21 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C7743A6C5D
	for <emu@core3.amsl.com>; Fri, 22 Feb 2008 11:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rh-RMUrC9T0y for <emu@core3.amsl.com>;
	Fri, 22 Feb 2008 11:14:19 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id D1F7E3A6BB9
	for <emu@ietf.org>; Fri, 22 Feb 2008 11:14:18 -0800 (PST)
Received: (qmail invoked by alias); 22 Feb 2008 19:14:13 -0000
Received: from proxy2-nsn.nsn-inter.net (EHLO [217.115.75.230])
	[217.115.75.230]
	by mail.gmx.net (mp055) with SMTP; 22 Feb 2008 20:14:13 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19dSRQraMJdYRE208Wb4USnkl/cHan7UEytvagfQv
	JSLrbUhladibw5
Message-ID: <47BF1EFF.7030802@gmx.net>
Date: Fri, 22 Feb 2008 21:14:07 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Dan Harkins <dharkins@lounge.org>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>	<5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
	<22167.216.31.249.246.1203704539.squirrel@www.trepanning.net>
In-Reply-To: <22167.216.31.249.246.1203704539.squirrel@www.trepanning.net>
X-Y-GMX-Trusted: 0
Cc: ext Bernard Aboba <bernard_aboba@hotmail.com>, emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Hannes.Tschofenig@gmx.net
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Hi Dan,

you are asking me which EAP methods support weak passwords?

If so, here are a few examples:
* TTLS
* PEAP
* EAP-PAX
* EAP-FAST
* EAP-IKEv2

Please note that I am not against doing the work; I would just like to 
understand what the main motivation is.

Ciao
Hannes

Dan Harkins wrote:
>   Hi Hannes,
>
>   What are these methods? And is their security completely based
> on an assumption that the one deploying this method is following
> some strict regime (e.g. no weak passwords)?
>
>   regards,
>
>   Dan.
>
> On Fri, February 22, 2008 6:34 am, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>   
>> Hi Bernard,
>>
>> a question your excitment regarding strong password based EAP method.
>>
>> Why do you think they are useful? There are other ways (and they are
>> deployed already) that can accomplish the same result without going
>> along the SRP & co track.
>> Is it because you expect performance improvements or because the
>> crypto-mechanisms look nicer?
>>
>> I cannot quite understand the motivation.
>>
>> Ciao
>> Hannes
>>
>> ________________________________
>>
>> 	Von: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] Im
>> Auftrag von ext Bernard Aboba
>> 	Gesendet: Donnerstag, 21. Februar 2008 21:54
>> 	An: emu@ietf.org
>> 	Betreff: Re: [Emu] EMU Charter revision
>>
>>
>> 	I also do NOT approve of the current charter revision, for
>> several reasons:
>>
>> 	a.  The Charter text contains statements that are no longer
>> true.  For example:
>>
>> 	"Most of these methods are proprietary methods and only a few
>> methods
>> 	are documented in RFCs."
>>
>> 	The following EAP methods are now documented in RFCs:
>>
>> 	EAP-TLS (RFC 2716)
>> 	EAP-SIM (RFC 4186)
>> 	EAP-AKA (RFC 4187)
>> 	EAP-PAX (RFC 4746)
>> 	EAP-SAKE (RFC 4763)
>> 	EAP-PSK (RFC 4764)
>> 	EAP-POTP (RFC 4793)
>> 	EAP-FAST (RFC 4851)
>> 	EAP-IKEv2 (RFC 5106)
>>
>>     

	

>> 	9 methods claiming to satify RFC 4017 critieria is more than a
>> "few".
>>
>> 	b. The Charter requires support for Channel Bindings without
>> doing the
>> 	preparatory work to define how Channel Bindings works.  Either
>> the
>> 	requirement should be removed, or a work item should be added to
>>
>> 	better define the approach to Channel Bindings.
>>
>> 	c. The text on tunnel methods does not provide enough guidance
>> to avoid
>> 	potentially fruitless arguments.  So far, the EMU WG has not
>> been able
>> 	to come to consensus on selection of one of the existing
>> tunneling
>> 	protocols, and efforts to design "yet another" tunneling
>> protocol
>> 	haven't gotten very far either.  I'd like to see more specific
>> 	language that would make it clear that work on improving
>> existing
>> 	tunneling protocols is within scope, and also that the EMU WG,
>> 	if it cannot come to consensus on a single protocol, can proceed
>> to
>> 	work on one or more protocols with significant support.
>>
>> 	d. Password-based methods.  While I can understand the desire to
>> limit the
>> 	number of charter items, I do agree with Dan that work on
>> weak-password
>> 	methods is important.  With some of the IPR obstacles likely to
>> fall by
>> 	the wayside in coming years, it is time for the IETF to re-visit
>> its policy
>> 	on inclusion of "zero knowledge" algorithms within standards
>> track documents.
>> 	Dan Harkins said:
>>
>> 	" Hi Joe,
>>
>>
>> 	  I do NOT approve of the current charter revision, specifically
>> the
>> 	change that says the password-based method can only be via the
>> 	tunneled method. I do approve of the inclusion of tunneled
>> methods
>> 	in the charter though and would be willing to contribute as a
>> 	reviewer.
>>
>> 	  regards,
>>
>> 	  Dan."
>> 	On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey)
>> wrote:
>> 	> The response to the charter revision has been underwhelming.
>> I am a bit
>> 	> concerned that we do not have enough participation to complete
>> the
>> 	> tunnel method work (most of the recent discussion has been
>> about other
>> 	> methods).
>> 	>
>> 	> I would like to get an idea of the number working group
>> members that
>> 	> approve of working on the tunnel method items and are able to
>> 	> participate in the development of requirements and
>> specifications as
>> 	> contributors and/or reviewers.
>> 	>
>> 	> Please respond to this message and state whether you approve
>> of the
>> 	> current charter revision and what capacity you would be
>> willing to
>> 	> contribute towards tunneled method development: contributor,
>> reviewer or
>> 	> not able to contribute.
>> 	>
>> 	> I have submitted an internet draft attempt at an outline of
>> requirements
>> 	> for tunneled methods
>> 	>
>> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
>> 	> txt) that I hope can provided a starting point for discussions
>> on the
>> 	> list and in the Philadelphia meeting.
>> 	>
>> 	> Thanks,
>> 	>
>> 	> Joe
>>
>>
>> _______________________________________________
>> Emu mailing list
>> Emu@ietf.org
>> http://www.ietf.org/mailman/listinfo/emu
>>
>>     
>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>   

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Fri Feb 22 12:40:23 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B33AD28C5A9;
	Fri, 22 Feb 2008 12:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.866
X-Spam-Level: 
X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5
	tests=[AWL=-0.429, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AFpKQEISmuwb; Fri, 22 Feb 2008 12:40:22 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F203A28CC10;
	Fri, 22 Feb 2008 12:37:16 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60A0428CA21
	for <emu@core3.amsl.com>; Fri, 22 Feb 2008 12:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CUXSbdvrZn8B for <emu@core3.amsl.com>;
	Fri, 22 Feb 2008 12:37:12 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174])
	by core3.amsl.com (Postfix) with ESMTP id E912828C5A9
	for <emu@ietf.org>; Fri, 22 Feb 2008 12:32:53 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1])
	by colo.trepanning.net (Postfix) with ESMTP id EDF9A1FA6217;
	Fri, 22 Feb 2008 12:32:49 -0800 (PST)
Received: from 216.31.249.246
	(SquirrelMail authenticated user dharkins@lounge.org)
	by www.trepanning.net with HTTP;
	Fri, 22 Feb 2008 12:32:49 -0800 (PST)
Message-ID: <13062.216.31.249.246.1203712369.squirrel@www.trepanning.net>
In-Reply-To: <47BF1EFF.7030802@gmx.net>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
	<5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
	<22167.216.31.249.246.1203704539.squirrel@www.trepanning.net>
	<47BF1EFF.7030802@gmx.net>
Date: Fri, 22 Feb 2008 12:32:49 -0800 (PST)
From: "Dan Harkins" <dharkins@lounge.org>
To: Hannes.Tschofenig@gmx.net
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Cc: ext Bernard Aboba <bernard_aboba@hotmail.com>, emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org


  Hi Hannes,

  The first 4 of those require a certificate (well, PAX doesn't but as
it says in its Security Considerations if you don't use one then it's
open to dictionary attack) and in some situations it is desirable to not
have one.

  From personal experience I have run into scores and scores of
systems that get deployed using self-signed certificates and then
something that is not resistant to dictionary attack as the client-side
authentication method. So the end result is a system that does not
have the properties that the protocols it implements claim it should
have. The fact that "verify server certificate" is an option underscores
this problem.

  I think it is very valuable to have protocols that are secure in the
presence of poor operational deployment. We all know things will get
deployed in the most expeditious manner possible so having protocols
that remain secure in the presence of weak passwords or self-signed
certificates or whathaveyou is A Good Thing (tm). They are robust, not
fragile.

  About EAP-IKEv2.... Please don't take offense but I think it is
an abomination. We can have EAP-IKEv2 with AAA1 authenticating with a
certificate and the client doing EAP for client-side authentication
which gets passed to AAA2 which does TTLS (or FAST or PEAP) and
authenticates with its own certificate and the client authentication
is...EAP! Which gets passed to AAA3 where EAP-MSCHAPv2 is done and
AAA4 is asked if some particular username/password is correct or not.
Is that username the same as the one provided in EAP-IKEv2 or in TTLS?
Who knows! But some server somewhere says that a single username/password
combination is correct and that's just supposed to be OK. Note that if
a TLS ciphersuite to do EAP for client-side authentication goes past
I-D stage then this can be extended several more steps, involving AAA5
and AAA6, without even duplicating EAP methods anywhere.

  regards,

  Dan.

On Fri, February 22, 2008 11:14 am, Hannes Tschofenig wrote:
> Hi Dan,
>
> you are asking me which EAP methods support weak passwords?
>
> If so, here are a few examples:
> * TTLS
> * PEAP
> * EAP-PAX
> * EAP-FAST
> * EAP-IKEv2
>
> Please note that I am not against doing the work; I would just like to
> understand what the main motivation is.
>
> Ciao
> Hannes
>
> Dan Harkins wrote:
>>   Hi Hannes,
>>
>>   What are these methods? And is their security completely based
>> on an assumption that the one deploying this method is following
>> some strict regime (e.g. no weak passwords)?
>>
>>   regards,
>>
>>   Dan.
>>
>> On Fri, February 22, 2008 6:34 am, Tschofenig, Hannes (NSN - FI/Espoo)
>> wrote:
>>
>>> Hi Bernard,
>>>
>>> a question your excitment regarding strong password based EAP method.
>>>
>>> Why do you think they are useful? There are other ways (and they are
>>> deployed already) that can accomplish the same result without going
>>> along the SRP & co track.
>>> Is it because you expect performance improvements or because the
>>> crypto-mechanisms look nicer?
>>>
>>> I cannot quite understand the motivation.
>>>
>>> Ciao
>>> Hannes
>>>
>>> ________________________________
>>>
>>> 	Von: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] Im
>>> Auftrag von ext Bernard Aboba
>>> 	Gesendet: Donnerstag, 21. Februar 2008 21:54
>>> 	An: emu@ietf.org
>>> 	Betreff: Re: [Emu] EMU Charter revision
>>>
>>>
>>> 	I also do NOT approve of the current charter revision, for
>>> several reasons:
>>>
>>> 	a.  The Charter text contains statements that are no longer
>>> true.  For example:
>>>
>>> 	"Most of these methods are proprietary methods and only a few
>>> methods
>>> 	are documented in RFCs."
>>>
>>> 	The following EAP methods are now documented in RFCs:
>>>
>>> 	EAP-TLS (RFC 2716)
>>> 	EAP-SIM (RFC 4186)
>>> 	EAP-AKA (RFC 4187)
>>> 	EAP-PAX (RFC 4746)
>>> 	EAP-SAKE (RFC 4763)
>>> 	EAP-PSK (RFC 4764)
>>> 	EAP-POTP (RFC 4793)
>>> 	EAP-FAST (RFC 4851)
>>> 	EAP-IKEv2 (RFC 5106)
>>>
>>>
>
>
>
>>> 	9 methods claiming to satify RFC 4017 critieria is more than a
>>> "few".
>>>
>>> 	b. The Charter requires support for Channel Bindings without
>>> doing the
>>> 	preparatory work to define how Channel Bindings works.  Either
>>> the
>>> 	requirement should be removed, or a work item should be added to
>>>
>>> 	better define the approach to Channel Bindings.
>>>
>>> 	c. The text on tunnel methods does not provide enough guidance
>>> to avoid
>>> 	potentially fruitless arguments.  So far, the EMU WG has not
>>> been able
>>> 	to come to consensus on selection of one of the existing
>>> tunneling
>>> 	protocols, and efforts to design "yet another" tunneling
>>> protocol
>>> 	haven't gotten very far either.  I'd like to see more specific
>>> 	language that would make it clear that work on improving
>>> existing
>>> 	tunneling protocols is within scope, and also that the EMU WG,
>>> 	if it cannot come to consensus on a single protocol, can proceed
>>> to
>>> 	work on one or more protocols with significant support.
>>>
>>> 	d. Password-based methods.  While I can understand the desire to
>>> limit the
>>> 	number of charter items, I do agree with Dan that work on
>>> weak-password
>>> 	methods is important.  With some of the IPR obstacles likely to
>>> fall by
>>> 	the wayside in coming years, it is time for the IETF to re-visit
>>> its policy
>>> 	on inclusion of "zero knowledge" algorithms within standards
>>> track documents.
>>> 	Dan Harkins said:
>>>
>>> 	" Hi Joe,
>>>
>>>
>>> 	  I do NOT approve of the current charter revision, specifically
>>> the
>>> 	change that says the password-based method can only be via the
>>> 	tunneled method. I do approve of the inclusion of tunneled
>>> methods
>>> 	in the charter though and would be willing to contribute as a
>>> 	reviewer.
>>>
>>> 	  regards,
>>>
>>> 	  Dan."
>>> 	On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey)
>>> wrote:
>>> 	> The response to the charter revision has been underwhelming.
>>> I am a bit
>>> 	> concerned that we do not have enough participation to complete
>>> the
>>> 	> tunnel method work (most of the recent discussion has been
>>> about other
>>> 	> methods).
>>> 	>
>>> 	> I would like to get an idea of the number working group
>>> members that
>>> 	> approve of working on the tunnel method items and are able to
>>> 	> participate in the development of requirements and
>>> specifications as
>>> 	> contributors and/or reviewers.
>>> 	>
>>> 	> Please respond to this message and state whether you approve
>>> of the
>>> 	> current charter revision and what capacity you would be
>>> willing to
>>> 	> contribute towards tunneled method development: contributor,
>>> reviewer or
>>> 	> not able to contribute.
>>> 	>
>>> 	> I have submitted an internet draft attempt at an outline of
>>> requirements
>>> 	> for tunneled methods
>>> 	>
>>> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
>>> 	> txt) that I hope can provided a starting point for discussions
>>> on the
>>> 	> list and in the Philadelphia meeting.
>>> 	>
>>> 	> Thanks,
>>> 	>
>>> 	> Joe
>>>
>>>
>>> _______________________________________________
>>> Emu mailing list
>>> Emu@ietf.org
>>> http://www.ietf.org/mailman/listinfo/emu
>>>
>>>
>>
>>
>> _______________________________________________
>> Emu mailing list
>> Emu@ietf.org
>> http://www.ietf.org/mailman/listinfo/emu
>>
>
>


_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Fri Feb 22 13:23:44 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF18B3A6C1F;
	Fri, 22 Feb 2008 13:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.515
X-Spam-Level: 
X-Spam-Status: No, score=-0.515 tagged_above=-999 required=5
	tests=[AWL=-1.078, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lork8B7HjzCY; Fri, 22 Feb 2008 13:23:42 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12EDE3A6D2C;
	Fri, 22 Feb 2008 13:23:42 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 895773A6875
	for <emu@core3.amsl.com>; Fri, 22 Feb 2008 13:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8481+I2TlSTJ for <emu@core3.amsl.com>;
	Fri, 22 Feb 2008 13:23:38 -0800 (PST)
Received: from blu139-omc1-s23.blu139.hotmail.com
	(blu139-omc1-s23.blu139.hotmail.com [65.55.175.163])
	by core3.amsl.com (Postfix) with ESMTP id 7F22A3A6C6B
	for <emu@ietf.org>; Fri, 22 Feb 2008 13:23:37 -0800 (PST)
Received: from BLU137-W6 ([65.55.162.182]) by
	blu139-omc1-s23.blu139.hotmail.com with Microsoft
	SMTPSVC(6.0.3790.3959); Fri, 22 Feb 2008 13:23:33 -0800
Message-ID: <BLU137-W6942A03929159E244DCC6931D0@phx.gbl>
X-Originating-IP: [208.54.15.12]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>,
	<emu@ietf.org>
Date: Fri, 22 Feb 2008 13:23:33 -0800
Importance: Normal
In-Reply-To: <5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
	<5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
MIME-Version: 1.0
X-OriginalArrivalTime: 22 Feb 2008 21:23:33.0256 (UTC)
	FILETIME=[2D6C0880:01C87599]
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0906773856=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

--===============0906773856==
Content-Type: multipart/alternative;
	boundary="_9ecca39d-654a-4ffb-826c-42178ecd0407_"

--_9ecca39d-654a-4ffb-826c-42178ecd0407_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


"Zero knowledge" is definitely crypto-intensive.  For example, to get both =
privacy and strong password protection, at least two DHs are required.=20

However, there are circumstances where server-side certificates aren't acce=
ptable.  Even in today, many/(most?) EAP deployments do not involve certifi=
cates (e.g. LEAP, FAST).   Even if "zero knowledge" isn't used on an ongoin=
g basis (out of concern for load, for example), it still can be useful for =
initial provisioning.  For example, EAP FAST provisioning is vulnerable to =
man-in-the-middle attack or dictionary attack, which could be removed with =
use of "zero knowledge" algorithms.   =20

Subject: AW: [Emu] EMU Charter revision
Date: Fri, 22 Feb 2008 15:34:56 +0100
From: hannes.tschofenig@nsn.com
To: bernard_aboba@hotmail.com; emu@ietf.org










Hi Bernard,
=20
a question your excitment regarding strong password based EAP=20
method.=20
=20
Why do you think they are useful? There are other ways (and they=20
are deployed already) that can accomplish the same result without going=20
along the SRP & co track.=20
Is it because you expect performance improvements or because the=20
crypto-mechanisms look nicer?=20
=20
I cannot quite understand the motivation.=20
=20
Ciao
Hannes

 =20
 =20
  Von: emu-bounces@ietf.org=20
  [mailto:emu-bounces@ietf.org] Im Auftrag von ext Bernard=20
  Aboba
Gesendet: Donnerstag, 21. Februar 2008 21:54
An:=20
  emu@ietf.org
Betreff: Re: [Emu] EMU Charter=20
  revision


  I also do NOT approve of the current charter revision, for several=20
  reasons:

a.  The Charter text contains statements that are no=20
  longer true.  For example:
"Most of these methods are proprietary methods and only a few methods=20
are documented in RFCs."

The following EAP methods are now documented in RFCs:

EAP-TLS (RFC 2716)
EAP-SIM (RFC 4186)
EAP-AKA (RFC 4187)
EAP-PAX (RFC 4746)
EAP-SAKE (RFC 4763)
EAP-PSK (RFC 4764)
EAP-POTP (RFC 4793)
EAP-FAST (RFC 4851)
EAP-IKEv2 (RFC 5106)

9 methods claiming to satify RFC 4017 critieria is more than a "few".=20

b. The Charter requires support for Channel Bindings without doing the
preparatory work to define how Channel Bindings works.  Either the
requirement should be removed, or a work item should be added to=20
better define the approach to Channel Bindings.=20

c. The text on tunnel methods does not provide enough guidance to avoid
potentially fruitless arguments.  So far, the EMU WG has not been able
to come to consensus on selection of one of the existing tunneling
protocols, and efforts to design "yet another" tunneling protocol=20
haven't gotten very far either.  I'd like to see more specific=20
language that would make it clear that work on improving existing
tunneling protocols is within scope, and also that the EMU WG,
if it cannot come to consensus on a single protocol, can proceed to=20
work on one or more protocols with significant support. =20

d. Password-based methods.  While I can understand the desire to limit the
number of charter items, I do agree with Dan that work on weak-password
methods is important.  With some of the IPR obstacles likely to fall by
the wayside in coming years, it is time for the IETF to re-visit its policy
on inclusion of "zero knowledge" algorithms within standards track document=
s.=20
Dan=20
  Harkins said:

" Hi Joe,

  I do NOT approve of the current charter revision, specifically the
change that says the password-based method can only be via the
tunneled method. I do approve of the inclusion of tunneled methods
in the charter though and would be willing to contribute as a
reviewer.

  regards,

  Dan."
On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:
> The response to the charter revision has been underwhelming.  I am a bit
> concerned that we do not have enough participation to complete the
> tunnel method work (most of the recent discussion has been about other
> methods).
>
> I would like to get an idea of the number working group members that
> approve of working on the tunnel method items and are able to
> participate in the development of requirements and specifications as
> contributors and/or reviewers.
>
> Please respond to this message and state whether you approve of the
> current charter revision and what capacity you would be willing to
> contribute towards tunneled method development: contributor, reviewer or
> not able to contribute.
>
> I have submitted an internet draft attempt at an outline of requirements
> for tunneled methods
> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
> txt) that I hope can provided a starting point for discussions on the
> list and in the Philadelphia meeting.
>
> Thanks,
>
> Joe


--_9ecca39d-654a-4ffb-826c-42178ecd0407_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
<span style=3D"font-family: Geneva,Arial,Sans-serif;">"Zero knowledge" is d=
efinitely crypto-intensive.&nbsp; For example, to get both privacy and stro=
ng password protection, at least two DHs are required. <br><br>However, the=
re are circumstances where server-side certificates aren't acceptable.&nbsp=
; Even in today, many/(most?) EAP deployments do not involve certificates (=
e.g. LEAP, FAST). &nbsp; Even if "zero knowledge" isn't used on an ongoing =
basis (out of concern for load, for example), it still can be useful for in=
itial provisioning.&nbsp; For example, EAP FAST provisioning is vulnerable =
to man-in-the-middle attack or dictionary attack, which could be removed wi=
th use of "zero knowledge" algorithms. &nbsp;  <br></span><br><blockquote><=
hr>Subject: AW: [Emu] EMU Charter revision<br>Date: Fri, 22 Feb 2008 15:34:=
56 +0100<br>From: hannes.tschofenig@nsn.com<br>To: bernard_aboba@hotmail.co=
m; emu@ietf.org<br><br>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dunicode">
<meta name=3D"Generator" content=3D"Microsoft SafeHTML">

<style>
.ExternalClass .EC_hmmessage P
{padding-right:0px;padding-left:0px;padding-bottom:0px;padding-top:0px;}
.ExternalClass EC_BODY.hmmessage
{font-size:10pt;font-family:Tahoma;}
</style>



<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial">Hi Bernard,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial">a question your excitment regarding stron=
g password based EAP=20
method. </font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial">Why do you think they are useful? There a=
re other ways (and they=20
are deployed already)&nbsp;that can accomplish the same result without goin=
g=20
along the SRP &amp; co track. </font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial">Is it because you expect performance impr=
ovements or because the=20
crypto-mechanisms look nicer? </font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial">I cannot quite understand the motivation.=
 </font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"EC_900193707-22022008"><font=
 color=3D"#0000ff" face=3D"Arial">Ciao<br>Hannes</font></span></div>
<blockquote style=3D"border-left: 2px solid rgb(0, 0, 255); padding-left: 5=
px; margin-left: 5px; margin-right: 0px;">
  <div class=3D"EC_OutlookMessageHeader" dir=3D"ltr" align=3D"left" lang=3D=
"de">
  <hr>
  <font face=3D"Tahoma"><b>Von:</b> emu-bounces@ietf.org=20
  [mailto:emu-bounces@ietf.org] <b>Im Auftrag von </b>ext Bernard=20
  Aboba<br><b>Gesendet:</b> Donnerstag, 21. Februar 2008 21:54<br><b>An:</b=
>=20
  emu@ietf.org<br><b>Betreff:</b> Re: [Emu] EMU Charter=20
  revision<br></font><br></div>
  <div></div>I also do NOT approve of the current charter revision, for sev=
eral=20
  reasons:<br><br>a.&nbsp; The Charter text contains statements that are no=
=20
  longer true.&nbsp; For example:<br><pre>"Most of these methods are propri=
etary methods and only a few methods <br>are documented in RFCs."<br><br>Th=
e following EAP methods are now documented in RFCs:<br><br>EAP-TLS (RFC 271=
6)<br>EAP-SIM (RFC 4186)<br>EAP-AKA (RFC 4187)<br>EAP-PAX (RFC 4746)<br>EAP=
-SAKE (RFC 4763)<br>EAP-PSK (RFC 4764)<br>EAP-POTP (RFC 4793)<br>EAP-FAST (=
RFC 4851)<br>EAP-IKEv2 (RFC 5106)<br><br>9 methods claiming to satify RFC 4=
017 critieria is more than a "few". <br><br>b. The Charter requires support=
 for Channel Bindings without doing the<br>preparatory work to define how C=
hannel Bindings works.  Either the<br>requirement should be removed, or a w=
ork item should be added to <br>better define the approach to Channel Bindi=
ngs. <br><br>c. The text on tunnel methods does not provide enough guidance=
 to avoid<br>potentially fruitless arguments.  So far, the EMU WG has not b=
een able<br>to come to consensus on selection of one of the existing tunnel=
ing<br>protocols, and efforts to design "yet another" tunneling protocol <b=
r>haven't gotten very far either.  I'd like to see more specific <br>langua=
ge that would make it clear that work on improving existing<br>tunneling pr=
otocols is within scope, and also that the EMU WG,<br>if it cannot come to =
consensus on a single protocol, can proceed to <br>work on one or more prot=
ocols with significant support.  <br><br>d. Password-based methods.  While =
I can understand the desire to limit the<br>number of charter items, I do a=
gree with Dan that work on weak-password<br>methods is important.  With som=
e of the IPR obstacles likely to fall by<br>the wayside in coming years, it=
 is time for the IETF to re-visit its policy<br>on inclusion of "zero knowl=
edge" algorithms within standards track documents. <br></pre>Dan=20
  Harkins said:<br><br>" Hi Joe,<br><pre><br>  I do NOT approve of the curr=
ent charter revision, specifically the<br>change that says the password-bas=
ed method can only be via the<br>tunneled method. I do approve of the inclu=
sion of tunneled methods<br>in the charter though and would be willing to c=
ontribute as a<br>reviewer.<br><br>  regards,<br><br>  Dan."<br></pre><pre>=
On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:<br>&gt=
; The response to the charter revision has been underwhelming.  I am a bit<=
br>&gt; concerned that we do not have enough participation to complete the<=
br>&gt; tunnel method work (most of the recent discussion has been about ot=
her<br>&gt; methods).<br>&gt;<br>&gt; I would like to get an idea of the nu=
mber working group members that<br>&gt; approve of working on the tunnel me=
thod items and are able to<br>&gt; participate in the development of requir=
ements and specifications as<br>&gt; contributors and/or reviewers.<br>&gt;=
<br>&gt; Please respond to this message and state whether you approve of th=
e<br>&gt; current charter revision and what capacity you would be willing t=
o<br>&gt; contribute towards tunneled method development: contributor, revi=
ewer or<br>&gt; not able to contribute.<br>&gt;<br>&gt; I have submitted an=
 internet draft attempt at an outline of requirements<br>&gt; for tunneled =
methods<br>&gt; (<a href=3D"http://www.ietf.org/internet-drafts/draft-salow=
ey-emu-eaptunnel-req-00" rel=3D"nofollow" target=3D"_blank">http://www.ietf=
.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00</a>.<br>&gt; txt) t=
hat I hope can provided a starting point for discussions on the<br>&gt; lis=
t and in the Philadelphia meeting.<br>&gt;<br>&gt; Thanks,<br>&gt;<br>&gt; =
Joe</pre><br></blockquote>
</blockquote></body>
</html>=

--_9ecca39d-654a-4ffb-826c-42178ecd0407_--

--===============0906773856==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu

--===============0906773856==--


From emu-bounces@ietf.org  Sat Feb 23 01:19:55 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 950623A6866;
	Sat, 23 Feb 2008 01:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.552
X-Spam-Level: 
X-Spam-Status: No, score=-0.552 tagged_above=-999 required=5
	tests=[AWL=-0.115, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 067xRyZjX0HT; Sat, 23 Feb 2008 01:19:54 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9283A3A69E9;
	Sat, 23 Feb 2008 01:19:54 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01DBE3A69EB
	for <emu@core3.amsl.com>; Sat, 23 Feb 2008 01:19:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WtGjBbYSX-99 for <emu@core3.amsl.com>;
	Sat, 23 Feb 2008 01:19:52 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id 4FFBC3A6866
	for <emu@ietf.org>; Sat, 23 Feb 2008 01:19:51 -0800 (PST)
Received: (qmail invoked by alias); 23 Feb 2008 09:19:46 -0000
Received: from proxy2-nsn.nsn-inter.net (EHLO [217.115.75.230])
	[217.115.75.230]
	by mail.gmx.net (mp030) with SMTP; 23 Feb 2008 10:19:46 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19rV2wzOexrN3ANSQ9G6aJpVvvGW576BIXwxairU6
	AFLjRXeg4KFIrp
Message-ID: <47BFE534.80706@gmx.net>
Date: Sat, 23 Feb 2008 11:19:48 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>	<5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
	<BLU137-W6942A03929159E244DCC6931D0@phx.gbl>
In-Reply-To: <BLU137-W6942A03929159E244DCC6931D0@phx.gbl>
X-Y-GMX-Trusted: 0
Cc: emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Hannes.Tschofenig@gmx.net
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Hi Bernard,

Bernard Aboba wrote:
> "Zero knowledge" is definitely crypto-intensive.  For example, to get both privacy and strong password protection, at least two DHs are required. 
>
> However, there are circumstances where server-side certificates aren't acceptable.  Even in today, many/(most?) EAP deployments do not involve certificates (e.g. LEAP, FAST). 
The good thing is that the approach would work with even a self-signed 
certificate since there is a big difference between the certificates 
used in the Web environment and for network access. In the former case 
you want to make sure that the browser with any webserver on the 
Internet. This is an any-to-any relationship. For network access you 
have a many-to-one relationship.

>   Even if "zero knowledge" isn't used on an ongoing basis (out of concern for load, for example), it still can be useful for initial provisioning.
Provisioning the initial security is an entirely different problem. EAP 
is the wrong way todo that.
See for example the interesting work done in the KEYPROV working group.

>   For example, EAP FAST provisioning is vulnerable to man-in-the-middle attack or dictionary attack, which could be removed with use of "zero knowledge" algorithms.    
>   
Need to look at this aspect of the draft again.

Ciao
Hannes

> Subject: AW: [Emu] EMU Charter revision
> Date: Fri, 22 Feb 2008 15:34:56 +0100
> From: hannes.tschofenig@nsn.com
> To: bernard_aboba@hotmail.com; emu@ietf.org
>
>
>
>
>
>
>
>
>
>
> Hi Bernard,
>  
> a question your excitment regarding strong password based EAP 
> method. 
>  
> Why do you think they are useful? There are other ways (and they 
> are deployed already) that can accomplish the same result without going 
> along the SRP & co track. 
> Is it because you expect performance improvements or because the 
> crypto-mechanisms look nicer? 
>  
> I cannot quite understand the motivation. 
>  
> Ciao
> Hannes
>
>   
>   
>   Von: emu-bounces@ietf.org 
>   [mailto:emu-bounces@ietf.org] Im Auftrag von ext Bernard 
>   Aboba
> Gesendet: Donnerstag, 21. Februar 2008 21:54
> An: 
>   emu@ietf.org
> Betreff: Re: [Emu] EMU Charter 
>   revision
>
>
>   I also do NOT approve of the current charter revision, for several 
>   reasons:
>
> a.  The Charter text contains statements that are no 
>   longer true.  For example:
> "Most of these methods are proprietary methods and only a few methods 
> are documented in RFCs."
>
> The following EAP methods are now documented in RFCs:
>
> EAP-TLS (RFC 2716)
> EAP-SIM (RFC 4186)
> EAP-AKA (RFC 4187)
> EAP-PAX (RFC 4746)
> EAP-SAKE (RFC 4763)
> EAP-PSK (RFC 4764)
> EAP-POTP (RFC 4793)
> EAP-FAST (RFC 4851)
> EAP-IKEv2 (RFC 5106)
>
> 9 methods claiming to satify RFC 4017 critieria is more than a "few". 
>
> b. The Charter requires support for Channel Bindings without doing the
> preparatory work to define how Channel Bindings works.  Either the
> requirement should be removed, or a work item should be added to 
> better define the approach to Channel Bindings. 
>
> c. The text on tunnel methods does not provide enough guidance to avoid
> potentially fruitless arguments.  So far, the EMU WG has not been able
> to come to consensus on selection of one of the existing tunneling
> protocols, and efforts to design "yet another" tunneling protocol 
> haven't gotten very far either.  I'd like to see more specific 
> language that would make it clear that work on improving existing
> tunneling protocols is within scope, and also that the EMU WG,
> if it cannot come to consensus on a single protocol, can proceed to 
> work on one or more protocols with significant support.  
>
> d. Password-based methods.  While I can understand the desire to limit the
> number of charter items, I do agree with Dan that work on weak-password
> methods is important.  With some of the IPR obstacles likely to fall by
> the wayside in coming years, it is time for the IETF to re-visit its policy
> on inclusion of "zero knowledge" algorithms within standards track documents. 
> Dan 
>   Harkins said:
>
> " Hi Joe,
>
>   I do NOT approve of the current charter revision, specifically the
> change that says the password-based method can only be via the
> tunneled method. I do approve of the inclusion of tunneled methods
> in the charter though and would be willing to contribute as a
> reviewer.
>
>   regards,
>
>   Dan."
> On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:
>   
>> The response to the charter revision has been underwhelming.  I am a bit
>> concerned that we do not have enough participation to complete the
>> tunnel method work (most of the recent discussion has been about other
>> methods).
>>
>> I would like to get an idea of the number working group members that
>> approve of working on the tunnel method items and are able to
>> participate in the development of requirements and specifications as
>> contributors and/or reviewers.
>>
>> Please respond to this message and state whether you approve of the
>> current charter revision and what capacity you would be willing to
>> contribute towards tunneled method development: contributor, reviewer or
>> not able to contribute.
>>
>> I have submitted an internet draft attempt at an outline of requirements
>> for tunneled methods
>> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
>> txt) that I hope can provided a starting point for discussions on the
>> list and in the Philadelphia meeting.
>>
>> Thanks,
>>
>> Joe
>>     
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>   

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Sat Feb 23 02:38:52 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19B413A6A35;
	Sat, 23 Feb 2008 02:38:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.848
X-Spam-Level: 
X-Spam-Status: No, score=-0.848 tagged_above=-999 required=5
	tests=[AWL=-0.411, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MbaLaKYePBDs; Sat, 23 Feb 2008 02:38:50 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DAA9C3A6A2F;
	Sat, 23 Feb 2008 02:38:50 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E66C3A69E7
	for <emu@core3.amsl.com>; Sat, 23 Feb 2008 02:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3NbTgSc52Z0C for <emu@core3.amsl.com>;
	Sat, 23 Feb 2008 02:38:47 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174])
	by core3.amsl.com (Postfix) with ESMTP id A7D863A6849
	for <emu@ietf.org>; Sat, 23 Feb 2008 02:38:37 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1])
	by colo.trepanning.net (Postfix) with ESMTP id 557001FA620D;
	Sat, 23 Feb 2008 02:38:33 -0800 (PST)
Received: from 69.12.173.8
	(SquirrelMail authenticated user dharkins@lounge.org)
	by www.trepanning.net with HTTP;
	Sat, 23 Feb 2008 02:38:33 -0800 (PST)
Message-ID: <4841.69.12.173.8.1203763113.squirrel@www.trepanning.net>
In-Reply-To: <47BFE534.80706@gmx.net>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
	<5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
	<BLU137-W6942A03929159E244DCC6931D0@phx.gbl> <47BFE534.80706@gmx.net>
Date: Sat, 23 Feb 2008 02:38:33 -0800 (PST)
From: "Dan Harkins" <dharkins@lounge.org>
To: Hannes.Tschofenig@gmx.net
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org


  Hi Hannes,

  What you're saying is not that it "would work" but that it "could work".
If it's deployed correctly. And if there's some step that each and every
client MUST go through to accept a certificate. So _if_ _every_ client
goes through this step than it _can_ work. If, for some reason, this
strict regime is not followed then it doesn't work.

  The issue isn't whether it can be made secure provided some series
of steps are religiously followed. It's whether it will be secure even
if those steps are not religiously followed.

  Dan.

On Sat, February 23, 2008 1:19 am, Hannes Tschofenig wrote:
> Hi Bernard,
>
> Bernard Aboba wrote:
>> "Zero knowledge" is definitely crypto-intensive.  For example, to get
>> both privacy and strong password protection, at least two DHs are
>> required.
>>
>> However, there are circumstances where server-side certificates aren't
>> acceptable.  Even in today, many/(most?) EAP deployments do not involve
>> certificates (e.g. LEAP, FAST).
> The good thing is that the approach would work with even a self-signed
> certificate since there is a big difference between the certificates
> used in the Web environment and for network access. In the former case
> you want to make sure that the browser with any webserver on the
> Internet. This is an any-to-any relationship. For network access you
> have a many-to-one relationship.
>
>>   Even if "zero knowledge" isn't used on an ongoing basis (out of
>> concern for load, for example), it still can be useful for initial
>> provisioning.
> Provisioning the initial security is an entirely different problem. EAP
> is the wrong way todo that.
> See for example the interesting work done in the KEYPROV working group.
>
>>   For example, EAP FAST provisioning is vulnerable to man-in-the-middle
>> attack or dictionary attack, which could be removed with use of "zero
>> knowledge" algorithms.
>>
> Need to look at this aspect of the draft again.
>
> Ciao
> Hannes
>
>> Subject: AW: [Emu] EMU Charter revision
>> Date: Fri, 22 Feb 2008 15:34:56 +0100
>> From: hannes.tschofenig@nsn.com
>> To: bernard_aboba@hotmail.com; emu@ietf.org
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi Bernard,
>>
>> a question your excitment regarding strong password based EAP
>> method.
>>
>> Why do you think they are useful? There are other ways (and they
>> are deployed already) that can accomplish the same result without going
>> along the SRP & co track.
>> Is it because you expect performance improvements or because the
>> crypto-mechanisms look nicer?
>>
>> I cannot quite understand the motivation.
>>
>> Ciao
>> Hannes
>>
>>
>>
>>   Von: emu-bounces@ietf.org
>>   [mailto:emu-bounces@ietf.org] Im Auftrag von ext Bernard
>>   Aboba
>> Gesendet: Donnerstag, 21. Februar 2008 21:54
>> An:
>>   emu@ietf.org
>> Betreff: Re: [Emu] EMU Charter
>>   revision
>>
>>
>>   I also do NOT approve of the current charter revision, for several
>>   reasons:
>>
>> a.  The Charter text contains statements that are no
>>   longer true.  For example:
>> "Most of these methods are proprietary methods and only a few methods
>> are documented in RFCs."
>>
>> The following EAP methods are now documented in RFCs:
>>
>> EAP-TLS (RFC 2716)
>> EAP-SIM (RFC 4186)
>> EAP-AKA (RFC 4187)
>> EAP-PAX (RFC 4746)
>> EAP-SAKE (RFC 4763)
>> EAP-PSK (RFC 4764)
>> EAP-POTP (RFC 4793)
>> EAP-FAST (RFC 4851)
>> EAP-IKEv2 (RFC 5106)
>>
>> 9 methods claiming to satify RFC 4017 critieria is more than a "few".
>>
>> b. The Charter requires support for Channel Bindings without doing the
>> preparatory work to define how Channel Bindings works.  Either the
>> requirement should be removed, or a work item should be added to
>> better define the approach to Channel Bindings.
>>
>> c. The text on tunnel methods does not provide enough guidance to avoid
>> potentially fruitless arguments.  So far, the EMU WG has not been able
>> to come to consensus on selection of one of the existing tunneling
>> protocols, and efforts to design "yet another" tunneling protocol
>> haven't gotten very far either.  I'd like to see more specific
>> language that would make it clear that work on improving existing
>> tunneling protocols is within scope, and also that the EMU WG,
>> if it cannot come to consensus on a single protocol, can proceed to
>> work on one or more protocols with significant support.
>>
>> d. Password-based methods.  While I can understand the desire to limit
>> the
>> number of charter items, I do agree with Dan that work on weak-password
>> methods is important.  With some of the IPR obstacles likely to fall by
>> the wayside in coming years, it is time for the IETF to re-visit its
>> policy
>> on inclusion of "zero knowledge" algorithms within standards track
>> documents.
>> Dan
>>   Harkins said:
>>
>> " Hi Joe,
>>
>>   I do NOT approve of the current charter revision, specifically the
>> change that says the password-based method can only be via the
>> tunneled method. I do approve of the inclusion of tunneled methods
>> in the charter though and would be willing to contribute as a
>> reviewer.
>>
>>   regards,
>>
>>   Dan."
>> On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:
>>
>>> The response to the charter revision has been underwhelming.  I am a
>>> bit
>>> concerned that we do not have enough participation to complete the
>>> tunnel method work (most of the recent discussion has been about other
>>> methods).
>>>
>>> I would like to get an idea of the number working group members that
>>> approve of working on the tunnel method items and are able to
>>> participate in the development of requirements and specifications as
>>> contributors and/or reviewers.
>>>
>>> Please respond to this message and state whether you approve of the
>>> current charter revision and what capacity you would be willing to
>>> contribute towards tunneled method development: contributor, reviewer
>>> or
>>> not able to contribute.
>>>
>>> I have submitted an internet draft attempt at an outline of
>>> requirements
>>> for tunneled methods
>>> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
>>> txt) that I hope can provided a starting point for discussions on the
>>> list and in the Philadelphia meeting.
>>>
>>> Thanks,
>>>
>>> Joe
>>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Emu mailing list
>> Emu@ietf.org
>> http://www.ietf.org/mailman/listinfo/emu
>>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>


_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Sat Feb 23 10:57:39 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EE50F28C27E;
	Sat, 23 Feb 2008 10:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.431
X-Spam-Level: 
X-Spam-Status: No, score=-0.431 tagged_above=-999 required=5
	tests=[AWL=-0.994, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F6tYXYcY+YDD; Sat, 23 Feb 2008 10:57:39 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 357593A6AFC;
	Sat, 23 Feb 2008 10:57:39 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A51828C146
	for <emu@core3.amsl.com>; Sat, 23 Feb 2008 10:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id csf9auMofjrk for <emu@core3.amsl.com>;
	Sat, 23 Feb 2008 10:57:36 -0800 (PST)
Received: from blu139-omc3-s27.blu139.hotmail.com
	(blu139-omc3-s27.blu139.hotmail.com [65.55.175.227])
	by core3.amsl.com (Postfix) with ESMTP id 58E3D3A6BD6
	for <emu@ietf.org>; Sat, 23 Feb 2008 10:57:36 -0800 (PST)
Received: from BLU137-W15 ([65.55.162.187]) by
	blu139-omc3-s27.blu139.hotmail.com with Microsoft
	SMTPSVC(6.0.3790.3959); Sat, 23 Feb 2008 10:57:31 -0800
Message-ID: <BLU137-W1569620C4CCB84438495AA931E0@phx.gbl>
X-Originating-IP: [208.54.15.196]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Dan Harkins <dharkins@lounge.org>, <hannes.tschofenig@gmx.net>
Date: Sat, 23 Feb 2008 10:57:31 -0800
Importance: Normal
In-Reply-To: <4841.69.12.173.8.1203763113.squirrel@www.trepanning.net>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
	<5FB585F183235B42A9E70095055136FB0555FD@DEMUEXC012.nsn-intra.net>
	<BLU137-W6942A03929159E244DCC6931D0@phx.gbl> <47BFE534.80706@gmx.net> 
	<4841.69.12.173.8.1203763113.squirrel@www.trepanning.net>
MIME-Version: 1.0
X-OriginalArrivalTime: 23 Feb 2008 18:57:31.0595 (UTC)
	FILETIME=[F17A69B0:01C8764D]
Cc: emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0614677467=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

--===============0614677467==
Content-Type: multipart/alternative;
	boundary="_9cb0afef-8bd7-4846-8871-1cde1442092f_"

--_9cb0afef-8bd7-4846-8871-1cde1442092f_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


In practice it is difficult to securely support self-signed certificates.  =
There are several issues involved:

a. Vulnerability to man-in-the-middle attack on initial provisioning.  For =
wireless networks, this is a significant risk, more so than with protocols =
like SSH, where initial contact might occur over a wired network.=20

b. Potential for affecting other applications.  Self-signed certificates, i=
f trusted for a given use, must not be used as trust anchors for other uses=
.  This can require significant additional work to make sure that trust is =
properly isolated.=20

For these reasons, I do not believe that EAP methods relying on self-signed=
 certificates satisfy the requirements of RFC 4017.=20



--_9cb0afef-8bd7-4846-8871-1cde1442092f_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
In practice it is difficult to securely support self-signed certificates.&n=
bsp; There are several issues involved:<br><br>a. Vulnerability to man-in-t=
he-middle attack on initial provisioning.&nbsp; For wireless networks, this=
 is a significant risk, more so than with protocols like SSH, where initial=
 contact might occur over a wired network. <br><br>b. Potential for affecti=
ng other applications.&nbsp; Self-signed certificates, if trusted for a giv=
en use, must not be used as trust anchors for other uses.&nbsp; This can re=
quire significant additional work to make sure that trust is properly isola=
ted. <br><br>For these reasons, I do not believe that EAP methods relying o=
n self-signed certificates satisfy the requirements of RFC 4017. <br><br><b=
r></body>
</html>=

--_9cb0afef-8bd7-4846-8871-1cde1442092f_--

--===============0614677467==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu

--===============0614677467==--


From emu-bounces@ietf.org  Sat Feb 23 16:00:56 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A6C243A6B84;
	Sat, 23 Feb 2008 16:00:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.173
X-Spam-Level: 
X-Spam-Status: No, score=0.173 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	J_CHICKENPOX_21=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6RSUA7X+7241; Sat, 23 Feb 2008 16:00:55 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E21933A6B6E;
	Sat, 23 Feb 2008 16:00:55 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 66F3F3A6B6E
	for <emu@core3.amsl.com>; Sat, 23 Feb 2008 16:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ig-VxIQ245Xr for <emu@core3.amsl.com>;
	Sat, 23 Feb 2008 16:00:53 -0800 (PST)
Received: from bacon.cs.umd.edu (server-nat-2.cs.umd.edu [128.8.127.145])
	by core3.amsl.com (Postfix) with ESMTP id 8B0E03A6B13
	for <emu@ietf.org>; Sat, 23 Feb 2008 16:00:53 -0800 (PST)
Received: from [192.168.0.155] (pool-71-179-91-146.bltmmd.fios.verizon.net
	[71.179.91.146]) (authenticated bits=0)
	by bacon.cs.umd.edu (8.13.1/8.12.5) with ESMTP id m1O00X1E009895
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 23 Feb 2008 19:00:33 -0500
Message-ID: <47C0B39D.1080303@cs.umd.edu>
Date: Sat, 23 Feb 2008 19:00:29 -0500
From: Charles Clancy <clancy@cs.umd.edu>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: emu@ietf.org
X-CSD-MailScanner-Information: Please email staff@cs.umd.edu for more
	information
X-CSD-MailScanner: Found to be clean
X-CSD-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
	score=-4.399, required 5, autolearn=not spam, ALL_TRUSTED -1.80,
	BAYES_00 -2.60)
X-CSD-MailScanner-From: clancy@cs.umd.edu
Cc: Tim Polk <tim.polk@nist.gov>, khoeper@nist.gov
Subject: [Emu] EAP Channel Bindings Drafts
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

EMU,

Here are some rough -00 docs describing channel bindings for EAP.

http://www.ietf.org/internet-drafts/draft-clancy-emu-aaapay-00.txt
http://www.ietf.org/internet-drafts/draft-clancy-emu-chbind-00.txt

"aaapay" defines bindings to existing EAP methods for them to carry 
Diameter AVPs within their protected channels.  "chbind" then describes 
how to use these AVPs for channel bindings.  Certainly MUCH work still 
needs to be done, but I think they provide a framework within which to 
start the conversation.

-- 
t. charles clancy, ph.d.                 eng.umd.edu/~tcc
electrical & computer engineering, university of maryland
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Sat Feb 23 16:48:39 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 34DC928C1E9;
	Sat, 23 Feb 2008 16:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.365
X-Spam-Level: 
X-Spam-Status: No, score=-2.365 tagged_above=-999 required=5
	tests=[AWL=-1.928, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mY3H-tfh8znL; Sat, 23 Feb 2008 16:48:38 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22B473A69F7;
	Sat, 23 Feb 2008 16:48:38 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 72AE43A67E2
	for <emu@core3.amsl.com>; Sat, 23 Feb 2008 16:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KfsHCfjt67Wk for <emu@core3.amsl.com>;
	Sat, 23 Feb 2008 16:48:35 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id D0C0B28C14D
	for <emu@ietf.org>; Sat, 23 Feb 2008 16:48:34 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.25,396,1199692800"; 
   d="scan'208";a="6918730"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-4.cisco.com with ESMTP; 23 Feb 2008 16:48:30 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m1O0mUZQ003046; 
	Sat, 23 Feb 2008 16:48:30 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1O0mQp6010892;
	Sun, 24 Feb 2008 00:48:30 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Feb 2008 16:48:29 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 23 Feb 2008 16:49:13 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE50551957E@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <5bfe7a820802220824h6393e269nb280164b5411f6b4@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] EMU charter revision
Thread-Index: Ach1b3l0xK2/fVHJTeuMOzSh8U+nXQBDVcWw
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Dorothy Stanley" <dstanley1389@gmail.com>
X-OriginalArrivalTime: 24 Feb 2008 00:48:29.0511 (UTC)
	FILETIME=[F8F96570:01C8767E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7605; t=1203814110;
	x=1204678110; c=relaxed/simple; s=sjdkim4002;
	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@ci
	sco.com> |Subject:=20RE=3A=20[Emu]=20EMU=20charter=20revision
	|Sender:=20; bh=qQIzmFGqH1/Esv3gLbKyRfm/LN14YhlCtq3c361OzJc=;
	b=QVGWSZ3qkEdeF8R4gsJ/ONwvwWkjle+oz5SRkNWl339UAiZfi5PEPiuhCq
	HFuapXyu7zQMZcRWPJWhRQJLEa+jX6O3Mv7me469ich+Z6T0yhgklraA0GMp
	QpBqSrbWPF;
Authentication-Results: sj-dkim-4; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: emu@ietf.org
Subject: Re: [Emu] EMU charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Hi Dorothy,

The current charter item is for a method that works with existing
password databases.  This requires the method to work with databases
where the EAP server does not have access to the cleartext password and
in some cases does not have access even to the transform of the password
(in these cases a comparison function is available).  I don't believe
the method proposed in
http://www.ietf.org/internet-drafts/draft-harkins-emu-eap-pwd-00.txt
meets this requirement.

Can you clarify if you want to remove this requirement or if you want to
add a charter item for a "secure password only method" such as the on
proposed in the draft? 

Thanks,

Joe

> -----Original Message-----
> From: Dorothy Stanley [mailto:dstanley1389@gmail.com] 
> Sent: Friday, February 22, 2008 8:25 AM
> To: Joseph Salowey (jsalowey)
> Cc: emu@ietf.org
> Subject: Re: [Emu] EMU charter revision
> 
> Joe,
> 
> I do not approve of the charter revision; the charter should 
> not prohibit the group from using a non-tunneled method for 
> the password-based method. 
> My previous mail gave a suggested charter text change. 
> 
> I can participate as a reviewer.
> 
> Thanks,
> 
> Dorothy Stanley
> 
> 
> 
> On Tue, Feb 19, 2008 at 11:14 AM, Joseph Salowey (jsalowey) 
> <jsalowey@cisco.com> wrote:
> 
> 
> 	The response to the charter revision has been 
> underwhelming.  I am a bit
> 	concerned that we do not have enough participation to 
> complete the
> 	tunnel method work (most of the recent discussion has 
> been about other
> 	methods).
> 	
> 	I would like to get an idea of the number working group 
> members that
> 	approve of working on the tunnel method items and are able to
> 	participate in the development of requirements and 
> specifications as
> 	contributors and/or reviewers.
> 	
> 	Please respond to this message and state whether you 
> approve of the
> 	current charter revision and what capacity you would be 
> willing to
> 	contribute towards tunneled method development: 
> contributor, reviewer or
> 	not able to contribute.
> 	
> 	I have submitted an internet draft attempt at an 
> outline of requirements
> 	for tunneled methods
> 	
> (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunn
> el-req-00.
> 	txt 
> <http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunn
> el-req-00.txt> ) that I hope can provided a starting point 
> for discussions on the
> 	list and in the Philadelphia meeting.
> 	
> 	Thanks,
> 	
> 	Joe
> 	
> 
> 	> -----Original Message-----
> 	> From: Joseph Salowey (jsalowey)
> 	> Sent: Monday, February 04, 2008 9:13 PM
> 	> To: emu@ietf.org
> 	> Subject: EMU charter revision
> 	>
> 	> Below is a revised charter update based on the discussion on
> 	> the list.  I have left the password based method item as a
> 	> tunnel method because this represents the consensus the
> 	> working group has reached.  I also believe the working group
> 	> will have to focus on the tunnel method related items for the
> 	> near term to make progress.  This does not mean that we
> 	> cannot work on additional methods as working group items in
> 	> the future.
> 	>
> 	> Please review the charter update and post any issues you have
> 	> with the carter.  Please also indicate if you have reviewed
> 	> the proposed charter and have no issues.  It is difficult to
> 	> judge working group consensus unless there are 
> sufficient responses.
> 	>
> 	> Thanks,
> 	>
> 	> Joe
> 	>
> 	> Description of Working Group:
> 	> The Extensible Authentication Protocol (EAP) [RFC 3748] is a
> 	> network access authentication framework used in the PPP,
> 	> 802.11, 802.16, VPN, PANA, and in some functions in 3G
> 	> networks. EAP itself is a simple protocol and actual
> 	> authentication happens in EAP methods.
> 	>
> 	> Over 40 different EAP methods exist. Most of these methods
> 	> are proprietary methods and only a few methods are documented
> 	> in RFCs. The lack of documented, open specifications is a
> 	> deployment and interoperability problem. In addition, none of
> 	> the EAP methods in the standards track implement features
> 	> such as key derivation that are required for many modern
> 	> applications. This poses a problem for, among other things,
> 	> the selection of a mandatory to implement EAP method in new
> 	> network access technologies. For example, no standards track
> 	> methods meet new requirements such as those posed in RFC
> 	> 4017, which documents IEEE 802.11 requirements for 
> EAP methods.
> 	>
> 	> This group is chartered to work on the following types of
> 	> mechanisms to meet RFC 3748 and RFC 4017 requirements:
> 	>
> 	> - An update to RFC 2716 to bring EAP-TLS into standards
> 	> track, clarify specification, interoperability, and
> 	> implementation issues gathered over the years, and update the
> 	> document to meet the requirements of RFC 3748, RFC 4017, and
> 	> EAP keying framework documents. Backwards compatibility with
> 	> RFC 2716 is a requirement.
> 	>
> 	> - A mechanism based on strong shared secrets that meets RFC
> 	> 3748 and RFC 4017 requirements. This mechanism should strive
> 	> to be simple and compact for implementation in resource
> 	> constrained environments.
> 	>
> 	> - A mechanism to support extensible communication within a
> 	> TLS protected tunnel that meets RFC 3748 and RFC 4017
> 	> requirements. This mechanism must support channel bindings in
> 	> order to meet RFC 4962 requirements and it must provide
> 	> cryptographic algorithm agility. This mechanism will support
> 	> meeting the requirements of an enhanced TLS mechanism, a
> 	> password based authentication mechanism, and additional inner
> 	> authentication mechanisms.
> 	>
> 	> - Enable a TLS-based EAP method to support channel bindings.
> 	> So as to enable RFC 2716bis to focus solely on clarifications
> 	> to the existing protocol, this effort will be handled in a
> 	> separate document.  This item will not generate a new method,
> 	> rather it will enhance EAP-TLS or the TLS based tunnel method
> 	> work item.
> 	>
> 	> - A mechanism meeting RFC 3748 and RFC 4017 requirements that
> 	> makes use of existing password databases such as AAA
> 	> databases.  This item will be based on the tunnel 
> method work item.
> 	>
> 	> Goals and Milestones:
> 	> Done          Form design team to work on strong shared
> 	> secret mechanism
> 	> Done          Submit 2716bis I-D
> 	> Done          Submit first draft of shared secret 
> mechanism I-D
> 	> Done          Form password based mechanism design team
> 	> Done          Submit 2716bis draft to IESG for 
> Proposed Standard
> 	> Done          Submit Strong Shared Secret Mechanism to IESG
> 	> Apr 2008      Submit Tunnel and Password Method requirements
> 	> first draft
> 	> Jul 2008      Send Tunnel and Password Method 
> requirements to IESG
> 	> Oct 2008      Submit Tunnel Method first draft
> 	> Nov 2008    Submit TLS based method channel binding 
> first draft
> 	> Nov 2008      Submit Password Method first draft
> 	> Feb 2009      Send Tunnel Method to IESG
> 	> Apr 2009      Send TLS based method channel binding to IESG
> 	> Apr 2009      Send Password based method to IESG
> 	>
> 	>
> 	>
> 	>
> 	_______________________________________________
> 	Emu mailing list
> 	Emu@ietf.org
> 	http://www.ietf.org/mailman/listinfo/emu
> 	
> 
> 
> 
_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Sun Feb 24 12:23:53 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B8DE3A6C9F;
	Sun, 24 Feb 2008 12:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.398
X-Spam-Level: 
X-Spam-Status: No, score=-0.398 tagged_above=-999 required=5 tests=[AWL=0.039,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eKX1Al0ohykB; Sun, 24 Feb 2008 12:23:52 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8B0228C260;
	Sun, 24 Feb 2008 12:23:50 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D45728C260
	for <emu@core3.amsl.com>; Sun, 24 Feb 2008 12:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8-4oIzcvN0zw for <emu@core3.amsl.com>;
	Sun, 24 Feb 2008 12:23:48 -0800 (PST)
Received: from toshi17.tari.toshiba.com (unknown
	[IPv6:2001:418:1403:0:20e:7fff:fe65:c513])
	by core3.amsl.com (Postfix) with ESMTP id 00FA328C126
	for <emu@ietf.org>; Sun, 24 Feb 2008 12:23:34 -0800 (PST)
Received: from steelhead.localdomain (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	m1OKNQ9x024405; Sun, 24 Feb 2008 15:23:26 -0500 (EST)
	(envelope-from yohba@tari.toshiba.com)
Received: from ohba by steelhead.localdomain with local (Exim 4.69)
	(envelope-from <yohba@tari.toshiba.com>)
	id 1JTNNV-0007jT-PX; Sun, 24 Feb 2008 15:23:17 -0500
Date: Sun, 24 Feb 2008 15:23:15 -0500
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Message-ID: <20080224202315.GE27261@steelhead.localdomain>
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
Cc: emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

I have an opinion about Channel Binding.  Based on discussion to
create RFC 4962 and draft-ietf-hokey-key-mgt, I came to believe that
EAP method is not the right tool to solve the Channel Binding problem
even if RFC 3748 has Channel Binding in its list of security claims on
EAP method.  This is because EAP methods are based on two-party
keying, while the Channel Binding problem essentially came from
separation of EAP authenticator and EAP server.  I think Channel
Binding is best solved using a three-party key distribution protocol
e.g., by re-designing EAP to be a 3-party protocol, but that is not
what EMU WG is supposed to do, either.

Said that I suggest removing Channel Binding support from the EMU
charter.

Yoshihiro Ohba


On Thu, Feb 21, 2008 at 11:54:06AM -0800, Bernard Aboba wrote:
> 
> I also do NOT approve of the current charter revision, for several reasons:
> 
> a.  The Charter text contains statements that are no longer true.  For example:
> "Most of these methods are proprietary methods and only a few methods 
> are documented in RFCs."
> 
> The following EAP methods are now documented in RFCs:
> 
> EAP-TLS (RFC 2716)
> EAP-SIM (RFC 4186)
> EAP-AKA (RFC 4187)
> EAP-PAX (RFC 4746)
> EAP-SAKE (RFC 4763)
> EAP-PSK (RFC 4764)
> EAP-POTP (RFC 4793)
> EAP-FAST (RFC 4851)
> EAP-IKEv2 (RFC 5106)
> 
> 9 methods claiming to satify RFC 4017 critieria is more than a "few". 
> 
> b. The Charter requires support for Channel Bindings without doing the
> preparatory work to define how Channel Bindings works.  Either the
> requirement should be removed, or a work item should be added to 
> better define the approach to Channel Bindings. 
> 
> c. The text on tunnel methods does not provide enough guidance to avoid
> potentially fruitless arguments.  So far, the EMU WG has not been able
> to come to consensus on selection of one of the existing tunneling
> protocols, and efforts to design "yet another" tunneling protocol 
> haven't gotten very far either.  I'd like to see more specific 
> language that would make it clear that work on improving existing
> tunneling protocols is within scope, and also that the EMU WG,
> if it cannot come to consensus on a single protocol, can proceed to 
> work on one or more protocols with significant support.  
> 
> d. Password-based methods.  While I can understand the desire to limit the
> number of charter items, I do agree with Dan that work on weak-password
> methods is important.  With some of the IPR obstacles likely to fall by
> the wayside in coming years, it is time for the IETF to re-visit its policy
> on inclusion of "zero knowledge" algorithms within standards track documents. 
> Dan Harkins said:
> 
> " Hi Joe,
> 
>   I do NOT approve of the current charter revision, specifically the
> change that says the password-based method can only be via the
> tunneled method. I do approve of the inclusion of tunneled methods
> in the charter though and would be willing to contribute as a
> reviewer.
> 
>   regards,
> 
>   Dan."
> On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:
> > The response to the charter revision has been underwhelming.  I am a bit
> > concerned that we do not have enough participation to complete the
> > tunnel method work (most of the recent discussion has been about other
> > methods).
> >
> > I would like to get an idea of the number working group members that
> > approve of working on the tunnel method items and are able to
> > participate in the development of requirements and specifications as
> > contributors and/or reviewers.
> >
> > Please respond to this message and state whether you approve of the
> > current charter revision and what capacity you would be willing to
> > contribute towards tunneled method development: contributor, reviewer or
> > not able to contribute.
> >
> > I have submitted an internet draft attempt at an outline of requirements
> > for tunneled methods
> > (http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
> > txt) that I hope can provided a starting point for discussions on the
> > list and in the Philadelphia meeting.
> >
> > Thanks,
> >
> > Joe

> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu

_______________________________________________
Emu mailing list
Emu@ietf.org
http://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Wed Feb 27 15:05:11 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FB9B28C8BE;
	Wed, 27 Feb 2008 15:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.275
X-Spam-Level: 
X-Spam-Status: No, score=-2.275 tagged_above=-999 required=5
	tests=[AWL=-1.838, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F9NMylDy1kKy; Wed, 27 Feb 2008 15:05:10 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BE8D28C8F9;
	Wed, 27 Feb 2008 15:04:38 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5ACD328C347
	for <emu@core3.amsl.com>; Wed, 27 Feb 2008 15:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vMFfw8-LCgqc for <emu@core3.amsl.com>;
	Wed, 27 Feb 2008 15:04:30 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 9DF4628C84A
	for <emu@ietf.org>; Wed, 27 Feb 2008 15:03:54 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 27 Feb 2008 15:03:48 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1RN3mMe015567
	for <emu@ietf.org>; Wed, 27 Feb 2008 15:03:48 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1RN3dSM026290
	for <emu@ietf.org>; Wed, 27 Feb 2008 23:03:47 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Feb 2008 15:03:43 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 27 Feb 2008 15:04:29 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE50558F159@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Agenda Take 2
Thread-Index: Ach5lRsCJfN/keiXQp+WKY7Tddb07A==
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: <emu@ietf.org>
X-OriginalArrivalTime: 27 Feb 2008 23:03:43.0840 (UTC)
	FILETIME=[00131E00:01C87995]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=737; t=1204153428; x=1205017428;
	c=relaxed/simple; s=sjdkim2002;
	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@ci
	sco.com> |Subject:=20Agenda=20Take=202 |Sender:=20;
	bh=rHGsduFRXRBz2lV0IZCk3a/W+Qy3GrNu9WoI7wuIbvg=;
	b=wSNrdlbaqjaKZCMZwDslIS0fG2FbNb4EBPCLfn3GwAa4GvdyG5h8HOV2Dd
	emK4AsI0pyaC2jwGH4ulfYTHlR0C/xkX4rWW3MZpOITe4i4YlSVAyn4f8AgH
	oNI9G3OUCW;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [Emu] Agenda Take 2
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

EMU Agenda
IETF 71
THURSDAY, March 13, 2008
0900-1130 Morning Session I
---------------------------------------------
+ Administrivia (5 min)
 - agenda, blue sheets, note takers

+ Document Status (5 min)
 - EAP-TLS  - draft-simon-emu-rfc2716bis-13.txt
 - EAP-GPSK - draft-ietf-emu-eap-gpsk-08.txt

+ Charter Revision Status (70 min)
 - General text (10 min)
 - Tunnel Method (20 min) 
 - Secure Password Only Method (20 min)
 - Channel Bindings (20 min)
 
+ Tunnel Method Requirements (30 min)
 - draft-salowey-emu-eaptunnel-req-00.txt

+ Channel Bindings (20 min)
 - draft-clancy-emu-chbind-00.txt
 - draft-clancy-emu-aaapay-00.txt

+ Password only Mechanism (20 min)
 - draft-harkins-emu-eap-pwd-00.txt
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Wed Feb 27 22:36:13 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 20B853A698B;
	Wed, 27 Feb 2008 22:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.919
X-Spam-Level: 
X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5
	tests=[AWL=-0.482, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H0sztJ39NO1W; Wed, 27 Feb 2008 22:36:12 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 703FC3A685F;
	Wed, 27 Feb 2008 22:36:12 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ACEE03A685F
	for <emu@core3.amsl.com>; Wed, 27 Feb 2008 22:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id a5n-wHEK6heQ for <emu@core3.amsl.com>;
	Wed, 27 Feb 2008 22:36:05 -0800 (PST)
Received: from mail.arubanetworks.com (mail.arubanetworks.com [216.31.249.253])
	by core3.amsl.com (Postfix) with SMTP id 7940228C0E3
	for <emu@ietf.org>; Wed, 27 Feb 2008 22:36:05 -0800 (PST)
Received: from aruba-mx1.arubanetworks.com ([10.1.1.17]) by
	mail.arubanetworks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 27 Feb 2008 22:35:58 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 27 Feb 2008 22:35:55 -0800
Message-ID: <A3DA4C2546E1614D8ACC896746CDCF29CECE24@aruba-mx1.arubanetworks.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50558F159@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Agenda Take 2
Thread-Index: Ach5lRsCJfN/keiXQp+WKY7Tddb07AAPv+EA
References: <AC1CFD94F59A264488DC2BEC3E890DE50558F159@xmb-sjc-225.amer.cisco.com>
From: "Glen Zorn" <gzorn@arubanetworks.com>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
X-OriginalArrivalTime: 28 Feb 2008 06:35:58.0898 (UTC)
	FILETIME=[2DD46120:01C879D4]
Cc: emu@ietf.org
Subject: Re: [Emu] Agenda Take 2
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Looks OK to me.
...
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu


From emu-bounces@ietf.org  Thu Feb 28 14:31:04 2008
Return-Path: <emu-bounces@ietf.org>
X-Original-To: ietfarch-emu-archive@core3.amsl.com
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 936D73A6EA0;
	Thu, 28 Feb 2008 14:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.218
X-Spam-Level: 
X-Spam-Status: No, score=-0.218 tagged_above=-999 required=5
	tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, MIME_8BIT_HEADER=0.3,
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JdfKoqmYYkIU; Thu, 28 Feb 2008 14:31:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 390F43A6A8F;
	Thu, 28 Feb 2008 14:31:03 -0800 (PST)
X-Original-To: emu@core3.amsl.com
Delivered-To: emu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E26ED28C1F3
	for <emu@core3.amsl.com>; Wed, 27 Feb 2008 11:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eJPdmzYVGIqX for <emu@core3.amsl.com>;
	Wed, 27 Feb 2008 11:34:28 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172])
	by core3.amsl.com (Postfix) with ESMTP id B63DE28C54C
	for <emu@ietf.org>; Wed, 27 Feb 2008 11:32:53 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 25so2424651wfa.31
	for <emu@ietf.org>; Wed, 27 Feb 2008 11:32:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=wiV4CSWaPrJipk7en5YR8Wjj+h4p3l0epWDERf9sjPs=;
	b=d0hD5nneYSnirkOA+BEfBJFj6ydD/YhoxjHDXHTo0pcyrQejCHeATVZ/DyYwAVWAXrAFliKW/0JawR8W3+zQNPJpcqXMqxrJohNkhWX6E0zYt2LU2vehLEctGE0YRtc7XaPj+gIMJCp/59UHa+HLX5H8ghH0Jgc6pVobnJa/WoY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=gFMP+8ShWHr3jDS/8Z5m358rEIH6aj0/9NMfRL6nOTbxssGlvOyPutCCfpyM2giyqrP57SyXQ2ijWcL/qCEmaJKDw4Hv0YJzLxs4gTKXEmj4kIri9cClEw5kGi40UJNOrDhDXFBbmXewr6SG7kjzZKmYl5DBPFmklt2lO839Wgc=
Received: by 10.142.133.15 with SMTP id g15mr5679016wfd.110.1204140766971;
	Wed, 27 Feb 2008 11:32:46 -0800 (PST)
Received: by 10.142.232.11 with HTTP; Wed, 27 Feb 2008 11:32:46 -0800 (PST)
Message-ID: <98f5f260802271132u6b24786jf8a9bd3c99e07608@mail.gmail.com>
Date: Wed, 27 Feb 2008 14:32:46 -0500
From: "=?ISO-8859-1?Q?Katrin_H=F6per?=" <hoepi42@gmail.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
In-Reply-To: <20080224202315.GE27261@steelhead.localdomain>
MIME-Version: 1.0
References: <BLU137-W345413DF2873E51FEB91BF931C0@phx.gbl>
	<20080224202315.GE27261@steelhead.localdomain>
X-Mailman-Approved-At: Thu, 28 Feb 2008 14:31:00 -0800
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, emu@ietf.org
Subject: Re: [Emu] EMU Charter revision
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>,
	<mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1717099538=="
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

--===============1717099538==
Content-Type: multipart/alternative; 
	boundary="----=_Part_5022_26453412.1204140766979"

------=_Part_5022_26453412.1204140766979
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yoshi,

I disagree. I think channel binding can and should be be provided by EAP
methods.

An approach that can be used to add channel binding to any EAP method that
supports mutual authentication and key establishment is outlined in:

http://tools.ietf.org/id/draft-clancy-emu-aaapay-00.txt
and
http://tools.ietf.org/id/draft-clancy-emu-chbind-00.txt

Yes, some additional system requirements that must be ensured outside of EAP
seem to be necessary. But I believe that would be always the case, no matter
would protocol you would use to provide channel binding.

The drafts will be presented at the meeting in Philadelphia.

Katrin

On Sun, Feb 24, 2008 at 3:23 PM, Yoshihiro Ohba <yohba@tari.toshiba.com>
wrote:

> I have an opinion about Channel Binding.  Based on discussion to
> create RFC 4962 and draft-ietf-hokey-key-mgt, I came to believe that
> EAP method is not the right tool to solve the Channel Binding problem
> even if RFC 3748 has Channel Binding in its list of security claims on
> EAP method.  This is because EAP methods are based on two-party
> keying, while the Channel Binding problem essentially came from
> separation of EAP authenticator and EAP server.  I think Channel
> Binding is best solved using a three-party key distribution protocol
> e.g., by re-designing EAP to be a 3-party protocol, but that is not
> what EMU WG is supposed to do, either.
>
> Said that I suggest removing Channel Binding support from the EMU
> charter.
>
> Yoshihiro Ohba
>
>
> On Thu, Feb 21, 2008 at 11:54:06AM -0800, Bernard Aboba wrote:
> >
> > I also do NOT approve of the current charter revision, for several
> reasons:
> >
> > a.  The Charter text contains statements that are no longer true.  For
> example:
> > "Most of these methods are proprietary methods and only a few methods
> > are documented in RFCs."
> >
> > The following EAP methods are now documented in RFCs:
> >
> > EAP-TLS (RFC 2716)
> > EAP-SIM (RFC 4186)
> > EAP-AKA (RFC 4187)
> > EAP-PAX (RFC 4746)
> > EAP-SAKE (RFC 4763)
> > EAP-PSK (RFC 4764)
> > EAP-POTP (RFC 4793)
> > EAP-FAST (RFC 4851)
> > EAP-IKEv2 (RFC 5106)
> >
> > 9 methods claiming to satify RFC 4017 critieria is more than a "few".
> >
> > b. The Charter requires support for Channel Bindings without doing the
> > preparatory work to define how Channel Bindings works.  Either the
> > requirement should be removed, or a work item should be added to
> > better define the approach to Channel Bindings.
> >
> > c. The text on tunnel methods does not provide enough guidance to avoid
> > potentially fruitless arguments.  So far, the EMU WG has not been able
> > to come to consensus on selection of one of the existing tunneling
> > protocols, and efforts to design "yet another" tunneling protocol
> > haven't gotten very far either.  I'd like to see more specific
> > language that would make it clear that work on improving existing
> > tunneling protocols is within scope, and also that the EMU WG,
> > if it cannot come to consensus on a single protocol, can proceed to
> > work on one or more protocols with significant support.
> >
> > d. Password-based methods.  While I can understand the desire to limit
> the
> > number of charter items, I do agree with Dan that work on weak-password
> > methods is important.  With some of the IPR obstacles likely to fall by
> > the wayside in coming years, it is time for the IETF to re-visit its
> policy
> > on inclusion of "zero knowledge" algorithms within standards track
> documents.
> > Dan Harkins said:
> >
> > " Hi Joe,
> >
> >   I do NOT approve of the current charter revision, specifically the
> > change that says the password-based method can only be via the
> > tunneled method. I do approve of the inclusion of tunneled methods
> > in the charter though and would be willing to contribute as a
> > reviewer.
> >
> >   regards,
> >
> >   Dan."
> > On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:
> > > The response to the charter revision has been underwhelming.  I am a
> bit
> > > concerned that we do not have enough participation to complete the
> > > tunnel method work (most of the recent discussion has been about other
> > > methods).
> > >
> > > I would like to get an idea of the number working group members that
> > > approve of working on the tunnel method items and are able to
> > > participate in the development of requirements and specifications as
> > > contributors and/or reviewers.
> > >
> > > Please respond to this message and state whether you approve of the
> > > current charter revision and what capacity you would be willing to
> > > contribute towards tunneled method development: contributor, reviewer
> or
> > > not able to contribute.
> > >
> > > I have submitted an internet draft attempt at an outline of
> requirements
> > > for tunneled methods
> > > (
> http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00.
> > > txt) that I hope can provided a starting point for discussions on the
> > > list and in the Philadelphia meeting.
> > >
> > > Thanks,
> > >
> > > Joe
>
>  > _______________________________________________
> > Emu mailing list
> > Emu@ietf.org
> > http://www.ietf.org/mailman/listinfo/emu
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> http://www.ietf.org/mailman/listinfo/emu
>
>

------=_Part_5022_26453412.1204140766979
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Yoshi,</div>
<div>&nbsp;</div>
<div>I disagree. I think channel binding can and should be be provided by EAP methods.</div>
<div>&nbsp;</div>
<div>An approach that can be used to add channel binding to any EAP method that supports mutual authentication and key establishment is outlined in:</div>
<div>&nbsp;</div>
<div><a href="http://tools.ietf.org/id/draft-clancy-emu-aaapay-00.txt">http://tools.ietf.org/id/draft-clancy-emu-aaapay-00.txt</a></div>
<div>and</div>
<div><a href="http://tools.ietf.org/id/draft-clancy-emu-chbind-00.txt">http://tools.ietf.org/id/draft-clancy-emu-chbind-00.txt</a></div>
<div>&nbsp;</div>
<div>Yes, some additional system requirements that must be ensured outside of EAP seem to be necessary. But I believe that would be&nbsp;always the case,&nbsp;no matter would protocol you would use to provide channel binding.</div>

<div>&nbsp;</div>
<div>The drafts will be presented at the meeting in Philadelphia.</div>
<div>&nbsp;</div>
<div>Katrin<br><br></div>
<div class="gmail_quote">On Sun, Feb 24, 2008 at 3:23 PM, Yoshihiro Ohba &lt;<a href="mailto:yohba@tari.toshiba.com">yohba@tari.toshiba.com</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I have an opinion about Channel Binding. &nbsp;Based on discussion to<br>create RFC 4962 and draft-ietf-hokey-key-mgt, I came to believe that<br>
EAP method is not the right tool to solve the Channel Binding problem<br>even if RFC 3748 has Channel Binding in its list of security claims on<br>EAP method. &nbsp;This is because EAP methods are based on two-party<br>keying, while the Channel Binding problem essentially came from<br>
separation of EAP authenticator and EAP server. &nbsp;I think Channel<br>Binding is best solved using a three-party key distribution protocol<br>e.g., by re-designing EAP to be a 3-party protocol, but that is not<br>what EMU WG is supposed to do, either.<br>
<br>Said that I suggest removing Channel Binding support from the EMU<br>charter.<br><font color="#888888"><br>Yoshihiro Ohba<br></font>
<div>
<div></div>
<div class="Wj3C7c"><br><br>On Thu, Feb 21, 2008 at 11:54:06AM -0800, Bernard Aboba wrote:<br>&gt;<br>&gt; I also do NOT approve of the current charter revision, for several reasons:<br>&gt;<br>&gt; a. &nbsp;The Charter text contains statements that are no longer true. &nbsp;For example:<br>
&gt; &quot;Most of these methods are proprietary methods and only a few methods<br>&gt; are documented in RFCs.&quot;<br>&gt;<br>&gt; The following EAP methods are now documented in RFCs:<br>&gt;<br>&gt; EAP-TLS (RFC 2716)<br>
&gt; EAP-SIM (RFC 4186)<br>&gt; EAP-AKA (RFC 4187)<br>&gt; EAP-PAX (RFC 4746)<br>&gt; EAP-SAKE (RFC 4763)<br>&gt; EAP-PSK (RFC 4764)<br>&gt; EAP-POTP (RFC 4793)<br>&gt; EAP-FAST (RFC 4851)<br>&gt; EAP-IKEv2 (RFC 5106)<br>
&gt;<br>&gt; 9 methods claiming to satify RFC 4017 critieria is more than a &quot;few&quot;.<br>&gt;<br>&gt; b. The Charter requires support for Channel Bindings without doing the<br>&gt; preparatory work to define how Channel Bindings works. &nbsp;Either the<br>
&gt; requirement should be removed, or a work item should be added to<br>&gt; better define the approach to Channel Bindings.<br>&gt;<br>&gt; c. The text on tunnel methods does not provide enough guidance to avoid<br>&gt; potentially fruitless arguments. &nbsp;So far, the EMU WG has not been able<br>
&gt; to come to consensus on selection of one of the existing tunneling<br>&gt; protocols, and efforts to design &quot;yet another&quot; tunneling protocol<br>&gt; haven&#39;t gotten very far either. &nbsp;I&#39;d like to see more specific<br>
&gt; language that would make it clear that work on improving existing<br>&gt; tunneling protocols is within scope, and also that the EMU WG,<br>&gt; if it cannot come to consensus on a single protocol, can proceed to<br>
&gt; work on one or more protocols with significant support.<br>&gt;<br>&gt; d. Password-based methods. &nbsp;While I can understand the desire to limit the<br>&gt; number of charter items, I do agree with Dan that work on weak-password<br>
&gt; methods is important. &nbsp;With some of the IPR obstacles likely to fall by<br>&gt; the wayside in coming years, it is time for the IETF to re-visit its policy<br>&gt; on inclusion of &quot;zero knowledge&quot; algorithms within standards track documents.<br>
&gt; Dan Harkins said:<br>&gt;<br>&gt; &quot; Hi Joe,<br>&gt;<br>&gt; &nbsp; I do NOT approve of the current charter revision, specifically the<br>&gt; change that says the password-based method can only be via the<br>&gt; tunneled method. I do approve of the inclusion of tunneled methods<br>
&gt; in the charter though and would be willing to contribute as a<br>&gt; reviewer.<br>&gt;<br>&gt; &nbsp; regards,<br>&gt;<br>&gt; &nbsp; Dan.&quot;<br>&gt; On Tue, February 19, 2008 11:14 am, Joseph Salowey (jsalowey) wrote:<br>
&gt; &gt; The response to the charter revision has been underwhelming. &nbsp;I am a bit<br>&gt; &gt; concerned that we do not have enough participation to complete the<br>&gt; &gt; tunnel method work (most of the recent discussion has been about other<br>
&gt; &gt; methods).<br>&gt; &gt;<br>&gt; &gt; I would like to get an idea of the number working group members that<br>&gt; &gt; approve of working on the tunnel method items and are able to<br>&gt; &gt; participate in the development of requirements and specifications as<br>
&gt; &gt; contributors and/or reviewers.<br>&gt; &gt;<br>&gt; &gt; Please respond to this message and state whether you approve of the<br>&gt; &gt; current charter revision and what capacity you would be willing to<br>&gt; &gt; contribute towards tunneled method development: contributor, reviewer or<br>
&gt; &gt; not able to contribute.<br>&gt; &gt;<br>&gt; &gt; I have submitted an internet draft attempt at an outline of requirements<br>&gt; &gt; for tunneled methods<br>&gt; &gt; (<a href="http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00" target="_blank">http://www.ietf.org/internet-drafts/draft-salowey-emu-eaptunnel-req-00</a>.<br>
&gt; &gt; txt) that I hope can provided a starting point for discussions on the<br>&gt; &gt; list and in the Philadelphia meeting.<br>&gt; &gt;<br>&gt; &gt; Thanks,<br>&gt; &gt;<br>&gt; &gt; Joe<br><br></div></div>
<div>
<div></div>
<div class="Wj3C7c">&gt; _______________________________________________<br>&gt; Emu mailing list<br>&gt; <a href="mailto:Emu@ietf.org">Emu@ietf.org</a><br>&gt; <a href="http://www.ietf.org/mailman/listinfo/emu" target="_blank">http://www.ietf.org/mailman/listinfo/emu</a><br>
<br>_______________________________________________<br>Emu mailing list<br><a href="mailto:Emu@ietf.org">Emu@ietf.org</a><br><a href="http://www.ietf.org/mailman/listinfo/emu" target="_blank">http://www.ietf.org/mailman/listinfo/emu</a><br>
<br></div></div></blockquote></div><br>

------=_Part_5022_26453412.1204140766979--

--===============1717099538==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1717099538==--


