RFC 2799 on Summary of 2700-2799
RFC Editor <rfc-ed@ISI.EDU> Fri, 22 September 2000 23:27 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28453; Fri, 22 Sep 2000 19:27:02 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA19882 for ietf-123-outbound.10@ietf.org; Fri, 22 Sep 2000 19:15:01 -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 TAA19853 for <all-ietf@loki.ietf.org>; Fri, 22 Sep 2000 19:12:36 -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 TAA28247 for <all-ietf@ietf.org>; Fri, 22 Sep 2000 19:12:34 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA08013; Fri, 22 Sep 2000 16:12:34 -0700 (PDT)
Message-Id: <200009222312.QAA08013@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2799 on Summary of 2700-2799
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 22 Sep 2000 16:12:34 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2799 Title: Request for Comments Summary RFC Numbers 2700-2799 Author(s): S. Ginoza Status: Informational Date: September 2000 Mailbox: ginoza@isi.edu Pages: 23 Characters: 42622 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2799.txt Many RFCs, but not all, are Proposed Standards, Draft Standards, or Standards. Since the status of these RFCs may change during the standards processing, we note here only that they are on the standards track. Please see the latest edition of "Internet Official Protocol Standards" for the current state and status of these RFCs. In the following, RFCs on the standards track are marked [STANDARDS-TRACK]. This RFC is a slightly annotated list of the 100 RFCs from RFC 2700 through RFCs 2799. 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@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.
- RFC 2799 on Summary of 2700-2799 RFC Editor