[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC 3599 on Request for Comments Summary RFC Numbers 3500-3599




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.
<ftp://ftp.isi.edu/in-notes/rfc3599.txt>