Re: [pcp] Comparison of PCP authentication

Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Thu, 16 August 2012 09:24 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 473F321F863B for <pcp@ietfa.amsl.com>; Thu, 16 Aug 2012 02:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.779
X-Spam-Level:
X-Spam-Status: No, score=-3.779 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7yD84mDy9lnW for <pcp@ietfa.amsl.com>; Thu, 16 Aug 2012 02:24:07 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id 9106721F84D9 for <pcp@ietf.org>; Thu, 16 Aug 2012 02:24:05 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id q7G9O3xX004695; Thu, 16 Aug 2012 18:24:03 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id q7G9O3S4014763; Thu, 16 Aug 2012 18:24:03 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id UAA14760; Thu, 16 Aug 2012 18:24:03 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id q7G9O2ii016379; Thu, 16 Aug 2012 18:24:03 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id q7G9O25d021167; Thu, 16 Aug 2012 18:24:02 +0900 (JST)
Received: from [133.196.20.119] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0M8U00941CS2KIC0@mail.po.toshiba.co.jp>; Thu, 16 Aug 2012 18:24:02 +0900 (JST)
Date: Thu, 16 Aug 2012 18:24:04 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <C72CBD9FE3CA604887B1B3F1D145D05E305AADC2@szxeml528-mbx.china.huawei.com>
To: "Zhangdacheng (Dacheng)" <zhangdacheng@huawei.com>
Message-id: <502CBC34.4000408@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-2022-JP"
Content-transfer-encoding: 7bit
References: <9B57C850BB53634CACEC56EF4853FF653B6EC381@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <7FE144CF-00E3-4451-8CBE-A6A684DB7CC4@yegin.org> <067d01cd73fd$765a6c50$630f44f0$@com> <D6D2DEED-C35A-45AB-8B72-96195C308DB9@yegin.org> <57FF0F8E-1B86-410F-8B6B-C4893A28222F@lilacglade.org> <BB72B80F-0622-4A5B-A985-79D8AED13E0B@apple.com> <003b01cd7587$a111b760$e3352620$@com> <15990E87-2D59-49B1-845C-2A4CB5A1FBD6@lilacglade.org> <008801cd758f$3fd306e0$bf7914a0$@com> <C72CBD9FE3CA604887B1B3F1D145D05E2CE65225@szxeml528-mbx.china.huawei.com> <028801cd75d6$c5765490$5062fdb0$@com> <tsla9y4gptp.fsf@mit.edu> <04c901cd7658$37a740c0$a6f5c240$@com> <tslboikexlv.fsf@mit.edu> <054001cd765d$54c0f3e0$fe42dba0$@com> <0F259BA1-CEFF-4346-AFE5-3D33BB0CF0CC@lilacglade.org> <C72CBD9FE3CA604887B1B3F1D145D05E2CE756EE@szxeml528-mbs.china.huawei.com> <502C6BF0.3030400@toshiba.co.jp> <C72CBD9FE3CA604887B1B3F1D145D05E305AADC2@szxeml528-mbx.china.huawei.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Comparison of PCP authentication
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 09:24:15 -0000

Dacheng,

(2012/08/16 17:52), Zhangdacheng (Dacheng) wrote:
>>
>> Here is a brief comparison on both PANA-based schemes:
>>
>> Encapsulation/tunneling approach:
>> - Pros: No impact on PANA specification
>> - Cons: Encapsulation overhead
> About this Con. Maybe we can remove the redundant information in a pana packet and only transport the necessary part in a pcp packet. Therefore, after receiving the PCP packet, the receiver can re-construct the pana packet.
> 

If "remove the redundant information" means a change of the basic PANA
PDU format other than defining a new use of "Reserved" field, then it
is going towards "re-inventing the wheel" direction which we should
not go.

Yoshihiro Ohba


> Dacheng
> 
>