Hi, IPSECME WG,
The 01 version of draft-ietf-ipsecme-aes-ctr-ike was uploaded. The
modification addressed comments we received so far and also include some
other editing.
Your comments will be appreciated. 

Regard,

Sean

> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the IP Security Maintenance and 
> Extensions Working Group of the IETF.
> 
> 
>       Title           : Using Advanced Encryption Standard 
> (AES) Counter Mode with IKEv2
>       Author(s)       : S. Shen, et al.
>       Filename        : draft-ietf-ipsecme-aes-ctr-ikev2-01.txt
>       Pages           : 17
>       Date            : 2009-08-17
> 
> This document describes the usage of Advanced Encryption 
> Standard Counter Mode (AES_CTR), with an explicit 
> initialization vector, by
> IKEv2 for encrypting the IKEv2 exchanges that follow the 
> IKE_SA_INIT exchange.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipsecme-aes-ctr
> -ikev2-01.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail 
> reader implementation to automatically retrieve the ASCII 
> version of the Internet-Draft.

Major changes are as following:
#1.
Section 2
Rearranged sentences at the beginning of section 2 to simplify and clarify
AES and AES_CTR.  

#2
Section 2.1
Detailed description of counter mode was cited from corresponding section of
rfc3686

#3
Section 2.2: 
old:     All IKEv2 implementations MUST support the 128 key size.  
new:     All  IKEv2 implementations that implement AES-CTR MUST support the
128 key size.
Because AES-CTR is a "SHOULD" requirement for IKEv2.  

#4
Section 3.2
Added clear reference to rfc4302 and rfc4307 for integrity requirement and
algorithm choice.

#5
Section 4
Rewrote second paragraph in section 4 to clarify the role of Counter Block.
The Counter Block is same as that defined by rfc3686. 

#6
Section 4
Keep the Counter Block description in the same style as in rfc3686




<<< Message/External-body; name=draft-ietf-ipsecme-aes-ctr-ikev2-01.txt: Unrecognized >>>
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to