--- 1/draft-ietf-ipsecme-esp-ah-reqts-09.txt 2014-05-16 15:14:20.369661759 -0700 +++ 2/draft-ietf-ipsecme-esp-ah-reqts-10.txt 2014-05-16 15:14:20.393662343 -0700 @@ -1,20 +1,20 @@ Network Working Group D. McGrew Internet-Draft Cisco Systems Obsoletes: 4835 (if approved) P. Hoffman Intended status: Standards Track VPN Consortium Expires: November 17, 2014 May 16, 2014 Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH) - draft-ietf-ipsecme-esp-ah-reqts-09 + draft-ietf-ipsecme-esp-ah-reqts-10 Abstract This Internet Draft is a standards track proposal to update 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 make use of various cryptographic algorithms to @@ -71,23 +71,23 @@ 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 from RFC 4835 . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . 7 + 5. Algorithm Diversity . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction The Encapsulating Security Payload (ESP) [RFC4303] and the Authentication Header (AH) [RFC4302] are the mechanisms for applying @@ -192,20 +192,22 @@ the encryption from Section 2.2, the requirement for NULL encryption is truly "MAY"; see Section 3 for more detail. 2.4. AH Authentication Algorithms The requirements for AH are the same as for ESP Authentication Algorithms, except that NULL authentication is inapplicable. 2.5. Summary of Changes from RFC 4835 + The following is a summary of the changes from RFC 4835. + Old New Requirement Requirement Algorithm (notes) ---- ----------- ----------------- MAY SHOULD+ AES-GCM with a 16 octet ICV [RFC4106] MAY SHOULD+ AES-GMAC with AES-128 [RFC4543] MUST- MAY TripleDES-CBC [RFC2451] SHOULD NOT MUST NOT DES-CBC [RFC2405] SHOULD+ SHOULD AES-XCBC-MAC-96 [RFC3566] SHOULD MAY AES-CTR [RFC3686]