
From jsalowey@cisco.com  Tue Sep  8 14:09:08 2009
Return-Path: <jsalowey@cisco.com>
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 50A7F3A67B6 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 14:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.587
X-Spam-Level: 
X-Spam-Status: No, score=-6.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5EEt-4yrspuC for <emu@core3.amsl.com>; Tue,  8 Sep 2009 14:09:07 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 0274A3A6805 for <emu@ietf.org>; Tue,  8 Sep 2009 14:09:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAMxkpkqrR7PD/2dsb2JhbACQErVsiEMBMgMEj0wFgi4aBAiBRIFZ
X-IronPort-AV: E=Sophos;i="4.44,354,1249257600"; d="scan'208";a="42554263"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-4.cisco.com with ESMTP; 08 Sep 2009 21:09:38 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n88L9bCI013334;  Tue, 8 Sep 2009 14:09:37 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n88L9bsc015938; Tue, 8 Sep 2009 21:09:37 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.3959);  Tue, 8 Sep 2009 14:09:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Sep 2009 14:09:36 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508AF918A@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <BLU137-W36DE8884CA39C5ACAB551793FF0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] #18 Internationalization
Thread-Index: AcogDZ9SjavKawlHTZm2bxy43Fjr8gQuUxXQ
References: <BLU137-W4C1E9263CC3A9EDABFB8A93060@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5088B0F51@xmb-sjc-225.amer.cisco.com> <BLU137-W1351F278F8E9D7DB662C7193050@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5089320CE@xmb-sjc-225.amer.cisco.com> <BLU137-W36DE8884CA39C5ACAB551793FF0@phx.gbl>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <emu@ietf.org>
X-OriginalArrivalTime: 08 Sep 2009 21:09:37.0553 (UTC) FILETIME=[AC48E010:01CA30C8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7673; t=1252444177; x=1253308177; c=relaxed/simple; s=sjdkim3002; 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]=20#18=20Internationalization |Sender:=20; bh=ot87friUaQB54BYybJMHnEjLhtRTpmFyod/31nHwe9M=; b=GoTW0Rr7ZvjXvqINL8qXMu6IjU3mBrsZuUYdMtzOPGLSwHKmJm6yUtqbI4 TaBXYufpq5DMQYuo0z12dWl0JSi7ekJeCo1Pcf8SFDBYUDQ9vM4bFTmOYtoC Pa9esmfDa/;
Authentication-Results: sj-dkim-3; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [Emu] #18 Internationalization
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/mail-archive/web/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>
X-List-Received-Date: Tue, 08 Sep 2009 21:09:08 -0000

=20

> -----Original Message-----
> From: Bernard Aboba [mailto:bernard_aboba@hotmail.com]=20
> Sent: Tuesday, August 18, 2009 7:10 AM
> To: Joseph Salowey (jsalowey); emu@ietf.org
> Subject: RE: [Emu] #18 Internationalization
>=20
> The problem is that the internationalization language is too=20
> general. =20
> For example, Section 4.3.6 states:
>=20
>=20
> "  Any strings sent by the server intended for display to the=20
> user MUST=20
>    be sent in UTF-8 format and SHOULD be able to be marked=20
> with language=20
>    information and adapted to the user's language preference.
> "
>=20
> This language applies to any string sent by the server,=20
> regardless of whether it was sent as part of TLS, or an=20
> existing EAP method.  Changing this to "Strings sent as part=20
> of the tunnel method (e.g. not part of the tunneling protocol=20
> or inner method)"
> would make more sense.=20
>=20
[Joe] OK, I created issue 25 to track this. =20

> Also, we probably should make a distinction between numeric=20
> and non-numeric strings.  Requiring numbers to be=20
> internationalized (e.g. use of Arabic instead of ASCII=20
> digits) is not probably not what was intended here.=20
>=20
[Joe] Can you clarify this?  If the intention is for display to a user
shouldn't the numbers be displayed in a format that makes sense in that
context? =20

> Also, there are issues in Section 4.5.2:
>=20
> "
>    The password authentication exchange MUST support user names and
>    passwords in international languages.  It MUST support encoding of
>    user name and password strings in UTF-8 [RFC3629] format.  Any
>    strings sent by the server during the password exchange=20
> and intended
>    for display to the user MUST be sent in UTF-8 format and SHOULD be
>    able to be marked with language information and adapted to=20
> the user's
>    language preference.
> "
>=20
> Again, this section refers to "any strings sent by the=20
> server", regardless of whether those strings are sent within=20
> TLS or existing EAP methods.  The scope of this requirement=20
> should be narrowed.=20
>=20
[Joe] This seems pretty clear that it is strings sent by the server
during the password exchange and not within the tunnel or some other
context.   =20


> > Subject: RE: [Emu] #18 Internationalization
> > Date: Mon, 17 Aug 2009 15:06:22 -0700
> > From: jsalowey@cisco.com
> > To: bernard_aboba@hotmail.com; emu@ietf.org
> >=20
> > The scope of the work is a method for transporting passwords. The=20
> > requirements include appropriate internationalization support.
> >=20
> > Section 4.6 covers requirements that existing EAP method not be=20
> > modified by the tunnel. The sections that talk about=20
> internationalization are:
> >=20
> > 4.3.6 which discusses an optional requirement to have an attribute=20
> > format for display strings that supports internationalization.
> >=20
> > 4.5.2 which discusses the internationalization requirements for a=20
> > password exchange.
> >=20
> > If existing mechanisms do not meet the requirements for=20
> > internationalization then either they will need to be=20
> modified or new=20
> > ones will need to be developed.
> >=20
> > I'm not sure where the confusion exists, other than the=20
> requirements=20
> > for internationalization themselves.
> >=20
> > Joe
> >=20
> > > -----Original Message-----
> > > From: Bernard Aboba [mailto:bernard_aboba@hotmail.com]
> > > Sent: Thursday, August 13, 2009 4:39 PM
> > > To: Joseph Salowey (jsalowey); emu@ietf.org
> > > Subject: RE: [Emu] #18 Internationalization
> > >=20
> > > Within Tunnel methods, exchanges of user names and passwords are=20
> > > often accomplished either using TLS or existing EAP methods (e.g.=20
> > > Identity or inner authentication methods). There are some tunnel=20
> > > methods that have their own native authentication methods (e.g.=20
> > > EAP-TTLSv0), but even those typically reuse functionality defined=20
> > > previously (e.g. Diameter AVPs for PAP, CHAP, etc.).
> > >=20
> > > Given that, I'd suggest that the scope of the=20
> requirements needs to=20
> > > be clarified. For example, support for negotiation of=20
> language tags=20
> > > might make sense for tunnel methods that carry such text in an=20
> > > EAP-method specific way. However, a method that relies=20
> solely on TLS=20
> > > or existing EAP methods would not benefit from this=20
> functionality,=20
> > > and the requirements document should not imply that it is within=20
> > > scope for proposals to change TLS, RFC 3748 or existing=20
> EAP methods=20
> > > so as to better support internationalization.
> > >=20
> > > > Subject: RE: [Emu] #18 Internationalization
> > > > Date: Thu, 13 Aug 2009 12:31:59 -0700
> > > > From: jsalowey@cisco.com
> > > > To: bernard_aboba@hotmail.com; emu@ietf.org
> > > >=20
> > > > The core chartered requirements also include the use of=20
> the tunnel=20
> > > > method for password authentication, so it is important=20
> to consider=20
> > > > this case.
> > > >=20
> > > > In addition, there is a proposal for defining conventions
> > > for defining
> > > > generic textual attributes within the tunnel. I think the main=20
> > > > advantage of doing this would be to have a consistent=20
> approach to=20
> > > > internationalization. If this is too difficult, perhaps it
> > > should be
> > > > dropped, although I'm not sure these requirements would be too=20
> > > > different form what is needed for password authentication.
> > > >=20
> > > > Joe
> > > >=20
> > > > > -----Original Message-----
> > > > > From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org]
> > > On Behalf
> > > > > Of Bernard Aboba
> > > > > Sent: Monday, August 10, 2009 12:09 AM
> > > > > To: emu@ietf.org
> > > > > Subject: Re: [Emu] #18 Internationalization
> > > > >=20
> > > > > Joe Salowey said:
> > > > >=20
> > > > > "
> > > > > #18: Internationalization
> > > > >=20
> > > > > Is the use of UTF-8 sufficient or is other tagging necessary.=20
> > > > > The following cases need to be considered:
> > > > >=20
> > > > > 1. Usernames and passwords
> > > > > 2. Prompts and error associated with username and password=20
> > > > > authentication 3. Other textual data "
> > > > >=20
> > > > > It's important to keep in mind that this is a tunnel method=20
> > > > > requirements document. The tunnel method will use TLS, so
> > > as far as
> > > > > bringing up the tunnel is concerned, it is TLS
> > > internationalization
> > > > > that is relevant here. With respect to inner
> > > authentication methods,
> > > > > it is the internationalization support of the inner=20
> method that=20
> > > > > matters.
> > > > >=20
> > > > > Given this, what exactly is within the purview of the
> > > tunnel method
> > > > > with respect to internationalization? Clearly, the=20
> EMU WG is not=20
> > > > > chartered to change EAP itself, TLS or existing EAP methods.
> > > > >=20
> > > > > Given that, what *exactly* does this requirement refer to?=20
> > > > > While it's certainly possible for a tunnel method to=20
> do language=20
> > > > > negotiation, given that such a negotiation wouldn't
> > > affect most of
> > > > > what goes on in the method (e.g. TLS or the inner
> > > method), I don't
> > > > > see what good it would do.
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > >=20
> <http://im.live.com/Messenger/IM/Home/?source=3DEML_WLHM_GreaterGood>
> > > > >=20
> > > > >=20
> > >=20
> > >=20
>=20
>=20

From jsalowey@cisco.com  Tue Sep  8 17:17:17 2009
Return-Path: <jsalowey@cisco.com>
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 254BA3A69CB for <emu@core3.amsl.com>; Tue,  8 Sep 2009 17:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.588
X-Spam-Level: 
X-Spam-Status: No, score=-6.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 IB0iwqcrL2J5 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 17:17:16 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 3FC693A69B5 for <emu@ietf.org>; Tue,  8 Sep 2009 17:17:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAGOQpkqrR7O6/2dsb2JhbADFNYhDAZAWBYIuBYFl
X-IronPort-AV: E=Sophos;i="4.44,355,1249257600"; d="scan'208";a="239009102"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 09 Sep 2009 00:17:47 +0000
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 n890Hlu3027888;  Tue, 8 Sep 2009 17:17:47 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n890HlRD027892; Wed, 9 Sep 2009 00:17: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.3959);  Tue, 8 Sep 2009 17:17:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Sep 2009 17:17:45 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508AF92C8@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50883D06A@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Issue #14 Emergency auth
Thread-Index: AcoWygz7SUqy1ZFxRmuwSIaYjBW3YQAFrKsAAAM+WNAGfUfC0A==
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CECF@xmb-sjc-225.amer.cisco.com><7F9A6D26EB51614FBF9F81C0DA4CFEC80133E56C7788@il-ex01.ad.checkpoint.com> <AC1CFD94F59A264488DC2BEC3E890DE50883D06A@xmb-sjc-225.amer.cisco.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, "Yaron Sheffer" <yaronf@checkpoint.com>, <emu@ietf.org>
X-OriginalArrivalTime: 09 Sep 2009 00:17:47.0357 (UTC) FILETIME=[F58840D0:01CA30E2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3250; t=1252455467; x=1253319467; 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]=20Issue=20#14=20Emergency=20auth |Sender:=20; bh=/Vx2V2oEEF2UtnCQTGiYQq/twU1dZBVC81hNRYUMzeo=; b=NA8qEpQkCHC2b2wfg78y2Ln5NF2Kpq/dtzkC7Via8LM4XCFJZBYdrqBwM7 TmmQtWmnEnu0+CV60p9lJn0Qny+utAtHpaWP0sY2HYCwE5xV03q0Y5OV2VMS uHyj/BspHf;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [Emu] Issue #14 Emergency auth
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 00:17:17 -0000

Hi Yaron,

Does this issue still require the document to be modified?  If so what
text would you like to see.

Thanks,

Joe

> -----Original Message-----
> From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of Joseph Salowey (jsalowey)
> Sent: Thursday, August 06, 2009 4:36 PM
> To: Yaron Sheffer; emu@ietf.org
> Subject: Re: [Emu] Issue #14 Emergency auth
>=20
> Often, there is a richer interface between EAP and the authenticator.
> For example in an Access-Accept message from RADIUS a number=20
> of things can be communicated about the authentication=20
> including the identity of the authenticated peer.  I also=20
> don't think that EAP-Success necessarily implies mutual=20
> authentication, it just says that the EAP server is satisfied=20
> with the result of the process.=20
>=20
> Joe
>=20
> > -----Original Message-----
> > From: Yaron Sheffer [mailto:yaronf@checkpoint.com]
> > Sent: Thursday, August 06, 2009 3:05 PM
> > To: Joseph Salowey (jsalowey); emu@ietf.org
> > Subject: RE: Issue #14 Emergency auth
> >=20
> > The contract between the authenticator and the EAP layer is, when I=20
> > see an EAP Success message, it means that both sides are=20
> > authenticated. We are now breaking this contract, so it=20
> makes sense to=20
> > have EAP inform the upper layer of this fact.
> >=20
> > But I suppose EAP is not extensible enough to add such semantics.=20
> > Sigh.
> >=20
> > Thanks,
> > 	Yaron
> >=20
> > > -----Original Message-----
> > > From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On
> > Behalf Of
> > > Joseph Salowey (jsalowey)
> > > Sent: Thursday, August 06, 2009 22:14
> > > To: emu@ietf.org
> > > Subject: [Emu] Issue #14 Emergency auth
> > >=20
> > >=20
> > > > Referring to Sec. 3.5 of
> > > http://tools.ietf.org/html/draft-ietf-emu-eaptunnel-req-03, there=20
> > > should be an indication to the application that is using=20
> EAP > that=20
> > > such "strange" authentication took place. For example, the
> > VoIP server
> > > may than make sure that only calls to 911 or 112 are allowed.=20
> > > Otherwise
> > > > there is no way to authorize the user without some
> > backchannel into
> > > the AAA.
> > > >
> > > > So I propose to add:
> > >=20
> > > > "The tunnel method, if it supports emergency services,
> > MUST provide
> > > > an
> > > indication at the EAP or EAP-method level that such=20
> authentication=20
> > > took place; >
> > > >  the indication MUST be unencrypted but integrity protected".
> > >=20
> > > I don't understand what this text is for? Who is this
> > indication for?
> > > An application should not be sniffing EAP packets to see
> > what happens.
> > > It seems that this is the responsibility of a local API=20
> between the=20
> > > EAP server and the application.
> > >=20
> > >=20
> > > Joe
> > > _______________________________________________
> > > Emu mailing list
> > > Emu@ietf.org
> > > https://www.ietf.org/mailman/listinfo/emu
> > >=20
> > > Scanned by Check Point Total Security Gateway.
> >=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>=20

From jsalowey@cisco.com  Tue Sep  8 17:23:43 2009
Return-Path: <jsalowey@cisco.com>
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 3289F3A698A for <emu@core3.amsl.com>; Tue,  8 Sep 2009 17:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.588
X-Spam-Level: 
X-Spam-Status: No, score=-6.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 YzlfEYtmgrI9 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 17:23:42 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 3EEF73A68A1 for <emu@ietf.org>; Tue,  8 Sep 2009 17:23:42 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAEOSpkqrR7PE/2dsb2JhbADFNYhDATEEAY9lBYJHBQGBSw
X-IronPort-AV: E=Sophos;i="4.44,355,1249257600"; d="scan'208";a="93662283"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-5.cisco.com with ESMTP; 09 Sep 2009 00:24:12 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n890ODwt021162;  Tue, 8 Sep 2009 17:24:13 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n890ODT3005206; Wed, 9 Sep 2009 00:24:13 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.3959);  Tue, 8 Sep 2009 17:24:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Sep 2009 17:24:11 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508AF92DA@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <7F9A6D26EB51614FBF9F81C0DA4CFEC80133E56C7783@il-ex01.ad.checkpoint.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issue #17: What is "housekeeping"
Thread-Index: AcoWyMRQogTU5P0HRqukSGp1ecj+pQAAdGLgAALjzbAGg1TbQA==
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CED4@xmb-sjc-225.amer.cisco.com> <7F9A6D26EB51614FBF9F81C0DA4CFEC80133E56C7783@il-ex01.ad.checkpoint.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Yaron Sheffer" <yaronf@checkpoint.com>, <emu@ietf.org>
X-OriginalArrivalTime: 09 Sep 2009 00:24:13.0423 (UTC) FILETIME=[DBA53FF0:01CA30E3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1888; t=1252455853; x=1253319853; 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=20Issue=20#17=3A=20What=20is=20=22houseke eping=22 |Sender:=20; bh=OPJsuMySEl49591DteuG+r/SgiFlVHu1fLyG0Dvujvk=; b=FmBQOLhCwO94m4u615JRdsVKZ8u+TWjtYXsjiTcbHJvZqskySLCG1jVvjy KWqw3MoIO875J50WHMzaJ7PDtr8+01UoJZ8FtJRja04zhM1h6Sv1NE9OOdF0 6WtyDxCGSl;
Authentication-Results: sj-dkim-4; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [Emu] Issue #17: What is "housekeeping"
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 00:23:43 -0000

I agree that this is still to vague.  Does anyone have any suggestions?
Unless we can make this more specific I think the following text would
be better:

"The password authentication exchange MUST support password change.  The
exchange SHOULD be extensible to support other "housekeeping" functions,
such as the management of PINs or  other data, required by some
systems."

Thanks,

Joe

> -----Original Message-----
> From: Yaron Sheffer [mailto:yaronf@checkpoint.com]=20
> Sent: Thursday, August 06, 2009 1:41 PM
> To: Joseph Salowey (jsalowey); emu@ietf.org
> Subject: RE: Issue #17: What is "housekeeping"
>=20
> Well, this could stand even more detail, but fine...
>=20
> > -----Original Message-----
> > From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of=20
> > Joseph Salowey (jsalowey)
> > Sent: Thursday, August 06, 2009 22:18
> > To: emu@ietf.org
> > Subject: [Emu] Issue #17: What is "housekeeping"
> >=20
> > #17: What is "housekeeping"
> >=20
> > Issue:
> >=20
> > "The password authentication exchange MUST support password=20
> change, as=20
> > well as other "housekeeping" functions, such as the=20
> management of PINs=20
> > or other data, required by some systems."
> >=20
> > Comment:
> >=20
> >  Suggested Change:
> >=20
> >  "The password authentication exchange MUST support=20
> password change,=20
> > as well as other "housekeeping" functions, such as the=20
> management of=20
> > PINs or  other data, required by some systems."
> >=20
> > --
> > Ticket URL:=20
> > <http://wiki.tools.ietf.org/wg/emu/trac/ticket/17#comment:1>
> > emu <http://tools.ietf.org/wg/emu/>
> >=20
> > _______________________________________________
> > Emu mailing list
> > Emu@ietf.org
> > https://www.ietf.org/mailman/listinfo/emu
> >=20
> > Scanned by Check Point Total Security Gateway.
>=20

From jsalowey@cisco.com  Tue Sep  8 18:13:33 2009
Return-Path: <jsalowey@cisco.com>
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 590AF3A6B40 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 18:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.588
X-Spam-Level: 
X-Spam-Status: No, score=-6.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 WC6rZocRSLEU for <emu@core3.amsl.com>; Tue,  8 Sep 2009 18:13:32 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 3A20C3A6A98 for <emu@ietf.org>; Tue,  8 Sep 2009 18:13:32 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAL+dpkqrR7O6/2dsb2JhbADFXIhDAQ8jAwSPaQWCLhoECIFE
X-IronPort-AV: E=Sophos;i="4.44,355,1249257600"; d="scan'208";a="384708646"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 09 Sep 2009 01:14:03 +0000
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 n891E3Kn028522;  Tue, 8 Sep 2009 18:14:03 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n891E3lF007090; Wed, 9 Sep 2009 01:14:03 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.3959);  Tue, 8 Sep 2009 18:14:03 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Sep 2009 18:14:01 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508AF9310@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <4A7B4124.7000807@isode.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issue #18: Internationalization
Thread-Index: AcoW1wZEXR0gNSqnTg+pjTFmXGsl7gaEO2KA
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CEE0@xmb-sjc-225.amer.cisco.com> <AC6674AB7BC78549BB231821ABF7A9AE8E774C0C7B@EMBX01-WF.jnpr.net> <4A7B4124.7000807@isode.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "Stephen Hanna" <shanna@juniper.net>
X-OriginalArrivalTime: 09 Sep 2009 01:14:03.0366 (UTC) FILETIME=[D1CA5860:01CA30EA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7413; t=1252458843; x=1253322843; 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=20Issue=20#18=3A=20Internationalization |Sender:=20; bh=ntNcXwY0jeAcOoLM21F2q5D7QymWh52VpaYj4+0yXDo=; b=BtN61Xjs8cHzkP3bVrrsIRLl16VsYD86RuLGoZ25yeIfT4BeM5Llo8PEqB qxf1/isy5FW+zyBGONB73XY5+6fqa/Tk/lkasCGEY4E9vBMtXPJm2MBAWmfp Uue/jpRvI/;
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] Issue #18: Internationalization
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 01:13:33 -0000

