RE: Making AES a SHOULD in draft-ietf-smime-rfc2633bis?
"Blake Ramsdell" <blake@brutesquadlabs.com> Sun, 15 June 2003 01:06 UTC
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08884 for <smime-archive@lists.ietf.org>; Sat, 14 Jun 2003 21:06:50 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5F0igrb059729 for <ietf-smime-bks@above.proper.com>; Sat, 14 Jun 2003 17:44:42 -0700 (PDT) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5F0ifkX059728 for ietf-smime-bks; Sat, 14 Jun 2003 17:44:41 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from brutesquadlabs.com (gtec136-m.isomedia.com [207.115.67.136] (may be forged)) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5F0ifrb059710; Sat, 14 Jun 2003 17:44:41 -0700 (PDT) (envelope-from blake@brutesquadlabs.com)
Received: from DEXTER ([192.168.0.4]) by brutesquadlabs.com with ESMTP ; Sat, 14 Jun 2003 17:44:38 -0700
From: Blake Ramsdell <blake@brutesquadlabs.com>
To: 'Paul Hoffman / IMC' <phoffman@imc.org>, ietf-smime@imc.org
Subject: RE: Making AES a SHOULD in draft-ietf-smime-rfc2633bis?
Date: Sat, 14 Jun 2003 17:44:38 -0700
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAA3esnxoW6t0OGbmGL46MYoAEAAAAA@brutesquadlabs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <p05210611bb11105f6e4f@[63.202.92.152]>
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit
> -----Original Message----- > From: owner-ietf-smime@mail.imc.org > [mailto:owner-ietf-smime@mail.imc.org] On Behalf Of Paul Hoffman / IMC > Sent: Saturday, June 14, 2003 10:51 AM > To: ietf-smime@imc.org > Subject: Making AES a SHOULD in draft-ietf-smime-rfc2633bis? > > Do we want to add AES as a SHOULD in section 2.7? We have the > traditional TripleDES MUST and RC2-40 as SHOULD. That's looking > backwards (some might say "very backwards" for RC2-40). It might be > good to add a forwards-looking SHOULD, namely AES. > > How do others feel about this? I wouldn't cry if we did this. Does that help? Blake
- Making AES a SHOULD in draft-ietf-smime-rfc2633bi… Paul Hoffman / IMC
- RE: Making AES a SHOULD in draft-ietf-smime-rfc26… Blake Ramsdell