RFC 4308 on Cryptographic Suites for IPsec

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

        RFC 4308

        Title:      Cryptographic Suites for IPsec
        Author(s):  P. Hoffman
        Status:     Standards Track
        Date:       December 2005
        Mailbox:    paul.hoffman@vpnc.org
        Pages:      7
        Characters: 13127
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipsec-ui-suites-06.txt

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

The IPsec, Internet Key Exchange (IKE), and IKEv2 protocols rely on
security algorithms to provide privacy and authentication between the
initiator and responder.  There are many such algorithms available,
and two IPsec systems cannot interoperate unless they are using the
same algorithms.  This document specifies optional suites of
algorithms and attributes that can be used to simplify the
administration of IPsec when used in manual keying mode, with IKEv1 or
with IKEv2.

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

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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.

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.