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

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

Dear Alanna

Thank you for this reminder.
Mike, John, Hans, and I are working on our response.
As I am on vacation next week, it will take until the week after to respond in detail.

Best regards,
Hendrik

> -----Ursprüngliche Nachricht-----
> Von: Alanna Paloma <[e-mail]>
> Gesendet: Donnerstag, 28. September 2023 18:37
> An: Brockhaus, Hendrik (T CST SEA-DE) <[e-mail]>;
> Aschauer, Hans (T CST SES-DE) <[e-mail]>; Mike
> Ounsworth <Mike.Ounsworth=[e-mail]>; John Gray
> <[e-mail]>
> Cc: [e-mail]; [e-mail]; [e-mail];
> [e-mail]; [e-mail]
> Betreff: Re: [EXTERNAL] AUTH48: RFC-to-be 9481 <draft-ietf-lamps-cmp-
> algorithms-15> for your review
>
> Hi Hendrik, Hans, Mike, and John,
>
> This is a friendly reminder that we await your responses to the questions that
> we previously sent. We will wait for these to be addressed before continuing
> with the publication process.
>
> The AUTH48 status page for this document is located here:
> https://www.rf/
> c-
> editor.org%2Fauth48%2Frfc9481&data=05%7C01%7Chendrik.brockhaus%40si
> emens.com%7C5cdd08f64c614039c01008dbc041248b%7C38ae3bcd95794fd4
> addab42e1495d55a%7C1%7C0%7C638315158766830546%7CUnknown%7CT
> WFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJ
> XVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CQtN98nGOfC1vegSKDTZTw4Ac
> 9%2Fc7FL%2Fly5Y54PGTok%3D&reserved=0
>
> Thank you,
> RFC Editor/ap
>
> > On Sep 20, 2023, at 9:02 AM, Alanna Paloma <[e-mail]> wrote:
> >
> > Hi Mike,
> >
> > We will await for the queries to be addressed as well as reviews and
> approvals from each author prior to publishing this document. There is no
> requirement that reviews and approvals be complete within 48 hours.  While
> we encourage timely review, our goal is for the document to be as correct as
> possible upon publication.
> >
> > Thank you,
> > RFC Editor/ap
> >
> >> On Sep 19, 2023, at 6:08 AM, Mike Ounsworth
> <Mike.Ounsworth=[e-mail]> wrote:
> >>
> >> Hi Hendrik,
> >>
> >> Looks like we still have some editorial work to do here.
> >>
> >> If my understanding of AUTH48 is correct, then we only have 48 hours to
> make these changes? This is a particularly bad week for me as I’m travelling
> for the ICMC FIPS conference.
> >>
> >> ---
> >> Mike Ounsworth
> >>
> >> From: [e-mail] <[e-mail]>
> >> Sent: Tuesday, September 19, 2023 1:18 AM
> >> To: [e-mail]; [e-mail];
> Mike Ounsworth <[e-mail]>; John Gray
> <[e-mail]>
> >> Cc: [e-mail]; [e-mail]; [e-mail];
> [e-mail]; [e-mail]
> >> Subject: [EXTERNAL] 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: 
> >> 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://urldef/
> ense.com%2Fv3%2F__https%3A%2F%2Fauthors.ietf.org%2Fen%2Frfcxml-
> vocabulary*aside__%3BIw!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdosEmHCWn%24&data=05%7C01%7Chendrik.
> brockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38
> ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766830546%7
> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=T%2FyZ3MlAaV
> E1fLvkzDR3MdtIuvWczYqeKGkVjKuRawk%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://urldef/
> ense.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fstyleguide%2Fpart2%2F*inclusive_language__%3BIw!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdooPqpENE%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766830546%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=30LRr6EhMU25CJ
> z6NpLfI5i5gVrNHtgrje2h11oHlYs%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://urldef/
> ense.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Ffaq%2F__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdomoLbptT%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766830546%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JIk62TjoIHaE%2F
> S%2B2Jy4POgzt13vSAvD%2FqHRKejgMcJw%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://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Ftrustee.ietf.org%2Flicense-
> info%2F__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdote7kIsH%24&data=05%7C01%7Chendrik.br
> ockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38ae
> 3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766830546%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iFFqpNh0fST5yES
> GQFOb9zGSrpd8OrsEq2tW3UUcr3I%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://urldef/
> ense.com%2Fv3%2F__https%3A%2F%2Fauthors.ietf.org%2Frfcxml-
> vocabulary__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdopqw80La%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766830546%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HpZIOSyGwtm8d
> OrFXPSJDAOTZy0HDiKcvC8RuIOT1Mc%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://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2
> Fietf-announce%2Fyb6lpIGh-4Q9l2USxIAe6P8O4Zc__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdot0LAEg0%24&data=05%7C01%7Chendrik.br
> ockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38ae
> 3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766830546%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fAnNnDlK%2BbIq
> 8%2BS72v4e3Z1CMsoZBhIkMAlvTmYi%2BeA%3D&reserved=0
> >>
> >>     *  The archive itself:
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrows
> e%2Fauth48archive%2F__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdokxfp9tV%24&data=05%7C01%7Chendrik.br
> ockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38ae
> 3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766830546%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tkdFJ%2Fm583pvh
> AD%2Bft2UKjFIWUdwvNP2CMzakcytpHA%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://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481.xml__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdouLKIf_u%24&data=05%7C01%7Chendrik.br
> ockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38ae
> 3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XbEm%2F1sk82T1
> w3GLaog%2B1krzRu92Rdbcu50z%2FaQWb70%3D&reserved=0
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481.html__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdovQ-
> I1jn%24&data=05%7C01%7Chendrik.brockhaus%40siemens.com%7C5cdd08f
> 64c614039c01008dbc041248b%7C38ae3bcd95794fd4addab42e1495d55a%7C
> 1%7C0%7C638315158766987529%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
> C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000
> %7C%7C%7C&sdata=0b3Nygy5892OtHJ%2BGFybIiR5Lca9gPGLn7Px8QeTAOY%
> 3D&reserved=0
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481.pdf__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdonlM9NEY%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9Dr7kz4uSlMpTB
> 4owizRyyhK%2FaktESewHHXM%2BcI9XNY%3D&reserved=0
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481.txt__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdotCr9f09%24&data=05%7C01%7Chendrik.br
> ockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38ae
> 3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tcwZR1J2MVMDD
> 51p6XiTEmXRirVvJ9R2J%2F%2FXSNhXd0s%3D&reserved=0
> >>
> >> Diff file of the text:
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481-diff.html__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdoovrAGe6%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=D%2BABOA67D%
> 2FJOOz4YtqUQNsg6JGxadRV%2Bi%2By1kmh1Z14%3D&reserved=0
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481-rfcdiff.html__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdouCPXw6k%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=h9b%2FqBGNqY7
> 7WbHXHjt6D2AOUETtIrJaT%2FiE7rZmrbs%3D&reserved=0 (side by side)
> >>
> >> Diff of the XML:
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481-xmldiff1.html__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdok_JoZM_%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=INfRdH78UOTcyD
> QdMamuy2Y05Hln6yH2DZUHGqSWaF4%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://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481.original.v2v3.xml__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdogw_PEhs%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0OXJbmCGcd%2F
> CZ0iqY5p%2Fze3drrP4Q%2B3w2G0xXLFKIdU%3D&reserved=0
> >>
> >> XMLv3 file that is a best effort to capture v3-related format updates
> >> only:
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauthors%2Frfc9481.form.xml__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdojGa6MLz%24&data=05%7C01%7Chendrik.b
> rockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38a
> e3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xx2vlxgxiWPykv2
> mQiOKjea%2FPQsM9uiEEmd4L6XeUsI%3D&reserved=0
> >>
> >>
> >> Tracking progress
> >> -----------------
> >>
> >> The details of the AUTH48 status of your document are here:
> >>
> https://urldefe/
> nse.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-
> editor.org%2Fauth48%2Frfc9481__%3B!!FJ-
> Y8qCqXTj2!ZhSv8tcSblpo6M2EqIK6gbXe2su73bypLc5SDx4gLBiKNLtlf5TuXn1nKl
> fqOjBydRJFeBLkuiqCoYsMmDMdonk6PyX3%24&data=05%7C01%7Chendrik.br
> ockhaus%40siemens.com%7C5cdd08f64c614039c01008dbc041248b%7C38ae
> 3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638315158766987529%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mh9CFdFo200WT
> oCbFsQAmje0m0%2FIJsb9Hcgw1vF1O%2FE%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
> >>
> >>
> >> Any email and files/attachments transmitted with it 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.
> >