Last Call: Moving TPC.INT and NSAP.INT infrastructure domains to historic

The IESG <iesg-secretary@ietf.org> Wed, 30 March 2022 21:18 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: Moving TPC.INT and NSAP.INT infrastructure domains to historic
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <164867508759.15594.2523981628049164116@ietfa.amsl.com>
Date: Wed, 30 Mar 2022 14:18:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/oWlCPUVIhy_PXpeXqPr6Sf-MQeU>

-----
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
last-call@ietf.org mailing lists by 2022-04-27. Exceptionally, comments may
be sent to iesg@ietf.org 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/

Last Call: Moving TPC.INT and NSAP.INT infrastruc… The IESG