PKIX Working Group                         Serguei Leontiev, CRYPTO-PRO
Internet Draft                         Dennis Shefanovskij, Shefanovski, DEMOS Co Ltd
Expires August 5, 2005                                 February 5, March 8, 2006                                 September 8, 2005
Intended Category: Informational

            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.

                   <draft-ietf-pkix-gost-cppk-02.txt>

                   <draft-ietf-pkix-gost-cppk-03.txt>

Status of this Memo

   By submitting this Internet-Draft, I certify each author represents that any
   applicable patent or other IPR claims of which I am he or she is aware
   have been or will be disclosed, and any of which I become he or she becomes
   aware will be disclosed, in accordance with
   RFC 3668.

   This document is an Internet Draft and is subject to all provisions
   of Section 10 6 of RFC2026. Internet Drafts BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet Internet-
   Drafts. Internet Drafts

   Internet-Drafts are draft documents valid for a maximum of 6 six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use
   Internet Drafts Internet-Drafts as reference
   material or to cite them other than as a "work in progress". progress."

   The list of current Internet Drafts Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html
   http://www.ietf.org/1id-abstracts.html.

   The list of Internet Draft Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 8, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).  All Rights Reserved.

Abstract

   This document supplements RFC 3279. It describes encoding formats,
   identifiers and appropriate parameters parameter formats for the algorithms GOST R 34.10-94,
   GOST R 34.10-2001, 34.10-2001 and GOST R 34.11-94,
   and also ASN.1 encoding scheme 34.11-94 for digital signatures and public
   keys, used use in Internet X.509
   Public Key Infrastructure (PKI).  This
   specification extends [RFC3279], "Algorithms and Identifiers for the
   Internet X.509 Public Key Infrastructure Certificate and Certificate
   Revocation List (CRL) Profile" and, correspondingly, [RFC3280],
   "Internet X.509 Public Key Infrastructure: Certificate and
   Certificate Revocation List (CRL) Profile". All implementations of
   this specification MUST also satisfy the requirements of [RFC3280].

Table of Contents

   1      Introduction. . . . . . . . . . . . . . . . . . . . . .   2
   2      Algorithm Support . . . . . . . . . . . . . . . . . . .   3
   2.1    One-way Hash Function . . . . . . . . . . . . . . . . .   3
   2.1.1  One-way Hash Function GOST R 34.11-94 . . . . . . . . .   3
   2.2    Signature Algorithms. . . . . . . . . . . . . . . . . .   4   3
   2.2.1  Signature Algorithm GOST R 34.10-94 . . . . . . . . . .   4
   2.2.2  Signature Algorithm GOST R 34.10-2001 . . . . . . . . .   5
   2.3    Subject Public Key Algorithms . . . . . . . . . . . . .   6   5
   2.3.1  GOST R 34.10-94 Keys. . . . . . . . . . . . . . . . . .   6
   2.3.2  GOST R 34.10-2001 Keys. . . . . . . . . . . . . . . . .   8   7
   3      Security Considerations . . . . . . . . . . . . . . . .  10   9
   4      Appendix Examples . . . . . . . . . . . . . . . . . . .  11  10
   4.1    GOST R 34.10-94 Certificate . . . . . . . . . . . . . .  11  10
   4.2    GOST R 34.10-2001 Certificate . . . . . . . . . . . . .  13  12
   5      References. . . . . . . . . . . . . . . . . . . . . . .  16  15
   Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . .  17  16
   Author's Addresses . . . . . . . . . . . . . . . . . . . . . .  18  17
   Full Copyright Statement . . . . . . . . . . . . . . . . . . .  19  18

1  Introduction

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   This document defines identifiers and corresponding algorithm
   parameters and attributes proposed by CRYPTO-PRO Company within
   "Russian Cryptographic Software Compatibility Agreement" community supplements RFC 3279 [PKALGS].  It describes the
   conventions for using the algorithms GOST R 34.10-94, 34.10-94 and GOST R 34.10-2001, 34.10-2001
   signature algorithms, VKO GOST R
   34.11-94, key derivation algorithms based on 34.10-94 and VKO GOST R 34.10-94 public
   keys, 34.10-2001
   key derivation algorithms based on algorithms, and GOST R 34.10-2001 public
   keys, and also ASN.1 encoding [X.660] for digital signatures and
   public keys, used 34.11-94 one-way hash function
   in the Internet X.509 Public Key Infrastructure (PKI). (PKI) [PROFILE].

   This specification extends [RFC3279], "Algorithms document is a proposal put forward by the CRYPT-PRO Company to
   provide supplemental information and Identifiers for specifications needed by the Internet X.509 Public Key Infrastructure Certificate
   "Russian Cryptographic Software Compatibility Agreement" community.

   The algorithm identifiers and
   Certificate Revocation List (CRL) Profile" and, correspondingly,
   [RFC3280], "Internet X.509 Public Key Infrastructure: Certificate associated parameters for subject
   public keys that employ the GOST R 34.10-94 [GOSTR341094] / VKO GOST
   R 34.10-94 [CPALGS] or the GOST R 34.10-2001 [GOSTR341001] / VKO GOST
   R 34.10-2001 [CPALGS] algorithms, and
   Certificate Revocation List (CRL) Profile". All implementations of
   this specification MUST also satisfy the requirements of [RFC3280].

   This specification defines encoding format for the content of
   signatures produced by these algorithms are specified. Also, the signatureAlgorithm,
   signatureValue, signature, and subjectPublicKeyInfo fields within
   Internet X.509 certificates and CRLs.

   This document defines
   algorithm identifiers for using the use of one-way hash-function GOST R 34.11-94 [GOST3411] with digital signatures. This algorithm is used
   in conjunction with digital signature algorithms.

   This specification describes the encoding of digital signatures,
   generated one-way hash
   function with the following cryptographic algorithms:

      * GOST R 34.10-94;
      * 34.10-94 and GOST R 34.10-2001. 34.10-2001 signature
   algorithms are specified.

   This document also specification defines the contents of the signatureAlgorithm,
   signatureValue, signature, and subjectPublicKeyInfo
   field for fields within
   Internet X.509 certificates. Certificates and CRLs.  For each algorithm, the
   appropriate alternatives for the keyUsage certificate extension are
   provided.
   This specification describes encoding formats for public keys used
   with the following cryptographic algorithms:

      * GOST R 34.10-94 [GOST341094];
      * GOST R 34.10-2001 [GOST34102001];
      * Key derivation algorithm VKO GOST R 34.10-94 [CPALGS];
      * Key derivation algorithm VKO GOST R 34.10-2001 [CPALGS];

   ASN.1 modules, including all the definitions used in this document
   can be found in [CPALGS].

