[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What is the standardization status of AES in IPSec?
Well, since FIPS-197 says that one of the three key lengths MUST be
supported, and that the other two SHOULD be supported, it's probably a good
idea to follow that lead, and choose a single key size that must be
supported, and the keep the others optional.
"Scott Fanning"
<sfanning@cisco.com To: "Andrew Wenlang Zhu" <Andrew_zhu@hp.com>,
> <ipsec@lists.tislabs.com>
Sent by: cc:
owner-ipsec@lists.t Subject: Re: What is the standardization status of AES in IPSec?
islabs.com
02/01/02 02:59 PM
and on that note.. If AES is the MUST implement algorithm, does that
include
all key sizes?
Scott
----- Original Message -----
From: "Andrew Wenlang Zhu" <Andrew_zhu@hp.com>
To: <ipsec@lists.tislabs.com>
Sent: Friday, February 01, 2002 11:45 AM
Subject: What is the standardization status of AES in IPSec?
> Hello:
>
> Can any one give me an update on the standardization status of using AES
in
> IPSec?
>
> I am reading "The AES Cipher Algorithm and Its Use With IPsec"
> <draft-ietf-ipsec-ciph-aes-cbc-03.txt> and read " Once NIST has published
> the AES FIPS ... AES should become a default and mandatory-to-implement
> cipher algorithm for IPSec".
>
> FIPS-197 was out in Nov-2001. When an IPSec/AES RFC is expected to come
out?
>
> Thanks,
> ---------------------------------------
> Andrew Zhu
> HP Systems Networking Solution Lab
> IP Security & System Firewall Project
> Andrew_zhu@hp.com
>
>