1 Internet Engineering Task Force (IETF) J. Gould
2 Request for Comments: 8334 VeriSign, Inc.
3 Category: Standards Track W. Tan
4 ISSN: 2070-1721 Cloud Registry
5 G. Brown
6 CentralNic Ltd
7 March 2018
8
9
10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
11
12 Abstract
13
14 This document describes an Extensible Provisioning Protocol (EPP)
15 extension mapping for the provisioning and management of domain name
16 registrations and applications during the launch of a domain name
17 registry.
18
19 Status of This Memo
20
21 This is an Internet Standards Track document.
22
23 This document is a product of the Internet Engineering Task Force
24 (IETF). It represents the consensus of the IETF community. It has
25 received public review and has been approved for publication by the
26 Internet Engineering Steering Group (IESG). Further information on
27 Internet Standards is available in Section 2 of RFC 7841.
28
29 Information about the current status of this document, any errata,
30 and how to provide feedback on it may be obtained at
31 https://www.rfc-editor.org/info/rfc8334.
32
33 Copyright Notice
34
35 Copyright (c) 2018 IETF Trust and the persons identified as the
36 document authors. All rights reserved.
37
38 This document is subject to BCP 78 and the IETF Trust's Legal
39 Provisions Relating to IETF Documents
40 (https://trustee.ietf.org/license-info) in effect on the date of
41 publication of this document. Please review these documents
42 carefully, as they describe your rights and restrictions with respect
43 to this document. Code Components extracted from this document must
44 include Simplified BSD License text as described in Section 4.e of
45 the Trust Legal Provisions and are provided without warranty as
46 described in the Simplified BSD License.
47
48
49
50
51
52 Gould, et al. Standards Track [Page 1]
53 RFC 8334 Launch Phase Mapping for EPP March 2018
54
55
56 Table of Contents
57
58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
59 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
60 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
61 2.1. Application Identifier . . . . . . . . . . . . . . . . . 4
62 2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5
63 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 5
64 2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 6
65 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9
66 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 11
67 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 12
68 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 14
69 2.6.1. <launch:codeMark> Element . . . . . . . . . . . . . . 15
70 2.6.2. <mark:mark> Element . . . . . . . . . . . . . . . . . 16
71 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16
72 2.6.3.1. <smd:signedMark> Element . . . . . . . . . . . . 16
73 2.6.3.2. <smd:encodedSignedMark> Element . . . . . . . . . 16
74 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 17
75 3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 17
76 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 17
77 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 22
78 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 23
79 3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 26
80 3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 30
81 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 30
82 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 36
83 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 39
84 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 40
85 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 42
86 3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 43
87 3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 44
88 3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 46
89 3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 46
90 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46
91 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 46
92 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
93 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 54
94 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 55
95 6. Security Considerations . . . . . . . . . . . . . . . . . . . 55
96 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 56
97 7.1. Normative References . . . . . . . . . . . . . . . . . . 56
98 7.2. Informative References . . . . . . . . . . . . . . . . . 57
99 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 57
100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58
101
102
103
104
105
106
107 Gould, et al. Standards Track [Page 2]
108 RFC 8334 Launch Phase Mapping for EPP March 2018
109
110
111 1. Introduction
112
113 This document describes an extension mapping for version 1.0 of the
114 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping
115 specifies a flexible schema that can be used to implement several
116 common use cases related to the provisioning and management of domain
117 name registrations and applications during the launch of a domain
118 name registry.
119
120 It is typical for domain registries to operate in special modes as
121 they begin operation to facilitate allocation of domain names, often
122 according to special rules. This document uses the term "launch
123 phase" and the shorter form "launch" to refer to such a period.
124 Multiple launch phases and multiple models are supported to enable
125 the launch of a domain name registry. Server policy determines what
126 is supported and validated. Communication of the server policy is
127 typically performed using an out-of-band mechanism that is not
128 specified in this document.
129
130 The EPP domain name mapping [RFC5731] is designed for the steady-
131 state operation of a registry. During a launch period, the model in
132 place may be different from what is defined in the EPP domain name
133 mapping [RFC5731]. For example, registries often accept multiple
134 applications for the same domain name during the "sunrise" launch
135 phase, referred to as a Launch Application. A Launch Registration
136 refers to a registration made during a launch phase when the server
137 uses a "first-come, first-served" model. Even in a "first-come,
138 first-served" model, additional steps and information might be
139 required, such as trademark information. In addition, RFC 7848
140 [RFC7848] defines a registry interface for the Trademark Claims or
141 "claims" launch phase that includes support for presenting a
142 Trademark Claims Notice to the registrant. This document proposes an
143 extension to the domain name mapping in order to provide a uniform
144 interface for the management of Launch Applications and Launch
145 Registrations in launch phases.
146
147 1.1. Conventions Used in This Document
148
149 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
150 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
151 "OPTIONAL" in this document are to be interpreted as described in
152 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
153 capitals, as shown here.
154
155 XML [W3C.REC-xml11-20060816] is case sensitive. Unless stated
156 otherwise, XML specifications and examples provided in this document
157 MUST be interpreted in the character case presented in order to
158 develop a conforming implementation.
159
160
161
162 Gould, et al. Standards Track [Page 3]
163 RFC 8334 Launch Phase Mapping for EPP March 2018
164
165
166 In examples, "C:" represents lines sent by a protocol client and "S:"
167 represents lines returned by a protocol server. Indentation and
168 whitespace in examples are provided only to illustrate element
169 relationships and are not a REQUIRED feature of this protocol. The
170 use of "..." is used as shorthand for elements defined outside this
171 document.
172
173 A Launch Registration is a domain name registration during a launch
174 phase when the server uses a "first-come, first-served" model. Only
175 a single registration for a domain name can exist in the server at a
176 time.
177
178 A Launch Application represents the intent to register a domain name
179 during a launch phase when the server accepts multiple applications
180 for a domain name, and the server later selects one of the
181 applications to allocate as a registration. Many Launch Applications
182 for a domain name can exist in the server at a time.
183
184 The XML namespace prefix "launch" is used for the namespace
185 "urn:ietf:params:xml:ns:launch-1.0", but implementations MUST NOT
186 depend on it and instead employ a proper namespace-aware XML parser
187 and serializer to interpret and output the XML documents.
188
189 The XML namespace prefix "smd" is used for the namespace
190 "urn:ietf:params:xml:ns:signedMark-1.0" [RFC7848], but
191 implementations MUST NOT depend on it and instead employ a proper
192 namespace-aware XML parser and serializer to interpret and output the
193 XML documents.
194
195 The XML namespace prefix "mark" is used for the namespace
196 "urn:ietf:params:xml:ns:mark-1.0" [RFC7848], but implementations MUST
197 NOT depend on it and instead employ a proper namespace-aware XML
198 parser and serializer to interpret and output the XML documents.
199
200 2. Object Attributes
201
202 This extension adds additional elements to the EPP domain name
203 mapping [RFC5731]. Only those new elements are described here.
204
205 2.1. Application Identifier
206
207 Servers MAY allow multiple applications, referred to as a Launch
208 Application, of the same domain name during its launch phase
209 operations. Upon receiving a valid <domain:create> command to create
210 a Launch Application, the server MUST create an application object
211 corresponding to the request, assign an application identifier for
212 the Launch Application, set the pendingCreate status [RFC5731], and
213 return the application identifier to the client with the
214
215
216
217 Gould, et al. Standards Track [Page 4]
218 RFC 8334 Launch Phase Mapping for EPP March 2018
219
220
221 <launch:applicationID> element. In order to facilitate correlation,
222 all subsequent launch operations on the Launch Application MUST be
223 qualified by the previously assigned application identifier using the
224 <launch:applicationID> element.
225
226 2.2. Validator Identifier
227
228 The Validator Identifier is unique to the server and is the
229 identifier for a Trademark Validator, which validates marks and has a
230 repository of validated marks. The OPTIONAL "validatorID" attribute
231 is used to define the Validator Identifier of the Trademark
232 Validator. Registries MAY support more than one third-party
233 Trademark Validator. The unique set of Validator Identifier values
234 supported by the server is up to server policy. The Internet
235 Corporation for Assigned Names and Numbers (ICANN) Trademark
236 Clearinghouse (TMCH) is the default Trademark Validator and is
237 reserved for the Validator Identifier of "tmch". If the ICANN TMCH
238 is not used or multiple Trademark Validators are used, the Validator
239 Identifier MUST be defined using the "validatorID" attribute.
240
241 The Validator Identifier MAY be related to one or more issuer
242 identifiers of the <mark:id> and <smd:id> elements defined in
243 [RFC7848]. Both the Validator Identifier and the Issuer Identifier
244 used MUST be unique in the server. If the ICANN TMCH is not used or
245 multiple Trademark Validators are used, the server MUST define the
246 list of supported validator identifiers and MUST make this
247 information available to clients using a mutually acceptable, out-of-
248 band mechanism.
249
250 The Validator Identifier may define a non-Trademark Validator that
251 supports a form of claims, where claims and a Validator Identifier
252 can be used for purposes beyond trademarks.
253
254 2.3. Launch Phases
255
256 The server MAY support multiple launch phases sequentially or
257 simultaneously. The <launch:phase> element MUST be included by the
258 client to define the target launch phase of the command. The server
259 SHOULD validate the phase and MAY validate the sub-phase of the
260 <launch:phase> element against the active phase and OPTIONAL sub-
261 phase of the server, and return an EPP error result code of 2306
262 [RFC5730] if there is a mismatch.
263
264 The following launch phase values are defined:
265
266 sunrise: The phase during which trademark holders can submit
267 registrations or applications with trademark information that can
268 be validated by the server.
269
270
271
272 Gould, et al. Standards Track [Page 5]
273 RFC 8334 Launch Phase Mapping for EPP March 2018
274
275
276 landrush: A post-"sunrise" launch phase when non-trademark holders
277 are allowed to register domain names with steps taken to address a
278 large volume of initial registrations.
279
280 claims: The phase, as defined in Section 2.3.1, in which a claims
281 notice must be displayed to a prospective registrant of a domain
282 name that matches trademarks.
283
284 open: A phase that is also referred to as "steady state". Servers
285 may require additional trademark protection during this phase.
286
287 custom: A custom server launch phase that is defined using the
288 "name" attribute.
289
290 For extensibility, the <launch:phase> element includes an OPTIONAL
291 "name" attribute that can define a sub-phase or the full name of the
292 phase when the <launch:phase> element has the "custom" value. For
293 example, the "claims" launch phase could have two sub-phases that
294 include "landrush" and "open".
295
296 Launch phases MAY overlap to support the "claims" launch phase,
297 defined in Section 2.3.1, and to support a traditional "landrush"
298 launch phase. The overlap of the "claims" and "landrush" launch
299 phases SHOULD be handled by setting "claims" as the <launch:phase>
300 value and setting "landrush" as the sub-phase with the "name"
301 attribute. For example, the <launch:phase> element should be
302 <launch:phase name="landrush">claims</launch:phase>.
303
304 2.3.1. Trademark Claims Phase
305
306 The Trademark Claims Phase is when a claims notice must be displayed
307 to a prospective registrant of a domain name that matches trademarks.
308 See [ICANN-TMCH] for additional details of trademark claims handling.
309 The source of the trademarks is a Trademark Validator, and the source
310 of the claims notice information is a Claims Notice Information
311 Service (CNIS), which may be directly linked to a Trademark
312 Validator. The client interfaces with 1) the server to determine if
313 a trademark exists for a domain name, 2) a CNIS to get the claims
314 notice information, and 3) the server to pass the claims notice
315 acceptance information in a create command. This document supports
316 the Trademark Claims Phase in two ways, including:
317
318 Claims Check Form: Is defined in Section 3.1.1 and is used to
319 determine whether or not there are any matching trademarks for a
320 domain name. If there is at least one matching trademark that
321 exists for the domain name, a claims key is returned. The mapping
322 of domain names and the claims keys is based on an out-of-band
323 interface between the server and the Trademark Validator. The
324
325
326
327 Gould, et al. Standards Track [Page 6]
328 RFC 8334 Launch Phase Mapping for EPP March 2018
329
330
331 CNIS associated with the claims key Validator Identifier
332 (Section 2.2) MUST accept the claims key as the basis for
333 retrieving the claims information.
334
335 Claims Create Form: Is defined in Section 3.3.2 and is used to pass
336 the claims notice acceptance information in a create command. The
337 notice identifier (<launch:noticeID>) format, validation rules,
338 and server processing is up to the interface between the server
339 and the Trademark Validator. The CNIS associated with the
340 Validator Identifier (Section 2.2) MUST generate a notice
341 identifier compliant with the <launch:noticeID> element.
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 Gould, et al. Standards Track [Page 7]
383 RFC 8334 Launch Phase Mapping for EPP March 2018
384
385
386 The following shows the Trademark Claims Phase registration flow:
387
388 .------------. .--------. .--------. .------.
389 | Registrant | | Client | | Server | | CNIS |
390 '------------' '--------' '--------' '------'
391 | Request Domain | | |
392 | Registration | | |
393 |--------------->| Domain Check | |
394 | |--------------------------->| |
395 | Domain | Domain Unavailable .------------. |
396 | Unavailable |<---------------------( Available? ) |
397 |<---------------| No '------------' |
398 | | Domain Available | Yes |
399 | |<---------------------------| |
400 | | Domain Claims Check | |
401 | |--------------------------->| |
402 | | .---------. |
403 | | Claims Don't Exist / Does \ |
404 | |<--------------------( Domain have ) |
405 | | No \ Claims? / |
406 | | '---------' |
407 | | Domain Create | | Yes |
408 | |--------------------------->| | |
409 | Domain | Domain Registered | | |
410 | Registered |<---------------------------| | |
411 |<---------------| | |
412 | | |
413 | | Claims Exist with Claims Keys | |
414 | |<------------------------------' |
415 | | |
416 .-----. | | Request Claims Info with Claims Key |
417 |Abort| | Display |-------------------------------------->|
418 '-----' | Claims | Return Claims Info |
419 ^ | Notice |<--------------------------------------|
420 | No |<---------------| |
421 | .------. Yes | |
422 '-( Ack? )----------->| Domain Claims Create Form | |
423 '------' |--------------------------->| |
424 | Registration | Error .----------------------. |
425 | Error |<-----------( Validation Successful? ) |
426 |<---------------| No '----------------------' |
427 | | | Yes |
428 | Domain | Domain Registered | |
429 | Registered |<---------------------------| |
430 |<---------------| | |
431
432 Figure 1
433
434
435
436
437 Gould, et al. Standards Track [Page 8]
438 RFC 8334 Launch Phase Mapping for EPP March 2018
439
440
441 2.4. Status Values
442
443 A Launch Application or Launch Registration object MAY have a launch
444 status value. The <launch:status> element is used to convey the
445 launch status pertaining to the object, beyond what is specified in
446 the object mapping. A Launch Application or Launch Registration MUST
447 set the "pendingCreate" status [RFC5731] if a launch status is
448 supported and is not one of the final statuses ("allocated" and
449 "rejected").
450
451 The following status values are defined using the required "s"
452 attribute:
453
454 pendingValidation: The initial state of a newly created application
455 or registration object. The application or registration requires
456 validation, but the validation process has not yet completed.
457
458 validated: The application or registration meets relevant registry
459 rules.
460
461 invalid: The application or registration does not validate according
462 to registry rules. Server policies permitting, it may transition
463 back into "pendingValidation" for revalidation, after
464 modifications are made to ostensibly correct attributes that
465 caused the validation failure.
466
467 pendingAllocation: The allocation of the application or registration
468 is pending based on the results of some out-of-band process (for
469 example, an auction).
470
471 allocated: The object corresponding to the application or
472 registration has been provisioned. This is a possible end state
473 of an application or registration object.
474
475 rejected: The application or registration object was not
476 provisioned. This is a possible end state of an application or
477 registration object.
478
479 custom: A custom status that is defined using the "name" attribute.
480
481 Each status value MAY be accompanied by a string of human-readable
482 text that describes the rationale for the status applied to the
483 object. The OPTIONAL "lang" attribute, as defined in [RFC5646], MAY
484 be present to identify the language if the negotiated value is
485 something other than the default value of "en" (English).
486
487
488
489
490
491
492 Gould, et al. Standards Track [Page 9]
493 RFC 8334 Launch Phase Mapping for EPP March 2018
494
495
496 For extensibility, the <launch:status> element includes an OPTIONAL
497 "name" attribute that can define a sub-status or the full name of the
498 status when the status value is "custom". The server SHOULD use one
499 of the non-"custom" status values.
500
501 Status values MAY be skipped. For example, an application or
502 registration MAY immediately start at the "allocated" status, or an
503 application or registration MAY skip the "pendingAllocation" status.
504 If the launch phase does not require validation of a request, an
505 application or registration MAY immediately skip to
506 "pendingAllocation".
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 Gould, et al. Standards Track [Page 10]
548 RFC 8334 Launch Phase Mapping for EPP March 2018
549
550
551 2.4.1. State Transition
552
553 The transitions between the states is a matter of server policy.
554 This diagram defines one possible set of permitted transitions.
555
556 | request
557 |
558 | +--------------------------+
559 | | |
560 v v |
561 +-------------------+ |
562 | | |
563 | pendingValidation +--------------+ |
564 | | | |
565 +---------+---------+ | |
566 | | |
567 | | |
568 v v |
569 +-----------+ +---------+ |
570 | | | | |
571 | validated | | invalid +--+
572 | | | |
573 +-----+-----+ +----+----+
574 | |
575 | |
576 v |
577 +-------------------+ |
578 | | |
579 | pendingAllocation +-----------+ |
580 | | | |
581 +---------+---------+ | |
582 | | |
583 | | |
584 | | |
585 | | |
586 | | |
587 v v v
588 +---------+ +--------+
589 / \ / \
590 | allocated | | rejected |
591 \ / \ /
592 +---------+ +--------+
593
594
595 Figure 2
596
597
598
599
600
601
602 Gould, et al. Standards Track [Page 11]
603 RFC 8334 Launch Phase Mapping for EPP March 2018
604
605
606 2.5. Poll Messaging
607
608 A Launch Application MUST be handled as an EPP domain name object as
609 specified in RFC 5731 [RFC5731], with the "pendingCreate" status and
610 launch status values defined in Section 2.4. A Launch Registration
611 MAY be handled as an EPP domain name object as specified in RFC 5731
612 [RFC5731], with the "pendingCreate" status and launch status values
613 defined in Section 2.4. As a Launch Application or Launch
614 Registration transitions between the status values defined in
615 Section 2.4, the server SHOULD insert poll messages, per [RFC5730],
616 for the applicable intermediate statuses, including the
617 "pendingValidation", "validated", "pendingAllocation", and "invalid"
618 statuses, using the <domain:infData> element with the
619 <launch:infData> extension. The <domain:infData> element MAY contain
620 non-mandatory information, like contact and name server information.
621 Also, further extensions that would normally be included in the
622 response of a <domain:info> command, per [RFC5731], MAY be included.
623 For the final statuses, including the "allocated" and "rejected"
624 statuses, the server MUST insert a <domain:panData> poll message, per
625 [RFC5731], with the <launch:infData> extension.
626
627 The following is an example poll message for a Launch Application
628 that has transitioned to the "pendingAllocation" state.
629
630 S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
631 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
632 S: <response>
633 S: <result code="1301">
634 S: <msg>Command completed successfully; ack to dequeue</msg>
635 S: </result>
636 S: <msgQ count="5" id="12345">
637 S: <qDate>2013-04-04T22:01:00.0Z</qDate>
638 S: <msg>Application pendingAllocation.</msg>
639 S: </msgQ>
640 S: <resData>
641 S: <domain:infData
642 S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
643 S: <domain:name>domain.example</domain:name>
644 S: ...
645 S: </domain:infData>
646 S: </resData>
647 S: <extension>
648 S: <launch:infData
649 S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
650 S: <launch:phase>sunrise</launch:phase>
651 S: <launch:applicationID>abc123</launch:applicationID>
652 S: <launch:status s="pendingAllocation"/>
653 S: </launch:infData>
654
655
656
657 Gould, et al. Standards Track [Page 12]
658 RFC 8334 Launch Phase Mapping for EPP March 2018
659
660
661 S: </extension>
662 S: <trID>
663 S: <clTRID>ABC-12345</clTRID>
664 S: <svTRID>54322-XYZ</svTRID>
665 S: </trID>
666 S: </response>
667 S:</epp>
668
669 The following is an example <domain:panData> poll message for an
670 "allocated" Launch Application.
671
672 S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
673 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
674 S: <response>
675 S: <result code="1301">
676 S: <msg>Command completed successfully; ack to dequeue</msg>
677 S: </result>
678 S: <msgQ count="5" id="12345">
679 S: <qDate>2013-04-04T22:01:00.0Z</qDate>
680 S: <msg>Application successfully allocated.</msg>
681 S: </msgQ>
682 S: <resData>
683 S: <domain:panData
684 S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
685 S: <domain:name paResult="1">domain.example</domain:name>
686 S: <domain:paTRID>
687 S: <clTRID>ABC-12345</clTRID>
688 S: <svTRID>54321-XYZ</svTRID>
689 S: </domain:paTRID>
690 S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
691 S: </domain:panData>
692 S: </resData>
693 S: <extension>
694 S: <launch:infData
695 S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
696 S: <launch:phase>sunrise</launch:phase>
697 S: <launch:applicationID>abc123</launch:applicationID>
698 S: <launch:status s="allocated"/>
699 S: </launch:infData>
700 S: </extension>
701 S: <trID>
702 S: <clTRID>BCD-23456</clTRID>
703 S: <svTRID>65432-WXY</svTRID>
704 S: </trID>
705 S: </response>
706 S:</epp>
707
708
709
710
711
712 Gould, et al. Standards Track [Page 13]
713 RFC 8334 Launch Phase Mapping for EPP March 2018
714
715
716 The following is an example <domain:panData> poll message for an
717 "allocated" Launch Registration.
718
719 S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
720 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
721 S: <response>
722 S: <result code="1301">
723 S: <msg>Command completed successfully; ack to dequeue</msg>
724 S: </result>
725 S: <msgQ count="5" id="12345">
726 S: <qDate>2013-04-04T22:01:00.0Z</qDate>
727 S: <msg>Registration successfully allocated.</msg>
728 S: </msgQ>
729 S: <resData>
730 S: <domain:panData
731 S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
732 S: <domain:name paResult="1">domain.example</domain:name>
733 S: <domain:paTRID>
734 S: <clTRID>ABC-12345</clTRID>
735 S: <svTRID>54321-XYZ</svTRID>
736 S: </domain:paTRID>
737 S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
738 S: </domain:panData>
739 S: </resData>
740 S: <extension>
741 S: <launch:infData
742 S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
743 S: <launch:phase>sunrise</launch:phase>
744 S: <launch:status s="allocated"/>
745 S: </launch:infData>
746 S: </extension>
747 S: <trID>
748 S: <clTRID>BCD-23456</clTRID>
749 S: <svTRID>65432-WXY</svTRID>
750 S: </trID>
751 S: </response>
752 S:</epp>
753
754 2.6. Mark Validation Models
755
756 A server MUST support at least one of the following models for
757 validating trademark information:
758
759 code: Use of a mark code by itself to validate that the mark matches
760 the domain name. This model is supported using the
761 <launch:codeMark> element with just the <launch:code> element.
762
763
764
765
766
767 Gould, et al. Standards Track [Page 14]
768 RFC 8334 Launch Phase Mapping for EPP March 2018
769
770
771 mark: The mark information is passed without any other validation
772 element. The server will use some custom form of validation to
773 validate that the mark information is authentic. This model is
774 supported using the <launch:codeMark> element with just the
775 <mark:mark> (Section 2.6.2) element.
776
777 code with mark: A code is used along with the mark information by
778 the server to validate the mark utilizing an external party. The
779 code represents some form of secret that matches the mark
780 information passed. This model is supported using the
781 <launch:codeMark> element that contains both the <launch:code> and
782 the <mark:mark> (Section 2.6.2) elements.
783
784 signed mark: The mark information is digitally signed as described
785 in the Digital Signature section (Section 2.6.3). The digital
786 signature can be directly validated by the server using the public
787 key of the external party that created the signed mark using its
788 private key. This model is supported using the <smd:signedMark>
789 (Section 2.6.3.1) and <smd:encodedSignedMark> (Section 2.6.3.2)
790 elements.
791
792 More than one <launch:codeMark>, <smd:signedMark> (Section 2.6.3.1),
793 or <smd:encodedSignedMark> (Section 2.6.3.2) element MAY be
794 specified. The maximum number of marks per domain name is up to
795 server policy.
796
797 2.6.1. <launch:codeMark> Element
798
799 The <launch:codeMark> element is used by the "code", "mark", and
800 "code with mark" validation models and has the following child
801 elements:
802
803 <launch:code>: OPTIONAL mark code used to validate the <mark:mark>
804 (Section 2.6.2) information. The mark code is a mark-specific
805 secret that the server can verify against a third party. The
806 OPTIONAL "validatorID" attribute is the Validator Identifier
807 (Section 2.2) whose value indicates which Trademark Validator the
808 code originated from, with no default value.
809
810 <mark:mark>: OPTIONAL mark information with child elements defined
811 in the Mark section (Section 2.6.2).
812
813
814
815
816
817
818
819
820
821
822 Gould, et al. Standards Track [Page 15]
823 RFC 8334 Launch Phase Mapping for EPP March 2018
824
825
826 The following is an example <launch:codeMark> element with both a
827 <launch:code> and <mark:mark> (Section 2.6.2) element.
828
829 <launch:codeMark>
830 <launch:code validatorID="sample">
831 49FD46E6C4B45C55D4AC</launch:code>
832 <mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
833 ...
834 </mark:mark>
835 </launch:codeMark>
836
837 2.6.2. <mark:mark> Element
838
839 A <mark:mark> element describes an applicant's prior right to a given
840 domain name that is used with the "mark", "mark with code", and
841 "signed mark" validation models. The <mark:mark> element is defined
842 in [RFC7848]. A new mark format can be supported by creating a new
843 XML schema for the mark that has an element that substitutes for the
844 <mark:abstractMark> element from [RFC7848].
845
846 2.6.3. Digital Signature
847
848 Digital signatures MAY be used by the server to validate the mark
849 information, when using the "signed mark" validation model with the
850 <smd:signedMark> (Section 2.6.3.1) and <smd:encodedSignedMark>
851 (Section 2.6.3.2) elements. When using digital signatures, the
852 server MUST validate the digital signature.
853
854 2.6.3.1. <smd:signedMark> Element
855
856 The <smd:signedMark> element contains the digitally signed mark
857 information. The <smd:signedMark> element is defined in [RFC7848].
858 A new signed mark format can be supported by creating a new XML
859 schema for the signed mark that has an element that substitutes for
860 the <smd:abstractSignedMark> element from [RFC7848].
861
862 2.6.3.2. <smd:encodedSignedMark> Element
863
864 The <smd:encodedSignedMark> element contains an encoded form of the
865 digitally signed <smd:signedMark> (Section 2.6.3.1) element. The
866 <smd:encodedSignedMark> element is defined in [RFC7848]. A new
867 encoded signed mark format can be supported by creating a new XML
868 schema for the encoded signed mark that has an element that
869 substitutes for the <smd:encodedSignedMark> element from [RFC7848].
870
871
872
873
874
875
876
877 Gould, et al. Standards Track [Page 16]
878 RFC 8334 Launch Phase Mapping for EPP March 2018
879
880
881 3. EPP Command Mapping
882
883 A detailed description of the EPP syntax and semantics can be found
884 in the EPP core protocol specification [RFC5730]. The command
885 mappings described here are specifically for use in the Launch Phase
886 Extension.
887
888 This mapping is designed to be flexible, requiring only a minimum set
889 of required elements.
890
891 While it is meant to serve several use cases, it does not prescribe
892 any interpretation by the client or server. Such processing is
893 typically highly policy dependent and therefore specific to
894 implementations.
895
896 Operations on application objects are done via one or more of the
897 existing EPP commands defined in the EPP domain name mapping
898 [RFC5731]. Registries MAY choose to support a subset of the
899 operations.
900
901 3.1. EPP <check> Command
902
903 There are three forms of the extension to the EPP <check> command:
904 the Claims Check Form (Section 3.1.1), the Availability Check Form
905 (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The
906 <launch:check> element "type" attribute defines the form, with the
907 value of "claims" for the Claims Check Form (Section 3.1.1), "avail"
908 for the Availability Check Form (Section 3.1.2), and "trademark" for
909 the Trademark Check Form (Section 3.1.3). The default value of the
910 "type" attribute is "claims". The forms supported by the server is
911 determined by server policy. The server MUST return an EPP error
912 result code of 2307 [RFC5730] if it receives a check form that is not
913 supported.
914
915 3.1.1. Claims Check Form
916
917 The Claims Check Form defines a new command called the Claims Check
918 Command that is used to determine whether or not there are any
919 matching trademarks, in the specified launch phase, for each domain
920 name passed in the command, that require the use of the "Claims
921 Create Form" on a Domain Create Command. The availability check
922 information defined in the EPP domain name mapping [RFC5731] MUST NOT
923 be returned for the Claims Check Command. This form is the default
924 form and MAY be explicitly identified by setting the <launch:check>
925 "type" attribute to "claims".
926
927
928
929
930
931
932 Gould, et al. Standards Track [Page 17]
933 RFC 8334 Launch Phase Mapping for EPP March 2018
934
935
936 Instead of returning whether the domain name is available, the Claims
937 Check Command will return whether or not at least one matching
938 trademark exists for the domain name, which requires the use of the
939 "Claims Create Form" on a Domain Create Command. If there is at
940 least one matching trademark that exists for the domain name, a
941 <launch:claimKey> element is returned. The client MAY then use the
942 value of the <launch:claimKey> element to obtain information needed
943 to generate the Trademark Claims Notice from the Trademark Validator
944 based on the Validator Identifier (Section 2.2). The unique notice
945 identifier of the Trademark Claims Notice MUST be passed in the
946 <launch:noticeID> element of the extension to the Create Command
947 (Section 3.3).
948
949 The <domain:name> elements in the EPP <check> command of EPP domain
950 name mapping [RFC5731] define the domain names to check for matching
951 trademarks. The <launch:check> element contains the following child
952 element:
953
954 <launch:phase>: Contains the value of the active launch phase of the
955 server. The server SHOULD validate the value according to
956 Section 2.3.
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 Gould, et al. Standards Track [Page 18]
988 RFC 8334 Launch Phase Mapping for EPP March 2018
989
990
991 The following is an example Claims Check Command using the <check>
992 domain command and the <launch:check> extension with the "type"
993 explicitly set to "claims", to determine if "domain1.example",
994 "domain2.example", and "domain3.example" require claims notices
995 during the "claims" launch phase:
996
997 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
998 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
999 C: <command>
1000 C: <check>
1001 C: <domain:check
1002 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1003 C: <domain:name>domain1.example</domain:name>
1004 C: <domain:name>domain2.example</domain:name>
1005 C: <domain:name>domain3.example</domain:name>
1006 C: </domain:check>
1007 C: </check>
1008 C: <extension>
1009 C: <launch:check
1010 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
1011 C: type="claims">
1012 C: <launch:phase>claims</launch:phase>
1013 C: </launch:check>
1014 C: </extension>
1015 C: <clTRID>ABC-12345</clTRID>
1016 C: </command>
1017 C:</epp>
1018
1019 If the <check> command has been processed successfully, the EPP
1020 <response> MUST contain an <extension> <launch:chkData> element that
1021 identifies the launch namespace. The <launch:chkData> element
1022 contains the following child elements:
1023
1024 <launch:phase>: The phase that mirrors the <launch:phase> element
1025 included in the <launch:check>.
1026
1027 <launch:cd>: One or more <launch:cd> elements that contain the
1028 following child elements:
1029
1030 <launch:name>: Contains the fully qualified name of the queried
1031 domain name. This element MUST contain an "exists" attribute
1032 whose value indicates if a matching trademark exists for the
1033 domain name that requires the use of the "Claims Create Form"
1034 on a Domain Create Command. A value of "1" (or "true") means
1035 that a matching trademark does exist and that the "Claims
1036 Create Form" is required on a Domain Create Command. A value
1037
1038
1039
1040
1041
1042 Gould, et al. Standards Track [Page 19]
1043 RFC 8334 Launch Phase Mapping for EPP March 2018
1044
1045
1046 of "0" (or "false") means that a matching trademark does not
1047 exist or that the "Claims Create Form" is NOT required on a
1048 Domain Create Command.
1049
1050 <launch:claimKey>: Zero or more OPTIONAL claim keys that MAY be
1051 passed to a third-party Trademark Validator such as the ICANN
1052 TMCH for querying the information needed to generate a
1053 Trademark Claims Notice. The <launch:claimKey> is used as
1054 the key for the query in place of the domain name to securely
1055 query the service without using a well-known value like a
1056 domain name. The OPTIONAL "validatorID" attribute is the
1057 Validator Identifier (Section 2.2) whose value indicates
1058 which Trademark Validator to query for the claims notice
1059 information, with the default being the ICANN TMCH. The
1060 "validatorID" attribute MAY reference a non-trademark claims
1061 clearinghouse identifier to support other forms of claims
1062 notices.
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 Gould, et al. Standards Track [Page 20]
1098 RFC 8334 Launch Phase Mapping for EPP March 2018
1099
1100
1101 The following is an example Claims Check response when a claims
1102 notice for the "claims" launch phase is not required for the domain
1103 name domain1.example, is required for the domain name domain2.example
1104 in the "tmch", and is required for the domain name domain3.example in
1105 the "tmch" and "custom-tmch":
1106
1107 S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1108 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1109 S: <response>
1110 S: <result code="1000">
1111 S: <msg>Command completed successfully</msg>
1112 S: </result>
1113 S: <extension>
1114 S: <launch:chkData
1115 S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1116 S: <launch:phase>claims</launch:phase>
1117 S: <launch:cd>
1118 S: <launch:name exists="0">domain1.example</launch:name>
1119 S: </launch:cd>
1120 S: <launch:cd>
1121 S: <launch:name exists="1">domain2.example</launch:name>
1122 S: <launch:claimKey validatorID="tmch">
1123 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
1124 S: </launch:claimKey>
1125 S: </launch:cd>
1126 S: <launch:cd>
1127 S: <launch:name exists="1">domain3.example</launch:name>
1128 S: <launch:claimKey validatorID="tmch">
1129 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
1130 S: </launch:claimKey>
1131 S: <launch:claimKey validatorID="custom-tmch">
1132 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
1133 S: </launch:claimKey>
1134 S: </launch:cd>
1135 S: </launch:chkData>
1136 S: </extension>
1137 S: <trID>
1138 S: <clTRID>ABC-12345</clTRID>
1139 S: <svTRID>54321-XYZ</svTRID>
1140 S: </trID>
1141 S: </response>
1142 S:</epp>
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152 Gould, et al. Standards Track [Page 21]
1153 RFC 8334 Launch Phase Mapping for EPP March 2018
1154
1155
1156 3.1.2. Availability Check Form
1157
1158 The Availability Check Form defines additional elements to extend the
1159 EPP <check> command described in the EPP domain name mapping
1160 [RFC5731]. No additional elements are defined for the EPP <check>
1161 response. This form MUST be identified by setting the <launch:check>
1162 "type" attribute to "avail".
1163
1164 The EPP <check> command is used to determine if an object can be
1165 provisioned within a repository. Domain names may be made available
1166 only in unique launch phases, whilst remaining unavailable for
1167 concurrent launch phases. In addition to the elements expressed in
1168 the <domain:check>, the command is extended with the <launch:check>
1169 element that contains the following child element:
1170
1171 <launch:phase>: The launch phase to which domain name availability
1172 should be determined. The server SHOULD validate the value and
1173 return an EPP error result code of 2306 [RFC5730] if it is
1174 invalid.
1175
1176 The following is an example Availability Check Form Command using the
1177 <check> domain command and the <launch:check> extension with the
1178 "type" set to "avail", to determine the availability of two domain
1179 names in the "idn-release" custom launch phase:
1180
1181 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1182 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1183 C: <command>
1184 C: <check>
1185 C: <domain:check
1186 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1187 C: <domain:name>domain1.example</domain:name>
1188 C: <domain:name>domain2.example</domain:name>
1189 C: </domain:check>
1190 C: </check>
1191 C: <extension>
1192 C: <launch:check
1193 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
1194 C: type="avail">
1195 C: <launch:phase name="idn-release">custom</launch:phase>
1196 C: </launch:check>
1197 C: </extension>
1198 C: <clTRID>ABC-12345</clTRID>
1199 C: </command>
1200 C:</epp>
1201
1202
1203
1204
1205
1206
1207 Gould, et al. Standards Track [Page 22]
1208 RFC 8334 Launch Phase Mapping for EPP March 2018
1209
1210
1211 The Availability Check Form does not define any extension to the
1212 response of a <check> domain command. After processing the command,
1213 the server replies with a standard EPP response as defined in the EPP
1214 domain name mapping [RFC5731].
1215
1216 3.1.3. Trademark Check Form
1217
1218 The Trademark Check Form defines a new command called the Trademark
1219 Check Command that is used to determine whether or not there are any
1220 matching trademarks for each domain name passed in the command,
1221 independent of the active launch phase of the server and whether the
1222 "Claims Create Form" is required on a Domain Create Command. The
1223 availability check information defined in the EPP domain name mapping
1224 [RFC5731] MUST NOT be returned for the Trademark Check Command. This
1225 form MUST be identified by setting the <launch:check> "type"
1226 attribute to "trademark".
1227
1228 Instead of returning whether the domain name is available, the
1229 Trademark Check Command will return whether or not at least one
1230 matching trademark exists for the domain name. If there is at least
1231 one matching trademark that exists for the domain name, a
1232 <launch:claimKey> element is returned. The client MAY then use the
1233 value of the <launch:claimKey> element to obtain Trademark Claims
1234 Notice information from the Trademark Validator based on the
1235 Validator Identifier (Section 2.2).
1236
1237 The <domain:name> elements in the EPP <check> command of EPP domain
1238 name mapping [RFC5731] define the domain names to check for matching
1239 trademarks. The <launch:check> element does not contain any child
1240 elements with the "Trademark Check Form":
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262 Gould, et al. Standards Track [Page 23]
1263 RFC 8334 Launch Phase Mapping for EPP March 2018
1264
1265
1266 The following is an example Trademark Check Command using the <check>
1267 domain command and the <launch:check> extension with the "type" set
1268 to "trademark", to determine if "domain1.example", "domain2.example",
1269 and "domain3.example" have any matching trademarks:
1270
1271 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1272 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1273 C: <command>
1274 C: <check>
1275 C: <domain:check
1276 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1277 C: <domain:name>domain1.example</domain:name>
1278 C: <domain:name>domain2.example</domain:name>
1279 C: <domain:name>domain3.example</domain:name>
1280 C: </domain:check>
1281 C: </check>
1282 C: <extension>
1283 C: <launch:check
1284 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
1285 C: type="trademark"/>
1286 C: </extension>
1287 C: <clTRID>ABC-12345</clTRID>
1288 C: </command>
1289 C:</epp>
1290
1291 If the <check> command has been processed successfully, the EPP
1292 <response> MUST contain an <extension> <launch:chkData> element that
1293 identifies the launch namespace. The <launch:chkData> element
1294 contains the following child elements:
1295
1296 <launch:cd>: One or more <launch:cd> elements that contain the
1297 following child elements:
1298
1299 <launch:name>: Contains the fully qualified name of the queried
1300 domain name. This element MUST contain an "exists" attribute
1301 whose value indicates if a matching trademark exists for the
1302 domain name. A value of "1" (or "true") means that a
1303 matching trademark does exist. A value of "0" (or "false")
1304 means that a matching trademark does not exist.
1305
1306 <launch:claimKey>: Zero or more OPTIONAL claim keys that MAY be
1307 passed to a third-party Trademark Validator such as the ICANN
1308 TMCH for querying the information needed to generate a
1309 Trademark Claims Notice. The <launch:claimKey> is used as
1310 the key for the query in place of the domain name to securely
1311 query the service without using a well-known value like a
1312 domain name. The OPTIONAL "validatorID" attribute is the
1313 Validator Identifier (Section 2.2) whose value indicates
1314
1315
1316
1317 Gould, et al. Standards Track [Page 24]
1318 RFC 8334 Launch Phase Mapping for EPP March 2018
1319
1320
1321 which Trademark Validator to query for the claims notice
1322 information, with the default being the ICANN TMCH. The
1323 "validatorID" attribute MAY reference a non-trademark claims
1324 clearinghouse identifier to support other forms of claims
1325 notices.
1326
1327 The following is an example Trademark Check response for the "claims"
1328 launch phase when no matching trademarks are found for the domain
1329 name domain1.example, matching trademarks are found for the domain
1330 name domain2.example in the "tmch", and matching trademarks are found
1331 for domain name domain3.example in the "tmch" and "custom-tmch":
1332
1333 S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1334 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1335 S: <response>
1336 S: <result code="1000">
1337 S: <msg>Command completed successfully</msg>
1338 S: </result>
1339 S: <extension>
1340 S: <launch:chkData
1341 S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1342 S: <launch:cd>
1343 S: <launch:name exists="0">domain1.example</launch:name>
1344 S: </launch:cd>
1345 S: <launch:cd>
1346 S: <launch:name exists="1">domain2.example</launch:name>
1347 S: <launch:claimKey validatorID="tmch">
1348 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
1349 S: </launch:claimKey>
1350 S: </launch:cd>
1351 S: <launch:cd>
1352 S: <launch:name exists="1">domain3.example</launch:name>
1353 S: <launch:claimKey validatorID="tmch">
1354 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
1355 S: </launch:claimKey>
1356 S: <launch:claimKey validatorID="custom-tmch">
1357 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
1358 S: </launch:claimKey>
1359 S: </launch:cd>
1360 S: </launch:chkData>
1361 S: </extension>
1362 S: <trID>
1363 S: <clTRID>ABC-12345</clTRID>
1364 S: <svTRID>54321-XYZ</svTRID>
1365 S: </trID>
1366 S: </response>
1367 S:</epp>
1368
1369
1370
1371
1372 Gould, et al. Standards Track [Page 25]
1373 RFC 8334 Launch Phase Mapping for EPP March 2018
1374
1375
1376 3.2. EPP <info> Command
1377
1378 This extension defines additional elements to extend the EPP <info>
1379 command and response to be used in conjunction with the EPP domain
1380 name mapping [RFC5731].
1381
1382 The EPP <info> command is used to retrieve information for a Launch
1383 Registration or Launch Application. The Application Identifier
1384 (Section 2.1) returned in the <launch:creData> element of the create
1385 response (Section 3.3) can be used for retrieving information for a
1386 Launch Application. A <launch:info> element is sent along with the
1387 regular <info> domain command. The <launch:info> element includes an
1388 OPTIONAL "includeMark" boolean attribute, with a default value of
1389 "false", to indicate whether or not to include the mark in the
1390 response. The <launch:info> element contains the following child
1391 elements:
1392
1393 <launch:phase>: The phase during which the application or
1394 registration was submitted or is associated with. Server policy
1395 defines the phases that are supported. The server SHOULD
1396 validate the value and return an EPP error result code of 2306
1397 [RFC5730] if it is invalid.
1398
1399 <launch:applicationID>: OPTIONAL application identifier of the
1400 Launch Application.
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427 Gould, et al. Standards Track [Page 26]
1428 RFC 8334 Launch Phase Mapping for EPP March 2018
1429
1430
1431 The following is an example <info> domain command with the
1432 <launch:info> extension to retrieve information for the sunrise
1433 application for domain.example and application identifier "abc123":
1434
1435 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1436 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1437 C: <command>
1438 C: <info>
1439 C: <domain:info
1440 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1441 C: <domain:name>domain.example</domain:name>
1442 C: </domain:info>
1443 C: </info>
1444 C: <extension>
1445 C: <launch:info
1446 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
1447 C: includeMark="true">
1448 C: <launch:phase>sunrise</launch:phase>
1449 C: <launch:applicationID>abc123</launch:applicationID>
1450 C: </launch:info>
1451 C: </extension>
1452 C: <clTRID>ABC-12345</clTRID>
1453 C: </command>
1454 C:</epp>
1455
1456 The following is an example <info> domain command with the
1457 <launch:info> extension to retrieve information for the sunrise
1458 registration for domain.example:
1459
1460 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1461 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1462 C: <command>
1463 C: <info>
1464 C: <domain:info
1465 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1466 C: <domain:name>domain.example</domain:name>
1467 C: </domain:info>
1468 C: </info>
1469 C: <extension>
1470 C: <launch:info
1471 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1472 C: <launch:phase>sunrise</launch:phase>
1473 C: </launch:info>
1474 C: </extension>
1475 C: <clTRID>ABC-12345</clTRID>
1476 C: </command>
1477 C:</epp>
1478
1479
1480
1481
1482 Gould, et al. Standards Track [Page 27]
1483 RFC 8334 Launch Phase Mapping for EPP March 2018
1484
1485
1486 If the query was successful, the server replies with a
1487 <launch:infData> element along with the regular EPP <resData>. The
1488 <launch:infData> contains the following child elements:
1489
1490 <launch:phase>: The phase during which the application was submitted
1491 or is associated with that matches the associated <info> command
1492 <launch:phase>.
1493
1494 <launch:applicationID>: OPTIONAL Application Identifier of the
1495 Launch Application.
1496
1497 <launch:status>: OPTIONAL status of the Launch Application using one
1498 of the supported status values (Section 2.4).
1499
1500 <mark:mark>: Zero or more <mark:mark> (Section 2.6.2) elements only
1501 if the "includeMark" attribute is "true" in the command.
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537 Gould, et al. Standards Track [Page 28]
1538 RFC 8334 Launch Phase Mapping for EPP March 2018
1539
1540
1541 The following is an example <info> domain response using the
1542 <launch:infData> extension with the mark information:
1543
1544 S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1545 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1546 S: <response>
1547 S: <result code="1000">
1548 S: <msg>Command completed successfully</msg>
1549 S: </result>
1550 S: <resData>
1551 S: <domain:infData
1552 S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1553 S: <domain:name>domain.example</domain:name>
1554 S: <domain:roid>EXAMPLE1-REP</domain:roid>
1555 S: <domain:status s="pendingCreate"/>
1556 S: <domain:registrant>jd1234</domain:registrant>
1557 S: <domain:contact type="admin">sh8013</domain:contact>
1558 S: <domain:contact type="tech">sh8013</domain:contact>
1559 S: <domain:clID>ClientX</domain:clID>
1560 S: <domain:crID>ClientY</domain:crID>
1561 S: <domain:crDate>2012-04-03T22:00:00.0Z</domain:crDate>
1562 S: <domain:authInfo>
1563 S: <domain:pw>2fooBAR</domain:pw>
1564 S: </domain:authInfo>
1565 S: </domain:infData>
1566 S: </resData>
1567 S: <extension>
1568 S: <launch:infData
1569 S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1570 S: <launch:phase>sunrise</launch:phase>
1571 S: <launch:applicationID>abc123</launch:applicationID>
1572 S: <launch:status s="pendingValidation"/>
1573 S: <mark:mark
1574 S: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
1575 S: ...
1576 S: </mark:mark>
1577 S: </launch:infData>
1578 S: </extension>
1579 S: <trID>
1580 S: <clTRID>ABC-12345</clTRID>
1581 S: <svTRID>54321-XYZ</svTRID>
1582 S: </trID>
1583 S: </response>
1584 S:</epp>
1585
1586
1587
1588
1589
1590
1591
1592 Gould, et al. Standards Track [Page 29]
1593 RFC 8334 Launch Phase Mapping for EPP March 2018
1594
1595
1596 3.3. EPP <create> Command
1597
1598 There are four forms of the extension to the EPP <create> command
1599 that include the Sunrise Create Form (Section 3.3.1), the Claims
1600 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3),
1601 and the Mixed Create Form (Section 3.3.4). The form used is
1602 dependent on the supported launch phases (Section 2.3) as defined
1603 below.
1604
1605 sunrise: The EPP <create> command with the "sunrise" launch phase is
1606 used to submit a registration with trademark information that can
1607 be verified by the server with the <domain:name> value. The
1608 Sunrise Create Form (Section 3.3.1) is used for the "sunrise"
1609 launch phase.
1610
1611 landrush: The EPP <create> command with the "landrush" launch phase
1612 MAY use the General Create Form (Section 3.3.3) to explicitly
1613 specify the phase and optionally define the expected type of
1614 object to create.
1615
1616 claims: The EPP <create> command with the "claims" launch phase is
1617 used to pass the information associated with the presentation and
1618 acceptance of the claims notice. The Claims Create Form
1619 (Section 3.3.2) is used, and the General Create Form
1620 (Section 3.3.3) MAY be used for the "claims" launch phase.
1621
1622 open: The EPP <create> command with the "open" launch phase is
1623 undefined, but the form supported is up to server policy. The
1624 Claims Create Form (Section 3.3.2) MAY be used to pass the
1625 information associated with the presentation and acceptance of the
1626 claims notice if required for the domain name.
1627
1628 custom: The EPP <create> command with the "custom" launch phase is
1629 undefined, but the form supported is up to server policy.
1630
1631 3.3.1. Sunrise Create Form
1632
1633 The Sunrise Create Form of the extension to the EPP domain name
1634 mapping [RFC5731] includes the verifiable trademark information that
1635 the server uses to match against the domain name to authorize the
1636 domain create. A server MUST support one of four models in Mark
1637 Validation Models (Section 2.6) to verify the trademark information
1638 passed by the client.
1639
1640 A <launch:create> element is sent along with the regular <create>
1641 domain command. The <launch:create> element has an OPTIONAL "type"
1642 attribute that defines the expected type of object ("application" or
1643 "registration") to create. The server SHOULD validate the "type"
1644
1645
1646
1647 Gould, et al. Standards Track [Page 30]
1648 RFC 8334 Launch Phase Mapping for EPP March 2018
1649
1650
1651 attribute, when passed, against the type of object that will be
1652 created, and return an EPP error result code of 2306 [RFC5730] if the
1653 type is incorrect. The <launch:create> element contains the
1654 following child elements:
1655
1656 <launch:phase>: The identifier for the launch phase. The server
1657 SHOULD validate the value according to Section 2.3.
1658
1659 <launch:codeMark> or <smd:signedMark> or <smd:encodedSignedMark>:
1660
1661 <launch:codeMark>: Zero or more <launch:codeMark> elements. The
1662 <launch:codeMark> child elements are defined in
1663 "<launch:codeMark> Element" (Section 2.6.1).
1664
1665 <smd:signedMark>: Zero or more <smd:signedMark> elements. The
1666 <smd:signedMark> child elements are defined in
1667 "<smd:signedMark> Element" (Section 2.6.3.1).
1668
1669 <smd:encodedSignedMark>: Zero or more <smd:encodedSignedMark>
1670 elements. The <smd:encodedSignedMark> child elements are
1671 defined in "<smd:encodedSignedMark> Element"
1672 (Section 2.6.3.2).
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702 Gould, et al. Standards Track [Page 31]
1703 RFC 8334 Launch Phase Mapping for EPP March 2018
1704
1705
1706 The following is an example <create> domain command using the
1707 <launch:create> extension, following the "code" validation model,
1708 with multiple sunrise codes:
1709
1710 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1711 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1712 C: <command>
1713 C: <create>
1714 C: <domain:create
1715 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1716 C: <domain:name>domain.example</domain:name>
1717 C: <domain:registrant>jd1234</domain:registrant>
1718 C: <domain:contact type="admin">sh8013</domain:contact>
1719 C: <domain:contact type="tech">sh8013</domain:contact>
1720 C: <domain:authInfo>
1721 C: <domain:pw>2fooBAR</domain:pw>
1722 C: </domain:authInfo>
1723 C: </domain:create>
1724 C: </create>
1725 C: <extension>
1726 C: <launch:create
1727 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1728 C: <launch:phase>sunrise</launch:phase>
1729 C: <launch:codeMark>
1730 C: <launch:code validatorID="sample1">
1731 C: 49FD46E6C4B45C55D4AC</launch:code>
1732 C: </launch:codeMark>
1733 C: <launch:codeMark>
1734 C: <launch:code>49FD46E6C4B45C55D4AD</launch:code>
1735 C: </launch:codeMark>
1736 C: <launch:codeMark>
1737 C: <launch:code validatorID="sample2">
1738 C: 49FD46E6C4B45C55D4AE</launch:code>
1739 C: </launch:codeMark>
1740 C: </launch:create>
1741 C: </extension>
1742 C: <clTRID>ABC-12345</clTRID>
1743 C: </command>
1744 C:</epp>
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757 Gould, et al. Standards Track [Page 32]
1758 RFC 8334 Launch Phase Mapping for EPP March 2018
1759
1760
1761 The following is an example <create> domain command using the
1762 <launch:create> extension, following the "mark" validation model,
1763 with the mark information:
1764
1765 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1766 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1767 C: <command>
1768 C: <create>
1769 C: <domain:create
1770 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1771 C: <domain:name>domainone.example</domain:name>
1772 C: <domain:registrant>jd1234</domain:registrant>
1773 C: <domain:contact type="admin">sh8013</domain:contact>
1774 C: <domain:contact type="tech">sh8013</domain:contact>
1775 C: <domain:authInfo>
1776 C: <domain:pw>2fooBAR</domain:pw>
1777 C: </domain:authInfo>
1778 C: </domain:create>
1779 C: </create>
1780 C: <extension>
1781 C: <launch:create
1782 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1783 C: <launch:phase>sunrise</launch:phase>
1784 C: <launch:codeMark>
1785 C: <mark:mark
1786 C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
1787 C: ...
1788 C: </mark:mark>
1789 C: </launch:codeMark>
1790 C: </launch:create>
1791 C: </extension>
1792 C: <clTRID>ABC-12345</clTRID>
1793 C: </command>
1794 C:</epp>
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812 Gould, et al. Standards Track [Page 33]
1813 RFC 8334 Launch Phase Mapping for EPP March 2018
1814
1815
1816 The following is an example <create> domain command using the
1817 <launch:create> extension, following the "code with mark" validation
1818 model, with the code and mark information:
1819
1820 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1821 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1822 C: <command>
1823 C: <create>
1824 C: <domain:create
1825 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1826 C: <domain:name>domain.example</domain:name>
1827 C: <domain:registrant>jd1234</domain:registrant>
1828 C: <domain:contact type="admin">sh8013</domain:contact>
1829 C: <domain:contact type="tech">sh8013</domain:contact>
1830 C: <domain:authInfo>
1831 C: <domain:pw>2fooBAR</domain:pw>
1832 C: </domain:authInfo>
1833 C: </domain:create>
1834 C: </create>
1835 C: <extension>
1836 C: <launch:create
1837 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1838 C: <launch:phase>sunrise</launch:phase>
1839 C: <launch:codeMark>
1840 C: <launch:code validatorID="sample">
1841 C: 49FD46E6C4B45C55D4AC</launch:code>
1842 C: <mark:mark
1843 C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
1844 C: ...
1845 C: </mark:mark>
1846 C: </launch:codeMark>
1847 C: </launch:create>
1848 C: </extension>
1849 C: <clTRID>ABC-12345</clTRID>
1850 C: </command>
1851 C:</epp>
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867 Gould, et al. Standards Track [Page 34]
1868 RFC 8334 Launch Phase Mapping for EPP March 2018
1869
1870
1871 The following is an example <create> domain command using the
1872 <launch:create> extension, following the "signed mark" validation
1873 model, with the signed mark information for a sunrise application:
1874
1875 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1876 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1877 C: <command>
1878 C: <create>
1879 C: <domain:create
1880 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1881 C: <domain:name>domainone.example</domain:name>
1882 C: <domain:registrant>jd1234</domain:registrant>
1883 C: <domain:contact type="admin">sh8013</domain:contact>
1884 C: <domain:contact type="tech">sh8013</domain:contact>
1885 C: <domain:authInfo>
1886 C: <domain:pw>2fooBAR</domain:pw>
1887 C: </domain:authInfo>
1888 C: </domain:create>
1889 C: </create>
1890 C: <extension>
1891 C: <launch:create
1892 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
1893 C: type="application">
1894 C: <launch:phase>sunrise</launch:phase>
1895 C: <smd:signedMark id="signedMark"
1896 C: xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
1897 C: ...
1898 C: </smd:signedMark>
1899 C: </launch:create>
1900 C: </extension>
1901 C: <clTRID>ABC-12345</clTRID>
1902 C: </command>
1903 C:</epp>
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922 Gould, et al. Standards Track [Page 35]
1923 RFC 8334 Launch Phase Mapping for EPP March 2018
1924
1925
1926 The following is an example <create> domain command using the
1927 <launch:create> extension, following the "signed mark" validation
1928 model, with the base64-encoded signed mark information:
1929
1930 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
1931 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
1932 C: <command>
1933 C: <create>
1934 C: <domain:create
1935 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
1936 C: <domain:name>domainone.example</domain:name>
1937 C: <domain:registrant>jd1234</domain:registrant>
1938 C: <domain:contact type="admin">sh8013</domain:contact>
1939 C: <domain:contact type="tech">sh8013</domain:contact>
1940 C: <domain:authInfo>
1941 C: <domain:pw>2fooBAR</domain:pw>
1942 C: </domain:authInfo>
1943 C: </domain:create>
1944 C: </create>
1945 C: <extension>
1946 C: <launch:create
1947 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
1948 C: <launch:phase>sunrise</launch:phase>
1949 C: <smd:encodedSignedMark
1950 C: xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
1951 C: ...
1952 C: </smd:encodedSignedMark>
1953 C: </launch:create>
1954 C: </extension>
1955 C: <clTRID>ABC-12345</clTRID>
1956 C: </command>
1957 C:</epp>
1958
1959 3.3.2. Claims Create Form
1960
1961 The Claims Create Form of the extension to the EPP domain name
1962 mapping [RFC5731] includes the information related to the
1963 registrant's acceptance of the claims notice.
1964
1965 A <launch:create> element is sent along with the regular <create>
1966 domain command. The <launch:create> element has an OPTIONAL "type"
1967 attribute that defines the expected type of object ("application" or
1968 "registration") to create. The server SHOULD validate the "type"
1969 attribute, when passed, against the type of object that will be
1970 created, and return an EPP error result code of 2306 [RFC5730] if the
1971 type is incorrect. The <launch:create> element contains the
1972 following child elements:
1973
1974
1975
1976
1977 Gould, et al. Standards Track [Page 36]
1978 RFC 8334 Launch Phase Mapping for EPP March 2018
1979
1980
1981 <launch:phase>: Contains the value of the active launch phase of the
1982 server. The server SHOULD validate the value according to
1983 Section 2.3.
1984
1985 <launch:notice>: One or more <launch:notice> elements that contain
1986 the following child elements:
1987
1988 <launch:noticeID>: Unique notice identifier for the claims
1989 notice. The <launch:noticeID> element has an OPTIONAL
1990 "validatorID" attribute that is used to define the Validator
1991 Identifier (Section 2.2); it's value indicates which
1992 Trademark Validator is the source of the claims notice, with
1993 the default being the ICANN TMCH.
1994
1995 <launch:notAfter>: Expiry of the claims notice.
1996
1997 <launch:acceptedDate>: Contains the date and time that the
1998 claims notice was accepted.
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032 Gould, et al. Standards Track [Page 37]
2033 RFC 8334 Launch Phase Mapping for EPP March 2018
2034
2035
2036 The following is an example <create> domain command using the
2037 <launch:create> extension with the <launch:notice> information for
2038 the "tmch" and the "custom-tmch" validators, for the "claims" launch
2039 phase:
2040
2041 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2042 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
2043 C: <command>
2044 C: <create>
2045 C: <domain:create
2046 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
2047 C: <domain:name>domain.example</domain:name>
2048 C: <domain:registrant>jd1234</domain:registrant>
2049 C: <domain:contact type="admin">sh8013</domain:contact>
2050 C: <domain:contact type="tech">sh8013</domain:contact>
2051 C: <domain:authInfo>
2052 C: <domain:pw>2fooBAR</domain:pw>
2053 C: </domain:authInfo>
2054 C: </domain:create>
2055 C: </create>
2056 C: <extension>
2057 C: <launch:create
2058 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
2059 C: <launch:phase>claims</launch:phase>
2060 C: <launch:notice>
2061 C: <launch:noticeID validatorID="tmch">
2062 C: 370d0b7c9223372036854775807</launch:noticeID>
2063 C: <launch:notAfter>2014-06-19T10:00:00.0Z
2064 C: </launch:notAfter>
2065 C: <launch:acceptedDate>2014-06-19T09:00:00.0Z
2066 C: </launch:acceptedDate>
2067 C: </launch:notice>
2068 C: <launch:notice>
2069 C: <launch:noticeID validatorID="custom-tmch">
2070 C: 470d0b7c9223654313275808</launch:noticeID>
2071 C: <launch:notAfter>2014-06-19T10:00:00.0Z
2072 C: </launch:notAfter>
2073 C: <launch:acceptedDate>2014-06-19T09:00:30.0Z
2074 C: </launch:acceptedDate>
2075 C: </launch:notice>
2076 C: </launch:create>
2077 C: </extension>
2078 C: <clTRID>ABC-12345</clTRID>
2079 C: </command>
2080 C:</epp>
2081
2082
2083
2084
2085
2086
2087 Gould, et al. Standards Track [Page 38]
2088 RFC 8334 Launch Phase Mapping for EPP March 2018
2089
2090
2091 3.3.3. General Create Form
2092
2093 The General Create Form of the extension to the EPP domain name
2094 mapping [RFC5731] includes the launch phase and optionally the object
2095 type to create. The OPTIONAL "type" attribute defines the expected
2096 type of object ("application" or "registration") to create. The
2097 server SHOULD validate the "type" attribute, when passed, against the
2098 type of object that will be created, and return an EPP error result
2099 code of 2306 [RFC5730] if the type is incorrect.
2100
2101 A <launch:create> element is sent along with the regular <create>
2102 domain command. The <launch:create> element contains the following
2103 child element:
2104
2105 <launch:phase>: Contains the value of the active launch phase of the
2106 server. The server SHOULD validate the value according to
2107 Section 2.3.
2108
2109 The following is an example <create> domain command using the
2110 <launch:create> extension for a "landrush" launch phase application:
2111
2112 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2113 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
2114 C: <command>
2115 C: <create>
2116 C: <domain:create
2117 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
2118 C: <domain:name>domain.example</domain:name>
2119 C: <domain:registrant>jd1234</domain:registrant>
2120 C: <domain:contact type="admin">sh8013</domain:contact>
2121 C: <domain:contact type="tech">sh8013</domain:contact>
2122 C: <domain:authInfo>
2123 C: <domain:pw>2fooBAR</domain:pw>
2124 C: </domain:authInfo>
2125 C: </domain:create>
2126 C: </create>
2127 C: <extension>
2128 C: <launch:create
2129 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
2130 C: type="application">
2131 C: <launch:phase>landrush</launch:phase>
2132 C: </launch:create>
2133 C: </extension>
2134 C: <clTRID>ABC-12345</clTRID>
2135 C: </command>
2136 C:</epp>
2137
2138
2139
2140
2141
2142 Gould, et al. Standards Track [Page 39]
2143 RFC 8334 Launch Phase Mapping for EPP March 2018
2144
2145
2146 3.3.4. Mixed Create Form
2147
2148 The Mixed Create Form supports a mix of the create forms where, for
2149 example, the Sunrise Create Form (Section 3.3.1) and the Claims
2150 Create Form (Section 3.3.2) MAY be supported in a single command by
2151 including both the verified trademark information and the information
2152 related to the registrant's acceptance of the claims notice. The
2153 server MAY support the Mixed Create Form. The "custom" launch phase
2154 SHOULD be used when using the Mixed Create Form.
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197 Gould, et al. Standards Track [Page 40]
2198 RFC 8334 Launch Phase Mapping for EPP March 2018
2199
2200
2201 The following is an example <create> domain command using the
2202 <launch:create> extension, with a mix of the Sunrise Create Form
2203 (Section 3.3.1) and the Claims Create Form (Section 3.3.2), including
2204 both a mark and a notice:
2205
2206 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2207 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
2208 C: <command>
2209 C: <create>
2210 C: <domain:create
2211 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
2212 C: <domain:name>domainone.example</domain:name>
2213 C: <domain:registrant>jd1234</domain:registrant>
2214 C: <domain:contact type="admin">sh8013</domain:contact>
2215 C: <domain:contact type="tech">sh8013</domain:contact>
2216 C: <domain:authInfo>
2217 C: <domain:pw>2fooBAR</domain:pw>
2218 C: </domain:authInfo>
2219 C: </domain:create>
2220 C: </create>
2221 C: <extension>
2222 C: <launch:create
2223 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
2224 C: type="application">
2225 C: <launch:phase name="non-tmch-sunrise">custom</launch:phase>
2226 C: <launch:codeMark>
2227 C: <mark:mark
2228 C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
2229 C: ...
2230 C: </mark:mark>
2231 C: </launch:codeMark>
2232 C: <launch:notice>
2233 C: <launch:noticeID validatorID="tmch">
2234 C: 49FD46E6C4B45C55D4AC
2235 C: </launch:noticeID>
2236 C: <launch:notAfter>2012-06-19T10:00:10.0Z
2237 C: </launch:notAfter>
2238 C: <launch:acceptedDate>2012-06-19T09:01:30.0Z
2239 C: </launch:acceptedDate>
2240 C: </launch:notice>
2241 C: </launch:create>
2242 C: </extension>
2243 C: <clTRID>ABC-12345</clTRID>
2244 C: </command>
2245 C:</epp>
2246
2247
2248
2249
2250
2251
2252 Gould, et al. Standards Track [Page 41]
2253 RFC 8334 Launch Phase Mapping for EPP March 2018
2254
2255
2256 3.3.5. Create Response
2257
2258 If the create was successful, the server MAY add a <launch:creData>
2259 element to the regular EPP <resData> to indicate that the server
2260 generated an Application Identifier (Section 2.1), when multiple
2261 applications of a given domain name are supported; otherwise, no
2262 extension is included with the regular EPP <resData>. The
2263 <launch:creData> element contains the following child elements:
2264
2265 <launch:phase>: The phase of the application that mirrors the
2266 <launch:phase> element included in the <launch:create>.
2267
2268 <launch:applicationID>: The application identifier of the
2269 application.
2270
2271 The following is an example response when multiple overlapping
2272 applications are supported by the server:
2273
2274 S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2275 S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
2276 S: <response>
2277 S: <result code="1001">
2278 S: <msg>Command completed successfully; action pending</msg>
2279 S: </result>
2280 S: <resData>
2281 S: <domain:creData
2282 S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
2283 S: <domain:name>domain.example</domain:name>
2284 S: <domain:crDate>2010-08-10T15:38:26.623854Z</domain:crDate>
2285 S: </domain:creData>
2286 S: </resData>
2287 S: <extension>
2288 S: <launch:creData
2289 S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
2290 S: <launch:phase>sunrise</launch:phase>
2291 S: <launch:applicationID>2393-9323-E08C-03B1
2292 S: </launch:applicationID>
2293 S: </launch:creData>
2294 S: </extension>
2295 S: <trID>
2296 S: <clTRID>ABC-12345</clTRID>
2297 S: <svTRID>54321-XYZ</svTRID>
2298 S: </trID>
2299 S: </response>
2300 S:</epp>
2301
2302
2303
2304
2305
2306
2307 Gould, et al. Standards Track [Page 42]
2308 RFC 8334 Launch Phase Mapping for EPP March 2018
2309
2310
2311 3.4. EPP <update> Command
2312
2313 This extension defines additional elements to extend the EPP <update>
2314 command to be used in conjunction with the domain name mapping.
2315
2316 When an EPP <update> command with the extension is sent to a server
2317 that does not support Launch Applications, it will fail. A server
2318 that does not support Launch Applications during its launch phase
2319 MUST return an EPP error result code of 2102 [RFC5730] when receiving
2320 an EPP <update> command with the extension.
2321
2322 Registry policies permitting, clients may update an application
2323 object by submitting an EPP <update> command along with a
2324 <launch:update> element to indicate the application object to be
2325 updated. The <launch:update> element contains the following child
2326 elements:
2327
2328 <launch:phase>: The phase during which the application was submitted
2329 or is associated with. The server SHOULD validate the value and
2330 return an EPP error result code of 2306 [RFC5730] if it is
2331 invalid.
2332
2333 <launch:applicationID>: The application identifier for which the
2334 client wishes to update.
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362 Gould, et al. Standards Track [Page 43]
2363 RFC 8334 Launch Phase Mapping for EPP March 2018
2364
2365
2366 The following is an example <update> domain command with the
2367 <launch:update> extension to add and remove a name server of a
2368 sunrise application with the application identifier "abc123":
2369
2370 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2371 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
2372 C: <command>
2373 C: <update>
2374 C: <domain:update
2375 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
2376 C: <domain:name>domain.example</domain:name>
2377 C: <domain:add>
2378 C: <domain:ns>
2379 C: <domain:hostObj>ns2.domain.example</domain:hostObj>
2380 C: </domain:ns>
2381 C: </domain:add>
2382 C: <domain:rem>
2383 C: <domain:ns>
2384 C: <domain:hostObj>ns1.domain.example</domain:hostObj>
2385 C: </domain:ns>
2386 C: </domain:rem>
2387 C: </domain:update>
2388 C: </update>
2389 C: <extension>
2390 C: <launch:update
2391 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
2392 C: <launch:phase>sunrise</launch:phase>
2393 C: <launch:applicationID>abc123</launch:applicationID>
2394 C: </launch:update>
2395 C: </extension>
2396 C: <clTRID>ABC-12345</clTRID>
2397 C: </command>
2398 C:</epp>
2399
2400 This extension does not define any extension to the response of an
2401 <update> domain command. After processing the command, the server
2402 replies with a standard EPP response as defined in the EPP domain
2403 name mapping [RFC5731].
2404
2405 3.5. EPP <delete> Command
2406
2407 This extension defines additional elements to extend the EPP <delete>
2408 command to be used in conjunction with the domain name mapping.
2409
2410 A client MUST NOT pass the extension on an EPP <delete> command to a
2411 server that does not support Launch Applications. A server that does
2412
2413
2414
2415
2416
2417 Gould, et al. Standards Track [Page 44]
2418 RFC 8334 Launch Phase Mapping for EPP March 2018
2419
2420
2421 not support Launch Applications during its launch phase MUST return
2422 an EPP error result code of 2102 [RFC5730] when receiving an EPP
2423 <delete> command with the extension.
2424
2425 Registry policies permitting, clients MAY withdraw an application by
2426 submitting an EPP <delete> command along with a <launch:delete>
2427 element to indicate the application object to be deleted. The
2428 <launch:delete> element contains the following child elements:
2429
2430 <launch:phase>: The phase during which the application was submitted
2431 or is associated with. The server SHOULD validate the value and
2432 return an EPP error result code of 2306 [RFC5730] if it is
2433 invalid.
2434
2435 <launch:applicationID>: The application identifier for which the
2436 client wishes to delete.
2437
2438 The following is an example <delete> domain command with the
2439 <launch:delete> extension:
2440
2441 C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2442 C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
2443 C: <command>
2444 C: <delete>
2445 C: <domain:delete
2446 C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
2447 C: <domain:name>domain.example</domain:name>
2448 C: </domain:delete>
2449 C: </delete>
2450 C: <extension>
2451 C: <launch:delete
2452 C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
2453 C: <launch:phase>sunrise</launch:phase>
2454 C: <launch:applicationID>abc123</launch:applicationID>
2455 C: </launch:delete>
2456 C: </extension>
2457 C: <clTRID>ABC-12345</clTRID>
2458 C: </command>
2459 C:</epp>
2460
2461 This extension does not define any extension to the response of a
2462 <delete> domain command. After processing the command, the server
2463 replies with a standard EPP response as defined in the EPP domain
2464 name mapping [RFC5731].
2465
2466
2467
2468
2469
2470
2471
2472 Gould, et al. Standards Track [Page 45]
2473 RFC 8334 Launch Phase Mapping for EPP March 2018
2474
2475
2476 3.6. EPP <renew> Command
2477
2478 This extension does not define any extension to the EPP <renew>
2479 command or response described in the EPP domain name mapping
2480 [RFC5731].
2481
2482 3.7. EPP <transfer> Command
2483
2484 This extension does not define any extension to the EPP <transfer>
2485 command or response described in the EPP domain name mapping
2486 [RFC5731].
2487
2488 4. Formal Syntax
2489
2490 The EPP Launch Phase Mapping schema is presented in Section 4.1.
2491
2492 The formal syntax presented is a complete schema representation of
2493 the object mapping suitable for automated validation of EPP XML
2494 instances. The BEGIN and END tags are not part of the schema; they
2495 are used to note the beginning and ending of the schema for URI
2496 registration purposes.
2497
2498 4.1. Launch Schema
2499
2500 Copyright (c) 2018 IETF Trust and the persons identified as authors
2501 of the code. All rights reserved.
2502
2503 Redistribution and use in source and binary forms, with or without
2504 modification, are permitted provided that the following conditions
2505 are met:
2506
2507 o Redistributions of source code must retain the above copyright
2508 notice, this list of conditions and the following disclaimer.
2509
2510 o Redistributions in binary form must reproduce the above copyright
2511 notice, this list of conditions and the following disclaimer in
2512 the documentation and/or other materials provided with the
2513 distribution.
2514
2515 o Neither the name of Internet Society, IETF or IETF Trust, nor the
2516 names of specific contributors, may be used to endorse or promote
2517 products derived from this software without specific prior written
2518 permission.
2519
2520 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
2521 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
2522 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
2523 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
2524
2525
2526
2527 Gould, et al. Standards Track [Page 46]
2528 RFC 8334 Launch Phase Mapping for EPP March 2018
2529
2530
2531 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
2532 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
2533 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
2534 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
2535 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
2536 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
2537 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
2538
2539 BEGIN
2540 <?xml version="1.0" encoding="UTF-8"?>
2541 <schema
2542 targetNamespace="urn:ietf:params:xml:ns:launch-1.0"
2543 xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
2544 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
2545 xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
2546 xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
2547 xmlns="http://www.w3.org/2001/XMLSchema"
2548 elementFormDefault="qualified">
2549
2550 <!-- Import common element types -->
2551 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
2552 <import namespace="urn:ietf:params:xml:ns:mark-1.0"/>
2553 <import namespace="urn:ietf:params:xml:ns:signedMark-1.0"/>
2554
2555 <annotation>
2556 <documentation>
2557 Extensible Provisioning Protocol v1.0
2558 domain name
2559 extension schema
2560 for the launch phase processing.
2561 </documentation>
2562 </annotation>
2563
2564 <!-- Child elements found in EPP commands -->
2565 <element
2566 name="check"
2567 type="launch:checkType"/>
2568 <element
2569 name="info"
2570 type="launch:infoType"/>
2571 <element
2572 name="create"
2573 type="launch:createType"/>
2574 <element
2575 name="update"
2576 type="launch:idContainerType"/>
2577 <element
2578 name="delete"
2579
2580
2581
2582 Gould, et al. Standards Track [Page 47]
2583 RFC 8334 Launch Phase Mapping for EPP March 2018
2584
2585
2586 type="launch:idContainerType"/>
2587
2588 <!-- Common container of id (identifier) element -->
2589 <complexType name="idContainerType">
2590 <sequence>
2591 <element
2592 name="phase"
2593 type="launch:phaseType"/>
2594 <element
2595 name="applicationID"
2596 type="launch:applicationIDType"/>
2597 </sequence>
2598 </complexType>
2599
2600 <!-- Definition for application identifier -->
2601 <simpleType name="applicationIDType">
2602 <restriction base="token"/>
2603 </simpleType>
2604
2605 <!-- Definition for launch phase. Name is an
2606 optional attribute used to extend the phase type.
2607 For example, when using the phase type value
2608 of "custom", the "name" can be used to specify the
2609 custom phase. -->
2610 <complexType name="phaseType">
2611 <simpleContent>
2612 <extension base="launch:phaseTypeValue">
2613 <attribute
2614 name="name"
2615 type="token"/>
2616 </extension>
2617 </simpleContent>
2618 </complexType>
2619
2620 <!-- Enumeration of launch phase values -->
2621 <simpleType name="phaseTypeValue">
2622 <restriction base="token">
2623 <enumeration value="sunrise"/>
2624 <enumeration value="landrush"/>
2625 <enumeration value="claims"/>
2626 <enumeration value="open"/>
2627 <enumeration value="custom"/>
2628 </restriction>
2629 </simpleType>
2630
2631
2632 <!-- Definition for the sunrise code -->
2633 <simpleType name="codeValue">
2634
2635
2636
2637 Gould, et al. Standards Track [Page 48]
2638 RFC 8334 Launch Phase Mapping for EPP March 2018
2639
2640
2641 <restriction base="token">
2642 <minLength value="1"/>
2643 </restriction>
2644 </simpleType>
2645
2646 <complexType name="codeType">
2647 <simpleContent>
2648 <extension base="launch:codeValue">
2649 <attribute
2650 name="validatorID"
2651 type="launch:validatorIDType"
2652 use="optional"/>
2653 </extension>
2654 </simpleContent>
2655 </complexType>
2656
2657 <!-- Definition for the notice identifier -->
2658 <simpleType name="noticeIDValue">
2659 <restriction base="token">
2660 <minLength value="1"/>
2661 </restriction>
2662 </simpleType>
2663
2664 <complexType name="noticeIDType">
2665 <simpleContent>
2666 <extension base="launch:noticeIDValue">
2667 <attribute
2668 name="validatorID"
2669 type="launch:validatorIDType"
2670 use="optional"/>
2671 </extension>
2672 </simpleContent>
2673 </complexType>
2674
2675 <!-- Definition for the validator identifier -->
2676 <simpleType name="validatorIDType">
2677 <restriction base="token">
2678 <minLength value="1"/>
2679 </restriction>
2680 </simpleType>
2681
2682 <!-- Possible status values for sunrise application -->
2683 <simpleType name="statusValueType">
2684 <restriction base="token">
2685 <enumeration value="pendingValidation"/>
2686 <enumeration value="validated"/>
2687 <enumeration value="invalid"/>
2688 <enumeration value="pendingAllocation"/>
2689
2690
2691
2692 Gould, et al. Standards Track [Page 49]
2693 RFC 8334 Launch Phase Mapping for EPP March 2018
2694
2695
2696 <enumeration value="allocated"/>
2697 <enumeration value="rejected"/>
2698 <enumeration value="custom"/>
2699 </restriction>
2700 </simpleType>
2701
2702 <!-- Status type definition -->
2703 <complexType name="statusType">
2704 <simpleContent>
2705 <extension base="normalizedString">
2706 <attribute
2707 name="s"
2708 type="launch:statusValueType"
2709 use="required"/>
2710 <attribute
2711 name="lang"
2712 type="language"
2713 default="en"/>
2714 <attribute
2715 name="name"
2716 type="token"/>
2717 </extension>
2718 </simpleContent>
2719 </complexType>
2720
2721 <!-- codeMark Type that contains an optional
2722 code with mark information -->
2723 <complexType name="codeMarkType">
2724 <sequence>
2725 <element
2726 name="code"
2727 type="launch:codeType"
2728 minOccurs="0"/>
2729 <element
2730 ref="mark:abstractMark"
2731 minOccurs="0"/>
2732 </sequence>
2733 </complexType>
2734
2735 <!-- Child elements for the create command -->
2736 <complexType name="createType">
2737 <sequence>
2738 <element
2739 name="phase"
2740 type="launch:phaseType"/>
2741 <choice minOccurs="0">
2742 <element
2743 name="codeMark"
2744
2745
2746
2747 Gould, et al. Standards Track [Page 50]
2748 RFC 8334 Launch Phase Mapping for EPP March 2018
2749
2750
2751 type="launch:codeMarkType"
2752 maxOccurs="unbounded"/>
2753 <element
2754 ref="smd:abstractSignedMark"
2755 maxOccurs="unbounded"/>
2756 <element
2757 ref="smd:encodedSignedMark"
2758 maxOccurs="unbounded"/>
2759 </choice>
2760 <element
2761 name="notice"
2762 type="launch:createNoticeType"
2763 minOccurs="0"
2764 maxOccurs="unbounded"/>
2765 </sequence>
2766 <attribute
2767 name="type"
2768 type="launch:objectType"/>
2769 </complexType>
2770
2771 <!-- Type of launch object -->
2772 <simpleType name="objectType">
2773 <restriction base="token">
2774 <enumeration value="application"/>
2775 <enumeration value="registration"/>
2776 </restriction>
2777 </simpleType>
2778
2779
2780 <!-- Child elements of the create notice element -->
2781 <complexType name="createNoticeType">
2782 <sequence>
2783 <element
2784 name="noticeID"
2785 type="launch:noticeIDType"/>
2786 <element
2787 name="notAfter"
2788 type="dateTime"/>
2789 <element
2790 name="acceptedDate"
2791 type="dateTime"/>
2792 </sequence>
2793 </complexType>
2794
2795
2796 <!-- Child elements of check (Claims Check Command) -->
2797 <complexType name="checkType">
2798 <sequence>
2799
2800
2801
2802 Gould, et al. Standards Track [Page 51]
2803 RFC 8334 Launch Phase Mapping for EPP March 2018
2804
2805
2806 <element
2807 name="phase"
2808 type="launch:phaseType"
2809 minOccurs="0"/>
2810 </sequence>
2811 <attribute
2812 name="type"
2813 type="launch:checkFormType"
2814 default="claims"/>
2815 </complexType>
2816
2817
2818 <!-- Type of check form (Claims Check or Availability Check) -->
2819 <simpleType name="checkFormType">
2820 <restriction base="token">
2821 <enumeration value="claims"/>
2822 <enumeration value="avail"/>
2823 <enumeration value="trademark"/>
2824 </restriction>
2825 </simpleType>
2826
2827
2828 <!-- Child elements of info command -->
2829 <complexType name="infoType">
2830 <sequence>
2831 <element
2832 name="phase"
2833 type="launch:phaseType"/>
2834 <element
2835 name="applicationID"
2836 type="launch:applicationIDType"
2837 minOccurs="0"/>
2838 </sequence>
2839 <attribute
2840 name="includeMark"
2841 type="boolean"
2842 default="false"/>
2843 </complexType>
2844
2845 <!-- Child response elements -->
2846 <element
2847 name="chkData"
2848 type="launch:chkDataType"/>
2849 <element
2850 name="creData"
2851 type="launch:idContainerType"/>
2852 <element
2853 name="infData"
2854
2855
2856
2857 Gould, et al. Standards Track [Page 52]
2858 RFC 8334 Launch Phase Mapping for EPP March 2018
2859
2860
2861 type="launch:infDataType"/>
2862
2863 <!-- <check> response elements -->
2864 <complexType name="chkDataType">
2865 <sequence>
2866 <element
2867 name="phase"
2868 type="launch:phaseType"
2869 minOccurs="0"/>
2870 <element
2871 name="cd"
2872 type="launch:cdType"
2873 maxOccurs="unbounded"/>
2874 </sequence>
2875 </complexType>
2876
2877 <complexType name="cdType">
2878 <sequence>
2879 <element
2880 name="name"
2881 type="launch:cdNameType"/>
2882 <element
2883 name="claimKey"
2884 type="launch:claimKeyType"
2885 minOccurs="0"
2886 maxOccurs="unbounded"/>
2887 </sequence>
2888 </complexType>
2889
2890 <complexType name="cdNameType">
2891 <simpleContent>
2892 <extension base="eppcom:labelType">
2893 <attribute
2894 name="exists"
2895 type="boolean"
2896 use="required"/>
2897 </extension>
2898 </simpleContent>
2899 </complexType>
2900
2901 <complexType name="claimKeyType">
2902 <simpleContent>
2903 <extension base="token">
2904 <attribute
2905 name="validatorID"
2906 type="launch:validatorIDType"
2907 use="optional"/>
2908 </extension>
2909
2910
2911
2912 Gould, et al. Standards Track [Page 53]
2913 RFC 8334 Launch Phase Mapping for EPP March 2018
2914
2915
2916 </simpleContent>
2917 </complexType>
2918
2919 <!-- <info> response elements -->
2920 <complexType name="infDataType">
2921 <sequence>
2922 <element
2923 name="phase"
2924 type="launch:phaseType"/>
2925 <element
2926 name="applicationID"
2927 type="launch:applicationIDType"
2928 minOccurs="0"/>
2929 <element
2930 name="status"
2931 type="launch:statusType"
2932 minOccurs="0"/>
2933 <element
2934 ref="mark:abstractMark"
2935 minOccurs="0"
2936 maxOccurs="unbounded"/>
2937 </sequence>
2938 </complexType>
2939
2940 </schema>
2941 END
2942
2943 5. IANA Considerations
2944
2945 5.1. XML Namespace
2946
2947 This document uses URNs to describe XML namespaces and XML schemas
2948 conforming to a registry mechanism described in [RFC3688].
2949
2950 IANA has registered the launch namespace as follows:
2951
2952 URI: urn:ietf:params:xml:ns:launch-1.0
2953
2954 Registrant Contact: IESG
2955
2956 XML: None. Namespace URIs do not represent an XML specification.
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967 Gould, et al. Standards Track [Page 54]
2968 RFC 8334 Launch Phase Mapping for EPP March 2018
2969
2970
2971 IANA has registered the launch XML schema as follows:
2972
2973 URI: urn:ietf:params:xml:schema:launch-1.0
2974
2975 Registrant Contact: IESG
2976
2977 XML: See the "Formal Syntax" section of this document.
2978
2979 5.2. EPP Extension Registry
2980
2981 IANA has registered the EPP extension described in this document in
2982 the "Extensions for the Extensible Provisioning Protocol (EPP)"
2983 registry described in [RFC7451]. The details of the registration are
2984 as follows:
2985
2986 Name of Extension: "Launch Phase Mapping for the Extensible
2987 Provisioning Protocol (EPP)"
2988
2989 Document Status: Standards Track
2990
2991 Reference: RFC 8334
2992
2993 Registrant Name and Email Address: IESG, <iesg@ietf.org>
2994
2995 TLDs: Any
2996
2997 IPR Disclosure: None
2998
2999 Status: Active
3000
3001 Notes: None
3002
3003 6. Security Considerations
3004
3005 The mapping extensions described in this document do not provide any
3006 security services beyond those described by EPP [RFC5730], the EPP
3007 domain name mapping [RFC5731], and protocol layers used by EPP. The
3008 security considerations described in these other specifications apply
3009 to this specification as well.
3010
3011 Updates to, and deletion of, an application object MUST be restricted
3012 to clients authorized to perform the said operation on the object.
3013
3014 Information contained within an application, or even the mere fact
3015 that an application exists, may be confidential. Any attempt to
3016 operate on an application object by an unauthorized client MUST be
3017 rejected with an EPP 2201 (authorization error) return code. Server
3018 policy may allow an <info> operation with filtered output by clients
3019
3020
3021
3022 Gould, et al. Standards Track [Page 55]
3023 RFC 8334 Launch Phase Mapping for EPP March 2018
3024
3025
3026 other than the sponsoring client, in which case the <domain:infData>
3027 and <launch:infData> responses SHOULD be filtered to include only
3028 fields that are publicly accessible.
3029
3030 7. References
3031
3032 7.1. Normative References
3033
3034 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
3035 Requirement Levels", BCP 14, RFC 2119,
3036 DOI 10.17487/RFC2119, March 1997,
3037 <https://www.rfc-editor.org/info/rfc2119>.
3038
3039 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
3040 DOI 10.17487/RFC3688, January 2004,
3041 <https://www.rfc-editor.org/info/rfc3688>.
3042
3043 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
3044 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
3045 September 2009, <https://www.rfc-editor.org/info/rfc5646>.
3046
3047 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
3048 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
3049 <https://www.rfc-editor.org/info/rfc5730>.
3050
3051 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
3052 Domain Name Mapping", STD 69, RFC 5731,
3053 DOI 10.17487/RFC5731, August 2009,
3054 <https://www.rfc-editor.org/info/rfc5731>.
3055
3056 [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping",
3057 RFC 7848, DOI 10.17487/RFC7848, June 2016,
3058 <https://www.rfc-editor.org/info/rfc7848>.
3059
3060 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
3061 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
3062 May 2017, <https://www.rfc-editor.org/info/rfc8174>.
3063
3064 [W3C.REC-xml11-20060816]
3065 Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E.,
3066 Yergeau, F., and J. Cowan, "Extensible Markup Language
3067 (XML) 1.1 (Second Edition)", World Wide Web Consortium
3068 Recommendation REC-xml11-20060816, August 2006,
3069 <http://www.w3.org/TR/2006/REC-xml11-20060816>.
3070
3071
3072
3073
3074
3075
3076
3077 Gould, et al. Standards Track [Page 56]
3078 RFC 8334 Launch Phase Mapping for EPP March 2018
3079
3080
3081 7.2. Informative References
3082
3083 [ICANN-TMCH]
3084 Lozano, G., "ICANN TMCH functional specifications", Work
3085 in Progress, draft-ietf-regext-tmch-func-spec-03, July
3086 2017.
3087
3088 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
3089 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
3090 February 2015, <https://www.rfc-editor.org/info/rfc7451>.
3091
3092 Acknowledgements
3093
3094 The authors wish to acknowledge the efforts of the leading
3095 participants of the Community TMCH Model that led to many of the
3096 changes to this document, which include Chris Wright, Jeff Neuman,
3097 Jeff Eckhaus, and Will Shorter.
3098
3099 Special suggestions that have been incorporated into this document
3100 were provided by Harald Alvestrand, Ben Campbell, Spencer Dawkins,
3101 Jothan Frakes, Keith Gaughan, Seth Goldman, Scott Hollenbeck, Michael
3102 Holloway, Jan Jansen, Rubens Kuhl, Mirja Kuehlewind, Warren Kumari,
3103 Ben Levac, Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Alexey
3104 Melnikov, Patrick Mevzek, James Mitchell, Francisco Obispo, Mike
3105 O'Connell, Eric Rescorla, Bernhard Reutner-Fischer, Sabrina Tanamal,
3106 Trung Tran, Ulrich Wisser, and Sharon Wodjenski.
3107
3108 Some of the description of the Trademark Claims Phase was based on
3109 the work done by Gustavo Lozano in the ICANN TMCH functional
3110 specifications.
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132 Gould, et al. Standards Track [Page 57]
3133 RFC 8334 Launch Phase Mapping for EPP March 2018
3134
3135
3136 Authors' Addresses
3137
3138 James Gould
3139 VeriSign, Inc.
3140 12061 Bluemont Way
3141 Reston, VA 20190
3142 United States of America
3143
3144 Email: jgould@verisign.com
3145 URI: http://www.verisign.com
3146
3147
3148 Wil Tan
3149 Cloud Registry
3150 Suite 32 Seabridge House
3151 377 Kent St
3152 Sydney, NSW 2000
3153 Australia
3154
3155 Phone: +61 414 710899
3156 Email: wil@cloudregistry.net
3157 URI: http://www.cloudregistry.net
3158
3159
3160 Gavin Brown
3161 CentralNic Ltd
3162 35-39 Mooregate
3163 London, England EC2R 6AR
3164 United Kingdom
3165
3166 Phone: +44 20 33 88 0600
3167 Email: gavin.brown@centralnic.com
3168 URI: https://www.centralnic.com
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187 Gould, et al. Standards Track [Page 58]
3188
The IETF is responsible for the creation and maintenance of the DNS RFCs. The ICANN DNS RFC annotation project provides a forum for collecting community annotations on these RFCs as an aid to understanding for implementers and any interested parties. The annotations displayed here are not the result of the IETF consensus process.
This RFC is included in the DNS RFCs annotation project whose home page is here.