[HOKEY] Change proposal for ERP-AAK - 8: Check fail processing
Qin Wu <bill.wu@huawei.com> Thu, 29 September 2011 10:26 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: hokey@ietfa.amsl.com
Delivered-To: hokey@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E33621F8C32 for <hokey@ietfa.amsl.com>; Thu, 29 Sep 2011 03:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.728
X-Spam-Level:
X-Spam-Status: No, score=-4.728 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WBU25kYvChy1 for <hokey@ietfa.amsl.com>; Thu, 29 Sep 2011 03:26:13 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 268F921F8C31 for <hokey@ietf.org>; Thu, 29 Sep 2011 03:26:13 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSA00J3454ERB@szxga05-in.huawei.com> for hokey@ietf.org; Thu, 29 Sep 2011 18:29:03 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSA0009654DW5@szxga05-in.huawei.com> for hokey@ietf.org; Thu, 29 Sep 2011 18:29:02 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id ADZ59870; Thu, 29 Sep 2011 18:28:44 +0800
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 29 Sep 2011 18:28:38 +0800
Received: from w53375q (10.138.41.130) by szxeml402-hub.china.huawei.com (10.82.67.32) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 29 Sep 2011 18:28:37 +0800
Date: Thu, 29 Sep 2011 18:28:37 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: hokey@ietf.org
Message-id: <F67175F57F7B450688E8AF96A8D40784@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_osp2VjyyE/hBP4BElNygBg)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
Subject: [HOKEY] Change proposal for ERP-AAK - 8: Check fail processing
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hokey>, <mailto:hokey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hokey>
List-Post: <mailto:hokey@ietf.org>
List-Help: <mailto:hokey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2011 10:26:14 -0000
Hi, In the section 3 of draft-ietf-hokey-erp-aak, we didn't consider what the server does if check failing happens. Therefore I propose to do the following change to the section 3: OLD TEXT: " Upon receiving the message, the ERP/AAK server first checks its integrity and freshness, then authorizes the CAP presented in the NAS-Identifier TLV(s) via the NAS-Identifier. " NEW TEXT " Upon receiving the message, the ERP/AAK server first verifies the authentication of the peer by checking username portion of KeyName-NAI and checks its integrity and freshness and, then verifies if the value(s) contained in the CAP-Identifier conflict with NAS-Identifier for SAP. Next,authenticates and authorizes the CAP(s) presented in the NAS-Identifier TLV(s). If any of the checks fail, the server sends an the early-authentication finish message (EAP-Finish/Re-auth with E-flag set) with the Result flag set to '1'. " OLD TEXT: " The ERP/AAK server transports the pMSK to the authenticated and authorized CAP(s) via AAA as described in Section 7. Finally, the ERP/AAK server sends the early-authentication finish message (EAP-Finish/Re-auth with E-flag set) containing the determined CAP to the peer via the SAP. " NEW TEXT: " The ERP/AAK server transports the pMSK(s) respectively to the authenticated and authorized CAP(s) via AAA as described in Section 7. After the keying materials are delivered, the ERP/AAK server should determine each CA whether accepts the pMSK and whether the peer could be attached to by interacting with the CA via AAA message. If the ERP/AAK server knows the CA does not support ERP, it should sends an the early-authentication finish message (EAP-Finish/Re-auth with E-flag set) with the Result flag set to '1'. Otherwise, the ERP/AAK server sends the early-authentication finish message (EAP-Finish/Re-auth with E-flag set) containing the determined CAP(s) to the peer via the SAP. " Regards! -Qin