Further closing the loop:
On Thursday's telechat, the IESG approved the status change of ADSP to
Historic status, and the official announcement of that (which this is
not) will be posted early next week. The IESG considers that it has
followed the process specified in RFC 2026, Section 6.4, with regard
to the status change. It also considers that further documentation
than what already is and will be provided (in the status change
document, in the telechat minutes, and so on) is neither required nor
particularly necessary. As Dave points out, some status changes have
come with associated RFCs, and some have not.
That said, a point was raised to me by Scott in an off-list exchange,
and indirectly on list by John: We do, indeed, have these nice, new
"status change" documents, but they are not RFCs and we have no
specification of the process by which they're approved and published.
I brought that point up, and the IESG will be discussing it in the
next few weeks.
My personal opinion on what we should do with that is a bit mixed: on
the one hand, these documents are tools to implement the discretion
the IESG already has according to RFC 2026, and their introduction
neither creates nor requires any change in process; on the other hand,
if we are, as I would like, to use them as permanent documentation for
our actions, some specification of how we use them might have value.
More on that, after the IESG has considered the question.
Separately, I will be asking the RFC Editor if they can include the
status change documents in their RFC metadata, adding one more place
where the right information can be found.
Barry, Applications AD