RPC Wiki

Note: The terms “definitive format” and “publication version” are used as defined in Section 1.1 of RFC 9720.

As noted in Section 3 of RFC 9720:

The RPC is permitted but not required to reissue publication versions of an RFC, as described in Section 1.2. In deciding whether to update the publication versions of an RFC, the RPC will take into account both the risk of semantic changes and consistency of the Series.

Below are the criteria for reissuing a publication version, where one or more publication versions of an RFC is posted *without* replacing the XML file. A publication version (TXT, HTML, and/or PDF) for a particular RFC may be reissued if all of the following conditions are true:

• An error materially affects at least one of the rendered outputs (e.g., text is missing).
• The error is a result of the conversion tools and correction does not require changes to the definitive format.
• Had the issue been identified earlier, publication of the affected document would have been delayed until the issue was fixed.

The defective file will be moved to a separate, publicly available directory https://www.rfc-editor.org/in-notes/rerendered/, which contains a README explaining the purpose of the directory. The reissued file will replace the defective file, and the replacement will be announced on the ietf-announce and rfc-dist mailing lists, which are the standard communication channels for announcing the publication of RFCs. A note will be added to the RFC's datatracker History tab.