Re: [auth48] AUTH48: RFC-to-be 9481 <draft-ietf-lamps-cmp-algorithms-15> for your review

["Brockhaus, Hendrik" <[e-mail]>]

RFC Editor, ADs, LAMPS Chairs

Please find attached the result of the AUTH48 review.
All feedbacks to [rfced] comments and any additional comments and changes are available in the .xml document.
The .txt, .html, and .pdf documents are added just for convenience.
If all these changes are OK, I am fine with this version to be published.
Many thanks to everyone supporting this effort!

@co-authors, can you please confirm if you also agree with the publication of this version.

Hendrik

> -----Ursprüngliche Nachricht-----
> Von: [e-mail] <[e-mail]>
> Gesendet: Dienstag, 19. September 2023 08:18
> An: Brockhaus, Hendrik (T CST SEA-DE) <[e-mail]>;
> Aschauer, Hans (T CST SES-DE) <[e-mail]>; Mike
> Ounsworth <[e-mail]>; John Gray
> <[e-mail]>
> Cc: [e-mail]; [e-mail]; [e-mail];
> [e-mail]; [e-mail]
> Betreff: Re: AUTH48: RFC-to-be 9481 <draft-ietf-lamps-cmp-algorithms-15>
> for your review
>
> Authors,
>
> While reviewing this document during AUTH48, please resolve (as necessary)
> the following questions, which are also in the XML file.
>
> 1) <!-- [rfced] The algorithms must be supported to conform with what?
> Please clarify.
>
> Original:
>    RFC 4210 Appendix D.2 [RFC4210] contains a set of algorithms,
>    mandatory to be supported by conforming implementations.
>
> Perhaps:
>    It is mandatory for implementations conformant with CMP to support the
>    set of algorithms defined in Appendix D.2 of [RFC4210].
> -->
>
>
> 2) <!--[rfced] Should "cryptoanalysis" be updated to be "cryptanalysis"?
>
> Original:
>   In general, new attacks are emerging due to research
>   cryptoanalysis or increase in computing power.
>
> Perhaps:
>   In general, new attacks are emerging due to research
>   cryptanalysis or increase in computing power.
> -->
>
>
> 3) <!-- [rfced] Should "(SHAKEs)" be "(XOF)"?  Or is "SHAKEs" an example of
> an XOF?
>
> Original:
>    The SHA-3 family of hash functions is defined in FIPS Pub 202
>    [NIST.FIPS.202] and includes fixed output length variants SHA3-224,
>    SHA3-256, SHA3-384, and SHA3-512, as well as extendable-output
>    functions (SHAKEs) SHAKE128 and SHAKE256.
>
> Perhaps:
>    The SHA-3 family of hash functions is defined in FIPS Pub 202
>    [NIST_FIPS_202] and includes fixed output length variants SHA3-224,
>    SHA3-256, SHA3-384, and SHA3-512, as well as extendable-output
>    functions (XOFs) such as SHAKE128 and SHAKE256.
> -->
>
>
> 4) <!--[rfced] Should instances of "ECDSA signature algorithm" and "EdDSA
> signature algorithm" be updated to read simply "ECDSA" and "EdDSA" to
> avoid
> redundancy? If expanded, "ECDSA signature algorithm" would read "Elliptic
> Curve Digital Signature Algorithm signature algorithm" and "EdDSA signature
> algorithm" would read "Edwards-curve Digital Signature Algorithm signature
> algorithm". Please review and let us know if any updates are needed.
> -->
>
>
> 5) <!--[rfced] May we expand "SECP" as "Standard for Efficient Cryptography"?
>
> Original:
>    As specified in RFC 5480 [RFC5480] the NIST-recommended SECP curves
>    are identified by the following OIDs:
> -->
>
>
> 6) <!-- [rfced] Please review whether any of the notes in this document
> should be in the <aside> element. It is defined as "a container for
> content that is semantically less important or tangential to the
> content that surrounds it"
> (https://author/
> s.ietf.org%2Fen%2Frfcxml-
> vocabulary%23aside&data=05%7C01%7Chendrik.brockhaus%40siemens.com
> %7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e14
> 95d55a%7C1%7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3d
> 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> D%7C3000%7C%7C%7C&sdata=8uVe7ey5W2dmTMtUub21IXCSDVWSdadz7v
> D%2BGTu8y7c%3D&reserved=0).
> -->
>
>
> 7) <!--[rfced] We note that "KM_KL_ALG" is not is not present in the
> Lightweight CMP Profile or Section 7. Please review and let us know if/how
> this this citation should be updated.
>
> Original:
>    The key transport algorithm is also referred to as PROT_ENC_ALG in
>    RFC 4210 Appendix D and E [RFC4210] and as KM_KL_ALG in the
>    Lightweight CMP Profile [I-D.ietf-lamps-lightweight-cmp-profile], as
>    well as in Section 7.
> -->
>
>
> 8) <!--[rfced] We note that "PROT_ENC_ALG" is defined in Section 7.1, not
> Section 7.2. "KM_KA_ALG", "KM_KT_ALG", and "KM_KD_ALG" are defined in
> Section 7.2, not Section 7.1. "SYM_PENC_ALG" is defined in Section 7.1, not
> Section 7.2. "KM_KW_ALG" and "PROT_SYM_ALG" are defined in Section 7.2,
> not
> Section 7.2. May we update these citations accordingly?
>
> Original:
>       -  Protection of centrally generated keys: The strength of the
>          algorithms used for the key management technique (Section 7.2:
>          PROT_ENC_ALG or Section 7.1: KM_KA_ALG, KM_KT_ALG, KM_KD_ALG)
>          and the encryption of the content-encryption key and private
>          key (Section 7.2: SYM_PENC_ALG, PROT_SYM_ALG or Section 7.1:
>          KM_KW_ALG, PROT_SYM_ALG).
> -->
>
>
> 9) <!-- [rfced] It appears as though you tried to avoid citation tags being
> read as part of the text.  This has been altered in some places to include
> links and avoid too much redundancy.  Please review and let us know if you
> have any objections.
>
> For example:
>
> Original:
>    Specific conventions to be considered are specified in RFC 5754
>    Section 2 [RFC5754].
>
> Current:
>    Specific conventions to be considered are specified in Section 2 of
>    [RFC5754].
> -->
>
>
> 10) <!-- [rfced] "With submitting" is unclear here.  Perhaps "for authoring" or
> "for editing" is meant?
>
> Original:
>    Thanks to Russ Housley for supporting this draft with submitting
>    [RFC9044] and [RFC9045].
> -->
>
>
> 11) <!--[rfced] The hyphenation of SHA is inconsistent in this document.
> Please review and let us know if/how these instances may be made
> consistent.
>
> SHA-224 vs. SHA224
> SHA-256 vs. SHA256
> SHA-384 vs. SHA384
> SHA-512 vs. SHA512
> -->
>
>
> 12) <!-- [rfced] FYI - We have added expansions for abbreviations upon
> first use per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review
> each expansion in the document carefully to ensure correctness.
> -->
>
>
> 13) <!-- [rfced] Please review the "Inclusive Language" portion of the
> online Style Guide
> <https://www/.
> rfc-
> editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C01
> %7Chendrik.brockhaus%40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d8
> 39f2%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638307011095
> 161494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l
> uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=X40jS
> HsEF0HZjYpXsxifsYZdr9tgWBXs5d1w7aJOrOc%3D&reserved=0>
> and let us know if any changes are needed.
>
> Note that our script did not flag any words in particular, but this should
> still be reviewed as a best practice.
> -->
>
>
> Thank you.
>
> RFC Editor
>
>
>
> On Sep 18, 2023, at 11:01 PM, [e-mail] wrote:
>
> *****IMPORTANT*****
>
> Updated 2023/09/18
>
> RFC Author(s):
> --------------
>
> Instructions for Completing AUTH48
>
> Your document has now entered AUTH48.  Once it has been reviewed and
> approved by you and all coauthors, it will be published as an RFC.
> If an author is no longer available, there are several remedies
> available as listed in the FAQ
> (https://www.r/
> fc-
> editor.org%2Ffaq%2F&data=05%7C01%7Chendrik.brockhaus%40siemens.co
> m%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e1
> 495d55a%7C1%7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3
> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
> 3D%7C3000%7C%7C%7C&sdata=88BNjx0UKhu6XRpzl%2BgjJ4jQ0lONrojaFMH
> SrH98Fi8%3D&reserved=0).
>
> You and you coauthors are responsible for engaging other parties
> (e.g., Contributors or Working Group) as necessary before providing
> your approval.
>
> Planning your review
> ---------------------
>
> Please review the following aspects of your document:
>
> *  RFC Editor questions
>
>    Please review and resolve any questions raised by the RFC Editor
>    that have been included in the XML file as comments marked as
>    follows:
>
>    <!-- [rfced] ... -->
>
>    These questions will also be sent in a subsequent email.
>
> *  Changes submitted by coauthors
>
>    Please ensure that you review any changes submitted by your
>    coauthors.  We assume that if you do not speak up that you
>    agree to changes submitted by your coauthors.
>
> *  Content
>
>    Please review the full content of the document, as this cannot
>    change once the RFC is published.  Please pay particular attention to:
>    - IANA considerations updates (if applicable)
>    - contact information
>    - references
>
> *  Copyright notices and legends
>
>    Please review the copyright notice and legends as defined in
>    RFC 5378 and the Trust Legal Provisions
>    (TLP -
> https://trustee/
> .ietf.org%2Flicense-
> info%2F&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7C0bfb160
> ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e1495d55a%7C1
> %7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC
> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%
> 7C%7C%7C&sdata=FmSnz8a2kfYjVcfi%2Fe%2FdW0E%2FIoGFskejOXzVadd5%2
> FlI%3D&reserved=0).
>
> *  Semantic markup
>
>    Please review the markup in the XML file to ensure that elements of
>    content are correctly tagged.  For example, ensure that <sourcecode>
>    and <artwork> are set correctly.  See details at
>
> <https://autho/
> rs.ietf.org%2Frfcxml-
> vocabulary&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7C0bfb
> 160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e1495d55a%
> 7C1%7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3d8eyJWIjo
> iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300
> 0%7C%7C%7C&sdata=1HpyfrSZqxZtH0s%2F8XanC7IvXCw2Z%2BWGuTJjXm3hx
> Ew%3D&reserved=0>.
>
> *  Formatted output
>
>    Please review the PDF, HTML, and TXT files to ensure that the
>    formatted output, as generated from the markup in the XML file, is
>    reasonable.  Please note that the TXT will have formatting
>    limitations compared to the PDF and HTML.
>
>
> Submitting changes
> ------------------
>
> To submit changes, please reply to this email using 'REPLY ALL' as all
> the parties CCed on this message need to see your changes. The parties
> include:
>
>    *  your coauthors
>
>    *  [e-mail] (the RPC team)
>
>    *  other document participants, depending on the stream (e.g.,
>       IETF Stream participants are your working group chairs, the
>       responsible ADs, and the document shepherd).
>
>    *  [e-mail], which is a new archival mailing list
>       to preserve AUTH48 conversations; it is not an active discussion
>       list:
>
>      *  More info:
>
> https://mailarc/
> hive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-
> 4Q9l2USxIAe6P8O4Zc&data=05%7C01%7Chendrik.brockhaus%40siemens.co
> m%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e1
> 495d55a%7C1%7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3
> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
> 3D%7C3000%7C%7C%7C&sdata=qFguWdVUu7d7kc%2B9UUPF5Y5%2Bpo6Wv
> o5nsR4UO9MCbWk%3D&reserved=0
>
>      *  The archive itself:
>
> https://mailarc/
> hive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C01%7Che
> ndrik.brockhaus%40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%
> 7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C63830701109516149
> 4%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi
> LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ftBsfE1N8n
> Udx60NXDWfMHz0Y8r62asgO%2FMqEAoYa%2F4%3D&reserved=0
>
>      *  Note: If only absolutely necessary, you may temporarily opt out
>         of the archiving of messages (e.g., to discuss a sensitive matter).
>         If needed, please add a note at the top of the message that you
>         have dropped the address. When the discussion is concluded,
>         [e-mail] will be re-added to the CC list and
>         its addition will be noted at the top of the message.
>
> You may submit your changes in one of two ways:
>
> An update to the provided XML file
>  - OR -
> An explicit list of changes in this format
>
> Section # (or indicate Global)
>
> OLD:
> old text
>
> NEW:
> new text
>
> You do not need to reply with both an updated XML file and an explicit
> list of changes, as either form is sufficient.
>
> We will ask a stream manager to review and approve any changes that seem
> beyond editorial in nature, e.g., addition of new text, deletion of text,
> and technical changes.  Information about stream managers can be found in
> the FAQ.  Editorial changes do not require approval from a stream manager.
>
>
> Approving for publication
> --------------------------
>
> To approve your RFC for publication, please reply to this email stating
> that you approve this RFC for publication.  Please use 'REPLY ALL',
> as all the parties CCed on this message need to see your approval.
>
>
> Files
> -----
>
> The files are available here:
>
> https://www.rf/
> c-
> editor.org%2Fauthors%2Frfc9481.xml&data=05%7C01%7Chendrik.brockhaus
> %40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd9579
> 4fd4addab42e1495d55a%7C1%7C0%7C638307011095161494%7CUnknown%
> 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
> iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lf4KBWb3ZNrbu3dqXPwY3Rf
> NfsZ9hZptJVCNjllWTFs%3D&reserved=0
>
> https://www.rf/
> c-
> editor.org%2Fauthors%2Frfc9481.html&data=05%7C01%7Chendrik.brockhaus
> %40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd9579
> 4fd4addab42e1495d55a%7C1%7C0%7C638307011095161494%7CUnknown%
> 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
> iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DEgSwjXAiKpR%2BJVg4tiy7N
> xFImaUjMchd07SJDgt%2FlM%3D&reserved=0
>
> https://www.rf/
> c-
> editor.org%2Fauthors%2Frfc9481.pdf&data=05%7C01%7Chendrik.brockhaus
> %40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd9579
> 4fd4addab42e1495d55a%7C1%7C0%7C638307011095161494%7CUnknown%
> 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
> iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=a%2BnLJnjdUUErKPDQywgv
> MqpHStyD6NzTb0j%2F%2FbIstog%3D&reserved=0
>
> https://www.rf/
> c-
> editor.org%2Fauthors%2Frfc9481.txt&data=05%7C01%7Chendrik.brockhaus%
> 40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794f
> d4addab42e1495d55a%7C1%7C0%7C638307011095161494%7CUnknown%7
> CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL
> CJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=y%2Bt4QeVFRgrFfDSf3wJ1KtL5
> tyY9qjzynZTvkHnvno0%3D&reserved=0
>
> Diff file of the text:
>
> https://www.rf/
> c-editor.org%2Fauthors%2Frfc9481-
> diff.html&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7C0bfb160
> ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e1495d55a%7C1
> %7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC
> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%
> 7C%7C%7C&sdata=0KfeeaQRwmhBUvBEYJ0CraV2RtQ2L2IulXJiN5CXPDY%3D&
> reserved=0
>
> https://www.rf/
> c-editor.org%2Fauthors%2Frfc9481-
> rfcdiff.html&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7C0bfb1
> 60ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e1495d55a%7
> C1%7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi
> MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300
> 0%7C%7C%7C&sdata=uttS5jfJgi80AfkBK2BkfLhtaPsLXt1UpV3uA4%2BODvE%3
> D&reserved=0 (side by side)
>
> Diff of the XML:
>
> https://www.rf/
> c-editor.org%2Fauthors%2Frfc9481-
> xmldiff1.html&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7C0b
> fb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4addab42e1495d55a
> %7C1%7C0%7C638307011095161494%7CUnknown%7CTWFpbGZsb3d8eyJWI
> joiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3
> 000%7C%7C%7C&sdata=nZQUrT6eR0WJ2tVZxdSLe%2FQEKGNGe2c4S5mGeeX
> nMQw%3D&reserved=0
>
> The following files are provided to facilitate creation of your own
> diff files of the XML.
>
> Initial XMLv3 created using XMLv2 as input:
>
> https://www.rf/
> c-
> editor.org%2Fauthors%2Frfc9481.original.v2v3.xml&data=05%7C01%7Chendr
> ik.brockhaus%40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C3
> 8ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638307011095161494%7
> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Am5FMUKu8w
> MvpMdW699FR50NiSr3ciYeSbtP9xGqp88%3D&reserved=0
>
> XMLv3 file that is a best effort to capture v3-related format updates
> only:
>
> https://www.rf/
> c-
> editor.org%2Fauthors%2Frfc9481.form.xml&data=05%7C01%7Chendrik.brock
> haus%40siemens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd
> 95794fd4addab42e1495d55a%7C1%7C0%7C638307011095161494%7CUnkno
> wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h
> aWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Fw2tdHqsEGOA3QZj3p
> %2FIxpZWgIfX1tXcIjD3hJVPFvw%3D&reserved=0
>
>
> Tracking progress
> -----------------
>
> The details of the AUTH48 status of your document are here:
>
> https://www.rf/
> c-
> editor.org%2Fauth48%2Frfc9481&data=05%7C01%7Chendrik.brockhaus%40si
> emens.com%7C0bfb160ff5cc4a029a6208dbb8d839f2%7C38ae3bcd95794fd4a
> ddab42e1495d55a%7C1%7C0%7C638307011095161494%7CUnknown%7CTW
> FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV
> CI6Mn0%3D%7C3000%7C%7C%7C&sdata=NX8j5vr%2BP3CZ4DTpMu2%2B2Zx
> FLrdJDXIC0PZXDD%2Ftn34%3D&reserved=0
>
> Please let us know if you have any questions.
>
> Thank you for your cooperation,
>
> RFC Editor
>
> --------------------------------------
> RFC9481 (draft-ietf-lamps-cmp-algorithms-15)
>
> Title            : Certificate Management Protocol (CMP) Algorithms
> Author(s)        : H. Brockhaus, H. Aschauer, M. Ounsworth, J. Gray
> WG Chair(s)      : Russ Housley, Tim Hollebeek
> Area Director(s) : Roman Danyliw, Paul Wouters
>