Implicit IV for Counter-based Ciphers in IPsec
draft-mglt-ipsecme-implicit-iv-02

Document Type Active Internet-Draft (individual)
Last updated 2016-11-14
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IPSECME                                                  D. Migault, Ed.
Internet-Draft                                                  Ericsson
Intended status: Standards Track                        T. Guggemos, Ed.
Expires: May 19, 2017                                         LMU Munich
                                                                  Y. Nir
                                                             Check Point
                                                       November 15, 2016

             Implicit IV for Counter-based Ciphers in IPsec
                 draft-mglt-ipsecme-implicit-iv-02.txt

Abstract

   IPsec ESP sends an initialization vector (IV) or nonce in each
   packet, adding 8 or 16 octets.  Some algorithms such as AES-GCM, AES-
   CCM, AES-CTR and ChaCha20-Poly1305 require a unique nonce but do not
   require an unpredictable nonce.  When using such algorithms the
   packet counter value can be used to generate a nonce, saving 8 octets
   per packet.  This document describes how to do this.

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 May 19, 2017.

Copyright Notice

   Copyright (c) 2016 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

Migault, et al.           Expires May 19, 2017                  [Page 1]
Internet-Draft                 Implicit IV                 November 2016

   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.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Implicit IV . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Initiator Behavior  . . . . . . . . . . . . . . . . . . . . .   4
   6.  Responder Behavior  . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Consideration  . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informational References  . . . . . . . . . . . . . . . .   6
   Appendix A.  Document Change Log  . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   Counter-based AES modes of operation such as AES-CTR ([RFC3686]),
   AES-CCM ([RFC4309]), and AES-GCM ([RFC4106]) require the
   specification of an nonce for each ESP packet.  The same applies for
   ChaCha20-Poly1305 ([RFC7634].  Currently this nonce is sent in each
   ESP packet ([RFC4303]).  This practice is designated in this document
   as "explicit nonce".

   In some context, such as IoT, it may be preferable to avoid carrying
   the extra bytes associated to the IV and instead generate it locally
   on each peer.  The local generation of the nonce is designated in
   this document as "implicit IV".

   The size of this nonce depends on the specific algorithm, but all of
   the algorithms mentioned above take an 8-octet nonce.

   This document defines how to compute the nonce locally when it is
   implicit.  It also specifies how peers agree with the Internet Key
Show full document text