ietf-tools / datatracker

The day-to-day front-end to the IETF database for people who work on IETF standards.
https://datatracker.ietf.org
BSD 3-Clause "New" or "Revised" License
588 stars 353 forks source link

"Also known as BCP" sometimes missing #4426

Open larseggert opened 2 years ago

larseggert commented 2 years ago

Describe the issue

https://datatracker.ietf.org/doc/rfc8713/ correctly says "Also known as BCP 79".

https://datatracker.ietf.org/doc/rfc8713/ is part of BCP 10 (see https://www.rfc-editor.org/rfc/rfc8713.html), but the datatracker page does not indicate that.

Code of Conduct

rjsparks commented 2 years ago

Well known problem with a solution in queue, but it will still be some time before the we can implement that solution. That will be to refactor RFCs to be their own document type, and then add the subseries as a document type. We will then use RelatedDocument relations to show what draft an RFC came from, and what RFCs are part of, e.g., a BCP.

See #4329 and follow the links in the comments from there.

This will be a big lift, but it will address many open issues, including our biggest performance bottleneck.

larseggert commented 2 years ago

Maybe we should take that "aka" bit out then, if it's not always correct.

rjsparks commented 2 years ago

(The same way we should remove most of /stats). We could do that, but before simply removing it from the template, we need a close look at the data to make sure that the only time it's being invoked is the use case we are focusing on here.