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


        RFC 2411:

        Title:	    IP Security Document Roadmap
	Author(s):  R. Thayer, N. Doraswamy, R. Glenn
	Status:     Informational
	Date:       November 1998
        Mailbox:    rodney@sabletech.com, naganand@baynetworks.com,
	            rob.glenn@nist.gov
	Pages:      11
        Characters: 22796
        Updates/Obsoletes/See Also: None
        I-D Tag:    draft-ietf-ipsec-doc-roadmap-02.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2411.txt


The IPsec protocol suite is used to provide privacy and
authentication services at the IP layer.  Several documents are used
to describe this protocol suite.  The interrelationship and
organization of the various documents covering the IPsec protocol are
discussed here.  An explanation of what to find in which document,
and what to include in new Encryption Algorithm and Authentication
Algorithm documents are described.

This document is a product of the IP Security Protocol Working Group
of the IETF.

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 Alegre Ramos
USC/Information Sciences Institute