On Mon, Jun 2, 2025 at 3:43 PM Megan Ferguson < mfergu...@staff.rfc-editor.org> wrote:
> Hi Marco and *Paul, > > [*Paul, we ask that you confirm the following updates, especially the > changes to Figure 4 (see Marco’s mail below or the diff between the last > version and this).] > Confirmed and approved. The values were translated properly. Paul > > Thank you for sending along these updates. We have incorporated these > changes and reposted the files. Please review carefully as we do not make > changes once the document is published as an RFC. > > The files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9770.txt > https://www.rfc-editor.org/authors/rfc9770.pdf > https://www.rfc-editor.org/authors/rfc9770.html > https://www.rfc-editor.org/authors/rfc9770.xml > > The relevant diff files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9770-diff.html (comprehensive diff) > https://www.rfc-editor.org/authors/rfc9770-auth48diff.html (AUTH48 > changes only) > https://www.rfc-editor.org/authors/rfc9770-lastdiff.html (last to > current version only) > https://www.rfc-editor.org/authors/rfc9770-lastrfcdiff.html (last to > current side by side) > > Please contact us with any further updates/questions/comments you may > have. > > We will await approvals from each of the parties listed on the AUTH48 > status page prior to moving forward to publication. > > The AUTH48 status page for this document is available here: > > https://www.rfc-editor.org/auth48/rfc9770 > > Thank you. > > RFC Editor/mf > > > On May 30, 2025, at 10:22 AM, Marco Tiloca <marco.til...@ri.se> wrote: > > > > Hello Megan, > > > > Thank you, the figures look good to me in all the document formats. > > > > I have now proofread the whole document and have a final set of > comments, please see below. They finish with the mark "=== END OF COMMENTS > ===". > > > > Best, > > /Marco > > > > > > ### Section 4.1.2 > > > > OLD: > > like it is defined in Section 3.2.2 of [RFC9202]. > > > > NEW: > > like it is defined in Section 3.3.2 of [RFC9202]. > > > > Rationale: It is actually in Section 3.3.2 of RFC 9202 that the use of > the mentioned fields is defined. > > > > > > ### Section 4.2.2 > > > > In the example in Figure 4, the following change is needed in the entry > of the third from last parameter. > > > > OLD: > > "pop", > > > > NEW: > > "PoP", > > > > Rationale: "PoP" is consistent with the capitalization used for the > registry entry at > https://www.iana.org/assignments/ace/ace.xhtml#oauth-access-token-type-cbor-mappings > > > > > > ### Section 4.2.2 > > > > In the example in Figure 4, the following change is needed in the entry > of the last parameter. > > > > OLD: > > "1" > > > > NEW: > > "coap_dtls" > > > > Rationale: Per the second paragraph of Section 5.8.4.3 of RFC 9200, > JSON-based interactions are supposed to use the textual representation of > the profile identifier, i.e., here "coap_dtls", see > https://www.iana.org/assignments/ace/ace.xhtml#ace-profiles > > > > > > ### Section 6 > > > > OLD: > > support its "Cursor" extension > > > > NEW: > > support the related "Cursor" extension > > > > > > ### Section 9.2.1 > > > > In the section title > > > > OLD: > > Empty Collection > > > > NEW: > > Empty Update Collection > > > > > > ### Section 11 > > > > OLD: > > Once registered at the AS, the administrator or registered device > > > > NEW: > > Once registered at the AS, an administrator or a registered device > > > > > > ### Section 14.7 > > > > OLD: > > Section 4.3.2 states that > > > > NEW: > > Section 4.3.2 specifies that > > > > > > ### Section 14.7 > > > > OLD: > > is a CWT since > > > > NEW: > > is a CWT, since > > > > > > ### Appendix C > > > > OLD: > > Registration is assumed > > > > NEW: > > The RS registration is assumed > > > > > > ### Appendix C > > > > OLD: > > with a registered device (see Section 8); > > > > NEW: > > with a registered device (see Section 6.2); > > > > Rationale: the bullet point is about the MAX_N parameter, which is first > introduced in Section 6.2. > > > > > > "=== END OF COMMENTS ===" > > > > > > On 2025-05-29 18:39, Megan Ferguson wrote: > >> Hi Marco, > >> > >> Thanks for sending these along. We have updated Figures 10-14 with the > ascii-art you provided. Please review all figures to ensure they appear as > you prefer. > >> > >> The files have been posted here (please refresh): > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.txt&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776466008%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=x6%2F3PDvm%2FxuiRZ5NyMBxm8NS2WYvtXfAvreUIPcZVbE%3D&reserved=0 > >> > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.pdf&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776485171%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=tSrIrAnH4dLlgQNlVSsmQS61k85UlsMBmqrQXusXYzs%3D&reserved=0 > >> > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776497438%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=SWMU53i8NSzxu3431irFYXrCQhD5PHnufqv%2BH7V3bbg%3D&reserved=0 > >> > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.xml&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776509648%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=0ngLzScHMmIsrrEYCc1QxWd2Rjr5ffPxXWHKH4TCu%2Fc%3D&reserved=0 > >> > >> > >> The relevant diff files have been posted here (please refresh): > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-diff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776522625%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=IfDvqMi3qaVzBuBT8RYKxu9kgUEkpgtXnn6UwDXI3fU%3D&reserved=0 > >> (comprehensive diff) > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-auth48diff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776534427%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=0ENJFmZivAeIXEqqSAfsoJzVsrPZBZBURnVE9cdMEVA%3D&reserved=0 > >> (AUTH48 changes only) > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-lastdiff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776546505%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=zGQj0NilUQp2toY%2FI%2FKMs5xVkJMajx8Wz8Tu%2FWOvEHs%3D&reserved=0 > >> (last to current version only) > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-lastrfcdiff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776557820%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=UmWiHR41M6rIHbZStK2GUivMSNwxE9M4G%2Bxhwu0W6yE%3D&reserved=0 > >> (last to current side by side) > >> > >> Please contact us with any further updates/questions/comments you may > have. > >> > >> We will await approvals from each of the parties listed on the AUTH48 > status page prior to moving forward to publication. > >> > >> The AUTH48 status page for this document is available here: > >> > >> > >> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9770&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776569080%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=SN1moiPXqZaJvR7ktjb6HIxSZ473D1iqKb8bAsOv%2FpQ%3D&reserved=0 > >> > >> > >> Thank you. > >> > >> RFC Editor/mf > >> > >> > >>> On May 29, 2025, at 2:20 AM, Marco Tiloca <marco.til...@ri.se> > >>> wrote: > >>> > >>> Hi Megan, > >>> > >>> Thank you; I understand the constraints, then let's have ascii-art for > Figures 10-14 also in the HTML. > >>> > >>> When checking rfc9770_test.html, I can see that those figures have > some differences in spacing and indentation if compared to what the result > was in SVG. > >>> > >>> Please see attached a ZIP archive with 5 TXT files, each with the > ascii-art of one of the Figures 10-14. Although I was using those files to > generate the SVG images, their content is exactly what is intended to be > shown in ascii-art. > >>> > >>> Would it be possible to use the content of those files to draw Figures > 10-14 in ascii-art? > >>> > >>> Best, > >>> /Marco > >>> > >>> On 2025-05-28 18:47, Megan Ferguson wrote: > >>> > >>>> Hi Marco, > >>>> > >>>> Thank you for your reply. We have updated accordingly. > >>>> > >>>> Please see below for further comment on the SVG issue (marked with > [rfced]): > >>>> > >>>> On May 24, 2025, at 9:39 AM, Marco Tiloca > >>>> > >>>> <marco.til...@ri.se> > >>>> > >>>> wrote: > >>>> > >>>> > >>>> > >>>>> 3) Regarding the SVG figures being cut off at the end of the pages > in the PDF output, this is a known issue with xml2rfc (see > >>>>> > >>>>> > >>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fietf-tools%2Fxml2rfc%2Fissues%2F860&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776580791%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=CvidDED0OaThaw4jPn2FSfKsXSr3Nti7l%2BH%2BRj4kqlU%3D&reserved=0 > >>>>> > >>>>> > >>>>> ). As the proposed workaround (to shrink the size of the SVG down so > that it fits on one page) is not a good solution for Figures 10-14, esp. > Fig 14 because it gets too small to be readable, we propose three possible > options to address this issue: > >>>>> > >>>>> a. Split one SVG element into two (or more) SVG elements so that a > page break appears in the PDF between the parts. (This would look odd in > the TXT and HTML.) > >>>>> b. Change the content of the SVG (and the equivalent ascii-art) to > be at high level with step numbers (move details of steps out of each > figure). > >>>>> c. Remove SVG, i.e., have ascii-art only for those 5 diagrams (SVG > would remain for fig 1 which is a different kind of figure). See here for > what this option would look like in the PDF output: > >>>>> > >>>>> > >>>>> > >>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770_test.pdf&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776592974%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=Pvyep8mrYXHop7w8fo0VvLlJ%2B6G0LhaWneJwfW8mkuQ%3D&reserved=0 > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> Which of the three actions would you prefer to take? Or is there > another way you would like to address this? > >>>>> > >>>>> > >>>>> > >>>> ==>MT > >>>> > >>>> Thanks for the clarifications and the good proposals. > >>>> > >>>> I certainly prefer to take option (c), consistent with what is shown > in the preview file rfc9770_test.pdf > >>>> > >>>> I suppose and hope that this solution would be applied only to the > PDF, i.e., SVG will remain in the HTML version :-) > >>>> > >>>> <== > >>>> > >>>> [rfced] Unfortunately, it is not currently possible for SVG to appear > in the HTML but not in the PDF. The same ascii-art will be applied to the > the HTML. > >>>> > >>>> See here: > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770_test.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776604297%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=MQiF82OfWKrRhn2Rvtk3PljrTwSnkFThv1TASxN%2FjzU%3D&reserved=0 > >>>> > >>>> > >>>> > >>>> Please let us know if this output is still agreeable or if you would > like to take a different course of action. > >>>> > >>>> The other updates are viewable in the files below. Please review the > files carefully as we do not make changes after publication. > >>>> > >>>> The files have been posted here (please refresh): > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.txt&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776615487%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=pYhSly0hkGzkUPj7nUjCVMljS61f60B%2FXQ6Jy418ldM%3D&reserved=0 > >>>> > >>>> > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.pdf&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776627385%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=hpRnQQm46bnP8ter4%2F73T5EUdZqua%2FqHS35u86ebzRs%3D&reserved=0 > >>>> > >>>> > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776638925%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=WNrNRyjguXMjlmmQGlYm%2BoGX2prD7lATAe3icJS7FMo%3D&reserved=0 > >>>> > >>>> > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.xml&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776650361%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=59r8%2FYYhSDI%2F4FLuM%2BBhyljwd3S5qhS4RMiyb%2FH2xkk%3D&reserved=0 > >>>> > >>>> > >>>> > >>>> The relevant diff files have been posted here (please refresh): > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-diff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776661885%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=i1aC1fTBlamXhRAD0Bmu6%2BezgleSHLjuQycg18ykkMc%3D&reserved=0 > >>>> > >>>> (comprehensive diff) > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-auth48diff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776675432%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=GsX7HH1NpPPFy5IU80J3ItVKviYNo3p%2FhBU6PwsQqUU%3D&reserved=0 > >>>> > >>>> (AUTH48 changes only) > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-lastdiff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776687769%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=lkEoBL8%2BNrKcRA3oKb2RU6PfCFOj0hUzpkIYTvOYNxE%3D&reserved=0 > >>>> > >>>> (last to current version only) > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-lastrfcdiff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776699280%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=QI5m7ijI0WbTqGazzfWMMiczzU3Wdi6okPAXgAurU7M%3D&reserved=0 > >>>> > >>>> (last to current side by side) > >>>> > >>>> Please contact us with any further updates/questions/comments you may > have. > >>>> > >>>> We will await approvals from each of the parties listed on the AUTH48 > status page prior to moving forward to publication. > >>>> > >>>> The AUTH48 status page for this document is available here: > >>>> > >>>> > >>>> > >>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9770&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776710754%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=2uJbVonS8uXBw0O4S8LGx5GKAEzysLppwuQytTckdbY%3D&reserved=0 > >>>> > >>>> > >>>> > >>>> Thank you. > >>>> > >>>> RFC Editor/mf > >>>> > >>>> > >>>> > >>>>> On May 24, 2025, at 9:39 AM, Marco Tiloca <marco.til...@ri.se> > >>>>> > >>>>> wrote: > >>>>> > >>>>> Hello Alanna, > >>>>> > >>>>> Thank you, please see my answers in line below. > >>>>> > >>>>> After those, I also suggest one more fix in Sections 15.4, 15.5, and > 15.6, for consistency of capitalization within this document and with the > IANA registries. > >>>>> > >>>>> Best, > >>>>> /Marco > >>>>> > >>>>> On 2025-05-23 18:25, Alanna Paloma wrote: > >>>>> > >>>>> > >>>>>> [You don't often get email from apal...@staff.rfc-editor.org. > Learn why this is important at > https://aka.ms/LearnAboutSenderIdentification > >>>>>> > >>>>>> > >>>>>> ] > >>>>>> > >>>>>> Hi Marco, > >>>>>> > >>>>>> Thank you for your reply. We have updated the files below with your > follow-up comments. > >>>>>> > >>>>>> We have additional comments/questions regarding the SVG figures. > >>>>>> > >>>>>> 1) We have made some adjustments to the SVG in Figure 14 so that > the “:” in Observe: 64, Observe: 89, and Observe: 92 are now aligned. > Please review all the instances of “:” within “Payload: {…}” to ensure that > are now all aligned as you prefer. > >>>>>> > >>>>>> > >>>>>> > >>>>> ==>MT > >>>>> > >>>>> Thanks a lot! I have checked again Figures 10-14 and the alignment > of ":" looks good to me. > >>>>> > >>>>> <== > >>>>> > >>>>> > >>>>> > >>>>>> 2) We are unable to see this overlap issue in the PDF that you > mentioned: > >>>>>> > >>>>>> > >>>>>> > >>>>>>> - In the occurrences of "Content-Format: 262", "262" overlaps > with "Content-Format”. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> Please provide us a screenshot of the overlap so that we may be > better able to understand the issue. > >>>>>> > >>>>>> > >>>>> ==>MT > >>>>> > >>>>> It actually looks fine now; I can't see that overlapping anymore. > >>>>> > >>>>> <== > >>>>> > >>>>> > >>>>> > >>>>>> 3) Regarding the SVG figures being cut off at the end of the pages > in the PDF output, this is a known issue with xml2rfc (see > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fietf-tools%2Fxml2rfc%2Fissues%2F860&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776722450%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=Ut9dLOeJ%2BjocMWReTPvRsNlzi%2Fkt2v8NbcL2OXfnXqA%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> ). As the proposed workaround (to shrink the size of the SVG down > so that it fits on one page) is not a good solution for Figures 10-14, esp. > Fig 14 because it gets too small to be readable, we propose three possible > options to address this issue: > >>>>>> > >>>>>> a. Split one SVG element into two (or more) SVG elements so that a > page break appears in the PDF between the parts. (This would look odd in > the TXT and HTML.) > >>>>>> b. Change the content of the SVG (and the equivalent ascii-art) to > be at high level with step numbers (move details of steps out of each > figure). > >>>>>> c. Remove SVG, i.e., have ascii-art only for those 5 diagrams (SVG > would remain for fig 1 which is a different kind of figure). See here for > what this option would look like in the PDF output: > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770_test.pdf&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776733922%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=MRd%2Fkjygc4hU%2Froc%2F%2FWZSszlKvVfN6Atz%2FE%2Fb%2BlrGi4%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> Which of the three actions would you prefer to take? Or is there > another way you would like to address this? > >>>>>> > >>>>>> > >>>>>> > >>>>> ==>MT > >>>>> > >>>>> Thanks for the clarifications and the good proposals. > >>>>> > >>>>> I certainly prefer to take option (c), consistent with what is shown > in the preview file rfc9770_test.pdf > >>>>> > >>>>> I suppose and hope that this solution would be applied only to the > PDF, i.e., SVG will remain in the HTML version :-) > >>>>> > >>>>> <== > >>>>> > >>>>> > >>>>> ==>MT > >>>>> > >>>>> ### Section 15.4 > >>>>> > >>>>> OLD: > >>>>> "Standards Action with Expert Review > >>>>> > >>>>> " > >>>>> > >>>>> NEW: > >>>>> " > >>>>> > >>>>> Standards Action With Expert Review" > >>>>> > >>>>> (2 instances) > >>>>> > >>>>> > >>>>> ### Section 15.5 > >>>>> > >>>>> OLD: > >>>>> "Standards Action with Expert Review > >>>>> > >>>>> " > >>>>> > >>>>> NEW: > >>>>> " > >>>>> > >>>>> Standards Action With Expert Review" > >>>>> > >>>>> (2 instances) > >>>>> > >>>>> > >>>>> ### Section 15.6 > >>>>> > >>>>> OLD: > >>>>> "Standards Action with Expert Review > >>>>> > >>>>> " > >>>>> > >>>>> NEW: > >>>>> " > >>>>> > >>>>> Standards Action With Expert Review" > >>>>> > >>>>> <== > >>>>> > >>>>> > >>>>> > >>>>>> The files have been posted here (please refresh): > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.txt&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776745474%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=TCoM5HWoG6gJFJh%2B7spFF3IR5hQtbeyOvL5fijpiSqc%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.pdf&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776756941%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=jvVPcaBRbTi9GM%2B7yodyosh%2F6VSdZGJHCltsJ4Fu4MY%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776768469%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=q9GYKPxMAgVDSXIIs%2FNa3ZZ1YEp7rpUUQ%2BNZUIP5q%2F0%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770.xml&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776780811%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=CIqY1W2c6VLSN4sbyrTbhNpAE4YUI4xQgaYNN09YhRc%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> The relevant diff files have been posted here (please refresh): > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-diff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776792438%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=mgLQfMfr483yW9VMDvX4gIG7xQXGnydUAMq384WEEX4%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> (comprehensive diff) > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-auth48diff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776803977%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=iY%2BaQFV9tChF%2BxTe449zKbwWExUwFG7XCxZqsZ3xh1Y%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> (AUTH48 changes only) > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-lastdiff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776815480%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=SOo26X8K5M5TU6EmMMbzaJi%2BuD%2BUgCSKLKyO1fMCJYQ%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> (last to current version only) > >>>>>> > >>>>>> > >>>>>> > >>>>>> > https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9770-lastrfcdiff.html&data=05%7C02%7Cmarco.tiloca%40ri.se%7C13e1042a972540f6394d08dd9ecf5985%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638841336776827660%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=%2BZkJ2ov2tLYNS%2FqGR2c7iQ1GZThfeJsUIl%2Bx9W0ovQQ%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> (last to current side by side) > >>>>>> > >>>>>> Thank you, > >>>>>> RFC Editor/ap > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>> On May 18, 2025, at 2:31 AM, Marco Tiloca <marco.tiloca= > 40ri...@dmarc.ietf.org> > >>>>>>> > >>>>>>> > >>>>>>> wrote: > >>>>>>> > >>>>>>> Hello Megan, > >>>>>>> > >>>>>>> Thank you; I have checked the latest edited version. Please see > follow-up comments below. The last one is about the figures. > >>>>>>> > >>>>>>> My comments finish with the mark "=== END OF COMMENTS ===". > >>>>>>> > >>>>>>> Best, > >>>>>>> /Marco > >>>>>>> > >>>>>>> > >>>>>>> ### Section 6.3 > >>>>>>> > >>>>>>> OLD: > >>>>>>> 'diff': if included, it indicates that the AS should perform a > diff query ... > >>>>>>> > >>>>>>> NEW: > >>>>>>> 'diff': if included, it asks the AS to perform a diff query ... > >>>>>>> > >>>>>>> Rationale: "should" can be misleading; performing a diff query is > really what the AS is supposed to do if supporting diff queries. The > formulation "asks the AS to ..." is consistent with what is used in other > sections of the document. > >>>>>>> > >>>>>>> > >>>>>>> ### Section 6.3 > >>>>>>> > >>>>>>> OLD: > >>>>>>> 'cursor': if included, it indicates the should perform a diff > query ... > >>>>>>> > >>>>>>> NEW: > >>>>>>> 'cursor': if included, it asks the AS to perform a diff query ... > >>>>>>> > >>>>>>> Rationale: "AS" is missing in the old text. "should" can be > misleading; performing a diff query is really what the AS is supposed to do > if supporting diff queries. The formulation "asks the AS to ..." is > consistent with what is used in other sections of the document. > >>>>>>> > >>>>>>> > >>>>>>> ### Section 8 > >>>>>>> > >>>>>>> OLD > >>>>>>> to perfrom > >>>>>>> > >>>>>>> NEW > >>>>>>> to perform > >>>>>>> > >>>>>>> > >>>>>>> ### Appendix C.5 > >>>>>>> > >>>>>>> OLD: > >>>>>>> to the AS, to perform a diff query of the TRL. > >>>>>>> > >>>>>>> NEW: > >>>>>>> to the AS, asking the AS to perform a diff query of the TRL. > >>>>>>> > >>>>>>> > >>>>>>> ### Authors' Addresses > >>>>>>> > >>>>>>> OLD: > >>>>>>> SE-SE-164 40 Kista > >>>>>>> > >>>>>>> NEW: > >>>>>>> SE-164 40 Kista > >>>>>>> > >>>>>>> > >>>>>>> ### Authors' Addresses > >>>>>>> > >>>>>>> OLD: > >>>>>>> SE-16440 Kista > >>>>>>> > >>>>>>> NEW: > >>>>>>> SE-164 40 Kista > >>>>>>> > >>>>>>> > >>>>>>> ### Figures > >>>>>>> > >>>>>>> * In Figure 14, there is indeed a misalignment for the ":" > characters under the payloads for Observe: 64, Observe: 89, and Observe: > 92. As you correctly imagined, the intention is to have the ":" characters > aligned there too, and they are aligned in the sources that I used (more on > that further below). > >>>>>>> > >>>>>>> I am not sure how that plays a role, but the misalignment seems > due to the fact that those entries are the only ones where the array used > as value of the parameter full_set includes two elements, both in the same > line. I am not sure how to fix this. > >>>>>>> > >>>>>>> In addition to that, Figure 14 had a display error to fix > anyway, see the right side of the right-to-left arrow for the message with > Observe: 64. I have now produced an updated SVG for Figure 14 where that is > fixed, together with a more consistent indentation of the lines for the > final message. > >>>>>>> > >>>>>>> Please find attached a ZIP archive including Figures 10-14, with > only Figure 14 updated with the fixes mentioned above. Together with the > SVG files, the archive includes also the TXT files that I used as sources
