Ran Thank you for your review and your comments. I am sorry for responding so late. The co-authors and I wanted to consolidate the feedback to the different reviews. I addressed the nits reported below. The latest version of the draft ready for submission and a diff to the latest version on datatracker are available on github: - https://lamps-wg.github.io/cmp-updates/#go.draft-ietf-lamps-rfc4210bis.html - https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-lamps-rfc4210bis&url_2=https://lamps-wg.github.io/cmp-updates/draft-ietf-lamps-rfc4210bis.txt Hendrik > Von: Ran Chen via Datatracker <noreply@xxxxxxxx> > Gesendet: Mittwoch, 23. Oktober 2024 12:35 > > Reviewer: Ran Chen > Review result: Has Nits > > I have reviewed this document as part of the Ops area directorate's ongoing effort to > review all IETF documents being processed by the IESG. These comments were > written primarily for the benefit of the Ops area directors. > Document editors and WG chairs should treat these comments just like any other > last-call comments. > > This document describes the Internet X.509 Public Key Infrastructure (PKI) > Certificate Management Protocol (CMP). It obsoletes RFC 4210 and RFC9480, and > in various parts of the draft, the importance of maintaining compatibility with older > versions when updating the CMP protocol has been emphasized. Here are some > nits. > > ## NITS: > - Expand on first use - CMS > - s/when the validity of the the "old with old" / when the validity of the "old with old"/ - > s/Updated the the page header to 'CMP' / Updated the page header to 'CMP' / > > The following idnits warnings should be attended: > draft-ietf-lamps-rfc4210bis-14.txt: > -(1840): Line appears to be too long, but this could be caused by non-ascii > characters in UTF-8 encoding > Checking boilerplate required by RFC 5378 and the IETF Trust (see > > https://trustee.ietf.or/ > g%2Flicense- > info&data=05%7C02%7Chendrik.brockhaus%40siemens.com%7C91ea54ca1de34b > d6f67708dcf34e55f4%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C63 > 8652764985820251%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC > JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=d > 0A6ND1FW6oMuP3YwGlg%2FYP5lY1ii3J6zu8DNc2MG%2F4%3D&reserved=0): > ---------------------------------------------------------------------------- > No issues found here. > Checking nits according to > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%25 > 2Fid-info%2F1id- > guidelines.txt&data=05%7C02%7Chendrik.brockhaus%40siemens.com%7C91ea54c > a1de34bd6f67708dcf34e55f4%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C > 0%7C638652764985838471%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw > MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C& > sdata=rdKo9A0%2FCWNr38wvm4m2zHDCJp1gHxSab6lwYNVzzbw%3D&reserved > =0: > ---------------------------------------------------------------------------- > == There are 2 instances of lines with non-ascii characters in the document. > Checking nits according to > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%25 > 2Fid- > info%2Fchecklist&data=05%7C02%7Chendrik.brockhaus%40siemens.com%7C91e > a54ca1de34bd6f67708dcf34e55f4%7C38ae3bcd95794fd4addab42e1495d55a%7C1 > %7C0%7C638652764985849774%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w > LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C% > 7C&sdata=ujXVHNcTuobWA9nhabBDTjcBdsXnZ3Cnc3M5G9lx2F4%3D&reserved= > 0 : > ---------------------------------------------------------------------------- > == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses > in the document. If these are example addresses, they should be changed. > -- The draft header indicates that this document obsoletes RFC9480, but the > abstract doesn't seem to directly say this. It does mention RFC9480 > though, so this could be OK. > -- The draft header indicates that this document updates RFC5912, but the > abstract doesn't seem to directly say this. It does mention RFC5912 > though, so this could be OK. > -- The abstract seems to indicate that this document updates RFC9480, but > the header doesn't have an 'Updates:' line to match this. > ..... > Summary: 2 errors (**), 0 flaws (~~), 10 warnings (==), 34 comments (--). > Run idnits with the --verbose option for more detailed information about the items > above. Thanks for your contribution! > > Best Regards, > Ran Chen > > -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
