IETF Logo Mail Archive

Re: [saag] draft-iab-crypto-alg-agility-00

"Salz, Rich" <rsalz@akamai.com> Sun, 06 April 2014 21:54 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 45AAA1A02AE for <saag@ietfa.amsl.com>; Sun, 6 Apr 2014 14:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, 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 yhX3emOEYF6y for <saag@ietfa.amsl.com>; Sun, 6 Apr 2014 14:54:43 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [72.246.2.115]) by ietfa.amsl.com (Postfix) with ESMTP id 36B561A029E for <saag@ietf.org>; Sun, 6 Apr 2014 14:54:42 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 92202474F8; Sun, 6 Apr 2014 21:54:36 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (unknown [172.17.121.112]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id 854B1474F7; Sun, 6 Apr 2014 21:54:36 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub5.kendall.corp.akamai.com [172.27.105.21]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id 82F1E8004F; Sun, 6 Apr 2014 21:54:36 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by USMA1EX-CASHUB5.kendall.corp.akamai.com ([172.27.105.21]) with mapi; Sun, 6 Apr 2014 17:54:35 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Ben Laurie <ben@links.org>, Russ Housley <housley@vigilsec.com>
Date: Sun, 6 Apr 2014 17:54:34 -0400
Thread-Topic: [saag] draft-iab-crypto-alg-agility-00
Thread-Index: Ac9RzS/x3aW19e1XQvSP1MFChNVf1AAFMk+A
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C7120A04EBD7@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>
In-Reply-To: <6.2.5.6.2.20140406121529.0bd2d730@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/saag/oQ06IAKHURhHx16d50nMtJgrpK0
Cc: "saag@ietf.org" <saag@ietf.org>
Subject: Re: [saag] 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: Sun, 06 Apr 2014 21:54:48 -0000

I know what the text says.  But there are no protocol operations, really, it's just HTTP/JSON, right?

Having said that, I think the agility document should say "protocols and data formats."

I was arguing (with Google folks, mainly) for crypto identifies in the CT data structures before the WG was convened. And I still think that CT should be brought in line with the letter and spirit of the agility document:  identify the mechanisms used, in the data types. If interop is a concern, make the current set be MUST and say SHOULD NOT implement anything else.

CT should not be a special case exemption from the agility spec.

	/r$

--  
Principal Security Engineer
Akamai Technology
Cambridge, MA

v2.8.7 | Report a Bug | By Email