Re: [saag] [Trans] draft-iab-crypto-alg-agility-00
"Salz, Rich" <rsalz@akamai.com> Tue, 08 April 2014 14:10 UTC
Return-Path: <rsalz@akamai.com>
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 F001B1A03E4; Tue, 8 Apr 2014 07:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.472
X-Spam-Level:
X-Spam-Status: No,
score=-4.472 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272] 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 bIGn9CH16EE4;
Tue, 8 Apr 2014 07:10:07 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (prod-mail-xrelay02.akamai.com
[72.246.2.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1F72C1A03F6;
Tue, 8 Apr 2014 07:10:03 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (localhost [127.0.0.1]) by
postfix.imss70 (Postfix) with ESMTP id B460A284A8;
Tue, 8 Apr 2014 14:10:02 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (unknown [172.17.121.112]) by
prod-mail-xrelay02.akamai.com (Postfix) with ESMTP id 9FC6528441;
Tue, 8 Apr 2014 14:10:02 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com
(usma1ex-cashub4.kendall.corp.akamai.com [172.27.105.20]) by
prod-mail-relay07.akamai.com (Postfix) with ESMTP id 792768003C;
Tue, 8 Apr 2014 14:10:02 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by
USMA1EX-CASHUB4.kendall.corp.akamai.com ([172.27.105.20]) with mapi;
Tue, 8 Apr 2014 10:10:02 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Ben Laurie <benl@google.com>
Date: Tue, 8 Apr 2014 10:10:01 -0400
Thread-Topic: [Trans] [saag] draft-iab-crypto-alg-agility-00
Thread-Index: Ac9TM/8HsmFpMT5DRZeb66rjILytWgAACODg
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C7120AC188A7@USMBX1.msg.corp.akamai.com>
References: <5999195E-9073-4649-A224-BF71BA61CBAF@vigilsec.com>
<CAG5KPzzqSQ++YpQcnYesecL0GQ0+J0ieMXBrNk6txMAC58xEQQ@mail.gmail.com>
<2A0EFB9C05D0164E98F19BB0AF3708C7120A04EBD0@USMBX1.msg.corp.akamai.com>
<6.2.5.6.2.20140406121529.0bd2d730@resistor.net>
<2A0EFB9C05D0164E98F19BB0AF3708C7120A04EBD7@USMBX1.msg.corp.akamai.com>
<CAG5KPzxihe+k0x0njC+BANacmrrQyfU5RAY_EYcMYW2rx8DZfw@mail.gmail.com>
<2A0EFB9C05D0164E98F19BB0AF3708C7120A04ED14@USMBX1.msg.corp.akamai.com>
<CAG5KPzzzmJhcPfs0cJuS3f8Lu_Rua9dj0XWaOZ0RQ0Mwyd+egw@mail.gmail.com>
<2A0EFB9C05D0164E98F19BB0AF3708C7120AC18663@USMBX1.msg.corp.akamai.com>
<CABrd9SQaGTFzRaaxs7HNJ7uD_Bb=qPtCtTTsu-ZFYh+QAduzsg@mail.gmail.com>
In-Reply-To: <CABrd9SQaGTFzRaaxs7HNJ7uD_Bb=qPtCtTTsu-ZFYh+QAduzsg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/saag/jyk3Ck4F-iShFWmPAm-EWVyBW0w
Cc: "trans@ietf.org" <trans@ietf.org>, "saag@ietf.org" <saag@ietf.org>
Subject: Re: [saag] [Trans] draft-iab-crypto-alg-agility-00
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: <http://www.ietf.org/mail-archive/web/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: Tue, 08 Apr 2014 14:10:11 -0000
> As I responded to Steve, I agree that there should be an identifier, but it belongs in the metadata about the logs. I do not understand why metadata is more secure then the data itself. I strongly disagree that CT should be a special case from the general agility doc. /r$ -- Principal Security Engineer Akamai Technology Cambridge, MA
- [saag] draft-iab-crypto-alg-agility-00 Russ Housley
- Re: [saag] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] draft-iab-crypto-alg-agility-00 Salz, Rich
- Re: [saag] draft-iab-crypto-alg-agility-00 S Moonesamy
- Re: [saag] draft-iab-crypto-alg-agility-00 Salz, Rich
- Re: [saag] draft-iab-crypto-alg-agility-00 S Moonesamy
- Re: [saag] draft-iab-crypto-alg-agility-00 Stephen Farrell
- Re: [saag] draft-iab-crypto-alg-agility-00 S Moonesamy
- Re: [saag] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] draft-iab-crypto-alg-agility-00 Salz, Rich
- Re: [saag] draft-iab-crypto-alg-agility-00 Salz, Rich
- Re: [saag] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] draft-iab-crypto-alg-agility-00 S Moonesamy
- Re: [saag] draft-iab-crypto-alg-agility-00 Stephen Kent
- Re: [saag] draft-iab-crypto-alg-agility-00 Salz, Rich
- Re: [saag] draft-iab-crypto-alg-agility-00 Stephen Kent
- Re: [saag] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Salz, Rich
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Salz, Rich
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Dmitry Belyavsky
- Re: [saag] draft-iab-crypto-alg-agility-00 Stephen Kent
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Stephen Kent
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Phillip Hallam-Baker
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Ben Laurie
- Re: [saag] [Trans] draft-iab-crypto-alg-agility-00 Phillip Hallam-Baker