Carlos, Thank you for your reply. The revised files are here (please refresh): https://www.rfc-editor.org/authors/rfc9845.html https://www.rfc-editor.org/authors/rfc9845.txt https://www.rfc-editor.org/authors/rfc9845.pdf https://www.rfc-editor.org/authors/rfc9845.xml
This diff file shows all changes from the approved I-D: https://www.rfc-editor.org/authors/rfc9845-diff.html https://www.rfc-editor.org/authors/rfc9845-rfcdiff.html (side by side) This diff file shows the changes made during AUTH48 thus far: https://www.rfc-editor.org/authors/rfc9845-auth48diff.html https://www.rfc-editor.org/authors/rfc9845-auth48rfcdiff.html (side by side) This diff file shows only the changes since the last posted version: https://www.rfc-editor.org/authors/rfc9845-lastrfcdiff.html In addition to the changes you requested: - removed extraneous 'to'. - lowercased 'fluorinated'. - replaced angled quotes with straight quotes per RFC style. Re: > After fixing these three nits, please note and write down my Approval of the > document at https://www.rfc-editor.org/auth48/rfc9845 Your approval has been recorded. We await word from your coauthors and the Document Shepherd before continuing the publication process. Alice Russo RFC Production Center > On Sep 5, 2025, at 10:05 PM, Carlos Pignataro <[email protected]> wrote: > > Hi, Alice, > > I sincerely appreciate the outstanding quality of your work on this. > > Here’s my responses — taking the lead as Alex is on vacation. > > 1. Correct. > We want the Telefonica-2020 reference removed. > > 2. Let’s go with “A”. > It is closer to the original, and also it is more descriptive using > “effectiveness”. > > 3. Let’s leave it, please. > Thank you for asking and for your patience with this :-) > I prefer not to shorten affiliation names, and use "NC State University & > Blue Fern Consulting" > > I can see it is long, but a quick search shows similar examples: > https://www.rfc-editor.org/rfc/rfc8452.txt > https://www.rfc-editor.org/rfc/rfc9324.txt > > > And now, doing another final pass, I noticed a couple of typos/grammos: > > Section 1.2: > “…improving the efficiency with with networks utilize power…” > —> > “…improving the efficiency with which networks utilize power…” > > Section 6.1: > “…for exmaple, virtualized network functions…” > —> > “…for example, virtualized network functions…” > > Section 8: > “…the constallation and any networking within it are powered by solar energy…” > —> > “…the constellation and any networking within it are powered by solar energy…” > > > And with that, I believe we had responded to all the queries, and all the > issues raised had been addressed. > > After fixing these three nits, please note and write down my Approval of the > document at https://www.rfc-editor.org/auth48/rfc9845 > > Thanks! > > Carlos. > > >> On Sep 3, 2025, at 12:57 PM, Alice Russo <[email protected]> wrote: >> >> Carlos, Alex, >> >> Thank you for your replies; we have updated the document accordingly (URLs >> below). A few follow-ups: >> >> 1) Section 1.1: The new text provided does not cite [Telefonica2020], so >> this reference has been removed. Please let us know if you prefer otherwise. >> >> 2) Section 6.1 re: >>> [CMP] "there are opportunities to identify the most suitable location for >>> functionality in the network” is the best one yet. >>> [CMP] But we can discuss and re-confirm. >> >> >> Do you prefer A or B or otherwise? >> >> A) Current: >> Likewise, there are opportunities to correctly place functionality in >> the network for optimal effectiveness. >> >> B) Perhaps: >> Likewise, there are opportunities to identify the most suitable location >> for functionality in the network. >> >> >> 3) Header: re: >>> [CMP] Top-page: “NC State University & Blue Fern Consulting” or “NC State >>> University / Blue Fern Consulting" >>> [CMP] Authos’ Addresses: “North Carolina State University & Blue Fern >>> Consulting” >> >> The abbreviated organization appears long for the text file, i.e., it >> horizontally overlaps with the left side. Do you prefer to leave it or >> change to "NCSU & Blue Fern Consulting" or otherwise? >> >> [best viewed with fixed-width font] >> >> Internet Research Task Force (IRTF) A. Clemm, Ed. >> Request for Comments: 9845 Independent >> Category: Informational C. Pignataro, Ed. >> ISSN: 2070-1721 NC State University & Blue Fern Consulting >> C. Westphal >> [...] >> >> >> The revised files are here (please refresh): >> https://www.rfc-editor.org/authors/rfc9845.html >> https://www.rfc-editor.org/authors/rfc9845.txt >> https://www.rfc-editor.org/authors/rfc9845.pdf >> https://www.rfc-editor.org/authors/rfc9845.xml >> >> This diff file shows all changes from the approved I-D: >> https://www.rfc-editor.org/authors/rfc9845-diff.html >> https://www.rfc-editor.org/authors/rfc9845-rfcdiff.html (side by side) >> >> This diff file shows the changes made during AUTH48 thus far: >> https://www.rfc-editor.org/authors/rfc9845-auth48diff.html >> https://www.rfc-editor.org/authors/rfc9845-auth48rfcdiff.html (side by side) >> >> This diff file shows only the changes since the last posted version: >> https://www.rfc-editor.org/authors/rfc9845-lastrfcdiff.html >> >> We will wait to hear from you again and from your coauthors >> before continuing the publication process. This page shows >> the AUTH48 status of your document: >> https://www.rfc-editor.org/auth48/rfc9845 >> >> Thank you. >> RFC Editor/ar -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
