[rfc-dist] RFC 3299 on Request for Comments Summary RFC Numbers 3200-3299

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Mon, 15 Dec 2003 16:33:04 -0800


A new Request for Comments is now available in online RFC libraries.

        RFC 3299

        Title:      Request for Comments Summary RFC Numbers 3200-3299
        Author(s):  S. Ginoza
        Status:     Informational
        Date:       December 2003
        Mailbox:    ginoza@isi.edu
        Pages:      30
        Characters: 63813
        Updates/Obsoletes/SeeAlso:    None

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3299.txt

This RFC is a slightly annotated list of the 100 RFCs from RFC 3200
through RFC 3299.  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

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.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <031215163205.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3299

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <031215163205.RFC@RFC-EDITOR.ORG>