[Gen-art] Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07

Linda Dunbar <Linda.dunbar@huawei.com> Mon, 07 January 2019 03:50 UTC

Return-Path: <Linda.dunbar@huawei.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E7E127133; Sun, 6 Jan 2019 19:50:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar <Linda.dunbar@huawei.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-curdle-ssh-ed25519-ed448.all@ietf.org, curdle@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154683304030.17040.15801682371972802372@ietfa.amsl.com>
Date: Sun, 06 Jan 2019 19:50:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ReDtcJMqTkeHcNZW5bGcZTpVYWI>
Subject: [Gen-art] Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 07 Jan 2019 03:50:40 -0000

Reviewer: Linda Dunbar
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>;.

Document: draft-ietf-curdle-ssh-ed25519-ed448-??
Reviewer: Linda Dunbar
Review Date: 2019-01-06
IETF LC End Date: 2019-01-04
IESG Telechat date: Not scheduled for a telechat

Summary:

This document proposes two names for public key algorithms (which are specified
by other RFCs): ssh-ed25519 & ssh-ed448

Major issues:

There is no "Standard" being specified by this document. The document has a few
sentences to explain "public key algorithm for use with SSH in accordance with
RFC4253, RFC4251" and give a name. and One sentence to say "Signatures are
generated according to the procedure in RFC8032".

I don't understand why it is "Standard Track" document, non do I understand why
it is a WG document. Does it take a whole WG to come out with a name for an
algorithm specified in an RFC?

Minor issues:

Nits/editorial comments:

Linda Dunbar