IETF Logo Mail Archive

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

"Sean P. Turner" <turners@ieca.com> Tue, 02 March 2004 00:57 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 TAA17336 for <smime-archive@lists.ietf.org>; Mon, 1 Mar 2004 19:57:52 -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 i220XYAc060155; Mon, 1 Mar 2004 16:33:34 -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 i220XYVO060154; Mon, 1 Mar 2004 16:33:34 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from smtp003.bizmail.yahoo.com (smtp003.bizmail.yahoo.com [216.136.130.195]) by above.proper.com (8.12.11/8.12.8) with SMTP id i220XV8j060145 for <ietf-smime@imc.org>; Mon, 1 Mar 2004 16:33:33 -0800 (PST) (envelope-from turners@ieca.com)
Received: from unknown (HELO ieca.com) (turners@ieca.com@218.37.226.73 with plain) by smtp003.bizmail.yahoo.com with SMTP; 2 Mar 2004 00:33:36 -0000
Message-ID: <40449AEB.8060109@ieca.com>
Date: Tue, 02 Mar 2004 09:32:11 -0500
From: "Sean P. Turner" <turners@ieca.com>
Organization: IECA, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
CC: Blake Ramsdell <blake@brutesquadlabs.com>, ietf-smime@imc.org
Subject: Re: WG LAST CALL: draft-ietf-smime-rfc2633bis-07.txt
References: <5.2.0.9.2.20040229235313.01f8f318@mail.binhost.com>
In-Reply-To: <5.2.0.9.2.20040229235313.01f8f318@mail.binhost.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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

Russ,

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

spt

Russ Housley wrote:

>
> Hare are seven comments.  I think number 6 is the most significant 
> one, but none of them are show stoppers.
>
> 1.  Should Section 1.4 reference RFC 3369?
>
> 2.  Delete section 1.6 before the document is sent to the IESG.
>
> 3.  Section 2.4 probably should point out that ContentInfo is needed 
> to encapsulate each of the protection content types.
>
> 4.  What compression algorithm MUST be implemented if CompressedData 
> is supported?
>
> 5.  Section 2.5.2: s/SMIMECapabilities attribute 
> should/SMIMECapabilities attribute SHOULD/
>
> 6.  Section 2.6:  the first two paragraphs are not clear.  S/MIME v3.1 
> MUST support both issuerAndSerialNumber and subjectKeyIdentifier for 
> sending and receiving.
>
> 7.  Section 3.4.3.2: s/not currently supported in S/MIME/not currently 
> recommended in S/MIME/
>
> Russ
>

v2.23.0 | Report a Bug | By Email