Re: [pcp] Posted auth req slide that was edited during meeting

Sam Hartman <hartmans@painless-security.com> Mon, 18 March 2013 12:14 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 EFB9921F8D03 for <pcp@ietfa.amsl.com>; Mon, 18 Mar 2013 05:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 b+57qv1XdvxM for <pcp@ietfa.amsl.com>; Mon, 18 Mar 2013 05:14:35 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 62E7421F85B0 for <pcp@ietf.org>; Mon, 18 Mar 2013 05:14:35 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 0EE1320115; Mon, 18 Mar 2013 08:13:59 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id B047341CF; Mon, 18 Mar 2013 08:14:29 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: yoshihiro.ohba@toshiba.co.jp
References: <341064315C6D0D498193B256F238CF9747C9C9@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com> <5EF8B214-6563-47C7-9D48-621D9D5E1B29@yegin.org> <tslip4r42r3.fsf@mit.edu> <674F70E5F2BE564CB06B6901FD3DD78B12CD0A01@tgxml337.toshiba.local>
Date: Mon, 18 Mar 2013 08:14:29 -0400
In-Reply-To: <674F70E5F2BE564CB06B6901FD3DD78B12CD0A01@tgxml337.toshiba.local> (yoshihiro ohba's message of "Sat, 16 Mar 2013 19:52:37 +0000")
Message-ID: <tslk3p4zyze.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] Posted auth req slide that was edited during meeting
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: Mon, 18 Mar 2013 12:14:36 -0000

>>>>>   <yoshihiro.ohba@toshiba.co.jp> writes:

    > Sam, It is quite obvious from the definition EAP re-authentication
    > in RFC 5247:

    > " EAP Re-Authentication EAP authentication between an EAP peer and
    > a server with whom the EAP peer shares valid unexpired EAP keying
    > material.  ^^^^^^^^^ "


I'm sorry, but that doesn't answer my question at all.  You're quoting
definitions at me.  I was hoping you'd be willing to engage in a
discussion of what security properties PCP needs and what attacks are
enabled by various decisions we make here.
Would you be willing to do that?

--Sam