[Curdle] new AD review comments on draft-ietf-curdle-ssh-ed25519-ed448-08

Benjamin Kaduk <kaduk@mit.edu> Tue, 04 June 2019 17:40 UTC

Return-Path: <kaduk@mit.edu>
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 76AAC12015F; Tue, 4 Jun 2019 10:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 5lwmZjD13hgV; Tue, 4 Jun 2019 10:40:37 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABAC0120157; Tue, 4 Jun 2019 10:40:34 -0700 (PDT)
Received: from prolepsis.kaduk.org (c-24-16-119-19.hsd1.wa.comcast.net [24.16.119.19]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x54HeU9Z011878 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 4 Jun 2019 13:40:32 -0400
Date: Tue, 04 Jun 2019 10:40:30 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: draft-ietf-curdle-ssh-ed25519-ed448.all@ietf.org
Cc: curdle@ietf.org
Message-ID: <20190604174029.GC8678@prolepsis.kaduk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/ZVNxioREgZjBn-2KxMNfU1Ah-ZA>
Subject: [Curdle] new AD review comments on draft-ietf-curdle-ssh-ed25519-ed448-08
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Jun 2019 17:40:40 -0000

Hi all,

I'm just about ready to send this to the IESG, but there seems to be a
few things to fix, first:

(1) In Section 8 we say "The generation of SSHFP resource records for
"ssh-ed448" keys is described as follows." but then give only an example
and not a description of what to do.  We need to say more about this
procedure

(2) I'm not sure if the chain on the opsdir review got fully resolved;
see https://mailarchive.ietf.org/arch/msg/curdle/DZc2Sr19zJ71nnC3pSIF0uPhaCk

(3) The shepherd writeup says that Ben did not confirm IPR (non)disclosure per
BCPs 78 and 79 -- Ben, can you please do so now?

(4) Daniel, can you please update the shepherd writeup to reflect the
discussions with the directorate reviewers about document status?  I'm
sure that some IESG members will ask "why not Informational?" if we
don't forestall them.

Thanks,

Ben