Re: [Ace] I-D Action: draft-ietf-ace-cmpv2-coap-transport-03.txt

[Daniel Migault <[e-mail]>]

On Mon, Oct 25, 2021 at 5:18 PM Mohit Sahni <[e-mail]> wrote:

> Hi Daniel,
>
> Please find answers to your questions:
> A) Currently there is an open source implementation to support CMP over
> CoAP maintained by @David von Oheimb <[e-mail]>. I
> believe these do not follow the draft exactly but are based on this draft.
> Here are github links:
>
>    - https://github.com/siemens/LightweightCmpRa
>    - https://github.com/siemens/embeddedCMP
>
> great. That is helpful for the shepherd

>
>    -
>
> B) I can confirm that I am not aware of any IPR. Adding @Saurabh Tripathi
> <[e-mail]> to confirm on this side also.
>
> thanks.

C) I generated the document using the xml2rfc v3 tool. The boilerplate is
> generated by the xml2rfc tool based on xml tags. It could be an issue with
> the NITS tool or XML2RFC tool, I will try to generate another txt version
> based on latest version of the tool or fix the issue manually.
>
> you did good. I was looking at the wrong place. The nits was misleading to
me.


> D) I will add a note for IANA mentioning this. Can you please review if
> this note looks good?
>
> This Internet draft references the .well-known/cmp temporary IANA registry
> [Link to:
> https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml].
> Please add a reference of this draft to the .well-known/cmp registry and if
> this draft is published before [I-D.ietf-lamps-cmp-updates] please make the
> .well-known/cmp registry permanent based on this draft's publication.
>
> That seems fine to me. They will probably ask for something else or remove
the text, but we have avoided running through the cracks.


> E) Can you confirm if this change looks good to you?
> OLD:
>    This document requires a new entry to the CoAP Content-Formats
>    Registry code for the content-type "application/pkixcmp" for
>    transfering CMP transactions over CoAP.
>
>    Type name: application
>
>    Subtype name: pkixcmp
>
> NEW:
>    This document requires a new entry to the CoAP Content-Formats
>    Registry code for the content-type "application/pkixcmp" for
>    transfering CMP transactions over CoAP from the identifier
>    range 256-9999 reserved for IETF specifications.
>
>    Type name: application
>
>    Subtype name: pkixcmp
>
>    Encoding: Content may contain arbitrary octet
>    values. The octet values are the ASN.1 DER
>    encoding of a PKI message, as defined in the
>    [RFC4210] specifications.
>
>    Reference: This internet draft and RFC4210
>
> Looks good!

> Thanks a lot for your help moving this forward.
>
> Regards
> Mohit
>
>
> On Mon, Oct 25, 2021 at 12:37 PM Daniel Migault <[e-mail]>
> wrote:
>
>> Hi,
>>
>> Here are some information I need to complete the shepherd:
>>
>> A.  Do we have existing implementation or intention to implement it.
>>
>> B. Can both co-authors confirm they are not aware of any IPR.
>>
>> C. The document seems to lack the recommended RFC 2119 boilerplate, even
>> if
>>
>>      it appears to use RFC 2119 keywords -- however, there's a paragraph with
>>      a matching beginning. Boilerplate error?
>>
>> D.  .The draft uses .well-known/cmp. .well-known/cmp is indicated as
>> temporary [iana] and cmp-updates is still a draft. I am not sure we need to
>> wait for cmp-updates to be published, but if the draft is abandoned we may
>> need to indicate IANA that the cmp needs to be moved to permanent after
>> 2022-05-20  - or may be at the publication of this draft. I suggest we add
>> a note in the IANA section which could be removed by IANA or the RFC
>> editor.
>>
>> E. I am not sure the registration of pkiccmp does not need more
>> information. More especially, I see
>>
>> https://www.iana.org/assignments/core-parameters/core-parameters.xhtml#content-formats
>> https://www.rfc-editor.org/rfc/rfc7252.html#section-12.3
>>
>> Please check what is needed and make sure the IANA is correct.
>>
>> Yours,
>> Daniel
>>
>>

-- 
Daniel Migault
Ericsson