Re: Comments on draft-ietf-smime-cms-rsaes-oaep-01.txt
Russ Housley <housley@spyrus.com> Tue, 01 August 2000 21:26 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 RAA09286 for <smime-archive@odin.ietf.org>; Tue, 1 Aug 2000 17:26:24 -0400 (EDT)
Received: by ns.secondary.com (8.9.3/8.9.3) id NAA16811 for ietf-smime-bks; Tue, 1 Aug 2000 13:48:20 -0700 (PDT)
Received: from mail.spyrus.com (mail.spyrus.com [207.212.34.20]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id NAA16807 for <ietf-smime@imc.org>; Tue, 1 Aug 2000 13:48:19 -0700 (PDT)
Received: from rhousley_laptop (wireless-135-26.ietf.marconi.com [147.73.135.26]) by mail.spyrus.com (8.9.3/8.9.3) with ESMTP id NAA17112; Tue, 1 Aug 2000 13:50:51 -0700 (PDT)
Message-Id: <4.2.0.58.20000801164313.00ad77b0@mail.spyrus.com>
X-Sender: rhousley@mail.spyrus.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Tue, 01 Aug 2000 16:47:20 -0400
To: schaad@nwlink.com
From: Russ Housley <housley@spyrus.com>
Subject: Re: Comments on draft-ietf-smime-cms-rsaes-oaep-01.txt
Cc: ietf-smime@imc.org
In-Reply-To: <000001bffa69$4ef5b9a0$b2844993@revelation>
References: <200006221227.IAA27600@ietf.org>
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>
Jim: >Section 1 Paragraph 4: Spelling error on interactibe. Fixed. >Section 2 Paragraph 2: Remove last instance of "[CMS]" as it is not >necessary. Agree. >Section 2.1 Paragraph 3: Delete or reword this paragraph as it is not >correct. originatorInfo may be present due to other recipient infos. Agree. The originatorInfo may be present if some other recipient is using a different key management protocol. >Section 3 Paragraph 5 (maskGenFunc): MFG1 should be changed to MFG1SHA1 or >all references to it using SHA1 should be replaced with references to it >using a OWF. > >Section 3 Paragraph 5: Is SHA1 to be the one and only OWF supported here or >are others permitted. Text is not clear on this issue. Okay. >Section 3 Paragaraph 5 and 6: Why are you requiring that incorrectly >encoded (i.e. the default value is supplied) be recognized? "... recognize >both id-sha1 and absent..." This was done for alignment with PKCS#1 v2.0. >Section 4 Paragraph 1: Spelling error "SEQUNCEs" Fixed. >Please add ASN module to the end. (I am just lazy.) Will do. Either this draft will be folded into an algorithms document, or I will add a module here. Russ
- I-D ACTION:draft-ietf-smime-cms-rsaes-oaep-01.txt Internet-Drafts
- Comments on draft-ietf-smime-cms-rsaes-oaep-01.txt jimsch
- Re: Comments on draft-ietf-smime-cms-rsaes-oaep-0… Russ Housley