Re: [Pana] Regarding the optimization scope in EAP-PSK with PANA

<yoshihiro.ohba@toshiba.co.jp> Fri, 02 December 2016 00:59 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B27129A23 for <pana@ietfa.amsl.com>; Thu, 1 Dec 2016 16:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 NQ_2PGlU76pO for <pana@ietfa.amsl.com>; Thu, 1 Dec 2016 16:59:29 -0800 (PST)
Received: from mo.tsb.2iij.net (mo1502.tsb.2iij.net [210.149.48.174]) (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 CE325129A1D for <Pana@ietf.org>; Thu, 1 Dec 2016 16:59:25 -0800 (PST)
Received: by mo.tsb.2iij.net (tsb-mo1502) id uB20xLF6031550; Fri, 2 Dec 2016 09:59:21 +0900
Received: from unknown [172.27.153.184] (EHLO tsb-mr1500.hop.2iij.net) by mas1508.tsb.2iij.net(mxl_mta-7.2.4-7) with ESMTP id 967c0485.0.349680.00-665.634149.mas1508.tsb.2iij.net (envelope-from <yoshihiro.ohba@toshiba.co.jp>); Fri, 02 Dec 2016 09:59:21 +0900 (JST)
X-MXL-Hash: 5840c7691b6b2826-4a4f012cfaa3cfca2d8eeff29daa792f3e5c9c98
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by relay.tsb.2iij.net (tsb-mr1500) with ESMTP id uB20xKPr007708; Fri, 2 Dec 2016 09:59:20 +0900
Received: from tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp ([133.199.232.103]) by imx12.toshiba.co.jp with ESMTP id uB20xKZf022439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2016 09:59:20 +0900 (JST)
Received: from tsbmgw-mgw01 (localhost [127.0.0.1]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id uB20xKwE010229; Fri, 2 Dec 2016 09:59:20 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw01 (JAMES SMTP Server 2.3.1) with SMTP ID 778; Fri, 2 Dec 2016 09:59:20 +0900 (JST)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id uB20xJNH010217; Fri, 2 Dec 2016 09:59:19 +0900
Received: (from root@localhost) by arc11.toshiba.co.jp id uB20xJ66011541; Fri, 2 Dec 2016 09:59:19 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id KAA11522; Fri, 2 Dec 2016 09:59:19 +0900
Received: from mx12.toshiba.co.jp (mx12.toshiba.co.jp [133.199.90.142]) by ovp11.toshiba.co.jp with ESMTP id uB20xHek019863; Fri, 2 Dec 2016 09:59:17 +0900 (JST)
Received: from tgxml230.toshiba.local by toshiba.co.jp id uB20xHPF028078; Fri, 2 Dec 2016 09:59:17 +0900 (JST)
Received: from TGXML279.toshiba.local (133.199.71.134) by tgxml230.toshiba.local (133.199.62.21) with Microsoft SMTP Server (TLS) id 14.3.266.1; Fri, 2 Dec 2016 09:59:16 +0900
Received: from TGXML278.toshiba.local (133.199.71.133) by TGXML279.toshiba.local (133.199.71.134) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 2 Dec 2016 09:59:16 +0900
Received: from TGXML278.toshiba.local ([192.168.94.145]) by TGXML278.toshiba.local ([192.168.94.145]) with mapi id 15.00.1178.000; Fri, 2 Dec 2016 09:59:16 +0900
From: <yoshihiro.ohba@toshiba.co.jp>
To: <raja.ashok@huawei.com>, <basavaraj.patil@nokia.com>, <alper.yegin@yegin.org>, <jari.arkko@piuha.net>, <Pana@ietf.org>
Thread-Topic: Regarding the optimization scope in EAP-PSK with PANA
Thread-Index: AdJLuozNTjKsHaFPRSCggvrk+5xmwAAe1hcw
Date: Fri, 2 Dec 2016 00:59:16 +0000
Message-ID: <5529840c4adb4c5f8f93c03c94ce8fb1@TGXML278.toshiba.local>
References: <FDFEA8C9B9B6BD4685DCC959079C81F5E19142A0@BLREML509-MBX.china.huawei.com>
In-Reply-To: <FDFEA8C9B9B6BD4685DCC959079C81F5E19142A0@BLREML509-MBX.china.huawei.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: yes
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [133.120.178.44]
msscp.transfermailtomossagent: 103
Content-Type: multipart/related; boundary="_004_5529840c4adb4c5f8f93c03c94ce8fb1TGXML278toshibalocal_"; type="multipart/alternative"
MIME-Version: 1.0
X-MAIL-FROM: <yoshihiro.ohba@toshiba.co.jp>
X-SOURCE-IP: [172.27.153.184]
X-Spam: exempt
Archived-At: <https://mailarchive.ietf.org/arch/msg/pana/7XQGG25C0EMQua_1vAB3blgbcLk>
Subject: Re: [Pana] Regarding the optimization scope in EAP-PSK with PANA
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pana/>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2016 00:59:32 -0000

Hi Ashok,

According to RFC 3748: ¡°the authentication conversation can continue until the authenticator determines that successful authentication has occurred, in which case the authenticator MUST transmit an EAP Success (Code 3).¡±

Without changing RFC 3748, I do not think we can design an EAP method that does not use EAP Success.

Regards,
Yoshihiro Ohba



From: Raja ashok [mailto:raja.ashok@huawei.com]
Sent: Thursday, December 01, 2016 6:06 PM
To: ohba yoshihiro(´óˆö ÁxÑó £Ô£Å£Á Advanced Technical Marketing Department); basavaraj.patil@nokia.com; alper.yegin@yegin.org; jari.arkko@piuha.net; Pana@ietf.org
Subject: Regarding the optimization scope in EAP-PSK with PANA

Hi All,

Currently EAP-PSK with PANA takes 5RTT. I am felling this should be optimized for wiresless sensor network in mesh topology.

EAP-PSK 3rd and 4th message contains Protected channel (PCHANNEL). This is a secure channel formed between client and server with EAX algorithm. But as per my knowledge this channel is not required if EAP-PSK is used with PANA. Because anyway PANA session keys are there with that we can exchange information securely using Encrypt-Encapsulate AVP and Auth AVP.

So if we define a simplified EAP-PSK mechanism without PCHANNEL, we can omit 1 RTT message. This has been explained below

Client                                                                                                                    Server
-------                                                                                                                    --------
PAR/EAP-PSK 1st msg
[Flags||RAND_S||ID_S]                               --->
                                                                                                                PAN/EAP-PSK 2nd msg
                                                                                <---                        [Flags||RAND_S||RAND_P||MAC_P||ID_P]
                PAR¡¯C¡¯/EAP-PSK 3rd msg
[Flags||RAND_S||MAC_S]                         --->


Here we can omit EAP-Success msg also in PAR¡¯C¡¯ msg, because PANA result code AVP is there. I hope that is sufficient. So we can send EAP-PSK 3rd msg in PAR ¡®C¡¯ msg directly.

This saves 1 RTT in handshake. And also the EAX algorithm is not required, so this saves some flash memory in constraint environment. But this simplified EAP-PSK cannot be used alone. This can be used only with PANA.

Please provide your comments on it.

Regards,
Ashok

________________________________
[Company_logo]

Raja Ashok V K
Huawei Technologies
Bangalore, India
http://www.huawei.com
________________________________
±¾Óʼþ¼°Æ丽¼þº¬ÓлªÎª¹«Ë¾µÄ±£ÃÜÐÅÏ¢£¬½öÏÞÓÚ·¢Ë͸øÉÏÃæµØÖ·ÖÐÁгöµÄ¸öÈË»òȺ×é¡£½û
Ö¹ÈκÎÆäËûÈËÒÔÈκÎÐÎʽʹÓ㨰üÀ¨µ«²»ÏÞÓÚÈ«²¿»ò²¿·ÖµØй¶¡¢¸´ÖÆ¡¢»òÉ¢·¢£©±¾ÓʼþÖÐ
µÄÐÅÏ¢¡£Èç¹ûÄú´íÊÕÁ˱¾Óʼþ£¬ÇëÄúÁ¢¼´µç»°»òÓʼþ֪ͨ·¢¼þÈ˲¢É¾³ý±¾Óʼþ£¡
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!