Document: draft-ietf-lamps-rfc5273bis Title: Certificate Management over CMS (CMC): Transport Protocols Reviewer: Vidhi Goel Review result: Ready with Nits This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-art@xxxxxxxx if you reply to or forward this review. This document is ready with some nits I noted below: Nits: Section 4: Enrollment messages and responses may be transferred between clients and servers using file-system-based mechanisms, such as when enrollment is performed for an off-line client I am not sure if dash (-) is needed at file system based and offline. Please double check and remove any unnecessary dashes Section 5: A file name with the ".p7c" extension MUST be specified as part of the content- type Extra space before type Section 5: A file name with the ".p7m" extension MUST be specified as part of the content-type or content- disposition Extra space before disposition Section 6: this section describes the conventions for use of HTTP [HTTP] as a transport layer. In most circumstances, the use of HTTP over TLS [HTTP] Both sentences have a reference to HTTP RFC, did you mean to refer to a different RFC where you mentioned HTTP over TLS? Section 6: Clients and servers are expected to follow the other rules and restrictions in [HTTP] No need for "the" before other rules Thanks, Vidhi -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