So if I understand correctly the recommendation for usernames and
passwords is to follow something like SASLPrep [RFC4013] or Net-UTF-8
[RFC5198], but they do not require language tags.  I haven't looked at
RFC 5198 yet, but RFC 4013 seems uncertain as to when it is applicable.
For example it is often common for an email address to be used as a
username, but this seems to be out of scope of 4013.  Also how do you
know if passwords are treated as character data or binary data when used
in a comparison.  What is typically done to deal with these ambiguities?


For other text that is meant for display to a user we should indicate
language according to RFC 4646.  This would include the client
expressing its language preference. Would it also include tags to
indicate the language of the sent text? =20

Thanks,

Joe

> -----Original Message-----
> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]=20
> Sent: Thursday, August 06, 2009 1:46 PM
> To: Stephen Hanna
> Cc: Joseph Salowey (jsalowey); emu@ietf.org
> Subject: Re: Issue #18: Internationalization
>=20
> Hi Stephen,
>=20
> Stephen Hanna wrote:
>=20
> >With respect to the internationalization issue noted below,=20
> relating to=20
> >draft-ietf-emu-eaptunnel-req-02.txt, Alexey Melnikov=20
> recently pointed=20
> >out to me that BCP 18 (RFC 2277), section 4.2 says:
> >
> >   Protocols that transfer text MUST provide for carrying information
> >   about the language of that text.
> >
> >   Protocols SHOULD also provide for carrying information about the
> >   language of names, where appropriate.
> >
> >Section 4.1 of that document explains the reason why. Here's=20
> an excerpt:
> >
> >   Many operations, including high quality formatting, text-to-speech
> >   synthesis, searching, hyphenation, spellchecking and so on benefit
> >   greatly from access to information about the language of=20
> a piece of
> >   text. [WC 3.1.1.4].
> >
> >Internationalization of usernames and passwords has been=20
> discussed at=20
> >length on other lists. Nobody is suggesting in today's=20
> discussion that=20
> >they should have language tags.
> >
> Correct. UTF-8 usernames/password need some normalization=20
> instead (e.g.=20
> SASLPrep [RFC4013] or Net-UTF-8 [RFC5198]).
>=20
> >That is problematic since usernames
> >and passwords often aren't words in any language and the user often=20
> >doesn't have control over the language settings of the system being=20
> >used to enter the username and password. But the text being reviewed=20
> >does not have anything to do with username and password=20
> language issues.
> >
> >The text under discussion in=20
> draft-ietf-emu-eaptunnel-req-03.txt says=20
> >"Any strings sent by the server intended for display to the=20
> user MUST=20
> >be sent in UTF-8 format and SHOULD be able to be marked with=20
> language=20
> >information and adapted to the user's language preference."
> > =20
> >
> As a side note: this would need a reference to RFC 4646.
>=20
> >Notice the words "sent by the server intended for display to=20
> the user".
> >That would not generally apply to usernames and passwords.=20
> Instead, it=20
> >would apply to messages like "Please enter your password" or "Sorry,=20
> >you can't sign in right now due to system maintenance".
> >
> >In order to provide for proper formatting and to allow blind=20
> users to=20
> >have those messages properly converted to audio, it is a=20
> good idea for=20
> >our protocol to include a standard place where the EAP authenticator=20
> >can send language tags with such messages. It's also a good idea for=20
> >the protocol to include a way for the EAP peer to indicate what the=20
> >user's language preferences are (if known). That way, the=20
> authenticator=20
> >can send its messages in the user's preferred language (if=20
> the software=20
> >allows the administrator to enter messages in multiple languages and=20
> >the administrator has chosen to do so).
> > =20
> >
> Right.
>=20
> >So I submit that the text currently in=20
> >draft-ietf-emu-eaptunnel-req-03.txt
> >on this topic is a good idea and that it should not be=20
> removed. As Joe=20
> >noted below, there was not consensus on this issue in the=20
> EMU session=20
> >at IETF 75. I suggest that we discuss it on the list.
> >
> >One concern that I heard expressed was that servers may=20
> decide to fail=20
> >the entire exchange if they don't support any of the user's=20
> preferred=20
> >languages. Apparently, some other protocols some seen this behavior=20
> >when language preferences were sent. Maybe we should add text to the=20
> >eventual protocol specification advising servers not to do that.=20
> >Instead, they should fall back to a default language.
> >
> Agreed.
>=20
> >Are there other concerns?
> >
> >Thanks,
> >
> >Steve
> > =20
> >
> >>-----Original Message-----
> >>From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of=20
> >>Joseph Salowey (jsalowey)
> >>Sent: Thursday, August 06, 2009 3:28 PM
> >>To: emu@ietf.org
> >>Subject: [Emu] Issue #18: Internationalization
> >>
> >>
> >>#18: Internationalization
> >>
> >> Is the use of UTF-8 sufficient or is other tagging necessary.  The=20
> >> following cases need to be considered:
> >>
> >> 1. Usernames and passwords
> >> 2. Prompts and error associated with username and password=20
> >>authentication  3. Other textual data
> >>
> >> > Section 4.3.6
> >> >
> >> > "  The payload MAY provide a standard attribute format
> >>that supports
> >> >    international strings.  This attribute format MUST support
> >>encoding
> >> >    strings in UTF-8 [RFC3629] format.  Any strings sent by
> >>the server
> >> >    intended for display to the user MUST be sent in UTF-8
> >>format and
> >> >    SHOULD be able to be marked with language information and=20
> >> > adapted to
> >> >    the user's language preference."
> >> >
> >> > If UTF-8 is supported, is it necessary to also mark the language?
> >> > Why is language negotiation a SHOULD?
> >> >
> >> > EAP methods such as Identity & Notification don't support this.
> >> >
> >>
> >> and
> >>
> >> > Section 4.5.2
> >> >
> >> > "  The password authentication exchange MUST support=20
> user names and
> >> >    passwords in international languages.  It MUST support
> >>encoding of
> >> >    user name and password strings in UTF-8 [RFC3629] format.  Any
> >> >    strings sent by the server during the password exchange and=20
> >> > intended
> >> >    for display to the user MUST be sent in UTF-8 format
> >>and SHOULD be
> >> >    able to be marked with language information and=20
> adapted to the=20
> >> > user's
> >> >    language preference.
> >> > "
> >> > Why is it useful to mark usernames and passwords with language=20
> >> > information on the wire?
> >>
> >>Comment:
> >>
> >>In the Stockholm meeting it was suggested UTF-8 was sufficient, but=20
> >>there did not appear to be consensus on this.
> >>
> >>--
> >>Ticket URL: <http://trac.tools.ietf.org/wg/emu/trac/ticket/18>
> >>emu <http://tools.ietf.org/wg/emu/>
> >>
> >>_______________________________________________
> >>Emu mailing list
> >>Emu@ietf.org
> >>https://www.ietf.org/mailman/listinfo/emu
> >>   =20
> >>
>=20
>=20

From jsalowey@cisco.com  Tue Sep  8 19:06:10 2009
Return-Path: <jsalowey@cisco.com>
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 D56B428C1E5 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 19:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.288
X-Spam-Level: 
X-Spam-Status: No, score=-6.288 tagged_above=-999 required=5 tests=[AWL=-0.289, BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-4]
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 9-DlkLp-vH0O for <emu@core3.amsl.com>; Tue,  8 Sep 2009 19:06:09 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id E27643A6932 for <emu@ietf.org>; Tue,  8 Sep 2009 19:06:09 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAGeqpkqrR7MV/2dsb2JhbADFRohDAZAgBYQY
X-IronPort-AV: E=Sophos;i="4.44,355,1249257600"; d="scan'208";a="202787539"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 09 Sep 2009 02:06:41 +0000
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 n8926fti009748 for <emu@ietf.org>; Tue, 8 Sep 2009 19:06:41 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n8926fvG019576 for <emu@ietf.org>; Wed, 9 Sep 2009 02:06:41 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.3959);  Tue, 8 Sep 2009 19:06:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Sep 2009 19:06:40 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508AF932A@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50883CEED@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Issue #19: Method Chaining
Thread-Index: AcoWzeZWWi30NxybRpW3/EmLFyyDdwAACnFQBoj/HsA=
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CEED@xmb-sjc-225.amer.cisco.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
X-OriginalArrivalTime: 09 Sep 2009 02:06:41.0386 (UTC) FILETIME=[2C1DF4A0:01CA30F2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1963; t=1252462001; x=1253326001; 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:=20RE=3A=20[Emu]=20Issue=20#19=3A=20Method=20Chain ing |Sender:=20; bh=9NPDX1jNcjuAdOFfRr/y75TH0AXlfcn5/SYlh8YVuY8=; b=GJgYjR4c3ehlr9bMq8Q0HWRaA3AjEDr7KD/aMBiaZqpYuUWxu4EcyYIogJ KKgKQamxGJiQj36GBqPRXjTrNgfMHboggEcuYzhZM1NPvQpoD3cjTmeW2l5g FqJzvfE7uMyJW+GTEc9NmJErNbtcfVfJOTCC8U2r0iEXZmoOs1vg0=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [Emu] Issue #19: Method Chaining
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 02:06:10 -0000

Any objection to changing MUST to SHOULD for method chaining?

Thanks,

Joe=20

> -----Original Message-----
> From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of Joseph Salowey (jsalowey)
> Sent: Thursday, August 06, 2009 12:44 PM
> To: emu@ietf.org
> Subject: [Emu] Issue #19: Method Chaining
>=20
> #19: Method Chaining
>=20
>  > Section 3.3
>  >
>  > "  Several circumstances are best addressed by using chained EAP
>  >    methods.  For example, it may be desirable to authenticate the
> user
>  >    and also authenticate the device that he or she is using."
>  > This requirement can be met by support for cryptographic =20
> > binding, without chaining of EAP methods.  For example, the=20
>  > combination of TLS and an inner method can support  >=20
> user/device auth.  Given that, why is support for chained  >=20
> methods a must, and not device/user auth support?
>  >
>  and
>  > Section 4.6.2
>  >
>  > "   The tunnel method MUST support the chaining of multiple
>  > EAP methods.
>  >    The tunnel method MUST allow for the communication of=20
> intermediate
>  >    result and verification of compound binding between=20
> executed inner
>  >    methods when chained methods are employed.
>  > "
>  >
>  > Given that the basic use case (machine + user auth)=20
> doesn't  > require chaining of EAP methods, why is this a MUST?
>  >
>=20
> --
>=20
> Comment(by jsalowey@cisco.com):
>=20
>  In the Stockholm meeting there was indication that there=20
> were other  mechanisms that could require chaining, such as=20
> posture checking.
> People
>  seemed to favor changing from MUST to SHOULD.
>=20
> --
> Ticket URL:=20
> <http://trac.tools.ietf.org/wg/emu/trac/ticket/19#comment:1>
> emu <http://tools.ietf.org/wg/emu/>
>=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>=20

From bernard_aboba@hotmail.com  Tue Sep  8 19:08:55 2009
Return-Path: <bernard_aboba@hotmail.com>
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 7B3AD3A6A31 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 19:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.394
X-Spam-Level: 
X-Spam-Status: No, score=0.394 tagged_above=-999 required=5 tests=[AWL=0.392,  BAYES_50=0.001, HTML_MESSAGE=0.001]
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 rKQANqlbCpZg for <emu@core3.amsl.com>; Tue,  8 Sep 2009 19:08:54 -0700 (PDT)
Received: from blu0-omc4-s28.blu0.hotmail.com (blu0-omc4-s28.blu0.hotmail.com [65.55.111.167]) by core3.amsl.com (Postfix) with ESMTP id 78FFA3A6828 for <emu@ietf.org>; Tue,  8 Sep 2009 19:08:54 -0700 (PDT)
Received: from BLU137-W1 ([65.55.111.137]) by blu0-omc4-s28.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 8 Sep 2009 19:09:26 -0700
Message-ID: <BLU137-W1CA15DB7FC869C351AC8293E90@phx.gbl>
Content-Type: multipart/alternative; boundary="_3d0ba1bd-58fe-4cf1-acda-4be66449329f_"
X-Originating-IP: [131.107.0.104]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
Date: Tue, 8 Sep 2009 19:09:25 -0700
Importance: Normal
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE508AF918A@xmb-sjc-225.amer.cisco.com>
References: <BLU137-W4C1E9263CC3A9EDABFB8A93060@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5088B0F51@xmb-sjc-225.amer.cisco.com> <BLU137-W1351F278F8E9D7DB662C7193050@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5089320CE@xmb-sjc-225.amer.cisco.com> <BLU137-W36DE8884CA39C5ACAB551793FF0@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE508AF918A@xmb-sjc-225.amer.cisco.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Sep 2009 02:09:26.0419 (UTC) FILETIME=[8E7BFE30:01CA30F2]
Subject: Re: [Emu] #18 Internationalization of error messages
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 02:08:55 -0000

--_3d0ba1bd-58fe-4cf1-acda-4be66449329f_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


I don't have a problem with requiring support for UTF-8 in usernames
and passwords within authentication mechanisms native to the tunnel
method.  However=2C I do have an issue with requiring internationalization =
of error message text. =20

One of the principles of good protocol design is to *avoid* internationaliz=
ation problems within error messages by use of error numbers (e.g. 404 in H=
TTP and SIP).  This makes it possible for client software to display locali=
zed versions of error messages without requiring the server to support inte=
rnationalization.

If the tunnel protocol incorporates error numbers=2C it should therefore no=
t be necessary for the server to send internationalized error text. =20

Adding requirements for internationalization of error text or negotiation o=
f language tags for error messages is not only unnecessary=2C it is actuall=
y enforcing a requirement for a *bad design*. =20





--_3d0ba1bd-58fe-4cf1-acda-4be66449329f_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
I don't have a problem with requiring support for UTF-8 in usernames
and passwords within authentication mechanisms native to the tunnel
method.&nbsp=3B However=2C I do have an issue with requiring internationali=
zation of error message text.&nbsp=3B <br><br>One of the principles of good=
 protocol design is to *avoid* internationalization problems within error m=
essages by use of error numbers (e.g. 404 in HTTP and SIP).&nbsp=3B This ma=
kes it possible for client software to display localized versions of error =
messages without requiring the server to support internationalization.<br><=
br>If the tunnel protocol incorporates error numbers=2C it should therefore=
 not be necessary for the server to send internationalized error text.&nbsp=
=3B <br><br>Adding requirements for internationalization of error text or n=
egotiation of language tags for error messages is not only unnecessary=2C i=
t is actually enforcing a requirement for a *bad design*.&nbsp=3B <br><br><=
br><br><br></body>
</html>=

--_3d0ba1bd-58fe-4cf1-acda-4be66449329f_--

From jsalowey@cisco.com  Tue Sep  8 19:25:51 2009
Return-Path: <jsalowey@cisco.com>
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 28F9C28C167 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 19:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.583
X-Spam-Level: 
X-Spam-Status: No, score=-6.583 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 1ZZxEXlomwNO for <emu@core3.amsl.com>; Tue,  8 Sep 2009 19:25:50 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 31A893A6B42 for <emu@ietf.org>; Tue,  8 Sep 2009 19:25:50 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq8EAKqupkqrR7O6/2dsb2JhbACQFLUbiEMBkCIFhBg
X-IronPort-AV: E=Sophos;i="4.44,355,1249257600"; d="scan'208";a="42576039"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-4.cisco.com with ESMTP; 09 Sep 2009 02:26:21 +0000
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 n892QLi8011053;  Tue, 8 Sep 2009 19:26:21 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n892QL9Y022165; Wed, 9 Sep 2009 02:26:21 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.3959);  Tue, 8 Sep 2009 19:26:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Sep 2009 19:26:20 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508AF933C@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <BLU137-W1CA15DB7FC869C351AC8293E90@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] #18 Internationalization of error messages
Thread-Index: Acow8pECy5t3EbJmRw6/TF16ntl5YgAAE2tQ
References: <BLU137-W4C1E9263CC3A9EDABFB8A93060@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5088B0F51@xmb-sjc-225.amer.cisco.com> <BLU137-W1351F278F8E9D7DB662C7193050@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5089320CE@xmb-sjc-225.amer.cisco.com> <BLU137-W36DE8884CA39C5ACAB551793FF0@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE508AF918A@xmb-sjc-225.amer.cisco.com> <BLU137-W1CA15DB7FC869C351AC8293E90@phx.gbl>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <emu@ietf.org>
X-OriginalArrivalTime: 09 Sep 2009 02:26:21.0653 (UTC) FILETIME=[EB9C6850:01CA30F4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1772; t=1252463181; x=1253327181; 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]=20#18=20Internationalization=20of =20error=20messages |Sender:=20; bh=eRf5fGqv+u9lEu5mAMq3G04ekZ7wD0NhmKW5LMT7xWA=; b=TkQgFMuKNzqvbdHWLn3FpLCGEiovTweFG+mhcRcRySFbMWlPQko4tvUESF 6vw4MdzAO7D389qEkSWIr95CrUKuTFYakf/Ksy0RwvWP2TjBIJ4ihQUvVO3U wP2ud+4j9B;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [Emu] #18 Internationalization of error messages
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 02:25:51 -0000

