From nobody Fri Feb 2 09:02:15 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B23C212DA6D; Fri, 2 Feb 2018 09:02:13 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Kathleen Moriarty To: "The IESG" Cc: emu-chairs@ietf.org, emu@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.71.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151759093372.31806.10796579098479490610.idtracker@ietfa.amsl.com> Date: Fri, 02 Feb 2018 09:02:13 -0800 Archived-At: Subject: [Emu] Kathleen Moriarty's Yes on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 17:02:13 -0000 Kathleen Moriarty has entered the following ballot position for charter-ietf-emu-04-00: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-emu/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Milestones are likely to change (dates, etc.), but aligns with the charter. Jari's time was limited, so I helped and he will adjust. From nobody Sat Feb 3 00:36:29 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 713A112778D for ; Sat, 3 Feb 2018 00:36:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.32 X-Spam-Level: X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WTeRqVo66aoO for ; Sat, 3 Feb 2018 00:36:26 -0800 (PST) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BE271201F2 for ; Sat, 3 Feb 2018 00:36:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517646984; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=2tXkReGbGkSWFrPn+ClxC+9223kS03UOJ1+m8U0wIto=; b=TvGFQurOYm/Rmn/i7H0rbqEQfwKwwjsE6ewdUGqWeRC2dPS85WHTXwZ/TICzrwli CWDvi82HYP7FJOzjVqkiiwfGgHnnoEgG7iqO5/6IX/QxI+rabe26KwXq2QoZ8KFl +789tVLTg2pBytdolipBq/thEOsWQlZz2D0iJ3YQWMQ=; X-AuditID: c1b4fb2d-4b1ff70000005540-a7-5a7574875a79 Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id A1.13.21824.784757A5; Sat, 3 Feb 2018 09:36:24 +0100 (CET) Received: from nomadiclab.fi.eu.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.47) with Microsoft SMTP Server id 14.3.352.0; Sat, 3 Feb 2018 09:36:23 +0100 Received: from nomadiclab.fi.eu.ericsson.se (localhost [127.0.0.1]) by nomadiclab.fi.eu.ericsson.se (Postfix) with ESMTP id BE9614811FA; Sat, 3 Feb 2018 10:36:23 +0200 (EET) Received: from [127.0.0.1] (localhost [IPv6:::1]) by nomadiclab.fi.eu.ericsson.se (Postfix) with ESMTP id 5F588480F4B; Sat, 3 Feb 2018 10:36:23 +0200 (EET) To: Kathleen Moriarty , The IESG CC: , References: <151759093372.31806.10796579098479490610.idtracker@ietfa.amsl.com> From: Mohit Sethi Message-ID: <07c2cbc1-6bc2-7a9a-e010-99a229131761@ericsson.com> Date: Sat, 3 Feb 2018 10:36:22 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <151759093372.31806.10796579098479490610.idtracker@ietfa.amsl.com> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms020900060107020007040903" X-AV-Checked: ClamAV using ClamSMTP X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDIsWRmVeSWpSXmKPExsUyM2K7rm5HSWmUQVcPt8XU1t3MFsfWr2Wx mPFnIrNFw858BxaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugSvjS3MDa8Fh64qj516xNDB2 WHQxcnJICJhI7D1+kR3EFhI4zCgxY4pXFyMXkL2dUWLmi3tMEM4mRondBz8yQlQtYJS4/l8Y xBYWCJN4/HQrWLeIQIjEw89TWEBsZgFNiXVvLrBB1PtJHFywnBXEZhPQk+g8d5wZxOYVsJc4 2joNbCaLgIrE6k2bmUBsUYEIic6V81kgagQlTs58AmZzCvhLPGj+xAZyELNAN6PEvR3b2CFe UJZY0LII6jh1ia0dBxgnMArNQtI/C1nPLLADzSTmbX7IDGFrSyxb+BrKFpe49WQ+E4RtLTHj 10E2CFtRYkr3Q6heU4nXRz8yQtjGEsvW/WVbwMi5ilG0OLW4ODfdyFgvtSgzubg4P08vL7Vk EyMw3g5u+a27g3H1a8dDjAIcjEo8vB+zSqOEWBPLiitzDzGqAM15tGH1BUYplrz8vFQlEd5t a0uihHhTEiurUovy44tKc1KLDzFKc7AoifOe9OSNEhJITyxJzU5NLUgtgskycXBKNTBqZ648 ErbknsefuzbxxzgqvDos/A817Y5c8yPw7f7KlpRzxd8yJsapLdHfu++b5UqD+3s7uy5yinf9 LO1QVQm9HVS27UB3t+brw08mzhLcvtWvh3FZk8m+5XZ8Tk9PRS/MTvO405beqN8iFlcc0/Vl 2/PfMxdOrQo/LH2kzD9MzUBl9voTDZOVWIozEg21mIuKEwF4UVoSvwIAAA== Archived-At: Subject: Re: [Emu] Kathleen Moriarty's Yes on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 08:36:28 -0000 --------------ms020900060107020007040903 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi Kathleen, Thanks. This looks good. I understand that the milestones are likely to change. I believe that=20 the milestone "Adopt draft to define session identifiers for fast=20 re-authentication for EAP-SIM, EAP-AKA, and EAP-AKA" has a typo and=20 should include EAP-AKA'. Also, I think the session identifier for fast=20 re-authentication in EAP-AKA' would be part of the rfc5448bis document.=20 A separate document would only be needed for EAP-SIM and EAP-AKA session = identifiers. --Mohit On 02/02/2018 07:02 PM, Kathleen Moriarty wrote: > Kathleen Moriarty has entered the following ballot position for > charter-ietf-emu-04-00: Yes > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this= > introductory paragraph, however.) > > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/charter-ietf-emu/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Milestones are likely to change (dates, etc.), but aligns with the char= ter. > Jari's time was limited, so I helped and he will adjust. > > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu --------------ms020900060107020007040903 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC DMUwggX7MIID46ADAgECAhBcf8Ki080s7KKjg2APnSBWMA0GCSqGSIb3DQEBCwUAMEcxCzAJ BgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k aXZpZHVhbCBDQSB2MzAeFw0xNzEwMDgxMDAzMjJaFw0yMDEwMDgxMDAzMjFaMGgxETAPBgNV BAoMCEVyaWNzc29uMRYwFAYDVQQDDA1Nb2hpdCBTZXRoaSBNMSkwJwYJKoZIhvcNAQkBFhpt b2hpdC5tLnNldGhpQGVyaWNzc29uLmNvbTEQMA4GA1UEBRMHZXNldG1vaDCCASIwDQYJKoZI hvcNAQEBBQADggEPADCCAQoCggEBAN23/VIr1UI1NLeaFL45vzBE0NglNKyyUQknMqT5zRxm ocJ74fYRJmfHmaQxEYdxp6cCYFxbM2OJOiMN5LRxEQG282Dsjnff6mHXt5wNsMrHZ88poT3X yZCzFBkQF/kswJKu6OD9v1J6WWl9fV2h0QRP0ju+B/H2O3OzioHDP9Qazzr5TMTvmRmXoMfh WXyH/joBaGVyn8SCeRaI0wVGRCKDp93UzdL5o+qGqCUPJQP/2SR/4UoCUTqEtSgh4iCBNAs/ OwhHwbWdU73/EJtsaaOG2fhwMTgWR3KJOIUMyWtRBcO9cIan+82SNgAByR4x2BKIWgFvSPNo GXKn1nOi0W0CAwEAAaOCAcAwggG8MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6Ly9jcmwudHJ1 c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jcmwwgYIGCCsGAQUFBwEB BHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggrBgEF BQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp ZHVhbGNhdjMuY2VyMCUGA1UdEQQeMByBGm1vaGl0Lm0uc2V0aGlAZXJpY3Nzb24uY29tMFUG A1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3Np dG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggr BgEFBQcDAjAdBgNVHQ4EFgQUM0z7o31aA+qQasQqDc7/Ppn7u5MwHwYDVR0jBBgwFoAUHHsZ npecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3DQEBCwUAA4ICAQCB 35yJmyIRJUmxQmpYX7hNdQJXxJdIAMzCe+rQsz+0F1zA8xsYn4Rn5m7SVGKbE4ONC+EUHHzQ o1OpA5txlK+IPRMqZTM2cQpAet8Qy2vRqFVd0pFDmPx0Az/SPooz7gnuIaPaCGeXOSSxtSOu rX+7fE2EiE/SuCFKmtsFmwnZH62hDDtzd3XTwmJia/5Ab+8/elAstT5a1cP52SorrkuLPgAB ny/XJzsU3LOQQ37Wm5DMyMPEK+zkBG/+2t1cOGgryvu7Hq14NfkAUZxHMei6Yf2UABNxbapB 4tyxqpZuPZDl1AwRKMGYHPsnywK4PZDdsD6R+O/YCWdfq9Q3MMCT3C6vu38phy1r6QDCVHVI IPdirDfZ2ypbeqHAwkswioykkBTln9DEyaTYMlxb41EYh/3JwUQmuQQ4ozSfcLTwoaQ+M+Z4 1J/n7AARwD7u3Lb2ls+fmvOLrC+tc0pXlvTKspIhpaNC1Cz7sbsjMSbSqBW9PtY+Vex7GB2J zI8fDHTT/8Jx+33cta2BE6mPFeUY2lu12zQiqNVUc9zEQ7WqGz4VTGFZDnzfU2gCAAYsuimf kQJD+Sr2G3wXs38yN1OhWHBuG1fglz0k5URhXMNC8HtRityIm2504ym5GpTrriJ8X1fQDYN1 WlOPvv4xJpfHAz4NMKJKQmCNtfuZ8BNNyTCCBsIwggSqoAMCAQICEFO4foPhnJkok7CbSRzs uOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMMFlRl bGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUxMDI3MTIxNjQ2WjBH MQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5M IEluZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDs8t8A ALhQ8qe72FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfSTm+7meisbhkqUXkL 7fFzoe4iIZCh/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbXILlLhRummTdDdxhV W4Leo0awEhfLf98MvWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfpVdiCulPTlmsmV2RS BSAwqBshZYRcQBIDfqmdvkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2PUmE0rhu+Zs0nujn whljPA2/8b8v9tGixD1zbtT7zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2H/E0XY1LwJez89W0 7nscEocyBmpC+zJAmKxKhzEWqIyP1UrZaEIFu+hO+s0Nm8sOUMa4TlG4rAUikc5U5TmUIGBR QGxulYhfAzqSYf8oLUMLky1DOa9eRu3sp0FdQDEzQlnF/h1L4AK1MOkX1vS+fLgOvBo5LRU1 fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25aEvAA+yrrplCh/kYvSBjvZibz9Obbwx4yqS77 /NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUUkBUrrvijPDaGK5FNVSaioGvkC7IKioIT KffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCCAbQwgYoGCCsGAQUFBwEBBH4wfDAt BggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25lcmEuY29tMEsGCCsGAQUF BzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25l cmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAETjBMMEoGDCsGAQQB gg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3QudGVsaWFz b25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3JsLTMudHJ1c3QudGVs aWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1UdJQQWMBQGCCsGAQUF BwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7GZ6XnHasID3Y3OOR auPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0GCSqGSIb3DQEBCwUA A4ICAQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDUJQEPRs5QtaZiObNH CZ7mmSNMVek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHGvw5RY6vRlZrj0uKv dASzYL4KMaB7m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYnnl2t3D3oBX2NZCQy sshUcqRdUbkS13HTCIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwfixWms+C8sF0r9qN1 uJGx6ELPOiFrLfNtcMNMMbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ85AKjqzBnLSsjRGgb MgJ+xKtngmvEA155JmoKfUD7DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4HdDc1P+UMYm16m2L6L kIIoRlx0A5mi+K7jewuGqzFKkaPNmJ0RLCi+4d4/47Zs3DC3PUNOxdOEEHf4kkdWOaSIuj3T QYhNv+LsgF0uijiBmaz2zUFDa2bcIkKakDZfAFM4HoHz8K2BZRaHKWhd3dZua/tlSiqokUFX 2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i0bqGahxlHYzl/QyEG/dujp3lewuVjCI0mPDk ZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+WkDGCAzswggM3AgEBMFswRzELMAkGA1UE BhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlk dWFsIENBIHYzAhBcf8Ki080s7KKjg2APnSBWMA0GCWCGSAFlAwQCAQUAoIIBsTAYBgkqhkiG 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xODAyMDMwODM2MjNaMC8GCSqG SIb3DQEJBDEiBCDFgNPzCUwJ2op+rt0jN9DAATlLOMb2JeoSDgHEuzo1pzBqBgkrBgEEAYI3 EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJp Y3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQXH/CotPNLOyio4NgD50gVjBsBgkqhkiG9w0B CQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcN AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMGwGCyqGSIb3 DQEJEAILMV2gWzBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMM HEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCEFx/wqLTzSzsoqODYA+dIFYwDQYJKoZI hvcNAQEBBQAEggEADoRqPmzF+bedCKdQwo4C6L9BiePOZtshuC4lGIYwlRnP6WtCMsHh8D/q F2W5tWCUlbMqcP4HlY8siktysMPW03l98Y0gSTOotSX4kWOP2bFHQQvyU6qVWQV4OR4fEKuZ naPJN337REcNVhxCJeu3gI4do62yDKMjn4D3O5piYXx3up1AJeBVHgi4RYYZ6Rplbwfp9MmA N/QLNp98rZVzyPRVILyVV5U1NRaVPw8hbhZ9+qjY4hy0NaVl8FAyqfqnPNWs2T1O9ToT1Fkm O9Cx8OahSyZacz3pRg8FtRV7zqOUCHlz+DofMFOCc3GQ1Pf4Eab3Ieh4czpxQNn2ppq/EgAA AAAAAA== --------------ms020900060107020007040903-- From nobody Mon Feb 5 01:03:55 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A967128C0A for ; Mon, 5 Feb 2018 01:03:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.321 X-Spam-Level: X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1LDxBZ5hxPu for ; Mon, 5 Feb 2018 01:03:51 -0800 (PST) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D94CD126CC4 for ; Mon, 5 Feb 2018 01:03:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517821429; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=2N65va+ZuGPbKSEii5Hip0AKquhtM8hveSx0ro0WSHs=; b=KdyMctWvHMtsaQULCRRkuLBfal19petsKy4xfOsWB5Jb83m9TmoIY3RWCWN7a+UK VGJXBWPxA5WbYuWlU+orOWKozNtq/pCLW1sqKR/0omfBo8eYVfM/Y/YYT/Y9oyX1 bImpegZSd2Eo95mV/SrMPbLMnWDxhvf4A44CiLZac+w=; X-AuditID: c1b4fb30-399ff70000004778-78-5a781df4e59c Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id E5.B3.18296.4FD187A5; Mon, 5 Feb 2018 10:03:49 +0100 (CET) Received: from nomadiclab.fi.eu.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.3.352.0; Mon, 5 Feb 2018 10:03:48 +0100 Received: from nomadiclab.fi.eu.ericsson.se (localhost [127.0.0.1]) by nomadiclab.fi.eu.ericsson.se (Postfix) with ESMTP id 9884D4815CB; Mon, 5 Feb 2018 11:03:48 +0200 (EET) Received: from [127.0.0.1] (localhost [IPv6:::1]) by nomadiclab.fi.eu.ericsson.se (Postfix) with ESMTP id 4B21A480F54; Mon, 5 Feb 2018 11:03:48 +0200 (EET) To: Alan DeKok , Arkko Jari CC: References: <4D44B5F1-AE1E-4564-8366-31903B76FA9D@piuha.net> <574BCF7A-8172-4B12-9FB2-96CD3E4ECD76@deployingradius.com> From: Mohit Sethi Message-ID: <1345eef5-9f7d-afaf-71b9-7ebbac6e47c7@ericsson.com> Date: Mon, 5 Feb 2018 11:03:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <574BCF7A-8172-4B12-9FB2-96CD3E4ECD76@deployingradius.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-AV-Checked: ClamAV using ClamSMTP X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2J7oO5X2YoogzXTuC2aPjexWxxbv5bF Ysa+FWwOzB4tR1tYPJYs+cnksXXJdLYA5igum5TUnMyy1CJ9uwSujNn3LzAV/OGvOLfvG0sD 4zOeLkZODgkBE4l93yaxdzFycQgJHGaUuPS8BcrZzigxffMRKGcTo0TD3BUsEM4CRoklDZ+Z QPqFBdwkLpxcxQJiiwj4SrRNbGMGsZkFhCTmPboLViMkUCkxZc8rRhCbTUBPovPccbAaXgF7 iQVr+tlAbBYBFYn+0zfYQWxRgQiJzpXzWSBqBCVOznwCZHNwcAq4S5y/GQYx3kJi5vzzjBC2 tsSyha+h1opL3HoynwniNWWJBS2LGCFOUJfY2nGAcQKjyCwkU2chGTULyahZSEYtYGRZxSha nFqclJtuZKSXWpSZXFycn6eXl1qyiREYJwe3/DbYwfjyueMhRgEORiUe3iNSFVFCrIllxZW5 hxglOJiVRHidrpdHCfGmJFZWpRblxxeV5qQWH2KU5mBREuc96ckbJSSQnliSmp2aWpBaBJNl 4uCUamBs2v7526Ont0uexC181ST7I+Cb/Fe+Dez3esrS7jq/2CG4xTz40+kVamG2/qEHH65V joxdL3bg5UIVyWLFT12ugiJTihv+X24tmvN/Q84N4eiTN3x4q4vPd32s/vR/zwaLtGdzPty5 xLFExeDq4Rlfbm6SuzLZNeZZdJxab4RxBZvurnM75vDEKLEUZyQaajEXFScCAJyzTE+PAgAA Archived-At: Subject: Re: [Emu] Potential re-establishment of the EMU working group X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2018 09:03:53 -0000 Hi Alan, Thanks for raising this issue. I am trying to understand the problem of=20 large certificates and longer certificate chains a bit better. From your deployment experience, is the problem equally bad for=20 authentication in both directions (i.e. both client and server=20 certificates are large with long certificate chains)? And is the problem = only the number of EAP messages/packets, or also the duration of a=20 single authentication run (i.e. AP implementations drop EAP session if=20 not completed within x seconds/minutes)? --Mohit On 12/21/2017 04:01 PM, Alan DeKok wrote: > On Dec 21, 2017, at 8:40 AM, Jari Arkko wrote: >> I=E2=80=99ve been thinking of what to do with the EAP work that got di= scussed both in the SAAG meeting last time (my drafts), as well on the li= st. The latter was more on the EAP-TLS side, and it seems that the discus= sion has converged to a reasonable direction recently. >> >> Wondering how we could get the work moving forward. The first thought = that came to my mind was to start a small working group. Thoughts? A ver= y drafty idea of what it would do is below. Comments appreciated. > The Session ID also needs to be defined for SIM and AKA, as per Joun= i's comments. That doesn't fit in with AKA' changes. > > It may also be worth re-examining EAP-TLS. Modern certificates are = getting large, and people are using longer certificate chains. The resul= t can be that initial EAP-TLS authentication takes many packets. This ha= s issues not just for latency, but also access point implementations. Mo= st implementations will drop an EAP session if it hasn't finished after 4= 0-50 packets. > > I've seen people run into this issue with large certificates and lon= g certificate chains. It would be good to find a way to allow this use-c= ase. > > Alan DeKok. > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu From nobody Mon Feb 5 04:41:13 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A67612AF83 for ; Mon, 5 Feb 2018 04:41:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ud5rXJHnEv7d for ; Mon, 5 Feb 2018 04:41:08 -0800 (PST) Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) by ietfa.amsl.com (Postfix) with ESMTP id 96D571201F2 for ; Mon, 5 Feb 2018 04:41:08 -0800 (PST) Received: from [192.168.2.28] (198-84-205-59.cpe.teksavvy.com [198.84.205.59]) by mail.networkradius.com (Postfix) with ESMTPSA id 5C5A920E7; Mon, 5 Feb 2018 12:41:07 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Alan DeKok In-Reply-To: <1345eef5-9f7d-afaf-71b9-7ebbac6e47c7@ericsson.com> Date: Mon, 5 Feb 2018 07:41:06 -0500 Cc: emu@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <3AFB3ED0-A3E0-4052-A5E3-7DB589127F66@deployingradius.com> References: <4D44B5F1-AE1E-4564-8366-31903B76FA9D@piuha.net> <574BCF7A-8172-4B12-9FB2-96CD3E4ECD76@deployingradius.com> <1345eef5-9f7d-afaf-71b9-7ebbac6e47c7@ericsson.com> To: Mohit Sethi X-Mailer: Apple Mail (2.3124) Archived-At: Subject: Re: [Emu] Potential re-establishment of the EMU working group X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2018 12:41:11 -0000 On Feb 5, 2018, at 4:03 AM, Mohit Sethi = wrote: > Thanks for raising this issue. I am trying to understand the problem = of large certificates and longer certificate chains a bit better. >=20 > =46rom your deployment experience, is the problem equally bad for = authentication in both directions (i.e. both client and server = certificates are large with long certificate chains)? More so for clients. > And is the problem only the number of EAP messages/packets, or also = the duration of a single authentication run (i.e. AP implementations = drop EAP session if not completed within x seconds/minutes)? Mainly the number of EAP messages. The duration is less of an issue, = because it almost always happens within a second. Alan DeKok. From nobody Mon Feb 5 08:37:06 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C6E1270B4; Mon, 5 Feb 2018 08:36:59 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?Mirja_K=C3=BChlewind?= To: "The IESG" Cc: emu-chairs@ietf.org, emu@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.71.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151784861975.5719.2261756268635049659.idtracker@ietfa.amsl.com> Date: Mon, 05 Feb 2018 08:36:59 -0800 Archived-At: Subject: [Emu] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_charter-?= =?utf-8?q?ietf-emu-04-00=3A_=28with_COMMENT=29?= X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2018 16:37:00 -0000 Mirja Kühlewind has entered the following ballot position for charter-ietf-emu-04-00: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-emu/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I would actually rather like to see milestones for when the work is supposed to be finished (send to IESG for publication) than when it is supposed to start (wg adoption) as the first is probably harder to achieve in time than the second. From nobody Tue Feb 6 15:09:46 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD123124207; Tue, 6 Feb 2018 15:09:44 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: Kathleen.Moriarty.ietf@gmail.com, lflynn@amsl.com, emu-chairs@ietf.org, emu@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.72.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151795858468.25858.10883374057024525975.idtracker@ietfa.amsl.com> Date: Tue, 06 Feb 2018 15:09:44 -0800 Archived-At: Subject: [Emu] emu - New Meeting Session Request for IETF 101 X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2018 23:09:44 -0000 A new meeting session request has just been submitted by Liz Flynn, on behalf of the emu working group. --------------------------------------------------------- Working Group Name: EAP Method Update Area Name: Security Area Session Requester: Liz Flynn Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 30 Conflicts to Avoid: People who must be present: Kathleen Moriarty Resources Requested: Special Requests: --------------------------------------------------------- From nobody Wed Feb 7 10:26:30 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A181270AE; Wed, 7 Feb 2018 10:26:24 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Spencer Dawkins To: "The IESG" Cc: emu-chairs@ietf.org, emu@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.72.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151802798426.4831.16330955195087990127.idtracker@ietfa.amsl.com> Date: Wed, 07 Feb 2018 10:26:24 -0800 Archived-At: Subject: [Emu] Spencer Dawkins' No Objection on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2018 18:26:24 -0000 Spencer Dawkins has entered the following ballot position for charter-ietf-emu-04-00: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-emu/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Is "This working group has been chartered to provide updates to some commonly used EAP method." really singular? Or should it be "commonly used EAP methods"? From nobody Wed Feb 7 18:13:51 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 96E33124B18; Wed, 7 Feb 2018 18:13:49 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Ben Campbell To: "The IESG" Cc: emu-chairs@ietf.org, emu@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.72.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151805602957.17143.8761779262512562317.idtracker@ietfa.amsl.com> Date: Wed, 07 Feb 2018 18:13:49 -0800 Archived-At: Subject: [Emu] Ben Campbell's No Objection on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2018 02:13:49 -0000 Ben Campbell has entered the following ballot position for charter-ietf-emu-04-00: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-emu/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Substantive: First bullet point: "or other new concerns." makes this very open ended. Is this planned to be a standing working group? If not, can we put some constraints around "other new concerns"? The prohibition against obsoleting RFCs seems harsh. It's possible to require backwards compatibility without this restriction. I think it should be up to the working group to decide whether work can be better organized using updates or bis-drafts. The Feb 2019 milestone seems like two milestones. Editorial: -3rd paragraph: "And the understanding of security threats in today's Internet evolves as well,..." I suggest dropping "And" -- 2nd bullet: This is a bit hard to parse. I suggest: OLD: Update the EAP-AKA' specification (RFC 5448) to ensure that its capability to provide a cryptographic binding to network context stays in sync with what updates may come to the referenced 3GPP specifications through the use of EAP in 5G. NEW: Update the EAP-AKA' specification (RFC 5448) to ensure that its capability to provide a cryptographic binding to network context stays in sync with any 5G related updates to the referenced 3GPP specifications. Same bullet point: The second paragraph seems out of place; was it intended to be its own bullet point? 4th bullet point: The second sentence seems like a non-sequiter. I suggest a top-level bullet point for "Analyzing opportunities to improve privacy..." From nobody Fri Feb 9 09:04:15 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F041412D77B; Fri, 9 Feb 2018 09:04:13 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.72.0 Auto-Submitted: auto-generated Precedence: bulk Cc: emu@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-ID: <151819585397.1301.18231653830870910365.idtracker@ietfa.amsl.com> Date: Fri, 09 Feb 2018 09:04:13 -0800 Archived-At: Subject: [Emu] WG Review: EAP Method Update (emu) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2018 17:04:14 -0000 A new IETF WG has been proposed in the Security Area. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by 2018-02-19. EAP Method Update (emu) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: TBD Assigned Area Director: Kathleen Moriarty Security Area Directors: Kathleen Moriarty Eric Rescorla Mailing list: Address: emu@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/emu Archive: https://mailarchive.ietf.org/arch/search/?email_list=emu Group page: https://datatracker.ietf.org/group/emu/ Charter: https://datatracker.ietf.org/doc/charter-ietf-emu/ The Extensible Authentication Protocol (EAP) [RFC 3748] is a network access authentication framework used, for instance, in 802.11 and VPN networks and mobile networks. EAP itself is a simple protocol and actual authentication happens in EAP methods. Over 50 different EAP methods exist, including several methods developed in the IETF, and support for EAP exists in a broad set of different devices. Previous larger EAP-related efforts at the IETF included rewriting the base EAP protocol documentation and the development of several standards track EAP methods. EAP methods are generally based on existing other security technologies, such as TLS, SIM cards, and various algorithms. Some of these technologies continue to evolve. And the understanding of security threats in today's Internet evolves as well, which has driven some of the evolution in these underlying technologies. At the same time, some new use cases for EAP have been identified, such as broader use of EAP in mobile network authentication. This working group has been chartered to provide updates to some commonly used EAP method. Specifically, the working group shall produce documents to: - Provide a guidance or update to enable the use of TLS 1.3 in the context of EAP TLS (RFC 5216). Update the security considerations relating to EAP TLS, to document the implications of using new vs. old TLS version, any recently gained new knowledge on vulnerabilities, and the possible implications of pervasive survellaince or other new concerns. - Update the EAP-AKA' specification (RFC 5448) to ensure that its capability to provide a cryptographic binding to network context stays in sync with what updates may come to the referenced 3GPP specifications through the use of EAP in 5G. Also, the group should document any recently gained new knowledge on vulnerabilities or the possible implications of pervasive surveillance or other new concerns. - Define session identifiers for fast re-authentication for EAP-SIM, EAP-AKA, and EAP-AKA’. The lack of this definition is a recently discovered bug in the original RFCs. - Develop an extension to EAP-AKA' such that Perfect Forward Secrecy can be provided. There may also be privacy improvements that have become feasible with the introduction of recent identity privacy improvements in 3GPP networks. - Gather experience regarding the use of large certificate and certificate chain sizes in the context of EAP-TLS (all versions), as some implementations and access networks may limit the number of EAP packet exchanges that can be handled. Document operational recommendations or other mitigation strategies to avoid issues. In all of the above, it is a requirement that none of the updates break backwards compatibility with existing specifications or implementations. The current RFCs shall not be obsoleted but rather updated with either new information or instructions on what is needed, for instance, to employ a new TLS version. The working group is expected to stay in close collaboration with the EAP deployment community, the TLS working group (for EAP-TLS work), and the 3GPP security architecture group (for EAP-AKA' work). Milestones: Apr 2018 - WG adopts initial draft on guidance for EAP TLS with TLS 1.3 Apr 2018 - Begin work on EAP-AKA update, RFC5448-bis May 2018 - Adopt draft for extension to EAP-AKA to support forward secrecy Jul 2018 - Adopt draft to define session identifiers for fast re-authentication for EAP-SIM, EAP-AKA, and EAP-AKA Jul 2018 - Adopt draft on operational recommendations for large certificate and chain sizes Feb 2019 - Working group last call for EAP-AKA update, RFC5448-bis From nobody Sun Feb 18 03:26:04 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51D92124B17; Sun, 18 Feb 2018 03:25:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJ_mId6OZM9D; Sun, 18 Feb 2018 03:25:56 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 20152120724; Sun, 18 Feb 2018 03:25:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id CA58D6601CA; Sun, 18 Feb 2018 13:25:54 +0200 (EET) Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMULoTaLNmSR; Sun, 18 Feb 2018 13:25:53 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 11F5C6601B3; Sun, 18 Feb 2018 13:25:53 +0200 (EET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Jari Arkko In-Reply-To: <07c2cbc1-6bc2-7a9a-e010-99a229131761@ericsson.com> Date: Sun, 18 Feb 2018 13:25:52 +0200 Cc: The IESG , emu-chairs@ietf.org, emu@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <720C6B8D-8E95-4192-A4A0-1CB7693364CA@piuha.net> References: <151759093372.31806.10796579098479490610.idtracker@ietfa.amsl.com> <07c2cbc1-6bc2-7a9a-e010-99a229131761@ericsson.com> To: Mohit Sethi , Kathleen Moriarty X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Emu] Kathleen Moriarty's Yes on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 11:25:58 -0000 Mohit, Kathleen, I=E2=80=99d suggest editing the current milestones as follows. The edit = and schedule suggestions are based in part on what I think the 3GPP schedules are = going to be. They need some stuff soon (e.g., any fixes to existing = EAP-AKA=E2=80=99; there=E2=80=99s a technical specification with a few paragraphs labeled = =E2=80=9Cmove these to IETF RFC when it is updated) but some of the other things (EAP TLS = 1.3, PFS solutions) can probably wait until their 5G phase 2 work. Then again, for the sake of resolving issues in existing RFCs and=20 general issues in EAP usage, we also want to pursue the other stuff. These are however my suggestions only; others may see priorities and order differently. So consider this proposal as a straw-man only. OLD: Apr 2018 - WG adopts initial draft on guidance for EAP TLS with TLS 1.3 Apr 2018 - Begin work on EAP-AKA update, RFC5448-bis May 2018 - Adopt draft for extension to EAP-AKA to support forward = secrecy Jul 2018 - Adopt draft to define session identifiers for fast re-authentication for EAP-SIM, EAP-AKA, and EAP-AKA Jul 2018 - Adopt draft on operational recommendations for large = certificate and chain sizes Feb 2019 - Working group last call for EAP-AKA update, RFC5448-bis NEW: Mar 2018 - WG established Apr 2018 - WG adopts initial draft on guidance for EAP TLS with TLS 1.3 Apr 2018 - WG adopts initial draft on EAP-AKA update, RFC5448-bis, including definition session identifiers for fast re-authentication for = EAP-AKA' Sep 2018 - WG last call on EAP-AKA update, RFC5448-bis Oct 2018 - WG adopts initial draft on extension to EAP-AKA to support = forward secrecy Oct 2018 - WG adopts initial draft on definition of session identifiers = for fast re-authentication in EAP-SIM and EAP-AKA Nov 2018 - WG last call on guidance for EAP TLS with TLS 1.3 Dec 2018 - WG adopts initial draft on operational recommendations for = large certificate and chain sizes Jan 2019 - WG last call on definition of session identifiers for fast re-authentication in EAP-SIM and EAP-AKA Feb 2019 - WG last call on extension to EAP-AKA to support forward = secrecy May 2019 - WG last call on operational recommendations for large certificate and chain sizes Jari From nobody Sun Feb 18 03:46:20 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E70D124BAC; Sun, 18 Feb 2018 03:46:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCbiDUk9LP0r; Sun, 18 Feb 2018 03:46:12 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id D67CA124B18; Sun, 18 Feb 2018 03:46:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F40686601CA; Sun, 18 Feb 2018 13:46:10 +0200 (EET) Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nVtcQzfP60b6; Sun, 18 Feb 2018 13:46:09 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id C66276601B3; Sun, 18 Feb 2018 13:46:09 +0200 (EET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Jari Arkko In-Reply-To: <151805602957.17143.8761779262512562317.idtracker@ietfa.amsl.com> Date: Sun, 18 Feb 2018 13:46:09 +0200 Cc: The IESG , emu-chairs@ietf.org, emu@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <4A85E1B5-1FC1-4F79-B58C-DE9A77549AE4@piuha.net> References: <151805602957.17143.8761779262512562317.idtracker@ietfa.amsl.com> To: Ben Campbell X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Emu] Ben Campbell's No Objection on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 11:46:14 -0000 Hi Ben, And thanks for your feedback. > First bullet point: "or other new concerns." makes this very open = ended. Is > this planned to be a standing working group? If not, can we put some > constraints around "other new concerns=E2=80=9D? Understood. Note that the sentence starts with =E2=80=9CUpdate the security = considerations=E2=80=A6=E2=80=9D so the goal of these updates is about discovering new vulnerabilities = and the like; not any random other concerns. That being said, the text = already covers new vulnerabilities, so may be this is merely unnecessary text. How about the following text: OLD: Update the security considerations relating to EAP TLS, to document the implications of using new vs. old TLS version, any recently gained new knowledge on vulnerabilities, and the possible implications of pervasive survellaince or other new concerns. NEW: Update the security considerations relating to EAP TLS, to document the implications of using new vs. old TLS version, any recently gained new knowledge on vulnerabilities, and the possible implications of pervasive surveillance. (Also updates a typo.) > The prohibition against obsoleting RFCs seems harsh. It's possible to = require > backwards compatibility without this restriction. I think it should be = up to > the working group to decide whether work can be better organized using = updates > or bis-drafts. There was a detailed discussion among the participants about this aspect = and a reasonable, strong opinion that the current EAP-TLS RFC remain as the primary, and that the new RFC would be an update to it when it comes to TLS 1.3. That being said, hmm=E2=80=A6 even my own draft for EAP-AKA=E2=80=99 bis = currently says =E2=80=9CObseletes RFC 5448 (if approved=E2=80=9D)=E2=80=A6 so=E2=80=A6 = how about this: OLD: The current RFCs shall not be obsoleted but rather updated with either new information or instructions on what is needed, for instance, to employ a new TLS version. NEW: The current EAP-TLS RFCs shall not be obsoleted but rather updated with either new information or instructions on what is needed, for instance, to employ a new TLS version. > -3rd paragraph: "And the > understanding of security threats in today's Internet evolves as > well,..." >=20 > I suggest dropping =E2=80=9CAnd" Yes. For Kathleen=E2=80=99s benefit, listing this in OLD/NEW style: OLD: And the understanding of security threats in today's Internet evolves as well, which has driven some of the evolution in these underlying technologies. NEW: The understanding of security threats in today's Internet evolves as well, which has driven some of the evolution in these underlying technologies. > -- 2nd bullet: This is a bit hard to parse. I suggest: >=20 > OLD: > Update the EAP-AKA' specification (RFC 5448) to ensure that its > capability to provide a cryptographic binding to network context > stays in sync with what updates may come to the referenced 3GPP > specifications through the use of EAP in 5G. > NEW: > Update the EAP-AKA' specification (RFC 5448) to ensure that its > capability to provide a cryptographic binding to network context > stays in sync with any 5G related updates to the referenced 3GPP > specifications. Seems good. Thanks. > Same bullet point: The second paragraph seems out of place; was it = intended to > be its own bullet point? I don=E2=80=99t have a strong opinion, but the two somewhat separate = issues were listed under the same bullet item since both of them should go into the same draft (rfc5448bis). The EAP TLS bullet item does the same thing, i.e., update tech + describe new knowledge of vulnerabilities. > 4th bullet point: The second sentence seems like a non-sequiter. I = suggest a > top-level bullet point for "Analyzing opportunities to improve = privacy..." I=E2=80=99d be fine with that. Suggested text: OLD: - Develop an extension to EAP-AKA' such that Perfect Forward Secrecy can be provided. There may also be privacy improvements that have become feasible with the introduction of recent identity privacy improvements in 3GPP networks. NEW: - Analysing opportunities to improve privacy in EAP-AKA=E2=80=99.=20 Develop an extension to EAP-AKA' such that Perfect Forward Secrecy can be provided. There may also be other privacy improvements that have become feasible with the introduction of recent identity privacy improvements in 3GPP networks. Jari From nobody Sun Feb 18 03:48:50 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5DB124B18; Sun, 18 Feb 2018 03:48:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpGS8JlpsSRy; Sun, 18 Feb 2018 03:48:47 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A4C36124B17; Sun, 18 Feb 2018 03:48:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0DD536601CA; Sun, 18 Feb 2018 13:48:46 +0200 (EET) Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzeBTkOob-sJ; Sun, 18 Feb 2018 13:48:45 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 1FA306601B3; Sun, 18 Feb 2018 13:48:45 +0200 (EET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Jari Arkko In-Reply-To: <151784861975.5719.2261756268635049659.idtracker@ietfa.amsl.com> Date: Sun, 18 Feb 2018 13:48:44 +0200 Cc: The IESG , emu-chairs@ietf.org, emu@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <151784861975.5719.2261756268635049659.idtracker@ietfa.amsl.com> To: =?utf-8?Q?Mirja_K=C3=BChlewind?= X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Emu] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_charter?= =?utf-8?q?-ietf-emu-04-00=3A_=28with_COMMENT=29?= X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 11:48:48 -0000 Mirja, > I would actually rather like to see milestones for when the work is = supposed to > be finished (send to IESG for publication) than when it is supposed to = start > (wg adoption) as the first is probably harder to achieve in time than = the > second. I suggested edits to the milestones in a response to Kathleen=E2=80=99s comments, and the suggested edits include having both start (adopt) and end (WGLC) for all work items. Does that work for you? (Although some of our charters speak about WGLC and others about sending to IESG=E2=80=A6 not sure the difference matters.) Jari From nobody Sun Feb 18 03:51:15 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F79E124BAC; Sun, 18 Feb 2018 03:51:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zwEAv721nr2i; Sun, 18 Feb 2018 03:51:12 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 65181124B17; Sun, 18 Feb 2018 03:51:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AB05A6601CA; Sun, 18 Feb 2018 13:51:11 +0200 (EET) Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03f6ULMSfljK; Sun, 18 Feb 2018 13:51:10 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 8EC786601B3; Sun, 18 Feb 2018 13:51:10 +0200 (EET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Jari Arkko In-Reply-To: <151802798426.4831.16330955195087990127.idtracker@ietfa.amsl.com> Date: Sun, 18 Feb 2018 13:51:09 +0200 Cc: The IESG , emu-chairs@ietf.org, emu@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <8299E98C-A069-439F-869F-366D6204BBC3@piuha.net> References: <151802798426.4831.16330955195087990127.idtracker@ietfa.amsl.com> To: Spencer Dawkins X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Emu] Spencer Dawkins' No Objection on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 11:51:13 -0000 > "This working group has been chartered to provide updates to some > commonly used EAP method." >=20 > really singular? Or should it be "commonly used EAP methods=E2=80=9D? Uh=E2=80=A6 a bug. Thanks for the careful read. For Kathleen: OLD: This working group has been chartered to provide updates to some commonly used EAP method. NEW: This working group has been chartered to provide updates to some commonly used EAP methods. Jari From nobody Sun Feb 18 09:32:36 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6C76120725; Sun, 18 Feb 2018 09:32:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.89 X-Spam-Level: X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y1vqtwzYgmGL; Sun, 18 Feb 2018 09:32:32 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C43C1200B9; Sun, 18 Feb 2018 09:32:32 -0800 (PST) Received: from [10.0.1.105] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w1IHWRs3065366 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 18 Feb 2018 11:32:28 -0600 (CST) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.105] From: Ben Campbell Message-Id: <91E74A49-A843-45AB-AF70-AD57CEAA90FD@nostrum.com> Content-Type: multipart/signed; boundary="Apple-Mail=_A6D282A7-00C5-46F9-9C40-02A545BDDB9E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Date: Sun, 18 Feb 2018 11:32:26 -0600 In-Reply-To: <4A85E1B5-1FC1-4F79-B58C-DE9A77549AE4@piuha.net> Cc: The IESG , emu-chairs@ietf.org, emu@ietf.org To: Jari Arkko References: <151805602957.17143.8761779262512562317.idtracker@ietfa.amsl.com> <4A85E1B5-1FC1-4F79-B58C-DE9A77549AE4@piuha.net> X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [Emu] Ben Campbell's No Objection on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 17:32:35 -0000 --Apple-Mail=_A6D282A7-00C5-46F9-9C40-02A545BDDB9E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Thanks, Jari, this all looks good to me. Ben. > On Feb 18, 2018, at 5:46 AM, Jari Arkko wrote: >=20 > Hi Ben, >=20 > And thanks for your feedback. >=20 >> First bullet point: "or other new concerns." makes this very open = ended. Is >> this planned to be a standing working group? If not, can we put some >> constraints around "other new concerns=E2=80=9D? >=20 > Understood. >=20 > Note that the sentence starts with =E2=80=9CUpdate the security = considerations=E2=80=A6=E2=80=9D > so the goal of these updates is about discovering new vulnerabilities = and > the like; not any random other concerns. That being said, the text = already > covers new vulnerabilities, so may be this is merely unnecessary text. >=20 > How about the following text: >=20 > OLD: > Update the security > considerations relating to EAP TLS, to document the implications > of using new vs. old TLS version, any recently gained new > knowledge on vulnerabilities, and the possible implications of > pervasive survellaince or other new concerns. >=20 > NEW: >=20 > Update the security > considerations relating to EAP TLS, to document the implications > of using new vs. old TLS version, any recently gained new > knowledge on vulnerabilities, and the possible implications of > pervasive surveillance. >=20 > (Also updates a typo.) >=20 >> The prohibition against obsoleting RFCs seems harsh. It's possible to = require >> backwards compatibility without this restriction. I think it should = be up to >> the working group to decide whether work can be better organized = using updates >> or bis-drafts. >=20 > There was a detailed discussion among the participants about this = aspect and > a reasonable, strong opinion that the current EAP-TLS RFC remain as > the primary, and that the new RFC would be an update to it when it = comes > to TLS 1.3. >=20 > That being said, hmm=E2=80=A6 even my own draft for EAP-AKA=E2=80=99 = bis currently says > =E2=80=9CObseletes RFC 5448 (if approved=E2=80=9D)=E2=80=A6 so=E2=80=A6 = how about this: >=20 > OLD: >=20 > The current RFCs shall not be obsoleted but > rather updated with either new information or instructions on > what is needed, for instance, to employ a new TLS version. >=20 > NEW: >=20 > The current EAP-TLS RFCs shall not be obsoleted but > rather updated with either new information or instructions on > what is needed, for instance, to employ a new TLS version. >=20 >> -3rd paragraph: "And the >> understanding of security threats in today's Internet evolves as >> well,..." >>=20 >> I suggest dropping =E2=80=9CAnd" >=20 > Yes. >=20 > For Kathleen=E2=80=99s benefit, listing this in OLD/NEW style: >=20 > OLD: >=20 > And the > understanding of security threats in today's Internet evolves as > well, which has driven some of the evolution in these underlying > technologies. >=20 > NEW: >=20 > The > understanding of security threats in today's Internet evolves as > well, which has driven some of the evolution in these underlying > technologies. >=20 >> -- 2nd bullet: This is a bit hard to parse. I suggest: >>=20 >> OLD: >> Update the EAP-AKA' specification (RFC 5448) to ensure that its >> capability to provide a cryptographic binding to network context >> stays in sync with what updates may come to the referenced 3GPP >> specifications through the use of EAP in 5G. >> NEW: >> Update the EAP-AKA' specification (RFC 5448) to ensure that its >> capability to provide a cryptographic binding to network context >> stays in sync with any 5G related updates to the referenced 3GPP >> specifications. >=20 > Seems good. Thanks. >=20 >> Same bullet point: The second paragraph seems out of place; was it = intended to >> be its own bullet point? >=20 > I don=E2=80=99t have a strong opinion, but the two somewhat separate = issues > were listed under the same bullet item since both of them should > go into the same draft (rfc5448bis). The EAP TLS bullet item > does the same thing, i.e., update tech + describe new knowledge > of vulnerabilities. >=20 >> 4th bullet point: The second sentence seems like a non-sequiter. I = suggest a >> top-level bullet point for "Analyzing opportunities to improve = privacy..." >=20 > I=E2=80=99d be fine with that. Suggested text: >=20 > OLD: >=20 > - Develop an extension to EAP-AKA' such that Perfect Forward Secrecy > can be provided. There may also be privacy improvements that > have become feasible with the introduction of recent identity > privacy improvements in 3GPP networks. >=20 > NEW: >=20 > - Analysing opportunities to improve privacy in EAP-AKA=E2=80=99. >=20 > Develop an extension to EAP-AKA' such that Perfect Forward Secrecy > can be provided. >=20 > There may also be other privacy improvements that > have become feasible with the introduction of recent identity > privacy improvements in 3GPP networks. >=20 > Jari >=20 --Apple-Mail=_A6D282A7-00C5-46F9-9C40-02A545BDDB9E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlqJuKoACgkQgFZKbJXz 1A0XjQ//fDpz3F3cr9qsabZfNfZw47Pls/QD4o9gDhucBpLOJ9UhOnnATFYhmKjg A0Q7A8qZ4UTfXfmDl6JlhN7LMJnw8JDUHseW9AT3OjLV/asDMHq/OKR2TUYnT4P+ jPICLxUBc4rc3hQWCX51m0lysZVEBGOz1eAlgXErooHNIeyPFMwGsRf/yOi64XpS UAvPxFvv5n5pGCo80k/0+XI74O8u8LzkRjCVGR95Pu0WMa30ZYWprJ0D1Zge/xti L6Gvw4yFmD1ljnFf2Z2fI7F81soY5WONypCo6UI4s1t3D/y781vekS/iHZx/jeb1 RF3//H4lAsruRpWDBtRAs6r7OmuV4mZNX//K/sl134SSSD/Eox3+tQF1PudU+3eO o6wJoaValnh8uE+gEqZAj6KWO2otMpxZ3LmPx8t0yKPgmlRgX8AWODHpQ//nqLka 7RpAj86Z6qrebX5Tcn6iXL7MMoTSoAHxaUP5MBl1cojtIxJLe3jeeU4J9N80tVZo ZtMgIxd1lZvHD0Ju6eGcjUrSuBHbtWEkvzbyj7wXy842HsAd1qB5nn8p+BX2EN7A /vAhYWzR9d25RQtiqlTuFBaFmCGvC6IF1or0NsOjzD+UIdkTo2mm+VN2xKXQK6dd ko44yz4HWwfrOVRyaA556VCV1XeSqmPKLUAUAqW6hgXOO9lndes= =pRbZ -----END PGP SIGNATURE----- --Apple-Mail=_A6D282A7-00C5-46F9-9C40-02A545BDDB9E-- From nobody Mon Feb 19 08:35:58 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C56A5120713; Mon, 19 Feb 2018 08:35:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMt9Z6mjeeX5; Mon, 19 Feb 2018 08:35:54 -0800 (PST) Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D11B61205F0; Mon, 19 Feb 2018 08:35:54 -0800 (PST) Received: by mail-pg0-x229.google.com with SMTP id l4so3890275pgp.11; Mon, 19 Feb 2018 08:35:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=jqrrMSfsgcsVn1Vn/xHlW9WCM8QVQ2Im/djwdOwyV40=; b=Kt2LrSxH9WS6pJeXMOfTIdng6JWsiKhnp9yAoDpjrXOEx6jzgBgScAMEF/AjGljOwo 10vt7VNehpqpF7oVSbQ4SkPs3lzPdTa2UPLndW8tMRDK5ihV+/xkGoqn9AB1HD4caJtz p4osXhEBnrLlaYARCYMaUaQHIhoj/DJQJGqGzY7hOFI9yq0ZsurL3ke4wyy2D/bCBfe7 XBkQMR4WXqmVzCjYBae/2M8Ive2uIewBJg5Q3pJfiIQNtQq24JpMGmrkJh9hVUhwjdjZ e/hW/IE4yhCXgED4oB49MuI+98+49GdPQlw2hx35V2zrsmfrpp3TOgrLWn7oywyNQAnQ Sb7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=jqrrMSfsgcsVn1Vn/xHlW9WCM8QVQ2Im/djwdOwyV40=; b=GnTFid73t/NrkPKS3eZeJ9ZfxJv1oSGC/AjQOrS+Xe8SqiAS38vV+xtptCaGZHGy4x kBOWbvIKXWFYLI/CgBuX9nBVB0ML4OZAGDBbaStT2K1DNW3AyORn95xluELpXpcRJLSZ aztbERxIfBB2jKEqy/TBYwQYWX9Or8WYQnVYhJfaUTUZN+VQ1pszyu+MSu0WTN0G9yML oVkM6z9lKIgGq5QLF/me4TIkDsM37YsOUccJIVT1FB54FTlfAJlTBwb2498GK0LCeg7F nQckzdcRtQj+aGuT1WsZZVziyioAeUEtXPDvpbZQd6y2WfsTf2ug0+5kyL8nen+j9id3 1PRg== X-Gm-Message-State: APf1xPC1horhIBJsy6Ost+KE9D4Lp3eVGLgFQAG/VWwJVKC1s4zIIa7A wmlbRlm/SirilYE9pa8Ju+wv10jjctAaZqIN1Tg= X-Google-Smtp-Source: AH8x2250PsS/4lQsg3JiwTszC5AW+2uIdxS9xDfooo4tbZrbLhFVemPxLYzyxCFiOzPBxqPTGohkNbhuqrLL+W5EfgY= X-Received: by 10.99.145.194 with SMTP id l185mr12403481pge.394.1519058154193; Mon, 19 Feb 2018 08:35:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.229.67 with HTTP; Mon, 19 Feb 2018 08:35:13 -0800 (PST) In-Reply-To: <91E74A49-A843-45AB-AF70-AD57CEAA90FD@nostrum.com> References: <151805602957.17143.8761779262512562317.idtracker@ietfa.amsl.com> <4A85E1B5-1FC1-4F79-B58C-DE9A77549AE4@piuha.net> <91E74A49-A843-45AB-AF70-AD57CEAA90FD@nostrum.com> From: Kathleen Moriarty Date: Mon, 19 Feb 2018 11:35:13 -0500 Message-ID: To: Ben Campbell Cc: Jari Arkko , emu@ietf.org, The IESG , emu-chairs@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Emu] Ben Campbell's No Objection on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2018 16:35:57 -0000 Thank you Ben and Jari. The updates will appear shortly int he new version= . Best regards, Kathleen On Sun, Feb 18, 2018 at 12:32 PM, Ben Campbell wrote: > Thanks, Jari, this all looks good to me. > > Ben. > >> On Feb 18, 2018, at 5:46 AM, Jari Arkko wrote: >> >> Hi Ben, >> >> And thanks for your feedback. >> >>> First bullet point: "or other new concerns." makes this very open ended= . Is >>> this planned to be a standing working group? If not, can we put some >>> constraints around "other new concerns=E2=80=9D? >> >> Understood. >> >> Note that the sentence starts with =E2=80=9CUpdate the security consider= ations=E2=80=A6=E2=80=9D >> so the goal of these updates is about discovering new vulnerabilities an= d >> the like; not any random other concerns. That being said, the text alrea= dy >> covers new vulnerabilities, so may be this is merely unnecessary text. >> >> How about the following text: >> >> OLD: >> Update the security >> considerations relating to EAP TLS, to document the implications >> of using new vs. old TLS version, any recently gained new >> knowledge on vulnerabilities, and the possible implications of >> pervasive survellaince or other new concerns. >> >> NEW: >> >> Update the security >> considerations relating to EAP TLS, to document the implications >> of using new vs. old TLS version, any recently gained new >> knowledge on vulnerabilities, and the possible implications of >> pervasive surveillance. >> >> (Also updates a typo.) >> >>> The prohibition against obsoleting RFCs seems harsh. It's possible to r= equire >>> backwards compatibility without this restriction. I think it should be = up to >>> the working group to decide whether work can be better organized using = updates >>> or bis-drafts. >> >> There was a detailed discussion among the participants about this aspect= and >> a reasonable, strong opinion that the current EAP-TLS RFC remain as >> the primary, and that the new RFC would be an update to it when it comes >> to TLS 1.3. >> >> That being said, hmm=E2=80=A6 even my own draft for EAP-AKA=E2=80=99 bis= currently says >> =E2=80=9CObseletes RFC 5448 (if approved=E2=80=9D)=E2=80=A6 so=E2=80=A6 = how about this: >> >> OLD: >> >> The current RFCs shall not be obsoleted but >> rather updated with either new information or instructions on >> what is needed, for instance, to employ a new TLS version. >> >> NEW: >> >> The current EAP-TLS RFCs shall not be obsoleted but >> rather updated with either new information or instructions on >> what is needed, for instance, to employ a new TLS version. >> >>> -3rd paragraph: "And the >>> understanding of security threats in today's Internet evolves as >>> well,..." >>> >>> I suggest dropping =E2=80=9CAnd" >> >> Yes. >> >> For Kathleen=E2=80=99s benefit, listing this in OLD/NEW style: >> >> OLD: >> >> And the >> understanding of security threats in today's Internet evolves as >> well, which has driven some of the evolution in these underlying >> technologies. >> >> NEW: >> >> The >> understanding of security threats in today's Internet evolves as >> well, which has driven some of the evolution in these underlying >> technologies. >> >>> -- 2nd bullet: This is a bit hard to parse. I suggest: >>> >>> OLD: >>> Update the EAP-AKA' specification (RFC 5448) to ensure that its >>> capability to provide a cryptographic binding to network context >>> stays in sync with what updates may come to the referenced 3GPP >>> specifications through the use of EAP in 5G. >>> NEW: >>> Update the EAP-AKA' specification (RFC 5448) to ensure that its >>> capability to provide a cryptographic binding to network context >>> stays in sync with any 5G related updates to the referenced 3GPP >>> specifications. >> >> Seems good. Thanks. >> >>> Same bullet point: The second paragraph seems out of place; was it inte= nded to >>> be its own bullet point? >> >> I don=E2=80=99t have a strong opinion, but the two somewhat separate iss= ues >> were listed under the same bullet item since both of them should >> go into the same draft (rfc5448bis). The EAP TLS bullet item >> does the same thing, i.e., update tech + describe new knowledge >> of vulnerabilities. >> >>> 4th bullet point: The second sentence seems like a non-sequiter. I sugg= est a >>> top-level bullet point for "Analyzing opportunities to improve privacy.= .." >> >> I=E2=80=99d be fine with that. Suggested text: >> >> OLD: >> >> - Develop an extension to EAP-AKA' such that Perfect Forward Secrecy >> can be provided. There may also be privacy improvements that >> have become feasible with the introduction of recent identity >> privacy improvements in 3GPP networks. >> >> NEW: >> >> - Analysing opportunities to improve privacy in EAP-AKA=E2=80=99. >> >> Develop an extension to EAP-AKA' such that Perfect Forward Secrecy >> can be provided. >> >> There may also be other privacy improvements that >> have become feasible with the introduction of recent identity >> privacy improvements in 3GPP networks. >> >> Jari >> > > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu > --=20 Best regards, Kathleen From nobody Mon Feb 19 08:37:08 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5B271243F6 for ; Mon, 19 Feb 2018 08:37:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFPWo6LOR3LE for ; Mon, 19 Feb 2018 08:37:05 -0800 (PST) Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09A351241F8 for ; Mon, 19 Feb 2018 08:37:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net; b=M47Odzdys8Z8hBUw2PweC6z8xPdZke3SmoDaUQZE89I+3+W+dpV32ix43pC2U9tYhw9tX+JrJrlu23vSFRCKpWCl6HAChDNjJK8clyHS93/IFRlWFYMyz63dQim3MLjsfq0nEUKerHiJR9NyStUhgikgnB/FRLcGHR5fLqYrJnM=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost; Received: (qmail 24553 invoked from network); 19 Feb 2018 17:36:02 +0100 Received: from mue-88-130-61-043.dsl.tropolys.de (HELO ?192.168.178.33?) (88.130.61.43) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 19 Feb 2018 17:36:02 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: "Mirja Kuehlewind (IETF)" In-Reply-To: Date: Mon, 19 Feb 2018 17:36:01 +0100 Cc: emu@ietf.org, The IESG , emu-chairs@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <41632F0A-823F-46FB-9E46-BA609A6154B2@kuehlewind.net> References: <151784861975.5719.2261756268635049659.idtracker@ietfa.amsl.com> To: Jari Arkko X-Mailer: Apple Mail (2.3445.5.20) X-PPP-Message-ID: <20180219163602.24546.42607@lvps83-169-45-111.dedicated.hosteurope.de> X-PPP-Vhost: kuehlewind.net Archived-At: Subject: Re: [Emu] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_charter?= =?utf-8?q?-ietf-emu-04-00=3A_=28with_COMMENT=29?= X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2018 16:37:07 -0000 Yes. I don=E2=80=99t see a big difference between =E2=80=9EWGLC" and = "send to IESG=E2=80=9C but it=E2=80=99s good to have a deadline! > Am 18.02.2018 um 12:48 schrieb Jari Arkko : >=20 > Mirja, >=20 >> I would actually rather like to see milestones for when the work is = supposed to >> be finished (send to IESG for publication) than when it is supposed = to start >> (wg adoption) as the first is probably harder to achieve in time than = the >> second. >=20 > I suggested edits to the milestones in a response to Kathleen=E2=80=99s > comments, and the suggested edits include having both start > (adopt) and end (WGLC) for all work items. Does that work for > you? >=20 > (Although some of our charters speak about WGLC and others > about sending to IESG=E2=80=A6 not sure the difference matters.) >=20 > Jari >=20 From nobody Mon Feb 19 08:37:20 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD43126B7E; Mon, 19 Feb 2018 08:37:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RceQ1u03XOAO; Mon, 19 Feb 2018 08:37:08 -0800 (PST) Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E83B9120713; Mon, 19 Feb 2018 08:37:07 -0800 (PST) Received: by mail-pf0-x233.google.com with SMTP id g17so2344596pfh.1; Mon, 19 Feb 2018 08:37:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=lr1t+h6sBcqAgtdXuzxQ28u2uR9R8PVD7ZzMuhO8UFs=; b=hhEH4/V75bXg/k301TcKQj5BFNuC3UiXLClPZjXJTzF+ypBbvpF+RHkdGxe4qzDkXo KNf5yuZHk0xnZmtvL5rtjQQt+fvZicAMvXOq5Mfd7qXVzDtLkrmXVFUQpePwnwaHBGmg Qo3lE9SUjQDeh+Rfcak81wTyzjojpDiXTi1PGbbbsZc1AEjYmCAuzO/tgniHFrUcfjmu FQpqtgQDt80UW/z98hWeRA7T4zxljVqwNCCrPUF56S6sg16xg1pC3LySLgfjPgoI7OLk 3OLOZlvquOEy+gy1W2FLuTVKU7Hqz0kp9kgPW6UTDD2XuHT+FA2wxeUWp30+uFYMA73u wGjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=lr1t+h6sBcqAgtdXuzxQ28u2uR9R8PVD7ZzMuhO8UFs=; b=hroCH0vkrop1YGnVN8XfuuGAEGpt5uGqX/S6bxy11ZzdGBc1p8JQm3RiE3jjnenC/c Mps11Yt0bGvIKVd379aE2SsRJSsqhZUQRTq0yE7mmo13RDZDGMLGIrY2ifRaC2KBI9AR 8oh9uFcyr/hhUOyeWWEKhWa+1EgPvfrMlzTYSolh4Bz3XltULXix2W2g01gF6xh/hKh/ VH6FuZEZYO6oC2io0kj+gBhKec+GMt93CsnwEWFkdZ8OZxQEaBxCcAaRwGIwYasl1pW1 hvWg7Ca6+KJO586h6gngFDAc6d7pKkmxb8NM+EaRsQgH7FS0dz7qjp1OYpEZ/kSkgRaR w0zQ== X-Gm-Message-State: APf1xPBH4ZOlFi1dak3etUAUMsXGx1+XTLxi6emvstCXS8y3kINM4dJZ 72HzZ5Dq4OtT/MkwN7paBptpfo++VVDPjjLQjRE= X-Google-Smtp-Source: AH8x225bV0uQniMHcYkxCLqo1zRnZQgVzhTUF9hDGg3vjf/Cjk3UucxLOyR/U91TeFbsWhhQNdqhPsD5ubAMDBZt7IY= X-Received: by 10.98.56.150 with SMTP id f144mr8044115pfa.150.1519058227541; Mon, 19 Feb 2018 08:37:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.229.67 with HTTP; Mon, 19 Feb 2018 08:36:27 -0800 (PST) In-Reply-To: <8299E98C-A069-439F-869F-366D6204BBC3@piuha.net> References: <151802798426.4831.16330955195087990127.idtracker@ietfa.amsl.com> <8299E98C-A069-439F-869F-366D6204BBC3@piuha.net> From: Kathleen Moriarty Date: Mon, 19 Feb 2018 11:36:27 -0500 Message-ID: To: Jari Arkko Cc: Spencer Dawkins , emu@ietf.org, The IESG , emu-chairs@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Emu] Spencer Dawkins' No Objection on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2018 16:37:09 -0000 Thank you Jari and Spencer. The update will appear shortly in the new vers= ion. On Sun, Feb 18, 2018 at 6:51 AM, Jari Arkko wrote: > >> "This working group has been chartered to provide updates to some >> commonly used EAP method." >> >> really singular? Or should it be "commonly used EAP methods=E2=80=9D? > > Uh=E2=80=A6 a bug. Thanks for the careful read. > > For Kathleen: > > OLD: > > This working group has been chartered to provide updates to some > commonly used EAP method. > > NEW: > > This working group has been chartered to provide updates to some > commonly used EAP methods. > > Jari > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu --=20 Best regards, Kathleen From nobody Mon Feb 19 08:51:02 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83CD8124BAC; Mon, 19 Feb 2018 08:50:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbgWzBaTIchi; Mon, 19 Feb 2018 08:50:55 -0800 (PST) Received: from mail-pl0-x229.google.com (mail-pl0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41866124B18; Mon, 19 Feb 2018 08:50:55 -0800 (PST) Received: by mail-pl0-x229.google.com with SMTP id s13so5913546plq.6; Mon, 19 Feb 2018 08:50:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=blWraPKg+RpUKao/ESIU5PjRLqX7RCyR9KsuUPDmbsU=; b=Ppw3BBTJ4Vb807NUKGB3sFIdTXVlm26pax5VX8Okdw7j+h6ACKbsA4dcQ3uU07b/nk tq1YWoHwyl2qM5fLMg8WxA81QC5h71+K0sXc2OdOSyRyzRK5/udaCTncbE4AD/7IbPz1 ZhDeI5jjm5+mkx4WyIB/rkGgXeMypO9zDtGkxO2c/nkwvWOSIKDGNclRIZIbwp8tBr8R ol+4cQLEbK7G5kT+IIBL13r9/mbzKZ2YPlhFPdndKL6uzWqzBWaYRwV00zC9G8Eb/9bD fZ5iMlB9MC4Hhs2G8Nk3RXBB61bG3vJU77Uxcx2zNyFndGzl4ZapLcYsCNSIrCd87mIw b3qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=blWraPKg+RpUKao/ESIU5PjRLqX7RCyR9KsuUPDmbsU=; b=tOPiFAVSHqPw2KDmFbpvuchBhogYRLORKp37TQUuNLBRMOArlXaxentcbAqINOcwyL wdeY9mj30Zl0yuwjGiZuhYFzcNhCdEpffz+iqTeAiJc7Qmj2gHBYgqdOLRR1bNI/EcVf MFwc+hPHE4gjWguKUe0p1uxYAmGMZguoMHbj1Fl1NkH618gSMPZKW5LtoLIy4Uwrj2uj +7osEnLQtr9S1/D7rlXRoIgHUqfvZ1sBWe6WXni1UZZYDWzAJkRaV6VmP1Asars77rO/ 8ZJhrfiV30LbOB9LcECDfHc6x+p2gnzPstAdlI2rlbG4YwmRqsqcxQUcLx/J4HEERIBf nSMQ== X-Gm-Message-State: APf1xPDhwLoSgTaRwZ652kp+ziY39167D74mlkGg+5RLs9NZGXpq2TP7 3439g/ZojeiE+ok5/SEe9qzc3Pv5P4YNJU5hMHI= X-Google-Smtp-Source: AH8x226vmwcFpx0co5yUeNkJIG5ErifMxXHW9HoySmEInUprNCYQ8e7pAy5OeVhOvsFdNgXD2T7tLV3cKZNluze5M3Q= X-Received: by 2002:a17:902:225:: with SMTP id 34-v6mr14854957plc.415.1519059054775; Mon, 19 Feb 2018 08:50:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.229.67 with HTTP; Mon, 19 Feb 2018 08:50:13 -0800 (PST) In-Reply-To: <720C6B8D-8E95-4192-A4A0-1CB7693364CA@piuha.net> References: <151759093372.31806.10796579098479490610.idtracker@ietfa.amsl.com> <07c2cbc1-6bc2-7a9a-e010-99a229131761@ericsson.com> <720C6B8D-8E95-4192-A4A0-1CB7693364CA@piuha.net> From: Kathleen Moriarty Date: Mon, 19 Feb 2018 11:50:13 -0500 Message-ID: To: Jari Arkko Cc: Mohit Sethi , The IESG , emu-chairs@ietf.org, emu@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Emu] Kathleen Moriarty's Yes on charter-ietf-emu-04-00: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2018 16:50:57 -0000 Thank you, Jari. The milestones have been updated. Best regards, Kathleen On Sun, Feb 18, 2018 at 6:25 AM, Jari Arkko wrote: > Mohit, Kathleen, > > I=E2=80=99d suggest editing the current milestones as follows. The edit a= nd schedule > suggestions are based in part on what I think the 3GPP schedules are goin= g > to be. They need some stuff soon (e.g., any fixes to existing EAP-AKA=E2= =80=99; > there=E2=80=99s a technical specification with a few paragraphs labeled = =E2=80=9Cmove these > to IETF RFC when it is updated) but some of the other things (EAP TLS 1.3= , > PFS solutions) can probably wait until their 5G phase 2 work. > > Then again, for the sake of resolving issues in existing RFCs and > general issues in EAP usage, we also want to pursue the other stuff. > > These are however my suggestions only; others may see priorities and > order differently. So consider this proposal as a straw-man only. > > OLD: > > Apr 2018 - WG adopts initial draft on guidance for EAP TLS with TLS 1.3 > Apr 2018 - Begin work on EAP-AKA update, RFC5448-bis > May 2018 - Adopt draft for extension to EAP-AKA to support forward secre= cy > Jul 2018 - Adopt draft to define session identifiers for fast > re-authentication for EAP-SIM, EAP-AKA, and EAP-AKA > Jul 2018 - Adopt draft on operational recommendations for large certific= ate > and chain sizes > Feb 2019 - Working group last call for EAP-AKA update, RFC5448-bis > > NEW: > > Mar 2018 - WG established > Apr 2018 - WG adopts initial draft on guidance for EAP TLS with TLS 1.3 > Apr 2018 - WG adopts initial draft on EAP-AKA update, RFC5448-bis, > including definition session identifiers for fast re-authentication for = EAP-AKA' > Sep 2018 - WG last call on EAP-AKA update, RFC5448-bis > Oct 2018 - WG adopts initial draft on extension to EAP-AKA to support fo= rward secrecy > Oct 2018 - WG adopts initial draft on definition of session identifiers = for fast > re-authentication in EAP-SIM and EAP-AKA > Nov 2018 - WG last call on guidance for EAP TLS with TLS 1.3 > Dec 2018 - WG adopts initial draft on operational recommendations for la= rge certificate > and chain sizes > Jan 2019 - WG last call on definition of session identifiers for fast > re-authentication in EAP-SIM and EAP-AKA > Feb 2019 - WG last call on extension to EAP-AKA to support forward secre= cy > May 2019 - WG last call on operational recommendations for large > certificate and chain sizes > > Jari > --=20 Best regards, Kathleen From nobody Mon Feb 19 08:51:44 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD3BB126DFB; Mon, 19 Feb 2018 08:51:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ynOwX5ZPo2lh; Mon, 19 Feb 2018 08:51:40 -0800 (PST) Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 899D6124BAC; Mon, 19 Feb 2018 08:51:40 -0800 (PST) Received: by mail-pf0-x243.google.com with SMTP id c143so2357687pfb.6; Mon, 19 Feb 2018 08:51:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=XFBTB2E5pq2rni/hAYOWT+NSDnhVrA5NDgIb0Jwj87s=; b=Snmlok0uHfKZBYfpfcuWiaRnLd1LCbh6aYuJY41KOgJCzkEKsHjbu2AgQcJ6w7Mj8w T+1MwVeVhfEkLxark21vC7mJSOzbE+w2xtu+STNugYTqklSuARJLrGUaWpjt2FMPvwoB l4emPoty5hE0uI6jseOowiSFoYbSMsjCrO7R7u5dRiSawYv1q5tKJdfkuMszSS2AKF36 zp0v7g2aVWudQyvZiowY0OO+UfD5fRjQczkSTBI2oHw5/CEkVWvfvcrZvHYU3et/dkl4 xTa1CcJlww6HjXSeAr1FFi95BogUiKZqDNbYYB53yI16LQmQuYb5plawmPpxSl84/EXf TCrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=XFBTB2E5pq2rni/hAYOWT+NSDnhVrA5NDgIb0Jwj87s=; b=VD2M4ZmgBDtDKqh3UM47pWt/2Tmd6FjI7I5JEprX5iRliATszAUj/3fCOwAfyEF0aj pj55GDNVVnuqmHAqV00Ee9aEZTRSejsM8M23kyuYgY84GUGYOacinykyKS/DrlT1+5IZ dZhBx1dhAH1ZnqJRdKdvXd2vvAxrv2CGpHfXKgoa4Zphsu2LMcJTpPpXM3FyIaFyNVmE LX7+afFFjfeyw1OpIfWzQ4tnoDgup+XgNml6rPfhGmyjD2dufRKL9l13AkBGZgce0QdD AAeLchT8RzXLvA8gMi3F6PF/EZdYzXCJRe/6j9KSwQVwPFGJK3bULj92lnHDyP8si58j USnA== X-Gm-Message-State: APf1xPC93MDFY7nZPxtxC+n89ZtJCY6l1M01fDwv7GkSPOGajOI8fs7l gayA+D0nTXVkDSCd8BfIhw0QeAQxrBKVItjGXE0= X-Google-Smtp-Source: AH8x225KfOdmN10JYtWQkyuFM4tIP4C8kNaKyMJsEEWWTrKHO4Sfp2dipop3Xg0tvaorpMZjOVOQsBUU35KSHoN9a/Q= X-Received: by 10.99.188.2 with SMTP id q2mr13037134pge.101.1519059100149; Mon, 19 Feb 2018 08:51:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.229.67 with HTTP; Mon, 19 Feb 2018 08:50:59 -0800 (PST) In-Reply-To: <41632F0A-823F-46FB-9E46-BA609A6154B2@kuehlewind.net> References: <151784861975.5719.2261756268635049659.idtracker@ietfa.amsl.com> <41632F0A-823F-46FB-9E46-BA609A6154B2@kuehlewind.net> From: Kathleen Moriarty Date: Mon, 19 Feb 2018 11:50:59 -0500 Message-ID: To: "Mirja Kuehlewind (IETF)" Cc: Jari Arkko , emu-chairs@ietf.org, emu@ietf.org, The IESG Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Emu] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_charter?= =?utf-8?q?-ietf-emu-04-00=3A_=28with_COMMENT=29?= X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2018 16:51:42 -0000 Mirja, The milestones have been updated per the dates and language provided by Jar= i. Thanks, Kathleen On Mon, Feb 19, 2018 at 11:36 AM, Mirja Kuehlewind (IETF) wrote: > Yes. I don=E2=80=99t see a big difference between =E2=80=9EWGLC" and "sen= d to IESG=E2=80=9C but it=E2=80=99s good to have a deadline! > >> Am 18.02.2018 um 12:48 schrieb Jari Arkko : >> >> Mirja, >> >>> I would actually rather like to see milestones for when the work is sup= posed to >>> be finished (send to IESG for publication) than when it is supposed to = start >>> (wg adoption) as the first is probably harder to achieve in time than t= he >>> second. >> >> I suggested edits to the milestones in a response to Kathleen=E2=80=99s >> comments, and the suggested edits include having both start >> (adopt) and end (WGLC) for all work items. Does that work for >> you? >> >> (Although some of our charters speak about WGLC and others >> about sending to IESG=E2=80=A6 not sure the difference matters.) >> >> Jari >> > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu --=20 Best regards, Kathleen From nobody Wed Feb 21 20:55:22 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 688B9126D3F; Wed, 21 Feb 2018 20:55:20 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Eric Rescorla To: "The IESG" Cc: emu-chairs@ietf.org, emu@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.72.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151927532042.21085.8931446748584031729.idtracker@ietfa.amsl.com> Date: Wed, 21 Feb 2018 20:55:20 -0800 Archived-At: Subject: [Emu] Eric Rescorla's Yes on charter-ietf-emu-04-01: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Feb 2018 04:55:20 -0000 Eric Rescorla has entered the following ballot position for charter-ietf-emu-04-01: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-emu/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- LGTM with some nits below: - Provide a guidance or update to enable the use of TLS 1.3 in the context of EAP TLS (RFC 5216). Update the security considerations relating to EAP TLS, to document the implications of using new vs. old TLS version, any recently gained new Nit: versions In all of the above, it is a requirement that none of the updates break backwards compatibility with existing specifications or implementations. The current EAP-TLS RFCs shall not be obsoleted but s/shall/will/? rather updated with either new information or instructions on what is needed, for instance, to employ a new TLS version. From nobody Thu Feb 22 06:43:21 2018 Return-Path: X-Original-To: emu@ietfa.amsl.com Delivered-To: emu@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A7012EAD6; Thu, 22 Feb 2018 06:43:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVQOlWfBFTK3; Thu, 22 Feb 2018 06:43:09 -0800 (PST) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11720126D05; Thu, 22 Feb 2018 06:43:09 -0800 (PST) Received: by mail-oi0-x22b.google.com with SMTP id f186so3849035oig.4; Thu, 22 Feb 2018 06:43:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tpE/g/6hLm0WN3IoU1gmC+qP8BmjkBXJXrambzffDZQ=; b=MhqYuIVSMdCBYXx1mLPes9dwSkD/aUtK42OssngXX3PaRIXdHDhxOgdvYfossN1aby 4ngqdgOAVXv3mHEOXRGJwqB3AWnuOAJjafHODee+TzaxQlrtdaoEBpqMsl79UEeKvBK+ /9FVf7CP3E++i1d3iacfpbKRMru9l2+VvYoVshjyreG540R65Qheb+L+HASLqFS4BNuS j2DFWHTeI3gJZp8Y7Pb9AMI9tU8JtMEfgvkbt5U/gYX2bTIpUSIKjoqzguO4em3CLtiT 1qSIjNREWJPuHLG3GnO8RUWco84+4StqCS6G2QYh2M3KbNV3LqR45OKdOoY3mKU+4DZ1 R9kA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tpE/g/6hLm0WN3IoU1gmC+qP8BmjkBXJXrambzffDZQ=; b=PmRyn2F0NUtFsLLu8miWQuWfQg6B6M/xdRGC1NfShEyJbcfXLNeJcrxytW2vRZBXEG U8JnpqJZpzFhkorKIVFBGij4IydYIyb+pxfHZFoFpRbyU5R+PUKLeS+ifdo4368jCcrJ +Xuu6Z8MlHyeRA9lPVHVQUcvoEQEEEbfwc/bPSECKXRG89kk/r+7xhxuLPjHbtWE4/Ue r4sCWmunFi+cLb7efbsRAOW43qsmtLXxET3chOZ4kONG0p+0PipqV0ZxvbunR8/ldz9B zAu+10jGMz10t7njc5OfTqxsODEuW2NfP+w0DoKwgDYu+KTuWBRWIe5vHjUQhcW7u5py 1pNg== X-Gm-Message-State: APf1xPCtyex/WIg5VXx7pAPRuTzlh+ByH49QqqhrfPuMD5via+toE0hh a9hQ3t3ezOZg3IrnhfgvKRyRixF4OFrhy96eDCk= X-Google-Smtp-Source: AH8x2279WfgSbmy3HYHKPruf9WqaV3c7z6z+zl7YXNdDtEAvdvJI0hkKdKyUjO0iy5hPEalsyWr1WXTeMfpEmjX4hMg= X-Received: by 10.202.1.200 with SMTP id 191mr4843255oib.206.1519310588488; Thu, 22 Feb 2018 06:43:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.46.119 with HTTP; Thu, 22 Feb 2018 06:42:28 -0800 (PST) In-Reply-To: <151927532042.21085.8931446748584031729.idtracker@ietfa.amsl.com> References: <151927532042.21085.8931446748584031729.idtracker@ietfa.amsl.com> From: Kathleen Moriarty Date: Thu, 22 Feb 2018 09:42:28 -0500 Message-ID: To: Eric Rescorla Cc: The IESG , emu-chairs@ietf.org, emu@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Emu] Eric Rescorla's Yes on charter-ietf-emu-04-01: (with COMMENT) X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Feb 2018 14:43:11 -0000 Hi Eric, On Wed, Feb 21, 2018 at 11:55 PM, Eric Rescorla wrote: > Eric Rescorla has entered the following ballot position for > charter-ietf-emu-04-01: Yes > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/charter-ietf-emu/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > LGTM with some nits below: > > > - Provide a guidance or update to enable the use of TLS 1.3 in the > context of EAP TLS (RFC 5216). Update the security > considerations relating to EAP TLS, to document the implications > of using new vs. old TLS version, any recently gained new > > Nit: versions > > In all of the above, it is a requirement that none of the updates > break backwards compatibility with existing specifications or > implementations. The current EAP-TLS RFCs shall not be obsoleted but > > s/shall/will/? > > rather updated with either new information or instructions on > what is needed, for instance, to employ a new TLS version. > > The suggested changes have been made, thank you. -- Best regards, Kathleen From nobody Tue Feb 27 15:14:10 2018 Return-Path: X-Original-To: emu@ietf.org Delivered-To: emu@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1293312E8F1; Tue, 27 Feb 2018 15:11:12 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: Kathleen.Moriarty.ietf@gmail.com, emu@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.73.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151977307206.5200.11761242059101084796.idtracker@ietfa.amsl.com> Date: Tue, 27 Feb 2018 15:11:12 -0800 Archived-At: Subject: [Emu] emu - Requested session has been scheduled for IETF 101 X-BeenThere: emu@ietf.org X-Mailman-Version: 2.1.22 List-Id: "EAP Methods Update \(EMU\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 23:11:12 -0000 Dear Liz Flynn, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. emu Session 1 (1:30:00) Monday, Afternoon Session II 1550-1720 Room Name: Richmond/Chelsea/Tower size: 75 --------------------------------------------- Request Information: --------------------------------------------------------- Working Group Name: EAP Method Update Area Name: Security Area Session Requester: Liz Flynn Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 30 Conflicts to Avoid: People who must be present: Kathleen Moriarty Resources Requested: Special Requests: ---------------------------------------------------------