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

Yaron Sheffer <yaronf.ietf@gmail.com> Fri, 22 August 2014 19:26 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 986CB1A058E for <ipsec@ietfa.amsl.com>; Fri, 22 Aug 2014 12:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 b75Nq7V-YeN5 for <ipsec@ietfa.amsl.com>; Fri, 22 Aug 2014 12:26:38 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4B961A04B4 for <ipsec@ietf.org>; Fri, 22 Aug 2014 12:26:37 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hi2so133340wib.17 for <ipsec@ietf.org>; Fri, 22 Aug 2014 12:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=aX4Bs0nsV37YycqloQt5yZyMX9Pac+pp9fOJavTSFs4=; b=wSw58LUtfhdgROhmOrsfPt9SEaX6vEE1l5tzFdrMDPHs5fAIOrmEBBM1tIbKK4V7mv G74OXZnrpnpku/T9Gnf+fpm55HWTdi0sJl/gCMehpHjkw6XN8UGOrwTa93H3qa7D8cHd Ch5l0kEjqHlDoS2S8jiiRF3oGdmR6A1Nr6X3BXyTbKklN61hJeWA/m+/DbAccbJxQJRd SJnvb/M9ZyoL9/UkxrmyRQ/RiY9kE3uiLVUt/RLtUKSuMRD1OolVB5qI37vCCzSoHZ9R HzxKE/A7CnZ0AOR+FZfBQ557UPLTKjW/liK0zxuBmdbQl9R/X3vJd8A8SZAHHRyiUCWp nYjA==
X-Received: by 10.180.99.4 with SMTP id em4mr541305wib.8.1408735596285; Fri, 22 Aug 2014 12:26:36 -0700 (PDT)
Received: from [10.0.0.3] (bzq-79-177-106-104.red.bezeqint.net. [79.177.106.104]) by mx.google.com with ESMTPSA id xw9sm77336389wjc.32.2014.08.22.12.26.35 for <ipsec@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Aug 2014 12:26:35 -0700 (PDT)
Message-ID: <53F79969.5030906@gmail.com>
Date: Fri, 22 Aug 2014 22:26:33 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: ipsec <ipsec@ietf.org>
References: <20140822174338.3A91F18047C@rfc-editor.org>
In-Reply-To: <20140822174338.3A91F18047C@rfc-editor.org>
X-Forwarded-Message-Id: <20140822174338.3A91F18047C@rfc-editor.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipsec/fp22-gZZytPLyY735dkzLLLHHTc
Subject: [IPsec] Fwd: RFC 7321 on Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2014 19:26:40 -0000



-------- Forwarded Message --------
Subject: RFC 7321 on Cryptographic Algorithm Implementation Requirements 
and Usage Guidance for Encapsulating Security Payload (ESP) and 
Authentication Header (AH)
Date: Fri, 22 Aug 2014 10:43:38 -0700 (PDT)
From: rfc-editor@rfc-editor.org
Reply-To: ietf@ietf.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org

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