OK, makes sense.  How about we make the language tags specific to text
sent from the server to the peer that is intended to be displayed to a
user.  We can also specifically state that it is also acceptable to send
numeric codes that can be mapped to a specific representation by the
client to meet the internationalization requirement.  These codes would
not be internationalized even if they were in ASCII/UTE-8 format.=20

Does this make sense?

Thanks,

Joe

> -----Original Message-----
> From: Bernard Aboba [mailto:bernard_aboba@hotmail.com]=20
> Sent: Tuesday, September 08, 2009 7:09 PM
> To: Joseph Salowey (jsalowey); emu@ietf.org
> Subject: RE: [Emu] #18 Internationalization of error messages
>=20
> I don't have a problem with requiring support for UTF-8 in=20
> usernames and passwords within authentication mechanisms=20
> native to the tunnel method.  However, I do have an issue=20
> with requiring internationalization of error message text. =20
>=20
> One of the principles of good protocol design is to *avoid*=20
> internationalization problems within error messages by use of=20
> error numbers (e.g. 404 in HTTP and SIP).  This makes it=20
> possible for client software to display localized versions of=20
> error messages without requiring the server to support=20
> internationalization.
>=20
> If the tunnel protocol incorporates error numbers, it should=20
> therefore not be necessary for the server to send=20
> internationalized error text. =20
>=20
> Adding requirements for internationalization of error text or=20
> negotiation of language tags for error messages is not only=20
> unnecessary, it is actually enforcing a requirement for a=20
> *bad design*. =20
>=20
>=20
>=20
>=20
>=20
>=20

From jsalowey@cisco.com  Tue Sep  8 20:30:38 2009
Return-Path: <jsalowey@cisco.com>
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 DCF1128C223 for <emu@core3.amsl.com>; Tue,  8 Sep 2009 20:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.583
X-Spam-Level: 
X-Spam-Status: No, score=-6.583 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 FqtMRWrcA9vb for <emu@core3.amsl.com>; Tue,  8 Sep 2009 20:30:37 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id CFB0B28C1C5 for <emu@ietf.org>; Tue,  8 Sep 2009 20:30:37 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAI++pkqrR7MV/2dsb2JhbADFL4hDATWPcAWCSAQIgUQ
X-IronPort-AV: E=Sophos;i="4.44,356,1249257600"; d="scan'208";a="384770961"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 09 Sep 2009 03:31:09 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n893V9c1001018 for <emu@ietf.org>; Tue, 8 Sep 2009 20:31:09 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n893V9MT001773 for <emu@ietf.org>; Wed, 9 Sep 2009 03:31:09 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.3959);  Tue, 8 Sep 2009 20:31:09 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Sep 2009 20:31:08 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508AF9355@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50883CF26@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Issue #24: Backend password attacks
Thread-Index: AcoW01ZQ6V50SEsMSQyQAcK39A7QJwAAD31wBoo9nYA=
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CF26@xmb-sjc-225.amer.cisco.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
X-OriginalArrivalTime: 09 Sep 2009 03:31:09.0320 (UTC) FILETIME=[F8D75080:01CA30FD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2794; t=1252467069; x=1253331069; 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:=20RE=3A=20[Emu]=20Issue=20#24=3A=20Backend=20pass word=20attacks |Sender:=20; bh=+EVnPqZ5LHx9lBhVikcr6XUj67Lv0ApnwC1ybkYjQl0=; b=ScA6HVT8rLMgjuRbeLHb/DbE1jaLqHTSGvg2K0dPEFpQRGBspf+e6AKy4j JiXskwIAg+fJXn6PamXkcBpyzOy1T//26Hr7CFkHnZR52Z0HoQP3KpPpg0xG gFH2+iZofjeaDb7CIgbdJMtywdu+4TcGkdVVIXYX9S0k/YAUT1vjs=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [Emu] Issue #24: Backend password attacks
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 03:30:38 -0000

How about adding the following section to the security considerations

"Separation of TLS tunnel and inner authentication termination

Terminating the inner method at a different location than the outer
tunnel needs careful consideration. The inner method data may be
vulnerable to modification and  eavesdropping between the server that
terminates the tunnel and the server that terminates the inner method.
For example if a clear text password is used then it may be sent to the
inner method server in a RADIUS password attribute which uses weak
encryption that may not be suitable  protection for many environments. =20

In some cases terminating the tunnel at a different location may make it
difficult for a peer to authenticate the server and trust it for further
communication.  For example, if the TLS tunnel is terminated by a
different organization the peer needs to be able to authenticate and
authorize the tunnel server to handle secret credentials that it shares
with the home server that terminates the inner method.  This may not
meet the security policy of many environments."

Cheers,

Joe

=20

> -----Original Message-----
> From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of Joseph Salowey (jsalowey)
> Sent: Thursday, August 06, 2009 1:23 PM
> To: emu@ietf.org
> Subject: [Emu] Issue #24: Backend password attacks
>=20
> #24: Backend password attacks
>=20
>  > Section 4.5
>  >
>  > "These typically
>  >    require the password in its original text form in order to
>  >    authenticate the peer, hence they require the peer to send
>  > the clear
>  >    text user name and password to the EAP server."
>  >
>  > One of the issues with support for cleartext passwords are=20
>  > the potential attacks against the AAA backend (e.g.
>  > User-Password attribute) in split authentication scenarios.
>  > Is it worth calling this out?
>  >
>=20
>  How about adding the following to security considerations section:
>=20
>  "If the inner method is terminated at a different location=20
> than the outer  tunnel then the inner method data may be=20
> vulnerable to modification and  eavesdropping between the=20
> server that terminates the tunnel and the server
>  that terminates the inner method.   For example if a clear text
> password
>  is used then it may be sent to the inner method server in a=20
> RADIUS  password attribute which uses weak encryption that=20
> may not be suitable  protection for many environments. "
>=20
> --
> Ticket URL: <http://wiki.tools.ietf.org/wg/emu/trac/ticket/24>
> emu <http://tools.ietf.org/wg/emu/>
>=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>=20

From aland@deployingradius.com  Wed Sep  9 00:55:16 2009
Return-Path: <aland@deployingradius.com>
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 41CC13A6835 for <emu@core3.amsl.com>; Wed,  9 Sep 2009 00:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.601,  BAYES_00=-2.599]
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 Em6dbdP0Dyq1 for <emu@core3.amsl.com>; Wed,  9 Sep 2009 00:55:15 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 727CE3A6938 for <emu@ietf.org>; Wed,  9 Sep 2009 00:55:15 -0700 (PDT)
Received: from Thor.local (mey38-2-82-228-181-7.fbx.proxad.net [82.228.181.7]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 45E9E12345E2; Wed,  9 Sep 2009 09:55:46 +0200 (CEST)
Message-ID: <4AA75F82.8040609@deployingradius.com>
Date: Wed, 09 Sep 2009 09:55:46 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CED4@xmb-sjc-225.amer.cisco.com>	<7F9A6D26EB51614FBF9F81C0DA4CFEC80133E56C7783@il-ex01.ad.checkpoint.com> <AC1CFD94F59A264488DC2BEC3E890DE508AF92DA@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE508AF92DA@xmb-sjc-225.amer.cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: emu@ietf.org, Yaron Sheffer <yaronf@checkpoint.com>
Subject: Re: [Emu] Issue #17: What is "housekeeping"
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 07:55:16 -0000

Joseph Salowey (jsalowey) wrote:
> I agree that this is still to vague.  Does anyone have any suggestions?
> Unless we can make this more specific I think the following text would
> be better:
> 
> "The password authentication exchange MUST support password change.  The
> exchange SHOULD be extensible to support other "housekeeping" functions,
> such as the management of PINs or  other data, required by some
> systems."

  That looks good to me.

  Alan DeKok.

From alexey.melnikov@isode.com  Wed Sep  9 02:57:05 2009
Return-Path: <alexey.melnikov@isode.com>
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 E70103A67E9 for <emu@core3.amsl.com>; Wed,  9 Sep 2009 02:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
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 TjNWzak8vYHW for <emu@core3.amsl.com>; Wed,  9 Sep 2009 02:57:04 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 2FEBE3A6909 for <emu@ietf.org>; Wed,  9 Sep 2009 02:57:04 -0700 (PDT)
Received: from [172.16.2.166] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Sqd8DQB9YSe0@rufus.isode.com>; Wed, 9 Sep 2009 10:57:34 +0100
Message-ID: <4AA77BF2.70501@isode.com>
Date: Wed, 09 Sep 2009 10:57:06 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CEE0@xmb-sjc-225.amer.cisco.com> <AC6674AB7BC78549BB231821ABF7A9AE8E774C0C7B@EMBX01-WF.jnpr.net> <4A7B4124.7000807@isode.com> <AC1CFD94F59A264488DC2BEC3E890DE508AF9310@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE508AF9310@xmb-sjc-225.amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: emu@ietf.org
Subject: Re: [Emu] Issue #18: Internationalization
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 09:57:06 -0000

Hi Joseph,

Joseph Salowey (jsalowey) wrote:

>So if I understand correctly the recommendation for usernames and
>passwords is to follow something like SASLPrep [RFC4013] or Net-UTF-8
>[RFC5198], but they do not require language tags.
>
Correct. RFC 4013, while not perfect, was specifically designed for 
usernames/textual passwords.

>I haven't looked at
>RFC 5198 yet, but RFC 4013 seems uncertain as to when it is applicable.
>For example it is often common for an email address to be used as a
>username, but this seems to be out of scope of 4013.
>
RFC 4013 was deliberately vague on this (and I disagreed with the author 
on this), but it is frequently used for email-like usernames. This is 
how it is used in SASL.

>Also how do you know if passwords are treated as character data or binary data when used
>in a comparison.  What is typically done to deal with these ambiguities?
>  
>
RFC 4013 only applies to textual passwords.

>For other text that is meant for display to a user we should indicate
>language according to RFC 4646.
>
Yes.

>This would include the client
>expressing its language preference. Would it also include tags to
>indicate the language of the sent text?
>  
>
Yes.

>Thanks,
>
>Joe
>
>  
>
>>-----Original Message-----
>>From: Alexey Melnikov [mailto:alexey.melnikov@isode.com] 
>>Sent: Thursday, August 06, 2009 1:46 PM
>>To: Stephen Hanna
>>Cc: Joseph Salowey (jsalowey); emu@ietf.org
>>Subject: Re: Issue #18: Internationalization
>>
>>Hi Stephen,
>>
>>Stephen Hanna wrote:
>>
>>    
>>
>>>With respect to the internationalization issue noted below, 
>>>      
>>>
>>relating to 
>>    
>>
>>>draft-ietf-emu-eaptunnel-req-02.txt, Alexey Melnikov 
>>>      
>>>
>>recently pointed 
>>    
>>
>>>out to me that BCP 18 (RFC 2277), section 4.2 says:
>>>
>>>  Protocols that transfer text MUST provide for carrying information
>>>  about the language of that text.
>>>
>>>  Protocols SHOULD also provide for carrying information about the
>>>  language of names, where appropriate.
>>>
>>>Section 4.1 of that document explains the reason why. Here's 
>>>      
>>>
>>an excerpt:
>>    
>>
>>>  Many operations, including high quality formatting, text-to-speech
>>>  synthesis, searching, hyphenation, spellchecking and so on benefit
>>>  greatly from access to information about the language of 
>>>      
>>>
>>a piece of
>>    
>>
>>>  text. [WC 3.1.1.4].
>>>
>>>Internationalization of usernames and passwords has been 
>>>      
>>>
>>discussed at 
>>    
>>
>>>length on other lists. Nobody is suggesting in today's 
>>>      
>>>
>>discussion that 
>>    
>>
>>>they should have language tags.
>>>
>>>      
>>>
>>Correct. UTF-8 usernames/password need some normalization 
>>instead (e.g. 
>>SASLPrep [RFC4013] or Net-UTF-8 [RFC5198]).
>>
>>    
>>
>>>That is problematic since usernames
>>>and passwords often aren't words in any language and the user often 
>>>doesn't have control over the language settings of the system being 
>>>used to enter the username and password. But the text being reviewed 
>>>does not have anything to do with username and password 
>>>      
>>>
>>language issues.
>>    
>>
>>>The text under discussion in 
>>>      
>>>
>>draft-ietf-emu-eaptunnel-req-03.txt says 
>>    
>>
>>>"Any strings sent by the server intended for display to the 
>>>      
>>>
>>user MUST 
>>    
>>
>>>be sent in UTF-8 format and SHOULD be able to be marked with 
>>>      
>>>
>>language 
>>    
>>
>>>information and adapted to the user's language preference."
>>> 
>>>
>>>      
>>>
>>As a side note: this would need a reference to RFC 4646.
>>
>>    
>>
>>>Notice the words "sent by the server intended for display to 
>>>      
>>>
>>the user".
>>    
>>
>>>That would not generally apply to usernames and passwords. 
>>>      
>>>
>>Instead, it 
>>    
>>
>>>would apply to messages like "Please enter your password" or "Sorry, 
>>>you can't sign in right now due to system maintenance".
>>>
>>>In order to provide for proper formatting and to allow blind 
>>>      
>>>
>>users to 
>>    
>>
>>>have those messages properly converted to audio, it is a 
>>>      
>>>
>>good idea for 
>>    
>>
>>>our protocol to include a standard place where the EAP authenticator 
>>>can send language tags with such messages. It's also a good idea for 
>>>the protocol to include a way for the EAP peer to indicate what the 
>>>user's language preferences are (if known). That way, the 
>>>      
>>>
>>authenticator 
>>    
>>
>>>can send its messages in the user's preferred language (if 
>>>      
>>>
>>the software 
>>    
>>
>>>allows the administrator to enter messages in multiple languages and 
>>>the administrator has chosen to do so).
>>> 
>>>
>>>      
>>>
>>Right.
>>
>>    
>>
>>>So I submit that the text currently in 
>>>draft-ietf-emu-eaptunnel-req-03.txt
>>>on this topic is a good idea and that it should not be 
>>>      
>>>
>>removed. As Joe 
>>    
>>
>>>noted below, there was not consensus on this issue in the 
>>>      
>>>
>>EMU session 
>>    
>>
>>>at IETF 75. I suggest that we discuss it on the list.
>>>
>>>One concern that I heard expressed was that servers may 
>>>      
>>>
>>decide to fail 
>>    
>>
>>>the entire exchange if they don't support any of the user's 
>>>      
>>>
>>preferred 
>>    
>>
>>>languages. Apparently, some other protocols some seen this behavior 
>>>when language preferences were sent. Maybe we should add text to the 
>>>eventual protocol specification advising servers not to do that. 
>>>Instead, they should fall back to a default language.
>>>
>>>      
>>>
>>Agreed.
>>
>>    
>>
>>>Are there other concerns?
>>>
>>>Thanks,
>>>
>>>Steve
>>> 
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On 
>>>>        
>>>>
>>Behalf Of 
>>    
>>
>>>>Joseph Salowey (jsalowey)
>>>>Sent: Thursday, August 06, 2009 3:28 PM
>>>>To: emu@ietf.org
>>>>Subject: [Emu] Issue #18: Internationalization
>>>>
>>>>
>>>>#18: Internationalization
>>>>
>>>>Is the use of UTF-8 sufficient or is other tagging necessary.  The 
>>>>following cases need to be considered:
>>>>
>>>>1. Usernames and passwords
>>>>2. Prompts and error associated with username and password 
>>>>authentication  3. Other textual data
>>>>
>>>>        
>>>>
>>>>>Section 4.3.6
>>>>>
>>>>>"  The payload MAY provide a standard attribute format
>>>>>          
>>>>>
>>>>that supports
>>>>        
>>>>
>>>>>   international strings.  This attribute format MUST support
>>>>>          
>>>>>
>>>>encoding
>>>>        
>>>>
>>>>>   strings in UTF-8 [RFC3629] format.  Any strings sent by
>>>>>          
>>>>>
>>>>the server
>>>>        
>>>>
>>>>>   intended for display to the user MUST be sent in UTF-8
>>>>>          
>>>>>
>>>>format and
>>>>        
>>>>
>>>>>   SHOULD be able to be marked with language information and 
>>>>>adapted to
>>>>>   the user's language preference."
>>>>>
>>>>>If UTF-8 is supported, is it necessary to also mark the language?
>>>>>Why is language negotiation a SHOULD?
>>>>>
>>>>>EAP methods such as Identity & Notification don't support this.
>>>>>
>>>>>          
>>>>>
>>>>and
>>>>
>>>>        
>>>>
>>>>>Section 4.5.2
>>>>>
>>>>>"  The password authentication exchange MUST support 
>>>>>          
>>>>>
>>user names and
>>    
>>
>>>>>   passwords in international languages.  It MUST support
>>>>>          
>>>>>
>>>>encoding of
>>>>        
>>>>
>>>>>   user name and password strings in UTF-8 [RFC3629] format.  Any
>>>>>   strings sent by the server during the password exchange and 
>>>>>intended
>>>>>   for display to the user MUST be sent in UTF-8 format
>>>>>          
>>>>>
>>>>and SHOULD be
>>>>        
>>>>
>>>>>   able to be marked with language information and 
>>>>>          
>>>>>
>>adapted to the 
>>    
>>
>>>>>user's
>>>>>   language preference.
>>>>>"
>>>>>Why is it useful to mark usernames and passwords with language 
>>>>>information on the wire?
>>>>>          
>>>>>
>>>>Comment:
>>>>
>>>>In the Stockholm meeting it was suggested UTF-8 was sufficient, but 
>>>>there did not appear to be consensus on this.
>>>>
>>>>--
>>>>Ticket URL: <http://trac.tools.ietf.org/wg/emu/trac/ticket/18>
>>>>emu <http://tools.ietf.org/wg/emu/>
>>>>
>>>>_______________________________________________
>>>>Emu mailing list
>>>>Emu@ietf.org
>>>>https://www.ietf.org/mailman/listinfo/emu
>>>>   
>>>>
>>>>        
>>>>
>
>  
>