2  Algorithm Support

   This section is an overview of cryptographic algorithms, that may be
   used within the Internet X.509 certificates and CRL profile
   [RFC3280].
   [PROFILE].  It describes one-way hash functions and digital signature
   algorithms, that may be used to sign certificates and CRLs, and
   identifies OIDs and ASN.1 encoding for public keys contained in a
   certificate.

   The conforming CAs and/or applications MUST fully support digital
   signatures and public keys for at least one of the specified
   algorithms.

2.1  One-way Hash Function

   This section identifies the use of one-way, collision free hash
   function GOST R 34.11-94 - the only one that can be used in digital
   signature algorithms GOST R 34.10-94/2001. The data that is hashed
   for certificates and CRL signing is fully described in [RFC3280]. RFC 3280
   [PROFILE].

2.1.1  One-way Hash Function GOST R 34.11-94

   GOST R 34.11-94 has been developed by "GUBS of Federal Agency
   Government Communication and Information" and "All-Russian Scientific
   and Research Institute of Standardization".  The algorithm GOST R
   34.11-94 produces a 256-bit hash value of the arbitrary finite bit
   length input. This document does not contain the full GOST R 34.11-94 full
   specification, which can be found in [GOSTR3411] in Russian. It's
   brief technical description in english can be found in [Schneier95],
   [Schneier95] ch. 18.11, p. 454.  contains a brief technical
   description in English.

   This function is MUST always be used with default parameter set
   gostR3411CryptoProParamSetAI identified by
   id-GostR3411-94-CryptoProParamSet (see section 8.2 of [CPALGS]).

2.2  Signature Algorithms

   Conforming CAs may use GOST R 34.10-94 or GOST R 34.10-2001 signature
   algorithms to sign certificates and CRLs.  The signatureAlgorithm
   field of Certificate or CertificateList indicates the

   These signature
   algorithm ID, and associated parameters.  This section also defines
   algorithm identifiers and parameters that MUST be used in the
   signatureAlgorithm field in a Certificate or CertificateList.

   Signature algorithms are MUST always be used conjointly with a one-way hash
   function GOST R 34.11-94 as indicated in [GOSTR341094] and
   [GOSTR34102001].
   [GOSTR341001].

   This section identifies OIDs for GOST R 34.10-94 and GOST R
   34.10-2001 algorithms. The contents of the parameters component for
   each defines algorithm may vary identifiers and details are provided below for each
   algorithm separately. parameters to be used
   in the signatureAlgorithm field in a Certificate or CertificateList.

