Document: draft-ietf-lamps-rfc5273bis Title: Certificate Management over CMS (CMC): Transport Protocols Reviewer: Thomas Fossati Review result: Ready with Nits I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-lamps-rfc5273bis-06 Reviewer: Thomas Fossati Review Date: 2025-08-12 IETF LC End Date: 2025-08-25 IESG Telechat date: Not scheduled for a telechat Summary: The document is straightforward, concise, and well written. Major issues: none Minor issues: none Nits/editorial comments: # Sections 6.1 and 6.2 > The Content-Type header MUST have the appropriate value from Table 2. Unsure whether the “SMIME Type” parameter is used or if it’s inferred from the request/response context. I’d say the former, but maybe better avoid any potential ambiguity. # Section 7 > The title of this IP Protocol number is "pkix-cmc”. ‘title of this IP Protocol number’ sounds odd. Perhaps: ‘The Service Name is “pkix-cmc”.’ as per the associated IANA ports entry [1]. [1] https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=5318 # Section 10.1 and 10.2 * Why is IPsec normative? * Why is BCP195 normative but TLS is only informative? -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