From aland@deployingradius.com  Wed Sep  9 08:07:51 2009
Return-Path: <aland@deployingradius.com>
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 D51FB3A6A08 for <emu@core3.amsl.com>; Wed,  9 Sep 2009 08:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.004
X-Spam-Level: 
X-Spam-Status: No, score=-2.004 tagged_above=-999 required=5 tests=[AWL=0.595,  BAYES_00=-2.599]
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 nhI6tynl5C3n for <emu@core3.amsl.com>; Wed,  9 Sep 2009 08:07:50 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 7009A28C294 for <emu@ietf.org>; Wed,  9 Sep 2009 08:07:50 -0700 (PDT)
Received: from Thor.local (mey38-2-82-228-181-7.fbx.proxad.net [82.228.181.7]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 9488B12345E2 for <emu@ietf.org>; Wed,  9 Sep 2009 17:08:22 +0200 (CEST)
Message-ID: <4AA7C4E6.9060609@deployingradius.com>
Date: Wed, 09 Sep 2009 17:08:22 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "emu@ietf.org" <emu@ietf.org>
X-Enigmail-Version: 0.96.0
Content-Type: multipart/mixed; boundary="------------060209060002000108050107"
Subject: [Emu] [Fwd: FW: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available]
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 15:07:51 -0000

This is a multi-part message in MIME format.
--------------060209060002000108050107
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


--------------060209060002000108050107
Content-Type: message/rfc822;
 name="FW: Nomcom 2009-10: Important Reminder: Call for Nominations,	Local Officehours, Nominee Questionnaires available.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="FW: Nomcom 2009-10: Important Reminder: Call for Nominations";
 filename*1=",	Local Office hours, Nominee Questionnaires available.eml"

X-Account-Key: account3
X-Mozilla-Keys: 
Return-Path: <wgchairs-bounces@ietf.org>
X-Original-To: aland@deployingradius.com
Delivered-To: aland@deployingradius.com
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
	by liberty.deployingradius.com (Postfix) with ESMTP id 9BC6712345E2
	for <aland@deployingradius.com>; Wed,  9 Sep 2009 16:44:51 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7D913A6BD9;
	Wed,  9 Sep 2009 07:44:17 -0700 (PDT)
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E92893A6985
	for <wgchairs@core3.amsl.com>; Wed,  9 Sep 2009 07:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.559
X-Spam-Level: 
X-Spam-Status: No, score=-6.559 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OhUM+Hoyq6D1 for <wgchairs@core3.amsl.com>;
	Wed,  9 Sep 2009 07:44:15 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 95D903A67F9
	for <wgchairs@ietf.org>; Wed,  9 Sep 2009 07:44:15 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	n89EifM16307 for <wgchairs@ietf.org>; Wed, 9 Sep 2009 14:44:42 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: FW: Nomcom 2009-10: Important Reminder: Call for Nominations,
	Local Office hours, Nominee Questionnaires available 
Date: Wed, 9 Sep 2009 09:46:38 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1FD67837@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Nomcom 2009-10: Important Reminder: Call for Nominations,
	Local Office hours, Nominee Questionnaires available 
Thread-Index: AcoxW3x0itr054ovT3Oh2zchhv74PgAALA6g
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Working Group Chairs" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Sender: wgchairs-bounces@ietf.org
Errors-To: wgchairs-bounces@ietf.org

Hi all,

Thanks to the ADs and chairs that forwarded the previous reminder to
their mailing lists. I would appreciate it if other chairs and ADs could
do so, since we are really in need of more nominations.

Thanks,
Mary.=20

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of Barnes, Mary
(RICH2:AR00)
Sent: Wednesday, September 09, 2009 9:38 AM
To: IETF Announcement list
Cc: ietf@ietf.org
Subject: Nomcom 2009-10: Important Reminder: Call for Nominations, Local
Office hours, Nominee Questionnaires available=20

Hi all,

This is a 2nd reminder of the Call for Nominations that is underway.  We
*really* need more nominations in order to properly execute the task of
selecting candidates for the open positions. At this time, the number of
nominations for all the positions is about 1/2 of what is necessary for
the Nomcom to do a conscientious job of evaluating the nominees and we
are over 2/3 of the way through the nominations period. Nomcom cannot do
their job without this important input from the community.=20

So, please consider making nominations for the open positions - it takes
just a few minutes of your time - the details are below.  Right now, we
just need the names/email addresses for the nominees - we'll be
soliciting feedback later. Also, consider that over 1/2 the nominees are
not able to accept the nominations for a variety of reasons - e.g., lack
of funding, lack of sponsor support, etc. Thus, please consider
nominating more than one individual for each of the positions. =20

As well as the reminder for the call for nominations, this email also
serves as a reminder for:
2) Local Office Hours
3) Questionnaires available for nominees=20

Best Regards,
Mary Barnes
nomcom-chair@ietf.org
mary.h.barnes@gmail.com
mary.barnes@nortel.com


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D

1) Call for Nominations
------------------------
The nomination period ends in less than 2 weeks on Sept. 18th, 2009. We
appreciate the folks that have taken the time to make nominations thus
far. But, we do need more nominations. Please use the online tool to
nominate - it's fast, easy and secure:
https://wiki.tools.ietf.org/group/nomcom/09/nominate

Details on the open positions, as well as other details and options for
making nominations are available on the Nomcom homepage:
https://wiki.tools.ietf.org/group/nomcom/09/

Please consider that the sooner you make the nominations, the more time
your nominee(s) will have to complete the necessary questionnaire (item
3
below).  As well, please consider nominating more than one person for a
particular position. You will have the opportunity to provide additional
feedback later and it's important to consider that not all nominees will
be able to accept the nomination.=20


2) Local office hours
-----------------------

In order facilitate additional feedback, the Nomcom has decided to make
themselves available for office areas at various geographic locations
for
3 weeks in September, starting on the 8th.=20

Below please find the list of locations where Nomcom members will be
available for these f2f meetings . Unless dates are identified below,
the
Nomcom member is generally available for part of the day during the
weeks
of Sept 8-11, Sept 14-18 and Sept 21-25. Also, languages other than
English in which the Nomcom member is fluent are identfied. =20

Please contact a Nomcom member in a specific geographic location to
arrange a convenient meeting time and place. Most Nomcom members are
flexible as to meeting locations - i.e., we can travel to your office,
meet at our offices or somewhere in between. =20

As a reminder folks can always contact any Nomcom member to provide
feedback at anytime - i.e., you don't need to participate in these f2f
sessions to provide feedback.=20


Belgium:=20
     Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept
21-25) (Languages: French)=20

Boston, Mass, USA: =20
     Stephen Kent - kent@bbn.com  (Sept 16-18)=20

Boulder, CO, USA:=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 14-18)

Dallas/Ft. Worth, TX, USA: =20
     Mary Barnes  - mary.h.barnes@gmail.com=20
     Lucy Yong - lucyyong@huawei.com  (Languages: Chinese)=20

Helsinki, Finland:=20
      Simo Veikkolainen - simo.veikkolainen@nokia.com (Languages:
Finnish)
=20

Ithaca, NY, USA:=20
      Scott Brim - scott.brim@gmail.com

Montevideo, Uruguay:=20
      Roque Gagliano - roque@lacnic.net (Sept 14-18, 21-25) (Languages:
Spanish, Portuguese)=20

Montreal, Quebec, Canada=20
     Wassim Haddad - wmhaddad@gmail.com (Sept 8-11)
     -- Can also be available in Ottawa if folks are interested=20

Paris, France:=20
      Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be
(Sept 15-18)  (Languages: French)

San Diego, CA, USA:=20
      Randall Gellens - rg+ietf@qualcomm.com  =20
      Dave Crocker - dcrocker@bbiw.net  (Sept 16-18)

Silicon Valley/SF Bay,  CA, USA:=20
      Dave Crocker - dcrocker@bbiw.net  (Sept 8-11, Sept 14-15, Sept
21-25)  =20
      Dorothy Gellert - Dorothy.gellert@gmail.com

3) Questionnaires available for nominees:=20

For folks that have been notified that they have been nominated for any
of the positions, the questionnaires are now available on the Nomcom09
tools website:
https://wiki.tools.ietf.org/group/nomcom/09/iab-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iaoc-questionnaire
https://wiki.tools.ietf.org/group/nomcom/09/iesg-questionnaire

If you have any questions, please let me know. I will be contacting
everyone individually, as well as sending reminders.=20


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce



--------------060209060002000108050107--

From bernard_aboba@hotmail.com  Wed Sep  9 12:36:22 2009
Return-Path: <bernard_aboba@hotmail.com>
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 7883828C12E for <emu@core3.amsl.com>; Wed,  9 Sep 2009 12:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.607
X-Spam-Level: 
X-Spam-Status: No, score=-0.607 tagged_above=-999 required=5 tests=[AWL=1.372,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619]
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 afsRDYoENSt3 for <emu@core3.amsl.com>; Wed,  9 Sep 2009 12:36:21 -0700 (PDT)
Received: from blu0-omc4-s34.blu0.hotmail.com (blu0-omc4-s34.blu0.hotmail.com [65.55.111.173]) by core3.amsl.com (Postfix) with ESMTP id 1BFAC28C0DD for <emu@ietf.org>; Wed,  9 Sep 2009 12:36:21 -0700 (PDT)
Received: from BLU137-W9 ([65.55.111.137]) by blu0-omc4-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 9 Sep 2009 12:36:54 -0700
Message-ID: <BLU137-W9ADA53CF5798ECFC91A4793E90@phx.gbl>
Content-Type: multipart/alternative; boundary="_99899a5d-a506-4996-934c-f32639c081ab_"
X-Originating-IP: [131.107.0.86]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
Date: Wed, 9 Sep 2009 12:36:54 -0700
Importance: Normal
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE508AF933C@xmb-sjc-225.amer.cisco.com>
References: <BLU137-W4C1E9263CC3A9EDABFB8A93060@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5088B0F51@xmb-sjc-225.amer.cisco.com> <BLU137-W1351F278F8E9D7DB662C7193050@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE5089320CE@xmb-sjc-225.amer.cisco.com> <BLU137-W36DE8884CA39C5ACAB551793FF0@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE508AF918A@xmb-sjc-225.amer.cisco.com> <BLU137-W1CA15DB7FC869C351AC8293E90@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE508AF933C@xmb-sjc-225.amer.cisco.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Sep 2009 19:36:54.0764 (UTC) FILETIME=[E30462C0:01CA3184]
Subject: Re: [Emu] #18 Internationalization of error messages
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 19:36:22 -0000

--_99899a5d-a506-4996-934c-f32639c081ab_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Yes=2C this makes more sense.=20

=20
> Subject: RE: [Emu] #18 Internationalization of error messages
> Date: Tue=2C 8 Sep 2009 19:26:20 -0700
> From: jsalowey@cisco.com
> To: bernard_aboba@hotmail.com=3B emu@ietf.org
>=20
> OK=2C makes sense. How about we make the language tags specific to text
> sent from the server to the peer that is intended to be displayed to a
> user. We can also specifically state that it is also acceptable to send
> numeric codes that can be mapped to a specific representation by the
> client to meet the internationalization requirement. These codes would
> not be internationalized even if they were in ASCII/UTE-8 format.=20
>=20
> Does this make sense?
>=20
> Thanks=2C
>=20
> Joe
>=20
> > -----Original Message-----
> > From: Bernard Aboba [mailto:bernard_aboba@hotmail.com]=20
> > Sent: Tuesday=2C September 08=2C 2009 7:09 PM
> > To: Joseph Salowey (jsalowey)=3B emu@ietf.org
> > Subject: RE: [Emu] #18 Internationalization of error messages
> >=20
> > I don't have a problem with requiring support for UTF-8 in=20
> > usernames and passwords within authentication mechanisms=20
> > native to the tunnel method. However=2C I do have an issue=20
> > with requiring internationalization of error message text.=20
> >=20
> > One of the principles of good protocol design is to *avoid*=20
> > internationalization problems within error messages by use of=20
> > error numbers (e.g. 404 in HTTP and SIP). This makes it=20
> > possible for client software to display localized versions of=20
> > error messages without requiring the server to support=20
> > internationalization.
> >=20
> > If the tunnel protocol incorporates error numbers=2C it should=20
> > therefore not be necessary for the server to send=20
> > internationalized error text.=20
> >=20
> > Adding requirements for internationalization of error text or=20
> > negotiation of language tags for error messages is not only=20
> > unnecessary=2C it is actually enforcing a requirement for a=20
> > *bad design*.=20
> >=20
> >=20
> >=20
> >=20
> >=20
> >=20

--_99899a5d-a506-4996-934c-f32639c081ab_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
</style>
</head>
<body class=3D'hmmessage'>
Yes=2C this makes more sense. <BR>
&nbsp=3B<BR>&gt=3B Subject: RE: [Emu] #18 Internationalization of error mes=
sages<BR>&gt=3B Date: Tue=2C 8 Sep 2009 19:26:20 -0700<BR>&gt=3B From: jsal=
owey@cisco.com<BR>&gt=3B To: bernard_aboba@hotmail.com=3B emu@ietf.org<BR>&=
gt=3B <BR>&gt=3B OK=2C makes sense. How about we make the language tags spe=
cific to text<BR>&gt=3B sent from the server to the peer that is intended t=
o be displayed to a<BR>&gt=3B user. We can also specifically state that it =
is also acceptable to send<BR>&gt=3B numeric codes that can be mapped to a =
specific representation by the<BR>&gt=3B client to meet the internationaliz=
ation requirement. These codes would<BR>&gt=3B not be internationalized eve=
n if they were in ASCII/UTE-8 format. <BR>&gt=3B <BR>&gt=3B Does this make =
sense?<BR>&gt=3B <BR>&gt=3B Thanks=2C<BR>&gt=3B <BR>&gt=3B Joe<BR>&gt=3B <B=
R>&gt=3B &gt=3B -----Original Message-----<BR>&gt=3B &gt=3B From: Bernard A=
boba [mailto:bernard_aboba@hotmail.com] <BR>&gt=3B &gt=3B Sent: Tuesday=2C =
September 08=2C 2009 7:09 PM<BR>&gt=3B &gt=3B To: Joseph Salowey (jsalowey)=
=3B emu@ietf.org<BR>&gt=3B &gt=3B Subject: RE: [Emu] #18 Internationalizati=
on of error messages<BR>&gt=3B &gt=3B <BR>&gt=3B &gt=3B I don't have a prob=
lem with requiring support for UTF-8 in <BR>&gt=3B &gt=3B usernames and pas=
swords within authentication mechanisms <BR>&gt=3B &gt=3B native to the tun=
nel method. However=2C I do have an issue <BR>&gt=3B &gt=3B with requiring =
internationalization of error message text. <BR>&gt=3B &gt=3B <BR>&gt=3B &g=
t=3B One of the principles of good protocol design is to *avoid* <BR>&gt=3B=
 &gt=3B internationalization problems within error messages by use of <BR>&=
gt=3B &gt=3B error numbers (e.g. 404 in HTTP and SIP). This makes it <BR>&g=
t=3B &gt=3B possible for client software to display localized versions of <=
BR>&gt=3B &gt=3B error messages without requiring the server to support <BR=
>&gt=3B &gt=3B internationalization.<BR>&gt=3B &gt=3B <BR>&gt=3B &gt=3B If =
the tunnel protocol incorporates error numbers=2C it should <BR>&gt=3B &gt=
=3B therefore not be necessary for the server to send <BR>&gt=3B &gt=3B int=
ernationalized error text. <BR>&gt=3B &gt=3B <BR>&gt=3B &gt=3B Adding requi=
rements for internationalization of error text or <BR>&gt=3B &gt=3B negotia=
tion of language tags for error messages is not only <BR>&gt=3B &gt=3B unne=
cessary=2C it is actually enforcing a requirement for a <BR>&gt=3B &gt=3B *=
bad design*. <BR>&gt=3B &gt=3B <BR>&gt=3B &gt=3B <BR>&gt=3B &gt=3B <BR>&gt=
=3B &gt=3B <BR>&gt=3B &gt=3B <BR>&gt=3B &gt=3B <BR></body>
</html>=

--_99899a5d-a506-4996-934c-f32639c081ab_--

From khoeper@motorola.com  Fri Sep 11 13:20:30 2009
Return-Path: <khoeper@motorola.com>
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 8C9CA3A697D for <emu@core3.amsl.com>; Fri, 11 Sep 2009 13:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 KfVGWoJgmbMV for <emu@core3.amsl.com>; Fri, 11 Sep 2009 13:20:29 -0700 (PDT)
Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with ESMTP id 258E43A692A for <emu@ietf.org>; Fri, 11 Sep 2009 13:20:29 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: khoeper@motorola.com
X-Msg-Ref: server-3.tower-55.messagelabs.com!1252700465!10495770!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [136.182.1.12]
Received: (qmail 7670 invoked from network); 11 Sep 2009 20:21:06 -0000
Received: from motgate2.mot.com (HELO motgate2.mot.com) (136.182.1.12) by server-3.tower-55.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Sep 2009 20:21:06 -0000
Received: from il27exr04.cig.mot.com (il27exr04.mot.com [10.17.196.73]) by motgate2.mot.com (8.14.3/8.14.3) with ESMTP id n8BKL5lE000747 for <emu@ietf.org>; Fri, 11 Sep 2009 13:21:05 -0700 (MST)
Received: from az10vts04.mot.com (il27vts04.cig.mot.com [10.17.196.88]) by il27exr04.cig.mot.com (8.13.1/Vontu) with SMTP id n8BKL5Rc028007 for <emu@ietf.org>; Fri, 11 Sep 2009 15:21:05 -0500 (CDT)
Received: from de01exm68.ds.mot.com (de01exm68.am.mot.com [10.176.8.24]) by il27exr04.cig.mot.com (8.13.1/8.13.0) with ESMTP id n8BKL5BO028002 for <emu@ietf.org>; Fri, 11 Sep 2009 15:21:05 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Sep 2009 16:20:43 -0400
Message-ID: <3A241A6B234BE948B8B474D261FEBC2F0673769E@de01exm68.ds.mot.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50883CF15@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [Emu] Issue #23: Tunnel Protection requirements
thread-index: AcoW0bmrfo86FVOiSKaD4Oj6uKLQHwAAEzHQBw7E9JA=
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CF15@xmb-sjc-225.amer.cisco.com>
From: "Hoeper Katrin-QWKN37" <khoeper@motorola.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
X-CFilter-Loop: Reflected
Subject: Re: [Emu] Issue #23: Tunnel Protection requirements
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 20:20:30 -0000

Please find my comments and suggested solution inline.

Katrin

PS: Note that NIST DRAFT SP 800-120 and SP 800-57 part 3 both completed
the public call for comments a while ago and can be expected to be
published soon.

