On 18 Dec 2024, at 10:43, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
Brian E Carpenter writes:
A good example of the possible confusion that such a move would
cause. RFC1725 was obsoleted by RFC1939, which is the current POP3
standard (and has itself been updated by four other RFCs).
That raises an interesting philosophical question, though. When A
is obsoleted by B which is then updated by C and D, what *is* the
actual status of A? It has always been my impression that, while
A is effectively 'dead', it is still the foundation document for
the series, and I think A's 'obsolete' status clearly indicates
that. But to declare A as dead, to me, is a declaration that the
entire series is also dead, and should be marked as such.
But ulitmately, I just don't understand the recent fetish people
have picked up for marking everything more than a decade old as
'historic'. Surely they have better things they can waste their,
and our, time on.
For things that never made it to Internet Standard, I totally agree. But
for things that are on the Internet Standard list (and we can argue
about whether *that* is useful or not), they stick out like sore thumbs
on the website. The mechanism to undo that is to move them to Historic.
And that now takes just a simple Last Call like this one. And there's
only a handful of them. So why not?
pr
--
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
