Implicit IV for AES-CBC, AES-CTR, AES-CCM and AES-GCM
draft-mglt-6lo-aes-implicit-iv-01

Document Type Replaced Internet-Draft (individual)
Last updated 2015-08-20 (latest revision 2015-02-16)
Replaced by draft-ietf-ipsecme-implicit-iv
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ipsecme-implicit-iv
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mglt-6lo-aes-implicit-iv-01.txt

Abstract

IPsec ESP with AES-CBC, AES-CTR, AES-CCM or AES-GCM sends an IV in each IP packet, which represents 8 or 16 additional bytes. In some context, such as IoT, the cost of sending bytes over computing these bytes is generally in favor of the computation. As a result, it would be better to compute the IV on each party then to send it. The document describes how to the IV can be generated instead of being sent. This document limits the IV generation for AES-CBC, AES- CTR, AES-CCM and AES-GCM but can be used for additional cryptographic mode and suites.

Authors

Daniel Migault (mglt.ietf@gmail.com)
Tobias Guggemos (tobias.guggemos@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)