It appears that Pete Resnick <resnick@xxxxxxxxxxxx> said: >> In an odd way, your example involving using RFC 793 supports my point: >> if you retrieve the text form rfc-index from the RFC Editor site, you >> will find that, while the "STD 7" designation is gone, the Status >> listed is not, e.g., Historic but "Internet Standard". Same issue if >> one goes to https://rfc-editor.org/ end enters "793" in the search >> box: the page that turns up says "Internet Standard" in the Status >> column. > >Well, that is clearly a bug that needs to be fixed. That file is created from the RPC's database by an old tired script. I was probably the last person to touch it when I added DOIs. There are other Internet Standards that haves been obsoleted, 1119, 1723 and 1725, and lots and lots of Proposed Standard, Draft Standard, and BCP. It would not be hard to patch the script to say "Status before being obsoleted" to make it clearer what happened. It seems to me that if something has been obsoleted that should automatically make it Historic. RFC 2026 even says so: 4.2.4 Historic A specification that has been superseded by a more recent specification or is for any other reason considered to be obsolete is assigned to the "Historic" level. R's, John -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
