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

The information below is for an old version of the document
Document Type Active Internet-Draft (ipsecme WG)
Last updated 2014-04-12 (latest revision 2014-04-11)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yaron Sheffer
Shepherd write-up Show (last changed 2014-04-12)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Kathleen Moriarty
Send notices to ipsecme-chairs@tools.ietf.org, draft-ietf-ipsecme-esp-ah-reqts@tools.ietf.org
Network Working Group                                          D. McGrew
Internet-Draft                                             Cisco Systems
Obsoletes: 4835 (if approved)                                 P. Hoffman
Intended status: Standards Track                          VPN Consortium
Expires: October 13, 2014                                 April 11, 2014

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

Abstract

   This Internet Draft is standards track proposal to update to the
   Cryptographic Algorithm Implementation Requirements for ESP and AH;
   it also adds usage guidance to help in the selection of these
   algorithms.

   The Encapsulating Security Payload (ESP) and Authentication Header
   (AH) protocols makes 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.

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 October 13, 2014.

McGrew & Hoffman        Expires October 13, 2014                [Page 1]
Internet-Draft         Requirements for ESP and AH            April 2014

Copyright Notice

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

   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.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Implementation Requirements . . . . . . . . . . . . . . . . .   4
     2.1.  ESP Authenticated Encryption (Combined Mode Algorithms) .   4
     2.2.  ESP Encryption Algorithms . . . . . . . . . . . . . . . .   4
     2.3.  ESP Authentication Algorithms . . . . . . . . . . . . . .   4
     2.4.  AH Authentication Algorithms  . . . . . . . . . . . . . .   5
     2.5.  Summary of Changes  . . . . . . . . . . . . . . . . . . .   5
   3.  Usage Guidance  . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Authenticated Encryption  . . . . . . . . . . . . . . . .   6
     4.2.  Encryption Transforms . . . . . . . . . . . . . . . . . .   6
     4.3.  Authentication Transforms . . . . . . . . . . . . . . . .   7
   5.  Algorithm Diversity . . . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

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
Show full document text