Mykyta Yevstifeyev wrote:
Hello,
The proposed statement is mostly fine. But, since RFC 2026 gives very
little information on some issues, I'd like you considered them in the
statement.
First, for RFCs of what categories is it legitimate to move them to
Historic. Whether Experimental or Informational RFCs could be
considered for such action? As far as I understand RFC 2026, Historic
can be assigned to Standards Track documents; however it won't be
excessive to clarify this regulation in the IESG statement additionally.
My understanding is that any RFC can be moved to Historic. But if this
is not clear from RFC 2026, maybe it is worth clarifying.
I support the opinion that the information on what the particular RFC
moves to Historic shouldn't go in the Abstract; the current practice
is also the same (see eg. http://tools.ietf.org/html/rfc6265, end of
Section 1). Let's mention it is only put in the Introduction.
The proposed statement says almost nothing about how the RFC may be
moved to Historic status without the necessity to publish a separate
RFC for this purpose. Here I agree with John Klensin. Let's adopt
something like proposed in
http://tools.ietf.org/id/draft-ietf-newtrk-cruft-00.txt, but more
lightweight. What I mean is that the procedure should be:
(1) an individual or a group of individuals apply to the appropriate
AD for moving some specification to Historic;
(2) AD asks Secretariat to issue a 2-to-4-week Last Call on
reclassification;
(3) once community consensus is determined, AD brings the question to
IESG's attention via putting it on agenda as "Management Issue";
From the pedantic deparment:
As a matter of clarification: it is already possible to move an RFC to
Historic without new draft using the datatracker. The RFC is added to
datatracker (just like a draft), etc. This is not going to be a
management item, it would appear as a proper document on IESG agenda.
"Management items" are second class citizens during IESG telechats...
(4) if IESG does not object, the announcement is sent to RFC Editor
and copied to IETF Announce list containing request to change the
particular RFC's status to Historic.
Such procedure seems lightweight enough not to create dozens of new
RFCs reclassifying the old ones but have the appropriate community
involvement.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf