RFC 2555 on 30 Years of RFCs
RFC Editor <rfc-ed@ISI.EDU> Wed, 07 April 1999 20:15 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14620 for ietf-123-outbound.10@ietf.org; Wed, 7 Apr 1999 16:15:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14475 for <all-ietf@ietf.org>; Wed, 7 Apr 1999 16:08:48 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA00356; Wed, 7 Apr 1999 13:08:50 -0700 (PDT)
Message-Id: <199904072008.NAA00356@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2555 on 30 Years of RFCs
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 07 Apr 1999 13:08:50 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2555:
Title: 30 Years of RFCs
Author(s): RFC Editor, et al.
Status: Informational
Date: 7 April 1999
Mailbox: braden@isi.edu, jkrey@isi.edu, crocker@mbl.edu,
vcerf@mci.net, feinler@juno.com, celeste@isi.edu
Pages: 18
Characters: 42902
Updates/Obsoletes/See Also: None
I-D Tag: none
URL: ftp://ftp.isi.edu/in-notes/rfc2555.txt
History and reflections on the Request for Comments (RFC) document
series, and the people who made it possible, on its 30th anniversary.
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 Alegre Ramos
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.
- RFC 2555 on 30 Years of RFCs RFC Editor