> -----Original Message-----
> From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On Behalf Of
> Joseph Salowey (jsalowey)
> Sent: Thursday, August 06, 2009 3:12 PM
> To: emu@ietf.org
> Subject: [Emu] Issue #23: Tunnel Protection requirements
>=20
> #23: Tunnel Protection requirements
>=20
>  > Section 4.2.1.1.2
>  >
>  > "See Part 1 of the NIST Recommendation for
>  >    Key Management [NIST SP 800-57] for a discussion of the relative
>  >    strengths of common algorithms."
>  >
>  > Why not reference the NIST SP 800-120 requirements here?


[KH] This issue talks about Section 4.2.1.1.2 "Tunnel Data Protection
Algorithms". Here it is required that "The tunnel method MUST provide at
least one mandatory to implement cipher suite that provides the
equivalent security of 128-bit AES for encryption and message
authentication."

The reference to NIST SP 800-57 part 3 is meant to help implementers to
determine other cryptographic algorithm with key lengths that correspond
to 128-bit AES security. This NIST recommendation is the correct
reference here because it lists the security strength of crypto
algorithms with particular key lengths.

On the other hand, NIST SP 800-120 (not published yet, but will be soon)
describes security requirements for tunnel protocols, including
requirements for data protection. Note that these requirements are for
Federal networks and it would need to be determined whether these
requirements are reasonable (i.e., not too restrictive) for commercial
networks too.

So either we leave the text as is, i.e. with one example of how to do it
and a reference on how to construct other secure solutions, or we delete
the current text and say that=20
"The tunnel method MUST provide at least one mandatory to implement
cipher suite that meets all security requirements for data protections
of a tunnel protocol in NIST DRAFT Recommendation for EAP Methods Used
in Wireless Network Access Authentication [NIST SP 800-120]."

>  >
>=20
>  > "o One-way key derivation
>  >  o Cryptographically separated keys.
>  >  o Cryptographically separated entities.
>  >  o Identity binding
>  >  o Context binding
>  >  o Key lifetime
>  >  o Mutual implicit key authentication
>  >  o Key freshness"
>  >
>  > Given that this document assumes a TLS-based tunnel method,
>  > the text on requirements can be made considerably more
>  > specific and actionable based on TLS properties and the
>  > specific requirements of NIST 800-120.
>  > As it stands, a number of these requirements either don't
>  > apply to EAP methods at all (e.g. context binding, key
>  > lifetime) but rather to other elements of the system, or are
>  > automatically provided by TLS (e.g. key freshness, Identity
>  > binding).
>  >
>  > So these requirements need to be made actionable and
>  > specific.  The ones that don't apply to the problem at hand
>  > (e.g. TLS-based tunnel euth) should be removed.
>  >
>=20
[KH] This issue addresses Section 4.2.1.1.3. "Tunnel Authentication and
Key Establishment". I agree that the requirements need to be more
specific and some need to be removed altogether.=20

NIST DRAFT Recommendation for Key Management, Part 3 [NIST SP 800-57,
part3] will be published soon and specifically lists secure ciphersuites
for Federal Government Use of TLS v1.0, v1.1 and v1.2, including
conventional public key, elliptic curve and pre-shared key ciphersuites.
These ciphersuite meet strict security requirements.

In NIST DRAFT Recommendation for EAP Methods Used in Wireless Network
Access Authentication [NIST SP 800-120], the requirements for TLS
ciphersuites also refer to NIST SP 800-57, part3. However, in addition
requirements for authentication and key establishments for tunnel
protocols are listed.

I suggest changing the text in Section 4.2.1.1.3 to

"A tunnel method MUST provide unidirectional authentication from
authentication server to EAP peer or mutual authentication between
authentication server and EAP peer.  The tunnel method MUST provide at
least one mandatory to implement cipher suite that provides
certificate-based authentication of the server and provides optional
certificate-based authentication of the client.  Other types of
authentication MAY be supported.

At least one mandatory to implement cipher suite MUST be approved by
NIST DRAFT Recommendation for Key Management, Part 3 [NIST SP 800-57,
part3], i.e., the ciphersuite MUST be listed in Table 4-1, 4-2 or 4-3 in
[NIST SP 800-57, part 3].

The mandatory to implement cipher suites MUST NOT include "export
strength" cipher suites, cipher suites providing mutually anonymous
authentication or static Diffie-Hellman cipher suites. =20

Other ciphersuites MAY be selected following the security requirements
for tunnel protocols in NIST DRAFT Recommendation for EAP Methods Used
in Wireless Network Access Authentication [NIST SP 800-120]."


> --
> Ticket URL: <http://trac.tools.ietf.org/wg/emu/trac/ticket/23>
> emu <http://tools.ietf.org/wg/emu/>
>=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu

From david@mitton.com  Tue Sep 22 14:26:41 2009
Return-Path: <david@mitton.com>
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 956DE3A681B for <emu@core3.amsl.com>; Tue, 22 Sep 2009 14:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.055
X-Spam-Level: *
X-Spam-Status: No, score=1.055 tagged_above=-999 required=5 tests=[AWL=-1.857,  BAYES_20=-0.74, FRT_LEVITRA=1.812, J_CHICKENPOX_31=0.6, SARE_LWSHORTT=1.24]
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 ulopyNCopuGU for <emu@core3.amsl.com>; Tue, 22 Sep 2009 14:26:40 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0217.hostedemail.com [216.40.44.217]) by core3.amsl.com (Postfix) with ESMTP id 126963A6452 for <emu@ietf.org>; Tue, 22 Sep 2009 14:26:36 -0700 (PDT)
Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay02.hostedemail.com (Postfix) with SMTP id 9A2C918788D6 for <emu@ietf.org>; Tue, 22 Sep 2009 21:27:39 +0000 (UTC)
X-Session-Marker: 6461766964406D6974746F6E2E636F6D
X-Filterd-Recvd-Size: 11296
Received: from webmail09 (imap-ext [216.40.42.5]) (Authenticated sender: david@mitton.com) by omf04.hostedemail.com (Postfix) with ESMTP for <emu@ietf.org>; Tue, 22 Sep 2009 21:27:38 +0000 (UTC)
Received: from 128.221.197.54 ([128.221.197.54]) by webmail09 (Tucows Webmail) with HTTP; Tue, 22 Sep 2009 21:27:38 +0000 (GMT)
Date: Tue, 22 Sep 2009 21:27:38 +0000 (GMT)
From: David Mitton <david@mitton.com>
To: emu@ietf.org
Message-ID: <119511687.149944.1253654858415.JavaMail.mail@webmail09>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [128.221.197.54]
Subject: [Emu] Notes from the Interactive EAP implementation front
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: david@mitton.com
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/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Sep 2009 21:26:41 -0000

Over the previous year, I was the Project Leader for a Windows Vista implem=
entation of the RSA SecurID OTP EAP methods (15  & 32 - Protected OTP).   D=
uring this project we had a number of setbacks, and I achieved a new enligh=
tenment about where some long suffering problems with our user interactive =
EAP methods actually come from.

The primary goal of this project was to port our XP client to Vista and use=
 the new Windows EAP API, EAPHost.
The first problem we found is that Vista EAPHost doesn't support RAS connec=
tions (PPP and VPN), only 802.1X connections. This has been "fixed" in Wind=
ows 7.   However, we needed to support those connection methods, and we she=
lved the EAPHost version in favor of upgrading the existing RasEap API impl=
ementation (which all Microsoft methods use anyways).

A major problem we have run into with SecurID EAP is timeouts by access poi=
nts during the authentication process.
As I've discussed before (http://www.ietf.org/proceedings/66/slides/emu-4/s=
ld1.htm) some access point implementations have a very short timer on EAP a=
uthentication turnaround.

A typical SecurID token generates a new One Time Password (OTP) value once =
every minute.  A row of indicators indicates where the token is in the cycl=
e, and some users prefer to wait for a new token code, instead of starting =
to make an entry and having it change before they are done.   Furthermore, =
if the user is more than 3 minutes out of sync with the server, they may al=
so have to wait for a second code and enter it.   This leads to user input =
times on the order of a minute easy to possibly 3 minutes total.   Independ=
ently, the system Admin may also force a PIN code change, (similar to a pas=
sword change) and this process needs PIN input as well as another token val=
ue, before authentication is granted.


Given our experience, both of our EAP methods have designed-in protocol mes=
sages to generate EAP keep-alive traffic while the user interacting with th=
eir token.  Our next major problem was that Windows Vista changed the way t=
hat EAP user interfaces were supported, and our implementation that support=
ed this was utterly broken.


In order to both display a dialog to the user, and send network keep-alive =
messages, we had to get two things going at once.  This is not trivially po=
ssible inside the Windows EAP environment as most of the code is of a singl=
e-threaded callback and return nature.  Our XP client would create an extra=
 thread in the EAP UI environment, and support the user dialog from there. =
 When a keep-alive message was needed, it would return to the network code =
to send it.  And when the response returned, it would call back to the UI h=
ost code, which was still running in the same multithreaded server process,=
 and re-establish a shared context.

Vista broke this by moving the UI host environment to a single threaded COM=
 apartment, and terminates the entire process when it returns status to the=
 network component.

I first tried to just end around the Windows EAP UI and invoke my own UI pr=
ocess.  At first that worked just fine, until I let 60 seconds go by.   The=
n the session was shutdown by the Windows 802.1X state machine.  This is no=
t even an inactivity timer.  It would kill the session after one minute eve=
n if it had just seconds before sent a response to the server.=20

Further tracing and an open support ticket revealed that the Windows 802.1X=
 state machine would not let an authentication stay open for longer than 1 =
minute unless it had a UI active.  If I had a UI active, it would allow 5 p=
eriods.  I asked, but was not offered any interfaces that could manipulate =
this timer or alter it's sense of the UI state.  Microsoft's recommendation=
 was to re-build our XP solution but using external processes instead of mu=
lti-threading their new UI infrastructure.

I ended up implementing a separate UI service process that ran the input di=
alogs.  This process was started from the EAP UI context when an authentica=
tion began, and would be contacted every keep-alive cycle, until the user i=
nput was complete.  Debugging the interprocess communication and state mach=
ines took a little bit more time.


While I was trying to understand the issues involved in the client, I start=
ed experimenting with alternate approaches in the server.  The RasEap API o=
ffers two transmit message calls to the EAP server (sorry - Authenticator);=
 one EAPACTION_SendWithTimeoutInteractive which was what the code was using=
 or EAPACTION_SendWithTimeout, which might have offered a way for the serve=
r to catch a timeout and act on it.  To get more information I sent Microso=
ft a support request to explain the differences between the two.   The answ=
er I got was that EAPACTION_SendWithTimeoutInteractive had a 30 second time=
out, and EAPACTION_SendWithTimeout had a 60 second timeout.  What I was loo=
king for was any way the server could catch the timeout and resend the prev=
ious message.   I noticed that the code to do that was there, but the event=
 never happened.

So, I tried the SendWithTimeout to see if an extra 30 seconds would get me =
some more breathing room.  Instead the authentication failed immediately.  =
 I finally busted out Kismet and Wireshark to find out WTF was going on.
I wanted to know how an internal EAP server call was affecting the client E=
APOL AP authentication in the air.

I discovered that the Windows IAS server was using the API action code to s=
et a Session-Timeout value in the RADIUS message carrying the EAP request m=
essage.  For the SendWithTimeoutInteractive it was setting the value to 30.=
  For the SendWithTimeout it was setting it to 6, not 60 as I had been told=
. =20

Furthermore, the access point I use, the Cisco Aironet 1230 [v12.3(8)JEC2] =
would take those timeout values and treat them as a session expiration time=
r, instead of a re-transmit timer.  If a message wasn't received in that pe=
riod, it would abort the authentication.   I do not think this is what is i=
ntended by RFC 3580, sect 3.17, page 11:

   When sent in an Access-Challenge, this attribute represents the
   maximum number of seconds that an IEEE 802.1X Authenticator should
   wait for an EAP-Response before retransmitting. =20

Hunting around for an explanation of 1200 AP behavior was difficult to find=
.  At one time I found a Meetinghouse website that mentioned that you incre=
ase the "Session timeout" for interactive protocols, but that disappeared. =
  And on my AP's management GUI for this particular parameter does not show=
 on that page.   I was finally able to locate in a Cisco command reference =
that recent versions of IOS that lets you extend the timeout default to a m=
ax of 120 seconds and (on some platforms) allow it to ignore the RADIUS  Se=
ssion-Timeout value.

  dox1x timeout supp-response 120 local

This command doesn't seem to have a GUI equivalent on my AP.

120 seconds, 2 minutes, is not as much as I would like, but this is only fo=
r one EAP message request/response.  Normally a user won't take that long f=
or one step of the authentication.  I still don't know why it doesn't retra=
nsmit, or if it can at all.  The 802.1X specs are extremely vague as to wha=
t the values in this area should be, but it seems that retransmission would=
 be highly desirable for better reliability while authenticating.


Eventually we were able to put the whole thing together.  There are Release=
 Notes that discuss the issues and parameters that allow you to tune it as =
desired.   Our new EAP UI process can ride out the keep-alive cycles in it'=
s own execution context and it tries to keep the MS dialog transitions happ=
y by generating clicks on the annoying =E2=80=9Ca response is required=E2=
=80=9D dialogs or balloons.   An extra feature is a short term username/ide=
ntity cache to allow a quick and silent IdentityResponse if the first didn'=
t get the session started.

I am now testing this on Windows 7, and have only found one EAP interface p=
roblem to date.


Design/Architecture problems I see:

- Windows 802.1X has a fixed timeout (5x60s),  there really should be some =
sort of override on a per-method basis somewhere.  A one size fits all time=
r seems rather presumptuous.

- The timeout should be sensitive to activity (or progress), not just time =
or UI state.
Our worse case authentication could have both a PIN change and a Token resy=
nc which would require 3 token codes (3 minutes) not including user typing =
and reaction time.

- The Windows EAP infrastructure doesn't easily support methods that need t=
o do two things at once.
It would be useful to queue events or wake up threads based on timers.

- Access Points (Cisco in this case) should not be setting short timers for=
 user interactive methods.
Human input really requires timeouts on the order of several minutes.

- Why is the AP killing sessions instead of retransmitting?

- Does any AP retransmit?  Why not?  It's in the 802.1X state machine.
The MS PPTP tunnel server does it frequently and my code tolerates it well.

