RFC 3602 on The AES-CBC Cipher Algorithm and Its Use with IPsec

rfc-editor@rfc-editor.org Wed, 24 September 2003 23:42 UTC

Message-Id: <200309242315.h8ONFFO11783@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3602 on The AES-CBC Cipher Algorithm and Its Use with IPsec
Cc: rfc-editor@rfc-editor.org, ipsec@lists.tislabs.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 24 Sep 2003 16:15:14 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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


        RFC 3602

        Title:      The AES-CBC Cipher Algorithm and Its Use with
                    IPsec
        Author(s):  S. Frankel, R. Glenn, S. Kelly
        Status:     Standards Track
        Date:       September 2003
        Mailbox:    sheila.frankel@nist.gov, rob.glenn@nist.gov,
                    scott@hyperthought.com
        Pages:      15
        Characters: 30254
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipsec-ciph-aes-cbc-05.txt

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


This document describes the use of the Advanced Encryption Standard
(AES) Cipher Algorithm in Cipher Block Chaining (CBC) Mode, with an
explicit Initialization Vector (IV), as a confidentiality mechanism
within the context of the IPsec Encapsulating Security Payload (ESP). 

This document is a product of the IP Security 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.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/rfc3602.txt"><ftp://ftp.isi.edu/in-notes/rfc3602.txt>

RFC 3602 on The AES-CBC Cipher Algorithm and Its … rfc-editor