[Top] [All Lists]

RE: Last Call: Cryptographic Message Syntax to Proposed Standard

2001-12-13 10:06:16

Two last call comments:


In section 5.3 the discussion of the signedAttrs field the following
sentence occurs "Each SignedAttribute in the SET MUST be DER encoded."
There are two problems with the statement.  First there is no
SignedAttribute field or structure.  Second, this statement does not
make sense.  It should either be "Each AttributeValue" or "The
SignedAttributes set MUST be DER encoded for tranmission as well as
signature processing." 

Working group straw poll at the IETF meeting prefered the second


In section 6.1 there is a discussion that CMS implemenations must accept
parameters as both NULL and absent for parsing.  There should be a
matching statement that CMS implementations SHOULD generate NULL
parameters.  [This could be absent as well, I don't currently have any
preference as to which option is chosen.]

Jim Schaad

-----Original Message-----
From: owner-ietf-smime(_at_)mail(_dot_)imc(_dot_)org 
[mailto:owner-ietf-smime(_at_)mail(_dot_)imc(_dot_)org] On Behalf Of The IESG
Sent: Thursday, November 08, 2001 2:46 PM
To: IETF-Announce:
Cc: ietf-smime(_at_)imc(_dot_)org
Subject: Last Call: Cryptographic Message Syntax to Proposed Standard

The IESG has received a request from the S/MIME Mail Security Working
Group to consider the following as Proposed Standards:

 o Cryptographic Message Syntax
 o Cryptographic Message Syntax (CMS) Algorithms

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg(_at_)ietf(_dot_)org or ietf(_at_)ietf(_dot_)org mailing lists by 
November 21, 2001.

Files can be obtained via

<Prev in Thread] Current Thread [Next in Thread>
  • RE: Last Call: Cryptographic Message Syntax to Proposed Standard, Jim Schaad <=