[ 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.

Note: RFC 1528 and RFC 1706 are both on the "Legacy Stream" (before the "IETF Stream" was created by eg RFC 2026, RFC 5741). Technically this might mean that the IESG cannot officially mark them as historic, and
officially this decision may belong to the RFC Editor -- and so, the IESG is "suggesting" that the RFC Editor does this, and not instructing the RFC Editor to do so. Yay, isn't process wonkery fun?! ]

draft-davies-int-historic [RFC ED: Please replace with the RFC number when published] 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].