Re: [pcp] Comparison of PCP authentication

Margaret Wasserman <mrw@lilacglade.org> Wed, 08 August 2012 17:07 UTC

Return-Path: <mrw@lilacglade.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 6424321F8499 for <pcp@ietfa.amsl.com>; Wed, 8 Aug 2012 10:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.709
X-Spam-Level:
X-Spam-Status: No, score=-95.709 tagged_above=-999 required=5 tests=[AWL=0.003, 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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DELnFFfN2dz5 for <pcp@ietfa.amsl.com>; Wed, 8 Aug 2012 10:07:13 -0700 (PDT)
Received: from ec2-23-21-76-251.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 B02CA21F846F for <pcp@ietf.org>; Wed, 8 Aug 2012 10:07:11 -0700 (PDT)
Received: from lilac-too.home (permutation-city.suchdamage.org [69.25.196.28]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 5EF8D2014C; Wed, 8 Aug 2012 13:07:10 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <003b01cd7587$a111b760$e3352620$@com>
Date: Wed, 08 Aug 2012 13:07:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <15990E87-2D59-49B1-845C-2A4CB5A1FBD6@lilacglade.org>
References: <9B57C850BB53634CACEC56EF4853FF653B6EC381@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <7FE144CF-00E3-4451-8CBE-A6A684DB7CC4@yegin.org> <067d01cd73fd$765a6c50$630f44f0$@com> <D6D2DEED-C35A-45AB-8B72-96195C308DB9@yegin.org> <57FF0F8E-1B86-410F-8B6B-C4893A28222F@lilacglade.org> <BB72B80F-0622-4A5B-A985-79D8AED13E0B@apple.com> <003b01cd7587$a111b760$e3352620$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: pcp@ietf.org
Subject: Re: [pcp] Comparison of PCP authentication
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: Wed, 08 Aug 2012 17:07:14 -0000

On Aug 8, 2012, at 1:02 PM, Dan Wing wrote:
> So, I think we are okay -- assuming we keep the idea that the PCP 
> client tries to first send a PCP request (and not to first send
> a PANA request).  

Actually, we don't keep this, even now.  There is certainly a notion that a client could be configured to use authentication for all (or some) PCP exchanges, and that the authentication would come first.  

> However, I do worry that implementations may optimize themselves
> to send a PANA request first, which would cause the problem you
> describe if they send the PANA request to a NAT-PMP server.  That
> is, this would be a problem:
> 
>  PCP client                           NAT-PMP server
>      |                                    |    
> 1.    |-------(authentication message)---->|
> 2.    |<--NAT-PMP error--------------------|
>      |                                    | 
> 
> But the PCP client doesn't speak NAT-PMP, so there isn't a way
> for it to handle that case, anyway (no matter if we had PCP
> authentication or not).
> 
> In summary, I think we can skate around problems with talking
> to a NAT-PMP server.

Makes sense.

Margaret