Re: [sidr] WGLC for draft-ietf-sidr-algorithm-agility-03

Christopher Morrow <morrowc.lists@gmail.com> Sun, 20 November 2011 06:56 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E08E121F854D for <sidr@ietfa.amsl.com>; Sat, 19 Nov 2011 22:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.555
X-Spam-Level:
X-Spam-Status: No, score=-103.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 9E0uQd0c2M6Y for <sidr@ietfa.amsl.com>; Sat, 19 Nov 2011 22:56:31 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 618C321F84FA for <sidr@ietf.org>; Sat, 19 Nov 2011 22:56:31 -0800 (PST)
Received: by iaeo4 with SMTP id o4so7009336iae.31 for <sidr@ietf.org>; Sat, 19 Nov 2011 22:56:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=eaP/Mlg+kIl6q0E6wk5SJsHR6WbLv5tP1XQ+jiOIdVU=; b=pxHAgp18lycjsWrrQC+QmpJlKxyOm9NTfLM42TqCJsFgEcQZ6BVuHBnWuAv12mIPjN X+eO9uYB/KYIAKPt2PeXG0yhHkPTFQY0UW/yVTBZtuZ48jAogekg3A0j0rZcF7vzfpou DBlJf1epc2BD2/fFruGcY8ac9CpNUehYGiocU=
MIME-Version: 1.0
Received: by 10.231.41.4 with SMTP id m4mr2146658ibe.44.1321772191009; Sat, 19 Nov 2011 22:56:31 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.231.202.142 with HTTP; Sat, 19 Nov 2011 22:56:30 -0800 (PST)
In-Reply-To: <4EC60A7D.3030306@ieca.com>
References: <CAD6DA02.1C611%terry.manderson@icann.org> <p06240803cad6af1b0ce7@193.0.26.186> <7B40776F-D906-46DA-A788-C4E9C0E758A9@verisign.com> <p06240803cad951813fd9@193.0.26.186> <CB6FE413-BEC2-4910-AEEF-98D6EAFD4E83@verisign.com> <p06240802cadde494171b@128.89.89.6> <3F1388E3-A694-42C9-AE2F-F12BF15DC86F@verisign.com> <p06240811cade1873e723@128.89.89.6> <BDA75A7E-2B2D-44A5-A18F-2D7DA01DF3A2@verisign.com> <p06240808cadf618efaa8@128.89.89.6> <E9BAE21C-A8EF-4D07-90C1-E8A5FD7F00E7@verisign.com> <p06240803cae62a2b13af@128.89.89.129> <CAH1iCiotmm47yZ_S_JyY8a0cODPFcnLe-CUSbzjYm7fdPcZDkA@mail.gmail.com> <p06240801cae63c0d5322@172.20.1.65> <CAH1iCioh1em9KjhFq2vTijpAOogL4nnc5=k0Eg3NFejVVdACRQ@mail.gmail.com> <CAL9jLaa+f3Be6M1tfrD+vLaivQ0Xf4a_6CEnvaSzXJDW3dZiFQ@mail.gmail.com> <4EC60A7D.3030306@ieca.com>
Date: Sun, 20 Nov 2011 01:56:30 -0500
X-Google-Sender-Auth: SaUJfAqr_t07YiNsok3rdgTwoNM
Message-ID: <CAL9jLaYy5cZa_cjVJ--LSH3H9-9KnUL5wdA0vdk6w8kkpes8PA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Sean Turner <turners@ieca.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sidr@ietf.org list" <sidr@ietf.org>
Subject: Re: [sidr] WGLC for draft-ietf-sidr-algorithm-agility-03
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Nov 2011 06:56:32 -0000

On Fri, Nov 18, 2011 at 2:34 AM, Sean Turner <turners@ieca.com> wrote:
> On 11/18/11 2:21 PM, Christopher Morrow wrote:
>>
>> On Thu, Nov 17, 2011 at 12:50 PM, Brian Dickson
>> <brian.peter.dickson@gmail.com>  wrote:
>>
>>> Here's the thing - if all-A chains continue to exist until Phase 4,
>>> _and_ fallback to Suite A is required, this is a downgrade-attack
>>> vulnerability.
>>>
>>
>> It seems to me that as long as there are consumers of cert material
>> that can not do the 'new hotness' (B in your example) you will have to
>> make products in the 'old and busted' form. Once everyone can do 'new
>> hotness', there is a relatively short period of time required to kill
>> off 'old and busted'.
>>
>> I don't think you can get away with not making 'old and busted' until
>> everyone is able to plan ball, eh?
>
> Hope of hopes here is that we don't just transition when an alg is broke.
>  Algs weaken over time - that's just a fact.  When we retire an alg because
> it doesn't cut it anymore, then running with the old unbroken alg is a
> downgrade but assuming the alg ain't broke then it's probably okay for the
> transition period.

do I have to apologize for the MIB refernce?