[Curdle] Spencer Dawkins' No Objection on draft-ietf-curdle-ssh-dh-group-exchange-05: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Tue, 12 September 2017 18:48 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
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 C3BF11330B5; Tue, 12 Sep 2017 11:48:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-curdle-ssh-dh-group-exchange@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.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150524208179.17923.6018833793093966718.idtracker@ietfa.amsl.com>
Date: Tue, 12 Sep 2017 11:48:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/lCvRJ7ZevRDWPRC4foj1FEoMnaY>
Subject: [Curdle] Spencer Dawkins' No Objection on draft-ietf-curdle-ssh-dh-group-exchange-05: (with COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
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, 12 Sep 2017 18:48:02 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-curdle-ssh-dh-group-exchange-05: 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-dh-group-exchange/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

So, I see that the recommendations are mostly SHOULDs.

Is this, perhaps, for backward compatibility with SSH implementations that
don't implement this specification?

This isn't remotely something I'm smart about, but I do wonder about bid-down
attacks to, say, 1024. Is that possible?