- Note that given the AP behavior, if the RADIUS Server gave the EAP method=
 authenticator a timeout event (which I've yet to observe), for a potential=
 retransmission, the AP would not accept the message, because it's using th=
e value for a different purpose. =20

Another potential way to solve the keep-alive problem would have been for t=
he client to use a retransmitted request (and the network context thread th=
at receives and processes it) as a way to send a keep-alive message.   But =
given the AP and RADIUS behavior, I was not able to follow that path.


Dave Mitton,
RSA Security, Division of EMC
Bedford, MA


PS: I forgot about the EAP Notification message bug in Vista.   If you use =
the EapRas API method, wireless EAP Notification messages you might receive=
 are discarded silently and without a response to the authenticator. (for s=
ome reason RAS EAP connections actually give you the message and let you re=
spond)  If you have a server that sends Notification messages, your protoco=
l will break at this point. On XP even if the wireless method didn't receiv=
e the message, the underlying code would send a response.  There is now a p=
atch for this KB967802. Evidently EAPHost will let you get your message.

From jsalowey@cisco.com  Tue Sep 22 15:39:51 2009
Return-Path: <jsalowey@cisco.com>
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 B56F53A67A3 for <emu@core3.amsl.com>; Tue, 22 Sep 2009 15:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level: 
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 eZc-NsNE4he3 for <emu@core3.amsl.com>; Tue, 22 Sep 2009 15:39:48 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 9EA2E3A6800 for <emu@ietf.org>; Tue, 22 Sep 2009 15:39:48 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAOPuuEqrR7MV/2dsb2JhbAC+GohPAZAfBYIugW2BXQ
X-IronPort-AV: E=Sophos;i="4.44,433,1249257600"; d="scan'208";a="393989924"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 22 Sep 2009 22:40:46 +0000
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 n8MMekN3024601;  Tue, 22 Sep 2009 15:40:46 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n8MMefQf005135; Tue, 22 Sep 2009 22:40:46 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.3959);  Tue, 22 Sep 2009 15:40:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Sep 2009 15:40:37 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508C62DE8@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <3A241A6B234BE948B8B474D261FEBC2F0673769E@de01exm68.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Issue #23: Tunnel Protection requirements
Thread-Index: AcoW0bmrfo86FVOiSKaD4Oj6uKLQHwAAEzHQBw7E9JACMdI4AA==
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CF15@xmb-sjc-225.amer.cisco.com> <3A241A6B234BE948B8B474D261FEBC2F0673769E@de01exm68.ds.mot.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Hoeper Katrin-QWKN37" <khoeper@motorola.com>, <emu@ietf.org>
X-OriginalArrivalTime: 22 Sep 2009 22:40:38.0915 (UTC) FILETIME=[B54B1530:01CA3BD5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6408; t=1253659246; x=1254523246; 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:=20RE=3A=20[Emu]=20Issue=20#23=3A=20Tunnel=20Prote ction=20requirements |Sender:=20; bh=Nu49mQm6QYNS5ljMHv5cPZ1PUCQq8E3g0Dk11Zw0RQo=; b=YeSS1MVJWjZXxtEfYsiE2RV/BFCT7yt0lzNYwQrIvqK8lkzcL8j953QJ6e 3CygqFdk49V6y0BmOD8xF8c+Fl7Cq0tpwhwn1YZsx6cgSecunIF+rQUFaXvB y1XqmIwjvrALL5rfNgPIHxzreE1RWkujfxAJFsAfAI+GK65y3CDxI=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [Emu] Issue #23: Tunnel Protection requirements
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/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Sep 2009 22:39:51 -0000

Thanks Katrin,

I propose we leave section 4.2.1.1.2 as is and adopt the supplied text
to replace 4.2.1.1.3 (keeping the change from issue 22). =20

Cheers,

Joe=20

> -----Original Message-----
> From: Hoeper Katrin-QWKN37 [mailto:khoeper@motorola.com]=20
> Sent: Friday, September 11, 2009 1:21 PM
> To: Joseph Salowey (jsalowey); emu@ietf.org
> Subject: RE: [Emu] Issue #23: Tunnel Protection requirements
>=20
> Please find my comments and suggested solution inline.
>=20
> Katrin
>=20
> PS: Note that NIST DRAFT SP 800-120 and SP 800-57 part 3 both=20
> completed the public call for comments a while ago and can be=20
> expected to be published soon.
>=20
> > -----Original Message-----
> > From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of=20
> > Joseph Salowey (jsalowey)
> > Sent: Thursday, August 06, 2009 3:12 PM
> > To: emu@ietf.org
> > Subject: [Emu] Issue #23: Tunnel Protection requirements
> >=20
> > #23: Tunnel Protection requirements
> >=20
> >  > Section 4.2.1.1.2
> >  >
> >  > "See Part 1 of the NIST Recommendation for
> >  >    Key Management [NIST SP 800-57] for a discussion of=20
> the relative
> >  >    strengths of common algorithms."
> >  >
> >  > Why not reference the NIST SP 800-120 requirements here?
>=20
>=20
> [KH] This issue talks about Section 4.2.1.1.2 "Tunnel Data=20
> Protection Algorithms". Here it is required that "The tunnel=20
> method MUST provide at least one mandatory to implement=20
> cipher suite that provides the equivalent security of 128-bit=20
> AES for encryption and message authentication."
>=20
> The reference to NIST SP 800-57 part 3 is meant to help=20
> implementers to determine other cryptographic algorithm with=20
> key lengths that correspond to 128-bit AES security. This=20
> NIST recommendation is the correct reference here because it=20
> lists the security strength of crypto algorithms with=20
> particular key lengths.
>=20
> On the other hand, NIST SP 800-120 (not published yet, but=20
> will be soon) describes security requirements for tunnel=20
> protocols, including requirements for data protection. Note=20
> that these requirements are for Federal networks and it would=20
> need to be determined whether these requirements are=20
> reasonable (i.e., not too restrictive) for commercial networks too.
>=20
> So either we leave the text as is, i.e. with one example of=20
> how to do it and a reference on how to construct other secure=20
> solutions, or we delete the current text and say that "The=20
> tunnel method MUST provide at least one mandatory to=20
> implement cipher suite that meets all security requirements=20
> for data protections of a tunnel protocol in NIST DRAFT=20
> Recommendation for EAP Methods Used in Wireless Network=20
> Access Authentication [NIST SP 800-120]."
>=20
> >  >
> >=20
> >  > "o One-way key derivation
> >  >  o Cryptographically separated keys.
> >  >  o Cryptographically separated entities.
> >  >  o Identity binding
> >  >  o Context binding
> >  >  o Key lifetime
> >  >  o Mutual implicit key authentication  >  o Key freshness"
> >  >
> >  > Given that this document assumes a TLS-based tunnel=20
> method,  > the=20
> > text on requirements can be made considerably more  > specific and=20
> > actionable based on TLS properties and the  > specific=20
> requirements of=20
> > NIST 800-120.
> >  > As it stands, a number of these requirements either=20
> don't  > apply=20
> > to EAP methods at all (e.g. context binding, key  > lifetime) but=20
> > rather to other elements of the system, or are  > automatically=20
> > provided by TLS (e.g. key freshness, Identity  > binding).
> >  >
> >  > So these requirements need to be made actionable and  >=20
> specific. =20
> > The ones that don't apply to the problem at hand  > (e.g. TLS-based=20
> > tunnel euth) should be removed.
> >  >
> >=20
> [KH] This issue addresses Section 4.2.1.1.3. "Tunnel=20
> Authentication and Key Establishment". I agree that the=20
> requirements need to be more specific and some need to be=20
> removed altogether.=20
>=20
> NIST DRAFT Recommendation for Key Management, Part 3 [NIST SP=20
> 800-57, part3] will be published soon and specifically lists=20
> secure ciphersuites for Federal Government Use of TLS v1.0,=20
> v1.1 and v1.2, including conventional public key, elliptic=20
> curve and pre-shared key ciphersuites.
> These ciphersuite meet strict security requirements.
>=20
> In NIST DRAFT Recommendation for EAP Methods Used in Wireless=20
> Network Access Authentication [NIST SP 800-120], the=20
> requirements for TLS ciphersuites also refer to NIST SP=20
> 800-57, part3. However, in addition requirements for=20
> authentication and key establishments for tunnel protocols are listed.
>=20
> I suggest changing the text in Section 4.2.1.1.3 to
>=20
> "A tunnel method MUST provide unidirectional authentication=20
> from authentication server to EAP peer or mutual=20
> authentication between authentication server and EAP peer. =20
> The tunnel method MUST provide at least one mandatory to=20
> implement cipher suite that provides certificate-based=20
> authentication of the server and provides optional=20
> certificate-based authentication of the client.  Other types=20
> of authentication MAY be supported.
>=20
> At least one mandatory to implement cipher suite MUST be=20
> approved by NIST DRAFT Recommendation for Key Management,=20
> Part 3 [NIST SP 800-57, part3], i.e., the ciphersuite MUST be=20
> listed in Table 4-1, 4-2 or 4-3 in [NIST SP 800-57, part 3].
>=20
> The mandatory to implement cipher suites MUST NOT include=20
> "export strength" cipher suites, cipher suites providing=20
> mutually anonymous authentication or static Diffie-Hellman=20
> cipher suites. =20
>=20
> Other ciphersuites MAY be selected following the security=20
> requirements for tunnel protocols in NIST DRAFT=20
> Recommendation for EAP Methods Used in Wireless Network=20
> Access Authentication [NIST SP 800-120]."
>=20
>=20
> > --
> > Ticket URL: <http://trac.tools.ietf.org/wg/emu/trac/ticket/23>
> > emu <http://tools.ietf.org/wg/emu/>
> >=20
> > _______________________________________________
> > Emu mailing list
> > Emu@ietf.org
> > https://www.ietf.org/mailman/listinfo/emu
>=20

From jsalowey@cisco.com  Tue Sep 22 15:52:08 2009
Return-Path: <jsalowey@cisco.com>
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 45BEE3A659C for <emu@core3.amsl.com>; Tue, 22 Sep 2009 15:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level: 
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 hRARgVNjRx1s for <emu@core3.amsl.com>; Tue, 22 Sep 2009 15:52:07 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 2D7023A683D for <emu@ietf.org>; Tue, 22 Sep 2009 15:52:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAGfyuEqrR7O6/2dsb2JhbAC9e4hPATaPZgWCTIFP
X-IronPort-AV: E=Sophos;i="4.44,433,1249257600"; d="scan'208";a="393997290"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 22 Sep 2009 22:53:11 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n8MMrBC0025326 for <emu@ietf.org>; Tue, 22 Sep 2009 15:53:11 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n8MMrBnC014928 for <emu@ietf.org>; Tue, 22 Sep 2009 22:53:11 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.3959);  Tue, 22 Sep 2009 15:53:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Sep 2009 15:53:09 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508C62E0C@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50883CEF1@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Issue #20: Method Meta-Data
Thread-Index: AcoWzxG4GdSmFqmjRFqXehvVx1UUbAAAB7WwCUIL4QA=
References: <AC1CFD94F59A264488DC2BEC3E890DE50883CEF1@xmb-sjc-225.amer.cisco.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, <emu@ietf.org>
X-OriginalArrivalTime: 22 Sep 2009 22:53:11.0735 (UTC) FILETIME=[76024C70:01CA3BD7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2162; t=1253659991; x=1254523991; 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]=20Issue=20#20=3A=20Method=20Meta- Data |Sender:=20; bh=7GuZWRyakqPdD3vn0qnspOmuUgS+iCe3Ceq2dldul5w=; b=LJF/6QxOdpRAc7ltmw0L6QVIi+Re0FS+O3KhfmjhoHRJK8tfmIVSwNJcTj AovxuZI1CcxbljiUizLqfxDWycJGsuPG43ofjALAwd7zLnpa09mkx7z+SoeC rYfJcns7L+;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [Emu] Issue #20: Method Meta-Data
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/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Sep 2009 22:52:08 -0000

Any objection to resolving this by changing the MUSTs to SHOULDs?

Thanks,

Joe=20

> -----Original Message-----
> From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of Joseph Salowey (jsalowey)
> Sent: Thursday, August 06, 2009 12:51 PM
> To: emu@ietf.org
> Subject: [Emu] Issue #20: Method Meta-Data
>=20
>=20
> #20: Method Meta-Data
>=20
>  > Section 4.5.3
>  >
>  > "   The password authentication exchange MUST support additional
>  >    associated meta-data which can be used to indicate whether the
>  >    authentication is for a user or a machine.  This allows the EAP
>  >    server and peer to request and negotiate authentication
>  > specifically
>  >    for a user or machine.  This is useful in the case of
>  > multiple inner
>  >    authentications where the user and machine both need to be
>  >    authenticated.
>  > "
>  > Why is it necessary to support meta-data to indicate=20
> whether  > authentication is for a user or machine?  Few=20
> authentication  > protocols support this today and don't seem=20
> to miss it.  For  > example, does Kerberos or PKI distinguish=20
> explicitly between  > user and machine credentials?
>  >
>=20
>  and
>=20
>  > Section 4.6.5
>  >
>  > "   The tunnel method MUST allow for the communication of
>  > additional data
>  >    associated with an EAP method.  This can be used to
>  > indicate whether
>  >    the authentication is for a user or a machine.  This allows the
> EAP
>  >    server and peer to request and negotiate authentication
>  > specifically
>  >    for a user or machine.  This is useful in the case of
>  > multiple inner
>  >    EAP authentications where the user and machine both need to be
>  >    authenticated.
>  > "
>  > Again, why is meta-data necessary?  Can't the basic need=20
> for  > machine + user auth be met without this?
>  >
>=20
> --
> Ticket URL: <http://wiki.tools.ietf.org/wg/emu/trac/ticket/20>
> emu <http://tools.ietf.org/wg/emu/>
>=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>=20

From jsalowey@cisco.com  Tue Sep 22 16:21:31 2009
Return-Path: <jsalowey@cisco.com>
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 18D523A6879 for <emu@core3.amsl.com>; Tue, 22 Sep 2009 16:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level: 
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 uEQ10vejWIbZ for <emu@core3.amsl.com>; Tue, 22 Sep 2009 16:21:30 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 4AE073A67ED for <emu@ietf.org>; Tue, 22 Sep 2009 16:21:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAPf4uEqrR7PD/2dsb2JhbAC9a4hPATMDBI9cBYJIBAiBRw
X-IronPort-AV: E=Sophos;i="4.44,433,1249257600"; d="scan'208";a="245468727"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 22 Sep 2009 23:18:14 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n8MNIE43014128 for <emu@ietf.org>; Tue, 22 Sep 2009 16:18:14 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n8MNIELu025451 for <emu@ietf.org>; Tue, 22 Sep 2009 23:18:14 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.3959);  Tue, 22 Sep 2009 16:18:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Sep 2009 16:18:11 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revised sections for  Issue #18 (Internationalization)
Thread-Index: Aco72vQMMEAbRjKBTzilU6TDAxPZuQ==
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: <emu@ietf.org>
X-OriginalArrivalTime: 22 Sep 2009 23:18:14.0412 (UTC) FILETIME=[F5AC9CC0:01CA3BDA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1718; t=1253661494; x=1254525494; c=relaxed/simple; s=sjdkim3002; 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:=20Revised=20sections=20for=20=20Issue=20#18=20(In ternationalization) |Sender:=20; bh=B7eNQUGJ0AOoyUwoXh9dhZGkaFUy6tHbyC85uul0Cp0=; b=X7YmhOpzJq6qEx2SS7VZX2wF8nxjAU+YhPYhic52/s19aqoHfjPW1vtBY/ 68sgNi5aisrglBoyhC7bqKm2qJLZhvEc6t+EVGL5z3vhsNS45x7mtRA1dFqT yLhGJF0D/c;
Authentication-Results: sj-dkim-3; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Sep 2009 23:21:31 -0000

"4.3.6. Internationalization of Display Strings


The payload MAY provide a standard attribute format that supports
international strings.  This attribute format MUST support encoding
strings in UTF-8 [RFC3629] format.  Any strings sent by the server
intended for display to the user MUST be sent in UTF-8 format and
SHOULD be able to be marked with language information and adapted to
the user's language preference as indicated by RFC 4646 [RFC4646]. =20
Note that in some cases, such as when transmitting error codes, it=20
is acceptable to exchange numeric codes that can be translated by the=20
client to support the particular local language.  These numeric codes
are not subject internationalization during transmission. "

"4.5.2. Internationalization


   The password authentication exchange MUST support user names and
   passwords in international languages.  It MUST support encoding of
   user name and password strings in UTF-8 [RFC3629] format. The method=20
   MUST specify how username and password normalization is performed in=20
   reference to SASLPrep [RFC4013] or Net-UTF-8 [RFC5198].

   Any strings sent by the server during the password exchange and
intended
   for display to the user MUST be sent in UTF-8 format and SHOULD be
   able to be marked with language information and adapted to the user's
   language preference as indicated by RFC 4646 [RFC4646].  Note that in
some=20
   cases, such as when transmitting error codes, it is acceptable to
exchange=20
   numeric codes that can be translated by the client to support the=20
   particular local language.  These numeric codes are not subject=20
   internationalization during transmission. "

From simon@josefsson.org  Wed Sep 23 01:48:21 2009
Return-Path: <simon@josefsson.org>
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 614673A62C1 for <emu@core3.amsl.com>; Wed, 23 Sep 2009 01:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599]
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 wzSgku77tGIX for <emu@core3.amsl.com>; Wed, 23 Sep 2009 01:48:20 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 0CB283A67E6 for <emu@ietf.org>; Wed, 23 Sep 2009 01:48:18 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8N8ms1H019414 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 23 Sep 2009 10:48:57 +0200
From: Simon Josefsson <simon@josefsson.org>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090923:emu@ietf.org::LYuzf0TA8sf+hX2r:1AGy
X-Hashcash: 1:22:090923:jsalowey@cisco.com::wiJKBlED4QMsx7Dw:JOlO
Date: Wed, 23 Sep 2009 10:48:54 +0200
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> (Joseph Salowey's message of "Tue, 22 Sep 2009 16:18:11 -0700")
Message-ID: <877hvqavwp.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Sep 2009 08:48:21 -0000

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> writes:

> "4.3.6. Internationalization of Display Strings
>
>
> The payload MAY provide a standard attribute format that supports
> international strings.  This attribute format MUST support encoding
> strings in UTF-8 [RFC3629] format.  Any strings sent by the server
> intended for display to the user MUST be sent in UTF-8 format and
> SHOULD be able to be marked with language information and adapted to
> the user's language preference as indicated by RFC 4646 [RFC4646].  
> Note that in some cases, such as when transmitting error codes, it 
> is acceptable to exchange numeric codes that can be translated by the 
> client to support the particular local language.  These numeric codes
> are not subject internationalization during transmission. "
>
> "4.5.2. Internationalization
>
>
>    The password authentication exchange MUST support user names and
>    passwords in international languages.  It MUST support encoding of
>    user name and password strings in UTF-8 [RFC3629] format. The method 
>    MUST specify how username and password normalization is performed in 
>    reference to SASLPrep [RFC4013] or Net-UTF-8 [RFC5198].

There is some discussion about SASLprep on the ietf@ietf.org mailing
list right now that you may want to review.

One of my experiences with SASLprep is that it makes sense to normalize
passwords (because they are input to hashes so some ambiguities needs to
be resolved) but it does not always make sense to normalize usernames.
Some characters that may occur in a username are converted to other
characters by SASLprep, a simple example is SASLprep('ª') = 'a.'  So
using SASLprep for usernames may prevent otherwise reasonable usernames
from being usable.

Another concern with SASLprep is that it is based on Unicode 3.2 and
does not support newer Unicode versions.

Perhaps you want to consider an approach where passwords are normalized
using Net-UTF-8 and usernames are sent as-is but mandate that
username-to-username comparisons use Net-UTF-8 on both strings before
comparing them.

Username and passwords strings are somewhat different beasts, and it
does not necessarily make sense to use the same normalization or
comparison algorithms for both strings.

/Simon

>    Any strings sent by the server during the password exchange and
> intended
>    for display to the user MUST be sent in UTF-8 format and SHOULD be
>    able to be marked with language information and adapted to the user's
>    language preference as indicated by RFC 4646 [RFC4646].  Note that in
> some 
>    cases, such as when transmitting error codes, it is acceptable to
> exchange 
>    numeric codes that can be translated by the client to support the 
>    particular local language.  These numeric codes are not subject 
>    internationalization during transmission. "

From aland@deployingradius.com  Wed Sep 23 06:27:36 2009
Return-Path: <aland@deployingradius.com>
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 3A9BB28C11C for <emu@core3.amsl.com>; Wed, 23 Sep 2009 06:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.946
X-Spam-Level: 
X-Spam-Status: No, score=-1.946 tagged_above=-999 required=5 tests=[AWL=0.653,  BAYES_00=-2.599]
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 YuwsCeewFQt3 for <emu@core3.amsl.com>; Wed, 23 Sep 2009 06:27:35 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 3F6EF3A67B3 for <emu@ietf.org>; Wed, 23 Sep 2009 06:27:32 -0700 (PDT)
Received: from Thor.local (mey38-2-82-228-181-7.fbx.proxad.net [82.228.181.7]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 88C561234491; Wed, 23 Sep 2009 15:26:06 +0200 (CEST)
Message-ID: <4ABA2282.4080207@deployingradius.com>
Date: Wed, 23 Sep 2009 15:28:34 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> <877hvqavwp.fsf@mocca.josefsson.org>
In-Reply-To: <877hvqavwp.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Sep 2009 13:27:36 -0000

Simon Josefsson wrote:
> Perhaps you want to consider an approach where passwords are normalized
> using Net-UTF-8 and usernames are sent as-is but mandate that
> username-to-username comparisons use Net-UTF-8 on both strings before
> comparing them.

  I would like to see some more details around this suggestion.  Issues
of data entry (user -> keyboard -> ?? -> EAP) and user store (admin ->
keyboard -> ??? -> database) are important.

  Something like:

The canonical form of the username and password as carried in EAP or
placed in an authentication store SHOULD be Net-UTF-8.

  In practice, this means that the supplicant converts both to Net-UTF-8
prior to placing them in an EAP packet.  It means that an authentication
system converts them to Net-UTF-8 prior to placing them in a data store.
 It means that the data store treats them as an opaque sequence of
bytes, and does *not* mangle them in any way.  It means that any
cryptographic calculations based on the passwords must be done on the
Net-UTF-8 form.

  i.e. whatever a supplicant places in the packet is considered by the
authenticator to be the "canonical" form of the username and password.

  Having the authenticator canonicalize the username or password that is
takes from an EAP packet is a recipe for disaster.

> Username and passwords strings are somewhat different beasts, and it
> does not necessarily make sense to use the same normalization or
> comparison algorithms for both strings.

  Why not?  memcmp(s1, s2, length) would be fine if we assume that the
strings are both canonicalized *before* the comparison is done.  Stating
*who* does the canonicalization ensures that only a limited number of
entities do the canonicalization, which minimizes errors and
inter-operability.

  The nice thing about that requirement is that it is very compatible
with sites choosing to not use Net-UTF-8.  If they choose to put
something else in a DB as the authentication credentials, it will work
so long as the supplicant puts exactly the same data into the EAP packet.

  Alan DeKok.

From simon@josefsson.org  Wed Sep 23 07:16:54 2009
Return-Path: <simon@josefsson.org>
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 2AB4B3A69D0 for <emu@core3.amsl.com>; Wed, 23 Sep 2009 07:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599]
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 iR7uDmFtPXYl for <emu@core3.amsl.com>; Wed, 23 Sep 2009 07:16:53 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 9EF0E3A6835 for <emu@ietf.org>; Wed, 23 Sep 2009 07:16:51 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8NEHlti029440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 23 Sep 2009 16:17:51 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Alan DeKok <aland@deployingradius.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> <877hvqavwp.fsf@mocca.josefsson.org> <4ABA2282.4080207@deployingradius.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090923:aland@deployingradius.com::7ChtDeElFw8tjjAO:5zWP
X-Hashcash: 1:22:090923:emu@ietf.org::Zr9dMoCIOP91dy68:Y+cj
Date: Wed, 23 Sep 2009 16:17:46 +0200
In-Reply-To: <4ABA2282.4080207@deployingradius.com> (Alan DeKok's message of "Wed, 23 Sep 2009 15:28:34 +0200")
Message-ID: <87r5txu4mt.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Sep 2009 14:16:54 -0000

Alan DeKok <aland@deployingradius.com> writes:

> Simon Josefsson wrote:
>> Perhaps you want to consider an approach where passwords are normalized
>> using Net-UTF-8 and usernames are sent as-is but mandate that
>> username-to-username comparisons use Net-UTF-8 on both strings before
>> comparing them.
>
>   I would like to see some more details around this suggestion.  Issues
> of data entry (user -> keyboard -> ?? -> EAP) and user store (admin ->
> keyboard -> ??? -> database) are important.

Yes, more details are definitely needed.

>   Something like:
>
> The canonical form of the username and password as carried in EAP or
> placed in an authentication store SHOULD be Net-UTF-8.

Should we suggest that passwords are sent over the wire at all?  In good
systems that should be the exception.  I think there are three different
kind of strings that needs to be discussed.

1) Usernames.  Should be sent over the wire as-is, or possibly
Net-UTF-8.  It is not clear to me that the even the weak NFC part of
Net-UTF-8 is always a good idea for usernames, you could just send the
username as-is and require that COMPARISONS are done in a way that
reduces ambitious.  There are some indication that the algorithm of
comparing two strings for equality is simpler to make robust and
ambigious-free than an algorithm that normalize strings.

2) Passwords sent to servers.  This has similar properties as 1) but
there could be differences in how they are treated.

