ietf-smime
[Top] [All Lists]

RFC 4490 on Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)

2006-05-22 15:48:13


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4490

        Title:      Using the GOST 28147-89, GOST 
                    R 34.11-94, GOST R 34.10-94, and 
                    GOST R 34.10-2001 Algorithms with Cryptographic 
                    Message Syntax (CMS) 
        Author:     S. Leontiev, Ed.,
                    G. Chudov, Ed.
        Status:     Standards Track
        Date:       May 2006
        Mailbox:    lse(_at_)cryptopro(_dot_)ru, 
                    chudov(_at_)cryptopro(_dot_)ru
        Pages:      29
        Characters: 54912
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-smime-gost-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4490.txt

This document describes the conventions for using the cryptographic
algorithms GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and
GOST R 34.11-94 with the Cryptographic Message Syntax (CMS).  The
CMS is used for digital signature, digest, authentication, and encryption
of arbitrary message contents.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST(_at_)IETF(_dot_)ORG(_dot_)  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST(_at_)RFC-EDITOR(_dot_)ORG(_dot_)

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info(_at_)RFC-EDITOR(_dot_)ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info(_at_)RFC-EDITOR(_dot_)ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to 
RFC-Manager(_at_)RFC-EDITOR(_dot_)ORG(_dot_)  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR(_at_)RFC-EDITOR(_dot_)ORG(_dot_)  Please consult RFC 2223, 
Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...


<Prev in Thread] Current Thread [Next in Thread>
  • RFC 4490 on Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS), rfc-editor <=