[rfc-dist] RFC 4494 on The AES-CMAC-96 Algorithm and Its Use with IPsec

[rfc-editor@rfc-editor.org]

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

        
        RFC 4494

        Title:      The AES-CMAC-96 Algorithm and Its 
                    Use with IPsec 
        Author:     JH. Song, R. Poovendran,
                    J. Lee
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    songlee at ee.washington.edu, 
                    radha at ee.washington.edu, 
                    jicheol.lee at samsung.com
        Pages:      8
        Characters: 14992
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-songlee-aes-cmac-96-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4494.txt

The National Institute of Standards and Technology (NIST) has recently
specified the Cipher-based Message Authentication Code (CMAC), which
is equivalent to the One-Key CBC-MAC1 (OMAC1) algorithm submitted by
Iwata and Kurosawa.  OMAC1 efficiently reduces the key size of
Extended Cipher Block Chaining mode (XCBC).  This memo specifies the
use of CMAC mode as an authentication mechanism of the IPsec
Encapsulating Security Payload (ESP) and the Authentication Header
(AH) protocols.  This new algorithm is named AES-CMAC-96.  
[STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...