Network Working Group S. Leontiev Internet-Draft P. Smirnov Intended status: Informational A. Chelpanov Expires: June 19, 2009 CRYPTO-PRO December 16, 2008 Using GOST 28147-89, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms for XML Security draft-chudov-cryptopro-cpxmldsig-02 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of 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- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on June 19, 2009. Abstract This document specifies how to use Russian national cryptographic standards GOST 28147-89, GOST R 34.10-2001 and GOST R 34.11-94 with XML Signatures, XML Encryption, WS-SecureConversation, WS- SecurityPolicy and WS-Trust. A number of Uniform Resource Identifiers (URIs) and XML elements are defined. Leontiev, et al. Expires June 19, 2009 [Page 1] Internet-Draft GOST based Security URIs December 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. GOST Cryptographic Algorithms . . . . . . . . . . . . . . . . 3 3. Version and Namespaces . . . . . . . . . . . . . . . . . . . . 3 4. XML Schema Preamble and DTD Replacement . . . . . . . . . . . 4 4.1. XML Schema Preamble . . . . . . . . . . . . . . . . . . . 4 4.2. DTD Replacement . . . . . . . . . . . . . . . . . . . . . 4 5. Object Identifiers Representation . . . . . . . . . . . . . . 5 6. Specifying GOST within XML Signature and XML Encryption . . . 5 6.1. GOST R 34.11-94 Algorithm in DigestMethod . . . . . . . . 5 6.2. GOST R 34.11-94 HMAC Algorithm in SignatureMethod . . . . 6 6.3. GOST R 34.10-2001 Algorithm in SignatureMethod . . . . . . 6 6.4. GOST R 34.10-2001 Public Key in KeyValue . . . . . . . . . 7 6.4.1. Key Value Root Element . . . . . . . . . . . . . . . . 7 6.4.2. Public Key Parameters . . . . . . . . . . . . . . . . 8 6.5. GOST R 34.10-2001-based Key Agreement Algorithm in AgreementMethod . . . . . . . . . . . . . . . . . . . . . 9 6.6. GOST R 34.10-2001-based Key Transport Algorithm in EncryptionMethod . . . . . . . . . . . . . . . . . . . . . 9 6.7. GOST 28147-89 Algorithm in EncryptionMethod . . . . . . . 10 6.8. Symmetric Key Wrap . . . . . . . . . . . . . . . . . . . . 11 6.8.1. GOST 28147-89 Key Wrap in EncryptionMethod . . . . . . 11 6.8.2. CryptoPro Key Wrap in EncryptionMethod . . . . . . . . 13 7. Specifying GOST within WS-* . . . . . . . . . . . . . . . . . 14 7.1. GOST Algorithm Suite for WS-SecurityPolicy . . . . . . . . 14 8. Security Considerations . . . . . . . . . . . . . . . . . . . 15 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 9.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:xmlsec-gost . . . . . . . . . . . . 16 9.2. Schema Registration . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 10.1. Normative references . . . . . . . . . . . . . . . . . . . 16 10.2. Informative references . . . . . . . . . . . . . . . . . . 19 Appendix A. Aggregate XML Schema . . . . . . . . . . . . . . . . 19 Appendix B. Aggregate DTD . . . . . . . . . . . . . . . . . . . . 21 Appendix C. Examples . . . . . . . . . . . . . . . . . . . . . . 21 C.1. Signed document . . . . . . . . . . . . . . . . . . . . . 21 Appendix D. Acknowledgments . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . . . 24 Leontiev, et al. Expires June 19, 2009 [Page 2] Internet-Draft GOST based Security URIs December 2008 1. Introduction This document specifies how to use GOST R 34.10-2001 digital signatures and public keys, GOST R 34.11-94 hash, GOST 28147-89 encryption algorithms with XML Signatures [XMLDSIG], XML Encryption [XMLENC-CORE], WS-SecureConversation [WS-SECURECONVERSATION], WS- SecurityPolicy [WS-SECURITYPOLICY] and WS-Trust [WS-TRUST]. This document uses both XML Schemas ([XML-SCHEMA-1], [XML-SCHEMA-2]) (normative) and DTDs [XML] (informational) to specify the corresponding XML structures. 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 [KEYWORDS]. 2. GOST Cryptographic Algorithms Algorithms GOST R 34.10-2001, GOST R 34.11-94 and GOST 28147-89 have been developed by Russian Federal Agency of Governmental Communication and Information (FAGCI) and "All-Russian Scientific and Research Institute of Standardization". They are described in [GOSTR341001], [GOSTR341194] ([GOST3431004] and [GOST3431195]) and [GOST28147]. RECOMMENDED parameters for those algorithms are described in [CPALGS]. 3. Version and Namespaces This specification makes no provision for an explicit version number in the syntax. If a future version is needed, it will use a different namespace. The XML namespace [XML-NS] URI [RFC3986] that MUST be used by implementations of this (dated) specification is: urn:ietf:params:xml:ns:xmlsec-gost The following external XML namespaces are used in this specification (the choice of any namespace prefix is arbitrary and not semantically significant): http://www.w3.org/2000/09/xmldsig# Prefix: dsig Leontiev, et al. Expires June 19, 2009 [Page 3] Internet-Draft GOST based Security URIs December 2008 Specification: [XMLDSIG] http://www.w3.org/2001/04/xmlenc# Prefix: xenc Specification: [XMLENC-CORE] http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702 Prefix: sp Specification: [WS-SECURITYPOLICY] http://www.w3.org/ns/ws-policy Prefix: wsp Specification: [WS-POLICY] In the remaining sections of this document elements in the external namespaces are marked as such by using the namespace prefixes defined above. 4. XML Schema Preamble and DTD Replacement 4.1. XML Schema Preamble The subsequent preamble is to be used with the XML Schema definitions given in the remaining sections of this document. 4.2. DTD Replacement In order to include GOST XML-signature syntax, the following definition of the entity Key.ANY SHOULD replace the one in [XMLDSIG]: Leontiev, et al. Expires June 19, 2009 [Page 4] Internet-Draft GOST based Security URIs December 2008 5. Object Identifiers Representation Object Identifiers (OIDs) are included in XML by the corresponding URN value as defined in [URNOID]. The subsequent type is to be used to define algorithm parameters by OIDs: 6. Specifying GOST within XML Signature and XML Encryption This section specifies the details of how to use GOST algorithms with XML Signature Syntax and Processing [XMLDSIG] and XML Encryption Syntax and Processing [XMLENC-CORE]. It relies heavily on syntaxes and namespaces defined in [XMLDSIG] and [XMLENC-CORE]. 6.1. GOST R 34.11-94 Algorithm in DigestMethod The identifier for the GOST R 34.11-94 digest algorithm is: urn:ietf:params:xml:ns:xmlsec-gost:algorithms:gostr3411 The dsig:DigestMethod node may contain a child node gost: ParametersR3411 specifying parameters for GOST R 34.11-94 algorithm. gost:ParametersR3411 node contains one OID specified in section 8.2 [CPALGS]. If gost:ParametersR3411 node is missing, the application should infer algorithm parameters from other sources. If the application omits gost:ParametersR3411 node, it SHOULD use parameters defined by id-GostR3411-94-CryptoProParamSet (see Section 11.2 of [CPALGS]). Schema Definition: DTD Definition: Leontiev, et al. Expires June 19, 2009 [Page 5] Internet-Draft GOST based Security URIs December 2008 An example of a GOST R 34.11-94 dsig:DigestMethod node is: urn:oid:1.2.643.2.2.30.1< /gost:ParametersR3411> A GOST R 34.11-94 digest is a 256-bit string. The content of the dsig:DigestValue element shall be the base64 [RFC4648] encoding of this bit string viewed as a 32-octet octet stream. 6.2. GOST R 34.11-94 HMAC Algorithm in SignatureMethod GOST R 34.11-94 can also be used in HMAC [HMAC] as described in section 6.3.1 of [XMLDSIG]. Identifier: urn:ietf:params:xml:ns:xmlsec-gost:algorithms:hmac-gostr3411 The dsig:SignatureMethod node may contain a child node gost: ParametersR3411 specifying parameters for GOST R 34.11-94 algorithm. gost:ParametersR3411 node syntax and processing in this case are equivalent to the ones in dsig:DigestMethod case. An example of a GOST R 34.11-94 HMAC disg:SignatureMethod node is: urn:oid:1.2.643.2.2.30.1< /gost:ParametersR3411> The output of the GOST R 34.11-94 HMAC algorithm is ultimately the output of the GOST R 34.11-94 digest algorithm. This value shall be base64 [RFC4648] encoded for the dsig:SignatureValue in the same straightforward fashion as the output of the digest algorithm. 6.3. GOST R 34.10-2001 Algorithm in SignatureMethod The input to the GOST R 34.10-2001 algorithm is the canonicalized representation of the dsig:SignedInfo element as specified in Section 3 of [XMLDSIG]. The identifier for the GOST R 34.10-2001 signature algorithm is (without line break): Leontiev, et al. Expires June 19, 2009 [Page 6] Internet-Draft GOST based Security URIs December 2008 urn:ietf:params:xml:ns:xmlsec-gost:algorithms:gostr34102001- gostr3411 An example of a GOST R 34.10-2001 dsig:SignatureMethod node is (without line break in attribute value): GOST R 34.10-2001 signature is a 64-octet value as described in section 2.2 of [CPPK]. The content of the dsig:SignatureValue element shall be the base64 [RFC4648] encoding of this value. 6.4. GOST R 34.10-2001 Public Key in KeyValue 6.4.1. Key Value Root Element GOST R 34.10-2001 public key can be transmitted in gost:GOSTKeyValue node. It is included in dsig:KeyValue node just like dsig: RSAKeyValue or xenc:DHKeyValue. gost:GOSTKeyValue node consists of an optional child node gost: PublicKeyParameters and a mandatory child node gost:PublicKey. If gost:PublicKeyParameters node is missing, the application should infer parameters from other sources. Schema Definition: DTD Definition: Leontiev, et al. Expires June 19, 2009 [Page 7] Internet-Draft GOST based Security URIs December 2008 If the application omits gost:PublicKeyParameters node, it SHOULD use parameters identified by DefaultPublicKeyParameters. DefaultPublicKeyParameters: urn:oid:1.2.643.2.2.35.1< /gost:publicKeyParamSet> urn:oid:1.2.643.2.2.30.1 urn:oid:1.2.643.2.2.31.1 6.4.2. Public Key Parameters gost:PublicKeyParameters node contains three OIDs: gost: publicKeyParamSet, gost:digestParamSet and optional gost: encryptionParamSet. Parameter values corresponding to these OIDs can be found in [CPALGS]. Schema Definition: DTD Definition: Leontiev, et al. Expires June 19, 2009 [Page 8] Internet-Draft GOST based Security URIs December 2008 6.5. GOST R 34.10-2001-based Key Agreement Algorithm in AgreementMethod Key agreement algorithm based on GOST R 34.10-2001 public keys (see Section 5 of [CPALGS]) involves the derivation of shared secret information using keys from the sender and recipient. The identifier for the key agreement algorithm based on GOST R 34.10- 2001 is: urn:ietf:params:xml:ns:xmlsec-gost:algorithms:agree-gost2001 An example of a GOST R 34.10-2001-based key agreement AgreementMethod node is: ... ... ... The shared keying material for algorithm based on GOST R 34.10-2001 needed will be calculated as a result of function VKO GOST R 34.10- 2001 (see Section 5.2 of [CPALGS]), which generates GOST KEK using two GOST R 34.10-2001 keypairs and UKM. xenc:KA-Nonce node of xenc: AgreementMethod contains base64 encoded 64-bits value of UKM, if UKM is used. 6.6. GOST R 34.10-2001-based Key Transport Algorithm in EncryptionMethod The key transport alogorithm based on VKO GOST R 34.10-2001, specified in [CPALGS], is public key encryption algorithms, that MUST be used for key encryption/decryption only. The identifier for the key transport algorithm based on VKO GOST R 34.10-2001 is: urn:ietf:params:xml:ns:xmlsec-gost:algorithms:transport-gost2001 Leontiev, et al. Expires June 19, 2009 [Page 9] Internet-Draft GOST based Security URIs December 2008 An example of a VKO GOST R 34.10-2001-based key transport EncryptedKey node is: ... ... The CipherValue for such encrypted key is the base64 encoding of the [X.208-88] DER encoding of a GostR3410-KeyTransport structure (see section 4.2.1 of [CPCMS]). 6.7. GOST 28147-89 Algorithm in EncryptionMethod The identifier for the GOST 28147-89 symmetric encryption algorithm is: urn:ietf:params:xml:ns:xmlsec-gost:algorithms:gost28147 The xenc:EncryptionMethod node may contain a child node gost: Parameters28147 specifying parameters for GOST 28147-89 algorithm. gost:Parameters28147 specifies the set of corresponding Gost28147-89- ParamSetParameters (see Section 8.1 of [CPALGS]). Encryption mode is specified by mode parameter of Gost28147-89-ParamSetParameters structure. CFB and CNT modes are RECOMMENDED to use. If gost: Parameters28147 node is missing, the application should infer algorithm parameters from other sources. If the application omits gost:Parameters28147 node, it SHOULD use parameters defined by id-Gost28147-89-CryptoPro-A-ParamSet (see Section of 10.2 [CPALGS]). Schema Definition: Leontiev, et al. Expires June 19, 2009 [Page 10] Internet-Draft GOST based Security URIs December 2008 DTD Definition: An example of a GOST 28147-89 xenc:EncryptionMethod node is: urn:oid:1.2.643.2.2.31.1< /gost:Parameters28147> 256-bit key, 64-bit Initialization Vector (IV), and optional parameters are used in GOST 28147-89 encryption algorithm. The resulting cipher text is prefixed by the IV. If included in XML output, it is then base64 encoded. 6.8. Symmetric Key Wrap Symmetric Key Wrap algorithms considered in this section are shared secret key encryption algorithms that MUST be used for symmetric keys encryption/decryption only. 6.8.1. GOST 28147-89 Key Wrap in EncryptionMethod The GOST 28147-89 Key Wrap algorithm wraps (encrypts) a key (the wrapped key, WK) under a GOST 28147-89 Key Wrap (specified in sections 6.1, 6.2 of [CPALGS]). Note: This algorithm MUST NOT be used without key agreement algorithm, because such WK is constant for every wrapping-encrypting pair. Encrypting many different keys with the same constant WK may reveal that WK. The only key agreement algorithm possible to use with GOST 28147-89 Key Wrap defined by this specification is a GOST R 34.10-2001-based key agreement (see Section 6.5). The identifier for the GOST 28147-89 Key Wrap algorithm is urn:ietf:params:xml:ns:xmlsec-gost:algorithms:kw-gost The CipherValue for such wrapped key is the base64 encoding of the [X.208-88] DER encoding of a GostR3410-KeyWrap structure. Leontiev, et al. Expires June 19, 2009 [Page 11] Internet-Draft GOST based Security URIs December 2008 ASN.1 structure: GostR3410-KeyWrap ::= SEQUENCE { encryptedKey Gost28147-89-EncryptedKey, encryptedParameters Gost28147-89-KeyWrapParameters } An example of a GOST 28147-89 Key Wrap EncryptedData node is: ... ... ... ... ... Gost28147-89-KeyWrapParameters is described in section 4.1.1 of [CPCMS]. The xenc:KA-Nonce node value of the xenc:AgreementMethod node MUST be used as ukm. The resulting wrapped key (WK) is placed in the Gost28147-89- EncryptedKey encryptedKey field, its mac (CEK_MAC) is placed in the Gost28147-89-EncryptedKey macKey field. ukm field of Gost28147-89- Leontiev, et al. Expires June 19, 2009 [Page 12] Internet-Draft GOST based Security URIs December 2008 KeyWrapParameters MUST be absent. 6.8.2. CryptoPro Key Wrap in EncryptionMethod The CryptoPro Key Wrap algorithm wraps (encrypts) a key (wrapped key, WK) under a CryptoPro Key Wrap (specified in sections 6.3, 6.4 of [CPALGS]). The identifier for the CryptoPro Key Wrap algorithms is urn:ietf:params:xml:ns:xmlsec-gost:algorithms:kw-cp The CipherValue for such wrapped key is the base64 encoding of the [X.208-88] DER encoding of a GostR3410-KeyWrap structure (see Section 6.8.1). An example of a CryptoPro Key Wrap EncryptedData node is: ... ... ... ... ... Leontiev, et al. Expires June 19, 2009 [Page 13] Internet-Draft GOST based Security URIs December 2008 The resulting wrapped key (WK) is placed in the Gost28147-89- EncryptedKey encryptedKey field, its mac (CEK_MAC) is placed in the Gost28147-89-EncryptedKey macKey field. If CryptoPro Key Wrap algorithm is combined with Key Agreement Algorithm, the xenc:KA-Nonce node value of the xenc:AgreementMethod node MUST be used as ukm. ukm field of Gost28147-89-KeyWrapParameters type must be absent. Note: The only key agreement algorithm possible to use with CryptoPro Key Wrap defined by this specification is a GOST R 34.10-2001-based key agreement (see Section 6.5). If CryptoPro Key Wrap algorithm is not combined with Key Agreement Algorithm, ukm field of Gost28147-89-KeyWrapParameters type MUST be present. 7. Specifying GOST within WS-* This section specifies the details of how to use GOST algorithms with WS-SecureConversation [WS-SECURECONVERSATION], WS-SecurityPolicy [WS-SECURITYPOLICY] and WS-Trust [WS-TRUST]. 7.1. GOST Algorithm Suite for WS-SecurityPolicy This specification defines a new possible value for an [Algorithm Suite] property of a Security Binding (see section 6.1 of [WS-SECURITYPOLICY]). The new value is BasicGost. BasicGost Algorithm Suite defines the following values for operations and properties (without line breaks in URIs): [Sym Sig] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:hmac-gostr3411 [Asym Sig] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:gostr34102001- gostr3411 [Dig] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:gostr3411 [Enc] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:gost28147 [Sym KW] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:kw-cp [Asym KW] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:transport- gost2001 Leontiev, et al. Expires June 19, 2009 [Page 14] Internet-Draft GOST based Security URIs December 2008 [Comp Key] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:ck-p-gostr3411 [Enc KD] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:dk-p-gostr3411 [Sig KD] urn:ietf:params:xml:ns:xmlsec-gost:algorithms:dk-p-gostr3411 [Min SKL] 256 [Max SKL] 256 [Min AKL] 512 [Max AKL] 512 Note: For definitions of [Comp Key], [Enc KD] and [Sig KD] algorithms see below. To indicate a requirement to use GOST Algorithm Suite defined above conforming implementaions MUST place gost:BasicGost node in sp: AlgorithmSuite Assertion (see section 7.1 of [WS-SECURITYPOLICY]). Schema Definition: DTD Definition: An example of a GOST Algorithm Suite in sp:AlgorithmSuite Assertion: 8. Security Considerations Conforming applications MUST use unique values for ukm and iv. Recipients MAY verify that ukm and iv specified by the sender are unique. Applications SHOULD verify signature values, subject public keys and algorithm parameters to conform to [GOSTR341001], standard before Leontiev, et al. Expires June 19, 2009 [Page 15] Internet-Draft GOST based Security URIs December 2008 using them. Cryptographic algorithm parameters affect algorithm strength. Using parameters not listed in [CPALGS] is NOT RECOMMENDED (see the Security Considerations section of [CPALGS]). Using the same key for signature and key derivation is NOT RECOMMENDED. It is NOT RECOMMENDED to use XML encryption without XML signature or HMAC. 9. IANA Considerations This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. IANA has registered two URI assignments. 9.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:xmlsec-gost URI: urn:ietf:params:xml:ns:xmlsec-gost Registrant Contact: See the "Authors' Addresses" section of this document. XML: None. Namespace URIs do not represent an XML specification. 9.2. Schema Registration URI: urn:ietf:params:xml:schema:xmlsec-gost Registrant Contact: See the "Authors' Addresses" section of this document. XML: The XML can be found in Appendix A. 10. References 10.1. Normative references [CPALGS] Popov, V., Kurepkin, I., and S. Leontiev, "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", RFC 4357, January 2006. Leontiev, et al. Expires June 19, 2009 [Page 16] Internet-Draft GOST based Security URIs December 2008 [CPCMS] Leontiev, S. and G. Chudov, "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 4490, May 2006. [CPPK] Leontiev, S. and D. Shefanovski, "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", RFC 4491, May 2006. [GOST28147] Government Committee of the USSR for Standards, "Cryptographic Protection for Data Processing System, Gosudarstvennyi Standard of USSR (In Russian)", GOST 28147-89, 1989. [GOST3431004] Council for Standardization, Metrology and Certification of the Commonwealth of Independence States (EASC), Minsk, "Information technology. Cryptographic Data Security. Formation and verification processes of (electronic) digital signature based on Asymmetric Cryptographic Algorithm (In Russian)", GOST 34.310-2004, 2004. [GOST3431195] Council for Standardization, Metrology and Certification of the Commonwealth of Independence States (EASC), Minsk, "Information technology. Cryptographic Data Security. Cashing function (In Russian)", GOST 34.311-95, 1995. [GOSTR341001] Government Committee of the Russia for Standards, "Information technology. Cryptographic Data Security.Signature and verification processes of [electronic] digital signature, Gosudarstvennyi Standard of Russian Federation (In Russian)", GOST R 34.10-2001, 2001. [GOSTR341194] Government Committee of the Russia for Standards, "Information technology. Cryptographic Data Security. Hashing function, Gosudarstvennyi Standard of Russian Federation (In Russian)", GOST R 34.11-94, 1994. [HMAC] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- Hashing for Message Authentication", RFC 2104, February 1997. Leontiev, et al. Expires June 19, 2009 [Page 17] Internet-Draft GOST based Security URIs December 2008 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006. [WS-POLICY] Vedamuthu, A., Orchard, D., Hirsch, F., Hondo, M., Yendluri, P., Boubez, T., and Ue. Yalcinalp, "Web Services Policy 1.5 - Framework", W3C REC-ws-policy, September 2007, . [WS-SECURECONVERSATION] Lawrence, K. and C. Kaler, "WS-SecureConversation 1.3", OASIS Standard ws-secureconversation-1.3-os, March 2007, < http://docs.oasis-open.org/ws-sx/ws-secureconversation/ 200512/ws-secureconversation-1.3-os.html>. [WS-SECURITYPOLICY] Lawrence, K. and C. Kaler, "WS-SecurityPolicy 1.2", OASIS Standard ws-securitypolicy-1.2-spec-os, July 2007, . [WS-TRUST] Lawrence, K. and C. Kaler, "WS-Trust 1.3", OASIS Standard ws-trust-1.3-os, March 2007, . [X.208-88] International International Telephone and Telegraph Consultative Committee, "Specification of Abstract Syntax Notation One (ASN.1)", CCITT Recommendation X.208, November 1988. [XML-NS] Bray, T., Hollander, D., Layman, A., and R. Tobin, "Namespaces in XML (Second Edition)", W3C REC-xml-names, August 2006, . Leontiev, et al. Expires June 19, 2009 [Page 18] Internet-Draft GOST based Security URIs December 2008 [XML-SCHEMA-1] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML Schema Part 1: Structures Second Edition", W3C REC- xmlschema-1, October 2004, . [XML-SCHEMA-2] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Second Edition", W3C REC-xmlschema-2, October 2004, . [XMLDSIG] Eastlake, D., Reagle, J., and D. Solo, "(Extensible Markup Language) XML-Signature Syntax and Processing", RFC 3275, March 2002. [XMLENC-CORE] Eastlake, D. and J. Reagle , "XML Encryption Syntax and Processing", W3C Candidate Recommendation xmlenc-core, August 2002, . 10.2. Informative references [RFC4134] Hoffman, P., "Examples of S/MIME Messages", RFC 4134, July 2005. [URNOID] Mealling, M., "A URN Namespace of Object Identifiers", RFC 3061, February 2001. [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth Edition)", W3C REC-xml, August 2006, . Appendix A. Aggregate XML Schema ]> Leontiev, et al. Expires June 19, 2009 [Page 20] Internet-Draft GOST based Security URIs December 2008 Appendix B. Aggregate DTD Appendix C. Examples Examples here are stored in the same format as the examples in [RFC4134] and can be extracted using the same program. If you want to extract without the program, copy all the lines between the "|>" and "|<" markers, remove any page breaks, and remove the "|" in the first column of each line. The result is a valid Base64 blob that can be processed by any Base64 decoder. C.1. Signed document This sample contain the signed XML document using the sample certificate from Section 4.2 of [CPPK]. Leontiev, et al. Expires June 19, 2009 [Page 21] Internet-Draft GOST based Security URIs December 2008 |>XmlDocSigned2001.xml |PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz48Q3J5cHRvUHJv |WE1MIFNpZ25lZD0idHJ1ZSI+SGVyZSBpcyBzb21lIGRhdGEgdG8gc2lnbi48U2ln |bmF0dXJlIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3htbGRzaWcj |Ij48U2lnbmVkSW5mbz48Q2Fub25pY2FsaXphdGlvbk1ldGhvZCBBbGdvcml0aG09 |Imh0dHA6Ly93d3cudzMub3JnL1RSLzIwMDEvUkVDLXhtbC1jMTRuLTIwMDEwMzE1 |IiAvPjxTaWduYXR1cmVNZXRob2QgQWxnb3JpdGhtPSJodHRwOi8vd3d3LnczLm9y |Zy8yMDAxLzA0L3htbGRzaWctbW9yZSNnb3N0cjM0MTAyMDAxLWdvc3RyMzQxMSIg |Lz48UmVmZXJlbmNlIFVSST0iIj48VHJhbnNmb3Jtcz48VHJhbnNmb3JtIEFsZ29y |aXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMC8wOS94bWxkc2lnI2VudmVsb3Bl |ZC1zaWduYXR1cmUiIC8+PC9UcmFuc2Zvcm1zPjxEaWdlc3RNZXRob2QgQWxnb3Jp |dGhtPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxLzA0L3htbGRzaWctbW9yZSNnb3N0 |cjM0MTEiIC8+PERpZ2VzdFZhbHVlPi9Kd3RRc3Z5NWsvUjBWZUx6ZG0ySWlqUEJ0 |U0o1cEpSalQ5RlVRSEV5VGc9PC9EaWdlc3RWYWx1ZT48L1JlZmVyZW5jZT48L1Np |Z25lZEluZm8+PFNpZ25hdHVyZVZhbHVlPkZjYjNxNGlCdmRmZ1lvN245NUdhUUN1 |ZDkxWVA3dzhvVjAzUjZ6a1JEZGxjK0RuQ2MwcjlNc0E1YS9iaFlDeVdQZC9jRVU4 |K3FZRnJ5SmJjaXJ5d0hBPT08L1NpZ25hdHVyZVZhbHVlPjxLZXlJbmZvPjxYNTA5 |RGF0YT48WDUwOUNlcnRpZmljYXRlPk1JSUIwRENDQVg4Q0VDdjF4aDdDRWIwWHg5 |elVZbWEwTGlFd0NBWUdLb1VEQWdJRE1HMHhIekFkQmdOVkJBTU1Ga2R2YzNSU016 |UXhNQzB5TURBeElHVjRZVzF3YkdVeEVqQVFCZ05WQkFvTUNVTnllWEIwYjFCeWJ6 |RUxNQWtHQTFVRUJoTUNVbFV4S1RBbkJna3Foa2lHOXcwQkNRRVdHa2R2YzNSU016 |UXhNQzB5TURBeFFHVjRZVzF3YkdVdVkyOXRNQjRYRFRBMU1EZ3hOakUwTVRneU1G |b1hEVEUxTURneE5qRTBNVGd5TUZvd2JURWZNQjBHQTFVRUF3d1dSMjl6ZEZJek5E |RXdMVEl3TURFZ1pYaGhiWEJzWlRFU01CQUdBMVVFQ2d3SlEzSjVjSFJ2VUhKdk1R |c3dDUVlEVlFRR0V3SlNWVEVwTUNjR0NTcUdTSWIzRFFFSkFSWWFSMjl6ZEZJek5E |RXdMVEl3TURGQVpYaGhiWEJzWlM1amIyMHdZekFjQmdZcWhRTUNBaE13RWdZSEtv |VURBZ0lrQUFZSEtvVURBZ0llQVFOREFBUkFoSlZvZFdBQ0drQjFDTTBUakRHSkxQ |M2xCUU42UTF6MGJTc1A1MDh5ZmxlUDY4d1d1WldJQTlDYWZJV3VEK1NONnFhN2Zs |Ykh5N0RmRDJhOHl1b2FZREFJQmdZcWhRTUNBZ01EUVFBOEw4a0pSTGNucWV5bjFl |bjdVMjNTdzZwa2ZFUXUzdTB4RmtWUHZGUS8zY0hlRjI2TkcreHh0WlB6M1RhVFZY |ZG9pWWtYWWlEMDJyRXgxYlVjTTk3aTwvWDUwOUNlcnRpZmljYXRlPjwvWDUwOURh |dGE+PC9LZXlJbmZvPjwvU2lnbmF0dXJlPjwvQ3J5cHRvUHJvWE1MPg== |