Hi Eliot, The files have been updated as described below. Please review the files below and let us know if any additional updates are needed or if you approve the RFC for publication. https://www.rfc-editor.org/authors/rfc9945.xml https://www.rfc-editor.org/authors/rfc9945.txt https://www.rfc-editor.org/authors/rfc9945.pdf https://www.rfc-editor.org/authors/rfc9945.html
Diffs highlighting recent updates: https://www.rfc-editor.org/authors/rfc9945-lastdiff.html https://www.rfc-editor.org/authors/rfc9945-lastrfcdiff.html (side by side) AUTH48 diffs: https://www.rfc-editor.org/authors/rfc9945-auth48diff.html https://www.rfc-editor.org/authors/rfc9945-auth48rfcdiff.html (side by side) Comprehensive diffs: https://www.rfc-editor.org/authors/rfc9945-diff.html https://www.rfc-editor.org/authors/rfc9945-rfcdiff.html (side by side) Thanks, Sandy Ginoza RFC Production Center > On Feb 27, 2026, at 7:59 AM, Eliot Lear <[email protected]> wrote: > > Sandy, > Thanks. I must apologize for not having used Github to communicate the > following. However... > I cauht two instances of inconsistency between "moderator team" and > "moderation team". I believe the correct term is "moderator team", and so I > propose the following changes: > Section 3, under "Administrators" (second bullet, last sentence): > OLD: > amend or rescind actions, including those taken by members of the moderation > team after they have > NEW: > amend or rescind actions, including those taken by members of the moderator > team after they have > Section 6, point 3: > OLD: > be immediately reported to the affected person and to the moderation team, > and periodically reported to > NEW: > be immediately reported to the affected person and to the moderator team, and > periodically reported to > Thanks, > Eliot > > On 27.02.2026 16:21, Sandy Ginoza wrote: >> Hi Lars and Eliot, >> >> We have updated the document and posted the files here: >> https://www.rfc-editor.org/authors/rfc9945.xml >> https://www.rfc-editor.org/authors/rfc9945.txt >> https://www.rfc-editor.org/authors/rfc9945.pdf >> https://www.rfc-editor.org/authors/rfc9945.html >> >> Diffs highlighting the most recent change only: >> https://www.rfc-editor.org/authors/rfc9945-lastdiff.html >> https://www.rfc-editor.org/authors/rfc9945-lastrfcdiff.html (side by side) >> >> AUTH48 diffs: >> https://www.rfc-editor.org/authors/rfc9945-auth48diff.html >> https://www.rfc-editor.org/authors/rfc9945-auth48rfcdiff.html (side by side) >> >> Comprehensive diffs: >> https://www.rfc-editor.org/authors/rfc9945-diff.html >> https://www.rfc-editor.org/authors/rfc9945-rfcdiff.html (side by side) >> >> Lars, we have noted your approval on the AUTH48 page >> <https://www.rfc-editor.org/auth48/rfc9945>. >> >> Eliot, please let us know if any further updates are needed or if you >> approve the RFC for publication. >> >> Thank you, >> Sandy Ginoza >> RFC Production Center >> >> >> >> >>> On Feb 26, 2026, at 11:06 PM, Lars Eggert <[email protected]> wrote: >>> >>> I'm fine with reverting to "replaces". All good otherwise! >>> >>> >>>> On Feb 27, 2026, at 08:08, Eliot Lear <[email protected]> wrote: >>>> >>>> I do not agree with Lars’ change. The term “replaces” is what was agreed, >>>> and the mechanisms are separate and distinct. >>>> >>>> Eliot >>>> >>>> >>>>> On 27 Feb 2026, at 01:10, Sandy Ginoza <[email protected]> >>>>> wrote: >>>>> >>>>> Hi Eliot and Lars, >>>>> >>>>> Please note that we merged the updates and converted the markdown to xml >>>>> and made additional formatting updates (i.e., moved the acknowledgements >>>>> section and capitalized BCP in the doc header). The files are available >>>>> for review here: >>>>> https://www.rfc-editor.org/authors/rfc9945.xml >>>>> https://www.rfc-editor.org/authors/rfc9945.txt >>>>> https://www.rfc-editor.org/authors/rfc9945.pdf >>>>> https://www.rfc-editor.org/authors/rfc9945.html >>>>> >>>>> These updates highlight all of the changes made during AUTH48: >>>>> https://www.rfc-editor.org/authors/rfc9945-auth48diff.html >>>>> https://www.rfc-editor.org/authors/rfc9945-auth48rfcdiff.html (side by >>>>> side) >>>>> Note: We moved the Acknowledgements in the file that initiated AUTH48 (as >>>>> well as the current file) so you can easily see the changes in that >>>>> section. >>>>> >>>>> Comprehensive diffs: >>>>> https://www.rfc-editor.org/authors/rfc9945-diff.html >>>>> https://www.rfc-editor.org/authors/rfc9945-rfcdiff.html (side by side) >>>>> >>>>> >>>>> Eliot, in particular, please be aware this change made based on a >>>>> suggestion from Lars: >>>>> https://github.com/rfc-editor/AUTH48-rfc9945/pull/1/changes/3732420830438154b02a78a9099c968d7f20107d >>>>> >>>>> >>>>> Please review and let us know if any further changes are needed or if you >>>>> approve the RFC for publication. >>>>> >>>>> Thank you, >>>>> Sandy Ginoza >>>>> RFC Production Center >>>>> >>>>> >>>>> >>>>> >>>>>> On Feb 25, 2026, at 4:37 PM, Sandy Ginoza <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Hi Eliot, >>>>>> >>>>>> Thanks for your quick replies! I have updated the RPC-edits branch to >>>>>> include all of the updates and closed out the issues that have been >>>>>> addressed. Please see the updates and replies to comments in the file >>>>>> here: >>>>>> https://github.com/rfc-editor/AUTH48-rfc9945/pull/1/changes >>>>>> >>>>>> Please let us know if any further updates are needed. If none, please >>>>>> indicate that the markdown is ready to be converted to XML on this issue: >>>>>> https://github.com/rfc-editor/AUTH48-rfc9945/issues/17 >>>>>> >>>>>> Thanks! >>>>>> Sandy Ginoza >>>>>> RFC Production Center >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>>> On Feb 25, 2026, at 11:32 AM, Eliot Lear <[email protected]> wrote: >>>>>>>> >>>>>>> Hi Sandy, >>>>>>> I've done so now. >>>>>>> Thanks, >>>>>>> Eliot >>>>>>> On 25.02.2026 20:19, Sandy Ginoza wrote: >>>>>>> >>>>>>>> Hi Eliot and Lars, >>>>>>>> >>>>>>>> Thanks for reviewing the diff! Please note that there are open issues >>>>>>>> as well - see https://github.com/rfc-editor/AUTH48-rfc9945/issues. To >>>>>>>> address the issues, please reply within the issue, use suggestions in >>>>>>>> the RPC-edits branch, or submit a new PR against the RPC-edits branch. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> Sandy Ginoza >>>>>>>> RFC Production Center >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Feb 25, 2026, at 2:58 AM, Eliot Lear <[email protected]> wrote: >>>>>>>>> >>>>>>>>> Both Lars and I have done our review on Github. There are three >>>>>>>>> proposed edits (one from Lars and two from me), but otherwise please >>>>>>>>> note my approval. >>>>>>>>> Eliot >>>>>>>>> On 25.02.2026 00:45, [email protected] wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>>> Please disregard the previous message; it contained incorrect links. >>>>>>>>>> This message contains the correct links to the repo and README for >>>>>>>>>> this document. See below. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *****IMPORTANT***** >>>>>>>>>> >>>>>>>>>> Updated 2025/12/23 >>>>>>>>>> >>>>>>>>>> RFC Author(s): >>>>>>>>>> -------------- >>>>>>>>>> >>>>>>>>>> Your document has now entered AUTH48. >>>>>>>>>> >>>>>>>>>> The document was edited in kramdown-rfc as part of the RPC pilot >>>>>>>>>> test (see >>>>>>>>>> https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc). >>>>>>>>>> >>>>>>>>>> AUTH48 is being handled in GitHub as part of the GitHub pilot test >>>>>>>>>> (see >>>>>>>>>> https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test). >>>>>>>>>> >>>>>>>>>> Your document is available for review at:\\ >>>>>>>>>> https://github.com/rfc-editor/AUTH48-rfc9945 >>>>>>>>>> >>>>>>>>>> Please see the README for details on the AUTH48 process:\\ >>>>>>>>>> https://github.com/rfc-editor/AUTH48-rfc9945/blob/Approved/README.md >>>>>>>>>> >>>>>>>>>> Once the content of the .md file is stable, we will convert it to >>>>>>>>>> .xml >>>>>>>>>> and provide the .html, .pdf, .txt, and .xml files for review. >>>>>>>>>> >>>>>>>>>> You and your coauthors are responsible for engaging other parties >>>>>>>>>> (e.g., Contributors or Working Group) as necessary before providing >>>>>>>>>> your approval. >>>>>>>>>> >>>>>>>>>> Once the document has been reviewed and approved by all of the >>>>>>>>>> authors, >>>>>>>>>> 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.rfc-editor.org/faq/). >>>>>>>>>> >>>>>>>>>> Please let us know if you have any questions. >>>>>>>>>> >>>>>>>>>> Thank you for your cooperation, >>>>>>>>>> >>>>>>>>>> RFC Editor >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> <OpenPGP_0x87B66B46D9D27A33.asc> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> <OpenPGP_0x87B66B46D9D27A33.asc> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> >> > <OpenPGP_0x87B66B46D9D27A33.asc> -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
