From aland@deployingradius.com Sun Mar 1 06:37:37 2009 Return-Path: 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 1946B3A6878 for ; Sun, 1 Mar 2009 06:37:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.547 X-Spam-Level: X-Spam-Status: No, score=-1.547 tagged_above=-999 required=5 tests=[AWL=1.052, 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 VETEYoo4oWCo for ; Sun, 1 Mar 2009 06:37:36 -0800 (PST) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 532953A6853 for ; Sun, 1 Mar 2009 06:37:36 -0800 (PST) Received: from Thor.local (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238]) by liberty.deployingradius.com (Postfix) with ESMTPSA id CBFE71234091 for ; Sun, 1 Mar 2009 15:37:59 +0100 (CET) Message-ID: <49AA9DC7.3050008@deployingradius.com> Date: Sun, 01 Mar 2009 15:37:59 +0100 From: Alan DeKok User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: emu@ietf.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Emu] Draft agenda for IETF 74 X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2009 14:37:37 -0000 The following is the draft agenda for IETF 74. Please email the chairs for any concerns or updates. Blue sheets and Agenda updates 5 minutes draft-ietf-emu-eaptunnel-req-02.txt 60 minutes draft-clancy-emu-chbind-04.txt 25 minutes draft-clancy-emu-aaapay-01.txt 10 minutes draft-sheffer-emu-eap-eke-01 10 minutes Closing comments 10 minutes From Hannes.Tschofenig@gmx.net Sun Mar 1 10:44:15 2009 Return-Path: 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 382D33A6881 for ; Sun, 1 Mar 2009 10:44:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.307 X-Spam-Level: X-Spam-Status: No, score=-2.307 tagged_above=-999 required=5 tests=[AWL=0.292, 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 lV42vVGElKve for ; Sun, 1 Mar 2009 10:44:13 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 27E383A6844 for ; Sun, 1 Mar 2009 10:44:12 -0800 (PST) Received: (qmail invoked by alias); 01 Mar 2009 18:44:32 -0000 Received: from a91-154-108-144.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.108.144] by mail.gmx.net (mp058) with SMTP; 01 Mar 2009 19:44:32 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX19s7LZMr1BsdOxeCfU5Wa8FAAG2dTTQyNQPy1tWJM kE1dMXQxCEcEus From: "Hannes Tschofenig" To: "'Alan DeKok'" , References: <49AA9DC7.3050008@deployingradius.com> Date: Sun, 1 Mar 2009 20:45:32 +0200 Message-ID: <009401c99a9d$e7362c80$0201a8c0@nsnintra.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <49AA9DC7.3050008@deployingradius.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Thread-index: Acmae1S7PSJbdeprSGyy8sPotpRc4AAF+D6Q X-Y-GMX-Trusted: 0 X-FuHaFi: 0.65 Subject: Re: [Emu] Draft agenda for IETF 74 X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2009 18:44:15 -0000 Hi Alan, a few questions inline. What is more important for me is what we could at best accomplish during the meeting. > The following is the draft agenda for IETF 74. Please email >the chairs for any concerns or updates. > > > >Blue sheets and Agenda updates >5 minutes > >draft-ietf-emu-eaptunnel-req-02.txt >60 minutes Do we really need 60 minutes for this document? What are the open issues with this document? (sorry if I haven't paid close attention). > >draft-clancy-emu-chbind-04.txt >25 minutes I guess this is now draft-ietf-emu-chbind-00 I see TBDs in the document - are those the only open issues? > >draft-clancy-emu-aaapay-01.txt >10 minutes I understand the issue of defining channel bindings. draft-ietf-emu-chbind-00 does this but it does not define payloads. Do we really need to split this aspect into separate drafts? The aspect of having the possibility to carry an opaque blob in EAP (based on a Diameter AVP) format is a totally different subject. > > draft-sheffer-emu-eap-eke-01 >10 minutes This is a document that has a relationship to a charter item :-) Ciao Hannes > >Closing comments >10 minutes >_______________________________________________ >Emu mailing list >Emu@ietf.org >https://www.ietf.org/mailman/listinfo/emu > From jsalowey@cisco.com Sun Mar 1 21:30:13 2009 Return-Path: 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 9CCA53A6B0A for ; Sun, 1 Mar 2009 21:30:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.073 X-Spam-Level: X-Spam-Status: No, score=-6.073 tagged_above=-999 required=5 tests=[AWL=0.526, 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 kDkw5PecMkZJ for ; Sun, 1 Mar 2009 21:30:12 -0800 (PST) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id ACFCA3A6B03 for ; Sun, 1 Mar 2009 21:30:12 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.38,287,1233532800"; d="url'?scan'208";a="138344870" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 02 Mar 2009 05:30:36 +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 n225Ua8e001003 for ; Sun, 1 Mar 2009 21:30:36 -0800 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n225UanL013140 for ; Mon, 2 Mar 2009 05:30:36 GMT Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 1 Mar 2009 21:30:36 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C99AF8.03A07F2B" Date: Sun, 1 Mar 2009 21:30:35 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Emu] I-D Action:draft-ietf-emu-eaptunnel-req-02.txt Thread-Index: AcmYeOzKSfwc0wiAR1yF3CBcCncfcQCffCbw From: "Joseph Salowey (jsalowey)" To: X-OriginalArrivalTime: 02 Mar 2009 05:30:36.0267 (UTC) FILETIME=[03C663B0:01C99AF8] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2352; t=1235971836; x=1236835836; 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 |Subject:=20FW=3A=20[Emu]=20I-D=20Action=3Adraft-ietf-emu-e aptunnel-req-02.txt |Sender:=20; bh=374kA1QyD5WIUGwFEU9F2D0LN408eX4U7lbpLJIzRws=; b=bYFZydocUVZRz/CrpQ/Tc3A8nZJr+4D66Am6IU7O0f8IDdPzv5GgVYGGfF 72gDMl90agJkuXMN9vOa9c7MYa9IOutw78IfJFg4o6HvyZDpTLNPVmOu7AT/ /VxHQSO/Wq; Authentication-Results: sj-dkim-3; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Subject: [Emu] FW: I-D Action:draft-ietf-emu-eaptunnel-req-02.txt X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 05:30:13 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C99AF8.03A07F2B Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable I believe the document contains all the changes discussed in the meeting and on the list. The document should be ready for working group last call. It would help if a few people could review it to make sure it is complete. The following link provides to access to diffs and previous versions: http://tools.ietf.org/html/draft-ietf-emu-eaptunnel-req-02 Thanks, Joe -----Original Message----- From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Thursday, February 26, 2009 5:15 PM To: i-d-announce@ietf.org Cc: emu@ietf.org Subject: [Emu] I-D Action:draft-ietf-emu-eaptunnel-req-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the EAP Method Update Working Group of the IETF. Title : Requirements for a Tunnel Based EAP Method Author(s) : K. Hoeper, et al. Filename : draft-ietf-emu-eaptunnel-req-02.txt Pages : 24 Date : 2009-02-26 This memo defines the requirements for a tunnel-based Extensible Authentication Protocol (EAP) Method. This method will use Transport Layer Security (TLS) to establish a secure tunnel. The tunnel will provide support for password authentication, EAP authentication and the transport of additional data for other purposes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-emu-eaptunnel-req-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_001_01C99AF8.03A07F2B Content-Type: application/octet-stream; name="draft-ietf-emu-eaptunnel-req-02.URL" Content-Transfer-Encoding: base64 Content-Description: draft-ietf-emu-eaptunnel-req-02.URL Content-Disposition: attachment; filename="draft-ietf-emu-eaptunnel-req-02.URL" W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1pZXRmLWVtdS1lYXB0dW5uZWwtcmVxLTAyLnR4dA0K ------_=_NextPart_001_01C99AF8.03A07F2B-- From jsalowey@cisco.com Sun Mar 1 21:45:04 2009 Return-Path: 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 9DC5C3A692D for ; Sun, 1 Mar 2009 21:45:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.178 X-Spam-Level: X-Spam-Status: No, score=-6.178 tagged_above=-999 required=5 tests=[AWL=0.421, 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 E7ht63wuAiF1 for ; Sun, 1 Mar 2009 21:45:01 -0800 (PST) Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 5DE473A67DB for ; Sun, 1 Mar 2009 21:45:01 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.38,287,1233532800"; d="scan'208";a="136437871" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 02 Mar 2009 05:45:27 +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 n225jR6h030781; Sun, 1 Mar 2009 21:45:27 -0800 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n225jRUW018115; Mon, 2 Mar 2009 05:45:27 GMT Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 1 Mar 2009 21:45:26 -0800 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: Sun, 1 Mar 2009 21:45:25 -0800 Message-ID: In-Reply-To: <009401c99a9d$e7362c80$0201a8c0@nsnintra.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Emu] Draft agenda for IETF 74 Thread-Index: Acmae1S7PSJbdeprSGyy8sPotpRc4AAF+D6QABk2REA= References: <49AA9DC7.3050008@deployingradius.com> <009401c99a9d$e7362c80$0201a8c0@nsnintra.net> From: "Joseph Salowey (jsalowey)" To: "Hannes Tschofenig" , "Alan DeKok" , X-OriginalArrivalTime: 02 Mar 2009 05:45:26.0658 (UTC) FILETIME=[167D4620:01C99AFA] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2668; t=1235972727; x=1236836727; 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 |Subject:=20RE=3A=20[Emu]=20Draft=20agenda=20for=20IETF=207 4 |Sender:=20; bh=SrxUXBHRCfY6epRRUJG0M+hi/ONgbUVv5HRV1LrEnSg=; b=D7fkhYlK0liYTRtN7pPgrz3HhjzxmLPz5LZmbzRKFTtaIBHS9bNdb1YV90 Q8UHDBlVv313CeR4PNT9tsksSY8s7CwNlMCTtO8Q/9jUQw98k8k2LTZf8DkX brVezIlStj5Du3rRZ8plWS3zMi0oDVwd+9kUBRE2GKl2VwsP+B+rY=; Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); Subject: Re: [Emu] Draft agenda for IETF 74 X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 05:45:04 -0000 =20 > -----Original Message----- > From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On=20 > Behalf Of Hannes Tschofenig > Sent: Sunday, March 01, 2009 10:46 AM > To: 'Alan DeKok'; emu@ietf.org > Subject: Re: [Emu] Draft agenda for IETF 74 >=20 > Hi Alan,=20 >=20 > a few questions inline. What is more important for me is what=20 > we could at best accomplish during the meeting.=20 >=20 > > The following is the draft agenda for IETF 74. Please email the=20 > >chairs for any concerns or updates. > > > > > > > >Blue sheets and Agenda updates > >5 minutes > > > >draft-ietf-emu-eaptunnel-req-02.txt > >60 minutes >=20 > Do we really need 60 minutes for this document?=20 > What are the open issues with this document? (sorry if I=20 > haven't paid close attention).=20 >=20 [Joe] This document should not require 60 minutes, however we really do need to close on any issues that come out of last call. =20 >=20 > > > >draft-clancy-emu-chbind-04.txt > >25 minutes >=20 > I guess this is now draft-ietf-emu-chbind-00 I see TBDs in=20 > the document - are those the only open issues?=20 >=20 >=20 [Joe] I am not confident that there has been enough review of the document say these are the only issues. =20 > > > >draft-clancy-emu-aaapay-01.txt > >10 minutes >=20 > I understand the issue of defining channel bindings. > draft-ietf-emu-chbind-00 does this but it does not define payloads.=20 > Do we really need to split this aspect into separate drafts?=20 >=20 > The aspect of having the possibility to carry an opaque blob=20 > in EAP (based on a Diameter AVP) format is a totally=20 > different subject.=20 >=20 [Joe] OK, we should start a separate thread on this topic. =20 > > > > draft-sheffer-emu-eap-eke-01 > >10 minutes >=20 > This is a document that has a relationship to a charter item :-) > =20 [Joe] I agree that this is related to EMU work, but I believe we would require AD approval to take on work in this area. I think we will have more time to discuss this type of method and get an idea of the level of interest in the various approaches. =20 >=20 > Ciao > Hannes >=20 > > > >Closing comments > >10 minutes [Joe] If we can get note takers and Jabber scribes to volunteer ahead of time that would eliminate overhead at the beginning and end of the meeting. =20 > >_______________________________________________ > >Emu mailing list > >Emu@ietf.org > >https://www.ietf.org/mailman/listinfo/emu > > >=20 > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu >=20 From jsalowey@cisco.com Sun Mar 1 22:06:06 2009 Return-Path: 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 B712C28C11E for ; Sun, 1 Mar 2009 22:06:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.248 X-Spam-Level: X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[AWL=0.351, 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 PPzQiHWkVJBO for ; Sun, 1 Mar 2009 22:06:06 -0800 (PST) Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id E66E728C10E for ; Sun, 1 Mar 2009 22:06:05 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.38,287,1233532800"; d="scan'208";a="136443407" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 02 Mar 2009 06:06:31 +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 n2266VnT019793; Sun, 1 Mar 2009 22:06:31 -0800 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n2266VCq022779; Mon, 2 Mar 2009 06:06:31 GMT Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 1 Mar 2009 22:06:31 -0800 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: Sun, 1 Mar 2009 22:06:30 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Comments from Hannes on draft-clancy-emu-aaapay-01.txt Thread-Index: Acma/QfKwZ1BGZ9XRearXtWaa0O56Q== From: "Joseph Salowey (jsalowey)" To: , "Hannes Tschofenig" X-OriginalArrivalTime: 02 Mar 2009 06:06:31.0580 (UTC) FILETIME=[08710DC0:01C99AFD] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=521; t=1235973991; x=1236837991; 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 |Subject:=20Comments=20from=20Hannes=20on=20=20draft-clancy -emu-aaapay-01.txt |Sender:=20; bh=IwlVlRxFjERPWrHuNEjf+/RHGaIiX/TDx2gYzY4NigE=; b=p4ELgiQoJ2IelOua7ewX187ZWV/BMfEJiS3aqkegauqYAbO2IRb1tTETBk D4ymYEpN2vNrJI88XEVbNN5E00ZzRp1+dOkUfovvzdxV6+cshIU2crPKUC0M nc1Ub85NZNnQ/6vKhCGeWbSI7NoH4gJlWQQ+YbGcW62k4IGVUbm0I=; Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); Subject: [Emu] Comments from Hannes on draft-clancy-emu-aaapay-01.txt X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 06:06:06 -0000 Hannes said: >=20 > I understand the issue of defining channel bindings. > draft-ietf-emu-chbind-00 does this but it does not define payloads.=20 > Do we really need to split this aspect into separate drafts?=20 >=20 [Joe] Not necessarily. > The aspect of having the possibility to carry an opaque blob=20 > in EAP (based on a Diameter AVP) format is a totally=20 > different subject.=20 >=20 [Joe] Are you suggesting that the AAA payloads document is the right focus? If not then what would you suggest? From hannes.tschofenig@nsn.com Mon Mar 2 00:11:33 2009 Return-Path: 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 721953A68FE for ; Mon, 2 Mar 2009 00:11:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.69 X-Spam-Level: X-Spam-Status: No, score=-5.69 tagged_above=-999 required=5 tests=[AWL=0.909, 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 i7Ck15aTlh1b for ; Mon, 2 Mar 2009 00:11:32 -0800 (PST) Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 624323A68E0 for ; Mon, 2 Mar 2009 00:11:32 -0800 (PST) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n228Bnsi029483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 2 Mar 2009 09:11:49 +0100 Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n228Bk87014710; Mon, 2 Mar 2009 09:11:49 +0100 Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Mar 2009 09:11:47 +0100 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, 2 Mar 2009 10:12:46 +0200 Message-ID: <3D3C75174CB95F42AD6BCC56E5555B45011841C2@FIESEXC015.nsn-intra.net> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Emu] Comments from Hannes on draft-clancy-emu-aaapay-01.txt Thread-Index: Acma/QfKwZ1BGZ9XRearXtWaa0O56QADkZag References: From: "Tschofenig, Hannes (NSN - FI/Espoo)" To: "ext Joseph Salowey (jsalowey)" , , "Hannes Tschofenig" X-OriginalArrivalTime: 02 Mar 2009 08:11:47.0211 (UTC) FILETIME=[881B55B0:01C99B0E] Subject: Re: [Emu] Comments from Hannes on draft-clancy-emu-aaapay-01.txt X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 08:11:33 -0000 Hi Joe,=20 The idea of defining one payload format for carrying information in EAP methods sounds useful.=20 Then, someone only has to define something once and it is available (at least from a specification point of view) in all EAP methods.=20 In practice, this obviously requires code changes and there is the question of what you would like to carry in there. Do we have some good examples on what we would like to carry? My experience from various research projects is that everyone is very excited to define a new container but nobody tries to figure out what should be carried in it.=20 Using the Diameter format is OK for me. I wonder, however, whether the idea is to have automatically all the RADIUS and Diameter attributes / AVPs available for exchange in EAP methods? Furthermore, if someone believes that something is useful for exchange in an EAP method does this mean that this new extension gets automatically registered for the RADIUS and Diameter AVP/attribute space?=20 Ciao Hannes >Hannes said: >>=20 >> I understand the issue of defining channel bindings. >> draft-ietf-emu-chbind-00 does this but it does not define payloads.=20 >> Do we really need to split this aspect into separate drafts?=20 >>=20 >[Joe] Not necessarily. > >> The aspect of having the possibility to carry an opaque blob in EAP=20 >> (based on a Diameter AVP) format is a totally different subject. >>=20 >[Joe] Are you suggesting that the AAA payloads document is the=20 >right focus? If not then what would you suggest? > > >_______________________________________________ >Emu mailing list >Emu@ietf.org >https://www.ietf.org/mailman/listinfo/emu > From carolin.latze@unifr.ch Tue Mar 3 12:01:46 2009 Return-Path: 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 A2E683A6C79 for ; Tue, 3 Mar 2009 12:01:46 -0800 (PST) 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 LtTEJSAMUxcz for ; Tue, 3 Mar 2009 12:01:45 -0800 (PST) Received: from siufsrv105.unifr.ch (siufsrv105.unifr.ch [134.21.14.71]) by core3.amsl.com (Postfix) with ESMTP id 16C0128C31B for ; Tue, 3 Mar 2009 12:01:31 -0800 (PST) Received: from sr-svw-321.unifr.ch ([134.21.56.45] helo=exchange.unifr.ch) by siufsrv105.unifr.ch stage1 with esmtp with id 1LeaoO-0000LL-TH for from ; Tue, 03 Mar 2009 21:01:56 +0100 Received: from mail.unifr.ch ([134.21.56.45]) by exchange.unifr.ch with Microsoft SMTPSVC(6.0.3790.3959); Tue, 3 Mar 2009 21:01:56 +0100 Received: from [134.21.34.190] ([134.21.34.190]) by mail.unifr.ch over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 3 Mar 2009 21:01:56 +0100 Message-ID: <49AD8CB3.8070707@unifr.ch> Date: Tue, 03 Mar 2009 21:01:55 +0100 From: Carolin Latze User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: emu@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Mar 2009 20:01:56.0294 (UTC) FILETIME=[E7832E60:01C99C3A] Subject: [Emu] [Fwd: {Virus?} I-D Action:draft-latze-emu-eap-tpm-00.txt] X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Mar 2009 20:01:46 -0000 Hi all, EAP-TPM is a new EAP method aiming to be as secure as EAP-TLS but more comfortable for the user. The main idea is to replace the X.509 certificates with TPM identities (to be precise: with certified TPM keys) and to provide a zero-configuration option, which allows to request identities on the fly. We are always open for discussions, (critical) feedback, suggestions, ... Regards Carolin Latze -------- Original Message -------- Subject: {Virus?} I-D Action:draft-latze-emu-eap-tpm-00.txt Date: Tue, 3 Mar 2009 10:30:01 -0800 (PST) From: Internet-Drafts@ietf.org Reply-To: internet-drafts@ietf.org To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Extensible Authentication Protocol Method for Trusted Computing Groups (TCG) Trusted Platform Modules Author(s) : C. Latze, et al. Filename : draft-latze-emu-eap-tpm-00.txt Pages : 14 Date : 2009-03-03 This document describes an Extensible Authentication Protocol (EAP) [RFC3748] method for identity distribution, authentication and session key distribution using the Trusted Computing Group's (TCG) Trusted Platform Module (TPM). The TPM has been defined by the TCG in order to establish a root of trust and measurements in (consumer) computers. It provides several cryptographic functions and a secure storage for keys and hashes. There is also a TPM specification for mobile devices called Mobile Trusted Module (MTM), which can also be used for EAP-TPM. This new EAP method allows network authentication, which also supports user anonymity, the usage of different user identities for the authentication with different network operators, result indication, and a fast re-authentication. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-latze-emu-eap-tpm-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. From tim.polk@nist.gov Wed Mar 4 06:42:25 2009 Return-Path: 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 E8A923A6C8E; Wed, 4 Mar 2009 06:42:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.544 X-Spam-Level: X-Spam-Status: No, score=-6.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 kM4ceBSQ646I; Wed, 4 Mar 2009 06:42:24 -0800 (PST) Received: from smtp.nist.gov (rimp2.nist.gov [129.6.16.227]) by core3.amsl.com (Postfix) with ESMTP id BCD083A6C7D; Wed, 4 Mar 2009 06:42:24 -0800 (PST) Received: from [129.6.224.67] ([129.6.224.67]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id n24Egbme005170; Wed, 4 Mar 2009 09:42:47 -0500 Message-Id: From: Tim Polk To: Tim Polk In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 4 Mar 2009 09:47:25 -0500 References: <808FD6E27AD4884E94820BC333B2DB7727E78F274C@NOK-EUMSG-01.mgdnok.nokia.com> <006c01c98781$5d6b8bf0$1842a3d0$@net> <808FD6E27AD4884E94820BC333B2DB7727E78F2B67@NOK-EUMSG-01.mgdnok.nokia.com> <003201c9880d$e8160780$b8421680$@net> X-Mailer: Apple Mail (2.930.3) X-NIST-MailScanner: Found to be clean X-NIST-MailScanner-From: tim.polk@nist.gov Cc: emu@ietf.org, "iesg@ietf.org IESG" Subject: Re: [Emu] Potential Notes in EAP-FAST Documents X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2009 14:42:26 -0000 Folks, I have been sorting through the email trail on this one. In my opinion, there is *rough* consensus for the notes and approach that I proposed in this email. Minor revisions were suggested, but the subsequent email thread seems to show the stated text was acceptable. I have also reviewed the "key derivation differences" thread. To quote Jouni's email from 24 February: > In other words, we cannot come up with a EAP-MSCHAPv2 MSK derivation > rules that would cleanly fit into all deployed uses and there will > unfortunately be need for tunnel method specific exception in either > EAP-PEAP with cryptobinding or EAP-FAST. Either way, it would be > useful to get this documented clearly so that all future uses of EAP- > MSCHAPv2 would be able to refer to an existing specification instead > of having to come up with their own MSK/ISK derivation rules as was > done with EAP-PEAP cryptobinding and EAP-FAST. I agree that it will be good to get this documented clearly for future specs, but do not see an impact on current specs, so I am not requesting any further changes to the documents. Accordingly, I have asked the IESG Secretary to forward the proposed IESG notes to the RFC Editor. Thanks, Tim Polk On Feb 11, 2009, at 9:26 AM, Tim Polk wrote: > Folks, > > As the AD that sponsored publication of the EAP-FAST documents under > discussion, > I have been trying to find the best way forward. I believe that the > best course of action > involves some clarifications to draft-cam-winget-eap-fast- > provisioning to distinguish > the modified and unmodified use of EAP-MSCHAPv2, and IESG notes to > ensure these > publications do not establish precedent for future reuse of EAP type > codes with > different semantics. > > First, I support revising draft-cam-winget-eap-fast-provisioning so > that the modified > form of EAP-MSCHAPv2 is consistently referred to as EAP-FAST- > MSCHAPv2. The > authors offered to make this change earlier in the thread, and I > have seen some > support and no opposition to this suggestion. > > Second, I will be offering the following text for IESG notes on both > documents. The > notes clearly state the drawbacks for EAP type code reuse and define > an acceptable > path for future protocol developers. > > ------ draft-cam-winget-eap-fast-provisioning ----- > > EAP-FAST has been implemented by many vendors and it is used in the > Internet. Publication of this specification is intended to promote > interoperability by documenting current use of existing EAP methods > within EAP-FAST. > > The EAP method EAP-FAST-MSCHAPv2 reuses the EAP type code > assigned to > EAP-MSCHAPv2 (26) for authentication within an anonymous TLS > tunnel. In > order to minimize the risk associated with an anonymous tunnel, > changes > to the method were made that are not interoperable with EAP- > MSCHAPv2. > Since EAP-MSCHAPv2 does not support method-specific version > negotiation, > the use of EAP-FAST-MSCHAPv2 is implied by the use of an anonymous > EAP-FAST tunnel. This behavior may cause problems in > implementations > where the use of unaltered EAP-MSCHAPv2 is needed inside an > anonymous > EAP-FAST tunnel. Since such support requires special case > execution of > a method within a tunnel, it also complicates implementations > that use > the same method code both within and outside of the tunnel > method. If > EAP-FAST were to be designed today, these difficulties could be > avoided > by utilization of unique EAP Type codes. Given these issues, > assigned > method types must not be re-used with different meaning inside > tunneled > methods in the future. > > ---- draft-zhou-emu-fast-gtc ------ > > EAP-FAST has been implemented by many vendors and it is used in the > Internet. Publication of this specification is intended to promote > interoperability by documenting current use of existing EAP methods > within EAP-FAST. > > The EAP method EAP-FAST-GTC reuses the EAP type code assigned to > EAP-GTC (6). The reuse of previously assigned EAP Type Codes is > incompatible with EAP method negotiation as defined in RFC 3748. > Since > EAP-GTC does not support method-specific version negotiation, > the use of > EAP-FAST-GTC is implied when used inside the EAP-FAST tunnel during > authentication. This behavior may cause problems in > implementations where > the use of another vendor's EAP-GTC is required. Since such > support requires > special case execution of a method within a tunnel, it also > complicates > implementations that use the same method code both within and > outside of > the tunnel method. If EAP-FAST were to be designed today, these > difficulties could be avoided by utilization of unique EAP Type > codes. > Given these issues, assigned method types must not be re-used with > different meaning inside tunneled methods in the future. > > I am not under the illusion that this text will be entirely > satisfactory to anyone, > but I believe that it is an *appropriate* resolution to the problem. > > Thanks, > > Tim Polk From root@core3.amsl.com Wed Mar 4 09:15:01 2009 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 94DFD3A6CC6; Wed, 4 Mar 2009 09:15:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090304171501.94DFD3A6CC6@core3.amsl.com> Date: Wed, 4 Mar 2009 09:15:01 -0800 (PST) Cc: emu@ietf.org Subject: [Emu] I-D Action:draft-ietf-emu-chbind-01.txt X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2009 17:15:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the EAP Method Update Working Group of the IETF. Title : Channel Binding Support for EAP Methods Author(s) : C. Clancy, K. Hoeper Filename : draft-ietf-emu-chbind-01.txt Pages : 23 Date : 2009-03-04 This document defines how to implement channel bindings for Extensible Authentication Protocol (EAP) methods to address the lying NAS as well as the lying provider problem. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-emu-chbind-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-emu-chbind-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-03-04090926.I-D@ietf.org> --NextPart-- From glenzorn@comcast.net Wed Mar 4 11:50:47 2009 Return-Path: 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 0DDCB28C46A for ; Wed, 4 Mar 2009 11:50:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.67 X-Spam-Level: X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.930, 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 NyVnGZuoU2FY for ; Wed, 4 Mar 2009 11:50:46 -0800 (PST) Received: from QMTA05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by core3.amsl.com (Postfix) with ESMTP id 3F07828C14E for ; Wed, 4 Mar 2009 11:50:46 -0800 (PST) Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by QMTA05.emeryville.ca.mail.comcast.net with comcast id P7fe1b00G0mlR8UA57rFqg; Wed, 04 Mar 2009 19:51:15 +0000 Received: from gwzPC ([24.18.239.198]) by OMTA11.emeryville.ca.mail.comcast.net with comcast id P7rE1b0014HXf1k8X7rEL6; Wed, 04 Mar 2009 19:51:15 +0000 From: "Glen Zorn" To: "'Tim Polk'" References: <808FD6E27AD4884E94820BC333B2DB7727E78F274C@NOK-EUMSG-01.mgdnok.nokia.com> <006c01c98781$5d6b8bf0$1842a3d0$@net> <808FD6E27AD4884E94820BC333B2DB7727E78F2B67@NOK-EUMSG-01.mgdnok.nokia.com> <003201c9880d$e8160780$b8421680$@net> In-Reply-To: Date: Wed, 4 Mar 2009 11:51:01 -0800 Message-ID: <015401c99d02$8ca1f710$a5e5e530$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 thread-index: Acmc14KdrLh+sNQ2SmSeQRF9jHVHYQAJtFtg Content-Language: en-us Cc: emu@ietf.org, iesg@ietf.org Subject: Re: [Emu] Potential Notes in EAP-FAST Documents X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2009 19:50:47 -0000 Tim Polk [mailto://tim.polk@nist.gov] writes: So, there's no problem with reusing IANA-assigned numbers for whatever incompatible purpose one might like; oh, no, WAIT! There's a NOTE! Oooo, scary. Just to save time and energy, I've saved the scary note as a XML file & will include it in every I-D I post because I, too, have better things to do than bother with IANA: I'll just reuse whatever numbers come to mind, secure in the knowledge that (as long as there's a note) nothing will stand in the way of publication. BTW, did anyone ever figure out what "Managed by Cisco" means? Bernard has claimed that vendor-specific namespaces are allowed by RFC 5226 but has yet to produce any evidence for that, AFAIK. None of that matters, either? Cool. ... From aland@deployingradius.com Mon Mar 9 11:01:21 2009 Return-Path: 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 27E7F28C24B for ; Mon, 9 Mar 2009 11:01:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.073 X-Spam-Level: X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=0.526, 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 6p-fxlPyLW1Z for ; Mon, 9 Mar 2009 11:01:20 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 4671C28C24A for ; Mon, 9 Mar 2009 11:01:20 -0700 (PDT) Received: from Thor.local (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 44D071234097; Mon, 9 Mar 2009 19:01:53 +0100 (CET) Message-ID: <49B55991.4050508@deployingradius.com> Date: Mon, 09 Mar 2009 19:01:53 +0100 From: Alan DeKok User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: "Joseph Salowey (jsalowey)" References: In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: emu@ietf.org Subject: [Emu] LAST CALL FW: I-D Action:draft-ietf-emu-eaptunnel-req-02.txt X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 18:01:21 -0000 Joseph Salowey (jsalowey) wrote: > I believe the document contains all the changes discussed in the meeting > and on the list. The document should be ready for working group last > call. It would help if a few people could review it to make sure it is > complete. The following link provides to access to diffs and previous > versions: > > http://tools.ietf.org/html/draft-ietf-emu-eaptunnel-req-02 This is a LAST CALL for the Tunnel Requirements document. It will last 2 weeks, until Monday, March 23. Please review the document, and provide feedback to the list. EMU is meeting Wednesday March 25, at 15:00. If there are no comments, we will take the opportunity for one last overview of the document, and then we will submit it for publication. Alan DeKok. From bernard_aboba@hotmail.com Wed Mar 11 16:05:03 2009 Return-Path: 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 D76C33A6957 for ; Wed, 11 Mar 2009 16:05:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.829 X-Spam-Level: X-Spam-Status: No, score=-0.829 tagged_above=-999 required=5 tests=[AWL=-1.267, BAYES_05=-1.11, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=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 zJqUMmCmtQZx for ; Wed, 11 Mar 2009 16:04:57 -0700 (PDT) Received: from blu0-omc3-s38.blu0.hotmail.com (blu0-omc3-s38.blu0.hotmail.com [65.55.116.113]) by core3.amsl.com (Postfix) with ESMTP id 2C0CA28C21B for ; Wed, 11 Mar 2009 16:04:57 -0700 (PDT) Received: from BLU137-W17 ([65.55.116.72]) by blu0-omc3-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Mar 2009 16:05:33 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_0efbf1ef-328a-4a30-96ec-924769446c8f_" X-Originating-IP: [206.191.100.200] From: Bernard Aboba To: Date: Wed, 11 Mar 2009 16:05:33 -0700 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 11 Mar 2009 23:05:33.0834 (UTC) FILETIME=[E1C85EA0:01C9A29D] Subject: [Emu] RFC 2759 Issue X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2009 23:05:03 -0000 --_0efbf1ef-328a-4a30-96ec-924769446c8f_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RFC 2759 Section 4 states: =20 " The Name field is a string of 0 to (theoretically) 256 case-sensitive A= SCII characters which identifies the peer's user account name." This text=2C if taken literally=2C would imply that the name field cannot n= atively support international character sets. =20 =20 Yet tests show that 8-bit characters can be (and are) sent. From a cryptog= raphic point of view=2C the Name field appears to be treated as opaque octe= ts. While existing Windows implementations appear to encoding the Name fi= eld using ANSI code pages=2C from a protocol point of view it would appear= that a peer and server configured with a Name field encoded in UTF-8 shoul= d be able to communicate. =20 =20 Therefore=2C a potential correction to this sentence is the following: =20 "The Name field is a string of 0 to (theoretically) 256 octets identifying = the peer's user account name. Implementations SHOULD treat the Name field = as opaque octets."=20 EMAILING FOR THE LESSER EVIL Join me= --_0efbf1ef-328a-4a30-96ec-924769446c8f_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RFC 2759 Section 4 states:
 =3B
