Re: [Gen-art] Gen-ART Last Call review of draft-iab-crypto-alg-agility-07.txt

Russ Housley <housley@vigilsec.com> Thu, 03 September 2015 18:59 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C5AF1A0163; Thu, 3 Sep 2015 11:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 hIXx2IZBwcMW; Thu, 3 Sep 2015 11:59:42 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id B2E191A8AEF; Thu, 3 Sep 2015 11:59:42 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 44AD1F241AA; Thu, 3 Sep 2015 14:59:32 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id iJjF2h2eVO1d; Thu, 3 Sep 2015 14:58:05 -0400 (EDT)
Received: from [192.168.2.100] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 8A375F2414D; Thu, 3 Sep 2015 14:59:02 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <E87B771635882B4BA20096B589152EF63A8EBB57@eusaamb107.ericsson.se>
Date: Thu, 03 Sep 2015 14:58:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA6AD9A8-325F-4344-8AE4-E5C53314058F@vigilsec.com>
References: <E87B771635882B4BA20096B589152EF63A8C9181@eusaamb107.ericsson.se> <B3AB6849-3274-423D-B508-34B93E0B4A1C@vigilsec.com> <E87B771635882B4BA20096B589152EF63A8EBB57@eusaamb107.ericsson.se>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/ARhFKkijlOLJLwIfG4eegFo3C2k>
Cc: "draft-iab-crypto-alg-agility.all@ietf.org" <draft-iab-crypto-alg-agility.all@ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-iab-crypto-alg-agility-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 18:59:44 -0000

Suresh:

{ Dropping parts that have been resolved. }

>>> * Section 3.4
>>> 
>>> The default server or
>>>    responder configuration SHOULD disable such algorithms
>> 
>> I do not understand this comment.
> 
> This text seems to be at odds with the earlier statement that
> 
> "Some nations specify cryptographic algorithms, and then require their 
> use through legislation or regulations"
> 
> It would be nice to clarify.

The idea is that only the administrators that must follow the legislation or regulations need to enable them.  I think this point is clear already, but you did not copy the whole sentence:

   The default server or
   responder configuration SHOULD disable such algorithms; in this way,
   explicit action by the system administrator is needed to enable them
   where they are actually required.


>>> * Section 2
>>> 
>>> OLD:
>>> one or more algorithm or suite identifier
>>> 
>>> NEW:
>>> one or more algorithm or suite identifiers
>> 
>> If you are talking about Section 2.1, this has been rewritten based on another comment:
>> 
>>    IETF protocols that make use of cryptographic algorithms MUST support
>>    one or more algorithm or suite.  The protocol MUST include a
>>    mechanism to identify the algorithm or suite that is being used.
> 
> s/one or more algorithm or suite/one or more algorithms or suites/

Fixed.

Russ