On 13 Mar 2025, at 14:59, Jay Daley wrote:
So that I understand correctly, is this the current position?
1. An RFC can be (Standards Track, Best Current Practice,
Informational, Experimental) and Obsolete
Correct.
2. An RFC cannot be (Standards Track, Best Current Practice,
Informational, Experimental) and Historic as the latter replaces the
former
Correct.
3. An RFC cannot be in the STD subseries or BCP subseries, and
Obsolete, as the latter removes it from subseries, even though it does
not change the Standards Track or Best Current Practice category
Not currently true (cf. RFC 822, 2822, 5322), but nobody is clear
whether that should have ever been allowed.
4. An RFC can be both Obsolete and Historic (e.g. RFC 3300)
Correct.
5. The only time the header of an RFC (not the extra HTML header)
says it is Historic is when it is published as Historic, otherwise the
header still says (Standards Track, Best Current Practice,
Informational, Experimental)
Currently true. It's not clear whether that is the consensus of the
community anymore, but that's what our practice has been.
pr
--
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
--
rswg mailing list -- rswg@rfc-editor.org
To unsubscribe send an email to rswg-le...@rfc-editor.org
