Hi all, My feedback has now been addressed via issues/PRs in rfc-editor-drafts/FinalReview-rfc10032. I've reviewed the PRs and believe they address everything important without introducing new mistakes.
Once those changes have been merged, I give my final approval for publishing. Many thanks, Samuel On Thursday, 27 August 2026 at 23:16, Samuel Lucas <[email protected]> wrote: > Hi all, > > I've attached my notes. Appreciate your flexibility Madison. It's my bad for > not doing this last time. > > Please could you review this Frank, and we can do any edits on GitHub so it's > easier to check. I'm happy to do the PRs if you want to wait until the > weekend, or I can just double check your changes if you'd prefer. > > Many thanks, > Samuel > > On Thursday, 27 August 2026 at 14:20, Madison Church > <[email protected]> wrote: > > > Hi Samuel, > > > > No worries at all! Please feel free to send along an updated markdown file > > once you’ve made those updates. > > > > Thank you, > > Madison Church > > RFC Production Center > > > > > On Aug 27, 2026, at 2:00 AM, Samuel Lucas <[email protected]> > > > wrote: > > > > > > Hi Madison, > > > > > > I'm about halfway through my rereview of the document and have found > > > several errors/clarity/undefined issues so far. > > > > > > Please could I check what can be changed at this stage so I can format my > > > feedback accordingly. Errors obviously need to be fixed, so it's more > > > whether things can be made clearer/more consistent. Can I send you a > > > Markdown file when I'm done? > > > > > > Sorry for not doing a full reread as part of the GitHub work. I can > > > assure you that we have both fully reviewed this document multiple times > > > before, so I think this is just what happens after a long break. > > > > > > Many thanks, > > > Samuel > > > > > > On Tuesday, 25 August 2026 at 15:51, Madison Church > > > <[email protected]> wrote: > > > > > >> Hi Frank, Samuel, > > >> > > >> Frank - Thank you for your approval! We have noted it here: > > >> https://queue.rfc-editor.org/final-review/rfc10032/. > > >> > > >> Samuel - No worries! We will wait to hear from you later this week. > > >> > > >> Thank you, > > >> Madison Church > > >> RFC Production Center > > >> > > >>> On Aug 25, 2026, at 7:01 AM, Samuel Lucas > > >>> <[email protected]> wrote: > > >>> > > >>> Hello RFC Editors, > > >>> > > >>> I trust Frank's judgement. However, if there's no rush, please could > > >>> you give me Wednesday/Thursday evening to review this. > > >>> > > >>> Sorry for the delay; I don't get notifications for this email account > > >>> and assumed this email might come after the weekend. > > >>> > > >>> Many thanks, > > >>> Samuel > > >>> > > >>> On Saturday, 22 August 2026 at 11:46, Frank Denis <[email protected]> wrote: > > >>> > > >>>> Hello RFC Editors, > > >>>> > > >>> > > >>>> I've reviewed the final version of the document, and I think it's > > >>>> ready for publication. > > >>>> > > >>> > > >>>> Thanks again for all your help! > > >>>> > > >>> > > >>>> -Frank. > > >>>> > > >>> > > >>>> On Fri, Aug 21, 2026 at 01:20:18PM -0500, Madison Church wrote: > > >>>>> Hello Authors, > > >>>>> > > >>>>> We have merged the updates and converted the kramdown-rfc file to > > >>>>> RFCXML. Thank you both for submitting PRs and comments throughout the > > >>>>> process, it was super helpful on our end! > > >>>>> > > >>>>> Please review the XML file and its TXT, HTML, and PDF outputs, and > > >>>>> let us know if any changes are required or if you approve the RFC for > > >>>>> publication. We consider this your final assent that the document is > > >>>>> ready for publication. To request changes or approve your RFC for > > >>>>> publication, please reply to this email. Please use ???REPLY ALL???, > > >>>>> as all the parties CCed on this message need to see your approval. > > >>>>> > > >>>>> Note that we will only make changes in the XML file from this point > > >>>>> on. > > >>>> > > >>> <publickey - [email protected] - 0xB416EEAC.asc> > > >> > > > <publickey - [email protected] - 0xB416EEAC.asc> > > > >
publickey - [email protected] - 0xB416EEAC.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
