The RFC Editor has completed their editing pass on ACME and assigned us RFC number -- ACME will be RFC 8555 🎉🎊
In order to finalize the RFC, we now need to reconcile that with the edits that have come in while they were working, and return to them an updated XML document.
This PR takes the first few steps in that process:
Most of the RFC Editor's content changes have been reflected in the Markdown. The ones that are not reflected are ones that I rejected after reviewing them.
Adds an rfced directory with:
A script clean-xml.py that removes some artifacts that kramdown-rfc2629 introduces
The RFC editor's proposed file, rfc8555.xml
Some intermediate XML files to help understand the differences between the updated source and what the RFC editor provided:
draft-ietf-acme-acme.xml - Raw output from kramdown-xml2rfc
draft-ietf-acme-acme.clean.xml - Output from clean-xml.py
rfc8555.src-clean.xml - Same content as draft.clean.xml, but has RFC editor's technical XML changes
rfc8555.edited.xml - Content is the same as rfc.xml, but has:
Whitespace adjustments to facilitate diffs with the above
My comments in response to the RFC editor
The authors, chairs, and ADs are currently working on a plan to work this through to completion.
The RFC Editor has completed their editing pass on ACME and assigned us RFC number -- ACME will be RFC 8555 🎉🎊
In order to finalize the RFC, we now need to reconcile that with the edits that have come in while they were working, and return to them an updated XML document.
This PR takes the first few steps in that process:
rfceddirectory with:clean-xml.pythat removes some artifacts that kramdown-rfc2629 introducesrfc8555.xmldraft-ietf-acme-acme.xml- Raw output from kramdown-xml2rfcdraft-ietf-acme-acme.clean.xml- Output from clean-xml.pyrfc8555.src-clean.xml- Same content as draft.clean.xml, but has RFC editor's technical XML changesrfc8555.edited.xml- Content is the same as rfc.xml, but has:The authors, chairs, and ADs are currently working on a plan to work this through to completion.