RFC 3599 on Request for Comments Summary RFC Numbers 3500-3599
rfc-editor@rfc-editor.org Tue, 16 December 2003 00:49 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08189 for <ietf-announce-web-archive@odin.ietf.org>; Mon, 15 Dec 2003 19:49:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AW3Ed-0002v8-RM for ietf-announce-list@asgard.ietf.org; Mon, 15 Dec 2003 19:38:47 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AW3Bw-0002rs-3j for all-ietf@asgard.ietf.org; Mon, 15 Dec 2003 19:36:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07802 for <all-ietf@ietf.org>; Mon, 15 Dec 2003 19:35:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AW3Bu-0006s4-00 for all-ietf@ietf.org; Mon, 15 Dec 2003 19:35:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AW3Bt-0006rx-00 for all-ietf@ietf.org; Mon, 15 Dec 2003 19:35:58 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AW3Bt-0006ru-00 for all-ietf@ietf.org; Mon, 15 Dec 2003 19:35:57 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBG0Zvs20888; Mon, 15 Dec 2003 16:35:57 -0800 (PST)
Message-Id: <200312160035.hBG0Zvs20888@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3599 on Request for Comments Summary RFC Numbers 3500-3599
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 15 Dec 2003 16:35:57 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.6 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3599 Title: Request for Comments Summary RFC Numbers 3500-3599 Author(s): S. Ginoza Status: Informational Date: December 2003 Mailbox: ginoza@isi.edu Pages: 34 Characters: 76893 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.rfc-editor.org/in-notes/rfc3599.txt This RFC is a slightly annotated list of the 100 RFCs from RFC 3500 through RFC 3599. 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.