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
|
<pre>Network Working Group S. Hollenbeck
Request for Comments: 3915 VeriSign, Inc.
Category: Standards Track September 2004
<span class="h1">Domain Registry Grace Period Mapping for the</span>
<span class="h1">Extensible Provisioning Protocol (EPP)</span>
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004).
Abstract
This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for the management of Domain Name System (DNS)
domain names subject to "grace period" policies defined by the
Internet Corporation for Assigned Names and Numbers (ICANN). Grace
period policies exist to allow protocol actions to be reversed or
otherwise revoked during a short period of time after the protocol
action has been performed. Specified in XML, this mapping extends
the EPP domain name mapping to provide additional features required
for grace period processing.
<span class="grey">Hollenbeck Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Conventions Used In This Document. . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Redemption Grace Period State Diagram . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Object Attributes . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.1">3.1</a>. Status Values . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.2">3.2</a>. Registration Data and Supporting Information . . . . . . <a href="#page-7">7</a>
<a href="#section-3.3">3.3</a>. Dates and Times . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.4">3.4</a>. Client Statements . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-4">4</a>. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-4.1">4.1</a> EPP Query Commands . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-4.1.1">4.1.1</a>. EPP <check> Command . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-4.1.2">4.1.2</a>. EPP <info> Command . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-4.1.3">4.1.3</a>. EPP <transfer> Command . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-4.2">4.2</a>. EPP Transform Commands . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-4.2.1">4.2.1</a>. EPP <create> Command . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-4.2.2">4.2.2</a>. EPP <delete> Command . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-4.2.3">4.2.3</a>. EPP <renew> Command . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-4.2.4">4.2.4</a>. EPP <transfer> Command . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-4.2.5">4.2.5</a>. EPP <update> Command . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-5">5</a>. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-6">6</a>. Internationalization Considerations . . . . . . . . . . . . . <a href="#page-19">19</a>
<a href="#section-7">7</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
<span class="grey">Hollenbeck Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document describes an extension mapping for version 1.0 of the
Extensible Provisioning Protocol (EPP) described in <a href="./rfc3730">RFC 3730</a> [<a href="#ref-1" title=""Extensible Provisioning Protocol (EPP)"">1</a>].
This mapping, an extension of the domain name mapping described in
<a href="./rfc3731">RFC 3731</a> [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>], is specified using the Extensible Markup Language (XML)
1.0 [<a href="#ref-3" title=""Extensible Markup Language (XML) 1.0 (2nd ed)"">3</a>] and XML Schema notation ([<a href="#ref-4" title=""XML Schema Part 1: Structures"">4</a>], [<a href="#ref-5" title=""XML Schema Part 2: Datatypes"">5</a>]).
The EPP core protocol specification [<a href="#ref-1" title=""Extensible Provisioning Protocol (EPP)"">1</a>] provides a complete
description of EPP command and response structures. A thorough
understanding of the base protocol specification is necessary to
understand the mapping described in this document.
Over the course of several months in 2002, The Internet Corporation
for Assigned Names and Numbers (ICANN) developed an implementation
proposal to provide a "grace period" for Domain Name System (DNS)
domain name recovery (or redemption) before a domain name is purged
from the repository of the authoritative registry for the domain
name. This mapping extends the EPP domain <update> command to
initiate the redemption process for a domain name that has entered
the Redemption Grace Period (RGP) and it extends the EPP domain
<info> response to identify the status of domains that have entered
various grace periods defined by ICANN policy.
In March 2003, ICANN published a task force report describing other
domain registry grace periods related to EPP operations. This
mapping describes extension status values to note the grace periods
described in the report, including:
o An "add grace period" after the initial registration of a domain
name. If the domain name is deleted by the registrar during this
period, the registry provides a credit to the registrar for the
cost of the registration.
o An "auto-renew grace period" after a domain name registration
period expires and is extended (renewed) automatically by the
registry. If the domain name is deleted by the registrar during
this period, the registry provides a credit to the registrar for
the cost of the renewal.
o A "renew grace period" after a domain name registration period is
explicitly extended (renewed) by the registrar. If the domain
name is deleted by the registrar during this period, the registry
provides a credit to the registrar for the cost of the renewal.
<span class="grey">Hollenbeck Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
o A "transfer grace period" after the successful transfer of domain
name registration sponsorship from one registrar to another
registrar. If the domain name is deleted by the new sponsoring
registrar during this period, the registry provides a credit to
the registrar for the cost of the transfer.
Each grace period exists for a specific period of time that is
typically measured in days. The duration of each grace period is a
matter of registry operational policy that is not addressed in this
document.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used In This Document</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="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a> [<a href="#ref-6" title=""Key words for use in RFCs to Indicate Requirement Levels"">6</a>].
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 is provided only to illustrate element
relationships and is not a REQUIRED feature of this specification.
XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the
character case presented to develop a conforming implementation.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Redemption Grace Period State Diagram</span>
The Redemption Grace Period (RGP) involves several domain state
transitions as a domain name moves through the redemption process:
1. A domain is initially in the EPP "ok" status, or some other
status that allows processing of the EPP <delete> command.
2. A <delete> command is received and processed for the domain name.
3. RGP begins once the <delete> command is processed successfully.
The EPP status changes to "pendingDelete", and the RGP status is
initialized to "redemptionPeriod". The domain remains in this
state until either a <restore> operation is requested or the
redemption period elapses.
4. A <restore> operation can be requested using the extended EPP
<update> command. Go to step 8 if the redemption period elapses
before a <restore> request is received.
<span class="grey">Hollenbeck Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
5. If the <restore> is successful, the Registry waits to receive a
restore report from the registrar for a period of time defined by
the Registry. The EPP status remains "pendingDelete" and the RGP
status changes to "pendingRestore". While this extension defines
a method to deliver a restore report via EPP, an out-of-band
mechanism (such as a web site) can also be used to deliver
restore reports.
6. The domain name returns to the redemption period state (state 3)
if a restore report is not received.
7. If a restore report is received the EPP status returns to "ok"
(or whatever it was prior to processing the <delete> command),
and the RGP status is removed completely.
8. The redemption period elapses before a <restore> request is
received.
9. The EPP status remains "pendingDelete" and the RGP status changes
to "pendingDelete". The domain name remains in this state for a
period of time defined by the Registry.
10. The domain name is purged once the pending delete period elapses.
11. The domain name is available for re-registration.
<span class="grey">Hollenbeck Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
Figure 1: RGP State Diagram
|
v
+----------------------+ (2) +----------------------+
|EPP: ok (1)| <delete> |EPP: pendingDelete (3)|
|RGP: N/A |--------->|RGP: redemptionPeriod |
+----------------------+ +----------------------+
^ (4) | ^ |
| <restore> | | No (8) |
| +-----------+ | <restore> |
| | | |
| v | v
| +----------------------+ | +----------------------+
| |EPP: pendingDelete (5)| | |EPP: pendingDelete (9)|
| |RGP: pendingRestore |---------+ |RGP: pendingDelete |
| +----------------------+ Report +----------------------+
| | not (6) |
| (7) | Received Purge (10) |
| Report Received | |
+--------------------+ v
+----------------------+
| Purged (11)|
| |
+----------------------+
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Object Attributes</span>
This extension adds additional elements to the EPP domain name
mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>]. Only new element descriptions are described here.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Status Values</span>
This extension defines new status values to represent the different
states that a domain name can be in as a result of grace period
processing. These are:
addPeriod: This grace period is provided after the initial
registration of a domain name. If the domain name is deleted by
the registrar during this period, the registry provides a credit
to the registrar for the cost of the registration.
autoRenewPeriod: This grace period is provided after a domain
name registration period expires and is extended (renewed)
automatically by the registry. If the domain name is deleted by
the registrar during this period, the registry provides a credit
to the registrar for the cost of the renewal.
<span class="grey">Hollenbeck Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
renewPeriod: This grace period is provided after a domain name
registration period is explicitly extended (renewed) by the
registrar. If the domain name is deleted by the registrar during
this period, the registry provides a credit to the registrar for
the cost of the renewal.
transferPeriod: This grace period is provided after the
successful transfer of domain name registration sponsorship from
one registrar to another registrar. If the domain name is deleted
by the new sponsoring registrar during this period, the registry
provides a credit to the registrar for the cost of the transfer.
redemptionPeriod: This status value is used to describe a
domain for which a <delete> command has been received, but the
domain has not yet been purged because an opportunity exists to
restore the domain and abort the deletion process.
pendingRestore: This status value is used to describe a domain that
is in the process of being restored after being in the
redemptionPeriod state.
pendingDelete: This status value is used to describe a domain that
has entered the purge processing state after completing the
redemptionPeriod state. A domain in this status MUST also be in
the pendingDelete status described in the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>].
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Registration Data and Supporting Information</span>
This extension allows a client to provide copies of registration data
(whois [<a href="#ref-9" title=""NICNAME/WHOIS"">9</a>] data, for example) and supporting information in a restore
report as required by the RGP process. No specific format is
required by this extension; both free text and XML markup MAY be
used.
Operators of servers that provide registration data might find it
useful to provide grace period status values in their responses to
client queries. This information can be useful to people who want to
understand the operations that can be performed on a domain name at
any give time.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Dates and Times</span>
Date and time attribute values MUST be represented in Universal
Coordinated Time (UTC) using the Gregorian calendar. The extended
date-time form using upper case "T" and "Z" characters defined in <a href="./rfc3339">RFC</a>
<a href="./rfc3339">3339</a> [<a href="#ref-7" title=""Date and Time on the Internet: Timestamps"">7</a>] MUST be used to represent date-time values as XML Schema
does not support truncated date-time forms or lower case "T" and "Z"
characters.
<span class="grey">Hollenbeck Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Client Statements</span>
The RGP process requires a client to make two statements regarding
the data included in a restore report. No specific format is
required by this extension; both free text and XML markup MAY be
used. English is the default language used within the statements,
but other languages MAY be used.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. EPP Command Mapping</span>
A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [<a href="#ref-1" title=""Extensible Provisioning Protocol (EPP)"">1</a>]. The command mappings
described here are specifically for use in implementing redemption
grace period processes via EPP.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. EPP Query Commands</span>
EPP provides three commands to retrieve object information: <check>
to determine if an object is known to the server, <info> to retrieve
detailed information associated with an object, and <transfer> to
retrieve object transfer status information.
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. EPP <check> Command</span>
This extension does not add any elements to the EPP <check> command
or <check> response described in the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>].
<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>. EPP <info> Command</span>
This extension does not add any elements to the EPP <info> command
described in the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>]. Additional elements are
defined for the <info> response.
When an <info> command has been processed successfully, the EPP
<resData> element MUST contain child elements as described in [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>]. In
addition, the EPP <extension> element MUST contain a child
<rgp:infData> element that identifies the registry grace period
namespace and the location of the registry grace period schema. The
<rgp:infData> element contains a single <rgp:rgpStatus> element that
contains a single attribute "s" whose value describes the current
grace period status of the domain. Possible status values are
described in section <a href="#section-3.1">Section 3.1</a>.
<span class="grey">Hollenbeck Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
Example <info> response for "addPeriod" status:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns1.example.net</domain:hostObj>
S: </domain:ns>
S: <domain:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientX</domain:crID>
S: <domain:crDate>2003-11-26T22:00:00.0Z</domain:crDate>
S: <domain:exDate>2005-11-26T22:00:00.0Z</domain:exDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="addPeriod"/>
S: </rgp:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
<span class="grey">Hollenbeck Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
S: </response>
S:</epp>
Example <info> response for "redemptionPeriod" status:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="pendingDelete"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns1.example.net</domain:hostObj>
S: </domain:ns>
S: <domain:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:upID>ClientX</domain:upID>
S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="redemptionPeriod"/>
<span class="grey">Hollenbeck Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
S: </rgp:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
Example <info> response extension for "pendingRestore" status (note
that only the extension element changes from the first example):
S:<extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingRestore"/>
S: </rgp:infData>
S:</extension>
Example <info> response extension for "pendingDelete" status (note
that only the extension element changes from the first example):
S:<extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingDelete"/>
S: </rgp:infData>
S:</extension>
<span class="h4"><a class="selflink" id="section-4.1.3" href="#section-4.1.3">4.1.3</a>. EPP <transfer> Command</span>
This extension does not add any elements to the EPP <transfer>
command or <transfer> response described in the EPP domain mapping
[<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>].
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. EPP Transform Commands</span>
EPP provides five commands to transform objects: <create> to create
an instance of an object, <delete> to delete an instance of an
object, <renew> to extend the validity period of an object,
<transfer> to manage object sponsorship changes, and <update> to
change information associated with an object.
<span class="grey">Hollenbeck Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. EPP <create> Command</span>
This extension does not add any elements to the EPP <create> command
or <create> response described in the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>].
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. EPP <delete> Command</span>
This extension does not add any elements to the EPP <delete> command
or <delete> response described in the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>].
<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. EPP <renew> Command</span>
This extension does not add any elements to the EPP <renew> command
or <renew> response described in the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>].
<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>. EPP <transfer> Command</span>
This extension does not add any elements to the EPP <transfer>
command or <transfer> response described in the EPP domain mapping
[<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>].
<span class="h4"><a class="selflink" id="section-4.2.5" href="#section-4.2.5">4.2.5</a>. EPP <update> Command</span>
This extension defines additional elements to extend the EPP <update>
command and response described in the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>] for
redemption grace period processing.
The EPP <update> command provides a transform operation that allows a
client to change the state of a domain object. The registry grace
period extension modifies base update processing to support
redemption of domain names for which a <delete> command has been
processed, but the name has not yet been purged.
<a href="#section-3.2.5">Section 3.2.5</a> of the EPP domain mapping describes the elements that
have to be specified within an <update> command. The requirement to
provide at least one <domain:add>, <domain:rem>, or <domain:chg>
element is updated by this extension such that at least one empty
<domain:add>, <domain:rem>, or <domain:chg> element MUST be present
if this extension is specified within an <update> command. This
requirement is updated to disallow the possibility of modifying a
domain object as part of redemption grace period recovery processing.
In addition to the EPP command elements described in the EPP domain
mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>], the <update> command MUST contain an <extension>
element. The <extension> element MUST contain a child <rgp:update>
element that identifies the registry grace period namespace and the
location of the registry grace period schema. The <rgp:update>
<span class="grey">Hollenbeck Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
element contains a single <rgp:restore> element that contains an
OPTIONAL <rgp:report> element that MAY be used to deliver a
redemption grace period restore report.
The <rgp:restore> element contains a REQUIRED "op" attribute that
describes the redemption grace period operation being requested. Two
values are defined: "request" is used to identify a restore request
that does not include a restore report, and "report" is used to
identify a restore request that contains a restore report. A report
MAY be submitted more than once if corrections are required. If the
value of the "op" attribute is "request" an <rgp:report> element MUST
NOT be present. If the value of the "op" attribute is "report" an
<rgp:report> element MUST be present.
The <rgp:report> element contains the following child elements:
- An <rgp:preData> element that contains a copy of the registration
data that existed for the domain name prior to the domain name
being deleted. This element MAY contain both text and XML markup.
- An <rgp:postData> element that contains a copy of the registration
data that exists for the domain name at the time the restore
report is submitted. This element MAY contain both text and XML
markup.
- An <rgp:delTime> element that contains the date and time when the
domain name delete request was sent to the server.
- An <rgp:resTime> element that contains the date and time when the
original <rgp:restore> command was sent to the server.
- An <rgp:resReason> element that contains a brief explanation of
the reason for restoring the domain name.
- An <rgp:statement> element that contains a text statement that the
client has not restored the domain name in order to assume the
rights to use or sell the domain name for itself or for any third
party. Supporting information related to this statement MAY be
supplied in the <rgp:other> element described below. An OPTIONAL
"lang" attribute MAY be present to identify the language if
English (value "en") is not used to represent the statement.
- A second <rgp:statement> element that contains a text statement
that the information in the restore report is factual to the best
of the client's knowledge. An OPTIONAL "lang" attribute MAY be
present to identify the language if English (value "en") is not
used to represent the statement.
<span class="grey">Hollenbeck Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
- An OPTIONAL <rgp:other> element that contains any information
needed to support the statements provided by the client. This
element MAY contain both text and XML markup.
More detailed information describing the information required to be
provided in a restore report is available from ICANN.
Example <update> command without a restore report:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>example.com</domain:name>
C: <domain:chg/>
C: </domain:update>
C: </update>
C: <extension>
C: <rgp:update xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
C: rgp-1.0.xsd">
C: <rgp:restore op="request"/>
C: </rgp:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
Example <update> command with a restore report:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
<span class="grey">Hollenbeck Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
C: <domain:name>example.com</domain:name>
C: <domain:chg/>
C: </domain:update>
C: </update>
C: <extension>
C: <rgp:update xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
C: rgp-1.0.xsd">
C: <rgp:restore op="report">
C: <rgp:report>
C: <rgp:preData>Pre-delete registration data goes here.
C: Both XML and free text are allowed.</rgp:preData>
C: <rgp:postData>Post-restore registration data goes here.
C: Both XML and free text are allowed.</rgp:postData>
C: <rgp:delTime>2003-07-10T22:00:00.0Z</rgp:delTime>
C: <rgp:resTime>2003-07-20T22:00:00.0Z</rgp:resTime>
C: <rgp:resReason>Registrant error.</rgp:resReason>
C: <rgp:statement>This registrar has not restored the
C: Registered Name in order to assume the rights to use
C: or sell the Registered Name for itself or for any
C: third party.</rgp:statement>
C: <rgp:statement>The information in this report is
C: true to best of this registrar's knowledge, and this
C: registrar acknowledges that intentionally supplying
C: false information in this report shall constitute an
C: incurable material breach of the
C: Registry-Registrar Agreement.</rgp:statement>
C: <rgp:other>Supporting information goes
C: here.</rgp:other>
C: </rgp:report>
C: </rgp:restore>
C: </rgp:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When an extended <update> command without a restore report has been
processed successfully, the EPP response is as described in the EPP
domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>] except that an extension element is added to
describe grace period status as a result of processing the <update>
command. The extension element contains a single child element
(<upData>) that itself contains a single child element (<rgpStatus>)
that contains a single attribute "s" whose value MUST be
"pendingRestore" if the <restore> request has been accepted.
<span class="grey">Hollenbeck Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
Example "restore request" <update> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <extension>
S: <rgp:upData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingRestore"/>
S: </rgp:upData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
When an extended <update> command with a restore report has been
processed successfully, the EPP response is as described in the EPP
domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>] with no registry grace period extension. Registry
grace period extension is not required because acceptance of the
restore report completes redemption grace period processing.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Formal Syntax</span>
An EPP object mapping is specified in XML Schema notation. 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.
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<span class="grey">Hollenbeck Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for registry grace period
processing.
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="update" type="rgp:updateType"/>
<!--
Child elements of the <update> command for the
redemption grace period.
-->
<complexType name="updateType">
<sequence>
<element name="restore" type="rgp:restoreType"/>
</sequence>
</complexType>
<complexType name="restoreType">
<sequence>
<element name="report" type="rgp:reportType"
minOccurs="0"/>
</sequence>
<attribute name="op" type="rgp:rgpOpType" use="required"/>
</complexType>
<!--
New redemption grace period operations can be defined
by adding to this enumeration.
-->
<simpleType name="rgpOpType">
<restriction base="token">
<enumeration value="request"/>
<enumeration value="report"/>
</restriction>
</simpleType>
<complexType name="reportType">
<sequence>
<element name="preData" type="rgp:mixedType"/>
<element name="postData" type="rgp:mixedType"/>
<element name="delTime" type="dateTime"/>
<element name="resTime" type="dateTime"/>
<span class="grey">Hollenbeck Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
<element name="resReason" type="rgp:reportTextType"/>
<element name="statement" type="rgp:reportTextType"
maxOccurs="2"/>
<element name="other" type="rgp:mixedType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="mixedType">
<complexContent mixed="true">
<restriction base="anyType">
<sequence>
<any processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</restriction>
</complexContent>
</complexType>
<complexType name="reportTextType">
<complexContent mixed="true">
<restriction base="anyType">
<sequence>
<any processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="lang" type="language" default="en"/>
</restriction>
</complexContent>
</complexType>
<!--
Child response elements.
-->
<element name="infData" type="rgp:respDataType"/>
<element name="upData" type="rgp:respDataType"/>
<!--
Response elements.
-->
<complexType name="respDataType">
<sequence>
<element name="rgpStatus" type="rgp:statusType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
<span class="grey">Hollenbeck Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
Status is a combination of attributes and an optional
human-readable message that may be expressed in languages
other than English.
-->
<complexType name="statusType">
<simpleContent>
<extension base="normalizedString">
<attribute name="s" type="rgp:statusValueType"
use="required"/>
<attribute name="lang" type="language" default="en"/>
</extension>
</simpleContent>
</complexType>
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="addPeriod"/>
<enumeration value="autoRenewPeriod"/>
<enumeration value="renewPeriod"/>
<enumeration value="transferPeriod"/>
<enumeration value="pendingDelete"/>
<enumeration value="pendingRestore"/>
<enumeration value="redemptionPeriod"/>
</restriction>
</simpleType>
<!--
End of schema.
-->
</schema>
END
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Internationalization Considerations</span>
EPP is represented in XML, which provides native support for encoding
information using the Unicode character set and its more compact
representations including UTF-8 [<a href="#ref-10" title=""UTF-8, a transformation format of ISO 10646"">10</a>]. Conformant XML processors
recognize both UTF-8 and UTF-16 [<a href="#ref-11" title=""UTF-16, an encoding of ISO 10646"">11</a>]. Though XML includes provisions
to identify and use other character encodings through use of an
"encoding" attribute in an <?xml?> declaration, use of UTF-8 is
RECOMMENDED in environments where parser encoding support
incompatibility exists.
As an extension of the EPP domain mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>], the elements, element
content, attributes, and attribute values described in this document
MUST inherit the internationalization conventions used to represent
higher-layer domain and core protocol structures present in an XML
instance that includes this extension.
<span class="grey">Hollenbeck Standards Track [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in <a href="./rfc3688">RFC 3688</a> [<a href="#ref-8" title=""The IETF XML Registry"">8</a>]. Two
URI assignments were requested and have been registered by the IANA.
Registration request for the registry grace period namespace:
URI: urn:ietf:params:xml:ns:rgp-1.0
Registrant Contact: See the "Author's Address" section of this
document.
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the registry grace period XML schema:
URI: urn:ietf:params:xml:schema:rgp-1.0
Registrant Contact: See the "Author's Address" section of this
document.
XML: See the "Formal Syntax" section of this document.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
The mapping extensions described in this document do not provide any
security services beyond those described by EPP [<a href="#ref-1" title=""Extensible Provisioning Protocol (EPP)"">1</a>], the EPP domain
name mapping [<a href="#ref-2" title=""Extensible Provisioning Protocol (EPP) Domain Name Mapping"">2</a>], and protocol layers used by EPP. The security
considerations described in these other specifications apply to this
specification as well.
As with other domain object updates, redemption of a deleted domain
object MUST be restricted to the sponsoring client as authenticated
using the mechanisms described in sections <a href="#section-2.9.1.1">2.9.1.1</a> and <a href="#section-7">7</a> of <a href="./rfc3730">RFC 3730</a>
[<a href="#ref-1" title=""Extensible Provisioning Protocol (EPP)"">1</a>]. Any attempt to recover a deleted domain object by any client
other than the sponsoring client MUST be rejected with an appropriate
EPP authorization error.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
The author would like to thank the following people who have provided
significant contributions to the development of this document:
James Gould, Antony Perkov, and Janusz Sienkiewicz.
<span class="grey">Hollenbeck Standards Track [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", <a href="./rfc3730">RFC</a>
<a href="./rfc3730">3730</a>, March 2004.
[<a id="ref-2">2</a>] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain
Name Mapping", <a href="./rfc3731">RFC 3731</a>, March 2004.
[<a id="ref-3">3</a>] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler,
"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml,
October 2000, <<a href="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</a>>.
[<a id="ref-4">4</a>] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML
Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001,
<<a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>>.
[<a id="ref-5">5</a>] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes", W3C
REC-xmlschema-2, May 2001, <<a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>>.
[<a id="ref-6">6</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>, March 1997.
[<a id="ref-7">7</a>] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", <a href="./rfc3339">RFC 3339</a>, July 2002.
[<a id="ref-8">8</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>, January
2004.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-9">9</a>] Harrenstien, K., Stahl, M., and E. Feinler, "NICNAME/WHOIS", <a href="./rfc954">RFC</a>
<a href="./rfc954">954</a>, October 1985.
[<a id="ref-10">10</a>] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD
63, <a href="./rfc3629">RFC 3629</a>, November 2003.
[<a id="ref-11">11</a>] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646",
<a href="./rfc2781">RFC 2781</a>, February 2000.
<span class="grey">Hollenbeck Standards Track [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
Author's Address
Scott Hollenbeck
VeriSign, Inc.
21345 Ridgetop Circle
Dulles, VA 20166-6503
US
EMail: shollenbeck@verisign.com
<span class="grey">Hollenbeck Standards Track [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc3915">RFC 3915</a> EPP Grace Period Mapping September 2004</span>
Full Copyright Statement
Copyright (C) The Internet Society (2004).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can
be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Hollenbeck Standards Track [Page 23]
</pre>
|
