On Thu, May 25, 2023 at 1:15 PM Mohit Sahni <mohit06...@gmail.com> wrote:

> Hi Paul,
> I think you may be looking at the older version of the draft. (Please
> check
> https://datatracker.ietf.org/doc/html/draft-ietf-ace-cmpv2-coap-transport)
>

Odd, I was and I wasn't. Maybe a caching issue. Thanks for pointing out
most of the ballot comments have been addressed.


> I submitted the xml version and the boilerplate is auto generated from the
> xml. I am not sure how to change the boiler plate text. My guess is that
> it's the xml2rfc tool that's adding the boilerplate.
>

We will let the RFC Editor worry about that.


> The reference of 5280 is added in the below text in the version 10 of the
> draft:
> Section 4 bullet point 4:
> An EE might not witness all of the Announcement messages when using the
> CoAP Observe option [RFC7641], since the Observe option is a "best-effort"
> approach and the server might lose its state for subscribers to its
> announcement messages. The EEs may use an alternate method described in
> section 2.6 to obtain time critical changes such as CRL [RFC5280] updates.
>

right.


>
> Reference to draft-ietf-lamps-lightweight-cmp-profile-13
> <https://datatracker.ietf.org/doc/draft-ietf-lamps-lightweight-cmp-profile/13/>
>  has
> been updated to version 21 now in the latest draft.
>

Indeed.


> The comment "without compromising the integrity of " be better than
> "without compromising the security" (given CMP does not provide
> confidentiality" was not directed me but to the ADs (i.e. Paul) If you
> agree, I can make the change to the text.
>

I agree that it is a better word, however since the bullet point immediatly
following it talks about confidentiality, I think it is fine to leave it
too.
If you were to do another update, please fold it in. Otherwise perhaps we
can change the one word during the RFC Editor phase.

I've cleared the state, so the document will proceed onwards now.

Paul


> Thanks
> Mohit
>
> On Thu, May 25, 2023 at 9:07 AM Paul Wouters <paul.wouters=
> 40aiven...@dmarc.ietf.org> wrote:
>
>> I should probably put it in Revised ID needed, as there are a few bugs
>> left:
>>
>> - the 2119 boilerplate triggers warning (although I don't see the
>> discrepancy)
>> - RFC 5280 is listed as informative reference but it is not references
>> anywhere in the text
>> - outdated reference to draft-ietf-lamps-lightweight-cmp-profile-13
>> <https://datatracker.ietf.org/doc/draft-ietf-lamps-lightweight-cmp-profile/13/>
>> -  "without compromising the integrity of " be better than "without
>> compromising the security" (given CMP does not provide confidentiality
>>
>> It seems the authors haven't gone yet through all the ballot comments at
>> https://datatracker.ietf.org/doc/draft-ietf-ace-cmpv2-coap-transport/ballot/
>>
>> I'll put it in revised ID needed now since at least the the above bullet
>> points should be fixed.
>>
>> Paul
>>
>> On Thu, May 25, 2023 at 11:13 AM Daniel Migault <mglt.i...@gmail.com>
>> wrote:
>>
>>> As far as I understand it, the document is in " Approved-announcement
>>> to be sent::AD Followup", which means the AD needs to approve the latest
>>> version to be sent to the RFC editor. Th elatest version has been published
>>> on may 15, so my guess is that the approval should come in the next few
>>> days.
>>>
>>> Yours,
>>> Daniel
>>>
>>>
>>> On Thu, May 25, 2023 at 8:52 AM Brockhaus, Hendrik <
>>> hendrik.brockh...@siemens.com> wrote:
>>>
>>>> Thanks to Mohit and Saurabh for the update also from my side.
>>>> Are there any further changes planned or is anything else necessary
>>>> before moving the draft to RFC Editor state?
>>>>
>>>> Hendrik
>>>>
>>>> > Von: Ace <ace-boun...@ietf.org> Im Auftrag von Daniel Migault
>>>> >
>>>> > Thanks for the submission Mohit.
>>>> >
>>>> > Yours,
>>>> > Daniel
>>>> >
>>>> > ________________________________________
>>>> > From: Ace <ace-boun...@ietf.org> on behalf of
>>>> internet-dra...@ietf.org
>>>> > <internet-dra...@ietf.org>
>>>> > Sent: Monday, May 15, 2023 4:44 PM
>>>> > To: i-d-annou...@ietf.org
>>>> > Cc: ace@ietf.org
>>>> > Subject: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-10.txt
>>>> >
>>>> >
>>>> > A New Internet-Draft is available from the on-line Internet-Drafts
>>>> > directories. This Internet-Draft is a work item of the Authentication
>>>> and
>>>> > Authorization for Constrained Environments (ACE) WG of the IETF.
>>>> >
>>>> >    Title           : CoAP Transfer for the Certificate Management
>>>> Protocol
>>>> >    Authors         : Mohit Sahni
>>>> >                      Saurabh Tripathi
>>>> >    Filename        : draft-ietf-ace-cmpv2-coap-transport-10.txt
>>>> >    Pages           : 11
>>>> >    Date            : 2023-05-15
>>>> >
>>>> > Abstract:
>>>> >    This document specifies the use of Constrained Application Protocol
>>>> >    (CoAP) as a transfer mechanism for the Certificate Management
>>>> >    Protocol (CMP).  CMP defines the interaction between various PKI
>>>> >    entities for the purpose of certificate creation and management.
>>>> >    CoAP is an HTTP-like client-server protocol used by various
>>>> >    constrained devices in the IoT space.
>>>> >
>>>> > The IETF datatracker status page for this Internet-Draft is:
>>>> > https://datatra/
>>>> > cker.ietf.org%2Fdoc%2Fdraft-ietf-ace-cmpv2-coap-
>>>> > transport%2F&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7Cb7
>>>> > 45642c8925408378c508db55a8f629%7C38ae3bcd95794fd4addab42e1495d55
>>>> > a%7C1%7C0%7C638197956407483228%7CUnknown%7CTWFpbGZsb3d8eyJ
>>>> > WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
>>>> > C3000%7C%7C%7C&sdata=NRMWomPpx1FbVSzl%2FLu0U0HQX3tpT9gXX2cbu
>>>> > Tq4cro%3D&reserved=0
>>>> >
>>>> > There is also an htmlized version available at:
>>>> > https://datatra/
>>>> > cker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-ace-cmpv2-coap-transport-
>>>> > 10&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7Cb745642c892
>>>> > 5408378c508db55a8f629%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7
>>>> > C0%7C638197956407483228%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
>>>> > LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
>>>> > %7C%7C&sdata=VlTKaJOKWtgld6rtRVKIen9ic5etr%2B3%2FXME4JIwoBG0%3D
>>>> > &reserved=0
>>>> >
>>>> > A diff from the previous version is available at:
>>>> > https://author/
>>>> > -tools.ietf.org
>>>> %2Fiddiff%3Furl2%3Ddraft-ietf-ace-cmpv2-coap-transport-
>>>> > 10&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7Cb745642c892
>>>> > 5408378c508db55a8f629%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7
>>>> > C0%7C638197956407483228%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
>>>> > LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
>>>> > %7C%7C&sdata=Nzg9WKRaw3P47ucvb3zEF0%2BsePKxR6Ps1oKjtdrZAXc%3D&
>>>> > reserved=0
>>>> >
>>>> > Internet-Drafts are also available by rsync at rsync.ietf.org:
>>>> :internet-drafts
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > Ace mailing list
>>>> > Ace@ietf.org
>>>> > https://www.ie/
>>>> > tf.org%2Fmailman%2Flistinfo%2Face&data=05%7C01%7Chendrik.brockhaus%
>>>> > 40siemens.com%7Cb745642c8925408378c508db55a8f629%7C38ae3bcd9579
>>>> > 4fd4addab42e1495d55a%7C1%7C0%7C638197956407483228%7CUnknown%
>>>> > 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
>>>> > iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gHv%2FbNIlQSoDTUBx1NY6S
>>>> > Snkc%2BtzbcFbp%2BXwInvd6Ss%3D&reserved=0
>>>> >
>>>> > _______________________________________________
>>>> > Ace mailing list
>>>> > Ace@ietf.org
>>>> > https://www.ie/
>>>> > tf.org%2Fmailman%2Flistinfo%2Face&data=05%7C01%7Chendrik.brockhaus%
>>>> > 40siemens.com%7Cb745642c8925408378c508db55a8f629%7C38ae3bcd9579
>>>> > 4fd4addab42e1495d55a%7C1%7C0%7C638197956407483228%7CUnknown%
>>>> > 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
>>>> > iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gHv%2FbNIlQSoDTUBx1NY6S
>>>> > Snkc%2BtzbcFbp%2BXwInvd6Ss%3D&reserved=0
>>>>
>>>
>>>
>>> --
>>> Daniel Migault
>>> Ericsson
>>>
>> _______________________________________________
>> Ace mailing list
>> Ace@ietf.org
>> https://www.ietf.org/mailman/listinfo/ace
>>
>
_______________________________________________
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Reply via email to