[rfc-dist] RFC 5282 on Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 (IKEv2) Protocol
rfc-editor at rfc-editor.org
Thu Aug 21 11:45:28 PDT 2008
A new Request for Comments is now available in online RFC libraries.
Title: Using Authenticated Encryption Algorithms with
the Encrypted Payload of the Internet
Key Exchange version 2 (IKEv2) Protocol
Author: D. Black, D. McGrew
Status: Standards Track
Date: August 2008
Mailbox: black_david at emc.com,
mcgrew at cisco.com
I-D Tag: draft-black-ipsec-ikev2-aead-modes-01.txt
An authenticated encryption algorithm combines encryption and
integrity into a single operation; such algorithms may also be
referred to as combined modes of an encryption cipher or as combined
mode algorithms. This document describes the use of authenticated
encryption algorithms with the Encrypted Payload of the Internet Key
Exchange version 2 (IKEv2) protocol.
The use of two specific authenticated encryption algorithms with the
IKEv2 Encrypted Payload is also described; these two algorithms are
the Advanced Encryption Standard (AES) in Galois/Counter Mode (AES
GCM) and AES in Counter with CBC-MAC Mode (AES CCM). Additional
documents may describe the use of other authenticated encryption
algorithms with the IKEv2 Encrypted Payload. [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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist