RFC 1699 on Summary of RFCs 1600-1699
RFC Editor <rfc-ed@isi.edu> Mon, 06 January 1997 19:25 UTC
Received: from ietf.org by ietf.org id aa15510; 6 Jan 97 14:25 EST
Received: from zephyr.isi.edu by ietf.org id aa15346; 6 Jan 97 14:23 EST
Received: from zephyr.isi.edu by zephyr.isi.edu (5.65c/5.61+local-23) id <AA05789>; Mon, 6 Jan 1997 11:21:35 -0800
Message-Id: <199701061921.AA05789@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC 1699 on Summary of RFCs 1600-1699
Cc: rfc-ed@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 06 Jan 1997 11:21:35 -0800
Sender: ietf-announce-request@ietf.org
From: RFC Editor <rfc-ed@isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 1699: Title: Request for Comments Summary Summary of 1600-1699 Author: J. Elliott Date: January 1997 Mailbox: elliott@isi.edu Pages: 21 Characters: 40674 Updates/Obsoletes: None URL: ftp://ds.internic.net/rfc/rfc1699.txt This RFC is a slightly annotated list of the 100 RFCs from RFC 1600 through RFCs 1699. This is a status report on these RFCs. 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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@ISI.EDU. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@ISI.EDU 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 admin@DS.INTERNIC.NET. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Mary Kennedy 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 1699 on Summary of RFCs 1600-1699 RFC Editor