3) Passwords sent to servers only in hashed form.  This has stricter
normalization requirements than 1) and 2) -- NFC is most certainly
needed, and probably something more, similar to SASLprep but preferably
without some of the problems that SASLprep has.

>> Username and passwords strings are somewhat different beasts, and it
>> does not necessarily make sense to use the same normalization or
>> comparison algorithms for both strings.
>
>   Why not?  memcmp(s1, s2, length) would be fine if we assume that the
> strings are both canonicalized *before* the comparison is done.  Stating
> *who* does the canonicalization ensures that only a limited number of
> entities do the canonicalization, which minimizes errors and
> inter-operability.

The problem with normalization early is that you end up with a interop
problem where both the client and server needs to implement the exact
same normalization algorithms for things to be robust.  If normalization
only happens in one implementation, things will be predictable.

Of course, it is not possible to avoid this problem for hashed password
strings.  They need to be normalized before hashing happens, on all
systems.

>   The nice thing about that requirement is that it is very compatible
> with sites choosing to not use Net-UTF-8.  If they choose to put
> something else in a DB as the authentication credentials, it will work
> so long as the supplicant puts exactly the same data into the EAP packet.

Right, it is a tradeoff between different neat properties.  I'm not sure
we have a good understanding of all the factors that are important yet.

/Simon

From khoeper@motorola.com  Wed Sep 23 11:48:15 2009
Return-Path: <khoeper@motorola.com>
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 067193A6A40; Wed, 23 Sep 2009 11:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 Pcyy70WHrV9f; Wed, 23 Sep 2009 11:48:14 -0700 (PDT)
Received: from mail153.messagelabs.com (mail153.messagelabs.com [216.82.253.51]) by core3.amsl.com (Postfix) with ESMTP id E77BB3A69D3; Wed, 23 Sep 2009 11:48:13 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: khoeper@motorola.com
X-Msg-Ref: server-11.tower-153.messagelabs.com!1253731759!10154611!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 23911 invoked from network); 23 Sep 2009 18:49:19 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-11.tower-153.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Sep 2009 18:49:19 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n8NInEuF006328; Wed, 23 Sep 2009 11:49:19 -0700 (MST)
Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142]) by il06exr04.mot.com (8.13.1/Vontu) with SMTP id n8NInDDs008915; Wed, 23 Sep 2009 13:49:13 -0500 (CDT)
Received: from de01exm68.ds.mot.com (de01exm68.am.mot.com [10.176.8.24]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id n8NInCtS008910; Wed, 23 Sep 2009 13:49:12 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA3C7E.7E2521B8"
Date: Wed, 23 Sep 2009 14:48:51 -0400
Message-ID: <3A241A6B234BE948B8B474D261FEBC2F067F6699@de01exm68.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: NIST SP 800-120: Recommendation for EAP Methods Used in Wireless Network Access Authentication published 
thread-index: Aco8fn4eeBHODY6FTzC58MDQiOShlw==
From: "Hoeper Katrin-QWKN37" <khoeper@motorola.com>
To: <emu@ietf.org>, <hokey@ietf.org>
X-CFilter-Loop: Reflected
Subject: [Emu] NIST SP 800-120: Recommendation for EAP Methods Used in Wireless Network Access Authentication published
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Sep 2009 18:48:15 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA3C7E.7E2521B8
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

FYI

Publication: SP 800-120 -- The National Institute of Standards and
Technology (NIST) is pleased to announce the release of Special
Publication 800-120. Recommendation for EAP Methods Used in Wireless
Network Access Authentication. This Recommendation formalizes core
security requirements for EAP methods when employed by the U.S. Federal
Government for wireless authentication and key establishment.

URL to SP 800-120:=20
http://csrc.nist.gov/publications/PubsSPs.html#800-120
<http://links.govdelivery.com:80/track?type=3Dclick&enid=3DbWFpbGluZ2lkPT=
U4N
Dg1NyZtZXNzYWdlaWQ9UFJELUJVTC01ODQ4NTcmZGF0YWJhc2VpZD0xMDAxJnNlcmlhbD0xM
jE1NTc0ODgyJmVtYWlsaWQ9aG9lcGk0MkBnbWFpbC5jb20mdXNlcmlkPWhvZXBpNDJAZ21ha
WwuY29tJmV4dHJhPSYmJg=3D=3D&&&103&&&http://csrc.nist.gov/publications/Pub=
sSP
s.html#800-120>=20

=20


------_=_NextPart_001_01CA3C7E.7E2521B8
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p><em><b><i><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:black;font-weight:bold'>FYI<o:p></o:p></span></fo=
nt></i></b></em></p>

<p><em><b><i><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:black;font-weight:bold'>Publication: SP 800-120 =
--</span></font></i></b></em><span
class=3Dapple-converted-space><b><i><font size=3D2 color=3Dblack =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:black;font-weight:bold;=

font-style:italic'>&nbsp;</span></font></i></b></span><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:black'>The
National Institute of Standards and Technology (NIST) is pleased to =
announce
the release of Special Publication 800-120. Recommendation for EAP =
Methods Used
in Wireless Network Access Authentication. This Recommendation =
formalizes core
security requirements for EAP methods when employed by the U.S. Federal
Government for wireless authentication and key =
establishment.<o:p></o:p></span></font></p>

<p><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:black'>URL to SP 800-120:<span
class=3Dapple-converted-space>&nbsp;</span><br>
<a
href=3D"http://links.govdelivery.com:80/track?type=3Dclick&amp;enid=3DbWF=
pbGluZ2lkPTU4NDg1NyZtZXNzYWdlaWQ9UFJELUJVTC01ODQ4NTcmZGF0YWJhc2VpZD0xMDAx=
JnNlcmlhbD0xMjE1NTc0ODgyJmVtYWlsaWQ9aG9lcGk0MkBnbWFpbC5jb20mdXNlcmlkPWhvZ=
XBpNDJAZ21haWwuY29tJmV4dHJhPSYmJg=3D=3D&amp;&amp;&amp;103&amp;&amp;&amp;h=
ttp://csrc.nist.gov/publications/PubsSPs.html#800-120"
target=3D"_blank"><font color=3D"#1d1ece"><span =
style=3D'color:#1D1ECE'>http://csrc.nist.gov/<wbr>publications/PubsSPs.ht=
ml#800-<wbr>120</span></font></a><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</span></div>

</body>

</html>

------_=_NextPart_001_01CA3C7E.7E2521B8--

From aland@deployingradius.com  Thu Sep 24 06:55:19 2009
Return-Path: <aland@deployingradius.com>
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 E6C3028C0E3 for <emu@core3.amsl.com>; Thu, 24 Sep 2009 06:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.968
X-Spam-Level: 
X-Spam-Status: No, score=-1.968 tagged_above=-999 required=5 tests=[AWL=0.631,  BAYES_00=-2.599]
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 uOdmzz+Y5rXw for <emu@core3.amsl.com>; Thu, 24 Sep 2009 06:55:19 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id DF4093A6A07 for <emu@ietf.org>; Thu, 24 Sep 2009 06:55:18 -0700 (PDT)
Received: from Thor.local (mey38-2-82-228-181-7.fbx.proxad.net [82.228.181.7]) by liberty.deployingradius.com (Postfix) with ESMTPSA id C25861234491; Thu, 24 Sep 2009 15:54:35 +0200 (CEST)
Message-ID: <4ABB7A8A.1070002@deployingradius.com>
Date: Thu, 24 Sep 2009 15:56:26 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com>	<877hvqavwp.fsf@mocca.josefsson.org>	<4ABA2282.4080207@deployingradius.com> <87r5txu4mt.fsf@mocca.josefsson.org>
In-Reply-To: <87r5txu4mt.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 13:55:20 -0000

Simon Josefsson wrote:
> Should we suggest that passwords are sent over the wire at all?  In good
> systems that should be the exception.

  It is widely deployed today with TTLS.  I think that allowing this
practice to continue is a requirement.

> 1) Usernames.  Should be sent over the wire as-is, or possibly
> Net-UTF-8.  It is not clear to me that the even the weak NFC part of
> Net-UTF-8 is always a good idea for usernames, you could just send the
> username as-is and require that COMPARISONS are done in a way that
> reduces ambitious.

  Ouch.  I fundamentally disagree.  See RFC 4282, and my attempt to
update it, based on real-world deployment experience:

http://tools.ietf.org/html/draft-dekok-radext-nai-00

  My document explains why it's difficult (i.e. impossible) for third
parties to "normalize" the data.

>  There are some indication that the algorithm of
> comparing two strings for equality is simpler to make robust and
> ambigious-free than an algorithm that normalize strings.

  Yes.  The systems which do end-user input likely have enough
information to normalize the data.  No one else does.  As a result,
everyone else should compare the two strings for equality.  They should
not normalize the strings.

> 2) Passwords sent to servers.  This has similar properties as 1) but
> there could be differences in how they are treated.
> 
> 3) Passwords sent to servers only in hashed form.  This has stricter
> normalization requirements than 1) and 2) -- NFC is most certainly
> needed, and probably something more, similar to SASLprep but preferably
> without some of the problems that SASLprep has.

  I beleive that (2) and (3) are the same case.  For (3), we will end up
checking for:

	hash(p1) == hash(p2)

  For strong hashes, the simplest way to ensure this is true is if:

	p1 == p2

> The problem with normalization early is that you end up with a interop
> problem where both the client and server needs to implement the exact
> same normalization algorithms for things to be robust.  If normalization
> only happens in one implementation, things will be predictable.

  RFC 5198 specifies a normalized form.  If two implementations
"normalize" to the RFC 5198 form differently, one of them is wrong.

  Alan DeKok.

From simon@josefsson.org  Thu Sep 24 07:13:35 2009
Return-Path: <simon@josefsson.org>
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 84D903A69E0 for <emu@core3.amsl.com>; Thu, 24 Sep 2009 07:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level: 
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599]
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 KXJ4h53hemXG for <emu@core3.amsl.com>; Thu, 24 Sep 2009 07:13:34 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 421913A6817 for <emu@ietf.org>; Thu, 24 Sep 2009 07:13:34 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8OEEaqS003359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 24 Sep 2009 16:14:39 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Alan DeKok <aland@deployingradius.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> <877hvqavwp.fsf@mocca.josefsson.org> <4ABA2282.4080207@deployingradius.com> <87r5txu4mt.fsf@mocca.josefsson.org> <4ABB7A8A.1070002@deployingradius.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090924:emu@ietf.org::DvA3jGCIQ7kgG9lc:7Clw
X-Hashcash: 1:22:090924:aland@deployingradius.com::lH+qBfkiUJy/xTbB:FxP1
Date: Thu, 24 Sep 2009 16:14:36 +0200
In-Reply-To: <4ABB7A8A.1070002@deployingradius.com> (Alan DeKok's message of "Thu, 24 Sep 2009 15:56:26 +0200")
Message-ID: <877hvoqvjn.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 14:13:35 -0000

Alan DeKok <aland@deployingradius.com> writes:

> Simon Josefsson wrote:
>> Should we suggest that passwords are sent over the wire at all?  In good
>> systems that should be the exception.
>
>   It is widely deployed today with TTLS.  I think that allowing this
> practice to continue is a requirement.

I agree, but that does not necessarily mean that
passwords-sent-over-the-wire and passwords-sent-hashed must have the
same internationalization treatment or considerations.

>> 1) Usernames.  Should be sent over the wire as-is, or possibly
>> Net-UTF-8.  It is not clear to me that the even the weak NFC part of
>> Net-UTF-8 is always a good idea for usernames, you could just send the
>> username as-is and require that COMPARISONS are done in a way that
>> reduces ambitious.
>
>   Ouch.  I fundamentally disagree.  See RFC 4282, and my attempt to
> update it, based on real-world deployment experience:
>
> http://tools.ietf.org/html/draft-dekok-radext-nai-00
>
>   My document explains why it's difficult (i.e. impossible) for third
> parties to "normalize" the data.

Interesting!  It is good to see work in this area, and your reasons
appears good to me.  I believe it is desirable to reduce the amount of
string normalization that happens, and instead use comparison-rules when
possible, but sometimes normalization is required for one reason or the
other.  As soon as normalization rules are suggested, I believe it is
worthwhile to evaluate why comparison-rules are not sufficient, and your
document address that.

>> The problem with normalization early is that you end up with a interop
>> problem where both the client and server needs to implement the exact
>> same normalization algorithms for things to be robust.  If normalization
>> only happens in one implementation, things will be predictable.
>
>   RFC 5198 specifies a normalized form.  If two implementations
> "normalize" to the RFC 5198 form differently, one of them is wrong.

Sure, but see section 4 of RFC 5198.  If it happens that NFC backwards
compatibility is broken, you end up with the interop problem.  This has
happened before for NFKC which has caused (theoretical) interop problems
for IDNA and SASLprep -- if two implementations of RFC 3454 use
different Unicode versions, they don't necessarily interop.

/Simon

