Re: [saag] AD review of draft-iab-crypto-alg-agility-06

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 24 August 2015 21:45 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3A81B2B89 for <saag@ietfa.amsl.com>; Mon, 24 Aug 2015 14:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTmc5PQ2v5Uh for <saag@ietfa.amsl.com>; Mon, 24 Aug 2015 14:45:45 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 936391B2B77 for <saag@ietf.org>; Mon, 24 Aug 2015 14:45:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E3A85BF13; Mon, 24 Aug 2015 22:45:43 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cctLIgNse5fN; Mon, 24 Aug 2015 22:45:42 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.21.200]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CE629BF10; Mon, 24 Aug 2015 22:45:41 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1440452741; bh=58U4BSsOtcNID152+T+7ikpzuVzYJRYOd50QBrL658o=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=ur1m5HeRmaoRtlnHF8Pzzys2gHzU7NWscziKYNjuZe3yS/MEs1+iSuKVd4XvUNTvG VXPt7zHnm1frty6VYaKD1cr425e4a3yXv9n8kZ05GubvOp8S8tyOQDeCasdUykliWX OTfngjH7dmrxWoQgjvEc22TSXgEbDHIqIMH/QAUM=
Message-ID: <55DB9085.2080504@cs.tcd.ie>
Date: Mon, 24 Aug 2015 22:45:41 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: "Salz, Rich" <rsalz@akamai.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
References: <55A938F1.9090404@cs.tcd.ie> <CD936D80-BEA2-4918-828C-E3A392761EC5@gmail.com> <20150727194020.GD15860@localhost> <55B6D36C.70105@iang.org> <20150728013020.GO4347@mournblade.imrryr.org> <DM2PR0301MB0655CF099FA7C56E9B9D24A9A88D0@DM2PR0301MB0655.namprd03.prod.outlook.com> <20150728053035.GR4347@mournblade.imrryr.org> <CAHbuEH7B3_G9vAhw=U2tuz-Uh8mKMUfL6s=H+BOG96FDZaACig@mail.gmail.com> <20150824212907.GN9021@mournblade.imrryr.org> <619ffebb05ba4e2a9af03a6dcc768d6e@ustx2ex-dag1mb2.msg.corp.akamai.com> <846AD897-C38F-4528-849D-B98B2D87798B@gmail.com> <b27927b4fb7d41b28a9bb7695971501f@ustx2ex-dag1mb2.msg.corp.akamai.com>
In-Reply-To: <b27927b4fb7d41b28a9bb7695971501f@ustx2ex-dag1mb2.msg.corp.akamai.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/lhr2ma0y63zvJ_F-ttsUreAIW40>
Cc: "saag@ietf.org" <saag@ietf.org>
Subject: Re: [saag] AD review of draft-iab-crypto-alg-agility-06
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2015 21:45:47 -0000


On 24/08/15 22:40, Salz, Rich wrote:
>> I agree this is the problem/poster child for this discussion.  I'd rather phrase it
>> that in some cases, deprecated crypto will be used when libraries/software
>> can't be updated rather than saying it's okay because it falls into OS.  But this
>> may just be me.
> 
> It's not just you. :)

And me too. However, there was strong push back to that from apps folks
when we debated this before. So even though I think all 3 of us are
correct, I think we're in the rough. But no harm validating that again.

S.

> 
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag
> 
>