Alvaro, Just to be sure the record is clear, there were objections to changing the status of RFC 911. They were not claims that 911 is still of active interest but objections to the idea of making changes to the status of _any_ status "Unknown" document, especially of that vintage, without a coherent plan about what to do about all of the others. The lack of clarity of responsibility to which you refer is only one of the obstacles to making such a plan. Not a big difference, but possibly helpful to the next person who comes along and tries to review the history. thanks, john --On Friday, February 18, 2022 11:38 -0800 Alvaro Retana <aretana.ietf@xxxxxxxxx> wrote: > Hi! > > This Last Call expired today. Thank you for all the feedback! > > > There was no objection to changing the status of rfc911. > > However, given that there is a lack of clarity of > responsibility related to "unknown" status RFCs published > before the IETF was formed, the IESG won't pursue a formal > action at this point. > > > Thanks! > > Alvaro. > > On January 20, 2022 at 5:34:38 PM, The IESG > (iesg-secretary@xxxxxxxx) wrote: > > > The IESG has received a request from an individual participant > to make the following status changes: > > - RFC911 from Unknown to Historic > (EGP Gateway under Berkeley UNIX 4.2) > > The supporting document for this request can be found here: > > https://datatracker.ietf.org/doc/status-change-rfc911-to-histo > ric/ > > The IESG plans to make a decision in the next few weeks, and > solicits final comments on this action. Please send > substantive comments to the last-call@xxxxxxxx mailing lists > by 2022-02-18. Exceptionally, comments may be sent to > iesg@xxxxxxxx instead. In either case, please retain the > beginning > of the Subject line to allow automated sorting. > > The affected document can be obtained via > https://datatracker.ietf.org/doc/rfc911/ > > IESG discussion of this request can be tracked via > https://datatracker.ietf.org/doc/status-change-rfc911-to-histo > ric/ballot/ > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf-announce -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
