Re: [pcp] EAP retransmits and re-authentication

Sam Hartman <hartmans@painless-security.com> Thu, 20 September 2012 15:33 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 1895F21F87B2 for <pcp@ietfa.amsl.com>; Thu, 20 Sep 2012 08:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.377
X-Spam-Level: ****
X-Spam-Status: No, score=4.377 tagged_above=-999 required=5 tests=[AWL=0.089, 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 jxMNJql4sxcb for <pcp@ietfa.amsl.com>; Thu, 20 Sep 2012 08:33:21 -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 9F42921F87E7 for <pcp@ietf.org>; Thu, 20 Sep 2012 08:33:21 -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 5BF7220167; Thu, 20 Sep 2012 11:33:11 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 91FA7414A; Thu, 20 Sep 2012 11:32:48 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
References: <14C7F4F06DB5814AB0DE29716C4F6D6702E12ABC28@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <CB96F2AF-7545-457D-96EB-F78B7666C00C@yegin.org> <tsl1ui0wvmo.fsf_-_@mit.edu> <E91C9554-FBCF-4324-A1BF-5C4D75F5264A@yegin.org> <9A2322BB-699A-4A71-89D5-9E3E48979272@yegin.org> <tslvcfbscqm.fsf_-_@mit.edu> <20FE79EA-9E75-49E7-9854-4AA24314FC7B@yegin.org> <tslipbap18s.fsf@mit.edu> <09E52F80-2292-42CB-9833-957D16DCF2AB@yegin.org> <tsl392clv10.fsf_-_@mit.edu> <505B35E4.5020108@toshiba.co.jp>
Date: Thu, 20 Sep 2012 11:32:48 -0400
In-Reply-To: <505B35E4.5020108@toshiba.co.jp> (Yoshihiro Ohba's message of "Fri, 21 Sep 2012 00:27:32 +0900")
Message-ID: <tslfw6ciuan.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] EAP retransmits and re-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: Thu, 20 Sep 2012 15:33:22 -0000

>>>>> "Yoshihiro" == Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> writes:

    Yoshihiro> While I agree that ERP is definitely not needed for PCP,
    Yoshihiro> but I think unsupporting EAP re-authentication in the
    Yoshihiro> context of RFC 3748 and RFC 5247 is NOT a good idea,
    Yoshihiro> because it enables smooth migration from old SA to new
    Yoshihiro> SA.  Without supporting EAP re-authentication in the
    Yoshihiro> context of RFC 3748 and RFC 5247, communications
    Yoshihiro> disruptions can happen during rekey, i.e., communication
    Yoshihiro> quality of PCP and data traffic controlled by PCP can
    Yoshihiro> affect in our case.

I'd like to hear from PCP implementors about whether smoothe SA
migration is even desirable.
My assumption would be that it would be entirely not worth the
complexity for PCP.

    Yoshihiro> Also, it seems that there is some desire to change
    Yoshihiro> PCP-specific authentication design to be based on
    Yoshihiro> client-

Actually, I didn't propose a change; I simply pointed out that you can
do it either way depending on what is easiest for PCP implementations;
we should pick, but what we pick should be based on the needs of the PCP
community.

It's my experience that security solutions are best when they provide a
good user experience and are easy to implement. I'm hoping to accomplish
that here.

--Sam