On 2018-05-15 02:17, Brian E Carpenter wrote:
Top posting to note that if you find the RFC via its DOI you also get the correct status first. I think the RFC Editor has done the best they can, consistent with the policy that the bits in the canonical form of an RFC never change. ...
In the hopefully not so distant future, the RFC Editor will also serve HTML. As that is *not* the "canonical" version, it could dynamically insert current metadata (such as demonstrated in various places, for instance <https://tools.ietf.org/html/rfc2616> or <https://greenbytes.de/tech/webdav/rfc2616.html>).
To make this work *well*, the RFC Editor should publish the metadata *per* RFC in a machine readable (XML or JSON) and web-friendly (CORS) way.
Best regards, Julian
