RE: Correct definition of ContentInfo in CMS-10
William Ottaway <w.ottaway@eris.dera.gov.uk> Wed, 24 February 1999 14:03 UTC
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id GAA14940 for ietf-smime-bks; Wed, 24 Feb 1999 06:03:33 -0800 (PST)
Received: from ns0.eris.dera.gov.uk (ns0.eris.dera.gov.uk [128.98.1.1]) by mail.proper.com (8.8.8/8.8.5) with SMTP id GAA14936 for <ietf-smime@imc.org>; Wed, 24 Feb 1999 06:03:31 -0800 (PST)
Received: (qmail 19326 invoked from network); 24 Feb 1999 14:08:21 -0000
Received: from unknown (HELO mail-relay.eris.dera.gov.uk) (128.98.2.7) by ns0.eris.dera.gov.uk with SMTP; 24 Feb 1999 14:08:21 -0000
Received: (qmail 23891 invoked from network); 24 Feb 1999 14:08:21 -0000
Received: from wottoway.eris.dera.gov.uk (HELO wottaway.eris.dera.gov.uk) (128.98.10.17) by mail-relay.eris.dera.gov.uk with SMTP; 24 Feb 1999 14:08:21 -0000
Received: by localhost with Microsoft MAPI; Wed, 24 Feb 1999 14:08:38 -0000
Message-ID: <01BE5FFF.2C9F7720.w.ottaway@eris.dera.gov.uk>
From: William Ottaway <w.ottaway@eris.dera.gov.uk>
To: 'Russ Housley' <housley@spyrus.com>
Cc: "'ietf-smime@imc.org'" <ietf-smime@imc.org>
Subject: RE: Correct definition of ContentInfo in CMS-10
Date: Wed, 24 Feb 1999 14:08:36 -0000
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-smime@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Russ: To draw this thread to a close, the content within ContentInfo is not optional. Therefore, the ASN.1 in the appendix to CMS defining ContentInfo needs to have optional removed.. Bill. -----Original Message----- From: Russ Housley [SMTP:housley@spyrus.com] Sent: Wednesday, February 24, 1999 12:08 PM To: Bonatti, Chris Cc: SMIME Subject: RE: Correct definition of ContentInfo in CMS-10 Chris: In PKCS#7 v1.5, ContentInfo was used as the outer wrapper (around SignedData, EnvelopedData, etc) as well as the wrapper around the content being protected. In CMS, two different ASN.1 types are used for the two different wrappers. ContentInfo remains the outer wrapper. There is no need for such a wrapper without a protecting content such as SignedData, EnvelopedData, etc., therefore the ContentInfo content should not be optional. The EncapsulatedContentInfo is the wrapper for the content being protected. To support a SignedData for distribution of certificates and CRLs without any content (this approach is used in many products for certificate user enrollment), EncapsulatedContentInfo has an OPTIONAL content. Russ -----Original Message----- From: owner-ietf-smime@imc.org [mailto:owner-ietf-smime@imc.org] On Behalf Of Bonatti, Chris Sent: Monday, February 22, 1999 9:42 AM To: William Ottaway; 'ietf-smime@imc.org'; Russ Housley Subject: Re: Correct definition of ContentInfo in CMS-10 I would submit that the 'content' field in the General Syntax section is correct. The instance of OPTIONAL in the appendix must be a copy artifact from the 'EncapsulatedContentInfo', in which the 'content' field is correctly optional. I can see no legitimate use of CMS in which you would send only a 'contentType' OID. Even if someone were sending a "detached content" in a separate body part, either MIME or X.400 mail systems are perfectly capable of attaching a content types for that information without utilizing this structure. Russ, Browsing through my historical archive of now "non-existent" I-Ds, I see that the OPTIONAL tag seems to have fallen out of the General Syntax starting in version 3 of CMS. Do you remember the reasoning behind the change? Chris --------------------------------------------------------------- | International Electronic Communication Analysts, Inc. | | Christopher D. Bonatti 15309 Turkey Foot Road | | Principal Engineer Darnestown, Md 20878-3640 | | bonattic@ieca.com Tel: 301-208-2349 Fax: 301-208-2379 | --------------------------------------------------------------- ____________________ William Ottaway wrote: > Within the body of CMS 10 ContentInfo is defined as : - > > ContentInfo ::= SEQUENCE { > contentType ContentType, > content [0] EXPLICIT ANY DEFINED BY contentType } > > However, in the appendix ContentInfo is defined as : - > > ContentInfo ::= SEQUENCE { > contentType ContentType, > content [0] EXPLICIT ANY DEFINED BY contentType OPTIONAL } > > I assume the one within the body (i.e. content not optional) is correct. > > Bill. > > "The Information contained in this E-Mail and any subsequent > correspondence is private and is intended solely for the intended > recipient(s). For those other than the intended recipient any > disclosure, copying, distribution, or any action taken or omitted to > be taken in reliance on such information is prohibited and may be > unlawful." > ____________________________________________________ > William Ottaway BSc Hons CEng MBCS, > L323, Tel: +44 (0) 1684 894079 > DERA Malvern, Fax: +44 (0) 1684 896113 > St. Andrews Road, email: w.ottaway@eris.dera.gov.uk > Malvern, > Worcs, > WR14 3PS > > All opinions are my own.
- Correct definition of ContentInfo in CMS-10 William Ottaway
- Re: Correct definition of ContentInfo in CMS-10 Bonatti, Chris
- RE: Correct definition of ContentInfo in CMS-10 Russ Housley
- Re: Correct definition of ContentInfo in CMS-10 Brian Korver
- Re: Correct definition of ContentInfo in CMS-10 Russ Housley
- Re: Correct definition of ContentInfo in CMS-10 Ross demon
- Re: Correct definition of ContentInfo in CMS-10 John Ross
- RE: Correct definition of ContentInfo in CMS-10 Darren Harter
- RE: Correct definition of ContentInfo in CMS-10 William Ottaway
- Re: Correct definition of ContentInfo in CMS-10 Peter Gutmann
- Re: Correct definition of ContentInfo in CMS-10 Russ Housley
- Re: Correct definition of ContentInfo in CMS-10 Ross demon