[lamps] [IANA #1261900] expert review for draft-ietf-lamps-lightweight-cmp-profile (cmp)

[Sabrina Tanamal via RT <[e-mail]>]

Hi John, 

Thank you for your review. I'll pass on your comments to the authors. 

Best regards, 

Sabrina Tanamal
Lead IANA Services Specialist

On Thu Jan 12 17:48:49 2023, [e-mail] wrote:
> First time as a reviewer, I guess I'm supposed to say if it is
> approved, denied or needs more information.
> 
> I will say "denied".   I believe I found a small issue which I
> reported below, so if that is confirmed and corrected, then I will
> switch to "approved".
> 
> Cheers,
> 
> John Gray
> 
> 
> -----Original Message-----
> From: John Gray
> Sent: Thursday, January 12, 2023 11:46 AM
> To: [e-mail]
> Cc: Brockhaus, Hendrik <[e-mail]>; David von
> Oheimb <[e-mail]>; Steffen Fries
> <[e-mail]>
> Subject: RE: [EXTERNAL] [IANA #1261900] expert review for draft-ietf-
> lamps-lightweight-cmp-profile (cmp)
> 
> I have reviewed the document for the Well-Known URI Path Segments for
> this document:   https://datatracker.ietf.org/doc/draft-ietf-lamps-
> lightweight-cmp-profile/.   I think there is an issue in section 6.1
> that looks like a copy/paste type of error:
> 
> Snippet from table 1 in section 6.1 (page 79):
> 
> +----------------------------+--------------------+---------+
> | Get CA Certificates        |     getcacerts     | Section |
> |                            |                    | 4.3.1   |
> +----------------------------+--------------------+---------+
> | Get Root CA Certificate    |   getrootupdate    | Section |
> | Update                     |                    | 4.3.2   |
> +----------------------------+--------------------+---------+
> | Get CA Certificates        | getcertreqtemplate | Section |
> |                            |                    | 4.3.1   |
> +----------------------------+--------------------+---------+
> | CRL Update Retrieval       |      getcrls       | Section |
> |                            |                    | 4.3.4   |
> +----------------------------+--------------------+---------+
> 
> The "Get CA Certificates" PKI Management Operation is listed twice.
> The second time it refers to the same section 4.3.1.   The path
> Segment says "getcertreqtemplate".    I compared it to the CoAP
> Transfer from table 2 in section 6.2, and section 6.2 seems correct
> and it contains a PKI Management Operation of "Get Certificate Request
> Template" which is what I think was meant in section 6.1.
> 
> From Table 2 section 6.2 (page 82) - Notice no duplicate and reference
> to 4.3.3
> +---------------------------------------+---------+---------+
> | Get CA Certificates                   |   crts  | Section |
> |                                       |         | 4.3.1   |
> +---------------------------------------+---------+---------+
> | Get Root CA Certificate Update        |   rcu   | Section |
> |                                       |         | 4.3.2   |
> +---------------------------------------+---------+---------+
> | Get Certificate Request Template      |   att   | Section |
> |                                       |         | 4.3.3   |
> +---------------------------------------+---------+---------+
> | CRL Update Retrieval                  |   crls  | Section |
> |                                       |         | 4.3.4   |
> +---------------------------------------+---------+---------+
> 
> 
> So I think section 6.1 needs to be updated as follows:
> 
> +----------------------------+--------------------+---------+
> | Get CA Certificates        |     getcacerts     | Section |
> |                            |                    | 4.3.1   |
> +----------------------------+--------------------+---------+
> | Get Root CA Certificate    |   getrootupdate    | Section |
> | Update                     |                    | 4.3.2   |
> +----------------------------+--------------------+---------+
> | Get Certificate Request Template        | getcertreqtemplate |
> | Section |
> |                            |                    | 4.3.3   |
> +----------------------------+--------------------+---------+
> | CRL Update Retrieval       |      getcrls       | Section |
> |                            |                    | 4.3.4   |
> +----------------------------+--------------------+---------+
> 
> The rest of it looks correct to me.
> 
> 
> Is this all I need to do for this review, or is there something more
> official needed?
> 
> 
> Cheers,
> 
> John Gray
> 
> -----Original Message-----
> From: John Gray
> Sent: Wednesday, January 11, 2023 4:29 PM
> To: [e-mail]
> Subject: RE: [EXTERNAL] [IANA #1261900] expert review for draft-ietf-
> lamps-lightweight-cmp-profile (cmp)
> 
> Hi Sabrina,
> 
> Its on my list of items to complete.  I know January 12th (tomorrow)
> is the deadline.   I've just been in meetings all day so this is a
> task I'm hoping to complete by tomorrow.
> 
> Thanks for pinging me about it...   😊
> 
> John Gray
> 
> 
> -----Original Message-----
> From: Sabrina Tanamal via RT <[e-mail]>
> Sent: Wednesday, January 11, 2023 4:26 PM
> Cc: John Gray <[e-mail]>; [e-mail]
> Subject: [EXTERNAL] [IANA #1261900] expert review for draft-ietf-
> lamps-lightweight-cmp-profile (cmp)
> 
> WARNING: This email originated outside of Entrust.
> DO NOT CLICK links or attachments unless you trust the sender and know
> the content is safe.
> 
> ______________________________________________________________________
> Hi John (cc: lamps wg),
> 
> Have you had a chance to review this request?
> 
> Thanks,
> 
> Sabrina Tanamal
> Lead IANA Services Specialist
> 
> On Fri Dec 30 00:50:09 2022, sabrina.tanamal wrote:
> > Dear John (cc: lamps wg),
> >
> > As the designated expert for the CMP Well-Known URI Path Segments
> > registry, can you review the proposed registration in draft-ietf-
> > lamps-lightweight-cmp-profile for us? Please see
> >
> > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-
> > iet
> > f-lamps-lightweight-cmp-__;!!FJ-
> > Y8qCqXTj2!YtpBnAjGOOsCPP5j6YbYViNYTYry
> > HrTqrfOTBYNCw2PXGvz8_A9IxOZWYMyJxbES1-lNecAAd0NIY-btTtQ0T0xTPrc$
> > profile/
> >
> > The due date is January 12th.
> >
> > If this is OK, when the IESG approves the document for publication,
> > we'll make the registration at
> >
> > https://urldefense.com/v3/__https://www.iana.org/assignments/cmp__;!!F
> > J-
> > Y8qCqXTj2!YtpBnAjGOOsCPP5j6YbYViNYTYryHrTqrfOTBYNCw2PXGvz8_A9IxOZWYM
> > yJxbES1-lNecAAd0NIY-btTtQ05lM5cLo$
> >
> > Hendrik Brockhaus and David von Oheimb are also experts for this
> > registry, but they're the authors of this document.
> >
> > Thank you,
> >
> > Sabrina Tanamal
> > Lead IANA Services Specialist
> 
> Any email and files/attachments transmitted with it are confidential
> and are intended solely for the use of the individual or entity to
> whom they are addressed. If this message has been sent to you in
> error, you must not copy, distribute or disclose of the information it
> contains. Please notify Entrust immediately and delete the message
> from your system.