1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
|
<pre>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
<span class="h1">Using the Elliptic Curve Signature Algorithm (ECDSA)</span>
<span class="h1">for XML Digital Signatures</span>
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).
IESG Note
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.
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.
<span class="grey">Blake-Wilson, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. ECDSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. Specifying ECDSA within XMLDSIG . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Version, Namespaces, and Identifiers . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. XML Schema Preamble and DTD Replacement. . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.2.1">3.2.1</a>. XML Schema Preamble. . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.2.2">3.2.2</a>. DTD Replacement. . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.3">3.3</a>. ECDSA Signatures . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.4">3.4</a>. ECDSA Key Values . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.4.1">3.4.1</a>. Key Value Root Element . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.4.2">3.4.2</a>. EC Domain Parameters . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.4.2.1">3.4.2.1</a>. Field Parameters . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.4.2.2">3.4.2.2</a>. Curve Parameters . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-3.4.2.3">3.4.2.3</a>. Base Point Parameters. . . . . . . . . <a href="#page-9">9</a>
<a href="#section-3.4.3">3.4.3</a>. EC Points . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-5">5</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-6">6</a>. Informative References . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-7">7</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#appendix-A">Appendix A</a>: Aggregate XML Schema . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#appendix-B">Appendix B</a>: Aggregate DTD. . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies how to use the Elliptic Curve Digital
Signature Algorithm (ECDSA) with XML signatures, as specified in
[<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>]. [<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>] defines only two digital signature methods: RSA
and DSA (DSS) signatures. This document introduces ECDSA signatures
as an additional method.
This document uses both XML Schemas [<a href="#ref-XML-schema" title="W3C Recommendation">XML-schema</a>] (normative) and DTDs
[<a href="#ref-XML" title="and Sperberg-McQueen">XML</a>] (informational) to specify the corresponding XML structures.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. ECDSA</span>
The Elliptic Curve Digital Signature Algorithm (ECDSA) is the
elliptic curve analogue of the DSA (DSS) signature method
[<a href="#ref-FIPS-186-2" title="Digital Signature Standard">FIPS-186-2</a>]. It is defined in the ANSI X9.62 standard [<a href="#ref-X9.62">X9.62</a>].
Other compatible specifications include FIPS 186-2 [<a href="#ref-FIPS-186-2" title="Digital Signature Standard">FIPS-186-2</a>], IEEE
1363 [<a href="#ref-IEEE1363" title="Standard Specifications for Public Key Cryptography">IEEE1363</a>], IEEE 1363a [<a href="#ref-IEEE1363a" title="Draft Standard Specifications for Public Key Cryptography -- Amendment 1: Additional Techniques">IEEE1363a</a>], and SEC1 [<a href="#ref-SEC1" title="Version 1.0">SEC1</a>]. [<a href="./rfc3279" title=""Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC3279</a>]
describes ways to carry ECDSA keys in X.509 certificates.
[<a href="#ref-FIPS-186-2" title="Digital Signature Standard">FIPS-186-2</a>], [<a href="#ref-SEC2" title="SEC 2: Recommended Elliptic Curve Domain Parameters">SEC2</a>], and [<a href="#ref-X9.62">X9.62</a>] provide recommended elliptic curve
domain parameters for use with ECDSA.
<span class="grey">Blake-Wilson, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
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 [<a href="#ref-FIPS-180-1" title="Secure Hash Standard">FIPS-180-1</a>].
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
[<a href="#ref-KEYS" title="E.R.">KEYS</a>] 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.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Specifying ECDSA within XMLDSIG</span>
This section specifies how to use ECDSA with XML Signature Syntax and
Processing [<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>]. It relies heavily on the syntax and namespace
defined in [<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>].
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Version, Namespaces, and Identifiers</span>
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 [<a href="#ref-XML-ns" title="A.">XML-ns</a>] URI that MUST be used by implementations
of this (dated) specification is:
<a href="http://www.w3.org/2001/04/xmldsig-more#">http://www.w3.org/2001/04/xmldsig-more#</a>
Elements in the namespace of the [<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>] specification are marked
by using the namespace prefix "dsig" in the remaining sections of
this document.
The identifier for the ECDSA signature algorithm as defined in
[<a href="#ref-Eastlake" title=""Additional XML Security Uniform Resource Identifiers (URIs)"">Eastlake</a>] is:
<a href="http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1">http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1</a>
<span class="grey">Blake-Wilson, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. XML Schema Preamble and DTD Replacement</span>
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. XML Schema Preamble</span>
The subsequent preamble is to be used with the XML Schema definitions
given in the remaining sections of this document.
<?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">
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. DTD Replacement</span>
To include ECDSA in XML-signature syntax, the following definition of
the entity Key.ANY SHOULD replace the one in [<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>]:
<!ENTITY % KeyValue.ANY '| ecdsa:ECDSAKeyValue'>
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. ECDSA Signatures</span>
The input to the ECDSA algorithm is the canonicalized representation
of the dsig:SignedInfo element as specified in Section 3 of
[<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>].
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 [<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>])
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
[<a href="#ref-IEEE1363" title="Standard Specifications for Public Key Cryptography">IEEE1363</a>].
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. ECDSA Key Values</span>
The syntax used for ECDSA key values closely follows the ASN.1 syntax
defined in ANSI X9.62 [<a href="#ref-X9.62">X9.62</a>].
<span class="h4"><a class="selflink" id="section-3.4.1" href="#section-3.4.1">3.4.1</a>. Key Value Root Element</span>
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).
<span class="grey">Blake-Wilson, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
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.
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>
DTD Definition:
<!ELEMENT ECDSAKeyValue (DomainParameters?, PublicKey)>
<!ELEMENT PublicKey (X, Y)?>
<!ELEMENT X EMPTY>
<!ATTLIST X Value CDATA #REQUIRED>
<!ELEMENT Y EMPTY>
<!ATTLIST Y Value CDATA #REQUIRED>
<span class="h4"><a class="selflink" id="section-3.4.2" href="#section-3.4.2">3.4.2</a>. EC Domain Parameters</span>
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
[<a href="#ref-X9.62">X9.62</a>], [<a href="#ref-FIPS-186-2" title="Digital Signature Standard">FIPS-186-2</a>], or [<a href="#ref-SEC2" title="SEC 2: Recommended Elliptic Curve Domain Parameters">SEC2</a>], 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 [<a href="./rfc3061" title=""A URN Namespace of Object Identifiers"">RFC3061</a>].
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>
<span class="grey">Blake-Wilson, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
DTD Definition:
<!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.
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>
DTD Definition:
<!ELEMENT ExplicitParams (FieldParams, CurveParams, BasePointParams)>
<span class="h5"><a class="selflink" id="section-3.4.2.1" href="#section-3.4.2.1">3.4.2.1</a>. Field Parameters</span>
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.
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.
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.
<span class="grey">Blake-Wilson, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
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.
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.
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.
Schema Definition:
<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: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>
<span class="grey">Blake-Wilson, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
</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>
DTD Definition:
<!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)>
<span class="h5"><a class="selflink" id="section-3.4.2.2" href="#section-3.4.2.2">3.4.2.2</a>. Curve Parameters</span>
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 [<a href="#ref-X9.62">X9.62</a>], the optional element Seed contains the value used to
derive the coefficients of a randomly generated elliptic curve.
<span class="grey">Blake-Wilson, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
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>
DTD Definition:
<!ELEMENT CurveParams (A, B, Seed?)>
<!ELEMENT A EMPTY>
<!ATTLIST A Value CDATA #REQUIRED>
<!ELEMENT B EMPTY>
<!ATTLIST B Value CDATA #REQUIRED>
<!ELEMENT Seed (#PCDATA)>
<span class="h5"><a class="selflink" id="section-3.4.2.3" href="#section-3.4.2.3">3.4.2.3</a>. Base Point Parameters</span>
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.
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>
DTD Definition:
<!ELEMENT BasePointParams (BasePoint, Order, Cofactor?)>
<!ELEMENT BasePoint (X, Y)?>
<!ELEMENT Order (#PCDATA)>
<!ELEMENT Cofactor (#PCDATA)>
<span class="grey">Blake-Wilson, et al. Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
<span class="h4"><a class="selflink" id="section-3.4.3" href="#section-3.4.3">3.4.3</a>. EC Points</span>
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.
The point at infinity is encoded by omitting both elements X and 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.
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.
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 [<a href="#ref-X9.62">X9.62</a>].
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 <a href="#section-5.3.3">section</a>
<a href="#section-5.3.3">5.3.3</a> of [<a href="#ref-IEEE1363a" title="Draft Standard Specifications for Public Key Cryptography -- Amendment 1: Additional Techniques">IEEE1363a</a>].
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"/>
<span class="grey">Blake-Wilson, et al. Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
<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>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
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 [<a href="#ref-X9.62">X9.62</a>], [<a href="#ref-FIPS-186-2" title="Digital Signature Standard">FIPS-186-2</a>], and [<a href="#ref-SEC2" title="SEC 2: Recommended Elliptic Curve Domain Parameters">SEC2</a>]. For further
security discussion, see [<a href="#ref-XMLDSIG" title=""(Extensible Markup Language) XML-Signature Syntax and Processing"">XMLDSIG</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Normative References</span>
[<a id="ref-Eastlake">Eastlake</a>] Eastlake 3rd, D., "Additional XML Security Uniform
Resource Identifiers (URIs)", <a href="./rfc4051">RFC 4051</a>, April 2005.
[<a id="ref-X9.62">X9.62</a>] American National Standards Institute. ANSI X9.62-1998,
Public Key Cryptography for the Financial Services
Industry: The Elliptic Curve Digital Signature
Algorithm. January 1999.
<span class="grey">Blake-Wilson, et al. Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
[<a id="ref-XMLDSIG">XMLDSIG</a>] Eastlake 3rd, D., Reagle, J., and D. Solo, "(Extensible
Markup Language) XML-Signature Syntax and Processing",
<a href="./rfc3275">RFC 3275</a>, March 2002.
[<a id="ref-XML-schema">XML-schema</a>] Beech, D., Maloney, M., Mendelsohn, N., and Thompson,
H., XML Schema Part 1: Structures, W3C Recommendation,
May 2001. <a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">http://www.w3.org/TR/2001/REC-xmlschema-1-</a>
<a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">20010502/</a> Biron, P., and Malhotra, A., ML Schema Part 2:
Datatypes, W3C Recommendation, May 2001.
<a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/</a>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Informative References</span>
[<a id="ref-FIPS-180-1">FIPS-180-1</a>] Federal Information Processing Standards Publication
(FIPS PUB) 180-1, Secure Hash Standard, April 1995.
[<a id="ref-FIPS-186-2">FIPS-186-2</a>] Federal Information Processing Standards Publication
(FIPS PUB) 186-2, Digital Signature Standard, January
2000.
[<a id="ref-IEEE1363">IEEE1363</a>] Institute for Electrical and Electronics Engineers
(IEEE) Standard 1363-2000, Standard Specifications for
Public Key Cryptography, January 2000.
[<a id="ref-IEEE1363a">IEEE1363a</a>] Institute for Electrical and Electronics Engineers
(IEEE) Standard 1363, Draft Standard Specifications for
Public Key Cryptography -- Amendment 1: Additional
Techniques, October 2002.
[<a id="ref-KEYS">KEYS</a>] Lenstra, A.K. and Verheul, E.R., Selecting Cryptographic
Key Sizes. October 1999. Presented at Public Key
Cryptography Conference, Melbourne, Australia, January
2000. <a href="http://www.cryptosavvy.com/">http://www.cryptosavvy.com/</a>
[<a id="ref-RFC3061">RFC3061</a>] Mealling, M., "A URN Namespace of Object Identifiers",
<a href="./rfc3061">RFC 3061</a>, February 2001.
[<a id="ref-RFC3279">RFC3279</a>] 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", <a href="./rfc3279">RFC 3279</a>, April 2002.
[<a id="ref-SEC1">SEC1</a>] Standards for Efficient Cryptography Group, SEC 1:
Elliptic Curve Cryptography, Version 1.0, September
2000. <a href="http://www.secg.org">http://www.secg.org</a>
<span class="grey">Blake-Wilson, et al. Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
[<a id="ref-SEC2">SEC2</a>] Standards for Efficient Cryptography Group, SEC 2:
Recommended Elliptic Curve Domain Parameters, Version
1.0, September 2000. <a href="http://www.secg.org">http://www.secg.org</a>
[<a id="ref-XML">XML</a>] Bray, T., Maler, E., Paoli, J., and Sperberg-McQueen, C.
M., Extensible Markup Language (XML) 1.0 (Second
Edition), W3C Recommendation, October 2000.
<a href="http://www.w3.org/TR/2000/REC-xml-20001006">http://www.w3.org/TR/2000/REC-xml-20001006</a>
[<a id="ref-XML-ns">XML-ns</a>] Bray, T., Hollander, D., and Layman, A., Namespaces in
XML, W3C Recommendation, January 1999.
<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">http://www.w3.org/TR/1999/REC-xml-names-19990114/</a>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
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.
<span class="grey">Blake-Wilson, et al. Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Aggregate XML Schema</span>
<?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-->
<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-->
<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>
<span class="grey">Blake-Wilson, et al. Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
<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"/>
<span class="grey">Blake-Wilson, et al. Informational [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
<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-->
<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-->
<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>
<span class="grey">Blake-Wilson, et al. Informational [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
</xs:complexType>
</xs:schema>
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Aggregate DTD</span>
<!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)>
<span class="grey">Blake-Wilson, et al. Informational [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
Authors' Addresses
Simon Blake-Wilson
BCI
96 Spadina Ave, Unit 606
Toronto, ON, M5V 2J6, Canada
EMail: sblakewilson@bcisse.com
Gregor Karlinger
Federal Staff Office for IT Strategies/Federal Chancellery
Ballhausplatz 2
1014 Wien, Austria
EMail: gregor.karlinger@cio.gv.at
Tetsutaro Kobayashi
NTT Laboratories
1-1 Hikarinooka, Yokosuka, 239-0847, Japan
EMail: kotetsu@isl.ntt.co.jp
Yongge Wang
University of North Carolina at Charlotte
9201 University City Blvd
Charlotte, NC 28223, USA
EMail: yonwang@uncc.edu
<span class="grey">Blake-Wilson, et al. Informational [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc4050">RFC 4050</a> ECDSA for XML Digital Signatures April 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
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 <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
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
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Blake-Wilson, et al. Informational [Page 19]
</pre>
|