" =3B =3B The Name field is a string of 0 to (theoretically) 256 ca= se-sensitive =3BASCII characters which identifies the peer's user accou= nt name."

This text=2C if taken literally=2C would imply that the na= me field cannot natively support international character sets. =3B
 =3B
Yet tests show that 8-bit characters can be (and are) sent. =3B From a = cryptographic point of view=2C the Name field appears to be treated as opaq= ue octets. =3B =3B While existing Windows implementations appear to= encoding the Name field =3Busing ANSI code pages=2C =3B from a pro= tocol point of view it would appear that a peer and server configured with = a Name field encoded in UTF-8 should be able to =3Bcommunicate. =3B=  =3B
 =3B
Therefore=2C a potential correction to this =3Bsentence is the followin= g:
 =3B
"The Name field is a string of 0 to (theoretically) 256 octets identifying = the peer's user account name. =3B Implementations SHOULD treat the Name= field as opaque octets." =3B

3D"i'm" EMAILING FOR THE LESSER EVILJoin me
= --_0efbf1ef-328a-4a30-96ec-924769446c8f_-- From khoeper@motorola.com Fri Mar 20 15:17:17 2009 Return-Path: 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 A834A3A69A6 for ; Fri, 20 Mar 2009 15:17:17 -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=[AWL=0.000, 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 ZPIkSo92i1Aw for ; Fri, 20 Mar 2009 15:17:17 -0700 (PDT) Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with ESMTP id BED3D3A67D9 for ; Fri, 20 Mar 2009 15:17:16 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: khoeper@motorola.com X-Msg-Ref: server-9.tower-55.messagelabs.com!1237587481!77395692!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 8660 invoked from network); 20 Mar 2009 22:18:02 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-9.tower-55.messagelabs.com with AES256-SHA encrypted SMTP; 20 Mar 2009 22:18:02 -0000 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n2KMI1iM017489 for ; Fri, 20 Mar 2009 15:18:01 -0700 (MST) Received: from il06vts03.mot.com (il06vts03.mot.com [129.188.137.143]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id n2KMI1NX024193 for ; Fri, 20 Mar 2009 17:18:01 -0500 (CDT) Received: from de01exm66.ds.mot.com (de01exm66.am.mot.com [10.176.8.17]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id n2KMI1c7024188 for ; Fri, 20 Mar 2009 17:18:01 -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, 20 Mar 2009 18:18:00 -0400 Message-ID: In-Reply-To: <49AA9DC7.3050008@deployingradius.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Emu] Draft agenda for IETF 74 Thread-Index: Acmae1fgPUS3372+TryhCbErBhiWQQPLhDww References: <49AA9DC7.3050008@deployingradius.com> From: "Hoeper Katrin-QWKN37" To: "Alan DeKok" , X-CFilter-Loop: Reflected Subject: Re: [Emu] Draft agenda for IETF 74 X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 22:17:17 -0000 Please replace "draft-clancy-emu-chbind-04.txt" with the current version "draft-ietf-emu-chbind-01.txt" in the agenda. Thanks, Katrin -----Original Message----- From: emu-bounces@ietf.org [mailto:emu-bounces@ietf.org] On Behalf Of Alan DeKok Sent: Sunday, March 01, 2009 8:38 AM To: emu@ietf.org Subject: [Emu] Draft agenda for IETF 74 The following is the draft agenda for IETF 74. Please email the chairs for any concerns or updates. Blue sheets and Agenda updates 5 minutes draft-ietf-emu-eaptunnel-req-02.txt 60 minutes draft-clancy-emu-chbind-04.txt 25 minutes draft-clancy-emu-aaapay-01.txt 10 minutes draft-sheffer-emu-eap-eke-01 10 minutes Closing comments 10 minutes _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu From aland@deployingradius.com Sat Mar 21 09:11:36 2009 Return-Path: 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 900263A6B4A for ; Sat, 21 Mar 2009 09:11:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.329 X-Spam-Level: X-Spam-Status: No, score=-1.329 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_05=-1.11] 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 WwS6TvM8A-dz for ; Sat, 21 Mar 2009 09:11:35 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 0863E3A6B53 for ; Sat, 21 Mar 2009 09:11:32 -0700 (PDT) Received: from Thor.local (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 075C3123449C for ; Sat, 21 Mar 2009 17:12:18 +0100 (CET) Message-ID: <49C511E2.9020000@deployingradius.com> Date: Sat, 21 Mar 2009 17:12:18 +0100 From: Alan DeKok User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: emu@ietf.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Emu] Call for slides X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Mar 2009 16:11:36 -0000 Would the people on the agenda in the EMU slot next week please send the chairs their presentations. Thanks. Alan DeKok. From aland@deployingradius.com Wed Mar 25 12:58:39 2009 Return-Path: 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 475DA3A6B91 for ; Wed, 25 Mar 2009 12:58:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 F0Dm7xE+sKCw for ; Wed, 25 Mar 2009 12:58:38 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 792223A68AB for ; Wed, 25 Mar 2009 12:58:38 -0700 (PDT) Received: from dhcp-178b.meeting.ietf.org (dhcp-178b.meeting.ietf.org [130.129.23.139]) by liberty.deployingradius.com (Postfix) with ESMTPSA id DE3051234326 for ; Wed, 25 Mar 2009 20:59:29 +0100 (CET) Message-ID: <49CA8D20.1030209@deployingradius.com> Date: Wed, 25 Mar 2009 12:59:28 -0700 From: Alan DeKok User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: emu@ietf.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Emu] Materials for the WG meeting X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2009 19:58:39 -0000 Are up on the IETF web site: https://datatracker.ietf.org/meeting/74/materials.html