Document: draft-ietf-avt-srtp-big-aes-05 Reviewer: Richard Barnes Review Date: 10 Dec 2010 IETF LC End Date: IESG Telechat date: (if known) Summary: This document is mostly ready for publication as a Standards Track RFC. I have one question about Suite B compatibility. Major issues: Minor issues: [Section4] The Suite B specifications require the use of SHA-256 and SHA-384 as hash functions for SECRET and TOP SECRET, respectively. Given that Suite B compatibility is listed as an objective of this document, it seems like there should be a cryptosuite that would use Suite B hash algorithms as well as encryption algorithms. Nits/editorial comments: [Section3] In the first sentence, should "AES_CM PRF" be changed to "AES_CM_PRF"? [Section3.1] Do you want to say explicitly that stronger KDFs MAY be used? That you could use the AES_256_CM KDF with AES_192_CM as the bulk encryption algorithm, or use either 192 or 256 with 128?