Re: [pcp] Server's auth policy discovery

Alper Yegin <alper.yegin@yegin.org> Fri, 12 October 2012 11:41 UTC

Return-Path: <alper.yegin@yegin.org>
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 EAB2021F853B for <pcp@ietfa.amsl.com>; Fri, 12 Oct 2012 04:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level:
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, 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 qY7QaqoVJASF for <pcp@ietfa.amsl.com>; Fri, 12 Oct 2012 04:41:51 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 65ADA21F8533 for <pcp@ietf.org>; Fri, 12 Oct 2012 04:41:51 -0700 (PDT)
Received: from [192.168.2.7] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0M54zu-1TZWbR3QR4-00z2tZ; Fri, 12 Oct 2012 07:41:49 -0400
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <tslzk3rj530.fsf@mit.edu>
Date: Fri, 12 Oct 2012 14:41:29 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <22CCCEB5-FA7E-474A-B890-5A6EB16E44DB@yegin.org>
References: <0BC19EAB-01F2-4AB9-B706-FD7C98FFAE86@yegin.org> <tsl4nm0j755.fsf@mit.edu> <5077FA0A.9030308@toshiba.co.jp> <tslzk3rj530.fsf@mit.edu>
To: Sam Hartman <hartmans@painless-security.com>
X-Mailer: Apple Mail (2.1278)
X-Provags-ID: V02:K0:i+4e7sFOZNHPxnXDcsTB45djzIjb0bn1jrxEe9IOldX UrS/lhFAn2rigpjmhyCcLGPxI1/R/wRxfZalh6r8QEkXso8VHj P7c2Ae4PNAZ0ok/95URCUoRqodQuhpI1cbh8GsE99ng30FsNhc OtDYz8UHTJ2n4jizpcpHYVcVJJvkm6gvkBwp4jQ7lxJNk8SjYh oxT7EzM+Zm44lZznpqgZh7Hi/QhQfPubF68m0x9L0PQS3R/kkY ivI7oIpMu1zi5F3zJ3GRwmXm3iB4TKtHATXhJwgzAbrmpLaTKg MKUH5kcKeq/m8kkyvD4ClITA8NdAiI+rkOgvICIcXw9FTNbbjT ovqLfpI20oxawGdpO08DydWNXxY5A5jx7M41xFeXVrsV51rrGq yCKnWySUWD6gA==
Cc: pcp@ietf.org
Subject: Re: [pcp] Server's auth policy 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, 12 Oct 2012 11:41:52 -0000

Sam,

On Oct 12, 2012, at 2:35 PM, Sam Hartman wrote:

>>>>>> "Yoshihiro" == Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> writes:
> 
>    Yoshihiro> Is discoverying binary policy (auth
>    Yoshihiro> unsupported/supported) is enough, or is discovering
>    Yoshihiro> three-policy (auth unsupported/mandated/optional) needed?
> 
> I think discovering auth supported is sufficient.

So, you suggest eliminating case 2 below?

1. auth not used (not supported, or disabled)
2. use of auth is optional (i.e., PCP Client's decision)
3. auth is mandatory to use


Alper