From aland@deployingradius.com  Thu Sep 24 08:21:05 2009
Return-Path: <aland@deployingradius.com>
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 E8C3C3A69CB for <emu@core3.amsl.com>; Thu, 24 Sep 2009 08:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[AWL=0.611,  BAYES_00=-2.599]
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 yCPcq8-HAOUu for <emu@core3.amsl.com>; Thu, 24 Sep 2009 08:21:05 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 0D2E83A6937 for <emu@ietf.org>; Thu, 24 Sep 2009 08:21:05 -0700 (PDT)
Received: from Thor.local (mey38-2-82-228-181-7.fbx.proxad.net [82.228.181.7]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 07DF61234491; Thu, 24 Sep 2009 17:20:24 +0200 (CEST)
Message-ID: <4ABB8EA5.20405@deployingradius.com>
Date: Thu, 24 Sep 2009 17:22:13 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com>	<877hvqavwp.fsf@mocca.josefsson.org>	<4ABA2282.4080207@deployingradius.com>	<87r5txu4mt.fsf@mocca.josefsson.org>	<4ABB7A8A.1070002@deployingradius.com> <877hvoqvjn.fsf@mocca.josefsson.org>
In-Reply-To: <877hvoqvjn.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 15:21:06 -0000

Simon Josefsson wrote:
>>   It is widely deployed today with TTLS.  I think that allowing this
>> practice to continue is a requirement.
> 
> I agree, but that does not necessarily mean that
> passwords-sent-over-the-wire and passwords-sent-hashed must have the
> same internationalization treatment or considerations.

  That isn't a requirement, but it does make things easier.

> Sure, but see section 4 of RFC 5198.  If it happens that NFC backwards
> compatibility is broken, you end up with the interop problem.

  ? Section 4 says explicitly:

   if a string does not contain any unassigned
   characters, and it is normalized according to NFC, it will always be
   normalized according to all future versions of the Unicode Standard.

  So there is no backwards compatibility problem.

  My interpretation is that every system taking user input needs to
perform this normalization.  Once that's done, string comparison is
essentially memcmp().

  If both user && authenticator are using the same version of Unicode,
then they inter-operate.

  If one is using a newer version, then it either

	(a) creates the same output string, because the *old* characters
            have not been re-assigned in the *new* standard

 	(b) creates a different output string than the old system,
	    because either the standard is not backwards compatible,
	    or the implementation is wrong.

  Is there anything I'm missing?

  Alan DeKok.

From simon@josefsson.org  Thu Sep 24 08:30:15 2009
Return-Path: <simon@josefsson.org>
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 335FF3A6944 for <emu@core3.amsl.com>; Thu, 24 Sep 2009 08:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599]
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 znVG4FrMVnF6 for <emu@core3.amsl.com>; Thu, 24 Sep 2009 08:30:14 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id B88813A6905 for <emu@ietf.org>; Thu, 24 Sep 2009 08:30:13 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8OFVHSV005472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 24 Sep 2009 17:31:19 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Alan DeKok <aland@deployingradius.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> <877hvqavwp.fsf@mocca.josefsson.org> <4ABA2282.4080207@deployingradius.com> <87r5txu4mt.fsf@mocca.josefsson.org> <4ABB7A8A.1070002@deployingradius.com> <877hvoqvjn.fsf@mocca.josefsson.org> <4ABB8EA5.20405@deployingradius.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090924:emu@ietf.org::S/1Q6J9HiPac3DrX:kuC
X-Hashcash: 1:22:090924:aland@deployingradius.com::r71HQPVKx9gbxcrh:69Ky
Date: Thu, 24 Sep 2009 17:31:17 +0200
In-Reply-To: <4ABB8EA5.20405@deployingradius.com> (Alan DeKok's message of "Thu, 24 Sep 2009 17:22:13 +0200")
Message-ID: <87ocp0pdfe.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 15:30:15 -0000

Alan DeKok <aland@deployingradius.com> writes:

> Simon Josefsson wrote:
>>>   It is widely deployed today with TTLS.  I think that allowing this
>>> practice to continue is a requirement.
>> 
>> I agree, but that does not necessarily mean that
>> passwords-sent-over-the-wire and passwords-sent-hashed must have the
>> same internationalization treatment or considerations.
>
>   That isn't a requirement, but it does make things easier.
>
>> Sure, but see section 4 of RFC 5198.  If it happens that NFC backwards
>> compatibility is broken, you end up with the interop problem.
>
>   ? Section 4 says explicitly:
>
>    if a string does not contain any unassigned
>    characters, and it is normalized according to NFC, it will always be
>    normalized according to all future versions of the Unicode Standard.
>
>   So there is no backwards compatibility problem.

See this part:

   Were Unicode to be changed in a way that violated these assumptions,
   i.e., that either invalidated the byte string order specified in RFC
   3629 or that changed the stability of NFC as stated above, this
   specification would not apply.

If that happens, there is a backwards compatibility problem with old
implementations.

>   My interpretation is that every system taking user input needs to
> perform this normalization.  Once that's done, string comparison is
> essentially memcmp().

Right.  My point is that the one needs to weight this approach to a
system which does not use normalization but instead use
internationalized comparison rules.

>   If both user && authenticator are using the same version of Unicode,
> then they inter-operate.
>
>   If one is using a newer version, then it either
>
> 	(a) creates the same output string, because the *old* characters
>             have not been re-assigned in the *new* standard
>
>  	(b) creates a different output string than the old system,
> 	    because either the standard is not backwards compatible,
> 	    or the implementation is wrong.
>
>   Is there anything I'm missing?

Yes: there is typically no version negotiation of SASLprep or RFC 5198
version used in protocols.  So a client would typically not know what
Unicode version the server uses.  This would be one reason to put the
Unicode version depended code into one place (where the comparison
happens) rather than in several places (normalization in the client and
in the server).

Which approach to use needs to be decided understanding these
trade-offs.  I'm not saying that the comparison-approach is always
better, but my experience with normalization in client/server-systems is
that it does not work well enough that we should consider if other
approaches may work better.

/Simon

From aland@deployingradius.com  Fri Sep 25 02:57:54 2009
Return-Path: <aland@deployingradius.com>
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 6D2233A690A for <emu@core3.amsl.com>; Fri, 25 Sep 2009 02:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level: 
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[AWL=0.592,  BAYES_00=-2.599]
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 aqkEhBbou9Zx for <emu@core3.amsl.com>; Fri, 25 Sep 2009 02:57:53 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id A79083A6824 for <emu@ietf.org>; Fri, 25 Sep 2009 02:57:53 -0700 (PDT)
Received: from Thor.local (mey38-2-82-228-181-7.fbx.proxad.net [82.228.181.7]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 7E0DD1234491; Fri, 25 Sep 2009 11:57:44 +0200 (CEST)
Message-ID: <4ABC9467.2000704@deployingradius.com>
Date: Fri, 25 Sep 2009 11:59:03 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com>	<877hvqavwp.fsf@mocca.josefsson.org>	<4ABA2282.4080207@deployingradius.com>	<87r5txu4mt.fsf@mocca.josefsson.org>	<4ABB7A8A.1070002@deployingradius.com>	<877hvoqvjn.fsf@mocca.josefsson.org>	<4ABB8EA5.20405@deployingradius.com> <87ocp0pdfe.fsf@mocca.josefsson.org>
In-Reply-To: <87ocp0pdfe.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Sep 2009 09:57:54 -0000

Simon Josefsson wrote:
> Right.  My point is that the one needs to weight this approach to a
> system which does not use normalization but instead use
> internationalized comparison rules.

  How do you do internationalized comparisons on hashed passwords?

  All you have is the hash.  And if the passwords input to the hash
aren't the same (i.e. non-normalized), then you're *guaranteed* that the
hashes won't match.

  Alan DeKok.

From simon@josefsson.org  Fri Sep 25 03:54:29 2009
Return-Path: <simon@josefsson.org>
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 1EE3F3A683D for <emu@core3.amsl.com>; Fri, 25 Sep 2009 03:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599]
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 qsP1nkHPcqn1 for <emu@core3.amsl.com>; Fri, 25 Sep 2009 03:54:28 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 0D3E93A6932 for <emu@ietf.org>; Fri, 25 Sep 2009 03:54:27 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8PAtW7x032666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 25 Sep 2009 12:55:34 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Alan DeKok <aland@deployingradius.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> <877hvqavwp.fsf@mocca.josefsson.org> <4ABA2282.4080207@deployingradius.com> <87r5txu4mt.fsf@mocca.josefsson.org> <4ABB7A8A.1070002@deployingradius.com> <877hvoqvjn.fsf@mocca.josefsson.org> <4ABB8EA5.20405@deployingradius.com> <87ocp0pdfe.fsf@mocca.josefsson.org> <4ABC9467.2000704@deployingradius.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090925:emu@ietf.org::CqIkcEF/0ddBKebG:Gqvj
X-Hashcash: 1:22:090925:aland@deployingradius.com::o5fCFKE4ALpCXqfK:PrLj
Date: Fri, 25 Sep 2009 12:55:32 +0200
In-Reply-To: <4ABC9467.2000704@deployingradius.com> (Alan DeKok's message of "Fri, 25 Sep 2009 11:59:03 +0200")
Message-ID: <87iqf7fg4b.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Sep 2009 10:54:29 -0000

Alan DeKok <aland@deployingradius.com> writes:

> Simon Josefsson wrote:
>> Right.  My point is that the one needs to weight this approach to a
>> system which does not use normalization but instead use
>> internationalized comparison rules.
>
>   How do you do internationalized comparisons on hashed passwords?
>
>   All you have is the hash.  And if the passwords input to the hash
> aren't the same (i.e. non-normalized), then you're *guaranteed* that the
> hashes won't match.

Right.  Hashed passwords is one example of when internationalized
comparisons wouldn't work.  I'm sorry if this wasn't clear in my earlier
note.

However there is a risk that normalization _introduce_ differences: if
two systems use different normalization algorithms that leads to
different outputs for the same input, the hashes won't match either.

/Simon

From jsalowey@cisco.com  Mon Sep 28 10:59:10 2009
Return-Path: <jsalowey@cisco.com>
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 7B1183A6834 for <emu@core3.amsl.com>; Mon, 28 Sep 2009 10:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 N1uQCpgOjMfr for <emu@core3.amsl.com>; Mon, 28 Sep 2009 10:59:06 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 864533A6829 for <emu@ietf.org>; Mon, 28 Sep 2009 10:59:06 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAAeWwEqrR7PD/2dsb2JhbADASIhTATaNegWCT4FP
X-IronPort-AV: E=Sophos;i="4.44,467,1249257600"; d="scan'208";a="208924486"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 28 Sep 2009 18:00:25 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n8SI0P5W017859;  Mon, 28 Sep 2009 11:00:25 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n8SI0PTJ007707; Mon, 28 Sep 2009 18:00:25 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.3959);  Mon, 28 Sep 2009 11:00:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Sep 2009 11:00:23 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE508CD2A68@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <87iqf7fg4b.fsf@mocca.josefsson.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Emu] Revised sections for  Issue #18 (Internationalization)
Thread-Index: Aco9zrpoyaEtx0K7QlilaX4Jx9bAogClmb4g
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com><877hvqavwp.fsf@mocca.josefsson.org><4ABA2282.4080207@deployingradius.com><87r5txu4mt.fsf@mocca.josefsson.org><4ABB7A8A.1070002@deployingradius.com><877hvoqvjn.fsf@mocca.josefsson.org><4ABB8EA5.20405@deployingradius.com><87ocp0pdfe.fsf@mocca.josefsson.org><4ABC9467.2000704@deployingradius.com> <87iqf7fg4b.fsf@mocca.josefsson.org>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Simon Josefsson" <simon@josefsson.org>, "Alan DeKok" <aland@deployingradius.com>
X-OriginalArrivalTime: 28 Sep 2009 18:00:24.0924 (UTC) FILETIME=[8DDA29C0:01CA4065]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1839; t=1254160825; x=1255024825; c=relaxed/simple; s=sjdkim3002; 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]=20Revised=20sections=20for=20=20I ssue=20#18=20(Internationalization) |Sender:=20; bh=TUlqvgjrShzdLGf60XiIqxrqmKsmZUijYUTm3YL7GHo=; b=dCxyN+UC5Iqn3OpV3wUBsGAOfVk+NFWX29B60SvnaQuDmH+xkJHiFD0B5/ OMHnF+ma2RkW7kjdUvNOddVvNhyL0ID4Pp3ykTtPZdRAgeYjkrq8sThsx6KI /teWl8S1Jj;
Authentication-Results: sj-dkim-3; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Sep 2009 17:59:10 -0000

I'd like to see if we can close on this issue soon.  The main use case
we are targeting is one where the password is sent to the server.  We do
not know how the server will do the comparison.   Given that this is a
requirement document I don't think we need to have the full solution
described.  Can you two work out some proposed text to go in the
requirements document on this issue with usernames and passwords? =20

Thanks,

Joe=20

> -----Original Message-----
> From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20
> Behalf Of Simon Josefsson
> Sent: Friday, September 25, 2009 3:56 AM
> To: Alan DeKok
> Cc: emu@ietf.org
> Subject: Re: [Emu] Revised sections for Issue #18=20
> (Internationalization)
>=20
> Alan DeKok <aland@deployingradius.com> writes:
>=20
> > Simon Josefsson wrote:
> >> Right.  My point is that the one needs to weight this=20
> approach to a=20
> >> system which does not use normalization but instead use=20
> >> internationalized comparison rules.
> >
> >   How do you do internationalized comparisons on hashed passwords?
> >
> >   All you have is the hash.  And if the passwords input to the hash=20
> > aren't the same (i.e. non-normalized), then you're=20
> *guaranteed* that=20
> > the hashes won't match.
>=20
> Right.  Hashed passwords is one example of when=20
> internationalized comparisons wouldn't work.  I'm sorry if=20
> this wasn't clear in my earlier note.
>=20
> However there is a risk that normalization _introduce_=20
> differences: if two systems use different normalization=20
> algorithms that leads to different outputs for the same=20
> input, the hashes won't match either.
>=20
> /Simon
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>=20

From simon@josefsson.org  Tue Sep 29 00:52:53 2009
Return-Path: <simon@josefsson.org>
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 E04BE3A68B1 for <emu@core3.amsl.com>; Tue, 29 Sep 2009 00:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level: 
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599]
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 8CydCgUyOWji for <emu@core3.amsl.com>; Tue, 29 Sep 2009 00:52:53 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id D2CD13A6A6C for <emu@ietf.org>; Tue, 29 Sep 2009 00:52:51 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8T7s3tY027725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 29 Sep 2009 09:54:04 +0200
From: Simon Josefsson <simon@josefsson.org>
To: "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> <877hvqavwp.fsf@mocca.josefsson.org> <4ABA2282.4080207@deployingradius.com> <87r5txu4mt.fsf@mocca.josefsson.org> <4ABB7A8A.1070002@deployingradius.com> <877hvoqvjn.fsf@mocca.josefsson.org> <4ABB8EA5.20405@deployingradius.com> <87ocp0pdfe.fsf@mocca.josefsson.org> <4ABC9467.2000704@deployingradius.com> <87iqf7fg4b.fsf@mocca.josefsson.org> <AC1CFD94F59A264488DC2BEC3E890DE508CD2A68@xmb-sjc-225.amer.cisco.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090929:emu@ietf.org::tkjaRLBjMqAojlZ3:083M
X-Hashcash: 1:22:090929:jsalowey@cisco.com::0+B/x761Ji1s2Riv:3Joc
X-Hashcash: 1:22:090929:aland@deployingradius.com::vauzjaUppIdkYnKl:28Sf
Date: Tue, 29 Sep 2009 09:54:03 +0200
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE508CD2A68@xmb-sjc-225.amer.cisco.com> (Joseph Salowey's message of "Mon, 28 Sep 2009 11:00:23 -0700")
Message-ID: <87tyymkwys.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 07:52:54 -0000

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> writes:

> I'd like to see if we can close on this issue soon.  The main use case
> we are targeting is one where the password is sent to the server.  We do
> not know how the server will do the comparison.   Given that this is a
> requirement document I don't think we need to have the full solution
> described.  Can you two work out some proposed text to go in the
> requirements document on this issue with usernames and passwords?  

I think the text proposed is mostly fine.  I would say "normalization
and/or comparison" instead of just "normalization" to allow for
mechanisms that just specify comparison-based rules rather than
normalization-based rules.  So:

OLD:
   The password authentication exchange MUST support user names and
   passwords in international languages.  It MUST support encoding of
   user name and password strings in UTF-8 [RFC3629] format. The method
   MUST specify how username and password normalization is performed in
   reference to SASLPrep [RFC4013] or Net-UTF-8 [RFC5198].

NEW:
   The password authentication exchange MUST support user names and
   passwords in international languages.  It MUST support encoding of
   user name and password strings in UTF-8 [RFC3629] format. The method
   MUST specify how username and password normalizations and/or
   comparisons is performed in reference to SASLPrep [RFC4013] or
   Net-UTF-8 [RFC5198].

/Simon

From aland@deployingradius.com  Tue Sep 29 06:20:17 2009
Return-Path: <aland@deployingradius.com>
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 16D5E3A6AAC for <emu@core3.amsl.com>; Tue, 29 Sep 2009 06:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.601,  BAYES_00=-2.599]
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 a-XINlnM+dkr for <emu@core3.amsl.com>; Tue, 29 Sep 2009 06:20:16 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 3D28B3A696A for <emu@ietf.org>; Tue, 29 Sep 2009 06:20:16 -0700 (PDT)
Received: from Thor.local (mey38-2-82-228-181-7.fbx.proxad.net [82.228.181.7]) by liberty.deployingradius.com (Postfix) with ESMTPSA id A618012345DC; Tue, 29 Sep 2009 15:21:35 +0200 (CEST)
Message-ID: <4AC209DF.5000101@deployingradius.com>
Date: Tue, 29 Sep 2009 15:21:35 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com>	<877hvqavwp.fsf@mocca.josefsson.org>	<4ABA2282.4080207@deployingradius.com>	<87r5txu4mt.fsf@mocca.josefsson.org>	<4ABB7A8A.1070002@deployingradius.com>	<877hvoqvjn.fsf@mocca.josefsson.org>	<4ABB8EA5.20405@deployingradius.com>	<87ocp0pdfe.fsf@mocca.josefsson.org>	<4ABC9467.2000704@deployingradius.com>	<87iqf7fg4b.fsf@mocca.josefsson.org>	<AC1CFD94F59A264488DC2BEC3E890DE508CD2A68@xmb-sjc-225.amer.cisco.com> <87tyymkwys.fsf@mocca.josefsson.org>
In-Reply-To: <87tyymkwys.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 13:20:17 -0000

Simon Josefsson wrote:
> I think the text proposed is mostly fine.  I would say "normalization
> and/or comparison" instead of just "normalization" to allow for
> mechanisms that just specify comparison-based rules rather than
> normalization-based rules.  So:

  The text looks OK to me.

  My only concern is that standardizing i18n in *each* possible EAP
document is duplicating work.  If we end up with only one tunnel method
that is standardized, then there's less of a problem.

  Alan DeKok.

From simon@josefsson.org  Tue Sep 29 07:07:55 2009
Return-Path: <simon@josefsson.org>
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 A28583A6ACB for <emu@core3.amsl.com>; Tue, 29 Sep 2009 07:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level: 
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599]
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 uONVUTDHiXGv for <emu@core3.amsl.com>; Tue, 29 Sep 2009 07:07:54 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 81C523A684B for <emu@ietf.org>; Tue, 29 Sep 2009 07:07:53 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8TE93VZ004923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 29 Sep 2009 16:09:06 +0200
X-Hashcash: 1:22:090929:aland@deployingradius.com::3re7E3fPWYrbTDnl:QhLr
X-Hashcash: 1:22:090929:emu@ietf.org::X+ISYTPumQymBmQs:7ql/
From: Simon Josefsson <simon@josefsson.org>
To: Alan DeKok <aland@deployingradius.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE508C62E3A@xmb-sjc-225.amer.cisco.com> <877hvqavwp.fsf@mocca.josefsson.org> <4ABA2282.4080207@deployingradius.com> <87r5txu4mt.fsf@mocca.josefsson.org> <4ABB7A8A.1070002@deployingradius.com> <877hvoqvjn.fsf@mocca.josefsson.org> <4ABB8EA5.20405@deployingradius.com> <87ocp0pdfe.fsf@mocca.josefsson.org> <4ABC9467.2000704@deployingradius.com> <87iqf7fg4b.fsf@mocca.josefsson.org> <AC1CFD94F59A264488DC2BEC3E890DE508CD2A68@xmb-sjc-225.amer.cisco.com> <87tyymkwys.fsf@mocca.josefsson.org> <4AC209DF.5000101@deployingradius.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090929:jsalowey@cisco.com::oEEAoFRZBy27uDr4:Fq4t
Date: Tue, 29 Sep 2009 16:09:02 +0200
In-Reply-To: <4AC209DF.5000101@deployingradius.com> (Alan DeKok's message of "Tue, 29 Sep 2009 15:21:35 +0200")
Message-ID: <873a65kflt.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: emu@ietf.org
Subject: Re: [Emu] Revised sections for  Issue #18 (Internationalization)
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 14:07:55 -0000

Alan DeKok <aland@deployingradius.com> writes:

> Simon Josefsson wrote:
>> I think the text proposed is mostly fine.  I would say "normalization
>> and/or comparison" instead of just "normalization" to allow for
>> mechanisms that just specify comparison-based rules rather than
>> normalization-based rules.  So:
>
>   The text looks OK to me.
>
>   My only concern is that standardizing i18n in *each* possible EAP
> document is duplicating work.  If we end up with only one tunnel method
> that is standardized, then there's less of a problem.

Standardizing multiple tunnel-based methods seems like a bad idea for
many reasons.

I agree that standardizing i18n in every document will lead to
duplication of work (and duplication of discussions and the potential
for mistakes), but placing too specific requirements on all future EAP
documents today is similar to placing too specific crypto requirements
on all future EAP documents today.  The algorithms are evolving and
there needs to be some element of agility in the requirements.  If there
is, any mistakes in this area can be fixed later on.

/Simon
