forked from wil/EPP-Launch-Phase-Extension-Specification
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathdraft-ietf-regext-launchphase.html
2569 lines (2437 loc) · 161 KB
/
draft-ietf-regext-launchphase.html
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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)</title>
<style type="text/css" title="Xml2Rfc (sans serif)">
/*<![CDATA[*/
a {
text-decoration: none;
}
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a.smpl {
color: black;
}
a:hover {
text-decoration: underline;
}
a:active {
text-decoration: underline;
}
address {
margin-top: 1em;
margin-left: 2em;
font-style: normal;
}
body {
color: black;
font-family: verdana, helvetica, arial, sans-serif;
font-size: 10pt;
max-width: 55em;
}
cite {
font-style: normal;
}
dd {
margin-right: 2em;
}
dl {
margin-left: 2em;
}
ul.empty {
list-style-type: none;
}
ul.empty li {
margin-top: .5em;
}
dl p {
margin-left: 0em;
}
dt {
margin-top: .5em;
}
h1 {
font-size: 14pt;
line-height: 21pt;
page-break-after: avoid;
}
h1.np {
page-break-before: always;
}
h1 a {
color: #333333;
}
h2 {
font-size: 12pt;
line-height: 15pt;
page-break-after: avoid;
}
h3, h4, h5, h6 {
font-size: 10pt;
page-break-after: avoid;
}
h2 a, h3 a, h4 a, h5 a, h6 a {
color: black;
}
img {
margin-left: 3em;
}
li {
margin-left: 2em;
margin-right: 2em;
}
ol {
margin-left: 2em;
margin-right: 2em;
}
ol p {
margin-left: 0em;
}
p {
margin-left: 2em;
margin-right: 2em;
}
pre {
margin-left: 3em;
background-color: lightyellow;
padding: .25em;
}
pre.text2 {
border-style: dotted;
border-width: 1px;
background-color: #f0f0f0;
width: 69em;
}
pre.inline {
background-color: white;
padding: 0em;
}
pre.text {
border-style: dotted;
border-width: 1px;
background-color: #f8f8f8;
width: 69em;
}
pre.drawing {
border-style: solid;
border-width: 1px;
background-color: #f8f8f8;
padding: 2em;
}
table {
margin-left: 2em;
}
table.tt {
vertical-align: top;
}
table.full {
border-style: outset;
border-width: 1px;
}
table.headers {
border-style: outset;
border-width: 1px;
}
table.tt td {
vertical-align: top;
}
table.full td {
border-style: inset;
border-width: 1px;
}
table.tt th {
vertical-align: top;
}
table.full th {
border-style: inset;
border-width: 1px;
}
table.headers th {
border-style: none none inset none;
border-width: 1px;
}
table.left {
margin-right: auto;
}
table.right {
margin-left: auto;
}
table.center {
margin-left: auto;
margin-right: auto;
}
caption {
caption-side: bottom;
font-weight: bold;
font-size: 9pt;
margin-top: .5em;
}
table.header {
border-spacing: 1px;
width: 95%;
font-size: 10pt;
color: white;
}
td.top {
vertical-align: top;
}
td.topnowrap {
vertical-align: top;
white-space: nowrap;
}
table.header td {
background-color: gray;
width: 50%;
}
table.header a {
color: white;
}
td.reference {
vertical-align: top;
white-space: nowrap;
padding-right: 1em;
}
thead {
display:table-header-group;
}
ul.toc, ul.toc ul {
list-style: none;
margin-left: 1.5em;
margin-right: 0em;
padding-left: 0em;
}
ul.toc li {
line-height: 150%;
font-weight: bold;
font-size: 10pt;
margin-left: 0em;
margin-right: 0em;
}
ul.toc li li {
line-height: normal;
font-weight: normal;
font-size: 9pt;
margin-left: 0em;
margin-right: 0em;
}
li.excluded {
font-size: 0pt;
}
ul p {
margin-left: 0em;
}
.comment {
background-color: yellow;
}
.center {
text-align: center;
}
.error {
color: red;
font-style: italic;
font-weight: bold;
}
.figure {
font-weight: bold;
text-align: center;
font-size: 9pt;
}
.filename {
color: #333333;
font-weight: bold;
font-size: 12pt;
line-height: 21pt;
text-align: center;
}
.fn {
font-weight: bold;
}
.hidden {
display: none;
}
.left {
text-align: left;
}
.right {
text-align: right;
}
.title {
color: #990000;
font-size: 18pt;
line-height: 18pt;
font-weight: bold;
text-align: center;
margin-top: 36pt;
}
.vcardline {
display: block;
}
.warning {
font-size: 14pt;
background-color: yellow;
}
@media print {
.noprint {
display: none;
}
a {
color: black;
text-decoration: none;
}
table.header {
width: 90%;
}
td.header {
width: 50%;
color: black;
background-color: white;
vertical-align: top;
font-size: 12pt;
}
ul.toc a::after {
content: leader('.') target-counter(attr(href), page);
}
ul.ind li li a {
content: target-counter(attr(href), page);
}
.print2col {
column-count: 2;
-moz-column-count: 2;
column-fill: auto;
}
}
@page {
@top-left {
content: "Internet-Draft";
}
@top-right {
content: "December 2010";
}
@top-center {
content: "Abbreviated Title";
}
@bottom-left {
content: "Doe";
}
@bottom-center {
content: "Expires June 2011";
}
@bottom-right {
content: "[Page " counter(page) "]";
}
}
@page:first {
@top-left {
content: normal;
}
@top-right {
content: normal;
}
@top-center {
content: normal;
}
}
/*]]>*/
</style>
<link href="#rfc.toc" rel="Contents"/>
<link href="#rfc.section.1" rel="Chapter" title="1 Introduction"/>
<link href="#rfc.section.1.1" rel="Chapter" title="1.1 Conventions Used in This Document"/>
<link href="#rfc.section.2" rel="Chapter" title="2 Object Attributes"/>
<link href="#rfc.section.2.1" rel="Chapter" title="2.1 Application Identifier"/>
<link href="#rfc.section.2.2" rel="Chapter" title="2.2 Validator Identifier"/>
<link href="#rfc.section.2.3" rel="Chapter" title="2.3 Launch Phases"/>
<link href="#rfc.section.2.3.1" rel="Chapter" title="2.3.1 Trademark Claims Phase"/>
<link href="#rfc.section.2.4" rel="Chapter" title="2.4 Status Values"/>
<link href="#rfc.section.2.4.1" rel="Chapter" title="2.4.1 State Transition"/>
<link href="#rfc.section.2.5" rel="Chapter" title="2.5 Poll Messaging"/>
<link href="#rfc.section.2.6" rel="Chapter" title="2.6 Mark Validation Models"/>
<link href="#rfc.section.2.6.1" rel="Chapter" title="2.6.1 <launch:codeMark> element"/>
<link href="#rfc.section.2.6.2" rel="Chapter" title="2.6.2 <mark:mark> element"/>
<link href="#rfc.section.2.6.3" rel="Chapter" title="2.6.3 Digital Signature"/>
<link href="#rfc.section.2.6.3.1" rel="Chapter" title="2.6.3.1 <smd:signedMark> element"/>
<link href="#rfc.section.2.6.3.2" rel="Chapter" title="2.6.3.2 <smd:encodedSignedMark> element"/>
<link href="#rfc.section.3" rel="Chapter" title="3 EPP Command Mapping"/>
<link href="#rfc.section.3.1" rel="Chapter" title="3.1 EPP <check> Command"/>
<link href="#rfc.section.3.1.1" rel="Chapter" title="3.1.1 Claims Check Form"/>
<link href="#rfc.section.3.1.2" rel="Chapter" title="3.1.2 Availability Check Form"/>
<link href="#rfc.section.3.1.3" rel="Chapter" title="3.1.3 Trademark Check Form"/>
<link href="#rfc.section.3.2" rel="Chapter" title="3.2 EPP <info> Command"/>
<link href="#rfc.section.3.3" rel="Chapter" title="3.3 EPP <create> Command"/>
<link href="#rfc.section.3.3.1" rel="Chapter" title="3.3.1 Sunrise Create Form"/>
<link href="#rfc.section.3.3.2" rel="Chapter" title="3.3.2 Claims Create Form"/>
<link href="#rfc.section.3.3.3" rel="Chapter" title="3.3.3 General Create Form"/>
<link href="#rfc.section.3.3.4" rel="Chapter" title="3.3.4 Mixed Create Form"/>
<link href="#rfc.section.3.3.5" rel="Chapter" title="3.3.5 Create Response"/>
<link href="#rfc.section.3.4" rel="Chapter" title="3.4 EPP <update> Command"/>
<link href="#rfc.section.3.5" rel="Chapter" title="3.5 EPP <delete> Command"/>
<link href="#rfc.section.3.6" rel="Chapter" title="3.6 EPP <renew> Command"/>
<link href="#rfc.section.3.7" rel="Chapter" title="3.7 EPP <transfer> Command"/>
<link href="#rfc.section.4" rel="Chapter" title="4 Formal Syntax"/>
<link href="#rfc.section.4.1" rel="Chapter" title="4.1 Launch Schema"/>
<link href="#rfc.section.5" rel="Chapter" title="5 IANA Considerations"/>
<link href="#rfc.section.5.1" rel="Chapter" title="5.1 XML Namespace"/>
<link href="#rfc.section.5.2" rel="Chapter" title="5.2 EPP Extension Registry"/>
<link href="#rfc.section.6" rel="Chapter" title="6 Implementation Status"/>
<link href="#rfc.section.6.1" rel="Chapter" title="6.1 Verisign EPP SDK"/>
<link href="#rfc.section.6.2" rel="Chapter" title="6.2 Verisign Consolidated Top Level Domain (CTLD) SRS"/>
<link href="#rfc.section.6.3" rel="Chapter" title="6.3 Verisign .COM / .NET SRS"/>
<link href="#rfc.section.6.4" rel="Chapter" title="6.4 REngin v3.7"/>
<link href="#rfc.section.6.5" rel="Chapter" title="6.5 RegistryEngine EPP Service"/>
<link href="#rfc.section.6.6" rel="Chapter" title="6.6 Neustar EPP SDK"/>
<link href="#rfc.section.6.7" rel="Chapter" title="6.7 gTLD Shared Registry System"/>
<link href="#rfc.section.7" rel="Chapter" title="7 Security Considerations"/>
<link href="#rfc.section.8" rel="Chapter" title="8 Acknowledgements"/>
<link href="#rfc.references" rel="Chapter" title="9 References"/>
<link href="#rfc.references.1" rel="Chapter" title="9.1 Normative References"/>
<link href="#rfc.references.2" rel="Chapter" title="9.2 Informative References"/>
<link href="#rfc.appendix.A" rel="Chapter" title="A Change History"/>
<link href="#rfc.appendix.A.1" rel="Chapter" title="A.1 Change from 00 to 01"/>
<link href="#rfc.appendix.A.2" rel="Chapter" title="A.2 Change from 01 to 02"/>
<link href="#rfc.appendix.A.3" rel="Chapter" title="A.3 Change from 02 to 03"/>
<link href="#rfc.appendix.A.4" rel="Chapter" title="A.4 Change from 03 to 04"/>
<link href="#rfc.appendix.A.5" rel="Chapter" title="A.5 Change from 04 to 05"/>
<link href="#rfc.appendix.A.6" rel="Chapter" title="A.6 Change from 05 to 06"/>
<link href="#rfc.appendix.A.7" rel="Chapter" title="A.7 Change from 06 to 07"/>
<link href="#rfc.appendix.A.8" rel="Chapter" title="A.8 Change from 07 to 08"/>
<link href="#rfc.appendix.A.9" rel="Chapter" title="A.9 Change from 08 to 09"/>
<link href="#rfc.appendix.A.10" rel="Chapter" title="A.10 Change from 09 to 10"/>
<link href="#rfc.appendix.A.11" rel="Chapter" title="A.11 Change from 10 to 11"/>
<link href="#rfc.appendix.A.12" rel="Chapter" title="A.12 Change from 11 to 12"/>
<link href="#rfc.appendix.A.13" rel="Chapter" title="A.13 Change from 12 to EPPEXT 00"/>
<link href="#rfc.appendix.A.14" rel="Chapter" title="A.14 Change EPPEXT 00 to EPPEXT 01"/>
<link href="#rfc.appendix.A.15" rel="Chapter" title="A.15 Change EPPEXT 01 to EPPEXT 02"/>
<link href="#rfc.appendix.A.16" rel="Chapter" title="A.16 Change EPPEXT 02 to EPPEXT 03"/>
<link href="#rfc.appendix.A.17" rel="Chapter" title="A.17 Change EPPEXT 03 to EPPEXT 04"/>
<link href="#rfc.appendix.A.18" rel="Chapter" title="A.18 Change EPPEXT 04 to EPPEXT 05"/>
<link href="#rfc.appendix.A.19" rel="Chapter" title="A.19 Change EPPEXT 05 to EPPEXT 06"/>
<link href="#rfc.appendix.A.20" rel="Chapter" title="A.20 Change EPPEXT 06 to EPPEXT 07"/>
<link href="#rfc.appendix.A.21" rel="Chapter" title="A.21 Change from EPPEXT 07 to REGEXT 00"/>
<link href="#rfc.appendix.A.22" rel="Chapter" title="A.22 Change from REGEXT 00 to REGEXT 01"/>
<link href="#rfc.appendix.A.23" rel="Chapter" title="A.23 Change from REGEXT 01 to REGEXT 02"/>
<link href="#rfc.appendix.A.24" rel="Chapter" title="A.24 Change from REGEXT 02 to REGEXT 03"/>
<link href="#rfc.appendix.A.25" rel="Chapter" title="A.25 Change from REGEXT 03 to REGEXT 04"/>
<link href="#rfc.appendix.A.26" rel="Chapter" title="A.26 Change from REGEXT 04 to REGEXT 05"/>
<link href="#rfc.appendix.A.27" rel="Chapter" title="A.27 Change from REGEXT 05 to REGEXT 06"/>
<link href="#rfc.appendix.A.28" rel="Chapter" title="A.28 Change from REGEXT 06 to REGEXT 07"/>
<link href="#rfc.authors" rel="Chapter"/>
<meta name="generator" content="xml2rfc version 2.5.2 - http://tools.ietf.org/tools/xml2rfc" />
<link rel="schema.dct" href="http://purl.org/dc/terms/" />
<meta name="dct.creator" content="Gould, J., Tan, W., and G. Brown" />
<meta name="dct.identifier" content="urn:ietf:id:draft-ietf-regext-launchphase-07" />
<meta name="dct.issued" scheme="ISO8601" content="2017-12-12" />
<meta name="dct.abstract" content="This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name registrations and applications during the launch of a domain name registry." />
<meta name="description" content="This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name registrations and applications during the launch of a domain name registry." />
</head>
<body>
<table class="header">
<tbody>
<tr>
<td class="left">Internet Engineering Task Force</td>
<td class="right">J. Gould</td>
</tr>
<tr>
<td class="left">Internet-Draft</td>
<td class="right">VeriSign, Inc.</td>
</tr>
<tr>
<td class="left">Intended status: Standards Track</td>
<td class="right">W. Tan</td>
</tr>
<tr>
<td class="left">Expires: June 15, 2018</td>
<td class="right">Cloud Registry</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">G. Brown</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">CentralNic Ltd</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">December 12, 2017</td>
</tr>
</tbody>
</table>
<p class="title">Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)<br />
<span class="filename">draft-ietf-regext-launchphase-07</span></p>
<h1 id="rfc.abstract">
<a href="#rfc.abstract">Abstract</a>
</h1>
<p>This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name registrations and applications during the launch of a domain name registry.</p>
<h1 id="rfc.status">
<a href="#rfc.status">Status of This Memo</a>
</h1>
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on June 15, 2018.</p>
<h1 id="rfc.copyrightnotice">
<a href="#rfc.copyrightnotice">Copyright Notice</a>
</h1>
<p>Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
<p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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.</p>
<hr class="noprint" />
<h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
<ul class="toc">
<li>1. <a href="#rfc.section.1">Introduction</a></li>
<ul><li>1.1. <a href="#rfc.section.1.1">Conventions Used in This Document</a></li>
</ul><li>2. <a href="#rfc.section.2">Object Attributes</a></li>
<ul><li>2.1. <a href="#rfc.section.2.1">Application Identifier</a></li>
<li>2.2. <a href="#rfc.section.2.2">Validator Identifier</a></li>
<li>2.3. <a href="#rfc.section.2.3">Launch Phases</a></li>
<ul><li>2.3.1. <a href="#rfc.section.2.3.1">Trademark Claims Phase</a></li>
</ul><li>2.4. <a href="#rfc.section.2.4">Status Values</a></li>
<ul><li>2.4.1. <a href="#rfc.section.2.4.1">State Transition</a></li>
</ul><li>2.5. <a href="#rfc.section.2.5">Poll Messaging</a></li>
<li>2.6. <a href="#rfc.section.2.6">Mark Validation Models</a></li>
<ul><li>2.6.1. <a href="#rfc.section.2.6.1"><launch:codeMark> element</a></li>
<li>2.6.2. <a href="#rfc.section.2.6.2"><mark:mark> element</a></li>
<li>2.6.3. <a href="#rfc.section.2.6.3">Digital Signature</a></li>
<ul><li>2.6.3.1. <a href="#rfc.section.2.6.3.1"><smd:signedMark> element</a></li>
<li>2.6.3.2. <a href="#rfc.section.2.6.3.2"><smd:encodedSignedMark> element</a></li>
</ul></ul></ul><li>3. <a href="#rfc.section.3">EPP Command Mapping</a></li>
<ul><li>3.1. <a href="#rfc.section.3.1">EPP <check> Command</a></li>
<ul><li>3.1.1. <a href="#rfc.section.3.1.1">Claims Check Form</a></li>
<li>3.1.2. <a href="#rfc.section.3.1.2">Availability Check Form</a></li>
<li>3.1.3. <a href="#rfc.section.3.1.3">Trademark Check Form</a></li>
</ul><li>3.2. <a href="#rfc.section.3.2">EPP <info> Command</a></li>
<li>3.3. <a href="#rfc.section.3.3">EPP <create> Command</a></li>
<ul><li>3.3.1. <a href="#rfc.section.3.3.1">Sunrise Create Form</a></li>
<li>3.3.2. <a href="#rfc.section.3.3.2">Claims Create Form</a></li>
<li>3.3.3. <a href="#rfc.section.3.3.3">General Create Form</a></li>
<li>3.3.4. <a href="#rfc.section.3.3.4">Mixed Create Form</a></li>
<li>3.3.5. <a href="#rfc.section.3.3.5">Create Response</a></li>
</ul><li>3.4. <a href="#rfc.section.3.4">EPP <update> Command</a></li>
<li>3.5. <a href="#rfc.section.3.5">EPP <delete> Command</a></li>
<li>3.6. <a href="#rfc.section.3.6">EPP <renew> Command</a></li>
<li>3.7. <a href="#rfc.section.3.7">EPP <transfer> Command</a></li>
</ul><li>4. <a href="#rfc.section.4">Formal Syntax</a></li>
<ul><li>4.1. <a href="#rfc.section.4.1">Launch Schema</a></li>
</ul><li>5. <a href="#rfc.section.5">IANA Considerations</a></li>
<ul><li>5.1. <a href="#rfc.section.5.1">XML Namespace</a></li>
<li>5.2. <a href="#rfc.section.5.2">EPP Extension Registry</a></li>
</ul><li>6. <a href="#rfc.section.6">Implementation Status</a></li>
<ul><li>6.1. <a href="#rfc.section.6.1">Verisign EPP SDK</a></li>
<li>6.2. <a href="#rfc.section.6.2">Verisign Consolidated Top Level Domain (CTLD) SRS</a></li>
<li>6.3. <a href="#rfc.section.6.3">Verisign .COM / .NET SRS</a></li>
<li>6.4. <a href="#rfc.section.6.4">REngin v3.7</a></li>
<li>6.5. <a href="#rfc.section.6.5">RegistryEngine EPP Service</a></li>
<li>6.6. <a href="#rfc.section.6.6">Neustar EPP SDK</a></li>
<li>6.7. <a href="#rfc.section.6.7">gTLD Shared Registry System</a></li>
</ul><li>7. <a href="#rfc.section.7">Security Considerations</a></li>
<li>8. <a href="#rfc.section.8">Acknowledgements</a></li>
<li>9. <a href="#rfc.references">References</a></li>
<ul><li>9.1. <a href="#rfc.references.1">Normative References</a></li>
<li>9.2. <a href="#rfc.references.2">Informative References</a></li>
</ul><li>Appendix A. <a href="#rfc.appendix.A">Change History</a></li>
<ul><li>A.1. <a href="#rfc.appendix.A.1">Change from 00 to 01</a></li>
<li>A.2. <a href="#rfc.appendix.A.2">Change from 01 to 02</a></li>
<li>A.3. <a href="#rfc.appendix.A.3">Change from 02 to 03</a></li>
<li>A.4. <a href="#rfc.appendix.A.4">Change from 03 to 04</a></li>
<li>A.5. <a href="#rfc.appendix.A.5">Change from 04 to 05</a></li>
<li>A.6. <a href="#rfc.appendix.A.6">Change from 05 to 06</a></li>
<li>A.7. <a href="#rfc.appendix.A.7">Change from 06 to 07</a></li>
<li>A.8. <a href="#rfc.appendix.A.8">Change from 07 to 08</a></li>
<li>A.9. <a href="#rfc.appendix.A.9">Change from 08 to 09</a></li>
<li>A.10. <a href="#rfc.appendix.A.10">Change from 09 to 10</a></li>
<li>A.11. <a href="#rfc.appendix.A.11">Change from 10 to 11</a></li>
<li>A.12. <a href="#rfc.appendix.A.12">Change from 11 to 12</a></li>
<li>A.13. <a href="#rfc.appendix.A.13">Change from 12 to EPPEXT 00</a></li>
<li>A.14. <a href="#rfc.appendix.A.14">Change EPPEXT 00 to EPPEXT 01</a></li>
<li>A.15. <a href="#rfc.appendix.A.15">Change EPPEXT 01 to EPPEXT 02</a></li>
<li>A.16. <a href="#rfc.appendix.A.16">Change EPPEXT 02 to EPPEXT 03</a></li>
<li>A.17. <a href="#rfc.appendix.A.17">Change EPPEXT 03 to EPPEXT 04</a></li>
<li>A.18. <a href="#rfc.appendix.A.18">Change EPPEXT 04 to EPPEXT 05</a></li>
<li>A.19. <a href="#rfc.appendix.A.19">Change EPPEXT 05 to EPPEXT 06</a></li>
<li>A.20. <a href="#rfc.appendix.A.20">Change EPPEXT 06 to EPPEXT 07</a></li>
<li>A.21. <a href="#rfc.appendix.A.21">Change from EPPEXT 07 to REGEXT 00</a></li>
<li>A.22. <a href="#rfc.appendix.A.22">Change from REGEXT 00 to REGEXT 01</a></li>
<li>A.23. <a href="#rfc.appendix.A.23">Change from REGEXT 01 to REGEXT 02</a></li>
<li>A.24. <a href="#rfc.appendix.A.24">Change from REGEXT 02 to REGEXT 03</a></li>
<li>A.25. <a href="#rfc.appendix.A.25">Change from REGEXT 03 to REGEXT 04</a></li>
<li>A.26. <a href="#rfc.appendix.A.26">Change from REGEXT 04 to REGEXT 05</a></li>
<li>A.27. <a href="#rfc.appendix.A.27">Change from REGEXT 05 to REGEXT 06</a></li>
<li>A.28. <a href="#rfc.appendix.A.28">Change from REGEXT 06 to REGEXT 07</a></li>
</ul><li><a href="#rfc.authors">Authors' Addresses</a></li>
</ul>
<h1 id="rfc.section.1"><a href="#rfc.section.1">1.</a> Introduction</h1>
<p id="rfc.section.1.p.1">This document describes an extension mapping for version 1.0 of the <a href="#RFC5730">Extensible Provisioning Protocol (EPP)</a> <cite title="NONE">[RFC5730]</cite>. This EPP mapping specifies a flexible schema that can be used to implement several common use cases related to the provisioning and management of domain name registrations and applications during the launch of a domain name registry.</p>
<p id="rfc.section.1.p.2">It is typical for domain registries to operate in special modes as they begin operation to facilitate allocation of domain names, often according to special rules. This document uses the term "launch phase" and the shorter form "launch" to refer to such a period. Multiple launch phases and multiple models are supported to enable the launch of a domain name registry. What is supported and what is validated is up to server policy. Communication of the server policy is typically performed using an out-of-band mechanism that is not specified in this document.</p>
<p id="rfc.section.1.p.3">The <a href="#RFC5731">EPP domain name mapping</a> <cite title="NONE">[RFC5731]</cite> is designed for the steady-state operation of a registry. During a launch period, the model in place may be different from what is defined in the <a href="#RFC5731">EPP domain name mapping</a> <cite title="NONE">[RFC5731]</cite>. For example, registries often accept multiple applications for the same domain name during the "Sunrise" launch phase, referred to as a Launch Application. A Launch Registration refers to a registration made during a launch phase when the server uses a "first-come, first-served" model. Even in a "first-come, first-served" model, additional steps and information might be required, such as trademark information. In addition, <a href="#RFC7848">RFC 7848</a> <cite title="NONE">[RFC7848]</cite> defines a registry interface for the Trademark Claims or "claims" launch phase that includes support for presenting a Trademark Claims Notice to the Registrant. This document proposes an extension to the domain name mapping in order to provide a uniform interface for the management of Launch Applications and Launch Registrations in launch phases.</p>
<h1 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1.</a> Conventions Used in This Document</h1>
<p id="rfc.section.1.1.p.1">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> <cite title="NONE">[RFC2119]</cite>.</p>
<p id="rfc.section.1.1.p.2">XML 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.</p>
<p id="rfc.section.1.1.p.3">In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol. The use of "..." is used as shorthand for elements defined outside this document.</p>
<p id="rfc.section.1.1.p.4">A Launch Registration is a domain name registration during a launch phase when the server uses a "first-come, first-served" model. Only a single registration for a domain name can exist in the server at a time.</p>
<p id="rfc.section.1.1.p.5">A Launch Application represents the intent to register a domain name during a launch phase when the server accepts multiple applications for a domain name and the server later selects one of the applications to allocate as a registration. Many Launch Applications for a domain name can exist in the server at a time.</p>
<p id="rfc.section.1.1.p.6">The XML namespace prefix "launch" is used for the namespace "urn:ietf:params:xml:ns:launch-1.0", 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.</p>
<p id="rfc.section.1.1.p.7">The XML namespace prefix "smd" is used for the <a href="#RFC7848">[RFC7848]</a> namespace "urn:ietf:params:xml:ns:signedMark-1.0", 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.</p>
<p id="rfc.section.1.1.p.8">The XML namespace prefix "mark" is used for the <a href="#RFC7848">[RFC7848]</a> namespace "urn:ietf:params:xml:ns:mark-1.0", 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.</p>
<h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a href="#attrs" id="attrs">Object Attributes</a></h1>
<p id="rfc.section.2.p.1">This extension adds additional elements to the <a href="#RFC5731">EPP domain name mapping</a> <cite title="NONE">[RFC5731]</cite>. Only those new elements are described here.</p>
<h1 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1.</a> <a href="#applicationID" id="applicationID">Application Identifier</a></h1>
<p id="rfc.section.2.1.p.1">Servers MAY allow multiple applications, referred to as a Launch Application, of the same domain name during its launch phase operations. Upon receiving a valid <domain:create> command to create a Launch Application, the server MUST create an application object corresponding to the request, assign an application identifier for the Launch Application, set the <a href="#RFC5731">[RFC5731]</a> pendingCreate status, and return the application identifier to the client with the <launch:applicationID> element. In order to facilitate correlation, all subsequent launch operations on the Launch Application MUST be qualified by the previously assigned application identifier using the <launch:applicationID> element.</p>
<h1 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2.</a> <a href="#validatorID" id="validatorID">Validator Identifier</a></h1>
<p id="rfc.section.2.2.p.1">The Validator Identifier is the identifier unique to the server, for a Trademark Validator that validates marks and has a repository of validated marks. The OPTIONAL "validatorID" attribute is used to define the Validator Identifier of the Trademark Validator. Registries MAY support more than one Third Party Trademark Validator. The unique set of Validator Identifier values supported by the server is up to server policy. The Internet Corporation for Assigned Names and Numbers (ICANN) Trademark Clearinghouse (TMCH) is the default Trademark Validator and is reserved the Validator Identifier of "tmch". If the ICANN TMCH is not used or multiple Trademark Validators are used, the Validator Identifier MUST be defined using the "validatorID" attribute.</p>
<p id="rfc.section.2.2.p.2">The Validator Identifier MAY be related to one or more issuer identifiers of the <mark:id> element and the <smd:id> element defined in <a href="#RFC7848">[RFC7848]</a>. Both the Validator Identifier and the Issuer Identifier used MUST be unique in the server. If the ICANN TMCH is not used or multiple Trademark Validators are used, the server MUST define the list of supported validator identifiers and MUST make this information available to clients using a mutually acceptable, out-of-band mechanism.</p>
<p id="rfc.section.2.2.p.3">The Validator Identifier may define a non-Trademark Validator that supports a form of claims, where claims and a Validator Identifier can be used for purposes beyond trademarks.</p>
<h1 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3.</a> <a href="#phases" id="phases">Launch Phases</a></h1>
<p id="rfc.section.2.3.p.1">The server MAY support multiple launch phases sequentially or simultaneously. The <launch:phase> element MUST be included by the client to define the target launch phase of the command. The server SHOULD validate the phase and MAY validate the sub-phase of the <launch:phase> element against the active phase and OPTIONAL sub-phase of the server, and return an EPP error result code of 2306 if there is a mismatch.</p>
<p id="rfc.section.2.3.p.2">The following launch phase values are defined: </p>
<dl>
<dt>sunrise:</dt>
<dd style="margin-left: 8">The phase during which trademark holders can submit registrations or applications with trademark information that can be validated by the server.</dd>
<dt>landrush:</dt>
<dd style="margin-left: 8">A post-Sunrise phase when non-trademark holders are allowed to register domain names with steps taken to address a large volume of initial registrations.</dd>
<dt>claims:</dt>
<dd style="margin-left: 8">The phase, as defined in the <a href="#claimsPhase">Section 2.3.1</a>, in which a Claims Notice must be displayed to a prospective registrant of a domain name that matches trademarks.</dd>
<dt>open:</dt>
<dd style="margin-left: 8">A phase that is also referred to as "steady state". Servers may require additional trademark protection during this phase.</dd>
<dt>custom:</dt>
<dd style="margin-left: 8">A custom server launch phase that is defined using the "name" attribute.</dd>
</dl>
<p id="rfc.section.2.3.p.3">For extensibility, the <launch:phase> element includes an OPTIONAL "name" attribute that can define a sub-phase, or the full name of the phase when the <launch:phase> element has the "custom" value. For example, the "claims" launch phase could have two sub-phases that include "landrush" and "open".</p>
<p id="rfc.section.2.3.p.4">Launch phases MAY overlap to support the "claims" launch phase, defined in the <a href="#claimsPhase">Section 2.3.1</a>, and to support a traditional "landrush" launch phase. The overlap of the "claims" and "landrush" launch phases SHOULD be handled by setting "claims" as the <launch:phase> value and setting "landrush" as the sub-phase with the "name" attribute. For example, the <launch:phase> element should be <launch:phase name="landrush">claims</launch:phase>. </p>
<h1 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1.</a> <a href="#claimsPhase" id="claimsPhase">Trademark Claims Phase</a></h1>
<p id="rfc.section.2.3.1.p.1">The Trademark Claims Phase is when a Claims Notice must be displayed to a prospective registrant of a domain name that matches trademarks. See <a href="#I-D.ietf-regext-tmch-func-spec">[I-D.ietf-regext-tmch-func-spec]</a> for additional details of trademark claims handling. The source of the trademarks is a Trademark Validator and the source of the Claims Notice information is a Claim Notice Information Service (CNIS), which may be directly linked to a Trademark Validator. The client interfaces with the server to determine if a trademark exists for a domain name, interfaces with a CNIS to get the Claims Notice information, and interfaces with the server to pass the Claims Notice acceptance information in a create command. This document supports the Trademark Claims Phase in two ways including:</p>
<p/>
<dl>
<dt>Claims Check Form:</dt>
<dd style="margin-left: 8">Is defined in <a href="#claimsCheckForm">Section 3.1.1</a> and is used to determine whether or not there are any matching trademarks for a domain name. If there is at least one matching trademark that exists for the domain name, a claims key is returned. The mapping of domain names and the claims keys is based on an out-of-band interface between the server and the Trademark Validator. The CNIS associated with the claims key <a href="#validatorID">Validator Identifier</a> <cite title="NONE">[validatorID]</cite> MUST accept the claims key as the basis for retrieving the claims information.</dd>
<dt>Claims Create Form:</dt>
<dd style="margin-left: 8">Is defined in <a href="#claimsCreateForm">Section 3.3.2</a> and is used to pass the Claims Notice acceptance information in a create command. The notice identifier (<launch:noticeID>) format, validation rules, and server processing is up to the interface between the server and the Trademark Validator. The CNIS associated with the <a href="#validatorID">Validator Identifier</a> <cite title="NONE">[validatorID]</cite> MUST generate a notice identifier compliant with the <launch:noticeID> element.</dd>
</dl>
<div id="rfc.figure.1"/>
<div id="claimsRegistrationFlow"/>
<p>The following shows the Trademark Claims Phase registration flow:</p>
<pre>
.------------. .--------. .--------. .------.
| Registrant | | Client | | Server | | CNIS |
'------------' '--------' '--------' '------'
| Request Domain | | |
| Registration | | |
|--------------->| Domain Check | |
| |--------------------------->| |
| Domain | Domain Unavailable .------------. |
| Unavailable |<---------------------( Available? ) |
|<---------------| No '------------' |
| | Domain Available | Yes |
| |<---------------------------| |
| | Domain Claims Check | |
| |--------------------------->| |
| | .---------. |
| | Claims Don't Exist / Does \ |
| |<--------------------( Domain have ) |
| | No \ Claims? / |
| | '---------' |
| | Domain Create | | Yes |
| |--------------------------->| | |
| Domain | Domain Registered | | |
| Registered |<---------------------------| | |
|<---------------| | |
| | |
| | Claims Exist with Claims Keys | |
| |<------------------------------' |
| | |
.-----. | | Request Claims Info with Claims Key |
|Abort| | Display |-------------------------------------->|
'-----' | Claims | Return Claims Info |
^ | Notice |<--------------------------------------|
| No |<---------------| |
| .------. Yes | |
'-( Ack? )----------->| Domain Claims Create Form | |
'------' |--------------------------->| |
| Registration | Error .----------------------. |
| Error |<-----------( Validation Successful? ) |
|<---------------| No '----------------------' |
| | | Yes |
| Domain | Domain Registered | |
| Registered |<---------------------------| |
|<---------------| | |
</pre>
<p class="figure">Figure 1</p>
<h1 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4.</a> <a href="#statuses" id="statuses">Status Values</a></h1>
<p id="rfc.section.2.4.p.1">A Launch Application or Launch Registration object MAY have a launch status value. The <launch:status> element is used to convey the launch status pertaining to the object, beyond what is specified in the object mapping. A Launch Application or Launch Registration MUST set the <a href="#RFC5731">[RFC5731]</a> "pendingCreate" status if a launch status is supported and the launch status is not one of the final statuses ("allocated" and "rejected").</p>
<p id="rfc.section.2.4.p.2">The following status values are defined using the required "s" attribute: </p>
<dl>
<dt>pendingValidation:</dt>
<dd style="margin-left: 8">The initial state of a newly-created application or registration object. The application or registration requires validation, but the validation process has not yet completed.</dd>
<dt>validated:</dt>
<dd style="margin-left: 8">The application or registration meets relevant registry rules.</dd>
<dt>invalid:</dt>
<dd style="margin-left: 8">The application or registration does not validate according to registry rules. Server policies permitting, it may transition back into "pendingValidation" for revalidation, after modifications are made to ostensibly correct attributes that caused the validation failure. </dd>
<dt>pendingAllocation:</dt>
<dd style="margin-left: 8">The allocation of the application or registration is pending based on the results of some out-of-band process (for example, an auction).</dd>
<dt>allocated:</dt>
<dd style="margin-left: 8">The object corresponding to the application or registration has been provisioned. This is a possible end state of an application or registration object.</dd>
<dt>rejected:</dt>
<dd style="margin-left: 8">The application or registration object was not provisioned. This is a possible end state of an application or registration object.</dd>
<dt>custom:</dt>
<dd style="margin-left: 8">A custom status that is defined using the "name" attribute.</dd>
</dl>
<p id="rfc.section.2.4.p.3">Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object. The OPTIONAL "lang" attribute, as defined in <a href="#RFC5646">[RFC5646]</a>, MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English).</p>
<p id="rfc.section.2.4.p.4">For extensibility the <launch:status> element includes an OPTIONAL "name" attribute that can define a sub-status or the full name of the status when the status value is "custom". The server SHOULD use one of the non-"custom" status values.</p>
<p id="rfc.section.2.4.p.5">Status values MAY be skipped. For example, an application or registration MAY immediately start at the "allocated" status or an application or registration MAY skip the "pendingAllocation" status. If the launch phase does not require validation of a request, an application or registration MAY immediately skip to "pendingAllocation".</p>
<h1 id="rfc.section.2.4.1"><a href="#rfc.section.2.4.1">2.4.1.</a> State Transition</h1>
<div id="rfc.figure.2"/>
<div id="fsm"/>
<p>The transitions between the states is a matter of server policy. This diagram defines one possible set of permitted transitions.</p>
<pre>
| request
|
| +--------------------------+
| | |
v v |
+-------------------+ |
| | |
| pendingValidation +--------------+ |
| | | |
+---------+---------+ | |
| | |
| | |
v v |
+-----------+ +---------+ |
| | | | |
| validated | | invalid +--+
| | | |
+-----+-----+ +----+----+
| |
| |
v |
+-------------------+ |
| | |
| pendingAllocation +-----------+ |
| | | |
+---------+---------+ | |
| | |
| | |
| | |
| | |
| | |
v v v
+---------+ +--------+
/ \ / \
| allocated | | rejected |
\ / \ /
+---------+ +--------+
</pre>
<p class="figure">Figure 2</p>
<h1 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5.</a> <a href="#pollMessaging" id="pollMessaging">Poll Messaging</a></h1>
<p id="rfc.section.2.5.p.1">A Launch Application MUST be handled as an EPP domain name object as specified in <a href="#RFC5731">RFC 5731</a> <cite title="NONE">[RFC5731]</cite>, with the "pendingCreate" status and with the launch status values defined in <a href="#statuses">Section 2.4</a>. A Launch Registration MUST be handled as an EPP domain name object as specified in <a href="#RFC5731">RFC 5731</a> <cite title="NONE">[RFC5731]</cite>, with the "pendingCreate" status and with the launch status values defined in <a href="#statuses">Section 2.4</a> As a Launch Application or Launch Registration transitions between the status values defined in <a href="#statuses">Section 2.4</a>, the server SHOULD insert poll messages, per <a href="#RFC5730">[RFC5730]</a>, for the applicable intermediate statuses, including the "pendingValidation", "validated", "pendingAllocation, and "invalid" statuses, using the <domain:infData> element with the <launch:infData> extension. The <domain:infData> element MAY contain non-mandatory information, like contact and name server information. Also, further extensions that would normally be included in the response of a <domain:info> command, per <a href="#RFC5731">[RFC5731]</a>, MAY be included. For the final statuses, including the "allocated" and "rejected" statuses, the server MUST insert a <domain:panData> poll message, per <a href="#RFC5731">[RFC5731]</a>, with the <launch:infData> extension.</p>
<p>The following is an example poll message for a Launch Application that has transitioned to the "pendingAllocation" state.</p>
<pre>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application pendingAllocation.</msg>
S: </msgQ>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name>
S: ...
S: </domain:infData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="pendingAllocation"/>
S: </launch:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp></pre>
<p>The following is an example <domain:panData> poll message for an "allocated" Launch Application.</p>
<pre>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application successfully allocated.</msg>
S: </msgQ>
S: <resData>
S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="allocated"/>
S: </launch:infData>
S: </extension>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp></pre>
<p>The following is an example <domain:panData> poll message for an "allocated" Launch Registration.</p>
<pre>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Registration successfully allocated.</msg>
S: </msgQ>
S: <resData>
S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:status s="allocated"/>
S: </launch:infData>
S: </extension>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp></pre>
<h1 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6.</a> <a href="#validationModels" id="validationModels">Mark Validation Models</a></h1>
<p id="rfc.section.2.6.p.1">A server MUST support at least one of the following models for validating trademark information:</p>
<p/>
<dl>
<dt>code:</dt>
<dd style="margin-left: 8">Use of a mark code by itself to validate that the mark matches the domain name. This model is supported using the <launch:codeMark> element with just the <launch:code> element.</dd>
<dt>mark:</dt>
<dd style="margin-left: 8">The mark information is passed without any other validation element. The server will use some custom form of validation to validate that the mark information is authentic. This model is supported using the <launch:codeMark> element with just the <a href="#mark"><mark:mark></a> <cite title="NONE">[mark]</cite> element.</dd>
<dt>code with mark:</dt>
<dd style="margin-left: 8">A code is used along with the mark information by the server to validate the mark utilizing an external party. The code represents some form of secret that matches the mark information passed. This model is supported using the <launch:codeMark> element that contains both the <launch:code> and the <a href="#mark"><mark:mark></a> <cite title="NONE">[mark]</cite> elements.</dd>
<dt>signed mark:</dt>
<dd style="margin-left: 8">The mark information is digitally signed as described in the <a href="#digitalsignature">Digital Signature</a> <cite title="NONE">[digitalsignature]</cite> section. The digital signature can be directly validated by the server using the public key of the external party that created the signed mark using its private key. This model is supported using the <a href="#signedMark"><smd:signedMark></a> <cite title="NONE">[signedMark]</cite> and <a href="#encodedSignedMark"><smd:encodedSignedMark></a> <cite title="NONE">[encodedSignedMark]</cite> elements.</dd>
</dl>
<p id="rfc.section.2.6.p.3">More than one <launch:codeMark>, <a href="#signedMark"><smd:signedMark></a> <cite title="NONE">[signedMark]</cite>, or <a href="#encodedSignedMark"><smd:encodedSignedMark></a> <cite title="NONE">[encodedSignedMark]</cite> element MAY be specified. The maximum number of marks per domain name is up to server policy.</p>
<h1 id="rfc.section.2.6.1"><a href="#rfc.section.2.6.1">2.6.1.</a> <a href="#codeMark" id="codeMark"><launch:codeMark> element</a></h1>
<p id="rfc.section.2.6.1.p.1">The <launch:codeMark> element is used by the "code", "mark", and "code with mark" validation models, has the following child elements:</p>
<p/>
<dl>
<dt><launch:code>:</dt>
<dd style="margin-left: 8">OPTIONAL mark code used to validate the <a href="#mark"><mark:mark></a> <cite title="NONE">[mark]</cite> information. The mark code is be a mark-specific secret that the server can verify against a third party. The OPTIONAL "validatorID" attribute is the <a href="#validatorID">Validator Identifier</a> <cite title="NONE">[validatorID]</cite> whose value indicates which Trademark Validator that the code originated from, with no default value.</dd>
<dt><mark:mark>:</dt>
<dd style="margin-left: 8">OPTIONAL mark information with child elements defined in the <a href="#mark">Mark</a> <cite title="NONE">[mark]</cite> section.</dd>
</dl>
<p>The following is an example <launch:codeMark> element with both a <launch:code> and <a href="#mark"><mark:mark></a> <cite title="NONE">[mark]</cite> element. </p>
<pre>
<launch:codeMark>
<launch:code validatorID="sample">
49FD46E6C4B45C55D4AC</launch:code>
<mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
...
</mark:mark>
</launch:codeMark></pre>
<h1 id="rfc.section.2.6.2"><a href="#rfc.section.2.6.2">2.6.2.</a> <a href="#mark" id="mark"><mark:mark> element</a></h1>
<p id="rfc.section.2.6.2.p.1">A <mark:mark> element describes an applicant's prior right to a given domain name that is used with the "mark", "mark with code", and the "signed mark" validation models. The <mark:mark> element is defined in <a href="#RFC7848">[RFC7848]</a>. A new mark format can be supported by creating a new XML schema for the mark that has an element that substitutes for the <mark:abstractMark> element from <a href="#RFC7848">[RFC7848]</a>.</p>
<h1 id="rfc.section.2.6.3"><a href="#rfc.section.2.6.3">2.6.3.</a> <a href="#digitalsignature" id="digitalsignature">Digital Signature</a></h1>
<p id="rfc.section.2.6.3.p.1">Digital signatures MAY be used by the server to validate the mark information, when using the "signed mark" validation model with the <a href="#signedMark"><smd:signedMark></a> <cite title="NONE">[signedMark]</cite> element and the <a href="#encodedSignedMark"><smd:encodedSignedMark></a> <cite title="NONE">[encodedSignedMark]</cite> element. When using digital signatures the server MUST validate the digital signature. </p>
<h1 id="rfc.section.2.6.3.1"><a href="#rfc.section.2.6.3.1">2.6.3.1.</a> <a href="#signedMark" id="signedMark"><smd:signedMark> element</a></h1>
<p id="rfc.section.2.6.3.1.p.1">The <smd:signedMark> element contains the digitally signed mark information. The <smd:signedMark> element is defined in <a href="#RFC7848">[RFC7848]</a>. A new signed mark format can be supported by creating a new XML schema for the signed mark that has an element that substitutes for the <smd:abstractSignedMark> element from <a href="#RFC7848">[RFC7848]</a>. </p>
<h1 id="rfc.section.2.6.3.2"><a href="#rfc.section.2.6.3.2">2.6.3.2.</a> <a href="#encodedSignedMark" id="encodedSignedMark"><smd:encodedSignedMark> element</a></h1>
<p id="rfc.section.2.6.3.2.p.1">The <smd:encodedSignedMark> element contains an encoded form of the digitally signed <a href="#signedMark"><smd:signedMark></a> <cite title="NONE">[signedMark]</cite> element. The <smd:encodedSignedMark> element is defined in <a href="#RFC7848">[RFC7848]</a>. A new encoded signed mark format can be supported by creating a new XML schema for the encoded signed mark that has an element that substitutes for the <smd:encodedSignedMark> element from <a href="#RFC7848">[RFC7848]</a>. </p>
<h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a href="#commands" id="commands">EPP Command Mapping</a></h1>
<p id="rfc.section.3.p.1">A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification <a href="#RFC5730">[RFC5730]</a>. The command mappings described here are specifically for use in the Launch Phase Extension.</p>
<p id="rfc.section.3.p.2">This mapping is designed to be flexible, requiring only a minimum set of required elements.</p>
<p id="rfc.section.3.p.3">While it is meant to serve several use cases, it does not prescribe any interpretation by the client or server. Such processing is typically highly policy-dependent and therefore specific to implementations.</p>
<p id="rfc.section.3.p.4">Operations on application objects are done via one or more of the existing EPP verbs defined in the <a href="#RFC5731">EPP domain name mapping</a> <cite title="NONE">[RFC5731]</cite>. Registries MAY choose to support a subset of the operations.</p>
<h1 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1.</a> <a href="#checkCommand" id="checkCommand">EPP <check> Command</a></h1>
<p id="rfc.section.3.1.p.1">There are three forms of the extension to the EPP <check> command: the <a href="#claimsCheckForm">Claims Check Form</a> <cite title="NONE">[claimsCheckForm]</cite>, the <a href="#availCheckForm">Availability Check Form</a> <cite title="NONE">[availCheckForm]</cite>, and the <a href="#trademarkCheckForm">Trademark Check Form</a> <cite title="NONE">[trademarkCheckForm]</cite>. The <launch:check> element "type" attribute defines the form, with the value of "claims" for the <a href="#claimsCheckForm">Claims Check Form</a> <cite title="NONE">[claimsCheckForm]</cite>, with the value of "avail" for the <a href="#availCheckForm">Availability Check Form</a> <cite title="NONE">[availCheckForm]</cite>, and with the value of "trademark" for the <a href="#trademarkCheckForm">Trademark Check Form</a> <cite title="NONE">[trademarkCheckForm]</cite>. The default value of the "type" attribute is "claims". The forms supported by the server is determined by server policy. The server MUST return an EPP error result code of 2307 if it receives a check form that is not supported.</p>
<h1 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1.</a> <a href="#claimsCheckForm" id="claimsCheckForm">Claims Check Form</a></h1>
<p id="rfc.section.3.1.1.p.1">The Claims Check Form defines a new command called the Claims Check Command that is used to determine whether or not there are any matching trademarks, in the specified launch phase, for each domain name passed in the command, that requires the use of the "Claims Create Form" on a Domain Create Command. The availability check information defined in the <a href="#RFC5731">EPP domain name mapping</a> <cite title="NONE">[RFC5731]</cite> MUST NOT be returned for the Claims Check Command. This form is the default form and MAY be explicitly identified by setting the <launch:check> "type" attribute to "claims".</p>
<p id="rfc.section.3.1.1.p.2">Instead of returning whether the domain name is available, the Claims Check Command will return whether or not at least one matching trademark exists for the domain name, that requires the use of the "Claims Create Form" on a Domain Create Command. If there is at least one matching trademark that exists for the domain name, a <launch:claimKey> element is returned. The client MAY then use the value of the <launch:claimKey> element to obtain information needed to generate the Trademark Claims Notice from Trademark Validator based on the <a href="#validatorID">Validator Identifier</a> <cite title="NONE">[validatorID]</cite>. The unique notice identifier of the Trademark Claims Notice MUST be passed in the <launch:noticeID> element of the extension to the <a href="#createCommand">Create Command</a> <cite title="NONE">[createCommand]</cite>.</p>
<p id="rfc.section.3.1.1.p.3">The <domain:name> elements in the EPP <check> command of <a href="#RFC5731">EPP domain name mapping</a> <cite title="NONE">[RFC5731]</cite> define the domain names to check for matching trademarks. The <launch:check> element contains the following child elements:</p>
<p/>
<dl>
<dt><launch:phase>:</dt>
<dd style="margin-left: 4">Contains the value of the active launch phase of the server. The server SHOULD validate the value according to <a href="#phases">Section 2.3</a>.</dd>
</dl>
<p>Example Claims Check command using the <check> domain command and the <launch:check> extension with the "type" explicitly set to "claims", to determine if "domain1.example", "domain2.example", and "domain3.example" require claims notices during the "claims" launch phase:</p>
<pre>
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <check>
C: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain1.example</domain:name>
C: <domain:name>domain2.example</domain:name>
C: <domain:name>domain3.example</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="claims">
C: <launch:phase>claims</launch:phase>
C: </launch:check>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp></pre>
<p id="rfc.section.3.1.1.p.5">If the <check> command has been processed successfully, the EPP <response> MUST contain an <extension> <launch:chkData> element that identifies the launch namespace. The <launch:chkData> element contains the following child elements:</p>
<p/>
<dl>
<dt><launch:phase>:</dt>
<dd style="margin-left: 4">The phase that mirrors the <launch:phase> element included in the <launch:check>.</dd>
<dt><launch:cd>:</dt>
<dd style="margin-left: 4">One or more <launch:cd> elements that contain the following child elements:</dd>
<dt></dt>
<dd style="margin-left: 4">
<dl>
<dt><launch:name>:</dt>
<dd style="margin-left: 4">Contains the fully qualified name of the queried domain name. This element MUST contain an "exists" attribute whose value indicates if a matching trademark exists for the domain name that requires the use of the "Claims Create Form" on a Domain Create Command. A value of "1" (or "true") means that a matching trademark does exist and that the "Claims Create Form" is required on a Domain Create Command. A value of "0" (or "false") means that a matching trademark does not exist or that the "Claims Create Form" is NOT required on a Domain Create Command.</dd>
<dt><launch:claimKey>:</dt>
<dd style="margin-left: 4">Zero or more OPTIONAL claim keys that MAY be passed to a third-party Trademark Validator such as the ICANN Trademark Clearinghouse (TMCH) for querying the information needed to generate a Trademark Claims Notice. The <launch:claimKey> is used as the key for the query in place of the domain name to securely query the service without using a well-known value like a domain name. The OPTIONAL "validatorID" attribute is the <a href="#validatorID">Validator Identifier</a> <cite title="NONE">[validatorID]</cite> whose value indicates which Trademark Validator to query for the Claims Notice information, with the default being the ICANN TMCH. The "validatorID" attribute MAY reference a non-trademark claims clearinghouse identifier to support other forms of claims notices.</dd>
</dl>
</dd>
</dl>
<p>Example Claims Check response when a claims notice is not required for the domain name domain1.example, a claims notice is required for the domain name domain2.example in the "tmch", and a claims notice is required for the domain name domain3.example in the "tmch" and "custom-tmch", for the "claims" launch phase:</p>
<pre>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <extension>