IESG Statement on Designating RFCs as Historic
NOTE: This IESG Statement is superseded by the IESG Statement "IESG Statement on Designating RFCs as Historic" dated 20 July 2014.
Date: 27 June 2011
RFC 2026 states the following:
In practice, the Historic status is not automatically assigned to RFCs
that have been "obsoleted". That is, when an RFC that contains the "Obsoletes: RFC XXXX" header is published the RFC editor does not
automatically apply the Historic status to the XXXX RFC. Note that in
some situations this is perfectly acceptable because multiple versions
of an Internet Standard are permitted to "honor the installed base," as
per RFC 2026.