Dear Shwetha Bhandari Thank you for your review and comments. > Von: Shwetha Bhandari via Datatracker <noreply@xxxxxxxx> > > > 1) Overall it is quite confusing on how these updates will be published - will there > be bis for each RFC4210, RFC5912 and RFC6712? There was a discussion at IETF 113 LAMPS meeting on CMP Updates style vs. RFC4210bis. Please see the meeting minutes: https://datatracker.ietf.org/meeting/113/materials/minutes-113-lamps-01.pdf As Russ points out in the shepherd writeup, the WG decided to go ahead with the CMP Updates document and provide a consolidated bis document in a later step. Regarding RFC5912, CMP Updates only updates the ASN.1 module for CMP. In detail it is like this, - Section 2 and Appendix A.1 update RFC4210, - Appendix A.2 updates RFC5912 Section 9, and - Section 3 updates RFC6712. Russ added this strategy also to the shepherd writeup: When this update was started, the number of updates was expected to be smaller. It is recognized that complex update documents place a burden on implementers. So, when LAMPS WG tries to progress CMP to Internet Standard, a bis document will be produced to combine the base specification and the updates. > > 2) The sections that update RFC6712 - There seems to be circular dependency > between this draft and draft-ietf-lamps-lightweight-cmp-profile. Assuming the > RFC6712 updates will be published as RFC6712 bis, Section 3.6. HTTP > Request-URI: " Further path segments, e.g., as specified in the Lightweight CMP > Profile [I-D.ietf-lamps-lightweight-cmp-profile], could indicate PKI > management operations using an operationLabel <operation>. A valid > full CMP URI can look like this:..." > This text is redundant and confusing as the operationLabel <operation> is only > defined in draft-ietf-lamps-lightweight-cmp-profile. Why should it be referenced > in 6712 bis? 6712 bis with the text changes proposed in this draft does not > restrict extension of the URI path. CMP Updates introduces the general concept on how URI path segments may be used with CMP. As a concrete path segment CMP Updates defines the 'p'. For further path segments CMP Updates refers to Lightweight CMP Profile. It is planned to publish CMP Updates together Lightweight CMP Profile. Russ stated in the shepherd writeup of Lightweight CMP Profile the following: There are four related Internet-Drafts that are coming to the IESG at roughly the same time. Please publish all four at the same time with consecutive RFC numbers. The documents are: 1. draft-ietf-lamps-cmp-updates 2. draft-ietf-lamps-cmp-algorithms 3. draft-ietf-lamps-lightweight-cmp-profile 4. draft-ietf-ace-cmpv2-coap-transport > > 3) General question on CMP server operations and management - is there a > document that covers data model, APIs to configure and collect operational > statistics of a CMP server? I could not find one. IF there is one, how will these > updates impact that. I am not aware of additional documents covering such data models. I hope, I sufficiently addressed your comments. If not or if you have further questions, please let me know. Hendrik -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