2.2.1  Signature Algorithm GOST R 34.10-94

   GOST R 34.10-94 has been developed by "GUBS of Federal Agency
   Government Communication and Information" and "All-Russian Scientific
   and Research Institute of Standardization".  This signature algorithm
   MUST be used conjointly with one-way, collision free hash function
   GOST R 34.11-94. This document does not
   contain the full GOST R 34.10-94
   standard description, specification, which is fully described in [GOSTR341094] in
   Russian, and brief description in English could can be found in
   [GOSTR341094] in Russian. [Schneier95] ch. 20.3, p. 495. 495 contains a
   brief technical description in English.

   The ASN.1 OID object identifier used to identify GOST R 34.10-94 this signature algorithm in
   fields signatureAlgorithm in Certificate and CertificateList
   is:

   id-CryptoPro-algorithms

   id-GostR3411-94-with-GostR3410-94 OBJECT IDENTIFIER ::=
         { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
           gostR3411-94-with-gostR3410-94(4) }

   id-GostR3411-94-with-GostR3410-94 OBJECT IDENTIFIER ::=
         { id-CryptoPro-algorithms gostR3411-94-with-gostR3410-94(4)}

   GostR3410-94-CertificateSignatureAlgorithms
      ALGORITHM-IDENTIFIER ::= {
         { NULL IDENTIFIED BY
                       id-GostR3411-94-with-GostR3410-94 } |
         { GostR3410-94-PublicKeyParameters IDENTIFIED BY
                       id-GostR3411-94-with-GostR3410-94 } }

   GostR3410-94-PublicKeyParameters are defined in section 2.3.1.

   When the id-GostR3411-94-with-GostR3410-94 algorithm identifier
   appears as the algorithm field in an AlgorithmIdentifier and parameters are omitted, AlgorithmIdentifier, the
   parameters from
   encoding SHALL omit the public key of parameters field.  That is, the signer's certificate MUST
   AlgorithmIdentifier SHALL be
   used.  If a SEQUENCE of one component: the OBJECT
   IDENTIFIER id-GostR3411-94-with-GostR3410-94.

   The parameters from in the public key subjectPublicKeyInfo field of the signer's certificate are also omited, and it's issuer's certificate has
   of the
   same public key algorithm, parameters from issuer SHALL apply to the public key verification of the
   issuer's certificate MUST be used, and so on. signature.

   Signature algorithm GOST R 34.10-94 generates digital signature in
   the form of two 256-bit numbers r' and s. Its octet string
   representation consists of 64 octets, where first 32 octets contain
   big endian representation of s and second 32 octets contain big
   endian representation of r'.

   Signature values in CMS [CMS] are represented as octet strings, and
   the output is used directly.  However, signature values in
   certificates and CRLs [PROFILE] are represented as bit strings, and
   conversion is needed.

   To convert a binary 512-bit vector (<r'>256||<s>256).  That is, signature value to a bit string, the
   least-significant (1-st) most significant
   bit of signatureValue BIT STRING contains the least-significant (1-st) first octet of the signature value SHALL become the first
   bit of <s>, the bit string, and so on through the most-significant
   (512th) least significant bit of signatureValue contains
   the most-significant (256th) last octet of the signature value, which SHALL become the last
   bit of <r'>. the bit string.

2.2.2  Signature Algorithm GOST R 34.10-2001

   GOST R 34.10-2001 was developed by "GUBS of Federal Agency Government
   Communication and Information" and "All-Russian Scientific and
   Research Institute of Standardization".  This signature algorithm
   MUST be used conjointly with one-way, collision free hash function
   GOST R 34.11-94. This document does not
   contain the full GOST R 34.10-2001
   standard description, specification, which is fully described can be found
   in [GOSTR34102001]. [GOSTR341001] in Russian.

   The ASN.1 OID object identifier used to identify GOST R 34.10-2001 this signature algorithm
   in fields signatureAlgorithm of Certificate and CertificateList
   is:

   id-GostR3411-94-with-GostR3410-2001 OBJECT IDENTIFIER ::=
         { id-CryptoPro-algorithms iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
           gostR3411-94-with-gostR3410-2001(3) }

   GostR3410-2001-CertificateSignatureAlgorithms
     ALGORITHM-IDENTIFIER ::= {
       { NULL IDENTIFIED BY
                       id-GostR3411-94-with-GostR3410-2001 } |
       { GostR3410-2001-PublicKeyParameters IDENTIFIED BY
                       id-GostR3411-94-with-GostR3410-2001 } }

   GostR3410-2001-PublicKeyParameters are defined in section 2.3.2.

   When the id-GostR3411-94-with-GostR3410-2001 algorithm identifier
   appears as the algorithm field in an AlgorithmIdentifier and parameters are omitted, AlgorithmIdentifier, the
   parameters from
   encoding SHALL omit the public key of parameters field.  That is, the signer's certificate MUST
   AlgorithmIdentifier SHALL be
   used.  If a SEQUENCE of one component: the OBJECT
   IDENTIFIER id-GostR3411-94-with-GostR3410-2001.

   The parameters from in the public key subjectPublicKeyInfo field of the signer's
   certificate are also omited, and it's issuer's certificate has
   of the
   same public key algorithm, parameters from issuer SHALL apply to the public key verification of the
   issuer's certificate MUST be used, and so on. signature.

   Signature algorithm GOST R 34.10-2001 generates digital signature in
   the form of two 256-bit numbers r' and s. Its octet string
   representation consists of 64 octets, where first 32 octets contain
   big endian representation of s and second 32 octets contain big
   endian representation of r'.

   Signature values in CMS [CMS] are represented as octet strings, and
   the output is used directly.  However, signature values in
   certificates and CRLs [PROFILE] are represented as bit strings, and
   conversion is needed.

   To convert a binary 512-bit vector (<r'>256||<s>256).  That is, signature value to a bit string, the
   least-significant (1-st) most significant
   bit of signatureValue BIT STRING contains the least-significant (1-st) first octet of the signature value SHALL become the first
   bit of <s>, the bit string, and so on through the most-significant
   (512th) least significant bit of signatureValue contains
   the most-significant (256th) last octet of the signature value, which SHALL become the last
   bit of <r'>. the bit string.

2.3  Subject Public Key Algorithms

   In according to [RFC3280] the certificates may contain a public key
   for any algorithm. Within the framework of this specification the
   only GOST R 34.10-94 and GOST R 34.10-2001 public key algorithms
   defined. The algorithm and associated parameters are definable as OID
   in certificate through ASN.1 structure AlgorithmIdentifier.

   This section identifies defines OID OIDs and public key parameters for public keys
   that employ the GOST R 34.10-94 and [GOSTR341094] / VKO GOST R 34.10-94
   [CPALGS] or the GOST R 34.10-2001 [GOSTR341001] / VKO GOST R
   34.10-2001 [CPALGS] algorithms. The appropriate CA
   MUST use

   Use of the predefined OID issuing certificates containing public
   keys same key for these algorithms. both signature and key derivation is NOT
   RECOMMENDED. The appropriate applications supporting
   any of these algorithms MUST fully recognize intended application for the OID identified key MAY be indicated in
   this section
   the keyUsage certificate extension (see [PROFILE], Section 4.2.1.3).

2.3.1  GOST R 34.10-94 Keys

   This section defines OID and parameter encoding for inclusion of

   GOST R 34.10-94 public key in certificate.  Such public key keys can be used for digital signature validation algorithm GOST
   R 34.10-94
   [GOSTR341094], [GOSTR341094] and for key derivation algorithm VKO GOST R
   34.10-94 [CPALGS].

   An assumed cryptographic key usage MAY be specified by keyUsage
   extension [RFC3280]. The usage of the same key for signature and key
   derivation is NOT RECOMMENDED, but possible.

   Public key OID for

   GOST R 34.10-94 declared in this document is: public keys are identified by the following OID:

   id-GostR3410-94 OBJECT IDENTIFIER ::=
       { id-CryptoPro-algorithms iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
           gostR3410-94(20) }

   SubjectPublicKeyInfo.algorithm.algorithm field (see [RFC3280]) RFC 3280
   [PROFILE]) for GOST R 34.10-94 keys MUST be id-GostR3410-94;

   SubjectPublicKeyInfo.algorithm.parameters id-GostR3410-94.

   When the id-GostR3410-94 algorithm identifier appears as the
   algorithm field in an AlgorithmIdentifier, the encoding MAY
   completely omit the parameters field or set it to null.  Otherwise
   this case field MUST have the following structure:

    GostR3410-94-PublicKeyParameters ::=
        SEQUENCE {
            publicKeyParamSet
                OBJECT IDENTIFIER,
            digestParamSet
                OBJECT IDENTIFIER,
            encryptionParamSet
                OBJECT IDENTIFIER OPTIONAL DEFAULT
                    id-Gost28147-89-CryptoPro-A-ParamSet
        }

   where:
    * publicKeyParamSet - public key parameters identifier for GOST R
      34.10-94 (see section 8.3 of [CPALGS])
    * digestParamSet - parameters identifier for GOST R 34.11-94 (see
      section 8.2 of [CPALGS])
    * encryptionParamSet - optional parameters identifier for GOST 28147-89 (see
      section 8.1 of [CPALGS]) MAY

   Absence of parameters SHALL be present processed as described in any
   certificate and MUST be present if keyUsage includes keyAgreement or
   keyEnchiperment.

   If GOST R 34.10-94 algorithm RFC 3280
   [PROFILE], section 6.1, that is, parameters are omitted in
   subjectPublicKeyInfo, and CA signs subject certificate using GOST R
   34.10-94, then GOST R 34.10-94 parameters taken inherited from
   subjectPublicKeyInfo field of the
   issuer certificate are applicable to
   public key of if possible.

   The GOST R 34.10-94 subject. That is, cryptographic
   parameters inheritance takes place. If subjectPublicKeyInfo
   AlgorithmIdentifier field contain no parameters, but CA sign
   certificate using signature algorithm different from GOST R 34.10-94,
   such certificate MUST be rejected by conforming applications.

   Public public key GOST R 34.10-94 MUST be ASN.1 DER encoded in following way.

   In GOST R 34.10-94 as an OCTET
   STRING; this encoding shall be used as the contents (i.e., the value)
   of the subjectPublicKey component (a BIT STRING) of the
   SubjectPublicKeyInfo data element.

   GostR3410-94-PublicKey ::= OCTET STRING -- public key, Y

   GostR3410-94-PublicKey MUST must contain 128 octets of the little-
   endian representation of the public key is a number y Y = a^x (mod p), where a and
   p - parameters, and y is a bit-vector (<y>1024), at that
   encoding should present <y>1024 (BIT STRING) as a vector holding
   data in a little-endian. At first, a key is presented as an   OCTET
   STRING, and then, being DER-encoded, presented as a BIT STRING.

   GostR3410-94-PublicKey ::= BIT STRING

   GostR3410-94-PublicKeyOctetString ::= OCTET STRING parameters.

   If the keyUsage extension is present in an end-entity certificate,
   which contains a GOST R 34.10-94 public key, the following values MAY
   be present:

      digitalSignature;
      nonRepudiation.
      keyEncipherment;
      keyAgreement.

   If the keyAgreement or keyEnchiperment extension is present in a
   certificate GOST R 34.10-94 public key, the following values MAY be
   present as well:

      encipherOnly;
      decipherOnly.

   The keyUsage extension MUST NOT assert both encipherOnly and
   decipherOnly.

   If the keyUsage extension is present in an CA or CRL signer
   certificate which contain contains a GOST R 34.10-94 public key, the
   following values MAY be present:

      digitalSignature;
      nonRepudiation;
      keyCertSign;
      cRLSign.

2.3.2  GOST R 34.10-2001 Keys

   This section defines OID and parameter encoding for inclusion of

   GOST R 34.10-2001 public key in certificate.  Such public key keys can be used for digital signature validation algorithm
   GOST R 34.10-2001
   [GOSTR34102001], [GOSTR341001] and for key derivation algorithm VKO
   GOST R 34.10-2001 [CPALGS].

   An assumed cryptographic key usage MAY be specified by keyUsage
   extension [RFC3280]. The usage of the same key for signature and key
   derivation is NOT RECOMMENDED, but possible.

   Public key OID for

   GOST R 34.10-2001 declared in this document is: public keys are identified by the following OID:

   id-GostR3410-2001 OBJECT IDENTIFIER ::=
       { id-CryptoPro-algorithms iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
           gostR3410-2001(19) }

   SubjectPublicKeyInfo.algorithm.algorithm field (see [RFC3280]) RFC 3280
   [PROFILE]) for GOST R 34.10-2001 keys MUST be id-GostR3410-2001;

   SubjectPublicKeyInfo.algorithm.parameters id-GostR3410-2001.

   When the id-GostR3410-2001 algorithm identifier appears as the
   algorithm field in an AlgorithmIdentifier, the encoding MAY
   completely omit the parameters field or set it to null.  Otherwise
   this case field MUST have the following structure:

    GostR3410-2001-PublicKeyParameters ::=
        SEQUENCE {
            publicKeyParamSet
                OBJECT IDENTIFIER,
            digestParamSet
                OBJECT IDENTIFIER,
            encryptionParamSet
                OBJECT IDENTIFIER OPTIONAL DEFAULT
                    id-Gost28147-89-CryptoPro-A-ParamSet
        }

   where:
    * publicKeyParamSet - public key parameters identifier for  GOST R
      34.10-2001 (see section 8.4 of [CPALGS])
    * digestParamSet - parameters identifier for GOST R 34.11-94 (see
      section 8.2 of [CPALGS])
    * encryptionParamSet - optional parameters identifier for GOST 28147-89 (see
      section 8.1 of [CPALGS]) MAY

   Absence of parameters SHALL be present processed as described in any
   certificate and MUST be present if keyUsage includes keyAgreement or
   keyEnchiperment.

   If GOST R 34.10-2001 algorithm RFC 3280
   [PROFILE], section 6.1, that is, parameters are omitted in
   subjectPublicKeyInfo, and CA signs subject certificate using GOST R
   34.10-2001, then GOST R 34.10-2001 parameters taken inherited from
   subjectPublicKeyInfo field of the
   issuer certificate are applicable to
   public key of GOST R 34.10-2001 subject. That is, cryptographic
   parameters inheritance takes place. If subjectPublicKeyInfo
   AlgorithmIdentifier field contain no parameters, but CA sign
   certificate using signature algorithm different from GOST R
   34.10-2001, such certificate MUST be rejected by conforming
   applications. if possible.

   The GOST R 34.10-2001 public key MUST be ASN.1 DER encoded in a following
   way. GOST R 34.10-2001 specifies that as an
   OCTET STRING; this encoding shall be used as the contents (i.e., the
   value) of the subjectPublicKey component (a BIT STRING) of the
   SubjectPublicKeyInfo data element.

   GostR3410-2001-PublicKey ::= OCTET STRING -- public key vector, Q

   According to [GOSTR341001], public key is a point on the elliptic
   curve Q = dP, (x,y).

   GostR3410-2001-PublicKey MUST must contain 64 octets, where d is a private key, P is a base point,
   and Q presents in a way of 512-bit vector  (<Xq>256||<Yq>256). This
   vector is DER-encoded as two data blocks. At first, <Xq>256 block,
   then <Yq>256 block. subjectPublicKey field BIT STRING type is
   presented as a  taken up object  GostR3410-2001-PublicKeyOctetString.

   At that, least-significant of the first octet
   (GostR3410-2001-PublicKeyOctetString[0]) corresponds to least-
   significant (1-st) 32
   octets contain little endian representation of vector  <Xq>256||<Yq>256 (Yq1 =
   (GostR3410-2001-PublicKeyOctetString[0] & 1)).

   Whereas most-significant x and second 32 octets
   contain little endian representation of  64-th octet
   (GostR3410-2001-PublicKeyOctetString[63]) y.  This corresponds to most-
   significant  (512-d)  of vector  <Xq>256||<Yq>256 (Xq256 =
   ((GostR3410-2001-PublicKeyOctetString[63] & 0x80)>>7)).

   In other words, <Xq>256||<Yq>256 vector is stored in little-endian,
   that correspond the
   binary vector form and their concatenation in GOST R
   34.10-2001 representation of (<y>256||<x>256) from [GOSTR341001], ch.
   5.3.  At first, key is placed in OCTET STRING, than is
   DER-encoded and placed in BIT STRING.

   GostR3410-2001-PublicKey ::= BIT STRING

   GostR3410-2001-PublicKeyOctetString ::= OCTET STRING

   If the keyUsage extension is present in an end-entity certificate,
   which conveys contains a GOST R 34.10-2001 public key, the following values
   MAY be present:

      digitalSignature,
      nonRepudiation,
      keyEncipherment,
      keyAgreement.

   If the keyAgreement or keyEnchiperment extension is present in a
   certificate, the following values MAY be present:

      encipherOnly,
      decipherOnly.

   The keyUsage extension MUST NOT assert both encipherOnly and
   decipherOnly.

   If the keyUsage extension is present in an CA or CRL signer
   certificate which contain contains a GOST R 34.10-2001 public key, the
   following values MAY be present:

      digitalSignature,
      nonRepudiation,
      keyCertSign,
      cRLSign.

