Network Working Group S. Blake-Wilson
Request for Comments: 4050 BCI
Category: Informational G. Karlinger
CIO Austria
T. Kobayashi
NTT
Y. Wang
UNCC
April 2005
Network Working Group S. Blake-Wilson
Request for Comments: 4050 BCI
Category: Informational G. Karlinger
CIO Austria
T. Kobayashi
NTT
Y. Wang
UNCC
April 2005
Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures
使用椭圆曲线签名算法（ECDSA）进行XML数字签名
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
IESG Note
IESG注释
This document is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this document for any purpose, and in particular notes that it has not had IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment.
本文件不适用于任何级别的互联网标准。IETF不承认对本文件适用于任何目的的任何了解，特别注意到IETF没有对安全性、拥塞控制或与已部署协议的不当交互等事项进行审查。RFC编辑已自行决定发布本文件。本文档的读者在评估其实施和部署价值时应谨慎。
Abstract
摘要
This document specifies how to use Elliptic Curve Digital Signature Algorithm (ECDSA) with XML Signatures. The mechanism specified provides integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or included by reference.
本文档指定如何将椭圆曲线数字签名算法（ECDSA）与XML签名结合使用。指定的机制为任何类型的数据提供完整性、消息身份验证和/或签名者身份验证服务，无论这些数据位于包含签名的XML中还是通过引用包含的XML中。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. ECDSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Specifying ECDSA within XMLDSIG . . . . . . . . . . . . . . . 3
3.1. Version, Namespaces, and Identifiers . . . . . . . . . . 3
3.2. XML Schema Preamble and DTD Replacement. . . . . . . . . 4
3.2.1. XML Schema Preamble. . . . . . . . . . . . . . . 4
3.2.2. DTD Replacement. . . . . . . . . . . . . . . . . 4
3.3. ECDSA Signatures . . . . . . . . . . . . . . . . . . . . 4
3.4. ECDSA Key Values . . . . . . . . . . . . . . . . . . . . 4
3.4.1. Key Value Root Element . . . . . . . . . . . . . 4
3.4.2. EC Domain Parameters . . . . . . . . . . . . . . 5
3.4.2.1. Field Parameters . . . . . . . . . . . 6
3.4.2.2. Curve Parameters . . . . . . . . . . . 8
3.4.2.3. Base Point Parameters. . . . . . . . . 9
3.4.3. EC Points . . . . . . . . . . . . . . . . . . . 10
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. Normative References . . . . . . . . . . . . . . . . . . . . . 11
6. Informative References . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
Appendix A: Aggregate XML Schema . . . . . . . . . . . . . . . . . 14
Appendix B: Aggregate DTD. . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. ECDSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Specifying ECDSA within XMLDSIG . . . . . . . . . . . . . . . 3
3.1. Version, Namespaces, and Identifiers . . . . . . . . . . 3
3.2. XML Schema Preamble and DTD Replacement. . . . . . . . . 4
3.2.1. XML Schema Preamble. . . . . . . . . . . . . . . 4
3.2.2. DTD Replacement. . . . . . . . . . . . . . . . . 4
3.3. ECDSA Signatures . . . . . . . . . . . . . . . . . . . . 4
3.4. ECDSA Key Values . . . . . . . . . . . . . . . . . . . . 4
3.4.1. Key Value Root Element . . . . . . . . . . . . . 4
3.4.2. EC Domain Parameters . . . . . . . . . . . . . . 5
3.4.2.1. Field Parameters . . . . . . . . . . . 6
3.4.2.2. Curve Parameters . . . . . . . . . . . 8
3.4.2.3. Base Point Parameters. . . . . . . . . 9
3.4.3. EC Points . . . . . . . . . . . . . . . . . . . 10
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. Normative References . . . . . . . . . . . . . . . . . . . . . 11
6. Informative References . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
Appendix A: Aggregate XML Schema . . . . . . . . . . . . . . . . . 14
Appendix B: Aggregate DTD. . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 19
This document specifies how to use the Elliptic Curve Digital Signature Algorithm (ECDSA) with XML signatures, as specified in [XMLDSIG]. [XMLDSIG] defines only two digital signature methods: RSA and DSA (DSS) signatures. This document introduces ECDSA signatures as an additional method.
本文档指定了如何使用椭圆曲线数字签名算法（ECDSA）和XML签名，如[XMLDSIG]中所述。[XMLDSIG]只定义了两种数字签名方法：RSA和DSA（DSS）签名。本文档介绍ECDSA签名作为一种附加方法。
This document uses both XML Schemas [XML-schema] (normative) and DTDs [XML] (informational) to specify the corresponding XML structures.
本文档使用XML模式[XML模式]（规范性）和DTD[XML]（信息性）来指定相应的XML结构。
The Elliptic Curve Digital Signature Algorithm (ECDSA) is the elliptic curve analogue of the DSA (DSS) signature method [FIPS-186-2]. It is defined in the ANSI X9.62 standard [X9.62]. Other compatible specifications include FIPS 186-2 [FIPS-186-2], IEEE 1363 [IEEE1363], IEEE 1363a [IEEE1363a], and SEC1 [SEC1]. [RFC3279] describes ways to carry ECDSA keys in X.509 certificates. [FIPS-186-2], [SEC2], and [X9.62] provide recommended elliptic curve domain parameters for use with ECDSA.
椭圆曲线数字签名算法（ECDSA）是DSA（DSS）签名方法的椭圆曲线模拟[FIPS-186-2]。它在ANSI X9.62标准[X9.62]中定义。其他兼容规范包括FIPS 186-2[FIPS-186-2]、IEEE 1363[IEEE1363]、IEEE 1363a[IEEE1363a]和SEC1[SEC1]。[RFC3279]描述了在X.509证书中携带ECDSA密钥的方法。[FIPS-186-2]、[SEC2]和[X9.62]提供了与ECDSA一起使用的推荐椭圆曲线域参数。
Like DSA, ECDSA incorporates the use of a hash function. Currently, the only hash function defined for use with ECDSA is the SHA-1 message digest algorithm [FIPS-180-1].
与DSA一样，ECDSA也使用了哈希函数。目前，唯一定义用于ECDSA的哈希函数是SHA-1消息摘要算法[FIPS-180-1]。
ECDSA signatures are smaller than RSA signatures of similar cryptographic strength. ECDSA public keys (and certificates) are smaller than similar strength DSA keys and result in improved communication efficiency. On many platforms, ECDSA operations can be computed faster than similar strength RSA or DSA operations (see [KEYS] for a security analysis of key sizes across public key algorithms). These advantages of signature size, bandwidth, and computational efficiency may make ECDSA an attractive choice for XMLDSIG implementations.
ECDSA签名比具有类似加密强度的RSA签名小。ECDSA公钥（和证书）比强度相似的DSA密钥小，从而提高了通信效率。在许多平台上，ECDSA操作的计算速度比类似强度的RSA或DSA操作要快（请参阅[KEYS]，了解公钥算法中密钥大小的安全性分析）。签名大小、带宽和计算效率的这些优势可能使ECDSA成为XMLDSIG实现的一个有吸引力的选择。
This section specifies how to use ECDSA with XML Signature Syntax and Processing [XMLDSIG]. It relies heavily on the syntax and namespace defined in [XMLDSIG].
本节指定如何将ECDSA与XML签名语法和处理[XMLDSIG]结合使用。它严重依赖于[XMLDSIG]中定义的语法和名称空间。
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 that MUST be used by implementations of this (dated) specification is:
此（已注明日期）规范的实现必须使用的XML命名空间[XML ns]URI为：
http://www.w3.org/2001/04/xmldsig-more#
http://www.w3.org/2001/04/xmldsig-more#
Elements in the namespace of the [XMLDSIG] specification are marked by using the namespace prefix "dsig" in the remaining sections of this document.
[XMLDSIG]规范名称空间中的元素在本文档其余部分中使用名称空间前缀“dsig”进行标记。
The identifier for the ECDSA signature algorithm as defined in [Eastlake] is:
[Eastlake]中定义的ECDSA签名算法的标识符为：
http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1
http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1
The subsequent preamble is to be used with the XML Schema definitions given in the remaining sections of this document.
后面的序言将与本文档其余部分中给出的XML模式定义一起使用。
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:ecdsa="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified"
version="0.2">
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:ecdsa="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified"
version="0.2">
To include ECDSA in XML-signature syntax, the following definition of the entity Key.ANY SHOULD replace the one in [XMLDSIG]:
要在XML签名语法中包含ECDSA，以下实体键.ANY的定义应替换[XMLDSIG]中的定义：
<!ENTITY % KeyValue.ANY '| ecdsa:ECDSAKeyValue'>
<!ENTITY % KeyValue.ANY '| ecdsa:ECDSAKeyValue'>
The input to the ECDSA algorithm is the canonicalized representation of the dsig:SignedInfo element as specified in Section 3 of [XMLDSIG].
ECDSA算法的输入是[XMLDSIG]第3节中指定的dsig:SignedInfo元素的规范化表示。
The output of the ECDSA algorithm consists of a pair of integers usually referred by the pair (r, s). The signature value (text value of element dsig:SignatureValue - see section 4.2 of [XMLDSIG]) consists of the base64 encoding of the concatenation of two octet-streams that respectively result from the octet-encoding of the values r and s. This concatenation is described in section E3.1 of [IEEE1363].
ECDSA算法的输出由一对整数组成，通常由该对（r，s）引用。签名值（元素dsig的文本值：SignatureValue-参见[XMLDSIG]的第4.2节）由两个八位字节流串联的base64编码组成，这两个八位字节流分别由值r和s的八位字节编码产生。[IEEE1363]第E3.1节描述了这种连接。
The syntax used for ECDSA key values closely follows the ASN.1 syntax defined in ANSI X9.62 [X9.62].
ECDSA键值使用的语法严格遵循ANSI X9.62[X9.62]中定义的ASN.1语法。
The element ECDSAKeyValue is used for encoding ECDSA public keys. For use with XMLDSIG, simply use this element inside dsig:KeyValue (such as the predefined elements dsig:RSAKeyValue or dsig:DSAKeyValue).
元素ECDSAKeyValue用于编码ECDSA公钥。要与XMLDSIG一起使用，只需在dsig:KeyValue中使用此元素（例如预定义的元素dsig:RSAKeyValue或dsig:DSAKeyValue）。
The element consists of an optional subelement DomainParameters and the mandatory subelement PublicKey. If Domainparameters is missing, the application implicitly knows about it from other means.
元素由可选的子元素DomainParameters和必需的子元素PublicKey组成。如果缺少Domainparameters，应用程序将通过其他方式隐式地了解它。
Schema Definition:
架构定义：
<xs:element name="ECDSAKeyValue" type="ecdsa:ECDSAKeyValueType"/>
<xs:complexType name="ECDSAKeyValueType">
<xs:sequence>
<xs:element name="DomainParameters" type="ecdsa:DomainParamsType"
minOccurs="0"/>
<xs:element name="PublicKey" type="ecdsa:ECPointType"/>
</xs:sequence>
</xs:complexType>
<xs:element name="ECDSAKeyValue" type="ecdsa:ECDSAKeyValueType"/>
<xs:complexType name="ECDSAKeyValueType">
<xs:sequence>
<xs:element name="DomainParameters" type="ecdsa:DomainParamsType"
minOccurs="0"/>
<xs:element name="PublicKey" type="ecdsa:ECPointType"/>
</xs:sequence>
</xs:complexType>
DTD Definition:
DTD定义：
<!ELEMENT ECDSAKeyValue (DomainParameters?, PublicKey)>
<!ELEMENT PublicKey (X, Y)?>
<!ELEMENT X EMPTY>
<!ATTLIST X Value CDATA #REQUIRED>
<!ELEMENT Y EMPTY>
<!ATTLIST Y Value CDATA #REQUIRED>
<!ELEMENT ECDSAKeyValue (DomainParameters?, PublicKey)>
<!ELEMENT PublicKey (X, Y)?>
<!ELEMENT X EMPTY>
<!ATTLIST X Value CDATA #REQUIRED>
<!ELEMENT Y EMPTY>
<!ATTLIST Y Value CDATA #REQUIRED>
Domain parameters can be encoded either explicitly using element ExplicitParams, or by reference using element NamedCurve. The latter simply consists of an attribute named URN, which bears a uniform resource name as its value. For the named curves of standards like [X9.62], [FIPS-186-2], or [SEC2], the OIDs of these curves SHOULD be used in this attribute, e.g., URN="urn:oid:1.2.840.10045.3.1.1". The mechanism for encoding OIDs in URNs is shown in [RFC3061].
域参数可以使用元素EXPLICITPAMS显式编码，也可以使用元素名称CURVE通过引用编码。后者只是由一个名为URN的属性组成，该属性的值为统一的资源名。对于[X9.62]、[FIPS-186-2]或[SEC2]等标准的命名曲线，应在该属性中使用这些曲线的oid，例如URN=“URN:oid:1.2.840.10045.3.1.1”。在URN中编码OID的机制如[RFC3061]所示。
Schema Definition:
架构定义：
<xs:complexType name="DomainParamsType">
<xs:choice>
<xs:element name="ExplicitParams"
type="ecdsa:ExplicitParamsType"/>
<xs:element name="NamedCurve">
<xs:complexType>
<xs:attribute name="URN" type="xs:anyURI" use="required"/>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
<xs:complexType name="DomainParamsType">
<xs:choice>
<xs:element name="ExplicitParams"
type="ecdsa:ExplicitParamsType"/>
<xs:element name="NamedCurve">
<xs:complexType>
<xs:attribute name="URN" type="xs:anyURI" use="required"/>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
DTD Definition:
DTD定义：
<!ELEMENT DomainParameters (ExplicitParams | NamedCurve)>
<!ELEMENT NamedCurve EMPTY>
<!ATTLIST NamedCurve URN CDATA #REQUIRED>
<!ELEMENT DomainParameters (ExplicitParams | NamedCurve)>
<!ELEMENT NamedCurve EMPTY>
<!ATTLIST NamedCurve URN CDATA #REQUIRED>
The element ExplicitParams is used for explicit encoding of domain parameters. It contains three subelements: FieldParams describes the underlying field, CurveParams describes the elliptic curve, and BasePointParams describes the base point of the elliptic curve.
元素显式图用于域参数的显式编码。它包含三个子元素：FieldParams描述基础字段，CurveParams描述椭圆曲线，BasePointParams描述椭圆曲线的基点。
Schema Definition:
架构定义：
<xs:complexType name="ExplicitParamsType">
<xs:sequence>
<xs:element name="FieldParams" type="ecdsa:FieldParamsType"/>
<xs:element name="CurveParams" type="ecdsa:CurveParamsType"/>
<xs:element name="BasePointParams"
type="ecdsa:BasePointParamsType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ExplicitParamsType">
<xs:sequence>
<xs:element name="FieldParams" type="ecdsa:FieldParamsType"/>
<xs:element name="CurveParams" type="ecdsa:CurveParamsType"/>
<xs:element name="BasePointParams"
type="ecdsa:BasePointParamsType"/>
</xs:sequence>
</xs:complexType>
DTD Definition:
DTD定义：
<!ELEMENT ExplicitParams (FieldParams, CurveParams, BasePointParams)>
<!ELEMENT ExplicitParams (FieldParams, CurveParams, BasePointParams)>
The element FieldParams is used for encoding field parameters. The corresponding XML Schema type FieldParamsType is declared abstract and will be extended by specialized types for prime field, characteristic two field, and odd characteristic extension fields parameters.
元素FieldParams用于编码字段参数。相应的XML模式类型FieldParamsType被声明为抽象类型，并将通过专用类型对prime字段、characteristic two字段和奇数characteristic extension fields参数进行扩展。
The XML Schema type PrimeFieldParamsType is derived from the FieldParamsType and is used for encoding prime field parameters. The type contains the order of the prime field as its single subelement P.
XML模式类型PrimeFieldParamsType是从FieldParamsType派生的，用于对prime字段参数进行编码。该类型包含素数字段的顺序作为其单个子元素P。
The XML Schema type CharTwoFieldParamsType is derived from FieldParamsType and is used for encoding parameters of a characteristic two field. It is again an abstract type and will be extended by specialized types for trinomial and pentanomial base fields. F2m Gaussian Normal Base fields are not supported by this specification to relieve interoperability. Common to both specialized types is the element M, the extension degree of the field.
XML模式类型CharTwoFieldParamsType派生自FieldParamsType，用于对特征双字段的参数进行编码。它也是一种抽象类型，并将通过三项式和五项式基域的专门类型进行扩展。为了减轻互操作性，本规范不支持F2m高斯标准基域。这两种特殊类型的共同点是元素M，字段的扩展度。
The XML Schema type TnBFieldParamsType is derived from the CharTwoFieldParamsType and is used for encoding trinomial base fields. It adds the single element K, which represents the integer k, where x^m + x^k + 1 is the reduction polynomial.
XML模式类型TnBFieldParamsType派生自CharTwoFieldParamsType，用于编码三项式基字段。它添加单个元素K，表示整数K，其中x^m+x^K+1是约化多项式。
The XML Schema type PnBFieldParamsType is derived from the CharTwoFieldParamsType and is used for encoding pentanomial base fields. It adds the three elements K1, K2 and K3, which represent the integers k1, k2 and k3 respectively, where x^m + x^k3 + x^k2 + x^k1 + 1 is the reduction polynomial.
XML模式类型PnBFieldParamsType派生自CharTwoFieldParamsType，用于编码五项式基字段。它将三个元素K1、K2和K3相加，分别表示整数K1、K2和K3，其中x^m+x^K3+x^K2+x^K1+1是约化多项式。
The XML Schema type OddCharExtensionFieldParamsType is derived from the FieldParamsType and is used for encoding parameters of an odd characteristic extension field. This type contains two elements: M, which represents the extension degree of the field m, and W, which represents the integer w, where x^m - w is the reduction polynomial.
XML架构类型OddCharExtensionFieldParamsType派生自FieldParamsType，用于编码奇数特征扩展字段的参数。此类型包含两个元素：M，表示字段M的扩展度；W，表示整数W，其中x^M-W是约化多项式。
Schema Definition:
架构定义：
<xs:complexType name="FieldParamsType" abstract="true"/>
<xs:complexType name="FieldParamsType" abstract="true"/>
<xs:complexType name="PrimeFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="P" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="PrimeFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="P" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldParamsType" abstract="true">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldParamsType" abstract="true">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OddCharExtensionFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
<xs:element name="W" type="xs:positiveInteger"/>
</xs:sequence>
<xs:complexType name="OddCharExtensionFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
<xs:element name="W" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="TnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="TnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="PnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K1" type="xs:positiveInteger"/>
<xs:element name="K2" type="xs:positiveInteger"/>
<xs:element name="K3" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="PnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K1" type="xs:positiveInteger"/>
<xs:element name="K2" type="xs:positiveInteger"/>
<xs:element name="K3" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
DTD Definition:
DTD定义：
<!ELEMENT FieldParams (P | (M, K) | (M, K1, K2, K3) | (M, W))>
<!ELEMENT P (#PCDATA)>
<!ELEMENT M (#PCDATA)>
<!ELEMENT K (#PCDATA)>
<!ELEMENT K1 (#PCDATA)>
<!ELEMENT K2 (#PCDATA)>
<!ELEMENT K3 (#PCDATA)>
<!ELEMENT W (#PCDATA)>
<!ELEMENT FieldParams (P | (M, K) | (M, K1, K2, K3) | (M, W))>
<!ELEMENT P (#PCDATA)>
<!ELEMENT M (#PCDATA)>
<!ELEMENT K (#PCDATA)>
<!ELEMENT K1 (#PCDATA)>
<!ELEMENT K2 (#PCDATA)>
<!ELEMENT K3 (#PCDATA)>
<!ELEMENT W (#PCDATA)>
The element CurveParams is used for encoding parameters of the elliptic curve. The corresponding XML Schema type CurveParamsType bears the elements A and B representing the coefficients a and b of the elliptic curve. According to the algorithm specified in annex A3.3 of [X9.62], the optional element Seed contains the value used to derive the coefficients of a randomly generated elliptic curve.
元素曲线图用于对椭圆曲线的参数进行编码。对应的XML模式类型CurveParamsType包含表示椭圆曲线的系数A和B的元素A和B。根据[X9.62]附录A3.3中规定的算法，可选元素种子包含用于推导随机生成的椭圆曲线系数的值。
Schema Definition:
架构定义：
<xs:complexType name="CurveParamsType">
<xs:sequence>
<xs:element name="A" type="ecdsa:FieldElemType"/>
<xs:element name="B" type="ecdsa:FieldElemType"/>
<xs:element name="Seed" type="xs:hexBinary" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="CurveParamsType">
<xs:sequence>
<xs:element name="A" type="ecdsa:FieldElemType"/>
<xs:element name="B" type="ecdsa:FieldElemType"/>
<xs:element name="Seed" type="xs:hexBinary" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
DTD Definition:
DTD定义：
<!ELEMENT CurveParams (A, B, Seed?)>
<!ELEMENT A EMPTY>
<!ATTLIST A Value CDATA #REQUIRED>
<!ELEMENT B EMPTY>
<!ATTLIST B Value CDATA #REQUIRED>
<!ELEMENT Seed (#PCDATA)>
<!ELEMENT CurveParams (A, B, Seed?)>
<!ELEMENT A EMPTY>
<!ATTLIST A Value CDATA #REQUIRED>
<!ELEMENT B EMPTY>
<!ATTLIST B Value CDATA #REQUIRED>
<!ELEMENT Seed (#PCDATA)>
The element BasePointParams is used for encoding parameters regarding the base point of the elliptic curve. BasePoint represents the base point itself, Order provides the order of the base point, and Cofactor optionally provides the cofactor of the base point.
元素BasePointParams用于编码有关椭圆曲线基点的参数。基点表示基点本身，顺序提供基点的顺序，辅因子可选地提供基点的辅因子。
Schema Definition:
架构定义：
<xs:complexType name="BasePointParamsType">
<xs:sequence>
<xs:element name="BasePoint" type="ecdsa:ECPointType"/>
<xs:element name="Order" type="xs:positiveInteger"/>
<xs:element name="Cofactor" type="xs:positiveInteger"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="BasePointParamsType">
<xs:sequence>
<xs:element name="BasePoint" type="ecdsa:ECPointType"/>
<xs:element name="Order" type="xs:positiveInteger"/>
<xs:element name="Cofactor" type="xs:positiveInteger"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
DTD Definition:
DTD定义：
<!ELEMENT BasePointParams (BasePoint, Order, Cofactor?)>
<!ELEMENT BasePoint (X, Y)?>
<!ELEMENT Order (#PCDATA)>
<!ELEMENT Cofactor (#PCDATA)>
<!ELEMENT BasePointParams (BasePoint, Order, Cofactor?)>
<!ELEMENT BasePoint (X, Y)?>
<!ELEMENT Order (#PCDATA)>
<!ELEMENT Cofactor (#PCDATA)>
The XML Schema type ECPointType is used for encoding a point on the elliptic curve. It consists of the subelements X and Y, providing the x and y coordinates of the point. Point compression representation is not supported by this specification for the sake of simple design.
XML模式类型ECPointType用于对椭圆曲线上的点进行编码。它由子元素X和Y组成，提供点的X和Y坐标。为了简单的设计，本规范不支持点压缩表示。
The point at infinity is encoded by omitting both elements X and Y.
无穷远处的点通过省略元素X和Y进行编码。
The subelements X and Y are of type FieldElemType. This is an abstract type for encoding elements of the elliptic curves underlying field and is extended by specialized types for prime field elements and characteristic two field elements.
子元素X和Y的类型为FieldElemType。这是一种抽象类型，用于编码椭圆曲线基础字段的元素，并通过素字段元素和特征双字段元素的专用类型进行扩展。
The XML Schema type PrimeFieldElemType is used for encoding prime field elements. It contains a single attribute named Value whose value represents the field element as an integer.
XML模式类型PrimeFieldElemType用于编码prime字段元素。它包含一个名为Value的属性，其值将field元素表示为整数。
The XML Schema type CharTwoFieldElemType is used for encoding characteristic two field elements. It contains a single attribute named Value whose value represents the field element as an octet string. The octet string must be composed as shown in paragraph 2 of section 4.3.3 of [X9.62].
XML模式类型CharTwoFieldElemType用于编码两个字段元素。它包含一个名为Value的属性，该属性的值将字段元素表示为八位字节字符串。八进制字符串必须按照[X9.62]第4.3.3节第2段所示组成。
The XML Schema type OddCharExtensionFieldElemType is used for encoding odd characteristic extension field elements. It contains a single attribute named Value whose value represents the field element as an integer. The integer must be composed as shown in section 5.3.3 of [IEEE1363a].
XML模式类型OddCharExtensionFileType用于编码奇数特征扩展字段元素。它包含一个名为Value的属性，其值将field元素表示为整数。整数必须按照[IEEE1363a]第5.3.3节所示进行组合。
Schema Definition:
架构定义：
<xs:complexType name="ECPointType">
<xs:sequence minOccurs="0">
<xs:element name="X" type="ecdsa:FieldElemType"/>
<xs:element name="Y" type="ecdsa:FieldElemType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="FieldElemType" abstract="true"/>
<xs:complexType name="ECPointType">
<xs:sequence minOccurs="0">
<xs:element name="X" type="ecdsa:FieldElemType"/>
<xs:element name="Y" type="ecdsa:FieldElemType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="FieldElemType" abstract="true"/>
<xs:complexType name="PrimeFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="PrimeFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:hexBinary"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:hexBinary"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OddCharExtensionFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OddCharExtensionFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Implementers should ensure that appropriate security measures are in place when they deploy ECDSA within XMLDSIG. In particular, the security of ECDSA requires careful selection of both key sizes and elliptic curve domain parameters. Selection guidelines for these parameters and some specific recommended curves that are considered safe are provided in [X9.62], [FIPS-186-2], and [SEC2]. For further security discussion, see [XMLDSIG].
实现者在XMLDSIG中部署ECDSA时，应该确保有适当的安全措施。特别是，ECDSA的安全性要求仔细选择密钥大小和椭圆曲线域参数。[X9.62]、[FIPS-186-2]和[SEC2]中提供了这些参数和一些被认为安全的特定推荐曲线的选择指南。有关进一步的安全性讨论，请参阅[XMLDSIG]。
[Eastlake] Eastlake 3rd, D., "Additional XML Security Uniform Resource Identifiers (URIs)", RFC 4051, April 2005.
[Eastlake]Eastlake 3rd，D.，“附加XML安全统一资源标识符（URI）”，RFC 4051，2005年4月。
[X9.62] American National Standards Institute. ANSI X9.62-1998, Public Key Cryptography for the Financial Services Industry: The Elliptic Curve Digital Signature Algorithm. January 1999.
[X9.62]美国国家标准协会。ANSI X9.62-1998，金融服务业的公钥加密：椭圆曲线数字签名算法。1999年1月。
[XMLDSIG] Eastlake 3rd, D., Reagle, J., and D. Solo, "(Extensible Markup Language) XML-Signature Syntax and Processing", RFC 3275, March 2002.
[XMLDSIG]Eastlake 3rd，D.，Reagle，J.，和D.Solo，“（可扩展标记语言）XML签名语法和处理”，RFC 3275，2002年3月。
[XML-schema] Beech, D., Maloney, M., Mendelsohn, N., and Thompson,
H., XML Schema Part 1: Structures, W3C Recommendation,
May 2001. http://www.w3.org/TR/2001/REC-xmlschema-1-
20010502/ Biron, P., and Malhotra, A., ML Schema Part 2:
Datatypes, W3C Recommendation, May 2001.
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
[XML-schema] Beech, D., Maloney, M., Mendelsohn, N., and Thompson,
H., XML Schema Part 1: Structures, W3C Recommendation,
May 2001. http://www.w3.org/TR/2001/REC-xmlschema-1-
20010502/ Biron, P., and Malhotra, A., ML Schema Part 2:
Datatypes, W3C Recommendation, May 2001.
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
[FIPS-180-1] Federal Information Processing Standards Publication (FIPS PUB) 180-1, Secure Hash Standard, April 1995.
[FIPS-180-1]联邦信息处理标准出版物（FIPS PUB）180-1，安全哈希标准，1995年4月。
[FIPS-186-2] Federal Information Processing Standards Publication (FIPS PUB) 186-2, Digital Signature Standard, January 2000.
[FIPS-186-2]联邦信息处理标准出版物（FIPS PUB）186-2，数字签名标准，2000年1月。
[IEEE1363] Institute for Electrical and Electronics Engineers (IEEE) Standard 1363-2000, Standard Specifications for Public Key Cryptography, January 2000.
[IEEE1363]电气和电子工程师协会（IEEE）标准1363-2000，公钥加密标准规范，2000年1月。
[IEEE1363a] Institute for Electrical and Electronics Engineers (IEEE) Standard 1363, Draft Standard Specifications for Public Key Cryptography -- Amendment 1: Additional Techniques, October 2002.
[IEEE1363a]电气和电子工程师协会（IEEE）标准1363，公钥加密的标准规范草案——修改件1：附加技术，2002年10月。
[KEYS] Lenstra, A.K. and Verheul, E.R., Selecting Cryptographic Key Sizes. October 1999. Presented at Public Key Cryptography Conference, Melbourne, Australia, January 2000. http://www.cryptosavvy.com/
[密钥]Lenstra，A.K.和Verheul，E.R.，选择加密密钥大小。1999年10月。2000年1月在澳大利亚墨尔本举行的公钥密码会议上发表。http://www.cryptosavvy.com/
[RFC3061] Mealling, M., "A URN Namespace of Object Identifiers", RFC 3061, February 2001.
[RFC3061]Mealling，M.，“对象标识符的URN名称空间”，RFC 3061，2001年2月。
[RFC3279] Bassham, L., Polk, W., and R. Housley, "Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 3279, April 2002.
[RFC3279]Bassham，L.，Polk，W.，和R.Housley，“互联网X.509公钥基础设施证书和证书撤销列表（CRL）配置文件的算法和标识符”，RFC 3279，2002年4月。
[SEC1] Standards for Efficient Cryptography Group, SEC 1: Elliptic Curve Cryptography, Version 1.0, September 2000. http://www.secg.org
[SEC1]高效加密标准集团，第1节：椭圆曲线加密，版本1.0，2000年9月。http://www.secg.org
[SEC2] Standards for Efficient Cryptography Group, SEC 2: Recommended Elliptic Curve Domain Parameters, Version 1.0, September 2000. http://www.secg.org
[SEC2]高效加密标准组，第2节：建议的椭圆曲线域参数，版本1.0，2000年9月。http://www.secg.org
[XML] Bray, T., Maler, E., Paoli, J., and Sperberg-McQueen, C.
M., Extensible Markup Language (XML) 1.0 (Second
Edition), W3C Recommendation, October 2000.
http://www.w3.org/TR/2000/REC-xml-20001006
[XML] Bray, T., Maler, E., Paoli, J., and Sperberg-McQueen, C.
M., Extensible Markup Language (XML) 1.0 (Second
Edition), W3C Recommendation, October 2000.
http://www.w3.org/TR/2000/REC-xml-20001006
[XML-ns] Bray, T., Hollander, D., and Layman, A., Namespaces in
XML, W3C Recommendation, January 1999.
http://www.w3.org/TR/1999/REC-xml-names-19990114/
[XML-ns] Bray, T., Hollander, D., and Layman, A., Namespaces in
XML, W3C Recommendation, January 1999.
http://www.w3.org/TR/1999/REC-xml-names-19990114/
The authors would like to acknowledge the many helpful comments of Wolfgang Bauer, Donald Eastlake, Tom Gindin, Chris Hawk, Akihiro Kato, Shiho Moriai, Joseph M. Reagle Jr., and Francois Rousseau.
作者要感谢沃尔夫冈·鲍尔、唐纳德·伊斯特莱克、汤姆·金丁、克里斯·霍克、加藤明弘、森爱、小约瑟夫·M·雷格尔和弗朗索瓦·卢梭的许多有益评论。
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:ecdsa="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
version="0.2">
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:ecdsa="http://www.w3.org/2001/04/xmldsig-more#"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
version="0.2">
<!--ECDSA key value root element-->
<!--ECDSA key value root element-->
<xs:element name="ECDSAKeyValue" type="ecdsa:ECDSAKeyValueType"/>
<xs:complexType name="ECDSAKeyValueType">
<xs:sequence>
<xs:element name="DomainParameters"
type="ecdsa:DomainParamsType" minOccurs="0"/>
<xs:element name="PublicKey" type="ecdsa:ECPointType"/>
</xs:sequence>
</xs:complexType>
<xs:element name="ECDSAKeyValue" type="ecdsa:ECDSAKeyValueType"/>
<xs:complexType name="ECDSAKeyValueType">
<xs:sequence>
<xs:element name="DomainParameters"
type="ecdsa:DomainParamsType" minOccurs="0"/>
<xs:element name="PublicKey" type="ecdsa:ECPointType"/>
</xs:sequence>
</xs:complexType>
<!--EC domain parameters-->
<!--EC domain parameters-->
<xs:complexType name="DomainParamsType">
<xs:choice>
<xs:element name="ExplicitParams"
type="ecdsa:ExplicitParamsType"/>
<xs:element name="NamedCurve">
<xs:complexType>
<xs:attribute name="URN" type="xs:anyURI" use="required"/>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
<xs:complexType name="FieldParamsType" abstract="true"/>
<xs:complexType name="DomainParamsType">
<xs:choice>
<xs:element name="ExplicitParams"
type="ecdsa:ExplicitParamsType"/>
<xs:element name="NamedCurve">
<xs:complexType>
<xs:attribute name="URN" type="xs:anyURI" use="required"/>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
<xs:complexType name="FieldParamsType" abstract="true"/>
<xs:complexType name="PrimeFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="P" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldParamsType" abstract="true">
<xs:complexContent>
<xs:complexType name="PrimeFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="P" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldParamsType" abstract="true">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OddCharExtensionFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
<xs:element name="W" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="TnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="PnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K1" type="xs:positiveInteger"/>
<xs:element name="K2" type="xs:positiveInteger"/>
<xs:element name="K3" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="ExplicitParamsType">
<xs:sequence>
<xs:element name="FieldParams" type="ecdsa:FieldParamsType"/>
<xs:element name="CurveParams" type="ecdsa:CurveParamsType"/>
<xs:element name="BasePointParams"
type="ecdsa:BasePointParamsType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="CurveParamsType">
<xs:sequence>
<xs:element name="A" type="ecdsa:FieldElemType"/>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OddCharExtensionFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldParamsType">
<xs:sequence>
<xs:element name="M" type="xs:positiveInteger"/>
<xs:element name="W" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="TnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="PnBFieldParamsType">
<xs:complexContent>
<xs:extension base="ecdsa:CharTwoFieldParamsType">
<xs:sequence>
<xs:element name="K1" type="xs:positiveInteger"/>
<xs:element name="K2" type="xs:positiveInteger"/>
<xs:element name="K3" type="xs:positiveInteger"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="ExplicitParamsType">
<xs:sequence>
<xs:element name="FieldParams" type="ecdsa:FieldParamsType"/>
<xs:element name="CurveParams" type="ecdsa:CurveParamsType"/>
<xs:element name="BasePointParams"
type="ecdsa:BasePointParamsType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="CurveParamsType">
<xs:sequence>
<xs:element name="A" type="ecdsa:FieldElemType"/>
<xs:element name="B" type="ecdsa:FieldElemType"/>
<xs:element name="Seed" type="xs:hexBinary" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="BasePointParamsType">
<xs:sequence>
<xs:element name="BasePoint" type="ecdsa:ECPointType"/>
<xs:element name="Order" type="xs:positiveInteger"/>
<xs:element name="Cofactor" type="xs:positiveInteger"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:element name="B" type="ecdsa:FieldElemType"/>
<xs:element name="Seed" type="xs:hexBinary" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="BasePointParamsType">
<xs:sequence>
<xs:element name="BasePoint" type="ecdsa:ECPointType"/>
<xs:element name="Order" type="xs:positiveInteger"/>
<xs:element name="Cofactor" type="xs:positiveInteger"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<!--EC point-->
<!--EC point-->
<xs:complexType name="ECPointType">
<xs:sequence minOccurs="0">
<xs:element name="X" type="ecdsa:FieldElemType"/>
<xs:element name="Y" type="ecdsa:FieldElemType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ECPointType">
<xs:sequence minOccurs="0">
<xs:element name="X" type="ecdsa:FieldElemType"/>
<xs:element name="Y" type="ecdsa:FieldElemType"/>
</xs:sequence>
</xs:complexType>
<!--Field element-->
<!--Field element-->
<xs:complexType name="FieldElemType" abstract="true"/>
<xs:complexType name="PrimeFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:hexBinary"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OddCharExtensionFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
<xs:complexType name="FieldElemType" abstract="true"/>
<xs:complexType name="PrimeFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="CharTwoFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:hexBinary"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OddCharExtensionFieldElemType">
<xs:complexContent>
<xs:extension base="ecdsa:FieldElemType">
<xs:attribute name="Value" type="xs:nonNegativeInteger"
use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
</xs:complexType>
</xs:schema>
<!ELEMENT ECDSAKeyValue (DomainParameters?, PublicKey)>
<!ELEMENT PublicKey (X, Y)?>
<!ELEMENT X EMPTY>
<!ATTLIST X Value CDATA #REQUIRED>
<!ELEMENT Y EMPTY>
<!ATTLIST Y Value CDATA #REQUIRED>
<!ELEMENT DomainParameters (ExplicitParams | NamedCurve)>
<!ELEMENT NamedCurve EMPTY>
<!ATTLIST NamedCurve URN CDATA #REQUIRED>
<!ELEMENT ExplicitParams (FieldParams, CurveParams, BasePointParams)>
<!ELEMENT FieldParams (P | (M, K) | (M, K1, K2, K3) | (M, W))>
<!ELEMENT P (#PCDATA)>
<!ELEMENT M (#PCDATA)>
<!ELEMENT W (#PCDATA)>
<!ELEMENT K (#PCDATA)>
<!ELEMENT K1 (#PCDATA)>
<!ELEMENT K2 (#PCDATA)>
<!ELEMENT K3 (#PCDATA)>
<!ELEMENT CurveParams (A, B, Seed?)>
<!ELEMENT A EMPTY>
<!ATTLIST A Value CDATA #REQUIRED>
<!ELEMENT B EMPTY>
<!ATTLIST B Value CDATA #REQUIRED>
<!ELEMENT Seed (#PCDATA)>
<!ELEMENT BasePointParams (BasePoint, Order, Cofactor?)>
<!ELEMENT BasePoint (X, Y)?>
<!ELEMENT Order (#PCDATA)>
<!ELEMENT Cofactor (#PCDATA)>
<!ELEMENT ECDSAKeyValue (DomainParameters?, PublicKey)>
<!ELEMENT PublicKey (X, Y)?>
<!ELEMENT X EMPTY>
<!ATTLIST X Value CDATA #REQUIRED>
<!ELEMENT Y EMPTY>
<!ATTLIST Y Value CDATA #REQUIRED>
<!ELEMENT DomainParameters (ExplicitParams | NamedCurve)>
<!ELEMENT NamedCurve EMPTY>
<!ATTLIST NamedCurve URN CDATA #REQUIRED>
<!ELEMENT ExplicitParams (FieldParams, CurveParams, BasePointParams)>
<!ELEMENT FieldParams (P | (M, K) | (M, K1, K2, K3) | (M, W))>
<!ELEMENT P (#PCDATA)>
<!ELEMENT M (#PCDATA)>
<!ELEMENT W (#PCDATA)>
<!ELEMENT K (#PCDATA)>
<!ELEMENT K1 (#PCDATA)>
<!ELEMENT K2 (#PCDATA)>
<!ELEMENT K3 (#PCDATA)>
<!ELEMENT CurveParams (A, B, Seed?)>
<!ELEMENT A EMPTY>
<!ATTLIST A Value CDATA #REQUIRED>
<!ELEMENT B EMPTY>
<!ATTLIST B Value CDATA #REQUIRED>
<!ELEMENT Seed (#PCDATA)>
<!ELEMENT BasePointParams (BasePoint, Order, Cofactor?)>
<!ELEMENT BasePoint (X, Y)?>
<!ELEMENT Order (#PCDATA)>
<!ELEMENT Cofactor (#PCDATA)>
Authors' Addresses
作者地址
Simon Blake-Wilson BCI 96 Spadina Ave, Unit 606 Toronto, ON, M5V 2J6, Canada
Simon Blake Wilson BCI 96 Spadina Ave，加拿大安大略省多伦多市第606单元，M5V 2J6
EMail: sblakewilson@bcisse.com
EMail: sblakewilson@bcisse.com
Gregor Karlinger Federal Staff Office for IT Strategies/Federal Chancellery Ballhausplatz 2 1014 Wien, Austria
Gregor Karlinger联邦IT战略办公室/奥地利维也纳联邦总理府Ballhausplatz 2 1014
EMail: gregor.karlinger@cio.gv.at
EMail: gregor.karlinger@cio.gv.at
Tetsutaro Kobayashi NTT Laboratories 1-1 Hikarinooka, Yokosuka, 239-0847, Japan
日本横须贺市Hikarinooka 1-1 Tetsutaro Kobayashi NTT实验室，239-0847
EMail: kotetsu@isl.ntt.co.jp
EMail: kotetsu@isl.ntt.co.jp
Yongge Wang University of North Carolina at Charlotte 9201 University City Blvd Charlotte, NC 28223, USA
王永格北卡罗来那大学夏洛特9201大学城夏洛特，美国28223
EMail: yonwang@uncc.edu
EMail: yonwang@uncc.edu
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（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.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。