Implicit IV for Counter-based Ciphers in IPsec
draft-mglt-ipsecme-implicit-iv-04
Document | Type |
Replaced Internet-Draft
(ipsecme WG)
Expired & archived
|
|
---|---|---|---|
Authors | Daniel Migault , Tobias Guggemos , Yoav Nir | ||
Last updated | 2017-11-11 (Latest revision 2017-06-21) | ||
Replaced by | draft-ietf-ipsecme-implicit-iv | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | In WG Last Call | |
Document shepherd | David Waltermire | ||
IESG | IESG state | Replaced by draft-ietf-ipsecme-implicit-iv | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | David Waltermire <david.waltermire@nist.gov> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Daniel Migault
Tobias Guggemos
Yoav Nir
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)