As noted in Section 10.2 of RFC 7990, “The actual rendering engine can go through further review and iteration, as the publication formats may be republished as needed.” Below are the criteria for republishing a publication format. To summarize, this is the case where one or more publication formats of an RFC is posted *without* replacing the XML file.
Below, the terms “canonical format” and “publication format” are used as defined in Section 3 of RFC 7990 and per Section 5 “The final XML file produced by the RFC Editor will be considered the canonical format for RFCs”.
Specifically, a publication format (TXT, HTML, and/or PDF) for a particular RFC may be rerendered if all of the following conditions are true:
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 rerendered 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.
RFC number | File(s) rerendered | Date | Reason |
---|---|---|---|
RFC 8677 | 2024-12-19, announcement | PDF rerendered so that list numbering is corrected in Section 6.2.2. (See https://github.com/ietf-tools/xml2rfc/pull/1055) | |
RFC 8680 | 2024-12-19, announcement | PDF rerendered so that list numbering is corrected in Section 4.3. (See https://github.com/ietf-tools/xml2rfc/pull/1055) | |
RFC 8681 | 2024-12-19, announcement | PDF rerendered so that list numbering is corrected in Section 1.4. (See https://github.com/ietf-tools/xml2rfc/pull/1055) | |
RFC 8994 | 2024-12-19, announcement | PDF rerendered so that list numbering is corrected in Section 6.2.3. (See https://github.com/ietf-tools/xml2rfc/pull/1055) | |
RFC 9019 | 2022-12-19, announcement | PDF rerendered so that Figures 2 and 3 are not cut off. (See https://github.com/ietf-tools/xml2rfc/pull/788) |