There are some minor issues with the IETF XML format:
-
No explicit versioning. RFCs are in general not versioned and the format does not allow a version field. There has been a suggestion to add this (draft-claise-semver-02). Some recent RFCs just have the version in the title (e.g. RFC 7950 - The YANG 1.1 Data Modeling Language). This is what I've done for now.
-
Expiration date. The rendering tool xml2rfc treats the specification as an Internet-Draft that has an expiration date. We don't wan't an expiration date.
-
Copyright. The rendering tool adds the IETF standard copyright notice. Specification is however CC-BY-SA-4.0. Don't know how to fix this.
-
Google Fonts. The rendering tool uses Google Fonts by default. I have disabled it by using a custom style.
Point 2 and 3 remain open. Don't know how to fix those without hacking the xml2rfc tool or writing our own XML->HTML tool.
There are some minor issues with the IETF XML format:
1. No explicit versioning. RFCs are in general not versioned and the format does not allow a version field. There has been a suggestion to add this ([draft-claise-semver-02](https://datatracker.ietf.org/doc/draft-claise-semver/)). Some recent RFCs just have the version in the title (e.g. [RFC 7950 - The YANG 1.1 Data Modeling Language](https://datatracker.ietf.org/doc/html/rfc7950)). This is what I've done for now.
2. Expiration date. The rendering tool xml2rfc treats the specification as an Internet-Draft that has an expiration date. We don't wan't an expiration date.
3. Copyright. The rendering tool adds the IETF standard copyright notice. Specification is however CC-BY-SA-4.0. Don't know how to fix this.
4. Google Fonts. The rendering tool uses Google Fonts by default. I have disabled it by using a custom style.
Point 2 and 3 remain open. Don't know how to fix those without hacking the xml2rfc tool or writing our own XML->HTML tool.