RFC 3109 Request to Move STD 39 to Historic Status
RFC Editor <rfc-ed@ISI.EDU> Tue, 05 June 2001 17:30 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26752; Tue, 5 Jun 2001 13:30:29 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA24669 for ietf-123-outbound.10@ietf.org; Tue, 5 Jun 2001 12:55:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id MAA24612 for <all-ietf@loki.ietf.org>; Tue, 5 Jun 2001 12:48:24 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25755 for <all-ietf@ietf.org>; Tue, 5 Jun 2001 12:48:21 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f55GlfG04760; Tue, 5 Jun 2001 09:47:41 -0700 (PDT)
Message-Id: <200106051647.f55GlfG04760@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3109 Request to Move STD 39 to Historic Status
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 05 Jun 2001 09:47:41 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
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-01.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.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.