[rfc-dist] RFC 4434 on The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)

rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Mon, 27 February 2006 20:58 UTC

From: "rfc-editor at rfc-editor.org"
Date: Mon, 27 Feb 2006 12:58:43 -0800
Subject: [rfc-dist] RFC 4434 on The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)
Message-ID: <200602272058.k1RKwhl6005509@nit.isi.edu>

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

        
        RFC 4434

        Title:      The AES-XCBC-PRF-128 Algorithm for the 
                    Internet Key Exchange Protocol (IKE) 
        Author:     P. Hoffman
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    paul.hoffman at vpnc.org
        Pages:      6
        Characters: 9384
        Obsoletes:  RFC3664
        See-Also:   

        I-D Tag:    draft-hoffman-rfc3664bis-05.txt

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

Some implementations of IP Security (IPsec) may want to use a
pseudo-random function derived from the Advanced Encryption Standard
(AES).  This document describes such an algorithm, called AES-XCBC-PRF-128.  [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

...