[Curdle] comments on draft-ietf-curdle-ssh-kex-sha2-09

[Daniel Migault <[e-mail]>]

Hi,

Please find the shepherd write-up [1] for draft-ietf-curdle-ssh-kex-sha2
[2]  as well as my comments regarding the current version below:

Unless some raises any concerns, the draft will be sent to the IESG as soon
as the current version is updated.

Yours,

Daniel

[1]
https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-kex-sha2/shepherdwriteup/
[2] https://tools.ietf.org/html/draft-ietf-curdle-ssh-kex-sha2-09

section 1

maybe the sentence below should be removed.

   [TO BE REMOVED: Please send comments on this draft to
   [e-mail].]

reference I-D.ietf-curdle-ssh-modp-dh-sha2 is now rfc8268, so references
should be updated and moved from informational to normative.

section 3.1

Curve25519 and SHA-256 may point to references such as RFC8031 RFC6234.

It might be also good to have a reference to the code point
curves25519-sha256 with draft-ietf-curdle-ssh-curves.

section 3.2

Curve448 and curve448-256 may also point to references RFC8031 and
draft-ietf-curdle-ssh-curves

section 3.3


I think the sentence below repeats itself and should be changed:
""
It is recommended that these key exchange groups NOT
be used. This key exchange SHOULD NOT be used.
"""

section 3.5

diffiehellman-group1-sha1 should be referenced by RFC4253

section 3.6 - 3.11

The code points should refer to rfc8268.

section 3.7

It is surprising DH is defined so deep in the document ;-)

section 3.12 -3.14

The code points should should refer rfc5656

section 3.15 - 3.17

The code points should refer rfc4462

section 3.18 - 3.27

The code points should refer draft-ietf-curdle-gss-keyex-sha2


section 3.28 - 3.29

The code points should  mention rfc 4432

In section 3.29 I think that more text should be added to justify the MAY.
rsa2048-sha256 matches all reasons rsa1024-sha1 's status is MUST NOT.

section 4

""Of course, use of SHA384""" may be """Of course, the use of SHA384"""
I might be wrong as well.

section 5

new-modp should be replaced by rfc8268



section 8

rsa1024-sha1 is the only code point to be updated by
IANA in that case, it may be easier to mention it rather than
referring to the table.

The nits provides the following output.

idnits 2.15.00

tmp/draft-ietf-curdle-ssh-kex-sha2-09.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
  ----------------------------------------------------------------------------

     (Using the creation date from RFC4250, updated by this document, for
     RFC5378 checks: 2005-03-16)

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If you
     have contacted all the original authors and they are all willing to grant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer.
     (See the Legal Provisions document at
     https://trustee.ietf.org/license-info for more information.)

  -- The document date (July 30, 2017) is 142 days in the past.  Is this
     intentional?


  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  == Outdated reference: A later version (-03) exists of
     draft-ietf-curdle-gss-keyex-sha2-02

  == Outdated reference: A later version (-06) exists of
     draft-ietf-curdle-ssh-curves-05

  == Outdated reference: draft-ietf-curdle-ssh-dh-group-exchange has been
     published as RFC 8270

  == Outdated reference: draft-ietf-curdle-ssh-modp-dh-sha2 has been
     published as RFC 8268


     Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.