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 dire
Sean Shen writes:
> 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.
> Major changes are as following:
> #4
> Section 3.2
> Added clear reference to rfc4302 and rfc4307 fo
Hi, Tero,
Thanks for the comments. Please check in lines:
> Sean Shen writes:
> > 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.
> > Major changes are as follow
etf.org [mailto:ipsec-boun...@ietf.org] On Behalf Of
> Sean Shen
> Sent: Wednesday, August 19, 2009 4:46
> To: 'Tero Kivinen'
> Cc: ipsec@ietf.org
> Subject: Re: [IPsec] FW: I-D Action:draft-ietf-ipsecme-aes-ctr-ikev2-
> 01.txt
>
> Hi, Tero,
> Thanks for the comments. Pl
Sean Shen writes:
> The point here is to say that integrity protection is needed with aes-ctr,
> not trying to specify which integrity algorithm to choose. rfc4306 already
> required integrity for ikev2 and we refered to 4306 here. The choice of
> integrity algorithm is up to rfc4307 or some update
> > The point here is to say that integrity protection is needed with
> > aes-ctr, not trying to specify which integrity algorithm to choose.
> > rfc4306 already required integrity for ikev2 and we refered to 4306
> > here. The choice of integrity algorithm is up to rfc4307 or some
> > update
