Request to Move STD 39 to Historic Status
draft-ymbk-std39-historic-02

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (individual)
Authors John Klensin  , Randy Bush 
Last updated 2013-03-02 (latest revision 2001-05-14)
Stream Legacy stream
Formats plain text pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3109 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3109

        Title:      Request to Move STD 39 to Historic Status
        Author(s):  R. Braden,  R. Bush, J. Klensin
        Status:     Informational
        Date:       May 2001
        Mailbox:    braden@isi.edu, randy@psg.com, klensin@jck.com 
        Pages:      4
        Characters: 5841
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ymbk-std39-historic-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3109.txt

This memo changes the status of STD 39, BBN Report 1822,
"Specification of the Interconnection of a Host and an IMP", from
Standard to Historic.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.