IETF Logo Mail Archive

Re: WG LAST CALL: draft-ietf-smime-rfc2633bis-07.txt

Russ Housley <housley@vigilsec.com> Tue, 02 March 2004 01:14 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 UAA18436 for <smime-archive@lists.ietf.org>; Mon, 1 Mar 2004 20:14:13 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.8) with ESMTP id i220u62J061928; Mon, 1 Mar 2004 16:56:06 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i220u6te061927; Mon, 1 Mar 2004 16:56:06 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [144.202.240.3]) by above.proper.com (8.12.11/8.12.8) with SMTP id i220u5ts061921 for <ietf-smime@imc.org>; Mon, 1 Mar 2004 16:56:05 -0800 (PST) (envelope-from housley@vigilsec.com)
Received: (qmail 23464 invoked by uid 0); 2 Mar 2004 00:52:38 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (218.37.227.193) by woodstock.binhost.com with SMTP; 2 Mar 2004 00:52:38 -0000
Message-Id: <5.2.0.9.2.20040301194955.02017f78@mail.binhost.com>
X-Sender: housley@mail.binhost.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 01 Mar 2004 19:56:05 -0500
To: "Sean P. Turner" <turners@ieca.com>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: WG LAST CALL: draft-ietf-smime-rfc2633bis-07.txt
Cc: Blake Ramsdell <blake@brutesquadlabs.com>, ietf-smime@imc.org
In-Reply-To: <40449AEB.8060109@ieca.com>
References: <5.2.0.9.2.20040229235313.01f8f318@mail.binhost.com> <5.2.0.9.2.20040229235313.01f8f318@mail.binhost.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

Sean:

>For #4 ZLIB compression algorithm from RFC1950/1951 is a MUST in the 
>RFC3274 do we need to say it again here?

Yes.  The decision of the S/MIME WG more than a year ago was to put all of 
the mandatory to implement algorithms in this document.  In this case, we 
need to say:

      If an implementation chooses to support compression, then
      the implementation MUST support the ZLIB compression
      algorithm.

Russ

v2.23.0 | Report a Bug | By Email