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

Raja ashok <raja.ashok@huawei.com> Thu, 01 December 2016 10:07 UTC

Return-Path: <raja.ashok@huawei.com>
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 BF6BD129613 for <pana@ietfa.amsl.com>; Thu, 1 Dec 2016 02:07:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.116
X-Spam-Level:
X-Spam-Status: No, score=-7.116 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, 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 rVtCi0OdHdud for <pana@ietfa.amsl.com>; Thu, 1 Dec 2016 02:07:43 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC570129C6B for <Pana@ietf.org>; Thu, 1 Dec 2016 02:06:32 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DBS59650; Thu, 01 Dec 2016 10:06:29 +0000 (GMT)
Received: from BLREML407-HUB.china.huawei.com (10.20.4.45) by lhreml702-cah.china.huawei.com (10.201.5.99) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 1 Dec 2016 10:06:28 +0000
Received: from BLREML509-MBX.china.huawei.com ([169.254.7.90]) by BLREML407-HUB.china.huawei.com ([10.20.4.45]) with mapi id 14.03.0301.000; Thu, 1 Dec 2016 15:36:16 +0530
From: Raja ashok <raja.ashok@huawei.com>
To: "yoshihiro.ohba@toshiba.co.jp" <yoshihiro.ohba@toshiba.co.jp>, "basavaraj.patil@nokia.com" <basavaraj.patil@nokia.com>, "alper.yegin@yegin.org" <alper.yegin@yegin.org>, "jari.arkko@piuha.net" <jari.arkko@piuha.net>, "Pana@ietf.org" <Pana@ietf.org>
Thread-Topic: Regarding the optimization scope in EAP-PSK with PANA
Thread-Index: AdJLuozNTjKsHaFPRSCggvrk+5xmwA==
Date: Thu, 01 Dec 2016 10:06:15 +0000
Message-ID: <FDFEA8C9B9B6BD4685DCC959079C81F5E19142A0@BLREML509-MBX.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.213.121]
Content-Type: multipart/related; boundary="_004_FDFEA8C9B9B6BD4685DCC959079C81F5E19142A0BLREML509MBXchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.583FF626.0469, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.7.90, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c081cf54b9d891a21dab9da3dd2304bb
Archived-At: <https://mailarchive.ietf.org/arch/msg/pana/fvn29-DgIuTRTdspYkKnozyMwho>
Subject: [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: Thu, 01 Dec 2016 10:07:49 -0000

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!