Den 12. aug. 2015 14:27, skrev Stephen Farrell:
> As far as I know there aren't any other status changes that
> provide us with useful precedent here, but I could be wrong
> on that.
These go the other way (from Proposed to Historic), but we have some
transitions that were managed by publishing RFCs:
3638 Applicability Statement for Reclassification of RFC 1643 to
Historic Status
4223 Reclassification of RFC 1863 to Historic.
5125 Reclassification of RFC 3525 to Historic.
7142 Reclassification of RFC 1142 to Historic.
And the following RFC that did a whole slew of reclassifications:
4450 Getting Rid of the Cruft: Report from an Experiment in
Identifying and Reclassifying Obsolete Standards Documents.
The pattern here, which may or may not be something we want to emulate,
is that when we make a decision, we publish a document saying why.
RFC numbers are cheap. (The debate required to agree on the text may not
be.)