[rfc-dist] RFC 4543 on The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed May 24 16:38:29 PDT 2006

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

        RFC 4543

        Title:      The Use of Galois Message 
                    Authentication Code (GMAC) in IPsec ESP 
                    and AH 
        Author:     D. McGrew, J. Viega
        Status:     Standards Track
        Date:       May 2006
        Mailbox:    mcgrew at cisco.com, 
                    viega at list.org
        Pages:      14
        Characters: 29818
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mcgrew-aes-gmac-esp-02.txt

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

This memo describes the use of the Advanced Encryption Standard (AES)
Galois Message Authentication Code (GMAC) as a mechanism to provide
data origin authentication, but not confidentiality, within the IPsec
Encapsulating Security Payload (ESP) and Authentication Header (AH).
GMAC is based on the Galois/Counter Mode (GCM) of operation, and can
be efficiently implemented in hardware for speeds of 10 gigabits per
second and above, and is also well-suited to software
implementations.  [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 

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

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


More information about the rfc-dist mailing list