3  Security Considerations

   It is RECCOMENDED, RECOMMENDED, that applications verify signature values and
   subject public keys to conform to [GOSTR34102001], [GOSTR341001] [GOSTR341094]
   standards prior to their use.

   When certificate is used as analogue to a manual signing, in the
   context of Russian Federal Digital Signature Law [RFDSL], certificate
   MUST contain keyUsage extension, it MUST be critical, and keyUsage
   MUST NOT include keyEncipherment and keyAgreement.

   When certificate validity period (typicaly 5 years for end entities
   and 7 years for CAs in Russia) is not equal to the private key
   validity period (typicaly 15 months in Russia) it is RECOMENDED RECOMMENDED to
   use private key usage period extension.

   For security discussion concerning use of algorithm parameters, see
   section Security Considerations from [CPALGS].

4  Appendix Examples
4.1  GOST R 34.10-94 Certificate

 -----BEGIN CERTIFICATE-----
 MIICCzCCAboCECMO42BGlSTOxwvklBgufuswCAYGKoUDAgIEMGkxHTAbBgNVBAMM
 FEdvc3RSMzQxMC05NCBleGFtcGxlMRIwEAYDVQQKDAlDcnlwdG9Qcm8xCzAJBgNV
 BAYTAlJVMScwJQYJKoZIhvcNAQkBFhhHb3N0UjM0MTAtOTRAZXhhbXBsZS5jb20w
 HhcNMDUwODE2MTIzMjUwWhcNMTUwODE2MTIzMjUwWjBpMR0wGwYDVQQDDBRHb3N0
 UjM0MTAtOTQgZXhhbXBsZTESMBAGA1UECgwJQ3J5cHRvUHJvMQswCQYDVQQGEwJS
 VTEnMCUGCSqGSIb3DQEJARYYR29zdFIzNDEwLTk0QGV4YW1wbGUuY29tMIGlMBwG
 BiqFAwICFDASBgcqhQMCAiACBgcqhQMCAh4BA4GEAASBgLuEZuF5nls02CyAfxOo
 GWZxV/6MVCUhR28wCyd3RpjG+0dVvrey85NsObVCNyaE4g0QiiQOHwxCTSs7ESuo
 v2Y5MlyUi8Go/htjEvYJJYfMdRv05YmKCYJo01x3pg+2kBATjeM+fJyR1qwNCCw+
 eMG1wra3Gqgqi0WBkzIydvp7MAgGBiqFAwICBANBABHHCH4S3ALxAiMpR3aPRyqB
 g1DjB8zy5DEjiULIc+HeIveF81W9lOxGkZxnrFjXBSqnjLeFKgF1hffXOAP7zUM=
 -----END CERTIFICATE-----

   0 30  527:  523: SEQUENCE {
   4 30  444:  442:  SEQUENCE {
   8 02   16:   INTEGER
            :       17 31 2A C2 1B D2 08 58 BC 04 1E 52 37 D0 74 50    23 0E E3 60 46 95 24 CE C7 0B E4 94 18 2E 7E EB
  26 30   10:    8:   SEQUENCE {
  28 06    6:    OBJECT IDENTIFIER
            :         id_GostR3411_94_with_GostR3410_94
            :           ( 1     id-GostR3411-94-with-GostR3410-94 (1 2 643 2 2 4)
  36 05    0:       NULL
            :    }
  38
  36 30  105:   SEQUENCE {
  40
  38 31   29:    SET {
  42
  40 30   27:     SEQUENCE {
  44
  42 06    3:      OBJECT IDENTIFIER
            : commonName (2 5 4 3)
  49
  47 0C   20:      UTF8String 'GostR3410-94 example'
            :      }
            :     }
  71
  69 31   18:    SET {
  73
  71 30   16:     SEQUENCE {
  75
  73 06    3:      OBJECT IDENTIFIER
            : organizationName (2 5 4 10)
  80
  78 0C    9:      UTF8String 'CryptoPro'
            :      }
            :     }
  91
  89 31   11:    SET {
  93
  91 30    9:     SEQUENCE {
  95
  93 06    3:      OBJECT IDENTIFIER
            : countryName (2 5 4 6)
 100
  98 13    2:      PrintableString 'RU'
            :      }
            :     }
 104
 102 31   39:    SET {
 106
 104 30   37:     SEQUENCE {
 108
 106 06    9:      OBJECT IDENTIFIER
            : emailAddress (1 2 840 113549 1 9 1)
 119
 117 16   24:      IA5String 'GostR3410-94@example.com'
            :      }
            :     }
            :    }
 145
 143 30   30:   SEQUENCE {
 147
 145 17   13:    UTCTime '050203151651Z'
 162 '050816123250Z'
 160 17   13:    UTCTime '150203151651Z' '150816123250Z'
            :    }
 177
 175 30  105:   SEQUENCE {
 179
 177 31   29:    SET {
 181
 179 30   27:     SEQUENCE {
 183
 181 06    3:      OBJECT IDENTIFIER
            : commonName (2 5 4 3)
 188
 186 0C   20:      UTF8String 'GostR3410-94 example'
            :      }
            :     }
 210
 208 31   18:    SET {
 212
 210 30   16:     SEQUENCE {
 214
 212 06    3:      OBJECT IDENTIFIER
            : organizationName (2 5 4 10)
 219
 217 0C    9:      UTF8String 'CryptoPro'
            :      }
            :     }
 230
 228 31   11:    SET {
 232
 230 30    9:     SEQUENCE {
 234
 232 06    3:      OBJECT IDENTIFIER
            : countryName (2 5 4 6)
 239
 237 13    2:      PrintableString 'RU'
            :      }
            :     }
 243
 241 31   39:    SET {
 245
 243 30   37:     SEQUENCE {
 247
 245 06    9:      OBJECT IDENTIFIER
            : emailAddress (1 2 840 113549 1 9 1)
 258
 256 16   24:      IA5String 'GostR3410-94@example.com'
            :      }
            :     }
            :    }
 284
 282 30  165:   SEQUENCE {
 287
 285 30   28:    SEQUENCE {
 289
 287 06    6:     OBJECT IDENTIFIER
            :           id_GostR3410_94 ( 1 id-GostR3410-94 (1 2 643 2 2 20)

 297
 295 30   18:     SEQUENCE {
 299
 297 06    7:      OBJECT IDENTIFIER
            :             id_GostR3410_94_CryptoPro_A_ParamSet       id-GostR3410-94-CryptoPro-A-ParamSet
            :               ( 1        (1 2 643 2 2 32 2)
 308
 306 06    7:      OBJECT IDENTIFIER
            :             id_GostR3411_94_CryptoProParamSet       id-GostR3411-94-CryptoProParamSet
            :               ( 1        (1 2 643 2 2 30 1)
            :      }
            :     }
 317
 315 03  132:    BIT STRING 0 unused bits, encapsulates {
 321
 319 04  128:     OCTET STRING
            :      BB 84 66 E1 79 9E 5B 34 D8 2C 80 7F 13 A8 19 66
            :      71 57 FE 8C 54 25 21 47 6F 30 0B 27 77 46 98 C6
            :      FB 47 55 BE B7 B2 F3 93 6C 39 B5 42 37 26 84 E2
            :      0D 10 8A 24 0E 1F 0C 42 4D 2B 3B 11 2B A8 BF 66
            :      39 32 5C 94 8B C1 A8 FE 1B 63 12 F6 09 25 87 CC
            :      75 1B F4 E5 89 8A 09 82 68 D3 5C 77 A6 0F B6 90
            :      10 13 8D E3 3E 7C 9C 91 D6 AC 0D 08 2C 3E 78 C1
            :      B5 C2 B6 B7 1A A8 2A 8B 45 81 93 32 32 76 FA 7B
            :     }
            :    }
            :   }
 452
 450 30   10:    8:  SEQUENCE {
 454
 452 06    6:   OBJECT IDENTIFIER
            :       id_GostR3411_94_with_GostR3410_94 ( 1    id-GostR3411-94-with-GostR3410-94 (1 2 643 2 2 4)
 462 05    0:     NULL
            :   }
 464
 460 03   65:  BIT STRING 0 unused bits
            :     71 28 D8 4E 9A 38 33 FE 2E 42   11 C7 08 7E 12 DC 02 CE F1 02 23 29 47 76 8F 47 2A
            :   81 83 50 E3 07 CC F2 E4 31 23 89 42 C8 AC B3 73 E1 DE
            :     F6 91   22 F7 85 F3 55 BD 94 EC 46 90 37 1A CA 6B 16 61 91 9C 67 AC 58 D7 05 95 BF B0 99 D2
            :     94 CC F0   2A A7 8C CC CE 45 B7 85 2A 01 5B 71 87 B1 48 C2 16 96
            :     A7 15 90 DF 83 6C EE 37 ED E4 4F EE BD E2 7F 41 75 85 F7 D7 38 03 FB CD 43
            :  }

 In the signature of the above certificate, r' equals to
 0x22F785F355BD94EC46919C67AC58D7052AA78CB7852A017585F7D73803FBCD43
 and s equals to
 0x11C7087E12DC02F102232947768F472A818350E307CCF2E431238942C873E1DE

4.2  GOST R 34.10-2001 Certificate

 -----BEGIN CERTIFICATE-----
 MIIB0DCCAX8CECv1xh7CEb0Xx9zUYma0LiEwCAYGKoUDAgIDMG0xHzAdBgNVBAMM
 Fkdvc3RSMzQxMC0yMDAxIGV4YW1wbGUxEjAQBgNVBAoMCUNyeXB0b1BybzELMAkG
 A1UEBhMCUlUxKTAnBgkqhkiG9w0BCQEWGkdvc3RSMzQxMC0yMDAxQGV4YW1wbGUu
 Y29tMB4XDTA1MDgxNjE0MTgyMFoXDTE1MDgxNjE0MTgyMFowbTEfMB0GA1UEAwwW
 R29zdFIzNDEwLTIwMDEgZXhhbXBsZTESMBAGA1UECgwJQ3J5cHRvUHJvMQswCQYD
 VQQGEwJSVTEpMCcGCSqGSIb3DQEJARYaR29zdFIzNDEwLTIwMDFAZXhhbXBsZS5j
 b20wYzAcBgYqhQMCAhMwEgYHKoUDAgIkAAYHKoUDAgIeAQNDAARAhJVodWACGkB1
 CM0TjDGJLP3lBQN6Q1z0bSsP508yfleP68wWuZWIA9CafIWuD+SN6qa7flbHy7Df
 D2a8yuoaYDAIBgYqhQMCAgMDQQA8L8kJRLcnqeyn1en7U23Sw6pkfEQu3u0xFkVP
 vFQ/3cHeF26NG+xxtZPz3TaTVXdoiYkXYiD02rEx1bUcM97i
 -----END CERTIFICATE-----

   0 30  468:  464: SEQUENCE {
   4 30  385:  383:  SEQUENCE {
   8 02   16:   INTEGER
            :       48 E9 54 A5 CF E9 69    2B F5 C9 5C F7 55 E7 83 41 AF C6 1E C2 11 BD 17 C7 DC D4 62 66 B4 2E 21
  26 30   10:    8:   SEQUENCE {
  28 06    6:    OBJECT IDENTIFIER
            :         id_GostR3411_94_with_GostR3410_2001
            :           ( 1     id-GostR3411-94-with-GostR3410-2001 (1 2 643 2 2 3)
  36 05    0:       NULL
            :    }
  38
  36 30  109:   SEQUENCE {
  40
  38 31   31:    SET {
  42
  40 30   29:     SEQUENCE {
  44
  42 06    3:      OBJECT IDENTIFIER
            : commonName (2 5 4 3)
  49
  47 0C   22:      UTF8String 'GostR3410-2001 example'
            :      }
            :     }
  73
  71 31   18:    SET {
  75
  73 30   16:     SEQUENCE {
  77
  75 06    3:      OBJECT IDENTIFIER
            : organizationName (2 5 4 10)
  82
  80 0C    9:      UTF8String 'CryptoPro'
            :      }
            :     }
  93
  91 31   11:    SET {
  95
  93 30    9:     SEQUENCE {
  97
  95 06    3:      OBJECT IDENTIFIER
            : countryName (2 5 4 6)
 102
 100 13    2:      PrintableString 'RU'
            :      }
            :     }
 106
 104 31   41:    SET {
 108
 106 30   39:     SEQUENCE {
 110
 108 06    9:      OBJECT IDENTIFIER
            : emailAddress (1 2 840 113549 1 9 1)
 121
 119 16   26:      IA5String 'GostR3410-2001@example.com'
            :      }
            :     }
            :    }
 149
 147 30   30:   SEQUENCE {
 151
 149 17   13:    UTCTime '050203151646Z'
 166 '050816141820Z'
 164 17   13:    UTCTime '150203151646Z' '150816141820Z'
            :    }
 181
 179 30  109:   SEQUENCE {
 183
 181 31   31:    SET {
 185
 183 30   29:     SEQUENCE {
 187
 185 06    3:      OBJECT IDENTIFIER
            : commonName (2 5 4 3)
 192
 190 0C   22:      UTF8String 'GostR3410-2001 example'
            :      }
            :     }
 216
 214 31   18:    SET {
 218
 216 30   16:     SEQUENCE {
 220
 218 06    3:      OBJECT IDENTIFIER
            : organizationName (2 5 4 10)
 225
 223 0C    9:      UTF8String 'CryptoPro'
            :      }
            :     }
 236
 234 31   11:    SET {
 238
 236 30    9:     SEQUENCE {
 240
 238 06    3:      OBJECT IDENTIFIER
            : countryName (2 5 4 6)
 245
 243 13    2:      PrintableString 'RU'
            :      }
            :     }
 249
 247 31   41:    SET {
 251
 249 30   39:     SEQUENCE {
 253
 251 06    9:      OBJECT IDENTIFIER
            : emailAddress (1 2 840 113549 1 9 1)
 264
 262 16   26:      IA5String 'GostR3410-2001@example.com'
            :      }
            :     }
            :    }
 292
 290 30   99:   SEQUENCE {
 294
 292 30   28:    SEQUENCE {
 296
 294 06    6:     OBJECT IDENTIFIER
            :           id_GostR3410_2001 ( 1 id-GostR3410-2001 (1 2 643 2 2 19)
 304
 302 30   18:     SEQUENCE {
 306
 304 06    7:      OBJECT IDENTIFIER
            :             id_GostR3410_2001_CryptoPro_XchA_ParamSet       id-GostR3410-2001-CryptoPro-XchA-ParamSet
            :               ( 1        (1 2 643 2 2 36 0)
 315
 313 06    7:      OBJECT IDENTIFIER
            :             id_GostR3411_94_CryptoProParamSet       id-GostR3411-94-CryptoProParamSet
            :               ( 1        (1 2 643 2 2 30 1)
            :      }
            :     }
 324
 322 03   67:    BIT STRING 0 unused bits, encapsulates {
 327
 325 04   64:     OCTET STRING
            :      84 95 68 75 60 02 1A 40 75 08 CD 13 8C 31 89 2C
            :      FD E5 05 03 7A 43 5C F4 6D 2B 0F E7 4F 32 7E 57
            :      8F EB CC 16 B9 95 88 03 D0 9A 7C 85 AE 0F E4 8D
            :      EA A6 BB 7E 56 C7 CB B0 DF 0F 66 BC CA EA 1A 60
            :     }
            :    }
            :   }
 393
 391 30   10:    8:  SEQUENCE {
 395
 393 06    6:   OBJECT IDENTIFIER
            :       id_GostR3411_94_with_GostR3410_2001 ( 1    id-GostR3411-94-with-GostR3410-2001 (1 2 643 2 2 3)
 403 05    0:     NULL
            :   }
 405
 401 03   65:  BIT STRING 0 unused bits
            :     1F 0E 5D   3C 2F C9 09 44 B7 27 A9 EC A7 D5 E9 FB 53 6D D2
            :   C3 F6 B0 FC E8 8D BC 7C 8E 13 AE AA 64 BF 7C 44 2E DE ED 31 16 45 4F BC 54 3F DD
            :     2A 38 1E 9D 2C 7F 3D DC B0 CE 94 52 4A 75 D1 53   C1 DE 17 6E 8D 1B EC 71 B5 93 F3 DD 36 93 55 77
            :     B6 E3 BA 1F 34 92 B7 B6 C2 DB   68 89 89 17 62 20 F4 DA B1 31 D5 B5 1C 33 DE E2 E3 51 AA B3
            :     79 FA E5 19 BD 75 5A 91 D8 AE F5 85 83 E1 5C 2C
            :  }

 In the public key of the above certificate, x equals to
 0x577E324FE70F2B6DF45C437A0305E5FD2C89318C13CD0875401A026075689584
 and y equals to
 0x601AEACABC660FDFB0CBC7567EBBA6EA8DE40FAE857C9AD0038895B916CCEB8F

 In the signature of the above certificate, r' equals to
 0xC1DE176E8D1BEC71B593F3DD36935577688989176220F4DAB131D5B51C33DEE2
 and s equals to
 0x3C2FC90944B727A9ECA7D5E9FB536DD2C3AA647C442EDEED3116454FBC543FDD

5  References

   Normative references:

   [GOST28147]   "Cryptographic Protection for Data Processing Sys-
                   tem", System",
                 GOST 28147-89, Gosudarstvennyi Standard of USSR, Government Gov-
                 ernment Committee of the USSR for Standards, 1989. (In
                 Russian);

   [GOSTR341094] "Information technology. Cryptographic Data Security.
                 Produce and check procedures of Electronic Digital
                   Signatures Sig-
                 natures based on Asymmetric Cryptographic Algo-
                   rithm.", Algorithm.",
                 GOST R 34.10-94, Gosudarstvennyi Standard of Russian
                 Federation, Government Committee of the Rus-
                   sia Russia for
                 Standards, 1994. (In Russian);

   [GOSTR34102001]

   [GOSTR341001] "Information technology. Cryptographic data security.
                 Signature and verification processes of [electronic]
                 digital signature.", GOST R 34.10-2001, Gosudarstven-
                   nyi Gosudarstvennyi
                 Standard of Russian Federation, Government Com-
                   mittee Committee of
                 the Russia for Standards, 2001. (In Rus-
                   sian); Russian);

   [GOSTR341194] "Information technology. Cryptographic Data Security.
                 Hashing function.", GOST R 34.10-94, Gosudarstvennyi
                 Standard of Russian Federation, Government Committee of
                 the Russia for Standards, 1994. (In Russian);

   [RFDSL]         Russian Federal Digital Signature Law, 10 Jan 2002
                   N1-FZ

   [CPALGS]      "Additional cryptographic algorithms for use with GOST
                 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST
                 R 34.11-94 algorithms", V. Popov, I. Kurep-
                   kin, Kurepkin, S. Leontiev, February 2004, draft-popov-crypto-
                   pro-cpalgs-01.txt Leon-
                 tiev, September 2005, draft-popov-cryptopro-
                 cpalgs-04.txt work in progress;

   [Schneier95]    B. Schneier, Applied cryptography, second edition,
                   John Wiley & Sons, Inc., 1995;

   [RFC3280]

   [PROFILE]     Housley, R., Polk, W., Ford, W.  and D.  Solo,
                   "Internet "Inter-
                 net X.509 Public Key Infrastructure Certificate and
                 Certificate Revocation List (CRL) Profile", RFC 3280,
                 April 2002.

   [RFC3279]       Algorithms

   [PKALGS]      L.  Bassham, W.  Polk, R.  Housley, "Algorithms and
                 Identifiers for the Internet X.509 Public Key Infrastructure Infras-
                 tructure Certificate and Certificate Revocation List
                 (CRL) Profile.  L.  Bassham, W.
                   Polk, R.  Housley. Profile", RFC 3279, April 2002.

   [RFC2119]       Bradner, S., "Key Words for Use in RFCs to Indicate
                   Requirement Levels", BCP 14, RFC 2119, March 1997.

   [TLS]           The TLS Protocol Version 1.0.  T.  Dierks, C.  Allen.
                   January 1999, RFC 2246.

   [X.660]       ITU-T Recommendation X.660 Information Technology -
                 ASN.1 encoding rules: Specification of Basic Encoding
                 Rules (BER), Canonical Encoding Rules (CER) and Dis-
                   tinguished Distin-
                 guished Encoding Rules (DER), 1997.

   Informative references:

   [Schneier95]  B. Schneier, Applied cryptography, second edition, John
                 Wiley & Sons, Inc., 1995;

   [RFDSL]       Russian Federal Digital Signature Law, 10 Jan 2002
                 N1-FZ

   [RFC2119]     Bradner, S., "Key Words for Use in RFCs to Indicate
                 Requirement Levels", BCP 14, RFC 2119, March 1997.

   [CMS]         Housley, R., "Cryptographic Message Syntax (CMS)", RFC
                 3852, July 2004.

Acknowledgments

   This document was created in accordance with "Russian Cryptographic
   Software Compatibility Agreement", signed by FGUE STC "Atlas",
   CRYPTO-PRO, Factor-TC, Factor-TS, MD PREI, Infotecs GmbH, SPRCIS (SPbRCZI),
   Cryptocom, R-Alpha.  The goal of this agreement is to achieve mutual
   compatibility of the products and solutions.

   The authors wish to thank:

      Microsoft Corporation Russia for provided information about
      company products and solutions, and also for technical consulting
      in PKI.

      RSA Security Russia and Demos Co Ltd for active colaboration and
      critical help in creation of this document.

      RSA Security Inc for compatibility testing of the proposed data
      formats while incorporating them into RSA Keon product.

      Baltimore Technology plc for compatibility testing of the proposed
      data formats while incorporating them into UniCERT product.

      Russ Hously (Vigil Security, LLC, housley@vigilsec.com) and
      Vasilij Sakharov (DEMOS Co Ltd, svp@dol.ru) for initiative
      creating this document.

      Grigorij Chudov for navigating the IETF process for this document.

   This document is based on a contribution of CRYPTO-PRO company.  Any
   substantial use of the text from this document must reference CRYPTO-
   PRO.  CRYPTO-PRO requests that all material mentioning or referencing
   this document identify this as "CRYPTO-PRO CPPK".

Author's Addresses

   Serguei Leontiev
   CRYPTO-PRO
   38, Obraztsova,
   Moscow, 127018, Russian Federation
   EMail: lse@cryptopro.ru

   Dennis Shefanovski
   DEMOS Co Ltd
   6/1, Ovchinnikovskaja naberezhnaya,
   Moscow, 113035, Russian Federation
   EMail: sdb@dol.ru

   Grigorij Chudov
   CRYPTO-PRO
   38, Obraztsova,
   Moscow, 127018, Russian Federation
   EMail: chudov@cryptopro.ru

   Alexandr Afanasiev
   Factor-TC
   Factor-TS
   office 711, 14, Presnenskij val,
   Moscow, 123557, Russian Federation
   EMail: aaaf@factor-ts.ru afa1@factor-ts.ru

   Nikolaj Nikishin
   Infotecs GmbH
   p/b 35, 80-5, Leningradskij prospekt,
   Moscow, 125315, Russian Federation
   EMail: nikishin@infotecs.ru

   Boleslav Izotov
   FGUE STC "Atlas"
   38, Obraztsova,
   Moscow, 127018, Russian Federation
   EMail: izotov@stcnet.ru izotov@nii.voskhod.ru

   Elena Minaeva
   MD PREI
   build 3, 6A, Vtoroj Troitskij per.,
   Moscow, Russian Federation
   EMail: evminaeva@mo.msk.ru evminaeva@mail.ru

   Serguei Murugov
   R-Alpha
   4/1, Raspletina,
   Moscow, 123060, Russian Federation
   EMail: msm@office.ru

   Igori msm@top-cross.ru

   Igor Ustinov
   Cryptocom
   office 239, 51, Leninskij prospekt,
   Moscow, 119991, Russian Federation
   EMail: igus@cryptocom.ru

   Anatolij Erkin
   SPRCIS (SPbRCZI)
   1, Obrucheva,
   St.Petersburg, 195220, Russian Federation
   EMail: erkin@nevsky.net

Full Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Full Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.