IETF Logo Mail Archive

Re: [pcp] Server's auth policy discovery

Sam Hartman <hartmans@painless-security.com> Fri, 12 October 2012 12:56 UTC

Return-Path: <hartmans@painless-security.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 541F821F84EF for <pcp@ietfa.amsl.com>; Fri, 12 Oct 2012 05:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.342
X-Spam-Level: ****
X-Spam-Status: No, score=4.342 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1]
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 uPQpgdCpbja7 for <pcp@ietfa.amsl.com>; Fri, 12 Oct 2012 05:56:38 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id A995921F84CE for <pcp@ietf.org>; Fri, 12 Oct 2012 05:56:38 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 8564920200; Fri, 12 Oct 2012 08:56:23 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A09FC4AD5; Fri, 12 Oct 2012 08:56:35 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: Alper Yegin <alper.yegin@yegin.org>
References: <0BC19EAB-01F2-4AB9-B706-FD7C98FFAE86@yegin.org> <tsl4nm0j755.fsf@mit.edu> <5077FA0A.9030308@toshiba.co.jp> <tslzk3rj530.fsf@mit.edu> <22CCCEB5-FA7E-474A-B890-5A6EB16E44DB@yegin.org> <tslvcefj3i3.fsf@mit.edu> <F2C651B4-76AB-409E-8540-892E5793ACC0@yegin.org>
Date: Fri, 12 Oct 2012 08:56:35 -0400
In-Reply-To: <F2C651B4-76AB-409E-8540-892E5793ACC0@yegin.org> (Alper Yegin's message of "Fri, 12 Oct 2012 15:44:28 +0300")
Message-ID: <tsld30nj1bw.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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 12:56:39 -0000

>>>>> "Alper" == Alper Yegin <alper.yegin@yegin.org> writes:

    Alper> Sam, For a client to decide whether it will use auth or not,
    Alper> it needs to know the server policy.  A server that implements
    Alper> auth does not mean that the client must use auth.  Server may
    Alper> still be configured to allow unauth clients.

    Alper> This is why I have three distinct cases.

I understand that's your model. My model is different, but probably
isomorphic.

    Alper> And this I'm asking independent of the PANA port-sharing
    Alper> discussion.

    Alper> As for dealing with discovery for PANA port-sharing, either:
    Alper> - We agree that it's OK for all clients to start with "no
    Alper> auth", or - We use a DHCP-based solution (I know you are not

Or we have a capability discovery mechanism
or we have a specific opcode for "do you support auth?"

v2.23.0 | Report a Bug | By Email