> On 5 May 2016, at 5:14 PM, Stephen Farrell <[email protected]> wrote: > > > > On 24/04/16 17:23, Alexey Melnikov wrote: >> Alexey Melnikov has entered the following ballot position for >> draft-ietf-tls-chacha20-poly1305-04: 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-tls-chacha20-poly1305/ >> >> >> >> ---------------------------------------------------------------------- >> COMMENT: >> ---------------------------------------------------------------------- >> >> Nit: SHA-256 probably needs a normative reference. > > I added an RFC editor note. If someone has the right reference > to add handy I can add that too. Or I'll get to it in a bit,
RFC 6234 works. Or: “Secure Hash Standard (SHS)”, FIPS PUB 180-4, August 2015, http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
