[Curdle] Adam Roach's No Objection on draft-ietf-curdle-ssh-curves-11: (with COMMENT)
Adam Roach via Datatracker <noreply@ietf.org> Wed, 04 September 2019 04:12 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: curdle@ietf.org
Delivered-To: curdle@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 12FBE120072; Tue, 3 Sep 2019 21:12:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Roach via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-curdle-ssh-curves@ietf.org, Daniel Migault <daniel.migault@ericsson.com>, curdle-chairs@ietf.org, daniel.migault@ericsson.com, curdle@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Adam Roach <adam@nostrum.com>
Message-ID: <156757036499.20526.150480359990174703.idtracker@ietfa.amsl.com>
Date: Tue, 03 Sep 2019 21:12:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/9D1RIiEm38OFAuXNdKpFi7fR46g>
Subject: [Curdle] Adam Roach's No Objection on draft-ietf-curdle-ssh-curves-11: (with COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 04 Sep 2019 04:12:46 -0000
Adam Roach has entered the following ballot position for draft-ietf-curdle-ssh-curves-11: 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-ssh-curves/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for the work on documenting this key exchange method. I'm a little surprised that there is no discussion of deployment considerations for deploying "curve25519-sha256" into an environment in which "curve25519-sha256@libssh.org" is already well-established (as described in the introduction), or of sunsetting the vendor-specific version. Some advice on which algorithms to offer and which ones to accept would probably be worthwhile, especially if there is any long-term hope of retiring the "curve25519-sha256@libssh.org" designator in favor of the standard one.
- [Curdle] Adam Roach's No Objection on draft-ietf-… Adam Roach via Datatracker
- Re: [Curdle] Adam Roach's No Objection on draft-i… Mark D. Baushke