Hi David. Thank you for your reply. We have made additional updates per your response to our follow-up questions.
The files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9733.xml https://www.rfc-editor.org/authors/rfc9733.txt https://www.rfc-editor.org/authors/rfc9733.html https://www.rfc-editor.org/authors/rfc9733.pdf The relevant diff files have been posted here: https://www.rfc-editor.org/authors/rfc9733-diff.html (comprehensive diff) https://www.rfc-editor.org/authors/rfc9733-auth48diff.html (AUTH48 changes) https://www.rfc-editor.org/authors/rfc9733-xmldiff3.html (xml diff between last version and this) We will await any further changes you may have and approvals from each author prior to moving forward in the publication process. For the AUTH48 status of this document, please see: https://www.rfc-editor.org/auth48/rfc9733 Thank you, RFC Editor/ap > On Feb 21, 2025, at 4:23 AM, von Oheimb, David <david.von.ohe...@siemens.com> > wrote: > > Dear RFC Editor, > > thank you for your updates and related message. > > On Thu, 2025-02-20 at 11:15 -0800, Alanna Paloma wrote: >> >> Thank you for your replies. We have updated as requested. > > Looks very good. > > > >> Please note that we have some follow-up notes/questions. >> >> 1) To have a 1:1 matchup with the acronym and expansion of “BRSKI-AE” and to >> reflect how it is expanded elsewhere in the document we have further updated >> your suggested title. Please review. >> >>> Update: >>> NEW: >>> BRSKI with Alternative Enrollment Protocols (BRSKI-AE) >> >> Current: >> BRSKI with Alternative Enrollment (BRSKI-AE) Protocol > > We meanwile believe that is best to simplify this to: > > NEW: > > BRSKI with Alternative Enrollment (BRSKI-AE) > > >> >> 2) FYI - We have also added “CMS” to the list in Section 2 as it appears in >> the expansion of “CMC”. Please let us know of any objections. >> >> Current: >> CMS: Cryptographic Message Syntax > > Good. > > >> 3) For consistency, should field names appear within <tt> or without <tt>? >> >>> OLD: >>> the <tt>caPubs</tt> field >>> NEW: >>> the '<tt>caPubs</tt>' field >>> >>> OLD: >>> the acp-node-name field >>> NEW: >>> the 'acp-node-name' field > > Yes, please use <tt> for all field names. > > >> 4) To make the following update in Figure 1, please provide us with updated >> SVG that includes this change. (We have made this update in the ascii-art, >> which appears in the txt file). >> >>>> b.) We note the following expanded forms of "PKI" are used after the >>>> abbreviation is introduced. May we update these instances below to the >>>> abbreviation? >>>> >>>> Public-Key Infrastructure >>>> public-key infrastructure >>> Figure 1: >>> OLD: >>> Public-Key Infrastructure >>> >>> NEW: >>> >>> Public-Key Infrastructure (PKI) > > Please find the new Figure 1 in SVG format attached. > > >> >> 5) After we have received the final approvals from each author, we will ask >> IANA to update their registry accordingly. > > Thank you. > > Best regards, > David von Oheimb and co-authors > > > >> >>> 6. >>> >>> We are ok with your change >>> from "Lightweight CMP Profile (LCMPP, [RFC9483])" >>> to "Lightweight CMP Profile (LCMPP) [RFC9483]" >>> because it improves consistency with the style used in sections 1 and 5.1. >>> Yet please just note that this change incurs a minor textual discrepancy >>> with the Description entry at >>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fservice-names-port-numbers%2Fservice-names-port-numbers.xhtml%3Fsearch%3Dbrski-reg-cmp&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403057881%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=soKXFGggGb71zrUvNIPKbL%2FyP2d3T2RCBpnCHB9MNhk%3D&reserved=0 >>> which uses "Lightweight CMP Profile (LCMPP, [RFC9483])". >> >> >> ... >> The files have been posted here (please refresh): >> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9733.xml&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403075334%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PU8Rm%2Fau4oXvg3jAdNaO0pJombEP8R2QJmUJ5RobP6w%3D&reserved=0 >> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9733.txt&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403086748%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=imL11i%2Bh942SpIH6uclDnca%2FHNq16W1RKo3UPaN3xRI%3D&reserved=0 >> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9733.html&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403097875%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=OMy%2B56LSN92Am8VZ%2BdoDHuqD2nRFK3l2hQs2BWM9Gbk%3D&reserved=0 >> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9733.pdf&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403109036%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=hnJZHYs%2BeAvmkZXCZceRDPVCmCvUwUsyx01WfqeUx7Q%3D&reserved=0 >> >> The relevant diff files have been posted here: >> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9733-diff.html&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403119981%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Kc%2BwQc0a%2BfF706Xf60SNkU3KN0iI%2B9DmnRHa6oixtGw%3D&reserved=0 >> (comprehensive diff) >> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9733-auth48diff.html&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403130870%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=sJ85a015Les7%2FMvIqcDyeAaZ%2Ft%2FHzC84b3It01WEOro%3D&reserved=0 >> (AUTH48 changes) >> >> Please review the document carefully and contact us with any further updates >> you may have. Note that we do not make changes once a document is published >> as an RFC. >> >> We will await approvals from each party listed on the AUTH48 status page >> below prior to moving this document forward in the publication process. >> >> For the AUTH48 status of this document, please see: >> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9733&data=05%7C02%7CDavid.von.Oheimb%40siemens.com%7Cc6fd975570094fd9212b08dd51e30a8e%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638756758403141806%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2VHLD4UgpBlKPsCQHrZoMUvYugCc1ciOS9CTfXdPklA%3D&reserved=0 >> >> Thank you, >> RFC Editor/ap >> >> > <Figure1.svg> -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
