Document Action: Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures to Historic

The IESG <iesg-secretary@ietf.org> Mon, 09 January 2023 23:00 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: Document Action: Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures to Historic
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, iana@iana.org, rfc-editor@rfc-editor.org, rfc1528@ietf.org, rfc1706@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <167330522928.3526.2057476230476181638@ietfa.amsl.com>
Date: Mon, 09 Jan 2023 15:00:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/0NUuUCzFL0bAqCuZgVpEld0wW9Q>

The IESG has approved changing the status of the following document:
- Principles of Operation for the TPC.INT Subdomain: Remote Printing --
Technical Procedures
  (rfc1528) to Historic

This document action is documented at:
https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc1528/

Status Change Details:

[ RFC Editor: Please remove this section before publication.

Dear community:
What you have here is the "status change" document for RFC 1528 and RFC 1706.
This document itself doesn't actually *do* anything; it will be published on
the datatracker pages for RFC 1528 and RFC 1706, and will point to whatever
RFC draft-davies-int-historic becomes.

If you are (understandably!) confused, the process for making an RFC
"historic" is documented here:
https://www.ietf.org/about/groups/iesg/statements/designating-rfcs-historic-2014-07-20/.
This document uses process #3.]

draft-davies-int-historic [RFC ED: Replace with RFC number] marks RFC 1528
and RFC 1706 as historic.

Section 3.1 of draft-davies-int-historic makes RFC 1528 historic:

   The specification for tpc.int [RFC1528] should be deemed historic as
   it no longer functions as described in the document.

Section 2.4 of draft-davies-int-historic makes RFC 1706 historic:

   The nsap.int domain name was specified to experimentally map Open
   Systems Interconnection (OSI) Network Service Access Points to domain
   names [RFC1706].

Personnel

   Warren Kumari is the responsible Area Director.

Document Action: Principles of Operation for the … The IESG