Re: [pcp] Capability discovery

Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Fri, 05 October 2012 15:14 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 E4BC821F869E for <pcp@ietfa.amsl.com>; Fri, 5 Oct 2012 08:14:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.015
X-Spam-Level:
X-Spam-Status: No, score=-7.015 tagged_above=-999 required=5 tests=[AWL=1.074, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, 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 AGfA9vg5bes5 for <pcp@ietfa.amsl.com>; Fri, 5 Oct 2012 08:14:29 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id C93A321F869C for <pcp@ietf.org>; Fri, 5 Oct 2012 08:14:28 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp with ESMTP id q95FEPtD027105; Sat, 6 Oct 2012 00:14:25 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp id q95FEPVV010653; Sat, 6 Oct 2012 00:14:25 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id AAA10652; Sat, 6 Oct 2012 00:14:25 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id q95FEPKY025858; Sat, 6 Oct 2012 00:14:25 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id q95FEPcx020522; Sat, 6 Oct 2012 00:14:25 +0900 (JST)
Received: from [133.199.16.47] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPSA id <0MBF00CLBEBPIV50@mail.po.toshiba.co.jp>; Sat, 06 Oct 2012 00:14:25 +0900 (JST)
Date: Sat, 06 Oct 2012 00:14:16 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <034101cda301$4972d690$dc5883b0$@com>
To: Dan Wing <dwing@cisco.com>
Message-id: <506EF948.40303@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
References: <506E4E07.3000807@toshiba.co.jp> <034101cda301$4972d690$dc5883b0$@com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
Cc: pcp@ietf.org
Subject: Re: [pcp] Capability discovery
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: Fri, 05 Oct 2012 15:14:30 -0000

(2012/10/05 22:56), Dan Wing wrote:
>> -----Original Message-----
>> From:pcp-bounces@ietf.org  [mailto:pcp-bounces@ietf.org] On Behalf Of
>> Yoshihiro Ohba
>> Sent: Thursday, October 04, 2012 8:04 PM
>> To:pcp@ietf.org
>> Subject: [pcp] Capability discovery
>>
>> There has been a question on what to do when PCP client supports PCP
>> authentication
>> while PCP server does not, and vise versa.
> Yes, that problem needs to be solved.
>
>> The same issue will exist for future PCP extensions.
> I disagree that problem exists for PCP extensions.  The client can
> simply try to use the extension, and will either get back an error
> (e.g., UNSUPP_OPCODE or UNSUPP_OPTION error), or the option will
> not be included in the response (for options outside the mandatory-
> to-process range).

In that case, the problem is specific to side-by-side PANA approach
which does not use PCP opcode/options.  Is this correct?

Yoshihiro Ohba



>> I would like to hear opinions whether defining a capability discovery
>> exchange
>> in PCP base specification ever makes sense, where the capability
>> discovery exchange is
>> expected to happen prior to any other PCP opcodes.
> I have not found that capability discovery is necessary.
>
> -d
>
>
>
>> Best Regards,
>> Yoshihiro Ohba
>>
>>
>>
>> _______________________________________________
>> pcp mailing list
>> pcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcp