draft-ietf-ipsecme-aes-ctr-ikev2-03.txt   draft-ietf-ipsecme-aes-ctr-ikev2-04.txt 
IPSECME S. Shen IPSECME S. Shen
Internet-Draft Huawei Internet-Draft Huawei
Updates: RFC4307 Y. Mao Updates: RFC4307 Y. Mao
(if approved) H3C (if approved) H3C
Expires: May 28, 2010 NSS. Murthy Intended status: Standards Track NSS. Murthy
Freescale Semiconductor Expires: June 7, 2010 Freescale Semiconductor
November 24, 2009 December 4, 2009
Using Advanced Encryption Standard (AES) Counter Mode with IKEv2 Using Advanced Encryption Standard (AES) Counter Mode with IKEv2
draft-ietf-ipsecme-aes-ctr-ikev2-03 draft-ietf-ipsecme-aes-ctr-ikev2-04
Abstract Abstract
This document describes the usage of Advanced Encryption Standard This document describes the usage of Advanced Encryption Standard
Counter Mode (AES-CTR), with an explicit initialization vector, by Counter Mode (AES-CTR), with an explicit initialization vector, by
IKEv2 for encrypting the IKEv2 exchanges that follow the IKE_SA_INIT IKEv2 for encrypting the IKEv2 exchanges that follow the IKE_SA_INIT
exchange. exchange.
Status of this Memo Status of this Memo
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 28, 2010. This Internet-Draft will expire on June 7, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 2, line 33 skipping to change at page 2, line 33
5. IKEv2 Conventions . . . . . . . . . . . . . . . . . . . . . . 10 5. IKEv2 Conventions . . . . . . . . . . . . . . . . . . . . . . 10
5.1. Keying Material and Nonces . . . . . . . . . . . . . . . . 10 5.1. Keying Material and Nonces . . . . . . . . . . . . . . . . 10
5.2. Encryption identifier . . . . . . . . . . . . . . . . . . 11 5.2. Encryption identifier . . . . . . . . . . . . . . . . . . 11
5.3. Key Length Attribute . . . . . . . . . . . . . . . . . . . 11 5.3. Key Length Attribute . . . . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
IKEv2 [RFC4306] is a component of IPsec used for performing mutual IKEv2 [RFC4306] is a component of IPsec used for performing mutual
authentication and establishing and maintaining security associations authentication and establishing and maintaining security associations
(SAs). [RFC4307] defines the set of algorithms that are mandatory to (SAs). [RFC4307] defines the set of algorithms that are mandatory to
implement as part of IKEv2, as well as algorithms that should be implement as part of IKEv2, as well as algorithms that should be
implemented because they may be promoted to mandatory at some future implemented because they may be promoted to mandatory at some future
time. [RFC4307] requires that an implementation "SHOULD" support time. [RFC4307] requires that an implementation "SHOULD" support
Advanced Encryption Standard [AES] in Counter Mode [MODES] (AES-CTR) Advanced Encryption Standard [AES] in Counter Mode [MODES] (AES-CTR)
skipping to change at page 10, line 21 skipping to change at page 10, line 21
are also defined. are also defined.
AES supports three key sizes: 128 bits, 192 bits, and 256 bits. All AES supports three key sizes: 128 bits, 192 bits, and 256 bits. All
IKEv2 implementations that implement AES-CTR MUST support the 128-bit IKEv2 implementations that implement AES-CTR MUST support the 128-bit
key size. An IKEv2 implementation MAY support key sizes of 192 and key size. An IKEv2 implementation MAY support key sizes of 192 and
256 bits. 256 bits.
5.1. Keying Material and Nonces 5.1. Keying Material and Nonces
IKEv2 can be used to establish fresh keys and nonces, as the same IKEv2 can be used to establish fresh keys and nonces, as the same
combination of IV and encryption key values MUST not be reused when combination of IV and encryption key values MUST NOT be reused when
the AES-CTR algorithm is used for encryption. This section describes the AES-CTR algorithm is used for encryption. This section describes
the conventions for generating an unpredictable and secret Nonce and the conventions for generating an unpredictable and secret Nonce and
an encryption key of required lengths using IKEv2. an encryption key of required lengths using IKEv2.
IKEv2 negotiates four cryptographic algorithms with its peer using IKEv2 negotiates four cryptographic algorithms with its peer using
the IKE_SA_INIT exchange. They include an encryption algorithm and a the IKE_SA_INIT exchange. They include an encryption algorithm and a
pseudo-random function (PRF). All the payloads of IKEv2 messages pseudo-random function (PRF). All the payloads of IKEv2 messages
that follow the IKE_SA_INIT exchange are encrypted using the that follow the IKE_SA_INIT exchange are encrypted using the
negotiated encryption algorithm. The PRF is used to generate the negotiated encryption algorithm. The PRF is used to generate the
keying material required for the encryption algorithm. keying material required for the encryption algorithm.
skipping to change at page 15, line 39 skipping to change at page 15, line 39
publications/nistpubs/800-38a/sp800-38a.pdf>. publications/nistpubs/800-38a/sp800-38a.pdf>.
9.2. Informative References 9.2. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 within [RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 within
ESP and AH", RFC 2404, November 1998. ESP and AH", RFC 2404, November 1998.
[RFC2409] Harkins, D. and D. Carrel, "The Internet Key Exchange
(IKE)", RFC 2409, November 1998.
[RFC3686] Housley, R., "Using Advanced Encryption Standard (AES) [RFC3686] Housley, R., "Using Advanced Encryption Standard (AES)
Counter Mode With IPsec Encapsulating Security Payload Counter Mode With IPsec Encapsulating Security Payload
(ESP)", RFC 3686, January 2004. (ESP)", RFC 3686, January 2004.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, December 2005. RFC 4303, December 2005.
[Recommendations] [Recommendations]
Barker, E., Barker, W., Burr, W., Polk, W., and M. Smid, Barker, E., Barker, W., Burr, W., Polk, W., and M. Smid,
"Recommendation for Key Management - Part1 - General "Recommendation for Key Management - Part1 - General
 End of changes. 6 change blocks. 
10 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.37b. The latest version is available from http://tools.ietf.org/tools/rfcdiff/