Re: What is the standardization status of AES in IPSec?

"Hilarie Orman, Purple Streak Development" <hilarie@xmission.com> Mon, 04 February 2002 20:37 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g14KbW311520; Mon, 4 Feb 2002 12:37:32 -0800 (PST)
Received: by lists.tislabs.com (8.9.1/8.9.1) id OAA00987 Mon, 4 Feb 2002 14:43:07 -0500 (EST)
From: "Hilarie Orman, Purple Streak Development" <hilarie@xmission.com>
To: jari.arkko@kolumbus.fi
Cc: ipsec@lists.tislabs.com
In-reply-to: Yourmessage <02bd01c1ac7d$f73c53e0$8a1b6e0a@arenanet.fi>
Subject: Re: What is the standardization status of AES in IPSec?
Message-Id: <E16XpBj-0006tO-00@xmission.xmission.com>
Date: Mon, 04 Feb 2002 12:54:03 -0700
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

I think you are asking for key exchange groups that match the
*maximum* strength of each AES key.  But can you say why that is that
actually necessary, at this time?

As for explaining strength issues, there's
draft-orman-public-key-lengths-05.txt.

Hilarie

>  > I'm curious as to how many people believe that a MUST for a 128-bit AES
>  > key means a MUST for 128 bits of entropy in the key.

>  I don't. While I believe we should move to AES as soon as possible, I
>  don't necessarily believe in the statement that all components of the
>  protocol set must be equally strong; you should be able to take advantage
>  of a new good algorithm even if you can't for e.g. computational reasons
>  increase Diffie-Hellman key lengths quite as much.

>  Thus, I believe we should standardize groups matching AES strength,
>  but not make them mandatory. And we need to explain the strength
>  issues somewhere.

>  Jari