| < draft-ietf-ipsecme-implicit-iv-05.txt | draft-ietf-ipsecme-implicit-iv-06.txt > | |||
|---|---|---|---|---|
| IPSECME D. Migault | IPSECME D. Migault | |||
| Internet-Draft Ericsson | Internet-Draft Ericsson | |||
| Intended status: Standards Track T. Guggemos | Intended status: Standards Track T. Guggemos | |||
| Expires: December 28, 2018 LMU Munich | Expires: May 20, 2019 LMU Munich | |||
| Y. Nir | Y. Nir | |||
| Dell EMC | Dell EMC | |||
| June 26, 2018 | November 16, 2018 | |||
| Implicit IV for Counter-based Ciphers in Encapsulating Security Payload | Implicit IV for Counter-based Ciphers in Encapsulating Security Payload | |||
| (ESP) | (ESP) | |||
| draft-ietf-ipsecme-implicit-iv-05 | draft-ietf-ipsecme-implicit-iv-06 | |||
| Abstract | Abstract | |||
| Encapsulating Security Payload (ESP) sends an initialization vector | Encapsulating Security Payload (ESP) sends an initialization vector | |||
| (IV) or nonce in each packet. The size of IV depends on the applied | (IV) or nonce in each packet. The size of IV depends on the applied | |||
| transform, being usually 8 or 16 octets for the transforms defined by | transform, being usually 8 or 16 octets for the transforms defined by | |||
| the time this document is written. Some algorithms such as AES-GCM, | the time this document is written. Some algorithms such as AES-GCM, | |||
| AES-CCM, AES-CTR and ChaCha20-Poly1305 require a unique nonce but do | AES-CCM, AES-CTR and ChaCha20-Poly1305 require a unique nonce but do | |||
| not require an unpredictable nonce. When using such algorithms the | not require an unpredictable nonce. When using such algorithms the | |||
| packet counter value can be used to generate a nonce. This avoids | packet counter value can be used to generate a nonce. This avoids | |||
| skipping to change at page 1, line 43 ¶ | skipping to change at page 1, line 43 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on December 28, 2018. | This Internet-Draft will expire on May 20, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 7, line 19 ¶ | skipping to change at page 7, line 19 ¶ | |||
| DOI 10.17487/RFC8221, October 2017, | DOI 10.17487/RFC8221, October 2017, | |||
| <https://www.rfc-editor.org/info/rfc8221>. | <https://www.rfc-editor.org/info/rfc8221>. | |||
| 10.2. Informational References | 10.2. Informational References | |||
| [BEAST] Thai, T. and J. Juliano, "Here Come The xor Ninjas", , | [BEAST] Thai, T. and J. Juliano, "Here Come The xor Ninjas", , | |||
| May 2011, <https://www.researchgate.net/ | May 2011, <https://www.researchgate.net/ | |||
| publication/266529975_Here_Come_The_Ninjas>. | publication/266529975_Here_Come_The_Ninjas>. | |||
| [I-D.yeung-g-ikev2] | [I-D.yeung-g-ikev2] | |||
| Weis, B., Nir, Y., and V. Smyslov, "Group Key Management | Weis, B. and V. Smyslov, "Group Key Management using | |||
| using IKEv2", draft-yeung-g-ikev2-13 (work in progress), | IKEv2", draft-yeung-g-ikev2-14 (work in progress), July | |||
| March 2018. | 2018. | |||
| [IANA] "IANA IKEv2 Parameter - Type 1 - Encryption Algorithm | [IANA] "IANA IKEv2 Parameter - Type 1 - Encryption Algorithm | |||
| Transform IDs", <https://www.iana.org/assignments/ikev2- | Transform IDs", <https://www.iana.org/assignments/ikev2- | |||
| parameters/ikev2-parameters.xhtml#ikev2-parameters-5>. | parameters/ikev2-parameters.xhtml#ikev2-parameters-5>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Daniel Migault | Daniel Migault | |||
| Ericsson | Ericsson | |||
| 8275 Trans Canada Route | 8275 Trans Canada Route | |||
| End of changes. 5 change blocks. | ||||
| 7 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||