[Swan-dev] [IPsec] Fwd: RFC 7321 on Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH) (fwd)
paul at nohats.ca
Fri Aug 22 22:48:42 EEST 2014
-------- Forwarded Message --------
Subject: RFC 7321 on Cryptographic Algorithm Implementation Requirements and
Usage Guidance for Encapsulating Security Payload (ESP) and Authentication
Date: Fri, 22 Aug 2014 10:43:38 -0700 (PDT)
From: rfc-editor at rfc-editor.org
Reply-To: ietf at ietf.org
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
CC: drafts-update-ref at iana.org, rfc-editor at rfc-editor.org
A new Request for Comments is now available in online RFC libraries.
Title: Cryptographic Algorithm Implementation
Requirements and Usage Guidance for
Encapsulating Security Payload (ESP) and
Authentication Header (AH)
Author: D. McGrew, P. Hoffman
Status: Standards Track
Date: August 2014
Mailbox: mcgrew at cisco.com,
paul.hoffman at vpnc.org
Obsoletes: RFC 4835
I-D Tag: draft-ietf-ipsecme-esp-ah-reqts-10.txt
This document updates the Cryptographic Algorithm Implementation
Requirements for the Encapsulating Security Payload (ESP) and
Authentication Header (AH). It also adds usage guidance to help in
the selection of these algorithms.
ESP and AH protocols make use of various cryptographic algorithms to
provide confidentiality and/or data origin authentication to
protected data communications in the IP Security (IPsec)
architecture. To ensure interoperability between disparate
implementations, the IPsec standard specifies a set of mandatory-to-
implement algorithms. This document specifies the current set of
mandatory-to-implement algorithms for ESP and AH, specifies
algorithms that should be implemented because they may be promoted to
mandatory at some future time, and also recommends against the
implementation of some obsolete algorithms. Usage guidance is also
provided to help the user of ESP and AH best achieve their security
goals through appropriate choices of cryptographic algorithms.
This document is a product of the IP Security Maintenance and Extensions
Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.rfc-editor.org/search
For downloading RFCs, see https://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
Association Management Solutions, LLC
More information about the Swan-dev