[rfc-dist] RFC 3199 on Request for Comments Summary RFC Numbers 3100-3199

[[e-mail] ([e-mail])]

--NextPart


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:    [e-mail]
        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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  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.

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

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="[e-mail]"

Content-Type: text/plain
Content-ID: <[e-mail]>

RETRIEVE: rfc
DOC-ID: rfc3199

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3199.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <[e-mail]>

--OtherAccess--
--NextPart--