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

Sam Hartman <hartmans@painless-security.com> Sat, 16 March 2013 18:29 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 236D721F886D for <pcp@ietfa.amsl.com>; Sat, 16 Mar 2013 11:29:43 -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 cdhCofw3c5EI for <pcp@ietfa.amsl.com>; Sat, 16 Mar 2013 11:29:42 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBCB21F886B for <pcp@ietf.org>; Sat, 16 Mar 2013 11:29:42 -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 9D47420414; Sat, 16 Mar 2013 14:29:10 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id EFEA141CF; Sat, 16 Mar 2013 14:29:36 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: Alper Yegin <alper.yegin@yegin.org>
References: <341064315C6D0D498193B256F238CF9747C9C9@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com> <5EF8B214-6563-47C7-9D48-621D9D5E1B29@yegin.org>
Date: Sat, 16 Mar 2013 14:29:36 -0400
In-Reply-To: <5EF8B214-6563-47C7-9D48-621D9D5E1B29@yegin.org> (Alper Yegin's message of "Fri, 15 Mar 2013 05:18:44 +0200")
Message-ID: <tslip4r42r3.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" <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: Sat, 16 Mar 2013 18:29:43 -0000

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

    Alper> Yeah, let me do that.

    Alper> Option 4 is based on using "expired" security associations as
    Alper> if they did not expire.

    Alper> This is obviously a bad idea. 

Alper, it's not obvious to me why using a security association for
status updates regarding an existing mapping is bad after it's expired
for new mappings.

I agree that we'll need to analyze the security of whatever we do and
document any attacks that result.

Would you care to explain why you think people set up security
association expiration so we can evaluate whether this particular use
opens up any attacks with regard to the design goals of security
association expiration?