Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)
draft-ietf-ipsecme-rfc7321bis-05

Document Type Active Internet-Draft (ipsecme WG)
Last updated 2017-03-29 (latest revision 2017-02-27)
Replaces draft-mglt-ipsecme-rfc7321bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
On Agenda ipsecme at IETF-98
Document shepherd David Waltermire
Shepherd write-up Show (last changed 2017-02-15)
IESG IESG state Approved-announcement to be sent::External Party
Consensus Boilerplate Yes
Telechat date
Responsible AD Eric Rescorla
Send notices to "David Waltermire" <david.waltermire@nist.gov>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Network Working Group                                         D. Migault
Internet-Draft                                               J. Mattsson
Obsoletes: 7321 (if approved)                                   Ericsson
Intended status: Standards Track                              P. Wouters
Expires: August 31, 2017                                         Red Hat
                                                                  Y. Nir
                                                             Check Point
                                                              T. Kivinen
                                                           INSIDE Secure
                                                       February 27, 2017

 Cryptographic Algorithm Implementation Requirements and Usage Guidance
for Encapsulating Security Payload (ESP) and Authentication Header (AH)
                    draft-ietf-ipsecme-rfc7321bis-05

Abstract

   This document updates the Cryptographic Algorithm Implementation
   Requirements for ESP and AH.  The goal of these document is to enable
   ESP and AH to benefit from cryptography that is up to date while
   making IPsec interoperable.

   This document obsoletes RFC 7321 on the cryptographic recommendations
   only.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 31, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Migault, et al.          Expires August 31, 2017                [Page 1]
Internet-Draft      ESP and AH Algorithm Requirements      February 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Updating Algorithm Implementation Requirements and Usage
           Guidance  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Updating Algorithm Requirement Levels . . . . . . . . . .   3
     1.3.  Document Audience . . . . . . . . . . . . . . . . . . . .   4
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Manual Keying . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Encryption must be Authenticated  . . . . . . . . . . . . . .   5
   5.  ESP Encryption Algorithms . . . . . . . . . . . . . . . . . .   6
   6.  ESP and AH Authentication Algorithms  . . . . . . . . . . . .   8
   7.  ESP and AH Compression Algorithms . . . . . . . . . . . . . .   9
   8.  Summary of Changes from RFC 7321  . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     12.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The Encapsulating Security Payload (ESP) [RFC4303] and the
   Authentication Header (AH) [RFC4302] are the mechanisms for applying
   cryptographic protection to data being sent over an IPsec Security
   Association (SA) [RFC4301].

   This document provides guidance and recommendations so that ESP and
   AH can be used with a cryptographic algorithms that are up to date.
   The challenge of such document is to make sure that over the time
   IPsec implementations can use secure and up-to-date cryptographic
   algorithms while keeping IPsec interoperable.
Show full document text