RFC 3199 on Request for Comments Summary RFC Numbers 3100-3199
rfc-editor@rfc-editor.org Thu, 06 February 2003 17:53 UTC
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27861; Thu, 6 Feb 2003 12:53:58 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18gqBN-0006RK-00 for ietf-announce-list@ran.ietf.org; Thu, 06 Feb 2003 12:51:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18gqBH-0006Q8-00 for all-ietf@ran.ietf.org; Thu, 06 Feb 2003 12:51:23 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27600 for <all-ietf@ietf.org>; Thu, 6 Feb 2003 12:46:05 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h16HniD21030; Thu, 6 Feb 2003 09:49:44 -0800 (PST)
Message-Id: <200302061749.h16HniD21030@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3199 on Request for Comments Summary RFC Numbers 3100-3199
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 06 Feb 2003 09:49:43 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3199 Title: Request for Comments Summary RFC Numbers 3100-3199 Author(s): S. Ginoza Status: Informational Date: February 2003 Mailbox: ginoza@isi.edu Pages: 24 Characters: 47287 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.rfc-editor.org/in-notes/rfc3199.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 3100 through RFCs 3199. 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.