Re: RFC 4491 on Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL Profile

["Gregory S. Chudov" <chudov@xxxxxxxxxxxx>]

Thanks and to everyone involved.
One funny thing - the announcement says "Obsoletes:  RFC3279"
(was "Updates:  RFC3279" in the document itself).
So GOST is now the one and only algorithm for PKIX? :)

Good luck!

----- Original Message ----- 
From: <rfc-editor@xxxxxxxxxxxxxx>
To: <ietf-announce@xxxxxxxx>; <rfc-dist@xxxxxxxxxxxxxx>
Cc: <rfc-editor@xxxxxxxxxxxxxx>; <ietf-pkix@xxxxxxx>
Sent: Tuesday, May 23, 2006 2:24 AM
Subject: RFC 4491 on Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST 
R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure 
Certificate and CRL Profile


> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 4491
>
>        Title:      Using the GOST R 34.10-94,
>                    GOST R 34.10-2001, and GOST R
>                    34.11-94 Algorithms with the Internet X.509
>                    Public Key Infrastructure Certificate and CRL
>                    Profile
>        Author:     S. Leontiev, Ed.,
>                    D. Shefanovski, Ed.
>        Status:     Standards Track
>        Date:       May 2006
>        Mailbox:    lse@xxxxxxxxxxxx,
>                    dbs@xxxxxx
>        Pages:      20
>        Characters: 39095
>        Obsoletes:  RFC3279
>        See-Also:
>
>        I-D Tag:    draft-ietf-pkix-gost-cppk-05.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc4491.txt
>
> This document supplements RFC 3279.  It describes encoding formats,
> identifiers, and parameter formats for the algorithms GOST R 34.10-94,
> GOST R 34.10-2001, and GOST R 34.11-94 for use in Internet X.509
> Public Key Infrastructure (PKI).  [STANDARDS TRACK]
>
> This document is a product of the Public-Key Infrastructure (X.509)
> 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@xxxxxxxxx  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body
>
> help: ways_to_get_rfcs. For example:
>
>        To: rfc-info@xxxxxxxxxxxxxx
>        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@xxxxxxxxxxxxxxx  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@xxxxxxxxxxxxxxx  Please consult RFC 2223, Instructions to RFC
> Authors, for further information.
>
>
> Joyce K. Reynolds and Sandy Ginoza
> USC/Information Sciences Institute
>
> ...