Re: [Curdle] Spencer Dawkins' No Objection on draft-ietf-curdle-pkix-07: (with COMMENT)

Jim Schaad <ietf@augustcellars.com> Thu, 12 April 2018 18:50 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 824C212DA11; Thu, 12 Apr 2018 11:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 CwGQIxL1pEal; Thu, 12 Apr 2018 11:50:26 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 960A612DA0D; Thu, 12 Apr 2018 11:50:25 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 12 Apr 2018 11:47:43 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Spencer Dawkins' <spencerdawkins.ietf@gmail.com>, 'The IESG' <iesg@ietf.org>
CC: <draft-ietf-curdle-pkix@ietf.org>, 'Daniel Migault' <daniel.migault@ericsson.com>, <curdle-chairs@ietf.org>, <daniel.migault@ericsson.com>, <curdle@ietf.org>
References: <152355400876.9332.2562335587618651703.idtracker@ietfa.amsl.com>
In-Reply-To: <152355400876.9332.2562335587618651703.idtracker@ietfa.amsl.com>
Date: Thu, 12 Apr 2018 11:49:55 -0700
Message-ID: <000001d3d28f$0eeb8a30$2cc29e90$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDmhzH1B8b5FHMBHYGIm62PWCqRMaXYDL/w
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/LmrcLyPtluOiiNgW2nMFBYbNVXo>
Subject: Re: [Curdle] Spencer Dawkins' No Objection on draft-ietf-curdle-pkix-07: (with COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Apr 2018 18:50:31 -0000

Need to have

Fixed in my local copy.

Jim


> -----Original Message-----
> From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
> Sent: Thursday, April 12, 2018 10:27 AM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-curdle-pkix@ietf.org; Daniel Migault
> <daniel.migault@ericsson.com>om>; curdle-chairs@ietf.org;
> daniel.migault@ericsson.com; curdle@ietf.org
> Subject: Spencer Dawkins' No Objection on draft-ietf-curdle-pkix-07: (with
> COMMENT)
> 
> Spencer Dawkins has entered the following ballot position for
> draft-ietf-curdle-pkix-07: No Objection
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-curdle-pkix/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Nit:
> 
>   o  The EdDSA algorithms are the only IETF algorithms that currently
>       support the use of contexts, however there is a possibility that
>       there will be confusion between which algorithms need have
>                                  "need" or "need to have"? ^
>       separate keys and which do not.  This may result in a decrease of
>       security for those other algorithms.
>