RFC 1799 on Summary of RFCs 1700-1799

RFC Editor <rfc-ed@isi.edu> Mon, 06 January 1997 19:28 UTC

Received: from ietf.org by ietf.org id aa15833; 6 Jan 97 14:28 EST
Received: from zephyr.isi.edu by ietf.org id aa15593; 6 Jan 97 14:26 EST
Received: from zephyr.isi.edu by zephyr.isi.edu (5.65c/5.61+local-23) id <AA06226>; Mon, 6 Jan 1997 11:24:54 -0800
Message-Id: <199701061924.AA06226@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC 1799 on Summary of RFCs 1700-1799
Cc: rfc-ed@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 06 Jan 1997 11:24:54 -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 1799:

        Title:      Request for Comments Summary
                    RFC Numbers 1700-1799
        Author:     M. Kennedy
        Date:       January 1997
        Mailbox:    mkennedy@isi.edu
        Pages:      21
        Characters: 42038
        Updates/Obsoletes: None

        URL:        ftp://ds.internic.net/rfc/rfc1799.txt


This RFC is a slightly annotated list of the 100 RFCs from RFC 1700
through RFCs 1799.  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.
ftp://ds.internic.net/rfc/rfc1799.txt"><ftp://ds.internic.net/rfc/rfc1799.txt>