IETF Logo Mail Archive

Re: [pcp] Capability discovery

Dave Thaler <dthaler@microsoft.com> Fri, 05 October 2012 17:42 UTC

Return-Path: <dthaler@microsoft.com>
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 D71E921F87C1 for <pcp@ietfa.amsl.com>; Fri, 5 Oct 2012 10:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.482
X-Spam-Level:
X-Spam-Status: No, score=-105.482 tagged_above=-999 required=5 tests=[AWL=1.117, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 LKU9oMT377Gn for <pcp@ietfa.amsl.com>; Fri, 5 Oct 2012 10:42:12 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe006.messaging.microsoft.com [216.32.180.16]) by ietfa.amsl.com (Postfix) with ESMTP id 41F9A21F87B3 for <pcp@ietf.org>; Fri, 5 Oct 2012 10:42:12 -0700 (PDT)
Received: from mail209-va3-R.bigfish.com (10.7.14.235) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 5 Oct 2012 17:42:11 +0000
Received: from mail209-va3 (localhost [127.0.0.1]) by mail209-va3-R.bigfish.com (Postfix) with ESMTP id 073E564013B; Fri, 5 Oct 2012 17:42:11 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14MLTC103.redmond.corp.microsoft.com; RD:none; EFVD:NLI
X-SpamScore: -29
X-BigFish: VS-29(zzbb2dI98dI9371I542M1432Izz1202h1d1ah1d2ahzz1033IL8275dhz2fh2a8h668h839h944hd25hf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1155h)
Received-SPF: pass (mail209-va3: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=dthaler@microsoft.com; helo=TK5EX14MLTC103.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail209-va3 (localhost.localdomain [127.0.0.1]) by mail209-va3 (MessageSwitch) id 1349458928965862_1047; Fri, 5 Oct 2012 17:42:08 +0000 (UTC)
Received: from VA3EHSMHS031.bigfish.com (unknown [10.7.14.241]) by mail209-va3.bigfish.com (Postfix) with ESMTP id E7738C80062; Fri, 5 Oct 2012 17:42:08 +0000 (UTC)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.8) by VA3EHSMHS031.bigfish.com (10.7.99.41) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 5 Oct 2012 17:42:08 +0000
Received: from TK5EX14MLTW653.wingroup.windeploy.ntdev.microsoft.com (157.54.24.14) by TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) with Microsoft SMTP Server (TLS) id 14.2.318.3; Fri, 5 Oct 2012 17:42:08 +0000
Received: from TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com ([169.254.4.114]) by TK5EX14MLTW653.wingroup.windeploy.ntdev.microsoft.com ([157.54.24.14]) with mapi id 14.02.0318.003; Fri, 5 Oct 2012 10:42:07 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>, Dan Wing <dwing@cisco.com>
Thread-Topic: [pcp] Capability discovery
Thread-Index: AQHNoqYGedw27p7IoES7IkeY9rafx5erMp4AgAAVmQD//7O2sA==
Date: Fri, 05 Oct 2012 17:42:07 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B8101A7@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
References: <506E4E07.3000807@toshiba.co.jp> <034101cda301$4972d690$dc5883b0$@com> <506EF948.40303@toshiba.co.jp>
In-Reply-To: <506EF948.40303@toshiba.co.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: "pcp@ietf.org" <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 17:42:13 -0000

Yoshihiro Ohba writes: 
> (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?

Yes, I believe that's correct.

-Dave

v2.23.0 | Report a Bug | By Email