Stephen Farrell has entered the following ballot position for draft-ietf-ipsecme-chacha20-poly1305-11: Yes
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-ipsecme-chacha20-poly1305/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- intro: "gold standard" is being a bit too keen IMO, I'd say toning the language down a bit would be better. intro: 3DES may be the "only other widely supported" cipher for IPsec, but that's not true more generally. section 2 says: "As the ChaCha20 block function is not applied directly to the plaintext, no padding should be necessary." That "should" could be confusing as written if a reader thinks it means their code doesn't have to do padding. It might be better to e.g. say something like "In theory no padding is needed for this cipher, however, in keeping with..." section 3: Is "SHOULD inlude no padding" really right? I'd have thought a MAY was better there. "MUST accept any length" is also a bit odd - what if I (try:-) add loads of padding? Appendices: thanks for those - I assume someone checked them for you? (I didn't:-) _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
