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 everyone,
As a general comment, this document got me thinking whether pseudo-code can
be made amenable to some minimal level of validation. For example, there is
so much code here that I could never be sure that all "goto"s are
referencing valid labels. If any member of this list is a aware
Works for me!
Thanks,
- Ken
>-Original Message-
>From: ipsec-boun...@ietf.org [mailto:ipsec-boun...@ietf.org] On Behalf
>Of Yaron Sheffer
>Sent: Tuesday, August 11, 2009 6:04 AM
>To: ipsec@ietf.org
>Subject: [IPsec] Relating the two ESP-null documents
>
>Hi,
>
>As we near publication o
Works for me too!
Cheers, Manav
> -Original Message-
> From: ipsec-boun...@ietf.org [mailto:ipsec-boun...@ietf.org]
> On Behalf Of Grewal, Ken
> Sent: Tuesday, August 18, 2009 10.03 PM
> To: Yaron Sheffer; ipsec@ietf.org
> Subject: Re: [IPsec] Relating the two ESP-null documents
>
> Wo
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