----- Please note: This is a second IETF LC. This isn't really a document (or at least a document that does anything). The "IESG Statement on Designating RFCs as Historic" (https://www.ietf.org/about/groups/iesg/statements/designating-rfcs-historic-2014-07-20/ ) says that: "The current process, then, of moving an RFC to Historic status is to follow one of these, depending upon the level of documentation and discussion of the documentation required: 1: [...] 2: "An individual or a working group posts an Internet Draft containing an explanation of the reason for the status change. The I-D is discussed and iterated as usual for I-Ds. At some point, it is sent to an appropriate AD to request publication. The AD creates a status-change document, with an explanation that points to the I-D. The I-D and the status-change are then last-called together, after which the IESG evaluates and ballots on both." [...] 3: "As #2 above, except that the I-D might also contain other information. In this case, after IESG approval the I-D is sent to the RFC Editor. When the RFC is published, the status-change document is changed to point to the RFC instead of the I-D." [...]
This last call is *just* for the status change document (https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic), which is just a supporting document for https://datatracker.ietf.org/doc/draft-davies-int-historic/ (which does the actual work and explains stuff). Basically, this is process-wonkey - please read https://datatracker.ietf.org/doc/draft-davies-int-historic/ instead, it's much more useful an interesting... ---- The IESG has received a request from an individual participant to make the following status changes: - RFC1706 from Informational to Historic (DNS NSAP Resource Records) - RFC1528 from Experimental to Historic (Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures) The supporting document for this request can be found here: https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/ 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 [email protected] mailing lists by 2022-04-27. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The affected documents can be obtained via https://datatracker.ietf.org/doc/rfc1706/ https://datatracker.ietf.org/doc/rfc1528/ IESG discussion of this request can be tracked via https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/ballot/ _______________________________________________ IETF-Announce mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-announce
