Alice; Looks good to me. Can we add <CODE BEGINS> and <CODE ENDS> markers in Section 6. Sorry that I did not norice they were missing earlier.
Russ > On Aug 10, 2026, at 11:43 AM, Alice Russo <[email protected]> wrote: > > Russ, > Good catch. The files have been corrected and posted here (please refresh): > > https://www.rfc-editor.org/authors/rfc10031.txt > https://www.rfc-editor.org/authors/rfc10031.html > https://www.rfc-editor.org/authors/rfc10031.pdf > https://www.rfc-editor.org/authors/rfc10031.xml (source) > > Comprehensive diff file of the text: > https://www.rfc-editor.org/authors/rfc10031-diff.html > https://www.rfc-editor.org/authors/rfc10031-rfcdiff.html (side by side) > > Only the most recent changes: > https://www.rfc-editor.org/authors/rfc10031-lastrfcdiff.html (side by side) > > FYI, line breaks were added in 3 lines (listed below) where the > line-length limit was exceeded. > > rfc10031.xml(166): Warning: Too long line found (L325), 8 characters > longer than 72 characters: > // e.g., we can add mask bits to the current set, we can not remove > them > rfc10031.xml(166): Warning: Too long line found (L329), 17 characters > longer than 72 characters: > // e.g., we can't change the values of the live bits from the > superior constraint > rfc10031.xml(201): Warning: Too long line found (L361), 6 characters > longer than 72 characters: > // This logic can be used for both MACAddress and iPAddress OtherName types > > Alice Russo > RFC Production Center > > On Sat, Aug 8, 2026 at 9:12 PM Russ Housley <[email protected]> wrote: >> >> In Section 5: s/RFC 100031/RFC 10031/ >> >>> On Aug 7, 2026, at 1:55 PM, [email protected] wrote: >>> >>> Authors, >>> >>> Summary: We've completed the GitHub portion; please review the files (links >>> below) and email your approval. >>> >>> Details: >>> We merged the updates, converted the kramdown-rfc file to RFCXML, and made >>> minor updates (removed "-latest" in the docName attribute; removed the >>> comment containing the markdown-source hash). >>> >>> 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. >>> >>> XML file: >>> https://www.rfc-editor.org/authors/rfc10031.xml >>> >>> Output files: >>> https://www.rfc-editor.org/authors/rfc10031.txt >>> https://www.rfc-editor.org/authors/rfc10031.html >>> https://www.rfc-editor.org/authors/rfc10031.pdf >>> >>> Comprehensive diff file of the text: >>> https://www.rfc-editor.org/authors/rfc10031-diff.html >>> https://www.rfc-editor.org/authors/rfc10031-rfcdiff.html (side by side) >>> >>> For the Final Review status of this document, please see: >>> https://queue.rfc-editor.org/final-review/rfc10031 >>> >>> Thank you. >>> >>> Alice Russo >>> RFC Production Center >> -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
