RFC 7321 on Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)

rfc-editor@rfc-editor.org Fri, 22 August 2014 17:43 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F17AD1A0679 for <ietf-announce@ietfa.amsl.com>; Fri, 22 Aug 2014 10:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.57
X-Spam-Level:
X-Spam-Status: No, score=-107.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ltn-MdJT1af1 for <ietf-announce@ietfa.amsl.com>; Fri, 22 Aug 2014 10:43:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id B43911A0428 for <ietf-announce@ietf.org>; Fri, 22 Aug 2014 10:43:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3A91F18047C; Fri, 22 Aug 2014 10:43:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7321 on Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140822174338.3A91F18047C@rfc-editor.org>
Date: Fri, 22 Aug 2014 10:43:38 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/7k56OPA1xb0_KhVD50o--zydNpI
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2014 17:43:50 -0000

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

        
        RFC 7321

        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
        Stream:     IETF
        Date:       August 2014
        Mailbox:    mcgrew@cisco.com, 
                    paul.hoffman@vpnc.org
        Pages:      11
        Characters: 25724
        Obsoletes:  RFC 4835

        I-D Tag:    draft-ietf-ipsecme-esp-ah-reqts-10.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7321.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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC