Re: [pcp] Server's auth policy discovery

Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Fri, 12 October 2012 11:07 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 A1EA121F85A4 for <pcp@ietfa.amsl.com>; Fri, 12 Oct 2012 04:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.93
X-Spam-Level:
X-Spam-Status: No, score=-4.93 tagged_above=-999 required=5 tests=[AWL=-0.841, 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 dHhrNYf614+N for <pcp@ietfa.amsl.com>; Fri, 12 Oct 2012 04:07:55 -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 9795121F85A1 for <pcp@ietf.org>; Fri, 12 Oct 2012 04:07:55 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id q9CB7sCZ028422 for <pcp@ietf.org>; Fri, 12 Oct 2012 20:07:54 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id q9CB7sRb000235 for pcp@ietf.org; Fri, 12 Oct 2012 20:07:54 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id WAA00234; Fri, 12 Oct 2012 20:07:54 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id q9CB7sKr017355 for <pcp@ietf.org>; Fri, 12 Oct 2012 20:07:54 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id q9CB7sIx010779; Fri, 12 Oct 2012 20:07:54 +0900 (JST)
Received: from [133.199.16.62] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPSA id <0MBS009281L3LC80@mail.po.toshiba.co.jp> for pcp@ietf.org; Fri, 12 Oct 2012 20:07:54 +0900 (JST)
Date: Fri, 12 Oct 2012 20:07:54 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <tsl4nm0j755.fsf@mit.edu>
To: pcp@ietf.org
Message-id: <5077FA0A.9030308@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
References: <0BC19EAB-01F2-4AB9-B706-FD7C98FFAE86@yegin.org> <tsl4nm0j755.fsf@mit.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
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:07:56 -0000

Is discoverying binary policy (auth unsupported/supported)
is enough, or is discovering three-policy (auth 
unsupported/mandated/optional) needed?

Yoshihiro Ohba


(2012/10/12 19:51), Sam Hartman wrote:
> Hi.
> As I've mentioned previously, I consider DHCP-based discovery of auth
> policy a significant down-side to an approach that requires it.
>
> For many of the same reasons that you want to avoid one port for
> authentication and one port for the protocol, you want to avoid one
> system for security policy discovery with another system for using that
> policy.  Tightly-coupled systems are easier to debug and support.  In
> this particular case, if auth policy discovery is in-band, you avoid the
> failure modes where the discovery solution has bad information.
>
> --Sam
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp
>