Reviewer: Christer Holmberg 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-core-cf-reg-update-04 Reviewer: Christer Holmberg Review Date: 2025-02-26 IETF LC End Date: 2025-03-10 IESG Telechat date: Not scheduled for a telechat Summary: The document updates and clarifies the procedures for registering CoAP Content-Formats, is well written and easy to understand. However, I have one editorial comment that I would like the authors to address. Major issues: N/A Minor issues: N/A Nits/editorial comments: It is a little confusing when the updates to RFC 7252 are in the IANA Considerations section of the document. In addition, new procedures are added in Sections 5.1 and 5.2, but those should be new 12.3 subsections in RFC 7252. I suggest to have a dedicated "Updates to RFC 7252" section, where the text in Sections 5.1 and Sections 5.2 are also added as new Sections 12.3.1 and Sections 12.3.2 to RFC 7252. For example: ---- 4. Updates to RFC 7252 This Section updates Section 12.3, and adds the new Sections 12.3.1 and 12.3.2, to [RFC7252]. 4.1. Updates to Section 12.3 // The text in Section 5 4.2. New Section 12.3.1 // The text in Section 5.1 4.2. New Section 12.3.2 // The text in Section 5.2 ---- The Security Considerations then become Section 5. The IANA Considerations become Section 6, and there you only need to state something like: "This document updates the IANA procedures of [RFC7252] for registering CoAP Content-Formats." -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
