On Tue, 19 Dec 2017, Tero Kivinen wrote:


8221 states properly:

        Obsoletes: 7321

This is in the RFC text itself and this is the proper place to
indicate that this obsoleted something.

but 7321 is missing:

        Obsoleted by: 8221

The actual RFC7321 cannot include text that it will be obseleted as
when it was published that was not known, and RFCs are not modified
after they are published.

I was not talking about the RFC text, but about the navigational support
of the datatracker based renderings of our RFCs.

The metadata header in the tools.ietf.org (the grey background block
in the beginning) can inclulde this information, but as tools.ietf.org
pages are not generated using the same database than what is used by
the datatracker, they can use old cached information that is not up to
date.

Most likely someone can, but there is nothing I can do for this, as
fixing this most likely would require cleaning the cached entry for
the rfc7321 from the tools site, and regenerate html version after all
other cached information has already been updated.

Most likely this will get fixed by itself after few weeks or months or
so when the old cached data is replaced with new data.

That is not my experience. I have seen this for drafts going back years
and they only get fixed when I point it out directly to the tools person
or sometimes when I poke this list.

Proper place to complain these things might be the
tools-disc...@ietf.org mailing list, but it is always better to check
things in the datatracker.ietf.org first and see if this is
tools.ietf.org related problem or whether there is real problem with
the source data...

It would be good if someone could scrape the entire repository and check
it for consistency. I'm pretty sure these artifacts are very common, and
that bugs are still present. And it is more then esthetic. People assume
the pages don't lie about what is a latest version or that a document is
really not obsoleted by a new document when it doesn't say so.

If anyone has no Christmas project, this could be a nice time killer :)

Paul

_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to