idnits 2.17.1 draft-ietf-eppext-launchphase-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 27, 2015) is 3346 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 2247 -- Looks like a reference, but probably isn't: '2' on line 2249 == Outdated reference: A later version (-06) exists of draft-ietf-eppext-tmch-smd-01 ** Obsolete normative reference: RFC 6982 (Obsoleted by RFC 7942) ** Downref: Normative reference to an Informational RFC: RFC 7451 Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Gould 3 Internet-Draft VeriSign, Inc. 4 Intended status: Standards Track W. Tan 5 Expires: August 31, 2015 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 February 27, 2015 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-ietf-eppext-launchphase-04 13 Abstract 15 This document describes an Extensible Provisioning Protocol (EPP) 16 extension mapping for the provisioning and management of domain name 17 registrations and applications during the launch of a domain name 18 registry. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on August 31, 2015. 37 Copyright Notice 39 Copyright (c) 2015 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Conventions Used in This Document . . . . . . . . . . . . 4 56 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 5 57 2.1. Application Identifier . . . . . . . . . . . . . . . . . 5 58 2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5 59 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 6 60 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 6 61 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 8 62 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 9 63 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 12 64 2.6.1. element . . . . . . . . . . . . . . 13 65 2.6.2. element . . . . . . . . . . . . . . . . . 14 66 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 14 67 2.6.3.1. element . . . . . . . . . . . . 14 68 2.6.3.2. element . . . . . . . . . 14 69 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 14 70 3.1. EPP Command . . . . . . . . . . . . . . . . . . . 15 71 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 15 72 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 18 73 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 20 74 3.2. EPP Command . . . . . . . . . . . . . . . . . . . 23 75 3.3. EPP Command . . . . . . . . . . . . . . . . . . 26 76 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 26 77 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 32 78 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 35 79 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 36 80 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 38 81 3.4. EPP Command . . . . . . . . . . . . . . . . . . 39 82 3.5. EPP Command . . . . . . . . . . . . . . . . . . 40 83 3.6. EPP Command . . . . . . . . . . . . . . . . . . . 41 84 3.7. EPP Command . . . . . . . . . . . . . . . . . 42 85 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 42 86 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 42 87 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 88 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 49 89 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 50 90 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 50 91 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 51 92 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 51 93 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 52 94 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 52 95 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 52 96 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 53 98 7. Security Considerations . . . . . . . . . . . . . . . . . . . 53 99 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 54 100 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 54 101 9.1. Normative References . . . . . . . . . . . . . . . . . . 54 102 9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 55 103 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 55 104 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 55 105 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 55 106 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 55 107 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 55 108 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 56 109 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 56 110 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 56 111 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 56 112 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 57 113 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 57 114 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 58 115 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 58 116 A.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 59 117 A.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 59 118 A.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 59 119 A.16. Change WG 02 to WG 03 . . . . . . . . . . . . . . . . . . 59 120 A.17. Change WG 03 to WG 04 . . . . . . . . . . . . . . . . . . 59 121 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59 123 1. Introduction 125 This document describes an extension mapping for version 1.0 of the 126 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 127 specifies a flexible schema that can be used to implement several 128 common use cases related to the provisioning and management of domain 129 name registrations and applications during the launch of a domain 130 name registry. 132 It is typical for domain registries to operate in special modes 133 during their initial launch to facilitate allocation of domain names, 134 often according to special rules. This document uses the term 135 "launch phase" and the shorter form "launch" to refer to such a 136 period. 138 The EPP domain name mapping [RFC5731] is designed for the steady- 139 state operation of a registry. During a launch period, the model in 140 place may be different from what is defined in the EPP domain name 141 mapping [RFC5731]. For example, registries often accept multiple 142 applications for the same domain name during the "Sunrise" launch 143 phase, referred to as a Launch Application. A Launch Registration 144 refers to a registration made during a launch phase when the server 145 uses a "first-come, first-served" model. Even in a "first-come, 146 first-served" model, additional steps and information might be 147 required, such as trademark information. In addition, the 148 [I-D.ietf-eppext-tmch-smd] defines a registry interface for the 149 Trademark Claims or "claims" launch phase that includes support for 150 presenting a Trademark Claims Notice to the Registrant. This 151 document proposes an extension to the domain name mapping in order to 152 provide a uniform interface for the management of Launch Applications 153 and Launch Registrations in launch phases. 155 1.1. Conventions Used in This Document 157 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 158 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 159 document are to be interpreted as described in RFC 2119 [RFC2119]. 161 XML is case sensitive. Unless stated otherwise, XML specifications 162 and examples provided in this document MUST be interpreted in the 163 character case presented in order to develop a conforming 164 implementation. 166 In examples, "C:" represents lines sent by a protocol client and "S:" 167 represents lines returned by a protocol server. Indentation and 168 white space in examples are provided only to illustrate element 169 relationships and are not a REQUIRED feature of this protocol. 171 "launch-1.0" is used as an abbreviation for 172 "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix 173 "launch" is used, but implementations MUST NOT depend on it and 174 instead employ a proper namespace-aware XML parser and serializer to 175 interpret and output the XML documents. 177 "signedMark-1.0" is used as an abbreviation for 178 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in 179 [I-D.ietf-eppext-tmch-smd]. The XML namespace prefix "smd" is used, 180 but implementations MUST NOT depend on it and instead employ a proper 181 namespace-aware XML parser and serializer to interpret and output the 182 XML documents. 184 "mark-1.0" is used as an abbreviation for 185 "urn:ietf:params:xml:ns:mark-1.0" that is defined in 186 [I-D.ietf-eppext-tmch-smd]. The XML namespace prefix "mark" is used, 187 but implementations MUST NOT depend on it and instead employ a proper 188 namespace-aware XML parser and serializer to interpret and output the 189 XML documents. 191 2. Object Attributes 193 This extension adds additional elements to the EPP domain name 194 mapping [RFC5731]. Only those new elements are described here. 196 2.1. Application Identifier 198 Servers MAY allow multiple applications, referred to as a Launch 199 Application, of the same domain name during its launch phase 200 operations. Upon receiving a valid request to create a Launch 201 Application, the server MUST create an application object 202 corresponding to the request, assign an application identifier for 203 the Launch Application, set the [RFC5731] pendingCreate status, and 204 return the application identifier to the client with the 205 element. In order to facilitate correlation, 206 all subsequent launch operations on the Launch Application MUST be 207 qualified by the previously assigned application identifier using the 208 element. 210 If the command processes a request synchronously 211 without the use of an intermediate Launch Application, then an 212 application identifier MAY not be needed. 214 2.2. Validator Identifier 216 The Validator Identifier is the unique identifier for a Trademark 217 Validator that validates marks and has a repository of validated 218 marks. The OPTIONAL "validatorID" attribute is used to define the 219 Validator Identifier of the Trademark Validator. Registries MAY 220 support more than one Third Party Trademark Validator. The Internet 221 Corporation for Assigned Names and Numbers (ICANN) Trademark 222 Clearinghouse (TMCH) is the default Trademark Validator and is 223 reserved the Validator Identifier of "tmch". If the ICANN TMCH is 224 not used or multiple Trademark Validators are used, the Validator 225 Identifier MUST be defined using the "validatorID" attribute. 227 The Validator Identifier MAY be related to one or more issuer 228 identifiers of the element and the element defined 229 in [I-D.ietf-eppext-tmch-smd]. Both the Validator Identifier and the 230 Issuer Identifier used MUST be unique. The list of validator 231 identifiers and the relationship to issuer identifiers is out of 232 scope for this document. 234 The Validator Identifier MAY define a non-Trademark Validator that 235 supports a form of claims. 237 2.3. Launch Phases 239 The server MAY support multiple launch phases sequentially or 240 simultaneously. The element MUST be included by the 241 client to define the target launch phase of the command. The server 242 SHOULD validate the phase and MAY validate the sub-phase of the 243 element against the active phase and OPTIONAL sub- 244 phase of the server on a create command, and return an EPP error 245 result code of 2306 if there is a mismatch. 247 The following launch phase values are defined: 249 sunrise The phase during which trademark holders can submit 250 registrations or applications with trademark information that can 251 be validated by the server. 252 landrush A post-Sunrise phase when non-trademark holders are allowed 253 to register domain names with steps taken to address a large 254 volume of initial registrations. 255 claims The Trademark Claims phase, as defined in the TMCH Functional 256 Specification [1], in which a Claims Notice must be displayed to a 257 prospective registrant of a domain name that matches trademarks. 258 open A post-launch phase that is also referred to as "steady state". 259 Servers MAY require additional trademark protection during this 260 phase. 261 custom A custom server launch phase that is defined using the "name" 262 attribute. 264 For extensibility, the element includes an OPTIONAL 265 "name" attribute that can define a sub-phase or the full name of the 266 phase when the element has the "custom" value. For 267 example, the "claims" launch phase could have two sub-phases that 268 include "landrush" and "open". 270 Launch phases MAY overlap to support the "claims" launch phase, 271 defined in the TMCH Functional Specification [2], and to support a 272 traditional "landrush" launch phase. The overlap of the "claims" and 273 "landrush" launch phases SHOULD be handled by setting "claims" as the 274 value and setting "landrush" as the sub-phase with the 275 "name" attribute. For example, the element SHOULD be 276 claims. 278 2.4. Status Values 280 A Launch Application or Launch Registration object MAY have a launch 281 status value. The element is used to convey the 282 launch status pertaining to the object, beyond what is specified in 283 the object mapping. A Launch Application or Launch Registration MUST 284 set the [RFC5731] "pendingCreate" status if a launch status is 285 supported and the launch status is not one of the final statuses, 286 including the "allocated" and "rejected" statuses. 288 The following status values are defined using the required "s" 289 attribute: 291 pendingValidation: The initial state of a newly-created application 292 or registration object. The application or registration requires 293 validation, but the validation process has not yet completed. 294 validated: The application or registration meets relevant registry 295 rules. 296 invalid: The application or registration does not validate according 297 to registry rules. Server policies permitting, it may transition 298 back into "pendingValidation" for revalidation, after 299 modifications are made to ostensibly correct attributes that 300 caused the validation failure. 301 pendingAllocation: The allocation of the application or registration 302 is pending based on the results of some out-of-band process (for 303 example, an auction). 304 allocated: The object corresponding to the application or 305 registration has been provisioned. Is a possible end state of an 306 application or registration object. 307 rejected: The application or registration object was not 308 provisioned. Is a possible end state of an application or 309 registration object. 310 custom: A custom status that is defined using the "name" attribute. 312 Each status value MAY be accompanied by a string of human-readable 313 text that describes the rationale for the status applied to the 314 object. The OPTIONAL "lang" attribute MAY be present to identify the 315 language if the negotiated value is something other than the default 316 value of "en" (English). 318 For extensibility the element includes an OPTIONAL 319 "name" attribute that can define a sub-status or the full name of the 320 status when the status value is "custom". The server SHOULD NOT use 321 the "custom" status value. 323 Status values MAY be skipped. For example, an application or 324 registration MAY immediately start at the "allocated" status or an 325 application or registration MAY skip the "pendingAllocation" status. 326 If the launch phase does not require validation of a request, an 327 application or registration MAY immediately skip to 328 "pendingAllocation". 330 2.4.1. State Transition 332 | request 333 | 334 | +--------------------------+ 335 | | | 336 v v | 337 +-------------------+ | 338 | | | 339 | pendingValidation +--------------+ | 340 | | | | 341 +---------+---------+ | | 342 | | | 343 | | | 344 v v | 345 +-----------+ +---------+ | 346 | | | | | 347 | validated | | invalid +--+ 348 | | | | 349 +-----+-----+ +----+----+ 350 | | 351 | | 352 v | 353 +-------------------+ | 354 | | | 355 | pendingAllocation +-----------+ | 356 | | | | 357 +---------+---------+ | | 358 | | | 359 | | | 360 | | | 361 | | | 362 | | | 363 v v v 364 +---------+ +--------+ 365 / \ / \ 366 | allocated | | rejected | 367 \ / \ / 368 +---------+ +--------+ 370 Figure 1 372 2.5. Poll Messaging 374 A Launch Application MUST and a Launch Registration MAY be handled as 375 a domain name of [RFC5731] in "pendingCreate" status, with the launch 376 status values defined in Section 2.4. As a Launch Application or 377 Launch Registration transitions between the status values defined in 378 Section 2.4, the server SHOULD insert poll messages, per [RFC5730], 379 for the applicable intermediate statuses, including the 380 "pendingValidation", "validated", "pendingAllocation, and "invalid" 381 statuses, using the element with the 382 extension. The element MAY contain 383 non-mandatory information, like contact and name server information. 384 Also, further extensions that would normally be included in the 385 response of a command, per [RFC5731], MAY be included. 386 For the final statuses, including the "allocated" and "rejected" 387 statuses, the server MUST insert a poll message, per 388 [RFC5731], with the extension. 390 The following is an example poll message for a Launch Application 391 that has transitioned to the "pendingAllocation" state. 393 S: 394 S: 395 S: 396 S: 397 S: Command completed successfully; ack to dequeue 398 S: 399 S: 400 S: 2013-04-04T22:01:00.0Z 401 S: Application pendingAllocation. 402 S: 403 S: 404 S: 406 S: example.tld 407 S: ... 408 S: 409 S: 410 S: 411 S: 413 S: sunrise 414 S: abc123 415 S: 416 S: 417 S: 418 S: 419 S: ABC-12345 420 S: 54322-XYZ 421 S: 422 S: 423 S: 424 The following is an example poll message for an 425 "allocated" Launch Application. 427 S: 428 S: 429 S: 430 S: 431 S: Command completed successfully; ack to dequeue 432 S: 433 S: 434 S: 2013-04-04T22:01:00.0Z 435 S: Application successfully allocated. 436 S: 437 S: 438 S: 440 S: example.tld 441 S: 442 S: ABC-12345 443 S: 54321-XYZ 444 S: 445 S: 2013-04-04T22:00:00.0Z 446 S: 447 S: 448 S: 449 S: 451 S: sunrise 452 S: abc123 453 S: 454 S: 455 S: 456 S: 457 S: BCD-23456 458 S: 65432-WXY 459 S: 460 S: 461 S: 462 The following is an example poll message for an 463 "allocated" Launch Registration. 465 S: 466 S: 467 S: 468 S: 469 S: Command completed successfully; ack to dequeue 470 S: 471 S: 472 S: 2013-04-04T22:01:00.0Z 473 S: Registration successfully allocated. 474 S: 475 S: 476 S: 478 S: example.tld 479 S: 480 S: ABC-12345 481 S: 54321-XYZ 482 S: 483 S: 2013-04-04T22:00:00.0Z 484 S: 485 S: 486 S: 487 S: 489 S: sunrise 490 S: 491 S: 492 S: 493 S: 494 S: BCD-23456 495 S: 65432-WXY 496 S: 497 S: 498 S: 500 2.6. Mark Validation Models 502 A server MUST support at least one of the following models for 503 validating trademark information: 505 code Use of a mark code by itself to validate that the mark matches 506 the domain name. This model is supported using the 507 element with just the element. 508 mark The mark information is passed without any other validation 509 element. The server will use some custom form of validation to 510 validate that the mark information is authentic. This model is 511 supported using the element with just the 512 (Section 2.6.2) element. 513 code with mark: A code is used along with the mark information by 514 the server to validate the mark utilizing an external party. The 515 code represents some form of secret that matches the mark 516 information passed. This model is supported using the 517 element that contains both the and 518 the (Section 2.6.2) elements. 519 signed mark: The mark information is digitally signed as described 520 in the Digital Signature (Section 2.6.3) section. The digital 521 signature can be directly validated by the server using the public 522 key of the external party that created the signed mark using its 523 private key. This model is supported using the 524 (Section 2.6.3.1) and (Section 2.6.3.2) 525 elements. 527 More than one , (Section 2.6.3.1), 528 or (Section 2.6.3.2) element MAY be 529 specified. The maximum number of marks per domain name is up to 530 server policy. 532 2.6.1. element 534 The element that is used by the "code", "mark", and 535 "code with mark" validation models, has the following child elements: 537 : OPTIONAL mark code used to validate the 538 (Section 2.6.2) information. The mark code is be a mark-specific 539 secret that the server can verify against a third party. The 540 OPTIONAL "validatorID" attribute is the Validator Identifier 541 (Section 2.2) whose value indicates which Trademark Validator that 542 the code originated from, with no default value. 543 : OPTIONAL mark information with child elements defined 544 in the Mark (Section 2.6.2) section. 546 The following is an example element with both a 547 and (Section 2.6.2) element. 549 550 551 49FD46E6C4B45C55D4AC 552 553 ... 554 555 557 2.6.2. element 559 A element describes an applicant's prior right to a given 560 domain name that is used with the "mark", "mark with code", and the 561 "signed mark" validation models. The element is defined 562 in [I-D.ietf-eppext-tmch-smd]. A new mark format can be supported by 563 creating a new XML schema for the mark that has an element that 564 substitutes for the element from 565 [I-D.ietf-eppext-tmch-smd]. 567 2.6.3. Digital Signature 569 Digital signatures MAY be used by the server to validate either the 570 mark information, when using the "signed mark" validation model with 571 the (Section 2.6.3.1) element or the 572 (Section 2.6.3.2) element. 574 2.6.3.1. element 576 The element contains the digitally signed mark 577 information. The element is defined in 578 [I-D.ietf-eppext-tmch-smd]. A new signed mark format can be 579 supported by creating a new XML schema for the signed mark that has 580 an element that substitutes for the element 581 from [I-D.ietf-eppext-tmch-smd]. 583 2.6.3.2. element 585 The element contains an encoded form of the 586 digitally signed (Section 2.6.3.1) element. The 587 element is defined in 588 [I-D.ietf-eppext-tmch-smd]. A new encoded signed mark format can be 589 supported by creating a new XML schema for the encoded signed mark 590 that has an element that substitutes for the 591 element from [I-D.ietf-eppext-tmch-smd]. 593 3. EPP Command Mapping 595 A detailed description of the EPP syntax and semantics can be found 596 in the EPP core protocol specification [RFC5730]. The command 597 mappings described here are specifically for use in the Launch Phase 598 Extension. 600 This mapping is designed to be flexible, requiring only a minimum set 601 of required elements. 603 While it is meant to serve several use cases, it does not prescribe 604 any interpretation by the client or server. Such processing is 605 typically highly policy-dependent and therefore specific to 606 implementations. 608 Operations on application objects are done via one or more of the 609 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 610 Registries MAY choose to support a subset of the operations. 612 3.1. EPP Command 614 There are three forms of the extension to the EPP command: 615 the Claims Check Form (Section 3.1.1), the Availability Check Form 616 (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The 617 element "type" attribute defines the form, with the 618 value of "claims" for the Claims Check Form (Section 3.1.1), with the 619 value of "avail" for the Availability Check Form (Section 3.1.2), and 620 with the value of "trademark" for the Trademark Check Form 621 (Section 3.1.3). The default value of the "type" attribute is 622 "claims". The forms supported by the server is determined by server 623 policy. The server MUST return an EPP error result code of 2307 if 624 it receives a check form that is not supported. 626 3.1.1. Claims Check Form 628 The Claims Check Form defines a new command called the Claims Check 629 Command that is used to determine whether or not there are any 630 matching trademarks, in the specified launch phase, for each domain 631 name passed in the command, that requires the use of the "Claims 632 Create Form" on a Domain Create Command. The availability check 633 information defined in the EPP domain name mapping [RFC5731] MUST NOT 634 be returned for the Claims Check Command. This form is the default 635 form and MAY be explicitly identified by setting the 636 "type" attribute to "claims". 638 Instead of returning whether the domain name is available, the Claims 639 Check Command will return whether or not at least one matching 640 trademark exists for the domain name, that requires the use of the 641 "Claims Create Form" on a Domain Create Command. If there is at 642 least one matching trademark that exists for the domain name, a 643 element is returned. The client MAY then use the 644 value of the element to obtain information needed 645 to generate the Trademark Claims Notice from Trademark Validator 646 based on the Validator Identifier (Section 2.2). The unique notice 647 identifier of the Trademark Claims Notice MUST be passed in the 648 element of the extension to the Create Command 649 (Section 3.3). 651 The elements in the EPP command of EPP domain 652 name mapping [RFC5731] define the domain names to check for matching 653 trademarks. The element contains the following child 654 elements: 656 Contains the value of the active launch phase of the 657 server. The server SHOULD validate the value against the active 658 server launch phase. 660 Example Claims Check command using the domain command and the 661 extension with the "type" explicitly set to "claims", 662 to determine if "example1.tld", "example2.tld", and "example3.tld" 663 require claims notices during the "claims" launch phase: 665 C: 666 C: 667 C: 668 C: 669 C: 671 C: example1.tld 672 C: example2.tld 673 C: example3.tld 674 C: 675 C: 676 C: 677 C: 680 C: claims 681 C: 682 C: 683 C: ABC-12345 684 C: 685 C: 687 If the command has been processed successfully, the EPP 688 MUST contain an element that 689 identifies the launch namespace. The element 690 contains the following child elements: 692 The phase that mirrors the element 693 included in the . 694 One or more elements that contain the 695 following child elements: 697 Contains the fully qualified name of the queried 698 domain name. This element MUST contain an "exists" attribute 699 whose value indicates if a matching trademark exists for the 700 domain name that requires the use of the "Claims Create Form" 701 on a Domain Create Command. A value of "1" (or "true") means 702 that a matching trademark does exist and that the "Claims 703 Create Form" is required on a Domain Create Command. A value 704 of "0" (or "false") means that a matching trademark does not 705 exist or that the "Claims Create Form" is NOT required on a 706 Domain Create Command. 707 Zero or more OPTIONAL claim keys that MAY be 708 passed to a third-party trademark validator such as the 709 Trademark Clearinghouse (TMCH) for querying the information 710 needed to generate a Trademark Claims Notice. The 711 is used as the key for the query in place 712 of the domain name to securely query the service without 713 using a well-known value like a domain name. The OPTIONAL 714 "validatorID" attribute is the Validator Identifier 715 (Section 2.2) whose value indicates which Trademark Validator 716 to query for the Claims Notice information, with the default 717 being the ICANN TMCH. The "validatorID" attribute MAY 718 reference a non-trademark claims clearinghouse identifer to 719 support other forms of claims notices. 721 Example Claims Check response when a claims notice is not required 722 for the domain name example1.tld, a claims notice is required for the 723 domain name example2.tld in the "tmch", and a claims notice is 724 required for the domain name example3.tld in the "tmch" and "custom- 725 tmch", for the "claims" launch phase: 727 S: 728 S: 729 S: 730 S: 731 S: Command completed successfully 732 S: 733 S: 734 S: 736 S: claims 737 S: 738 S: example1.tld 739 S: 740 S: 741 S: example2.tld 742 S: 743 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 744 S: 745 S: 746 S: 747 S: example3.tld 748 S: 749 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 750 S: 751 S: 752 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 753 S: 754 S: 755 S: 756 S: 757 S: 758 S: ABC-12345 759 S: 54321-XYZ 760 S: 761 S: 762 S: 764 3.1.2. Availability Check Form 766 The Availability Check Form defines additional elements to extend the 767 EPP command described in the EPP domain name mapping 768 [RFC5731]. No additional elements are defined for the EPP 769 response. This form MUST be identified by setting the 770 "type" attribute to "avail". 772 The EPP command is used to determine if an object can be 773 provisioned within a repository. Domain names may be made available 774 only in unique launch phases, whilst remaining unavailable for 775 concurrent launch phases. In addition to the elements expressed in 776 the , the command is extended with the 777 element that contains the following child elements: 779 The launch phase to which domain name availability 780 should be determined. 782 Example Availability Check Form command using the domain 783 command and the extension with the "type" set to 784 "avail", to determine the availability of two domain names in the 785 "idn-release" custom launch phase: 787 C: 788 C: 789 C: 790 C: 791 C: 793 C: example1.tld 794 C: example2.tld 795 C: 796 C: 797 C: 798 C: 801 C: custom 802 C: 803 C: 804 C: ABC-12345 805 C: 806 C: 808 The Availability Check Form does not define any extension to the 809 response of an domain command. After processing the command, 810 the server replies with a standard EPP response as defined in the EPP 811 domain name mapping [RFC5731]. 813 3.1.3. Trademark Check Form 815 The Trademark Check Form defines a new command called the Trademark 816 Check Command that is used to determine whether or not there are any 817 matching trademarks for each domain name passed in the command, 818 independent of the active launch phase of the server and whether the 819 "Claims Create Form" is required on a Domain Create Command. The 820 availability check information defined in the EPP domain name mapping 821 [RFC5731] MUST NOT be returned for the Claims Check Command. This 822 form MUST be identified by setting the "type" 823 attribute to "trademark". 825 Instead of returning whether the domain name is available, the 826 Trademark Check Command will return whether or not at least one 827 matching trademark exists for the domain name. If there is at least 828 one matching trademark that exists for the domain name, a 829 element is returned. The client MAY then use the 830 value of the element to obtain Trademark Claims 831 Notice information from Trademark Validator based on the Validator 832 Identifier (Section 2.2). 834 The elements in the EPP command of EPP domain 835 name mapping [RFC5731] define the domain names to check for matching 836 trademarks. The element does not contain any child 837 elements with the "Trademark Check Form": 839 Example Trademark Check command using the domain command and 840 the extension with the "type" set to "trademark", to 841 determine if "example1.tld", "example2.tld", and "example3.tld" have 842 any matching trademarks: 844 C: 845 C: 846 C: 847 C: 848 C: 850 C: example1.tld 851 C: example2.tld 852 C: example3.tld 853 C: 854 C: 855 C: 856 C: 859 C: 860 C: ABC-12345 861 C: 862 C: 864 If the command has been processed successfully, the EPP 865 MUST contain an element that 866 identifies the launch namespace. The element 867 contains the following child elements: 869 One or more elements that contain the 870 following child elements: 872 Contains the fully qualified name of the queried 873 domain name. This element MUST contain an "exists" attribute 874 whose value indicates if a matching trademark exists for the 875 domain name. A value of "1" (or "true") means that a 876 matching trademark does exist. A value of "0" (or "false") 877 means that a matching trademark does not exist. 878 Zero or more OPTIONAL claim keys that MAY be 879 passed to a third-party trademark validator such as the 880 Trademark Clearinghouse (TMCH) for querying the information 881 needed to generate a Trademark Claims Notice. The 882 is used as the key for the query in place 883 of the domain name to securely query the service without 884 using a well-known value like a domain name. The OPTIONAL 885 "validatorID" attribute is the Validator Identifier 886 (Section 2.2) whose value indicates which Trademark Validator 887 to query for the Claims Notice information, with the default 888 being the ICANN TMCH. The "validatorID" attribute MAY 889 reference a non-trademark claims clearinghouse identifer to 890 support other forms of claims notices. 892 Example Trademark Check response when no matching trademarks are 893 found for the domain name example1.tld, matching trademarks are found 894 for the domain name example2.tld in the "tmch", matching trademarks 895 are found for domain name example3.tld in the "tmch" and "custom- 896 tmch", for the "claims" launch phase: 898 S: 899 S: 900 S: 901 S: 902 S: Command completed successfully 903 S: 904 S: 905 S: 907 S: 908 S: example1.tld 909 S: 910 S: 911 S: example2.tld 912 S: 913 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 914 S: 915 S: 916 S: 917 S: example3.tld 918 S: 919 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 920 S: 921 S: 922 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 923 S: 924 S: 925 S: 926 S: 927 S: 928 S: ABC-12345 929 S: 54321-XYZ 930 S: 931 S: 932 S: 934 3.2. EPP Command 936 This extension defines additional elements to extend the EPP 937 command and response to be used in conjunction with the EPP domain 938 name mapping [RFC5731]. 940 The EPP command is used to retrieve information for a launch 941 phase registration or application. The Application Identifier 942 (Section 2.1) returned in the element of the create 943 response (Section 3.3) is used for retrieving information for a 944 Launch Application. A element is sent along with the 945 regular domain command. The element includes an 946 OPTIONAL "includeMark" boolean attribute, with a default value of 947 "false", to indicate whether or not to include the mark in the 948 response. The element contains the following child 949 elements: 951 The phase during which the application or 952 registration was submitted or is associated with. Server policy 953 defines the phases that are supported. 954 OPTIONAL application identifier of the Launch 955 Application. 957 Example domain command with the extension to 958 retrieve information for the sunrise application for example.tld and 959 application identifier "abc123": 961 C: 962 C: 963 C: 964 C: 965 C: 967 C: example.tld 968 C: 969 C: 970 C: 971 C: 974 C: sunrise 975 C: abc123 976 C: 977 C: 978 C: ABC-12345 979 C: 980 C: 981 Example domain command with the extension to 982 retrieve information for the sunrise registration for example.tld: 984 C: 985 C: 986 C: 987 C: 988 C: 990 C: example.tld 991 C: 992 C: 993 C: 994 C: 996 C: sunrise 997 C: 998 C: 999 C: ABC-12345 1000 C: 1001 C: 1003 If the query was successful, the server replies with a 1004 element along with the regular EPP . The 1005 contains the following child elements: 1007 The phase during which the application was submitted, 1008 or is associated with, that matches the associated command 1009 . 1010 OPTIONAL Application Identifier of the Launch 1011 Application. 1012 OPTIONAL status of the Launch Application using one 1013 of the supported status values (Section 2.4). 1014 Zero or more (Section 2.6.2) elements. 1016 Example domain response using the extension 1017 with the mark information: 1019 S: 1020 S: 1021 S: 1022 S: 1023 S: Command completed successfully 1024 S: 1025 S: 1026 S: 1028 S: example.tld 1029 S: EXAMPLE1-REP 1030 S: 1031 S: jd1234 1032 S: sh8013 1033 S: sh8013 1034 S: ClientX 1035 S: ClientY 1036 S: 2012-04-03T22:00:00.0Z 1037 S: 1038 S: 2fooBAR 1039 S: 1040 S: 1041 S: 1042 S: 1043 S: 1045 S: sunrise 1046 S: abc123 1047 S: 1048 S: 1050 S: ... 1051 S: 1052 S: 1053 S: 1054 S: 1055 S: ABC-12345 1056 S: 54321-XYZ 1057 S: 1058 S: 1059 S: 1061 3.3. EPP Command 1063 There are four forms of the extension to the EPP command 1064 that include the Sunrise Create Form (Section 3.3.1), the Claims 1065 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 1066 and the Mixed Create Form (Section 3.3.4). The form is dependent on 1067 the supported launch phases (Section 2.3) as defined below. 1069 sunrise The EPP command with the "sunrise" launch phase is 1070 used to submit a registration with trademark information that can 1071 be verified by the server with the value. The 1072 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 1073 launch phase. 1074 landrush The EPP command with the "landrush" launch phase 1075 MAY use the General Create Form (Section 3.3.3) to explicitly 1076 specify the phase and optionally define the expected type of 1077 object to create. 1078 claims The EPP command with the "claims" launch phase is 1079 used to pass the information associated with the presentation and 1080 acceptance of the Claims Notice. The Claims Create Form 1081 (Section 3.3.2) is used and the General Create Form 1082 (Section 3.3.3) MAY be used for the "claims" launch phase. 1083 open The EPP command with the "open" launch phase is 1084 undefined but the form supported is up to server policy. Use of 1085 the Claims Create Form (Section 3.3.2) MAY be used to pass the 1086 information associated with the presentation and acceptance of the 1087 Claims Notice if required for the domain name. 1088 custom The EPP command with the "custom" launch phase is 1089 undefined but the form supported is up to server policy. 1091 3.3.1. Sunrise Create Form 1093 The Sunrise Create Form of the extension to the EPP domain name 1094 mapping [RFC5731] includes the verifiable trademark information that 1095 the server uses to match against the domain name to authorize the 1096 domain create. A server MUST support one of four models in Claim 1097 Validation Models (Section 2.6) to verify the trademark information 1098 passed by the client. 1100 A element is sent along with the regular 1101 domain command. The element has an OPTIONAL "type" 1102 attribute that defines the expected type of object ("application" or 1103 "registration") to create. The server SHOULD validate the "type" 1104 attribute, when passed, against the type of object that will be 1105 created. The element contains the following child 1106 elements: 1108 The identifier for the launch phase. 1110 or or 1112 Zero or more elements. The 1113 child elements are defined in the 1114 element (Section 2.6.1) section. 1115 Zero or more elements. The 1116 child elements are defined in the 1117 element (Section 2.6.3.1) section. 1118 Zero or more 1119 elements. The child elements are 1120 defined in the element 1121 (Section 2.6.3.2) section. 1123 The following is an example domain command using the 1124 extension, following the "code" validation model, 1125 with multiple sunrise codes: 1127 C: 1128 C: 1129 C: 1130 C: 1131 C: 1133 C: example.tld 1134 C: jd1234 1135 C: sh8013 1136 C: sh8013 1137 C: 1138 C: 2fooBAR 1139 C: 1140 C: 1141 C: 1142 C: 1143 C: 1145 C: sunrise 1146 C: 1147 C: 1148 C: 49FD46E6C4B45C55D4AC 1149 C: 1150 C: 1151 C: 49FD46E6C4B45C55D4AD 1152 C: 1153 C: 1154 C: 1155 C: 49FD46E6C4B45C55D4AE 1156 C: 1157 C: 1158 C: 1159 C: ABC-12345 1160 C: 1161 C: 1162 The following is an example domain command using the 1163 extension, following the "mark" validation model, 1164 with the mark information: 1166 C: 1167 C: 1168 C: 1169 C: 1170 C: 1172 C: exampleone.tld 1173 C: jd1234 1174 C: sh8013 1175 C: sh8013 1176 C: 1177 C: 2fooBAR 1178 C: 1179 C: 1180 C: 1181 C: 1182 C: 1184 C: sunrise 1185 C: 1186 C: 1188 C: ... 1189 C: 1190 C: 1191 C: 1192 C: 1193 C: ABC-12345 1194 C: 1195 C: 1196 The following is an example domain command using the 1197 extension, following the "code with mark" validation 1198 model, with a code and mark information: 1200 C: 1201 C: 1202 C: 1203 C: 1204 C: 1206 C: example.tld 1207 C: jd1234 1208 C: sh8013 1209 C: sh8013 1210 C: 1211 C: 2fooBAR 1212 C: 1213 C: 1214 C: 1215 C: 1216 C: 1218 C: sunrise 1219 C: 1220 C: 1221 C: 49FD46E6C4B45C55D4AC 1222 C: 1224 C: ... 1225 C: 1226 C: 1227 C: 1228 C: 1229 C: ABC-12345 1230 C: 1231 C: 1232 The following is an example domain command using the 1233 extension, following the "signed mark" validation 1234 model, with the signed mark information for a sunrise application: 1236 C: 1237 C: 1238 C: 1239 C: 1240 C: 1242 C: exampleone.tld 1243 C: jd1234 1244 C: sh8013 1245 C: sh8013 1246 C: 1247 C: 2fooBAR 1248 C: 1249 C: 1250 C: 1251 C: 1252 C: 1255 C: sunrise 1256 C: 1258 C: ... 1259 C: 1260 C: 1261 C: 1262 C: ABC-12345 1263 C: 1264 C: 1265 The following is an example domain command using the 1266 extension, following the "signed mark" validation 1267 model, with the base64 encoded signed mark information: 1269 C: 1270 C: 1271 C: 1272 C: 1273 C: 1275 C: exampleone.tld 1276 C: jd1234 1277 C: sh8013 1278 C: sh8013 1279 C: 1280 C: 2fooBAR 1281 C: 1282 C: 1283 C: 1284 C: 1285 C: 1287 C: sunrise 1288 C: 1290 C: ... 1291 C: 1292 C: 1293 C: 1294 C: ABC-12345 1295 C: 1296 C: 1298 3.3.2. Claims Create Form 1300 The Claims Create Form of the extension to the EPP domain name 1301 mapping [RFC5731] includes the information related to the 1302 registrant's acceptance of the Claims Notice. 1304 A element is sent along with the regular 1305 domain command. The element has an OPTIONAL "type" 1306 attribute that defines the expected type of object ("application" or 1307 "registration") to create. The server SHOULD validate the "type" 1308 attribute, when passed, against the type of object that will be 1309 created. The element contains the following child 1310 elements: 1312 Contains the value of the active launch phase of the 1313 server. The server SHOULD validate the value against the active 1314 server launch phase. 1315 One or more elements that contain 1316 the following child elements: 1318 Unique notice identifier for the Claims 1319 Notice. The element has an OPTIONAL 1320 "validatorID" attribute is the Validator Identifier 1321 (Section 2.2) whose value indicates which Trademark Validator 1322 is the source of the claims notice, with the default being 1323 the ICANN TMCH. 1324 Expiry of the claims notice. 1325 Contains the date and time that the claims 1326 notice was accepted. 1328 The following is an example domain command using the 1329 extension with the information for 1330 the "tmch" and the "custom-tmch" validators, for the "claims" launch 1331 phase: 1333 C: 1334 C: 1335 C: 1336 C: 1337 C: 1339 C: example.tld 1340 C: jd1234 1341 C: sh8013 1342 C: sh8013 1343 C: 1344 C: 2fooBAR 1345 C: 1346 C: 1347 C: 1348 C: 1349 C: 1351 C: claims 1352 C: 1353 C: 1354 C: 370d0b7c9223372036854775807 1355 C: 2014-06-19T10:00:00.0Z 1356 C: 1357 C: 2014-06-19T09:00:00.0Z 1358 C: 1359 C: 1360 C: 1361 C: 1362 C: 470d0b7c9223654313275808 1363 C: 2014-06-19T10:00:00.0Z 1364 C: 1365 C: 2014-06-19T09:00:30.0Z 1366 C: 1367 C: 1368 C: 1369 C: 1370 C: ABC-12345 1371 C: 1372 C: 1374 3.3.3. General Create Form 1376 The General Create Form of the extension to the EPP domain name 1377 mapping [RFC5731] includes the launch phase and optionally the object 1378 type to create. The OPTIONAL "type" attribute defines the expected 1379 type of object ("application" or "registration") to create. The 1380 server SHOULD validate the "type" attribute, when passed, against the 1381 type of object that will be created. 1383 A element is sent along with the regular 1384 domain command. The element contains the following 1385 child elements: 1387 Contains the value of the active launch phase of the 1388 server. The server SHOULD validate the value against the active 1389 server launch phase. 1391 The following is an example domain command using the 1392 extension for a "landrush" launch phase application: 1394 C: 1395 C: 1396 C: 1397 C: 1398 C: 1400 C: example.tld 1401 C: jd1234 1402 C: sh8013 1403 C: sh8013 1404 C: 1405 C: 2fooBAR 1406 C: 1407 C: 1408 C: 1409 C: 1410 C: 1413 C: landrush 1414 C: 1415 C: 1416 C: ABC-12345 1417 C: 1418 C: 1420 3.3.4. Mixed Create Form 1422 The Mixed Create Form supports a mix of the create forms, where for 1423 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1424 Form (Section 3.3.2) MAY be supported in a single command by 1425 including both the verified trademark information and the information 1426 related to the registrant's acceptance of the Claims Notice. The 1427 server MAY support the Mixed Create Form. The "custom" launch phase 1428 SHOULD be used when using the Mixed Create Form. 1430 The following is an example domain command using the 1431 extension, with using a mix of the Sunrise Create 1432 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1433 including both a mark and a notice: 1435 C: 1436 C: 1437 C: 1438 C: 1439 C: 1441 C: exampleone.tld 1442 C: jd1234 1443 C: sh8013 1444 C: sh8013 1445 C: 1446 C: 2fooBAR 1447 C: 1448 C: 1449 C: 1450 C: 1451 C: 1454 C: custom 1455 C: 1456 C: 1458 C: ... 1459 C: 1460 C: 1461 C: 1462 C: 1463 C: 49FD46E6C4B45C55D4AC 1464 C: 1465 C: 2012-06-19T10:00:10.0Z 1466 C: 1467 C: 2012-06-19T09:01:30.0Z 1468 C: 1469 C: 1470 C: 1471 C: 1472 C: ABC-12345 1473 C: 1474 C: 1476 3.3.5. Create Response 1478 If the create was successful, the server MAY reply with the 1479 element along with the regular EPP to 1480 indicate the server generated Application Identifier (Section 2.1), 1481 when multiple applications of a given domain name are supported; 1482 otherwise no extension is included with the regular EPP . 1483 The element contains the following child elements: 1485 The phase of the application that mirrors the 1486 element included in the . 1487 The application identifier of the 1488 application. 1490 An example response when multiple overlapping applications are 1491 supported by the server: 1493 S: 1494 S: 1495 S: 1496 S: 1497 S: Command completed successfully; action pending 1498 S: 1499 S: 1500 S: 1502 S: example.tld 1503 S: 2010-08-10T15:38:26.623854Z 1504 S: 1505 S: 1506 S: 1507 S: 1509 S: sunrise 1510 S: 2393-9323-E08C-03B1 1511 S: 1512 S: 1513 S: 1514 S: 1515 S: ABC-12345 1516 S: 54321-XYZ 1517 S: 1518 S: 1519 S: 1521 3.4. EPP Command 1523 This extension defines additional elements to extend the EPP 1524 command to be used in conjunction with the domain name mapping. 1526 A client MUST NOT pass the extension on an EPP command to a 1527 server that does not support launch applications. A server that does 1528 not support launch applications during its launch phase MUST return 1529 an EPP error result code of 2102 when receiving an EPP 1530 command with the extension. 1532 Registry policies permitting, clients may update an application 1533 object by submitting an EPP command along with a 1534 element to indicate the application object to be 1535 updated. The element contains the following child 1536 elements: 1538 The phase during which the application was submitted 1539 or is associated with. 1540 The application identifier for which the 1541 client wishes to update. 1543 The following is an example domain command with the 1544 extension to add and remove a name server of a 1545 sunrise application with the application identifier "abc123": 1547 C: 1548 C: 1549 C: 1550 C: 1551 C: 1553 C: example.tld 1554 C: 1555 C: 1556 C: ns2.example.tld 1557 C: 1558 C: 1559 C: 1560 C: 1561 C: ns1.example.tld 1562 C: 1563 C: 1564 C: 1565 C: 1566 C: 1567 C: 1569 C: sunrise 1570 C: abc123 1571 C: 1572 C: 1573 C: ABC-12345 1574 C: 1575 C: 1577 This extension does not define any extension to the response of an 1578 domain command. After processing the command, the server 1579 replies with a standard EPP response as defined in the EPP domain 1580 name mapping [RFC5731]. 1582 3.5. EPP Command 1584 This extension defines additional elements to extend the EPP 1585 command to be used in conjunction with the domain name mapping. 1587 A client MUST NOT pass the extension on an EPP command to a 1588 server that does not support launch applications. A server that does 1589 not support launch applications during its launch phase MUST return 1590 an EPP error result code of 2102 when receiving an EPP 1591 command with the extension. 1593 Registry policies permitting, clients MAY withdraw an application by 1594 submitting an EPP command along with a 1595 element to indicate the application object to be deleted. The 1596 element contains the following child elements: 1598 The phase during which the application was submitted 1599 or is associated with. 1600 The application identifier for which the 1601 client wishes to delete. 1603 The following is an example domain command with the 1604 extension: 1606 C: 1607 C: 1608 C: 1609 C: 1610 C: 1612 C: example.tld 1613 C: 1614 C: 1615 C: 1616 C: 1618 C: sunrise 1619 C: abc123 1620 C: 1621 C: 1622 C: ABC-12345 1623 C: 1624 C: 1626 This extension does not define any extension to the response of a 1627 domain command. After processing the command, the server 1628 replies with a standard EPP response as defined in the EPP domain 1629 name mapping [RFC5731]. 1631 3.6. EPP Command 1633 This extension does not define any extension to the EPP 1634 command or response described in the EPP domain name mapping 1635 [RFC5731]. 1637 3.7. EPP Command 1639 This extension does not define any extension to the EPP 1640 command or response described in the EPP domain name mapping 1641 [RFC5731]. 1643 4. Formal Syntax 1645 One schema is presented here that is the EPP Launch Phase Mapping 1646 schema. 1648 The formal syntax presented here is a complete schema representation 1649 of the object mapping suitable for automated validation of EPP XML 1650 instances. The BEGIN and END tags are not part of the schema; they 1651 are used to note the beginning and ending of the schema for URI 1652 registration purposes. 1654 4.1. Launch Schema 1656 Copyright (c) 2012 IETF Trust and the persons identified as authors 1657 of the code. All rights reserved. 1659 Redistribution and use in source and binary forms, with or without 1660 modification, are permitted provided that the following conditions 1661 are met: 1663 o Redistributions of source code must retain the above copyright 1664 notice, this list of conditions and the following disclaimer. 1665 o Redistributions in binary form must reproduce the above copyright 1666 notice, this list of conditions and the following disclaimer in 1667 the documentation and/or other materials provided with the 1668 distribution. 1669 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1670 names of specific contributors, may be used to endorse or promote 1671 products derived from this software without specific prior written 1672 permission. 1674 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1675 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1676 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1677 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1678 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1679 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1680 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1681 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1682 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1683 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1684 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1686 BEGIN 1687 1688 1697 1700 1701 1702 1704 1705 1706 Extensible Provisioning Protocol v1.0 1707 domain name extension schema 1708 for the launch phase processing. 1709 1710 1712 1715 1716 1717 1718 1719 1721 1724 1725 1726 1728 1730 1731 1733 1736 1737 1738 1740 1746 1747 1748 1749 1750 1751 1752 1754 1757 1758 1759 1760 1761 1762 1763 1764 1765 1767 1770 1771 1772 1773 1774 1776 1777 1778 1779 1782 1783 1784 1786 1789 1790 1791 1792 1793 1795 1796 1797 1798 1800 1801 1802 1804 1807 1808 1809 1810 1811 1813 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1828 1831 1832 1833 1834 1836 1838 1839 1840 1841 1843 1847 1848 1849 1851 1853 1854 1856 1859 1860 1861 1862 1863 1865 1867 1869 1870 1873 1874 1875 1877 1880 1881 1882 1883 1884 1885 1887 1890 1891 1892 1893 1894 1895 1896 1898 1901 1902 1903 1905 1906 1908 1910 1914 1915 1916 1917 1918 1919 1920 1921 1924 1925 1926 1927 1930 1931 1933 1935 1938 1939 1940 1942 1945 1946 1947 1949 1951 1952 1954 1955 1956 1957 1959 1960 1962 1963 1964 1965 1967 1968 1970 1972 1973 1974 1975 1977 1978 1979 1981 1984 1985 1986 1987 1990 1992 1994 1995 1997 1998 END 2000 5. IANA Considerations 2002 5.1. XML Namespace 2004 This document uses URNs to describe XML namespaces and XML schemas 2005 conforming to a registry mechanism described in [RFC3688]. The 2006 following URI assignment is requested of IANA: 2008 URI: urn:ietf:params:xml:ns:launch-1.0 2010 Registrant Contact: See the "Author's Address" section of this 2011 document. 2013 XML: See the "Formal Syntax" section of this document. 2015 5.2. EPP Extension Registry 2017 The EPP extension described in this document should be registered by 2018 the IANA in the EPP Extension Registry described in [RFC7451]. The 2019 details of the registration are as follows: 2021 Name of Extension: "Launch Phase Mapping for the Extensible 2022 Provisioning Protocol (EPP)" 2024 Document status: Standards Track 2026 Reference: (insert reference to RFC version of this document) 2028 Registrant Name and Email Address: IESG, 2030 TLDs: Any 2032 IPR Disclosure: None 2034 Status: Active 2036 Notes: None 2038 6. Implementation Status 2040 Note to RFC Editor: Please remove this section and the reference to 2041 RFC 6982 [RFC6982] before publication. 2043 This section records the status of known implementations of the 2044 protocol defined by this specification at the time of posting of this 2045 Internet-Draft, and is based on a proposal described in RFC 6982 2046 [RFC6982]. The description of implementations in this section is 2047 intended to assist the IETF in its decision processes in progressing 2048 drafts to RFCs. Please note that the listing of any individual 2049 implementation here does not imply endorsement by the IETF. 2050 Furthermore, no effort has been spent to verify the information 2051 presented here that was supplied by IETF contributors. This is not 2052 intended as, and must not be construed to be, a catalog of available 2053 implementations or their features. Readers are advised to note that 2054 other implementations may exist. 2056 According to RFC 6982 [RFC6982], "this will allow reviewers and 2057 working groups to assign due consideration to documents that have the 2058 benefit of running code, which may serve as evidence of valuable 2059 experimentation and feedback that have made the implemented protocols 2060 more mature. It is up to the individual working groups to use this 2061 information as they see fit". 2063 6.1. Verisign EPP SDK 2065 Organization: Verisign Inc. 2067 Name: Verisign EPP SDK 2069 Description: The Verisign EPP SDK includes both a full client 2070 implementation and a full server stub implementation of draft-ietf- 2071 eppext-launchphase. 2073 Level of maturity: Production 2075 Coverage: All aspects of the protocol are implemented. 2077 Licensing: GNU Lesser General Public License 2079 Contact: jgould@verisign.com 2081 URL: http://www.verisigninc.com/en_US/channel-resources/domain- 2082 registry-products/epp-sdks 2084 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 2086 Organization: Verisign Inc. 2088 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 2089 System (SRS) 2091 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 2092 Registry System (SRS) implements the server-side of draft-ietf- 2093 eppext-launchphase for a variety of Top Level Domains (TLD's). 2095 Level of maturity: Production 2097 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2098 Form for the EPP Command, the Sunrise and Claims Forms for 2099 the EPP Command of Launch Registrations and Launch 2100 Applications. For Launch Applications the Poll Messaging, the EPP 2101 Command, the EPP Command, and the EPP 2102 Command is covered. 2104 Licensing: Proprietary 2106 Contact: jgould@verisign.com 2108 6.3. Verisign .COM / .NET SRS 2110 Organization: Verisign Inc. 2112 Name: Verisign .COM / .NET Shared Registry System (SRS) 2114 Description: The Verisign Shared Registry System (SRS) for .COM, .NET 2115 and other IDN TLD's implements the server-side of draft-ietf-eppext- 2116 launchphase. 2118 Level of maturity: Operational Test Environment (OTE) 2120 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2121 Form for the EPP Command, the Sunrise and Claims Forms for 2122 the EPP Command of Launch Registrations. 2124 Licensing: Proprietary 2126 Contact: jgould@verisign.com 2128 6.4. REngin v3.7 2130 Organization: Domain Name Services (Pty) Ltd 2132 Name: REngin v3.7 2134 Description: Server side implementation only 2136 Level of maturity: Production 2138 Coverage: All features from version 12 have been implemented 2140 Licensing: Proprietary Licensing with Maintenance Contracts 2142 Contact: info@dnservices.co.za 2144 URL: https://www.registry.net.za and soon http://dnservices.co.za 2146 6.5. RegistryEngine EPP Service 2148 Organization: CentralNic 2150 Name: RegistryEngine EPP Service 2152 Description: Generic high-volume EPP service for gTLDs, ccTLDs and 2153 SLDs 2154 Level of maturity: Deployed in CentralNic's production environment as 2155 well as two other gTLD registry systems, and two ccTLD registry 2156 systems. 2158 Coverage: Majority of elements including TMCH sunrise, landrush and 2159 TM claims as well as sunrise applications validated using codes. 2161 Licensing: Proprietary In-House software 2163 Contact: epp@centralnic.com 2165 URL: https://www.centralnic.com 2167 6.6. Neustar EPP SDK 2169 Organization: Neustar 2171 Name: Neustar EPP SDK 2173 Description: The Neustar EPP SDK includes client implementation of 2174 draft-ietf-eppext-launchphase in both Java and C++. 2176 Level of maturity: Production 2178 Coverage: All aspects of the protocol are implemented. 2180 Licensing: GNU Lesser General Public License 2182 Contact: trung.tran@neustar.biz 2184 7. Security Considerations 2186 The mapping extensions described in this document do not provide any 2187 security services beyond those described by EPP [RFC5730], the EPP 2188 domain name mapping [RFC5731], and protocol layers used by EPP. The 2189 security considerations described in these other specifications apply 2190 to this specification as well. 2192 Updates to, and deletion of an application object must be restricted 2193 to clients authorized to perform the said operation on the object. 2195 As information contained within an application, or even the mere fact 2196 that an application exists may be confidential. Any attempt to 2197 operate on an application object by an unauthorized client MUST be 2198 rejected with an EPP 2201 (authorization error) return code. Server 2199 policy may allow operation with filtered output by clients 2200 other than the sponsoring client, in which case the 2201 and response SHOULD be filtered to include only 2202 fields that are publicly accessible. 2204 8. Acknowledgements 2206 The authors wish to acknowledge the efforts of the leading 2207 participants of the Community TMCH Model that led to many of the 2208 changes to this document, which include Chris Wright, Jeff Neuman, 2209 Jeff Eckhaus, and Will Shorter. 2211 Special suggestions that have been incorporated into this document 2212 were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Michael 2213 Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus 2214 Malorny, Alexander Mayrhofer, Patrick Mevzek, James Mitchell, 2215 Francisco Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung 2216 Tran, Ulrich Wisser and Sharon Wodjenski. 2218 9. References 2220 9.1. Normative References 2222 [I-D.ietf-eppext-tmch-smd] 2223 Lozano, G., "Mark and Signed Mark Objects Mapping", draft- 2224 ietf-eppext-tmch-smd-01 (work in progress), February 2015. 2226 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2227 Requirement Levels", BCP 14, RFC 2119, March 1997. 2229 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2230 January 2004. 2232 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2233 STD 69, RFC 5730, August 2009. 2235 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2236 Domain Name Mapping", STD 69, RFC 5731, August 2009. 2238 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 2239 Code: The Implementation Status Section", RFC 6982, July 2240 2013. 2242 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 2243 Provisioning Protocol", RFC 7451, February 2015. 2245 9.2. URIs 2247 [1] http://tools.ietf.org/html/draft-lozano-tmch-func-spec 2249 [2] http://tools.ietf.org/html/draft-lozano-tmch-func-spec 2251 Appendix A. Change History 2253 A.1. Change from 00 to 01 2255 1. Changed to use camel case for the XML elements. 2256 2. Replaced "cancelled" status to "rejected" status. 2257 3. Added the child elements of the element. 2258 4. Removed the XML schema and replaced with "[TBD]". 2260 A.2. Change from 01 to 02 2262 1. Added support for both the ICANN and ARI/Neustar TMCH models. 2263 2. Changed the namespace URI and prefix to use "launch" instead of 2264 "launchphase". 2265 3. Added definition of multiple claim validation models. 2266 4. Added the and 2267 elements. 2268 5. Added support for Claims Info Command 2270 A.3. Change from 02 to 03 2272 1. Removed XSI namespace per Keith Gaughan's suggestion on the 2273 provreg list. 2274 2. Added extensibility to the launch:status element and added the 2275 pendingAuction status per Trung Tran's feedback on the provreg 2276 list. 2277 3. Added support for the Claims Check Command, updated the location 2278 and contents of the signedNotice, and replaced most references of 2279 Claim to Mark based on the work being done on the ARI/Neustar 2280 launch model. 2282 A.4. Change from 03 to 04 2284 1. Removed references to the ICANN model. 2285 2. Removed support for the Claims Info Command. 2286 3. Removed use of the signedClaim. 2287 4. Revised the method for referring to the signedClaim from the XML 2288 Signature using the IDREF URI. 2289 5. Split the launch-1.0.xsd into three XML schemas including launch- 2290 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 2291 6. Split the "claims" launch phase to the "claims1" and "claims2" 2292 launch phases. 2294 7. Added support for the encodedSignedMark with base64 encoded 2295 signedMark. 2296 8. Changed the elements in the createNoticeType to include the 2297 noticeID, timestamp, and the source elements. 2298 9. Added the class and effectiveDate elements to mark. 2300 A.5. Change from 04 to 05 2302 1. Removed reference to in the example. 2303 2. Incorporated feedback from Bernhard Reutner-Fischer on the 2304 provreg mail list. 2305 3. Added missing launch XML prefix to applicationIDType reference in 2306 the idContainerType of the Launch Schema. 2307 4. Added missing description of the element in the 2308 element. 2309 5. Updated note on replication of the EPP contact mapping elements 2310 in the Mark Contact section. 2312 A.6. Change from 05 to 06 2314 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 2315 replaced with reference to draft-lozano-smd, that contains the 2316 definition for the mark, signed marked, and encoded signed mark. 2317 2. Split the into and 2318 based on feedback from Trung Tran. 2319 3. Added the "includeMark" optional attribute to the 2320 element to enable the client to request whether or not to include 2321 the mark in the info response. 2322 4. Fixed state diagram to remove redundant transition from "invalid" 2323 to "rejected"; thanks Klaus Malorny. 2325 A.7. Change from 06 to 07 2327 1. Proof-read grammar and spelling. 2328 2. Changed "pendingAuction" status to "pendingAllocation", changed 2329 "pending" to "pendingValidation" status, per proposal from Trung 2330 Tran and seconded by Rubens Kuhl. 2331 3. Added text related to the use of RFC 5731 pendingCreate to the 2332 Application Identifier section. 2333 4. Added the Poll Messaging section to define the use of poll 2334 messaging for intermediate state transitions and pending action 2335 poll messaging for final state transitions. 2337 A.8. Change from 07 to 08 2339 1. Added support for use of the launch statuses and poll messaging 2340 for Launch Registrations based on feedback from Sharon Wodjenski 2341 and Trung Tran. 2343 2. Incorporated changes based on updates or clarifications in draft- 2344 lozano-tmch-func-spec-01, which include: 2346 1. Removed the unused element. 2347 2. Removed the element. 2348 3. Added the element based on the required 2349 element. 2351 A.9. Change from 08 to 09 2353 1. Made element optional in to allow 2354 passing just the in per request 2355 from Ben Levac. 2356 2. Added optional "type" attribute in to enable the 2357 client to explicitly define the desired type of object 2358 (application or registration) to create to all forms of the 2359 create extension. 2360 3. Added text that the server SHOULD validate the 2361 element in the Launch Phases section. 2362 4. Add the "General Create Form" to the create command extension to 2363 support the request from Ben Levac. 2364 5. Updated the text for the Poll Messaging section based on feedback 2365 from Klaus Malorny. 2366 6. Replaced the "claims1" and "claims2" phases with the "claims" 2367 phase based on discussion on the provreg list. 2368 7. Added support for a mixed create model (Sunrise Create Model and 2369 Claims Create Model), where a trademark (encoded signed mark, 2370 etc.) and notice can be passed, based on a request from James 2371 Mitchell. 2372 8. Added text for the handling of the overlapping "claims" and 2373 "landrush" launch phases. 2374 9. Added support for two check forms (claims check form and 2375 availability check form) based on a request from James Mitchell. 2376 The availability check form was based on the text in draft-rbp- 2377 application-epp-mapping. 2379 A.10. Change from 09 to 10 2381 1. Changed noticeIDType from base64Binary to token to be compatible 2382 with draft-lozano-tmch-func-spec-05. 2383 2. Changed codeType from base64Binary to token to be more generic. 2384 3. Updated based on feedback from Alexander Mayrhofer, which 2385 include: 2387 1. Changed "extension to the domain name extension" to 2388 "extension to the domain name mapping". 2389 2. Changed use of 2004 return code to 2306 return code when 2390 phase passed mismatches active phase and sub-phase. 2392 3. Changed description of "allocated" and "rejected" statuses. 2393 4. Moved sentence on a synchronous command 2394 without the use of an intermediate application, then an 2395 Application Identifier MAY not be needed to the Application 2396 Identifier section. 2397 5. Restructured the Mark Validation Models section to include 2398 the " element" sub-section, the 2399 " element" sub-section, and the Digital Signature 2400 sub-section. 2401 6. Changed "Registries may" to "Registries MAY". 2402 7. Changed "extensed" to "extended" in "Availability Check 2403 Form" section. 2404 8. Broke the mix of create forms in the "EPP Command" 2405 section to a fourth "Mixed Create Form" with its own sub- 2406 section. 2407 9. Removed "displayed or" from "displayed or accepted" in the 2408 description. 2409 10. Replaced "given domain name is supported" with "given domain 2410 name are supported" in the "Create Response" section. 2411 11. Changed the reference of 2303 (object does not exist) in the 2412 "Security Considerations" section to 2201 (authorization 2413 error). 2414 12. Added arrow from "invalid" status to "pendingValidation" 2415 status and "pendingAllocation" status to "rejected" status 2416 in the State Transition Diagram. 2417 4. Added the "C:" and "S:" example prefixes and related text in the 2418 "Conventions Used in This Document" section. 2420 A.11. Change from 10 to 11 2422 1. Moved the claims check response element under 2423 the element instead of the element based on 2424 the request from Francisco Obispo. 2426 A.12. Change from 11 to 12 2428 1. Added support for multiple validator identifiers for claims 2429 notices and marks based on a request and text provided by Mike 2430 O'Connell. 2431 2. Removed domain:exDate element from example in section 3.3.5 based 2432 on a request from Seth Goldman on the provreg list. 2433 3. Added clarifying text for clients not passing the launch 2434 extension on update and delete commands to servers that do not 2435 support launch applications based on a request from Sharon 2436 Wodjenski on the provreg list. 2438 A.13. Change from 12 to WG 00 2440 1. Changed to eppext working group draft by changing draft-tan-epp- 2441 launchphase to draft-ietf-eppext-launchphase and by changing 2442 references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch- 2443 smd. 2445 A.14. Change WG 00 to WG 01 2447 1. Removed text associated with support for the combining of status 2448 values based on feedback from Patrick Mevzek on the provreg 2449 mailing list, discussion on the eppext mailing list, and 2450 discussion at the eppext IETF meeting on March 6, 2014. 2452 A.15. Change WG 01 to WG 02 2454 1. Changed the element to be zero or more elements 2455 and the element to be one or more elements in the 2456 Claims Create Form. These changes were needed to be able to 2457 support more than one concurrent claims services. 2459 A.16. Change WG 02 to WG 03 2461 1. Added the "Implementation Status" section based on an action item 2462 from the eppext IETF-91 meeting. 2463 2. Moved Section 7 "IANA Considerations" and Section 9 "Security 2464 Considerations" before Section 5 "Acknowledgements". Moved 2465 "Change Log" Section to end. 2466 3. Updated the text for the Claims Check Form and the Claims Create 2467 Form to support checking for the need of the claims notice and 2468 passing the claims notice outside of the "claims" phase. 2469 4. Added the new Trademark Check Form to support determining whether 2470 or not a trademark exists that matches the domain name 2471 independent of whether a claims notice is required on create. 2472 This was based on a request from Trung Tran and a discussion on 2473 the eppext mailing list. 2475 A.17. Change WG 03 to WG 04 2477 1. Amended XML Namespace section of IANA Considerations, added EPP 2478 Extension Registry section. 2480 Authors' Addresses 2481 James Gould 2482 VeriSign, Inc. 2483 12061 Bluemont Way 2484 Reston, VA 20190 2485 US 2487 Email: jgould@verisign.com 2488 URI: http://www.verisigninc.com 2490 Wil Tan 2491 Cloud Registry 2492 Suite 32 Seabridge House 2493 377 Kent St 2494 Sydney, NSW 2000 2495 AU 2497 Phone: +61 414 710899 2498 Email: wil@cloudregistry.net 2499 URI: http://www.cloudregistry.net 2501 Gavin Brown 2502 CentralNic Ltd 2503 35-39 Mooregate 2504 London, England EC2R 6AR 2505 GB 2507 Phone: +44 20 33 88 0600 2508 Email: gavin.brown@centralnic.com 2509 URI: https://www.centralnic.com