RE: LAST CALL: draft-ietf-smime-cast-128-01.txt
"Jim Schaad" <jimsch@nwlink.com> Mon, 27 March 2000 07:33 UTC
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12716 for <smime-archive@odin.ietf.org>; Mon, 27 Mar 2000 02:33:47 -0500 (EST)
Received: by ns.secondary.com (8.9.3/8.9.3) id WAA23065 for ietf-smime-bks; Sun, 26 Mar 2000 22:59:27 -0800 (PST)
Received: from mail.iagu.net (ns.iagu.net [203.32.153.69]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA23060 for <ietf-smime@imc.org>; Sun, 26 Mar 2000 22:59:24 -0800 (PST)
Received: from dhcp-32-60.ietf.connect.com.au [169.208.32.60] by mail.iagu.net (8.8.5/AndrewR-19990125) with SMTP id QAA32577 return <jimsch@nwlink.com>; Mon, 27 Mar 2000 16:31:35 +0930 (CST)
From: Jim Schaad <jimsch@nwlink.com>
To: ietf-smime@imc.org
Cc: Carlisle Adams <carlisle.adams@entrust.com>
Subject: RE: LAST CALL: draft-ietf-smime-cast-128-01.txt
Date: Mon, 27 Mar 2000 16:31:06 +0930
Message-ID: <NDBBJGDMMGBPBDENLEIHEEIOCAAA.jimsch@nwlink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <4.2.0.58.20000309113750.00a61330@mail.spyrus.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
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
I have the following comments on the draft at this stage. I am sorry for being late, but I have been on holidays. 1. In section 3 paragraph 1 -- The size needs to be required for an SMimeCapablity and cannot be MAY. We do binary comparisions to see if the algorithms are the same so there can be no MAY fields. 2. In section 3 -- Again I ask that you include the actual list of bytes that are to be used for the SMimeCaps fields. For an example of what I am looking for you can look at section 7 of CMSKEA. Due to the fact that a binary comparision is being done, it is best to allow for no errors in the encoding of this field. Jim Schaad
- LAST CALL: draft-ietf-smime-cast-128-01.txt Russ Housley
- RE: LAST CALL: draft-ietf-smime-cast-128-01.txt Jim Schaad