[Top] [All Lists]

RE: I-D ACTION:draft-ietf-smime-rfc3369bis-00.txt

2004-03-16 18:49:58

Steve is correct.  The change was made by adding the OtherCertFormat data
type to section 10.2.2.

However I think that it is easier for people to find if the section number
is included in the changes section.


-----Original Message-----
From: owner-ietf-smime(_at_)mail(_dot_)imc(_dot_)org 
On Behalf Of Dr Stephen Henson
Sent: Tuesday, March 16, 2004 5:19 PM
To: Paul Hoffman / IMC
Cc: ietf-smime(_at_)imc(_dot_)org
Subject: Re: I-D ACTION:draft-ietf-smime-rfc3369bis-00.txt

Paul Hoffman / IMC wrote:

At 4:58 PM -0500 3/16/04, Russ Housley wrote:


Yes, we are making another round of updates to CMS.  I expect them to 
be very minor.  The changes are described in Section 1.2, which says:

   This document obsoletes RFC 3369 [CMS2].  As discussed above, RFC
   3369 introduced an extension mechanism to support new key management
   schemes without further changes to the CMS.  This document introduces
   a similar extension mechanism to support additional certificate
   formats for the verification of digital signatures without further
   changes to the CMS.  Backward compatibility with both RFC 2630 and
   RFC 3369 is preserved.

Maybe I'm being blind, but *where* is that extension mechanism 
introduced in the new document? Listing it explicitly in this 
introductory material would help the reader (or at least me...).

Presumably the CertificateChoices type mentioned in 10.2.2 and its use in


Dr Stephen N. Henson.
Core developer of the   OpenSSL project:
Freelance consultant see:
Email: shenson(_at_)drh-consultancy(_dot_)co(_dot_)uk, PGP key: via homepage.