Re: [IPsec] review of draft-ietf-ipsecme-aes-ctr-ikev2-02
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [IPsec] review of draft-ietf-ipsecme-aes-ctr-ikev2-02



Sean Shen wrote:

>> ...
>>
> [Sean] The IKEv2 requirement in the draft is only about key lengths.
> I never pretended that the AES standard allows arbitary conbinations
> of key lengths and rounds.
> I checked the document again and noticed that in the second paragraph
> of section 2:
> "... The choices of Key Size, Rounds and Block Size are defined as
>   following which are compatible with [RFC3686]."

That was one of my initial complaints ...

> If this sentense misleads readers to think that users can choose all
> conbinations, I will rewrite it as:
>  "... The choices of Key Size are defined as following which are
>   compatible with [RFC3686]."

... and that's essentially what I had proposed for that paragraph.

And yes, since that's written in the overview of Section 2, which
lays out the skeleton of the remainder of the section, the immediate
consequence of this change should be to drop sections 2.2 and 2.3
as well, as explained in my original review.
(To recall: The argument presented there was that, after dropping
inappropriate text, the remaining text in 2.2 & 2.3 would be a
simple -- yet verbose -- restatement of the first paragraph of
Section 2, and hence redundant anyway.)

Bingo!  We are converging.  Thanks.

> Best Regards,
>
> Sean

Kind regards,
  Alfred.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah at TR-Sys.de                     |
+------------------------+--------------------------------------------+


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.