Mike Bishop has entered the following ballot position for draft-ietf-tls-keylogfile-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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-tls-keylogfile/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for the work to document this widely used de facto standard. My only comments are minor, and mostly nits. In Section 2, "Including this field allows..." sounds like an argument for including it, but it's not an optional field. Consider a more declarative phrasing, such as "This field is used to correlate..." ===NITS FOLLOW=== Abstract, "supports the logging information" => "supports logging information" or "supports the logging of information" Section 2.2, "An implementation ... use" => "An implementation ... uses" or "Implementations ... use" Section 4.2, "in depth" => "in-depth" _______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
