Note: This ballot was opened for revision 07 and is now closed.Search Mailarchive
Thanks for your work on this draft. I agree with Alexey's comment on the normative reference and just have a tiny nit for the introduction: I suggest you remove the word recent since the reference on SHA-1 is 6 years old: s/Due to recent security concerns with SHA-1 [RFC6194]/Due to security concerns with SHA-1 [RFC6194]/
I understand that a new version will be published based on Linda Dunbar's OPS DIR review. Thank you.
1) To me this sentence does not belong in the IANA section as it is basically the main point of the document: "This document augments the Key Exchange Method Names in [RFC4253] and [RFC4250]." Maybe move it to sec 3? 2) Can you explain why the pre-5378 boilerplate is used?
RFC 6234 must be normative, as it is required to implement this document.
Section 1, paragraph 2: New MODP groups are being introduced starting with the MODP 3072-bit group 15 all use SHA512 as the hash algorithm. I can't parse this. Should there be a sentence break between "15" and "all"? I was surprised to find section 4 here; in part because it isn't related to the addition of new algorithms, but mostly because it's not mentioned in the abstract or the introduction. Please add mention of this erratum correction to both sections. I'm pretty sure RFC6234 needs to be normative.