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
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
|
<pre>Internet Engineering Task Force (IETF) G. Lozano
Request for Comments: 7848 ICANN
Category: Standards Track June 2016
ISSN: 2070-1721
<span class="h1">Mark and Signed Mark Objects Mapping</span>
Abstract
Domain Name Registries (DNRs) may operate in special modes for
certain periods of time, enabling trademark holders to protect their
rights during the introduction of a Top-Level Domain (TLD).
One of those special modes of operation is the Sunrise Period. The
Sunrise Period allows trademark holders an advance opportunity to
register domain names corresponding to their trademarks before names
are generally available to the public.
This document describes the format of a mark and a digitally signed
mark used by trademark holders for registering domain names during
the Sunrise Period of generic Top-Level Domains (gTLDs). Three types
of Mark objects are defined in this specification: registered
trademarks, court-validated marks, and marks protected by statue or
treaty.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7848">http://www.rfc-editor.org/info/rfc7848</a>.
<span class="grey">Lozano Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Object Description . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. Holder and Contact Objects . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.2">2.2</a>. Mark . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.3">2.3</a>. Signed Mark . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-2.4">2.4</a>. Encoded Signed Mark . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-3">3</a>. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-3.1">3.1</a>. Signed Mark Schema . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-3.2">3.2</a>. Mark Schema . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
<a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
<a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
<span class="grey">Lozano Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Domain Name Registries (DNRs) may operate in special modes for
certain periods of time enabling trademark holders to protect their
rights during the introduction of a Top-Level Domain (TLD).
One of those special modes of operation is the Sunrise Period. The
Sunrise Period allows trademark holders an advance opportunity to
register domain names corresponding to their trademarks before names
are generally available to the public.
This specification was defined as part of the development of the
ICANN Trademark Clearinghouse (TMCH). The ICANN TMCH is a global
repository for trademark data used by DNRs, registrars, and trademark
holders during the registration process of domain names.
This document describes a mapping of the common elements found in
trademark data. A digitally signed mark format is defined in order
to support digital signatures on the mark. Finally, a mapping for
encoding the signed mark document is defined.
Three types of Mark objects are defined in this specification:
registered trademarks, court-validated marks, and marks protected by
statue or treaty.
This specification is intended to be used in the gTLD space, but
nothing precludes the use of this format by other entities.
The detailed policy regarding the public key infrastructure (PKI),
authorized validators, and other requirements must be defined based
on the local policy of the entities using this specification. In the
case of gTLDs, the detailed policy regarding the use of this
specification is defined in the Rights Protection Mechanism
Requirements document (see [<a href="#ref-ICANN-TMCH">ICANN-TMCH</a>]), and the PKI is defined in
[<a href="#ref-TMCH" title=""ICANN TMCH functional specifications"">TMCH</a>]. Implementations will need to implement such a PKI (or an
equivalent) in order for the signatures defined in this document to
have any useful semantics.
The objects specified in this document can be referenced by
application protocols like the Extensible Provisioning Protocol
(EPP), defined in [<a href="./rfc5730" title=""Extensible Provisioning Protocol (EPP)"">RFC5730</a>].
<span class="grey">Lozano Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
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 <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
XML (EXtensible Markup Language) is case sensitive. Unless stated
otherwise, XML specifications and examples provided in this document
MUST be interpreted in the character case presented in order to
develop a conforming implementation.
"signedMark-1.0" is used as an abbreviation for
"urn:ietf:params:xml:ns:signedMark-1.0". The XML namespace prefix
"smd" is used, but implementations MUST NOT depend on it and instead
employ a proper namespace-aware XML parser and serializer to
interpret and output the XML documents.
"mark-1.0" is used as an abbreviation for
"urn:ietf:params:xml:ns:mark-1.0". The XML namespace prefix "mark"
is used, but implementations MUST NOT depend on it and instead employ
a proper namespace-aware XML parser and serializer to interpret and
output the XML documents.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Object Description</span>
This section defines the Mark and Signed Mark objects. Empty complex
element types and abstract elements are defined to support additional
definitions using XML schema substitution groups. Support for
replacement through the XML schema substitution groups is included in
the description of the objects.
This section defines some elements as OPTIONAL. If an element is not
defined as OPTIONAL, then it MUST be included in the object.
The following elements are defined as telephone numbers:
<mark:voice>, <mark:fax>, and <smd:voice>. The representation of
telephone numbers in this specification is derived from structures
defined in [<a href="#ref-ITU.E164.2005">ITU.E164.2005</a>]. Telephone numbers described in this
mapping are character strings that MUST begin with a plus sign ("+",
ASCII value 0x002B), followed by a country code defined in
[<a href="#ref-ITU.E164.2005">ITU.E164.2005</a>], followed by a dot (".", ASCII value 0x002E),
followed by a sequence of digits representing the telephone number.
An optional "x" attribute is provided to note telephone extension
information.
The following elements are defined as email addresses: <mark:email>
and <smd:email>. Email address syntax is defined in [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>].
<span class="grey">Lozano Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Holder and Contact Objects</span>
Marks are linked to Holder objects and optionally linked to Contact
objects. This section defines the <mark:holder> and <mark:contact>
objects.
o The child elements of <mark:holder> include:
* A <mark:name> element that contains the name of the individual
holder of the mark. At least one of <mark:name> and <mark:org>
MUST be specified, and <mark:name> is OPTIONAL if <mark:org> is
specified.
* A <mark:org> element that contains the name of the organization
holder of the mark. At least one of <mark:name> and <mark:org>
MUST be specified, and <mark:org> is OPTIONAL if <mark:name> is
specified.
* A <mark:addr> element that contains the address information of
the holder of a mark. A <mark:addr> contains the following
child elements:
+ One, two, or three OPTIONAL <mark:street> elements that
contain the holder's street address.
+ A <mark:city> element that contains the holder's city.
+ An OPTIONAL <mark:sp> element that contains the holder's
state or province.
+ An OPTIONAL <mark:pc> element that contains the holder's
postal code.
+ A <mark:cc> element that contains the holder's country code.
This is a two-character code from [<a href="#ref-ISO3166-2">ISO3166-2</a>].
* An OPTIONAL <mark:voice> element that contains the holder's
voice telephone number.
* An OPTIONAL <mark:fax> element that contains the holder's
facsimile telephone number.
* An OPTIONAL <mark:email> element that contains the email
address of the holder.
<span class="grey">Lozano Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
o The child elements of <mark:contact> include:
* A <mark:name> element that contains the name of the responsible
person.
* An OPTIONAL <mark:org> element that contains the name of the
organization of the contact.
* A <mark:addr> element that contains the address information of
the contact. A <mark:addr> contains the following child
elements:
+ One, two, or three OPTIONAL <mark:street> elements that
contain the contact's street address.
+ A <mark:city> element that contains the contact's city.
+ An OPTIONAL <mark:sp> element that contains the contact's
state or province.
+ An OPTIONAL <mark:pc> element that contains the contact's
postal code.
+ A <mark:cc> element that contains the contact's country
code. This is a two-character code from [<a href="#ref-ISO3166-2">ISO3166-2</a>].
* A <mark:voice> element that contains the contact's voice
telephone number.
* An OPTIONAL <mark:fax> element that contains the contact's
facsimile telephone number.
* A <mark:email> element that contains the contact's email
address.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Mark</span>
A <mark:mark> element that describes an applicant's prior right to a
given domain name.
A <mark:mark> element substitutes for the <mark:abstractMark>
abstract element to define a concrete definition of a mark. The
<mark:abstractMark> element can be replaced by other mark definitions
using the XML schema substitution groups feature.
<span class="grey">Lozano Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
The child elements of the <mark:mark> element include:
One or more <mark:trademark>, <mark:treatyOrStatute>, and
<mark:court> elements that contain the detailed information of marks.
o A <mark:trademark> element that contains the following child
elements:
* A <mark:id> that uniquely identifies a mark in relation to a
repository of marks potentially maintained by more than one
issuer. A <mark:id> value is a concatenation of the local
identifier, followed by a hyphen ("-", ASCII value 0x002D),
followed by the issuer identifier.
* A <mark:markName> element that contains the mark text string.
* One or more <mark:holder> elements that contain the information
of the holder of the mark. An "entitlement" attribute is used
to identify the entitlement of the holder; possible values are
"owner", "assignee", and "licensee".
* Zero or more OPTIONAL <mark:contact> elements that contain the
information of the representative of the mark registration. A
"type" attribute is used to identify the type of contact;
possible values are "owner", "agent", or "thirdparty".
* A <mark:jurisdiction> element that contains the two-character
code of the jurisdiction where the trademark was registered.
This is a two-character code from [<a href="#ref-WIPO.ST3" title=""Recommended standard on two-letter codes for the representation of states, other entities and intergovernmental organizations"">WIPO.ST3</a>].
* Zero or more OPTIONAL <mark:class> elements that contain the
World Intellectual Property Organization (WIPO) Nice
Classification class numbers of the mark as defined in the WIPO
Nice Classification [<a href="#ref-WIPO-NICE-CLASSES">WIPO-NICE-CLASSES</a>].
* Zero or more OPTIONAL <mark:label> elements that contain the
A-label form (as defined in [<a href="./rfc5890" title=""Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework"">RFC5890</a>]) of the label that
corresponds to the <mark:markName>.
* A <mark:goodsAndServices> element that contains the full
description of the goods and services from the document
certifying the registration of the mark.
* An OPTIONAL <mark:apId> element that contains the trademark
application ID registered in the trademark office.
* An OPTIONAL <mark:apDate> element that contains the date the
trademark was applied for.
<span class="grey">Lozano Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
* A <mark:regNum> element that contains the trademark
registration number registered in the trademark office.
* A <mark:regDate> element that contains the date the trademark
was registered.
* An OPTIONAL <mark:exDate> element that contains the expiration
date of the trademark.
o A <mark:treatyOrStatute> element that contains the following child
elements:
* A <mark:id> element; see definition in the <mark:trademark>
section above.
* A <mark:markName> element; see definition in the
<mark:trademark> section above.
* One or more <mark:holder> elements; see definition in the
<mark:trademark> section above.
* Zero or more OPTIONAL <mark:contact> elements; see definition
in the <mark:trademark> section above.
* One or more <mark:protection> elements that contain the
countries and region of the country where the mark is
protected. The <mark:protection> element contains the
following child elements:
+ A <mark:cc> element that contains the two-character code of
the country in which the mark is protected. This is a two-
character code from [<a href="#ref-ISO3166-2">ISO3166-2</a>].
+ An OPTIONAL <mark:region> element that contains the name of
a city, state, province, or other geographic region of
<mark:country> in which the mark is protected.
+ Zero or more OPTIONAL <mark:ruling> elements that contain
the two-character code of the national territory in which
the statute or treaty is applicable. This is a two-
character code from [<a href="#ref-ISO3166-2">ISO3166-2</a>].
+ Zero or more OPTIONAL <mark:label> elements; see definition
in the <mark:trademark> section above.
* A <mark:goodsAndServices> element; see definition in the
<mark:trademark> section above.
<span class="grey">Lozano Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
* A <mark:refNum> element that contains the serial number of the
mark.
* A <mark:proDate> element that contains the date of protection
of the mark.
* A <mark:title> element that contains the title of the treaty or
statute.
* A <mark:execDate> element that contains the execution date of
the treaty or statute.
o A <mark:court> element that contains the following child elements:
* A <mark:id> element; see definition in the <mark:trademark>
section above.
* A <mark:markName> element; see definition in the
<mark:trademark> section above.
* One or more <mark:holder> elements; see definition in the
<mark:trademark> section above.
* Zero or more OPTIONAL <mark:contact> elements; see definition
in the <mark:trademark> section above.
* Zero or more OPTIONAL <mark:label> elements; see definition in
the <mark:trademark> section above.
* A <mark:goodsAndServices> element; see definition in the
<mark:trademark> section above.
* A <mark:refNum> element that contains the reference number of
the court's opinion.
* A <mark:proDate> element that contains the date of protection
of the mark.
* A <mark:cc> element that contains the two-character code of the
country where the court is located. This is a two-character
code from [<a href="#ref-ISO3166-2">ISO3166-2</a>].
* Zero or more OPTIONAL <mark:region> elements that contain the
name of a city, state, province, or other geographic region of
<mark:cc> in which the mark is protected. In case
<mark:region> is specified, a default-deny approach MUST be
assumed regarding the regions of a country.
<span class="grey">Lozano Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
* A <mark:courtName> element that contains the name of the court.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Signed Mark</span>
The <smd:signedMark> is a digitally signed XML document using an XML
Signature [<a href="#ref-XMLDSIG" title=""XML Signature Syntax and Processing Version 1.1"">XMLDSIG</a>]. The <smd:signedMark> XML document (SMD)
includes a required "id" attribute of type XML Schema Definition
(XSD) ID for use with an IDREF URI from the Signature element. The
SMD might be transmitted as part of a protocol already based on XML;
therefore, exclusive XML canonicalization as defined in [<a href="#ref-XMLC14N" title=""Exclusive XML Canonicalization Version 1.0"">XMLC14N</a>]
MUST be used.
A <smd:signedMark> element substitutes for the
<smd:abstractSignedMark> abstract element to define a concrete
definition of a signed mark. The <smd:abstractSignedMark> element
can be replaced by other signed mark definitions using the XML schema
substitution groups feature.
The child elements of the <smd:signedMark> element include:
o The <smd:id> element that uniquely identifies an SMD in relation
to a repository of SMDs potentially maintained by more than one
issuer. The <smd:id> value is a concatenation of the local
identifier, followed by a hyphen ("-", ASCII value 0x002D),
followed by the issuer identifier.
o A <smd:issuerInfo> element that contains the information of the
issuer of the mark registration. An "issuerID" attribute is used
to specify the issuer identifier. The child elements include:
* A <smd:org> element that contains the organization name of the
issuer.
* A <smd:email> element that contains the issuer customer support
email address.
* An OPTIONAL <smd:url> element that contains the HTTP or HTTPS
URL of the issuer's site.
* An OPTIONAL <smd:voice> element that contains the issuer's
voice telephone number.
o A <smd:notBefore> element that contains the creation date and time
of the SMD.
o A <smd:notAfter> element that contains the expiration date and
time of the SMD.
<span class="grey">Lozano Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
o A <mark:mark> element that contains the mark information as
defined in <a href="#section-2.2">Section 2.2</a>.
The following is an example of an SMD:
<?xml version="1.0" encoding="UTF-8"?>
<smd:signedMark xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
id="smd1">
<smd:id>0000001751376056503931-65535</smd:id>
<smd:issuerInfo issuerID="65535">
<smd:org>ICANN TMCH TESTING TMV</smd:org>
<smd:email>notavailable@example.com</smd:email>
<smd:url>https://www.example.com</smd:url>
<smd:voice>+32.000000</smd:voice>
</smd:issuerInfo>
<smd:notBefore>2013-08-09T13:55:03.931Z</smd:notBefore>
<smd:notAfter>2017-07-23T22:00:00.000Z</smd:notAfter>
<mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
<mark:trademark>
<mark:id>00052013734689731373468973-65535</mark:id>
<mark:markName>Test &amp; Validate</mark:markName>
<mark:holder entitlement="owner">
<mark:org>Ag corporation</mark:org>
<mark:addr>
<mark:street>1305 Bright Avenue</mark:street>
<mark:city>Arcadia</mark:city>
<mark:sp>CA</mark:sp>
<mark:pc>90028</mark:pc>
<mark:cc>US</mark:cc>
</mark:addr>
</mark:holder>
<mark:contact type="agent">
<mark:name>Tony Holland</mark:name>
<mark:org>Ag corporation</mark:org>
<mark:addr>
<mark:street>1305 Bright Avenue</mark:street>
<mark:city>Arcadia</mark:city>
<mark:sp>CA</mark:sp>
<mark:pc>90028</mark:pc>
<mark:cc>US</mark:cc>
</mark:addr>
<mark:voice>+1.2025562302</mark:voice>
<mark:fax>+1.2025562301</mark:fax>
<mark:email>info@agcorporation.com</mark:email>
</mark:contact>
<mark:jurisdiction>US</mark:jurisdiction>
<mark:class>15</mark:class>
<mark:label>testandvalidate</mark:label>
<span class="grey">Lozano Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<mark:label>test---validate</mark:label>
<mark:label>testand-validate</mark:label>
<mark:label>test-et-validate</mark:label>
<mark:label>test-validate</mark:label>
<mark:label>test--validate</mark:label>
<mark:label>test-etvalidate</mark:label>
<mark:label>testetvalidate</mark:label>
<mark:label>testvalidate</mark:label>
<mark:label>testet-validate</mark:label>
<mark:goodsAndServices>guitar</mark:goodsAndServices>
<mark:regNum>1234</mark:regNum>
<mark:regDate>2012-12-31T23:00:00.000Z</mark:regDate>
</mark:trademark>
</mark:mark>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<SignatureMethod
Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
<Reference URI="#smd1">
<Transforms>
<Transform
Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
</Transforms>
<DigestMethod
Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
<DigestValue>wgyW3nZPoEfpptlhRILKnOQnbdtU6ArM7ShrAfHgDFg=</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>
jMu4PfyQGiJBF0GWSEPFCJjmywCEqR2h4LD+ge6XQ+JnmKFFCuCZS/3SLKAx0L1w
QDFO2e0Y69k2G7/LGE37X3vOflobFM1oGwja8+GMVraoto5xAd4/AF7eHukgAymD
o9toxoa2h0yV4A4PmXzsU6S86XtCcUE+S/WM72nyn47zoUCzzPKHZBRyeWehVFQ+
jYRMIAMzM57HHQA+6eaXefRvtPETgUO4aVIVSugc4OUAZZwbYcZrC6wOaQqqqAZi
30aPOBYbAvHMSmWSS+hFkbshomJfHxb97TD2grlYNrQIzqXk7WbHWy2SYdA+sI/Z
ipJsXNa6osTUw1CzA7jfwA==
</SignatureValue>
<KeyInfo>
<X509Data>
<X509Certificate>
MIIESTCCAzGgAwIBAgIBAjANBgkqhkiG9w0BAQsFADBiMQswCQYDVQQGEwJVUzEL
MAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJQ0FO
TiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0EwHhcNMTMwMjA4MDAw
MDAwWhcNMTgwMjA3MjM1OTU5WjBsMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex
FDASBgNVBAcTC0xvcyBBbmdlbGVzMRcwFQYDVQQKEw5WYWxpZGF0b3IgVE1DSDEh
MB8GA1UEAxMYVmFsaWRhdG9yIFRNQ0ggVEVTVCBDRVJUMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAo/cwvXhbVYl0RDWWvoyeZpETVZVVcMCovUVNg/sw
<span class="grey">Lozano Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
WinuMgEWgVQFrz0xA04pEhXCFVv4evbUpekJ5buqU1gmQyOsCKQlhOHTdPjvkC5u
pDqa51Flk0TMaMkIQjs7aUKCmA4RG4tTTGK/EjR1ix8/D0gHYVRldy1YPrMP+ou7
5bOVnIos+HifrAtrIv4qEqwLL4FTZAUpaCa2BmgXfy2CSRQbxD5Or1gcSa3vurh5
sPMCNxqaXmIXmQipS+DuEBqMM8tldaN7RYojUEKrGVsNk5i9y2/7sjn1zyyUPf7v
L4GgDYqhJYWV61DnXgx/Jd6CWxvsnDF6scscQzUTEl+hywIDAQABo4H/MIH8MAwG
A1UdEwEB/wQCMAAwHQYDVR0OBBYEFPZEcIQcD/Bj2IFz/LERuo2ADJviMIGMBgNV
HSMEgYQwgYGAFO0/7kEh3FuEKS+Q/kYHaD/W6wihoWakZDBiMQswCQYDVQQGEwJV
UzELMAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJ
Q0FOTiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0GCAQEwDgYDVR0P
AQH/BAQDAgeAMC4GA1UdHwQnMCUwI6AhoB+GHWh0dHA6Ly9jcmwuaWNhbm4ub3Jn
L3RtY2guY3JsMA0GCSqGSIb3DQEBCwUAA4IBAQB2qSy7ui+43cebKUKwWPrzz9y/
IkrMeJGKjo40n+9uekaw3DJ5EqiOf/qZ4pjBD++oR6BJCb6NQuQKwnoAz5lE4Ssu
y5+i93oT3HfyVc4gNMIoHm1PS19l7DBKrbwbzAea/0jKWVzrvmV7TBfjxD3AQo1R
bU5dBr6IjbdLFlnO5x0G0mrG7x5OUPuurihyiURpFDpwH8KAH1wMcCpXGXFRtGKk
wydgyVYAty7otkl/z3bZkCVT34gPvF70sR6+QxUy8u0LzF5A/beYaZpxSYG31amL
AdXitTWFipaIGea9lEGFM0L9+Bg7XzNn4nVLXokyEB3bgS4scG6QznX23FGk
</X509Certificate>
</X509Data>
</KeyInfo>
</Signature>
</smd:signedMark>
NOTE: The example shown above includes white space for indentation
purposes. It is RECOMMENDED that SMDs do not include white space
between the XML elements, in order to mitigate risks of invalidating
the digital signature when transferring of SMDs between applications
takes place.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Encoded Signed Mark</span>
The <smd:encodedSignedMark> element contains an encoded form of an
SMD (described in <a href="#section-2.3">Section 2.3</a>), with the encoding defined by the
"encoding" attribute with the default "encoding" value of "base64"
[<a href="./rfc4648" title=""The Base16, Base32, and Base64 Data Encodings"">RFC4648</a>].
The following is an example of a <smd:encodedSignedMark> element that
uses the default "base64" for encoding a <smd:signedMark> element.
<smd:encodedSignedMark
xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNtZDpzaWduZWRNYXJ
rIHhtbG5zOnNtZD0idXJuOmlldGY6cGFyYW1zOnhtbDpuczpzaWduZWRNYXJrLTEuMCIgaW
... (base64 data elided for brevity) ...
PC9zbWQ6c2lnbmVkTWFyaz4=
</smd:encodedSignedMark>
<span class="grey">Lozano Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Formal Syntax</span>
Two schemas are presented here. The first schema is the schema for
the Signed Mark object. The second schema is the schema for the Mark
object.
The formal syntax presented here is a complete schema representation
of the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they
are used to note the beginning and ending of the schema for URI
registration purposes.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Signed Mark Schema</span>
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="urn:ietf:params:xml:ns:signedMark-1.0"
xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation>
<documentation>
Schema for representing a Signed Mark object.
</documentation>
</annotation>
<import namespace="urn:ietf:params:xml:ns:mark-1.0" />
<import namespace="http://www.w3.org/2000/09/xmldsig#" />
<!--
Abstract Signed Mark object for replacement via substitution.
-->
<element name="abstractSignedMark" type="smd:abstractSignedMarkType"
abstract="true"/>
<!--
Empty type for use in extending for a Signed Mark object.
-->
<complexType name="abstractSignedMarkType"/>
<element name="signedMark" type="smd:signedMarkType"
substitutionGroup="smd:abstractSignedMark"/>
<element name="encodedSignedMark" type="smd:encodedSignedMarkType"/>
<span class="grey">Lozano Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<complexType name="signedMarkType">
<complexContent>
<extension base="smd:abstractSignedMarkType">
<sequence>
<element name="id" type="mark:idType"/>
<element name="issuerInfo" type="smd:issuerInfoType"/>
<element name="notBefore" type="dateTime"/>
<element name="notAfter" type="dateTime"/>
<element ref="mark:abstractMark"/>
<element ref="dsig:Signature"/>
</sequence>
<attribute name="id" type="ID" use="required"/>
</extension>
</complexContent>
</complexType>
<complexType name="issuerInfoType">
<sequence>
<element name="org" type="token"/>
<element name="email" type="mark:minTokenType"/>
<element name="url" type="token" minOccurs="0"/>
<element name="voice" type="mark:e164Type" minOccurs="0"/>
</sequence>
<attribute name="issuerID" type="token" use="required"/>
</complexType>
<complexType name="encodedSignedMarkType">
<simpleContent>
<extension base="token">
<attribute name="encoding" type="token" default="base64"/>
</extension>
</simpleContent>
</complexType>
</schema>
END
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Mark Schema</span>
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="urn:ietf:params:xml:ns:mark-1.0"
xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation>
<documentation>
<span class="grey">Lozano Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
Schema for representing a Trademark, also referred to
as Mark.
</documentation>
</annotation>
<!--
Abstract Mark object for replacement via substitution.
-->
<element name="abstractMark" type="mark:abstractMarkType"
abstract="true"/>
<!--
<mark:mark> element definition
-->
<element name="mark" type="mark:markType"
substitutionGroup="mark:abstractMark"/>
<!--
Empty type for use in extending for a Mark object.
-->
<complexType name="abstractMarkType"/>
<!--
<mark:mark> child elements
-->
<complexType name="markType">
<complexContent>
<extension base="mark:abstractMarkType">
<sequence>
<element name="trademark" type="mark:trademarkType"
minOccurs="0" maxOccurs="unbounded"/>
<element name="treatyOrStatute"
type="mark:treatyOrStatuteType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="court" type="mark:courtType" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="holderType">
<sequence>
<element name="name" type="token" minOccurs="0"/>
<element name="org" type="token" minOccurs="0"/>
<element name="addr" type="mark:addrType"/>
<element name="voice" type="mark:e164Type" minOccurs="0"/>
<element name="fax" type="mark:e164Type" minOccurs="0"/>
<span class="grey">Lozano Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<element name="email" type="mark:minTokenType" minOccurs="0"/>
</sequence>
<attribute name="entitlement" type="mark:entitlementType"/>
</complexType>
<complexType name="contactType">
<sequence>
<element name="name" type="token"/>
<element name="org" type="token" minOccurs="0"/>
<element name="addr" type="mark:addrType"/>
<element name="voice" type="mark:e164Type"/>
<element name="fax" type="mark:e164Type" minOccurs="0"/>
<element name="email" type="mark:minTokenType"/>
</sequence>
<attribute name="type" type="mark:contactTypeType"/>
</complexType>
<complexType name="trademarkType">
<sequence>
<element name="id" type="mark:idType"/>
<element name="markName" type="token"/>
<element name="holder" type="mark:holderType"
maxOccurs="unbounded" />
<element name="contact" type="mark:contactType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="jurisdiction" type="mark:ccType"/>
<element name="class" type="integer" minOccurs="0"
maxOccurs="unbounded"/>
<element name="label" type="mark:labelType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="goodsAndServices" type="token" />
<element name="apId" type="token" minOccurs="0"/>
<element name="apDate" type="dateTime" minOccurs="0"/>
<element name="regNum" type="token"/>
<element name="regDate" type="dateTime"/>
<element name="exDate" type="dateTime" minOccurs="0"/>
</sequence>
</complexType>
<complexType name="treatyOrStatuteType">
<sequence>
<element name="id" type="mark:idType"/>
<element name="markName" type="token"/>
<element name="holder" type="mark:holderType"
maxOccurs="unbounded" />
<element name="contact" type="mark:contactType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="protection" type="mark:protectionType"
<span class="grey">Lozano Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
maxOccurs="unbounded"/>
<element name="label" type="mark:labelType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="goodsAndServices" type="token" />
<element name="refNum" type="token"/>
<element name="proDate" type="dateTime"/>
<element name="title" type="token"/>
<element name="execDate" type="dateTime"/>
</sequence>
</complexType>
<complexType name="courtType">
<sequence>
<element name="id" type="mark:idType"/>
<element name="markName" type="token"/>
<element name="holder" type="mark:holderType"
maxOccurs="unbounded" />
<element name="contact" type="mark:contactType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="label" type="mark:labelType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="goodsAndServices" type="token" />
<element name="refNum" type="token"/>
<element name="proDate" type="dateTime"/>
<element name="cc" type="mark:ccType"/>
<element name="region" type="token" minOccurs="0"
maxOccurs="unbounded"/>
<element name="courtName" type="token"/>
</sequence>
</complexType>
<!--
Address (<mark:addr>) child elements
-->
<complexType name="addrType">
<sequence>
<element name="street" type="token" minOccurs="1" maxOccurs="3"/>
<element name="city" type="token"/>
<element name="sp" type="token" minOccurs="0"/>
<element name="pc" type="mark:pcType" minOccurs="0"/>
<element name="cc" type="mark:ccType"/>
</sequence>
</complexType>
<!--
<mark:protection> child elements
-->
<complexType name="protectionType">
<span class="grey">Lozano Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<sequence>
<element name="cc" type="mark:ccType"/>
<element name="region" type="token" minOccurs="0"/>
<element name="ruling" type="mark:ccType"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Postal code definition
-->
<simpleType name="pcType">
<restriction base="token">
<maxLength value="16"/>
</restriction>
</simpleType>
<!--
Country code definition
-->
<simpleType name="ccType">
<restriction base="token">
<length value="2"/>
</restriction>
</simpleType>
<!--
Phone number with extension definition
-->
<complexType name="e164Type">
<simpleContent>
<extension base="mark:e164StringType">
<attribute name="x" type="token"/>
</extension>
</simpleContent>
</complexType>
<!--
Phone number with extension definition
-->
<simpleType name="e164StringType">
<restriction base="token">
<pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?"/>
<maxLength value="17"/>
</restriction>
</simpleType>
<!--
<span class="grey">Lozano Standards Track [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
Id type definition
-->
<simpleType name="idType">
<restriction base="token">
<pattern value="\d+-\d+"/>
</restriction>
</simpleType>
<!--
DNS label type definition
-->
<simpleType name="labelType">
<restriction base="token">
<minLength value="1"/>
<maxLength value="63"/>
<pattern value="[a-zA-Z0-9]([a-zA-Z0-9\-]*[a-zA-Z0-9])?"/>
</restriction>
</simpleType>
<!--
Type used for email addresses
-->
<simpleType name="minTokenType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<simpleType name="entitlementType">
<restriction base="token">
<enumeration value="owner"/>
<enumeration value="assignee"/>
<enumeration value="licensee"/>
</restriction>
</simpleType>
<simpleType name="contactTypeType">
<restriction base="token">
<enumeration value="owner"/>
<enumeration value="agent"/>
<enumeration value="thirdparty"/>
</restriction>
</simpleType>
</schema>
END
<span class="grey">Lozano Standards Track [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
This document uses URNs to describe XML namespaces and XML schemas
conforming to the registry mechanism described in [<a href="./rfc3688" title=""The IETF XML Registry"">RFC3688</a>]. IANA
has registered two URI assignments: signed mark (signedMark-1.0) and
mark (mark-1.0).
o The signed mark namespace (signedMark-1.0) has been registered in
the "ns" registry.
URI: urn:ietf:params:xml:ns:signedMark-1.0
Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification.
o The signed mark schema (signedMark-1.0) has been registered in the
"schema" registry.
URI: urn:ietf:params:xml:schema:signedMark-1.0
Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document.
o The mark namespace (mark-1.0) has been registered in the "ns"
registry.
URI: urn:ietf:params:xml:ns:mark-1.0
Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification.
o The mark schema (mark-1.0) has been registered in the "schema"
registry.
URI: urn:ietf:params:xml:schema:mark-1.0
Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document.
<span class="grey">Lozano Standards Track [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
The security of a Signed Mark object depends on the security of the
underlying XML Digital Signature (DSIG) algorithms. As such, all the
security considerations from [<a href="#ref-XMLDSIG" title=""XML Signature Syntax and Processing Version 1.1"">XMLDSIG</a>] apply here as well.
The digital signature algorithm used in Signed Mark objects SHOULD be
RSA-SHA256 [<a href="./rfc6931" title=""Additional XML Security Uniform Resource Identifiers (URIs)"">RFC6931</a>]. The size of the RSA key SHOULD be at least
2048 bits. A valid reason for choosing something else would be if
RSA-SHA256 is deemed to not provide sufficient security.
In the case of the ICANN TMCH, Signed Mark objects use the algorithms
for digesting and signing recommended in this document.
Signed Mark objects are used primarily for domain name registrations
in gTLDs during the Sunrise Period, but other third parties might be
using them. A party using Signed Mark objects should verify that the
digital signature is valid based on local policy. In the case of
gTLDs, the Rights Protection Mechanism Requirements document
[<a href="#ref-ICANN-TMCH">ICANN-TMCH</a>] defines such policy, and the PKI is defined in [<a href="#ref-TMCH" title=""ICANN TMCH functional specifications"">TMCH</a>].
Implementations will need to implement such a PKI (or an equivalent)
in order for the signatures defined in this document to have any
useful semantics.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-ICANN-TMCH">ICANN-TMCH</a>]
ICANN, "Trademark Clearinghouse; Rights Protection
Mechanism Requirements", 2013,
<<a href="http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-30sep13-en.pdf">http://newgtlds.icann.org/en/about/</a>
<a href="http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-30sep13-en.pdf">trademark-clearinghouse/rpm-requirements-30sep13-en.pdf</a>>.
[<a id="ref-ISO3166-2">ISO3166-2</a>]
ISO, "International Standard for country codes and codes
for their subdivisions", 2006,
<<a href="http://www.iso.org/iso/home/standards/country_codes.htm">http://www.iso.org/iso/home/standards/country_codes.htm</a>>.
[<a id="ref-ITU.E164.2005">ITU.E164.2005</a>]
International Telecommunication Union, "The international
public telecommunication numbering plan", ITU-T
Recommendation E.164, November 2010,
<<a href="https://www.itu.int/rec/T-REC-E.164-201011-I/en">https://www.itu.int/rec/T-REC-E.164-201011-I/en</a>>.
<span class="grey">Lozano Standards Track [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC3688">RFC3688</a>] Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
DOI 10.17487/RFC3688, January 2004,
<<a href="http://www.rfc-editor.org/info/rfc3688">http://www.rfc-editor.org/info/rfc3688</a>>.
[<a id="ref-RFC4648">RFC4648</a>] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", <a href="./rfc4648">RFC 4648</a>, DOI 10.17487/RFC4648, October 2006,
<<a href="http://www.rfc-editor.org/info/rfc4648">http://www.rfc-editor.org/info/rfc4648</a>>.
[<a id="ref-RFC5322">RFC5322</a>] Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC 5322</a>,
DOI 10.17487/RFC5322, October 2008,
<<a href="http://www.rfc-editor.org/info/rfc5322">http://www.rfc-editor.org/info/rfc5322</a>>.
[<a id="ref-RFC5890">RFC5890</a>] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework",
<a href="./rfc5890">RFC 5890</a>, DOI 10.17487/RFC5890, August 2010,
<<a href="http://www.rfc-editor.org/info/rfc5890">http://www.rfc-editor.org/info/rfc5890</a>>.
[<a id="ref-RFC6931">RFC6931</a>] Eastlake 3rd, D., "Additional XML Security Uniform
Resource Identifiers (URIs)", <a href="./rfc6931">RFC 6931</a>,
DOI 10.17487/RFC6931, April 2013,
<<a href="http://www.rfc-editor.org/info/rfc6931">http://www.rfc-editor.org/info/rfc6931</a>>.
[<a id="ref-WIPO-NICE-CLASSES">WIPO-NICE-CLASSES</a>]
WIPO, "Nice Classification", January 2016,
<<a href="http://www.wipo.int/classifications/nice/en">http://www.wipo.int/classifications/nice/en</a>>.
[<a id="ref-WIPO.ST3">WIPO.ST3</a>] WIPO, "Recommended standard on two-letter codes for the
representation of states, other entities and
intergovernmental organizations", Standard ST.3, February
2015, <<a href="http://www.wipo.int/standards/en/pdf/03-03-01.pdf">http://www.wipo.int/standards/en/pdf/03-03-01.pdf</a>>.
[<a id="ref-XMLC14N">XMLC14N</a>] W3C, "Exclusive XML Canonicalization Version 1.0",
W3C Recommendation, July 2002,
<<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718</a>>.
[<a id="ref-XMLDSIG">XMLDSIG</a>] W3C, "XML Signature Syntax and Processing Version 1.1",
W3C Recommendation, April 2013,
<<a href="http://www.w3.org/TR/xmldsig-core1">http://www.w3.org/TR/xmldsig-core1</a>>.
<span class="grey">Lozano Standards Track [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc7848">RFC 7848</a> Mark and Signed Mark June 2016</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-EPP-LAUNCH">EPP-LAUNCH</a>]
Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping
for the Extensible Provisioning Protocol (EPP)", Work in
Progress, <a href="./draft-ietf-regext-launchphase-00">draft-ietf-regext-launchphase-00</a>, April 2016.
[<a id="ref-RFC5105">RFC5105</a>] Lendl, O., "ENUM Validation Token Format Definition",
<a href="./rfc5105">RFC 5105</a>, DOI 10.17487/RFC5105, December 2007,
<<a href="http://www.rfc-editor.org/info/rfc5105">http://www.rfc-editor.org/info/rfc5105</a>>.
[<a id="ref-RFC5730">RFC5730</a>] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, <a href="./rfc5730">RFC 5730</a>, DOI 10.17487/RFC5730, August 2009,
<<a href="http://www.rfc-editor.org/info/rfc5730">http://www.rfc-editor.org/info/rfc5730</a>>.
[<a id="ref-TMCH">TMCH</a>] Lozano, G., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22ICANN+TMCH+functional+specifications%22'>"ICANN TMCH functional specifications"</a>, Work
in Progress, <a href="./draft-ietf-regext-tmch-func-spec-00">draft-ietf-regext-tmch-func-spec-00</a>, April
2016.
Acknowledgements
Special thanks to Chris Wright for creating the first prototype of an
SMD and to James Gould, Wil Tan, and Gavin Brown for creating the
mark and SMD definitions in "Launch Phase Mapping for the Extensible
Provisioning Protocol (EPP)" [<a href="#ref-EPP-LAUNCH">EPP-LAUNCH</a>], on which this document is
based. Portions of the Security Considerations section were
shamefully copied from <a href="./rfc5105">RFC 5105</a> [<a href="./rfc5105" title=""ENUM Validation Token Format Definition"">RFC5105</a>]. The author would like to
acknowledge the following individuals for their contributions to this
document: Scott Hollenbeck and Jan Jansen.
Author's Address
Gustavo Lozano
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90292
United States
Phone: +1.3103015800
Email: gustavo.lozano@icann.org
Lozano Standards Track [Page 24]
</pre>
|
