On Fri, Jan 21, 2022 at 10:11 AM John C Klensin <john-ietf@xxxxxxx> wrote:
--On Friday, January 21, 2022 15:52 +0000 "Salz, Rich"
<rsalz@xxxxxxxxxx> wrote:
>> More broadly (and as explained in probably too much detail
>> in a
> note I sent last night), I think that either the IETF (or,
> better, the RFC Editor Function as Brian suggested) should
> initiate a project to clean out those old specs
>
> Such a project sounds good, but I worry about the best being
> the enemy of the goodXXXX any incremental progress.
On the other hand, considering all of the pre-IETF documents
that have so far been listed as "UNKNOWN", one at a time with
one Last Call per document and on-list negotiation of how the
permanent statement about the action should read strikes me a
horribly expensive in IETF Community and IESG time even though
it would probably constitute "incremental progress".
What if we looked at this from the converse, is there anything with a status of "UNKNOWN" that is currently useful information to the standards process, which is controlled by the IETF and IESG, other than as historical context?
If there is, then the IETF and the IESG should promote such documents with a relevant status within the standards process, be that "Informational", "BCP", or something else in the standards track. For example, as was done with RFC20 a few years ago. Once such a review for relevance to the standards process is completed, by the IETF and IESG, then the RFC Editor at their discretion can make the decision about the status of these older RFCs with a status of "UNKNOWN".
So, relating to the RFCs with "UNKNOWN" status, it is the IETF and IESG's job to determine if they have current relevance to the standards process, baring such current relevance the status of these documents should be the responsibility of the RFC Editor.
Thanks.
===============================================
David Farmer Email:farmer@xxxxxxx
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE Phone: 612-626-0815
Minneapolis, MN 55414-3029 Cell: 612-812-9952
===============================================
David Farmer Email:farmer@xxxxxxx
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE Phone: 612-626-0815
Minneapolis, MN 55414-3029 Cell: 612-812-9952
===============================================
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
