The IESG | 6 Feb 2006 23:00
Picon
Favicon

Protocol Action: 'Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94 and GOST R 34.10-2001 algorithms with the Cryptographic Message Syntax (CMS)' to Proposed Standard


The IESG has approved the following document:

- 'Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94 and GOST R 
   34.10-2001 algorithms with the Cryptographic Message Syntax (CMS) '
   <draft-ietf-smime-gost-07.txt> as a Proposed Standard

This document is the product of the S/MIME Mail Security Working Group. 

The IESG contact persons are Russ Housley and Sam Hartman.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-smime-gost-07.txt

Technical Summary

  This Internet Draft describes the conventions for using GOST (Russian
  national standard) set of symmetric cryptographic algorithms
  (signature, key management, and MAC) and their use with Cryptographic
  Message Syntax (CMS).  Object identifiers for algorithms, ASN.1 for
  parameters, and example encoded CMS messages are provided.

  Additional documents related to this Internet-Draft are:
     draft-popov-cryptopro-cpalgs-04.txt
     draft-ietf-pkix-gost-cppk-03.txt

Working Group Summary

  There was little list discussion of the Internet-Draft; however, there
  was working group member review provided primarily face-to-face
(Continue reading)

Blake Ramsdell | 2 Mar 2006 10:44
Favicon

Re: Multi-level CMS Signature evaluation Rules: Document Location


On Jan 13, 2006, at 8:52 AM, Russ Housley wrote:
> This has lead to very little discussion.  I am pleased to propose  
> the text for CMS if that is the direction that the S/MIME WG wants  
> to pursue.  Please pick a direction.  We need to get moving.

OK, well I guess I'm picking it. Russ, please propose some text for  
this in CMS, per Jim's option 1 below. The path here seems to be  
reopening CMS for the purpose of adding this clarification.

Multiple signatures will be on the agenda for IETF 65.

> At 05:09 PM 12/4/2005, Jim Schaad wrote:
>>
>> 1) CMS Base specification
>>         Pro:
>>                 - This is core functionality and it would be seen  
>> by all
>> implementers of CMS
>>                 - It would deal with ALL CMS objects
>>
>>         Con:
>>                 - The document is not currently open for changes
>>                 - Depending on how it is written, it might be more  
>> open to
>> changes in the future

Blake
--
Blake Ramsdell | Sendmail, Inc. | http://www.sendmail.com
(Continue reading)

Russ Housley | 2 Mar 2006 20:02

Re: Multi-level CMS Signature evaluation Rules: Document Location


Blake:

I will propose text.  However, I am not in favor of opening CMS.  I 
think we can generate a one or two paragraph update.

Russ

At 04:44 AM 3/2/2006, Blake Ramsdell wrote:
>On Jan 13, 2006, at 8:52 AM, Russ Housley wrote:
>>This has lead to very little discussion.  I am pleased to propose
>>the text for CMS if that is the direction that the S/MIME WG wants
>>to pursue.  Please pick a direction.  We need to get moving.
>
>OK, well I guess I'm picking it. Russ, please propose some text for
>this in CMS, per Jim's option 1 below. The path here seems to be
>reopening CMS for the purpose of adding this clarification.
>
>Multiple signatures will be on the agenda for IETF 65.
>
>>At 05:09 PM 12/4/2005, Jim Schaad wrote:
>>>
>>>1) CMS Base specification
>>>         Pro:
>>>                 - This is core functionality and it would be seen
>>>by all
>>>implementers of CMS
>>>                 - It would deal with ALL CMS objects
>>>
>>>         Con:
(Continue reading)

Blake Ramsdell | 2 Mar 2006 20:44
Favicon

Re: Multi-level CMS Signature evaluation Rules: Document Location


On Mar 2, 2006, at 11:02 AM, Russ Housley wrote:
> I will propose text.  However, I am not in favor of opening CMS.  I  
> think we can generate a one or two paragraph update.

OK, I was overly specific about the mechanism. I think the sprit here  
is that this is going to be a CMS-level change so that any consumer  
of CMS will benefit from it. The actual form of that change is indeed  
whatever makes the "most sense".

Blake
--
Blake Ramsdell | Sendmail, Inc. | http://www.sendmail.com


Gmane