idnits 2.17.1 draft-ietf-regext-launchphase-06.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 (August 21, 2017) is 2440 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) == Outdated reference: A later version (-15) exists of draft-ietf-regext-tmch-func-spec-03 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). 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: February 22, 2018 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 August 21, 2017 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-ietf-regext-launchphase-06 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 February 22, 2018. 37 Copyright Notice 39 Copyright (c) 2017 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.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 7 61 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9 62 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 10 63 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 11 64 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 14 65 2.6.1. element . . . . . . . . . . . . . . 15 66 2.6.2. element . . . . . . . . . . . . . . . . . 16 67 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16 68 2.6.3.1. element . . . . . . . . . . . . 16 69 2.6.3.2. element . . . . . . . . . 16 70 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 16 71 3.1. EPP Command . . . . . . . . . . . . . . . . . . . 17 72 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 17 73 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 20 74 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 22 75 3.2. EPP Command . . . . . . . . . . . . . . . . . . . 25 76 3.3. EPP Command . . . . . . . . . . . . . . . . . . 29 77 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 29 78 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 35 79 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 38 80 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 39 81 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 41 82 3.4. EPP Command . . . . . . . . . . . . . . . . . . 42 83 3.5. EPP Command . . . . . . . . . . . . . . . . . . 43 84 3.6. EPP Command . . . . . . . . . . . . . . . . . . . 44 85 3.7. EPP Command . . . . . . . . . . . . . . . . . 45 86 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 45 87 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 45 88 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 89 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 52 90 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 53 91 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 53 92 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 54 93 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 54 94 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 55 95 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 55 96 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 55 97 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 56 98 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 56 99 7. Security Considerations . . . . . . . . . . . . . . . . . . . 57 100 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57 101 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 58 102 9.1. Normative References . . . . . . . . . . . . . . . . . . 58 103 9.2. Informative References . . . . . . . . . . . . . . . . . 58 104 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 58 105 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 59 106 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 59 107 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 59 108 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 59 109 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 60 110 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 60 111 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 60 112 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 60 113 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 61 114 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 61 115 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 62 116 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 62 117 A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 62 118 A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 63 119 A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 63 120 A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 63 121 A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 63 122 A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 63 123 A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 63 124 A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 64 125 A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 64 126 A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 64 127 A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 64 128 A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 64 129 A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 64 130 A.26. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 65 131 A.27. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 65 132 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65 134 1. Introduction 136 This document describes an extension mapping for version 1.0 of the 137 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 138 specifies a flexible schema that can be used to implement several 139 common use cases related to the provisioning and management of domain 140 name registrations and applications during the launch of a domain 141 name registry. 143 It is typical for domain registries to operate in special modes 144 during their initial launch to facilitate allocation of domain names, 145 often according to special rules. This document uses the term 146 "launch phase" and the shorter form "launch" to refer to such a 147 period. 149 The EPP domain name mapping [RFC5731] is designed for the steady- 150 state operation of a registry. During a launch period, the model in 151 place may be different from what is defined in the EPP domain name 152 mapping [RFC5731]. For example, registries often accept multiple 153 applications for the same domain name during the "Sunrise" launch 154 phase, referred to as a Launch Application. A Launch Registration 155 refers to a registration made during a launch phase when the server 156 uses a "first-come, first-served" model. Even in a "first-come, 157 first-served" model, additional steps and information might be 158 required, such as trademark information. In addition, RFC 7848 159 [RFC7848] defines a registry interface for the Trademark Claims or 160 "claims" launch phase that includes support for presenting a 161 Trademark Claims Notice to the Registrant. This document proposes an 162 extension to the domain name mapping in order to provide a uniform 163 interface for the management of Launch Applications and Launch 164 Registrations in launch phases. 166 1.1. Conventions Used in This Document 168 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 169 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 170 document are to be interpreted as described in RFC 2119 [RFC2119]. 172 XML is case sensitive. Unless stated otherwise, XML specifications 173 and examples provided in this document MUST be interpreted in the 174 character case presented in order to develop a conforming 175 implementation. 177 In examples, "C:" represents lines sent by a protocol client and "S:" 178 represents lines returned by a protocol server. Indentation and 179 white space in examples are provided only to illustrate element 180 relationships and are not a REQUIRED feature of this protocol. 182 A Launch Registration is a domain name registration during a launch 183 phase when the server uses a "first-come, first-served" model. Only 184 a single registration for a domain name can exist in the server at a 185 time. 187 A Launch Application represents the intent to register a domain name 188 during a launch phase when the server accepts multiple applications 189 for a domain name and the server later selects one of the 190 applications to allocate as a registration. Many Launch Applications 191 for a domain name can exist in the server at a time. 193 "launch-1.0" is used as an abbreviation for 194 "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix 195 "launch" is used, but implementations MUST NOT depend on it and 196 instead employ a proper namespace-aware XML parser and serializer to 197 interpret and output the XML documents. 199 "signedMark-1.0" is used as an abbreviation for 200 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [RFC7848]. 201 The XML namespace prefix "smd" is used, but implementations MUST NOT 202 depend on it and instead employ a proper namespace-aware XML parser 203 and serializer to interpret and output the XML documents. 205 "mark-1.0" is used as an abbreviation for 206 "urn:ietf:params:xml:ns:mark-1.0" that is defined in [RFC7848]. The 207 XML namespace prefix "mark" is used, but implementations MUST NOT 208 depend on it and instead employ a proper namespace-aware XML parser 209 and serializer to interpret and output the XML documents. 211 2. Object Attributes 213 This extension adds additional elements to the EPP domain name 214 mapping [RFC5731]. Only those new elements are described here. 216 2.1. Application Identifier 218 Servers MAY allow multiple applications, referred to as a Launch 219 Application, of the same domain name during its launch phase 220 operations. Upon receiving a valid command to create 221 a Launch Application, the server MUST create an application object 222 corresponding to the request, assign an application identifier for 223 the Launch Application, set the [RFC5731] pendingCreate status, and 224 return the application identifier to the client with the 225 element. In order to facilitate correlation, 226 all subsequent launch operations on the Launch Application MUST be 227 qualified by the previously assigned application identifier using the 228 element. 230 2.2. Validator Identifier 232 The Validator Identifier is the identifier, that is unique to the 233 server, for a Trademark Validator that validates marks and has a 234 repository of validated marks. The OPTIONAL "validatorID" attribute 235 is used to define the Validator Identifier of the Trademark 236 Validator. Registries MAY support more than one Third Party 237 Trademark Validator. The unique set of Validator Identifier values 238 supported by the server is up to server policy. The Internet 239 Corporation for Assigned Names and Numbers (ICANN) Trademark 240 Clearinghouse (TMCH) is the default Trademark Validator and is 241 reserved the Validator Identifier of "tmch". If the ICANN TMCH is 242 not used or multiple Trademark Validators are used, the Validator 243 Identifier MUST be defined using the "validatorID" attribute. 245 The Validator Identifier MAY be related to one or more issuer 246 identifiers of the element and the element defined 247 in [RFC7848]. Both the Validator Identifier and the Issuer 248 Identifier used MUST be unique. If the ICANN TMCH is not used or 249 multiple Trademark Validators are used, the server MUST define the 250 list of supported validator identifiers and MUST make this 251 information available to clients using a mutually acceptable, out-of- 252 band mechanism. 254 The Validator Identifier MAY define a non-Trademark Validator that 255 supports a form of claims. 257 2.3. Launch Phases 259 The server MAY support multiple launch phases sequentially or 260 simultaneously. The element MUST be included by the 261 client to define the target launch phase of the command. The server 262 SHOULD validate the phase and MAY validate the sub-phase of the 263 element against the active phase and OPTIONAL sub- 264 phase of the server, and return an EPP error result code of 2306 if 265 there is a mismatch. 267 The following launch phase values are defined: 269 sunrise The phase during which trademark holders can submit 270 registrations or applications with trademark information that can 271 be validated by the server. 272 landrush A post-Sunrise phase when non-trademark holders are allowed 273 to register domain names with steps taken to address a large 274 volume of initial registrations. 275 claims The phase, as defined in the Section 2.3.1, in which a Claims 276 Notice MUST be displayed to a prospective registrant of a domain 277 name that matches trademarks. 278 open A post-launch phase that is also referred to as "steady state". 279 Servers MAY require additional trademark protection during this 280 phase. 281 custom A custom server launch phase that is defined using the "name" 282 attribute. 284 For extensibility, the element includes an OPTIONAL 285 "name" attribute that can define a sub-phase, or the full name of the 286 phase when the element has the "custom" value. For 287 example, the "claims" launch phase could have two sub-phases that 288 include "landrush" and "open". 290 Launch phases MAY overlap to support the "claims" launch phase, 291 defined in the Section 2.3.1, and to support a traditional "landrush" 292 launch phase. The overlap of the "claims" and "landrush" launch 293 phases SHOULD be handled by setting "claims" as the 294 value and setting "landrush" as the sub-phase with the "name" 295 attribute. For example, the element SHOULD be 296 claims. 298 2.3.1. Trademark Claims Phase 300 The Trademark Claims Phase is when a Claims Notice MUST be displayed 301 to a prospective registrant of a domain name that matches trademarks. 302 See [I-D.ietf-regext-tmch-func-spec] for additional details of 303 trademark claims handling. The source of the trademarks is a 304 Trademark Validator and the source of the Claims Notice information 305 is a Claim Notice Information Service (CNIS), which MAY be directly 306 linked to a Trademark Validator. The client interfaces with the 307 server to determine if a trademark exists for a domain name, 308 interfaces with a CNIS to get the Claims Notice information, and 309 interfaces with the server to pass the Claims Notice acceptance 310 information in a create command. This document supports the 311 Trademark Claims Phase in two ways including: 313 Claims Check Form Claims Check Form (Section 3.1.1) is used to 314 determine whether or not there are any matching trademarks for a 315 domain name. If there is at least one matching trademark that 316 exists for the domain name, a claims key is returned. The mapping 317 of domain names and the claims keys is based on an out-of-band 318 interface between the server and the Trademark Validator. The 319 CNIS associated with the claims key Validator Identifier 320 (Section 2.2) MUST accept the claims key as the basis for 321 retrieving the claims information. 322 Claims Create Form Claims Create Form (Section 3.3.2) is used to 323 pass the Claims Notice acceptance information in a create command. 324 The notice identifier () format, validation 325 rules, and server processing is up to the interface between the 326 server and the Trademark Validator. The CNIS associated with the 327 Validator Identifier (Section 2.2) MUST generate a notice 328 identifier compliant with the element. 330 The following shows the Trademark Claims Phase registration flow: 332 .------------. .--------. .--------. .------. 333 | Registrant | | Client | | Server | | CNIS | 334 '------------' '--------' '--------' '------' 335 | Request Domain | | | 336 | Registration | | | 337 |--------------->| Domain Check | | 338 | |--------------------------->| | 339 | Domain | Domain Unavailable .------------. | 340 | Unavailable |<---------------------( Available? ) | 341 |<---------------| No '------------' | 342 | | Domain Available | Yes | 343 | |<---------------------------| | 344 | | Domain Claims Check | | 345 | |--------------------------->| | 346 | | .---------. | 347 | | Claims Don't Exist / Does \ | 348 | |<--------------------( Domain have ) | 349 | | No \ Claims? / | 350 | | '---------' | 351 | | Domain Create | | Yes | 352 | |--------------------------->| | | 353 | Domain | Domain Registered | | | 354 | Registered |<---------------------------| | | 355 |<---------------| | | 356 | | | 357 | | Claims Exist with Claims Keys | | 358 | |<------------------------------' | 359 | | | 360 .-----. | | Request Claims Info with Claims Key | 361 |Abort| | Display |-------------------------------------->| 362 '-----' | Claims | Return Claims Info | 363 ^ | Notice |<--------------------------------------| 364 | No |<---------------| | 365 | .------. Yes | | 366 '-( Ack? )----------->| Domain Claims Create Form | | 367 '------' |--------------------------->| | 368 | Registration | Error .----------------------. | 369 | Error |<-----------( Validation Successful? ) | 370 |<---------------| No '----------------------' | 371 | | | Yes | 372 | Domain | Domain Registered | | 373 | Registered |<---------------------------| | 374 |<---------------| | | 376 Figure 1 378 2.4. Status Values 380 A Launch Application or Launch Registration object MAY have a launch 381 status value. The element is used to convey the 382 launch status pertaining to the object, beyond what is specified in 383 the object mapping. A Launch Application or Launch Registration MUST 384 set the [RFC5731] "pendingCreate" status if a launch status is 385 supported and the launch status is not one of the final statuses, 386 including the "allocated" and "rejected" statuses. 388 The following status values are defined using the required "s" 389 attribute: 391 pendingValidation: The initial state of a newly-created application 392 or registration object. The application or registration requires 393 validation, but the validation process has not yet completed. 394 validated: The application or registration meets relevant registry 395 rules. 396 invalid: The application or registration does not validate according 397 to registry rules. Server policies permitting, it may transition 398 back into "pendingValidation" for revalidation, after 399 modifications are made to ostensibly correct attributes that 400 caused the validation failure. 401 pendingAllocation: The allocation of the application or registration 402 is pending based on the results of some out-of-band process (for 403 example, an auction). 404 allocated: The object corresponding to the application or 405 registration has been provisioned. Is a possible end state of an 406 application or registration object. 407 rejected: The application or registration object was not 408 provisioned. Is a possible end state of an application or 409 registration object. 410 custom: A custom status that is defined using the "name" attribute. 412 Each status value MAY be accompanied by a string of human-readable 413 text that describes the rationale for the status applied to the 414 object. The OPTIONAL "lang" attribute MAY be present to identify the 415 language if the negotiated value is something other than the default 416 value of "en" (English). 418 For extensibility the element includes an OPTIONAL 419 "name" attribute that can define a sub-status or the full name of the 420 status when the status value is "custom". The server SHOULD NOT use 421 the "custom" status value. 423 Status values MAY be skipped. For example, an application or 424 registration MAY immediately start at the "allocated" status or an 425 application or registration MAY skip the "pendingAllocation" status. 427 If the launch phase does not require validation of a request, an 428 application or registration MAY immediately skip to 429 "pendingAllocation". 431 2.4.1. State Transition 433 | request 434 | 435 | +--------------------------+ 436 | | | 437 v v | 438 +-------------------+ | 439 | | | 440 | pendingValidation +--------------+ | 441 | | | | 442 +---------+---------+ | | 443 | | | 444 | | | 445 v v | 446 +-----------+ +---------+ | 447 | | | | | 448 | validated | | invalid +--+ 449 | | | | 450 +-----+-----+ +----+----+ 451 | | 452 | | 453 v | 454 +-------------------+ | 455 | | | 456 | pendingAllocation +-----------+ | 457 | | | | 458 +---------+---------+ | | 459 | | | 460 | | | 461 | | | 462 | | | 463 | | | 464 v v v 465 +---------+ +--------+ 466 / \ / \ 467 | allocated | | rejected | 468 \ / \ / 469 +---------+ +--------+ 471 Figure 2 473 2.5. Poll Messaging 475 A Launch Application MUST and a Launch Registration MAY be handled as 476 an EPP domain name object as specified in RFC 5731 [RFC5731] in 477 "pendingCreate" status, with the launch status values defined in 478 Section 2.4. As a Launch Application or Launch Registration 479 transitions between the status values defined in Section 2.4, the 480 server SHOULD insert poll messages, per [RFC5730], for the applicable 481 intermediate statuses, including the "pendingValidation", 482 "validated", "pendingAllocation, and "invalid" statuses, using the 483 element with the extension. The 484 element MAY contain non-mandatory information, like 485 contact and name server information. Also, further extensions that 486 would normally be included in the response of a 487 command, per [RFC5731], MAY be included. For the final statuses, 488 including the "allocated" and "rejected" statuses, the server MUST 489 insert a poll message, per [RFC5731], with the 490 extension. 492 The following is an example poll message for a Launch Application 493 that has transitioned to the "pendingAllocation" state. 495 S: 496 S: 497 S: 498 S: 499 S: Command completed successfully; ack to dequeue 500 S: 501 S: 502 S: 2013-04-04T22:01:00.0Z 503 S: Application pendingAllocation. 504 S: 505 S: 506 S: 508 S: domain.example 509 S: ... 510 S: 511 S: 512 S: 513 S: 515 S: sunrise 516 S: abc123 517 S: 518 S: 519 S: 520 S: 521 S: ABC-12345 522 S: 54322-XYZ 523 S: 524 S: 525 S: 526 The following is an example poll message for an 527 "allocated" Launch Application. 529 S: 530 S: 531 S: 532 S: 533 S: Command completed successfully; ack to dequeue 534 S: 535 S: 536 S: 2013-04-04T22:01:00.0Z 537 S: Application successfully allocated. 538 S: 539 S: 540 S: 542 S: domain.example 543 S: 544 S: ABC-12345 545 S: 54321-XYZ 546 S: 547 S: 2013-04-04T22:00:00.0Z 548 S: 549 S: 550 S: 551 S: 553 S: sunrise 554 S: abc123 555 S: 556 S: 557 S: 558 S: 559 S: BCD-23456 560 S: 65432-WXY 561 S: 562 S: 563 S: 564 The following is an example poll message for an 565 "allocated" Launch Registration. 567 S: 568 S: 569 S: 570 S: 571 S: Command completed successfully; ack to dequeue 572 S: 573 S: 574 S: 2013-04-04T22:01:00.0Z 575 S: Registration successfully allocated. 576 S: 577 S: 578 S: 580 S: domain.example 581 S: 582 S: ABC-12345 583 S: 54321-XYZ 584 S: 585 S: 2013-04-04T22:00:00.0Z 586 S: 587 S: 588 S: 589 S: 591 S: sunrise 592 S: 593 S: 594 S: 595 S: 596 S: BCD-23456 597 S: 65432-WXY 598 S: 599 S: 600 S: 602 2.6. Mark Validation Models 604 A server MUST support at least one of the following models for 605 validating trademark information: 607 code Use of a mark code by itself to validate that the mark matches 608 the domain name. This model is supported using the 609 element with just the element. 610 mark The mark information is passed without any other validation 611 element. The server will use some custom form of validation to 612 validate that the mark information is authentic. This model is 613 supported using the element with just the 614 (Section 2.6.2) element. 615 code with mark: A code is used along with the mark information by 616 the server to validate the mark utilizing an external party. The 617 code represents some form of secret that matches the mark 618 information passed. This model is supported using the 619 element that contains both the and 620 the (Section 2.6.2) elements. 621 signed mark: The mark information is digitally signed as described 622 in the Digital Signature (Section 2.6.3) section. The digital 623 signature can be directly validated by the server using the public 624 key of the external party that created the signed mark using its 625 private key. This model is supported using the 626 (Section 2.6.3.1) and (Section 2.6.3.2) 627 elements. 629 More than one , (Section 2.6.3.1), 630 or (Section 2.6.3.2) element MAY be 631 specified. The maximum number of marks per domain name is up to 632 server policy. 634 2.6.1. element 636 The element that is used by the "code", "mark", and 637 "code with mark" validation models, has the following child elements: 639 : OPTIONAL mark code used to validate the 640 (Section 2.6.2) information. The mark code is be a mark-specific 641 secret that the server can verify against a third party. The 642 OPTIONAL "validatorID" attribute is the Validator Identifier 643 (Section 2.2) whose value indicates which Trademark Validator that 644 the code originated from, with no default value. 645 : OPTIONAL mark information with child elements defined 646 in the Mark (Section 2.6.2) section. 648 The following is an example element with both a 649 and (Section 2.6.2) element. 651 652 653 49FD46E6C4B45C55D4AC 654 655 ... 656 657 659 2.6.2. element 661 A element describes an applicant's prior right to a given 662 domain name that is used with the "mark", "mark with code", and the 663 "signed mark" validation models. The element is defined 664 in [RFC7848]. A new mark format can be supported by creating a new 665 XML schema for the mark that has an element that substitutes for the 666 element from [RFC7848]. 668 2.6.3. Digital Signature 670 Digital signatures MAY be used by the server to validate either the 671 mark information, when using the "signed mark" validation model with 672 the (Section 2.6.3.1) element or the 673 (Section 2.6.3.2) element. 675 2.6.3.1. element 677 The element contains the digitally signed mark 678 information. The element is defined in [RFC7848]. 679 A new signed mark format can be supported by creating a new XML 680 schema for the signed mark that has an element that substitutes for 681 the element from [RFC7848]. 683 2.6.3.2. element 685 The element contains an encoded form of the 686 digitally signed (Section 2.6.3.1) element. The 687 element is defined in [RFC7848]. A new 688 encoded signed mark format can be supported by creating a new XML 689 schema for the encoded signed mark that has an element that 690 substitutes for the element from [RFC7848]. 692 3. EPP Command Mapping 694 A detailed description of the EPP syntax and semantics can be found 695 in the EPP core protocol specification [RFC5730]. The command 696 mappings described here are specifically for use in the Launch Phase 697 Extension. 699 This mapping is designed to be flexible, requiring only a minimum set 700 of required elements. 702 While it is meant to serve several use cases, it does not prescribe 703 any interpretation by the client or server. Such processing is 704 typically highly policy-dependent and therefore specific to 705 implementations. 707 Operations on application objects are done via one or more of the 708 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 709 Registries MAY choose to support a subset of the operations. 711 3.1. EPP Command 713 There are three forms of the extension to the EPP command: 714 the Claims Check Form (Section 3.1.1), the Availability Check Form 715 (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The 716 element "type" attribute defines the form, with the 717 value of "claims" for the Claims Check Form (Section 3.1.1), with the 718 value of "avail" for the Availability Check Form (Section 3.1.2), and 719 with the value of "trademark" for the Trademark Check Form 720 (Section 3.1.3). The default value of the "type" attribute is 721 "claims". The forms supported by the server is determined by server 722 policy. The server MUST return an EPP error result code of 2307 if 723 it receives a check form that is not supported. 725 3.1.1. Claims Check Form 727 The Claims Check Form defines a new command called the Claims Check 728 Command that is used to determine whether or not there are any 729 matching trademarks, in the specified launch phase, for each domain 730 name passed in the command, that requires the use of the "Claims 731 Create Form" on a Domain Create Command. The availability check 732 information defined in the EPP domain name mapping [RFC5731] MUST NOT 733 be returned for the Claims Check Command. This form is the default 734 form and MAY be explicitly identified by setting the 735 "type" attribute to "claims". 737 Instead of returning whether the domain name is available, the Claims 738 Check Command will return whether or not at least one matching 739 trademark exists for the domain name, that requires the use of the 740 "Claims Create Form" on a Domain Create Command. If there is at 741 least one matching trademark that exists for the domain name, a 742 element is returned. The client MAY then use the 743 value of the element to obtain information needed 744 to generate the Trademark Claims Notice from Trademark Validator 745 based on the Validator Identifier (Section 2.2). The unique notice 746 identifier of the Trademark Claims Notice MUST be passed in the 747 element of the extension to the Create Command 748 (Section 3.3). 750 The elements in the EPP command of EPP domain 751 name mapping [RFC5731] define the domain names to check for matching 752 trademarks. The element contains the following child 753 elements: 755 Contains the value of the active launch phase of the 756 server. The server SHOULD validate the value according to 757 Section 2.3. 759 Example Claims Check command using the domain command and the 760 extension with the "type" explicitly set to "claims", 761 to determine if "domain1.example", "domain2.example", and 762 "domain3.example" require claims notices during the "claims" launch 763 phase: 765 C: 766 C: 767 C: 768 C: 769 C: 771 C: domain1.example 772 C: domain2.example 773 C: domain3.example 774 C: 775 C: 776 C: 777 C: 780 C: claims 781 C: 782 C: 783 C: ABC-12345 784 C: 785 C: 787 If the command has been processed successfully, the EPP 788 MUST contain an element that 789 identifies the launch namespace. The element 790 contains the following child elements: 792 The phase that mirrors the element 793 included in the . 794 One or more elements that contain the 795 following child elements: 797 Contains the fully qualified name of the queried 798 domain name. This element MUST contain an "exists" attribute 799 whose value indicates if a matching trademark exists for the 800 domain name that requires the use of the "Claims Create Form" 801 on a Domain Create Command. A value of "1" (or "true") means 802 that a matching trademark does exist and that the "Claims 803 Create Form" is required on a Domain Create Command. A value 804 of "0" (or "false") means that a matching trademark does not 805 exist or that the "Claims Create Form" is NOT required on a 806 Domain Create Command. 807 Zero or more OPTIONAL claim keys that MAY be 808 passed to a third-party Trademark Validator such as the ICANN 809 Trademark Clearinghouse (TMCH) for querying the information 810 needed to generate a Trademark Claims Notice. The 811 is used as the key for the query in place 812 of the domain name to securely query the service without 813 using a well-known value like a domain name. The OPTIONAL 814 "validatorID" attribute is the Validator Identifier 815 (Section 2.2) whose value indicates which Trademark Validator 816 to query for the Claims Notice information, with the default 817 being the ICANN TMCH. The "validatorID" attribute MAY 818 reference a non-trademark claims clearinghouse identifer to 819 support other forms of claims notices. 821 Example Claims Check response when a claims notice is not required 822 for the domain name domain1.example, a claims notice is required for 823 the domain name domain2.example in the "tmch", and a claims notice is 824 required for the domain name domain3.example in the "tmch" and 825 "custom-tmch", for the "claims" launch phase: 827 S: 828 S: 829 S: 830 S: 831 S: Command completed successfully 832 S: 833 S: 834 S: 836 S: claims 837 S: 838 S: domain1.example 839 S: 840 S: 841 S: domain2.example 842 S: 843 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 844 S: 845 S: 846 S: 847 S: domain3.example 848 S: 849 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 850 S: 851 S: 852 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 853 S: 854 S: 855 S: 856 S: 857 S: 858 S: ABC-12345 859 S: 54321-XYZ 860 S: 861 S: 862 S: 864 3.1.2. Availability Check Form 866 The Availability Check Form defines additional elements to extend the 867 EPP command described in the EPP domain name mapping 868 [RFC5731]. No additional elements are defined for the EPP 869 response. This form MUST be identified by setting the 870 "type" attribute to "avail". 872 The EPP command is used to determine if an object can be 873 provisioned within a repository. Domain names may be made available 874 only in unique launch phases, whilst remaining unavailable for 875 concurrent launch phases. In addition to the elements expressed in 876 the , the command is extended with the 877 element that contains the following child elements: 879 The launch phase to which domain name availability 880 should be determined. The server SHOULD validate the value and 881 return an EPP error result code of 2306 if it is invalid. 883 Example Availability Check Form command using the domain 884 command and the extension with the "type" set to 885 "avail", to determine the availability of two domain names in the 886 "idn-release" custom launch phase: 888 C: 889 C: 890 C: 891 C: 892 C: 894 C: domain1.example 895 C: domain2.example 896 C: 897 C: 898 C: 899 C: 902 C: custom 903 C: 904 C: 905 C: ABC-12345 906 C: 907 C: 909 The Availability Check Form does not define any extension to the 910 response of an domain command. After processing the command, 911 the server replies with a standard EPP response as defined in the EPP 912 domain name mapping [RFC5731]. 914 3.1.3. Trademark Check Form 916 The Trademark Check Form defines a new command called the Trademark 917 Check Command that is used to determine whether or not there are any 918 matching trademarks for each domain name passed in the command, 919 independent of the active launch phase of the server and whether the 920 "Claims Create Form" is required on a Domain Create Command. The 921 availability check information defined in the EPP domain name mapping 922 [RFC5731] MUST NOT be returned for the Trademark Check Command. This 923 form MUST be identified by setting the "type" 924 attribute to "trademark". 926 Instead of returning whether the domain name is available, the 927 Trademark Check Command will return whether or not at least one 928 matching trademark exists for the domain name. If there is at least 929 one matching trademark that exists for the domain name, a 930 element is returned. The client MAY then use the 931 value of the element to obtain Trademark Claims 932 Notice information from Trademark Validator based on the Validator 933 Identifier (Section 2.2). 935 The elements in the EPP command of EPP domain 936 name mapping [RFC5731] define the domain names to check for matching 937 trademarks. The element does not contain any child 938 elements with the "Trademark Check Form": 940 Example Trademark Check command using the domain command and 941 the extension with the "type" set to "trademark", to 942 determine if "domain1.example", "domain2.example", and 943 "domain3.example" have any matching trademarks: 945 C: 946 C: 947 C: 948 C: 949 C: 951 C: domain1.example 952 C: domain2.example 953 C: domain3.example 954 C: 955 C: 956 C: 957 C: 960 C: 961 C: ABC-12345 962 C: 963 C: 965 If the command has been processed successfully, the EPP 966 MUST contain an element that 967 identifies the launch namespace. The element 968 contains the following child elements: 970 One or more elements that contain the 971 following child elements: 973 Contains the fully qualified name of the queried 974 domain name. This element MUST contain an "exists" attribute 975 whose value indicates if a matching trademark exists for the 976 domain name. A value of "1" (or "true") means that a 977 matching trademark does exist. A value of "0" (or "false") 978 means that a matching trademark does not exist. 979 Zero or more OPTIONAL claim keys that MAY be 980 passed to a third-party Trademark Validator such as the ICANN 981 Trademark Clearinghouse (TMCH) for querying the information 982 needed to generate a Trademark Claims Notice. The 983 is used as the key for the query in place 984 of the domain name to securely query the service without 985 using a well-known value like a domain name. The OPTIONAL 986 "validatorID" attribute is the Validator Identifier 987 (Section 2.2) whose value indicates which Trademark Validator 988 to query for the Claims Notice information, with the default 989 being the ICANN TMCH. The "validatorID" attribute MAY 990 reference a non-trademark claims clearinghouse identifer to 991 support other forms of claims notices. 993 Example Trademark Check response when no matching trademarks are 994 found for the domain name domain1.example, matching trademarks are 995 found for the domain name domain2.example in the "tmch", matching 996 trademarks are found for domain name domain3.example in the "tmch" 997 and "custom-tmch", for the "claims" launch phase: 999 S: 1000 S: 1001 S: 1002 S: 1003 S: Command completed successfully 1004 S: 1005 S: 1006 S: 1008 S: 1009 S: domain1.example 1010 S: 1011 S: 1012 S: domain2.example 1013 S: 1014 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 1015 S: 1016 S: 1017 S: 1018 S: domain3.example 1019 S: 1020 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 1021 S: 1022 S: 1023 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 1024 S: 1025 S: 1026 S: 1027 S: 1028 S: 1029 S: ABC-12345 1030 S: 54321-XYZ 1031 S: 1032 S: 1033 S: 1035 3.2. EPP Command 1037 This extension defines additional elements to extend the EPP 1038 command and response to be used in conjunction with the EPP domain 1039 name mapping [RFC5731]. 1041 The EPP command is used to retrieve information for a launch 1042 phase registration or application. The Application Identifier 1043 (Section 2.1) returned in the element of the create 1044 response (Section 3.3) can be used for retrieving information for a 1045 Launch Application. A element is sent along with the 1046 regular domain command. The element includes an 1047 OPTIONAL "includeMark" boolean attribute, with a default value of 1048 "false", to indicate whether or not to include the mark in the 1049 response. The element contains the following child 1050 elements: 1052 The phase during which the application or 1053 registration was submitted or is associated with. Server policy 1054 defines the phases that are supported. The server SHOULD 1055 validate the value and return an EPP error result code of 2306 if 1056 it is invalid. 1057 OPTIONAL application identifier of the Launch 1058 Application. 1060 Example domain command with the extension to 1061 retrieve information for the sunrise application for domain.example 1062 and application identifier "abc123": 1064 C: 1065 C: 1066 C: 1067 C: 1068 C: 1070 C: domain.example 1071 C: 1072 C: 1073 C: 1074 C: 1077 C: sunrise 1078 C: abc123 1079 C: 1080 C: 1081 C: ABC-12345 1082 C: 1083 C: 1085 Example domain command with the extension to 1086 retrieve information for the sunrise registration for domain.example: 1088 C: 1089 C: 1090 C: 1091 C: 1092 C: 1094 C: domain.example 1095 C: 1096 C: 1097 C: 1098 C: 1100 C: sunrise 1101 C: 1102 C: 1103 C: ABC-12345 1104 C: 1105 C: 1106 If the query was successful, the server replies with a 1107 element along with the regular EPP . The 1108 contains the following child elements: 1110 The phase during which the application was submitted, 1111 or is associated with, that matches the associated command 1112 . 1113 OPTIONAL Application Identifier of the Launch 1114 Application. 1115 OPTIONAL status of the Launch Application using one 1116 of the supported status values (Section 2.4). 1117 Zero or more (Section 2.6.2) elements only 1118 if the "includeMark" attribute is "true" in the command. 1120 Example domain response using the extension 1121 with the mark information: 1123 S: 1124 S: 1125 S: 1126 S: 1127 S: Command completed successfully 1128 S: 1129 S: 1130 S: 1132 S: domain.example 1133 S: EXAMPLE1-REP 1134 S: 1135 S: jd1234 1136 S: sh8013 1137 S: sh8013 1138 S: ClientX 1139 S: ClientY 1140 S: 2012-04-03T22:00:00.0Z 1141 S: 1142 S: 2fooBAR 1143 S: 1144 S: 1145 S: 1146 S: 1147 S: 1149 S: sunrise 1150 S: abc123 1151 S: 1152 S: 1154 S: ... 1155 S: 1156 S: 1157 S: 1158 S: 1159 S: ABC-12345 1160 S: 54321-XYZ 1161 S: 1162 S: 1163 S: 1165 3.3. EPP Command 1167 There are four forms of the extension to the EPP command 1168 that include the Sunrise Create Form (Section 3.3.1), the Claims 1169 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 1170 and the Mixed Create Form (Section 3.3.4). The form is dependent on 1171 the supported launch phases (Section 2.3) as defined below. 1173 sunrise The EPP command with the "sunrise" launch phase is 1174 used to submit a registration with trademark information that can 1175 be verified by the server with the value. The 1176 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 1177 launch phase. 1178 landrush The EPP command with the "landrush" launch phase 1179 MAY use the General Create Form (Section 3.3.3) to explicitly 1180 specify the phase and optionally define the expected type of 1181 object to create. 1182 claims The EPP command with the "claims" launch phase is 1183 used to pass the information associated with the presentation and 1184 acceptance of the Claims Notice. The Claims Create Form 1185 (Section 3.3.2) is used and the General Create Form 1186 (Section 3.3.3) MAY be used for the "claims" launch phase. 1187 open The EPP command with the "open" launch phase is 1188 undefined but the form supported is up to server policy. Use of 1189 the Claims Create Form (Section 3.3.2) MAY be used to pass the 1190 information associated with the presentation and acceptance of the 1191 Claims Notice if required for the domain name. 1192 custom The EPP command with the "custom" launch phase is 1193 undefined but the form supported is up to server policy. 1195 3.3.1. Sunrise Create Form 1197 The Sunrise Create Form of the extension to the EPP domain name 1198 mapping [RFC5731] includes the verifiable trademark information that 1199 the server uses to match against the domain name to authorize the 1200 domain create. A server MUST support one of four models in Claim 1201 Validation Models (Section 2.6) to verify the trademark information 1202 passed by the client. 1204 A element is sent along with the regular 1205 domain command. The element has an OPTIONAL "type" 1206 attribute that defines the expected type of object ("application" or 1207 "registration") to create. The server SHOULD validate the "type" 1208 attribute, when passed, against the type of object that will be 1209 created, and return an EPP error result code of 2306 if the type is 1210 incorrect. The element contains the following child 1211 elements: 1213 The identifier for the launch phase. The server 1214 SHOULD validate the value according to Section 2.3. 1215 or or 1217 Zero or more elements. The 1218 child elements are defined in the 1219 element (Section 2.6.1) section. 1220 Zero or more elements. The 1221 child elements are defined in the 1222 element (Section 2.6.3.1) section. 1223 Zero or more 1224 elements. The child elements are 1225 defined in the element 1226 (Section 2.6.3.2) section. 1228 The following is an example domain command using the 1229 extension, following the "code" validation model, 1230 with multiple sunrise codes: 1232 C: 1233 C: 1234 C: 1235 C: 1236 C: 1238 C: domain.example 1239 C: jd1234 1240 C: sh8013 1241 C: sh8013 1242 C: 1243 C: 2fooBAR 1244 C: 1245 C: 1246 C: 1247 C: 1248 C: 1250 C: sunrise 1251 C: 1252 C: 1253 C: 49FD46E6C4B45C55D4AC 1254 C: 1255 C: 1256 C: 49FD46E6C4B45C55D4AD 1257 C: 1258 C: 1259 C: 1260 C: 49FD46E6C4B45C55D4AE 1261 C: 1262 C: 1263 C: 1264 C: ABC-12345 1265 C: 1266 C: 1267 The following is an example domain command using the 1268 extension, following the "mark" validation model, 1269 with the mark information: 1271 C: 1272 C: 1273 C: 1274 C: 1275 C: 1277 C: domainone.example 1278 C: jd1234 1279 C: sh8013 1280 C: sh8013 1281 C: 1282 C: 2fooBAR 1283 C: 1284 C: 1285 C: 1286 C: 1287 C: 1289 C: sunrise 1290 C: 1291 C: 1293 C: ... 1294 C: 1295 C: 1296 C: 1297 C: 1298 C: ABC-12345 1299 C: 1300 C: 1301 The following is an example domain command using the 1302 extension, following the "code with mark" validation 1303 model, with a code and mark information: 1305 C: 1306 C: 1307 C: 1308 C: 1309 C: 1311 C: domain.example 1312 C: jd1234 1313 C: sh8013 1314 C: sh8013 1315 C: 1316 C: 2fooBAR 1317 C: 1318 C: 1319 C: 1320 C: 1321 C: 1323 C: sunrise 1324 C: 1325 C: 1326 C: 49FD46E6C4B45C55D4AC 1327 C: 1329 C: ... 1330 C: 1331 C: 1332 C: 1333 C: 1334 C: ABC-12345 1335 C: 1336 C: 1337 The following is an example domain command using the 1338 extension, following the "signed mark" validation 1339 model, with the signed mark information for a sunrise application: 1341 C: 1342 C: 1343 C: 1344 C: 1345 C: 1347 C: domainone.example 1348 C: jd1234 1349 C: sh8013 1350 C: sh8013 1351 C: 1352 C: 2fooBAR 1353 C: 1354 C: 1355 C: 1356 C: 1357 C: 1360 C: sunrise 1361 C: 1363 C: ... 1364 C: 1365 C: 1366 C: 1367 C: ABC-12345 1368 C: 1369 C: 1370 The following is an example domain command using the 1371 extension, following the "signed mark" validation 1372 model, with the base64 encoded signed mark information: 1374 C: 1375 C: 1376 C: 1377 C: 1378 C: 1380 C: domainone.example 1381 C: jd1234 1382 C: sh8013 1383 C: sh8013 1384 C: 1385 C: 2fooBAR 1386 C: 1387 C: 1388 C: 1389 C: 1390 C: 1392 C: sunrise 1393 C: 1395 C: ... 1396 C: 1397 C: 1398 C: 1399 C: ABC-12345 1400 C: 1401 C: 1403 3.3.2. Claims Create Form 1405 The Claims Create Form of the extension to the EPP domain name 1406 mapping [RFC5731] includes the information related to the 1407 registrant's acceptance of the Claims Notice. 1409 A element is sent along with the regular 1410 domain command. The element has an OPTIONAL "type" 1411 attribute that defines the expected type of object ("application" or 1412 "registration") to create. The server SHOULD validate the "type" 1413 attribute, when passed, against the type of object that will be 1414 created, and return an EPP error result code of 2306 if the type is 1415 incorrect. The element contains the following child 1416 elements: 1418 Contains the value of the active launch phase of the 1419 server. The server SHOULD validate the value according to 1420 Section 2.3. 1421 One or more elements that contain 1422 the following child elements: 1424 Unique notice identifier for the Claims 1425 Notice. The element has an OPTIONAL 1426 "validatorID" attribute is the Validator Identifier 1427 (Section 2.2) whose value indicates which Trademark Validator 1428 is the source of the claims notice, with the default being 1429 the ICANN TMCH. 1430 Expiry of the claims notice. 1431 Contains the date and time that the claims 1432 notice was accepted. 1434 The following is an example domain command using the 1435 extension with the information for 1436 the "tmch" and the "custom-tmch" validators, for the "claims" launch 1437 phase: 1439 C: 1440 C: 1441 C: 1442 C: 1443 C: 1445 C: domain.example 1446 C: jd1234 1447 C: sh8013 1448 C: sh8013 1449 C: 1450 C: 2fooBAR 1451 C: 1452 C: 1453 C: 1454 C: 1455 C: 1457 C: claims 1458 C: 1459 C: 1460 C: 370d0b7c9223372036854775807 1461 C: 2014-06-19T10:00:00.0Z 1462 C: 1463 C: 2014-06-19T09:00:00.0Z 1464 C: 1465 C: 1466 C: 1467 C: 1468 C: 470d0b7c9223654313275808 1469 C: 2014-06-19T10:00:00.0Z 1470 C: 1471 C: 2014-06-19T09:00:30.0Z 1472 C: 1473 C: 1474 C: 1475 C: 1476 C: ABC-12345 1477 C: 1478 C: 1480 3.3.3. General Create Form 1482 The General Create Form of the extension to the EPP domain name 1483 mapping [RFC5731] includes the launch phase and optionally the object 1484 type to create. The OPTIONAL "type" attribute defines the expected 1485 type of object ("application" or "registration") to create. The 1486 server SHOULD validate the "type" attribute, when passed, against the 1487 type of object that will be created, and return an EPP error result 1488 code of 2306 if the type is incorrect. 1490 A element is sent along with the regular 1491 domain command. The element contains the following 1492 child elements: 1494 Contains the value of the active launch phase of the 1495 server. The server SHOULD validate the value according to 1496 Section 2.3. 1498 The following is an example domain command using the 1499 extension for a "landrush" launch phase application: 1501 C: 1502 C: 1503 C: 1504 C: 1505 C: 1507 C: domain.example 1508 C: jd1234 1509 C: sh8013 1510 C: sh8013 1511 C: 1512 C: 2fooBAR 1513 C: 1514 C: 1515 C: 1516 C: 1517 C: 1520 C: landrush 1521 C: 1522 C: 1523 C: ABC-12345 1524 C: 1525 C: 1527 3.3.4. Mixed Create Form 1529 The Mixed Create Form supports a mix of the create forms, where for 1530 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1531 Form (Section 3.3.2) MAY be supported in a single command by 1532 including both the verified trademark information and the information 1533 related to the registrant's acceptance of the Claims Notice. The 1534 server MAY support the Mixed Create Form. The "custom" launch phase 1535 SHOULD be used when using the Mixed Create Form. 1537 The following is an example domain command using the 1538 extension, with using a mix of the Sunrise Create 1539 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1540 including both a mark and a notice: 1542 C: 1543 C: 1544 C: 1545 C: 1546 C: 1548 C: domainone.example 1549 C: jd1234 1550 C: sh8013 1551 C: sh8013 1552 C: 1553 C: 2fooBAR 1554 C: 1555 C: 1556 C: 1557 C: 1558 C: 1561 C: custom 1562 C: 1563 C: 1565 C: ... 1566 C: 1567 C: 1568 C: 1569 C: 1570 C: 49FD46E6C4B45C55D4AC 1571 C: 1572 C: 2012-06-19T10:00:10.0Z 1573 C: 1574 C: 2012-06-19T09:01:30.0Z 1575 C: 1576 C: 1577 C: 1578 C: 1579 C: ABC-12345 1580 C: 1581 C: 1583 3.3.5. Create Response 1585 If the create was successful, the server MAY add a 1586 element along to the regular EPP to indicate the server 1587 generated Application Identifier (Section 2.1), when multiple 1588 applications of a given domain name are supported; otherwise no 1589 extension is included with the regular EPP . The 1590 element contains the following child elements: 1592 The phase of the application that mirrors the 1593 element included in the . 1594 The application identifier of the 1595 application. 1597 An example response when multiple overlapping applications are 1598 supported by the server: 1600 S: 1601 S: 1602 S: 1603 S: 1604 S: Command completed successfully; action pending 1605 S: 1606 S: 1607 S: 1609 S: domain.example 1610 S: 2010-08-10T15:38:26.623854Z 1611 S: 1612 S: 1613 S: 1614 S: 1616 S: sunrise 1617 S: 2393-9323-E08C-03B1 1618 S: 1619 S: 1620 S: 1621 S: 1622 S: ABC-12345 1623 S: 54321-XYZ 1624 S: 1625 S: 1626 S: 1628 3.4. EPP Command 1630 This extension defines additional elements to extend the EPP 1631 command to be used in conjunction with the domain name mapping. 1633 A client MUST NOT pass the extension on an EPP command to a 1634 server that does not support launch applications. A server that does 1635 not support launch applications during its launch phase MUST return 1636 an EPP error result code of 2102 when receiving an EPP 1637 command with the extension. 1639 Registry policies permitting, clients may update an application 1640 object by submitting an EPP command along with a 1641 element to indicate the application object to be 1642 updated. The element contains the following child 1643 elements: 1645 The phase during which the application was submitted 1646 or is associated with. The server SHOULD validate the value and 1647 return an EPP error result code of 2306 if it is invalid. 1648 The application identifier for which the 1649 client wishes to update. 1651 The following is an example domain command with the 1652 extension to add and remove a name server of a 1653 sunrise application with the application identifier "abc123": 1655 C: 1656 C: 1657 C: 1658 C: 1659 C: 1661 C: domain.example 1662 C: 1663 C: 1664 C: ns2.domain.example 1665 C: 1666 C: 1667 C: 1668 C: 1669 C: ns1.domain.example 1670 C: 1671 C: 1672 C: 1673 C: 1674 C: 1675 C: 1677 C: sunrise 1678 C: abc123 1679 C: 1680 C: 1681 C: ABC-12345 1682 C: 1683 C: 1685 This extension does not define any extension to the response of an 1686 domain command. After processing the command, the server 1687 replies with a standard EPP response as defined in the EPP domain 1688 name mapping [RFC5731]. 1690 3.5. EPP Command 1692 This extension defines additional elements to extend the EPP 1693 command to be used in conjunction with the domain name mapping. 1695 A client MUST NOT pass the extension on an EPP command to a 1696 server that does not support launch applications. A server that does 1697 not support launch applications during its launch phase MUST return 1698 an EPP error result code of 2102 when receiving an EPP 1699 command with the extension. 1701 Registry policies permitting, clients MAY withdraw an application by 1702 submitting an EPP command along with a 1703 element to indicate the application object to be deleted. The 1704 element contains the following child elements: 1706 The phase during which the application was submitted 1707 or is associated with. The server SHOULD validate the value and 1708 return an EPP error result code of 2306 if it is invalid. 1709 The application identifier for which the 1710 client wishes to delete. 1712 The following is an example domain command with the 1713 extension: 1715 C: 1716 C: 1717 C: 1718 C: 1719 C: 1721 C: domain.example 1722 C: 1723 C: 1724 C: 1725 C: 1727 C: sunrise 1728 C: abc123 1729 C: 1730 C: 1731 C: ABC-12345 1732 C: 1733 C: 1735 This extension does not define any extension to the response of a 1736 domain command. After processing the command, the server 1737 replies with a standard EPP response as defined in the EPP domain 1738 name mapping [RFC5731]. 1740 3.6. EPP Command 1742 This extension does not define any extension to the EPP 1743 command or response described in the EPP domain name mapping 1744 [RFC5731]. 1746 3.7. EPP Command 1748 This extension does not define any extension to the EPP 1749 command or response described in the EPP domain name mapping 1750 [RFC5731]. 1752 4. Formal Syntax 1754 One schema is presented here that is the EPP Launch Phase Mapping 1755 schema. 1757 The formal syntax presented here is a complete schema representation 1758 of the object mapping suitable for automated validation of EPP XML 1759 instances. The BEGIN and END tags are not part of the schema; they 1760 are used to note the beginning and ending of the schema for URI 1761 registration purposes. 1763 4.1. Launch Schema 1765 Copyright (c) 2017 IETF Trust and the persons identified as authors 1766 of the code. All rights reserved. 1768 Redistribution and use in source and binary forms, with or without 1769 modification, are permitted provided that the following conditions 1770 are met: 1772 o Redistributions of source code must retain the above copyright 1773 notice, this list of conditions and the following disclaimer. 1774 o Redistributions in binary form must reproduce the above copyright 1775 notice, this list of conditions and the following disclaimer in 1776 the documentation and/or other materials provided with the 1777 distribution. 1778 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1779 names of specific contributors, may be used to endorse or promote 1780 products derived from this software without specific prior written 1781 permission. 1783 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1784 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1785 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1786 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1787 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1788 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1789 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1790 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1791 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1792 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1793 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1795 BEGIN 1796 1797 1806 1809 1810 1811 1813 1814 1815 Extensible Provisioning Protocol v1.0 1816 domain name extension schema 1817 for the launch phase processing. 1818 1819 1821 1824 1825 1826 1827 1828 1830 1833 1834 1835 1837 1839 1840 1842 1845 1846 1847 1849 1855 1856 1857 1858 1859 1860 1861 1863 1866 1867 1868 1869 1870 1871 1872 1873 1874 1876 1879 1880 1881 1882 1883 1885 1886 1887 1888 1891 1892 1893 1895 1898 1899 1900 1901 1902 1904 1905 1906 1907 1909 1910 1911 1913 1916 1917 1918 1919 1920 1922 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1937 1940 1941 1942 1943 1945 1947 1948 1949 1950 1952 1956 1957 1958 1960 1962 1963 1965 1968 1969 1970 1971 1972 1974 1976 1978 1979 1982 1983 1984 1986 1989 1990 1991 1992 1993 1994 1996 1999 2000 2001 2002 2003 2004 2005 2007 2010 2011 2012 2014 2015 2017 2019 2023 2024 2025 2026 2027 2028 2029 2030 2033 2034 2035 2036 2039 2040 2042 2044 2047 2048 2049 2051 2054 2055 2056 2058 2060 2061 2063 2064 2065 2066 2068 2069 2071 2072 2073 2074 2076 2077 2079 2081 2082 2083 2084 2086 2087 2088 2090 2093 2094 2095 2096 2099 2101 2103 2104 2106 2107 END 2109 5. IANA Considerations 2111 5.1. XML Namespace 2113 This document uses URNs to describe XML namespaces and XML schemas 2114 conforming to a registry mechanism described in [RFC3688]. 2116 Registration request for the launch namespace: 2118 URI: urn:ietf:params:xml:ns:launch-1.0 2119 Registrant Contact: IESG 2120 XML: None. Namespace URIs do not represent an XML specification. 2122 Registration request for the launch XML schema: 2124 URI: urn:ietf:params:xml:schema:launch-1.0 2125 Registrant Contact: IESG 2126 XML: See the "Formal Syntax" section of this document. 2128 5.2. EPP Extension Registry 2130 The EPP extension described in this document should be registered by 2131 the IANA in the EPP Extension Registry described in [RFC7451]. The 2132 details of the registration are as follows: 2134 Name of Extension: "Launch Phase Mapping for the Extensible 2135 Provisioning Protocol (EPP)" 2137 Document status: Standards Track 2139 Reference: (insert reference to RFC version of this document) 2141 Registrant Name and Email Address: IESG, 2143 TLDs: Any 2145 IPR Disclosure: None 2147 Status: Active 2149 Notes: None 2151 6. Implementation Status 2153 Note to RFC Editor: Please remove this section and the reference to 2154 RFC 7942 [RFC7942] before publication. 2156 This section records the status of known implementations of the 2157 protocol defined by this specification at the time of posting of this 2158 Internet-Draft, and is based on a proposal described in RFC 7942 2159 [RFC7942]. The description of implementations in this section is 2160 intended to assist the IETF in its decision processes in progressing 2161 drafts to RFCs. Please note that the listing of any individual 2162 implementation here does not imply endorsement by the IETF. 2163 Furthermore, no effort has been spent to verify the information 2164 presented here that was supplied by IETF contributors. This is not 2165 intended as, and must not be construed to be, a catalog of available 2166 implementations or their features. Readers are advised to note that 2167 other implementations may exist. 2169 According to RFC 7942 [RFC7942], "this will allow reviewers and 2170 working groups to assign due consideration to documents that have the 2171 benefit of running code, which may serve as evidence of valuable 2172 experimentation and feedback that have made the implemented protocols 2173 more mature. It is up to the individual working groups to use this 2174 information as they see fit". 2176 6.1. Verisign EPP SDK 2178 Organization: Verisign Inc. 2180 Name: Verisign EPP SDK 2182 Description: The Verisign EPP SDK includes both a full client 2183 implementation and a full server stub implementation of draft-ietf- 2184 regext-launchphase. 2186 Level of maturity: Production 2188 Coverage: All aspects of the protocol are implemented. 2190 Licensing: GNU Lesser General Public License 2192 Contact: jgould@verisign.com 2194 URL: http://www.verisigninc.com/en_US/channel-resources/domain- 2195 registry-products/epp-sdks 2197 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 2199 Organization: Verisign Inc. 2201 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 2202 System (SRS) 2204 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 2205 Registry System (SRS) implements the server-side of draft-ietf- 2206 regext-launchphase for a variety of Top Level Domains (TLD's). 2208 Level of maturity: Production 2210 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2211 Form for the EPP Command, the Sunrise and Claims Forms for 2212 the EPP Command of Launch Registrations and Launch 2213 Applications. For Launch Applications the Poll Messaging, the EPP 2214 Command, the EPP Command, and the EPP 2215 Command is covered. 2217 Licensing: Proprietary 2219 Contact: jgould@verisign.com 2221 6.3. Verisign .COM / .NET SRS 2223 Organization: Verisign Inc. 2225 Name: Verisign .COM / .NET Shared Registry System (SRS) 2227 Description: The Verisign Shared Registry System (SRS) for .COM, .NET 2228 and other IDN TLD's implements the server-side of draft-ietf-regext- 2229 launchphase. 2231 Level of maturity: Operational Test Environment (OTE) 2233 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2234 Form for the EPP Command, the Sunrise and Claims Forms for 2235 the EPP Command of Launch Registrations. 2237 Licensing: Proprietary 2239 Contact: jgould@verisign.com 2241 6.4. REngin v3.7 2243 Organization: Domain Name Services (Pty) Ltd 2245 Name: REngin v3.7 2247 Description: Server side implementation only 2249 Level of maturity: Production 2251 Coverage: All features from version 12 have been implemented 2253 Licensing: Proprietary Licensing with Maintenance Contracts 2255 Contact: info@dnservices.co.za 2257 URL: https://www.registry.net.za and soon http://dnservices.co.za 2259 6.5. RegistryEngine EPP Service 2261 Organization: CentralNic 2263 Name: RegistryEngine EPP Service 2265 Description: Generic high-volume EPP service for gTLDs, ccTLDs and 2266 SLDs 2267 Level of maturity: Deployed in CentralNic's production environment as 2268 well as two other gTLD registry systems, and two ccTLD registry 2269 systems. 2271 Coverage: Majority of elements including TMCH sunrise, landrush and 2272 TM claims as well as sunrise applications validated using codes. 2274 Licensing: Proprietary In-House software 2276 Contact: epp@centralnic.com 2278 URL: https://www.centralnic.com 2280 6.6. Neustar EPP SDK 2282 Organization: Neustar 2284 Name: Neustar EPP SDK 2286 Description: The Neustar EPP SDK includes client implementation of 2287 draft-ietf-regext-launchphase in both Java and C++. 2289 Level of maturity: Production 2291 Coverage: All aspects of the protocol are implemented. 2293 Licensing: GNU Lesser General Public License 2295 Contact: trung.tran@neustar.biz 2297 6.7. gTLD Shared Registry System 2299 Organization: Stichting Internet Domeinnaamregistratie Nederland 2300 (SIDN) 2302 Name: gTLD Shared Registry System 2304 Description: The gTLD SRS implements the server side of the draft- 2305 ietf-regext-launchphase. 2307 Level of maturity: (soon) Production 2309 Coverage: The following parts of the draft are supported: 2311 Signed mark validation model using Digital Signature 2312 (Section 2.6.3) 2313 Claims Check Form (Section 3.1.1) 2314 Sunrise Create Form (Section 3.3.1) 2315 Claims Create Form (Section 3.3.2) 2317 The parts of the document not described here are not implemented. 2319 Licensing: Proprietary 2321 Contact: rik.ribbers@sidn.nl 2323 7. Security Considerations 2325 The mapping extensions described in this document do not provide any 2326 security services beyond those described by EPP [RFC5730], the EPP 2327 domain name mapping [RFC5731], and protocol layers used by EPP. The 2328 security considerations described in these other specifications apply 2329 to this specification as well. 2331 Updates to, and deletion of an application object must be restricted 2332 to clients authorized to perform the said operation on the object. 2334 Information contained within an application, or even the mere fact 2335 that an application exists may be confidential. Any attempt to 2336 operate on an application object by an unauthorized client MUST be 2337 rejected with an EPP 2201 (authorization error) return code. Server 2338 policy may allow operation with filtered output by clients 2339 other than the sponsoring client, in which case the 2340 and response SHOULD be filtered to include only 2341 fields that are publicly accessible. 2343 8. Acknowledgements 2345 The authors wish to acknowledge the efforts of the leading 2346 participants of the Community TMCH Model that led to many of the 2347 changes to this document, which include Chris Wright, Jeff Neuman, 2348 Jeff Eckhaus, and Will Shorter. 2350 Special suggestions that have been incorporated into this document 2351 were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Scott 2352 Hollenbeck, Michael Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, 2353 Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Patrick Mevzek, 2354 James Mitchell, Francisco Obispo, Mike O'Connell, Bernhard Reutner- 2355 Fischer, Trung Tran, Ulrich Wisser and Sharon Wodjenski. 2357 Some of the description of the Trademark Claims Phase was based on 2358 the work done by Gustavo Lozano in the ICANN TMCH functional 2359 specifications. 2361 9. References 2363 9.1. Normative References 2365 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2366 Requirement Levels", BCP 14, RFC 2119, 2367 DOI 10.17487/RFC2119, March 1997, . 2370 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2371 DOI 10.17487/RFC3688, January 2004, . 2374 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2375 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 2376 . 2378 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2379 Domain Name Mapping", STD 69, RFC 5731, 2380 DOI 10.17487/RFC5731, August 2009, . 2383 [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", 2384 RFC 7848, DOI 10.17487/RFC7848, June 2016, 2385 . 2387 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 2388 Code: The Implementation Status Section", BCP 205, 2389 RFC 7942, DOI 10.17487/RFC7942, July 2016, 2390 . 2392 9.2. Informative References 2394 [I-D.ietf-regext-tmch-func-spec] 2395 Lozano, G., "ICANN TMCH functional specifications", draft- 2396 ietf-regext-tmch-func-spec-03 (work in progress), July 2397 2017. 2399 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 2400 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 2401 February 2015, . 2403 Appendix A. Change History 2404 A.1. Change from 00 to 01 2406 1. Changed to use camel case for the XML elements. 2407 2. Replaced "cancelled" status to "rejected" status. 2408 3. Added the child elements of the element. 2409 4. Removed the XML schema and replaced with "[TBD]". 2411 A.2. Change from 01 to 02 2413 1. Added support for both the ICANN and ARI/Neustar TMCH models. 2414 2. Changed the namespace URI and prefix to use "launch" instead of 2415 "launchphase". 2416 3. Added definition of multiple claim validation models. 2417 4. Added the and 2418 elements. 2419 5. Added support for Claims Info Command 2421 A.3. Change from 02 to 03 2423 1. Removed XSI namespace per Keith Gaughan's suggestion on the 2424 provreg list. 2425 2. Added extensibility to the launch:status element and added the 2426 pendingAuction status per Trung Tran's feedback on the provreg 2427 list. 2428 3. Added support for the Claims Check Command, updated the location 2429 and contents of the signedNotice, and replaced most references of 2430 Claim to Mark based on the work being done on the ARI/Neustar 2431 launch model. 2433 A.4. Change from 03 to 04 2435 1. Removed references to the ICANN model. 2436 2. Removed support for the Claims Info Command. 2437 3. Removed use of the signedClaim. 2438 4. Revised the method for referring to the signedClaim from the XML 2439 Signature using the IDREF URI. 2440 5. Split the launch-1.0.xsd into three XML schemas including launch- 2441 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 2442 6. Split the "claims" launch phase to the "claims1" and "claims2" 2443 launch phases. 2444 7. Added support for the encodedSignedMark with base64 encoded 2445 signedMark. 2446 8. Changed the elements in the createNoticeType to include the 2447 noticeID, timestamp, and the source elements. 2448 9. Added the class and effectiveDate elements to mark. 2450 A.5. Change from 04 to 05 2452 1. Removed reference to in the example. 2453 2. Incorporated feedback from Bernhard Reutner-Fischer on the 2454 provreg mail list. 2455 3. Added missing launch XML prefix to applicationIDType reference in 2456 the idContainerType of the Launch Schema. 2457 4. Added missing description of the element in the 2458 element. 2459 5. Updated note on replication of the EPP contact mapping elements 2460 in the Mark Contact section. 2462 A.6. Change from 05 to 06 2464 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 2465 replaced with reference to draft-lozano-smd, that contains the 2466 definition for the mark, signed marked, and encoded signed mark. 2467 2. Split the into and 2468 based on feedback from Trung Tran. 2469 3. Added the "includeMark" optional attribute to the 2470 element to enable the client to request whether or not to include 2471 the mark in the info response. 2472 4. Fixed state diagram to remove redundant transition from "invalid" 2473 to "rejected"; thanks Klaus Malorny. 2475 A.7. Change from 06 to 07 2477 1. Proof-read grammar and spelling. 2478 2. Changed "pendingAuction" status to "pendingAllocation", changed 2479 "pending" to "pendingValidation" status, per proposal from Trung 2480 Tran and seconded by Rubens Kuhl. 2481 3. Added text related to the use of RFC 5731 pendingCreate to the 2482 Application Identifier section. 2483 4. Added the Poll Messaging section to define the use of poll 2484 messaging for intermediate state transitions and pending action 2485 poll messaging for final state transitions. 2487 A.8. Change from 07 to 08 2489 1. Added support for use of the launch statuses and poll messaging 2490 for Launch Registrations based on feedback from Sharon Wodjenski 2491 and Trung Tran. 2492 2. Incorporated changes based on updates or clarifications in draft- 2493 lozano-tmch-func-spec-01, which include: 2495 1. Removed the unused element. 2496 2. Removed the element. 2498 3. Added the element based on the required 2499 element. 2501 A.9. Change from 08 to 09 2503 1. Made element optional in to allow 2504 passing just the in per request 2505 from Ben Levac. 2506 2. Added optional "type" attribute in to enable the 2507 client to explicitly define the desired type of object 2508 (application or registration) to create to all forms of the 2509 create extension. 2510 3. Added text that the server SHOULD validate the 2511 element in the Launch Phases section. 2512 4. Add the "General Create Form" to the create command extension to 2513 support the request from Ben Levac. 2514 5. Updated the text for the Poll Messaging section based on feedback 2515 from Klaus Malorny. 2516 6. Replaced the "claims1" and "claims2" phases with the "claims" 2517 phase based on discussion on the provreg list. 2518 7. Added support for a mixed create model (Sunrise Create Model and 2519 Claims Create Model), where a trademark (encoded signed mark, 2520 etc.) and notice can be passed, based on a request from James 2521 Mitchell. 2522 8. Added text for the handling of the overlapping "claims" and 2523 "landrush" launch phases. 2524 9. Added support for two check forms (claims check form and 2525 availability check form) based on a request from James Mitchell. 2526 The availability check form was based on the text in draft-rbp- 2527 application-epp-mapping. 2529 A.10. Change from 09 to 10 2531 1. Changed noticeIDType from base64Binary to token to be compatible 2532 with draft-lozano-tmch-func-spec-05. 2533 2. Changed codeType from base64Binary to token to be more generic. 2534 3. Updated based on feedback from Alexander Mayrhofer, which 2535 include: 2537 1. Changed "extension to the domain name extension" to 2538 "extension to the domain name mapping". 2539 2. Changed use of 2004 return code to 2306 return code when 2540 phase passed mismatches active phase and sub-phase. 2541 3. Changed description of "allocated" and "rejected" statuses. 2542 4. Moved sentence on a synchronous command 2543 without the use of an intermediate application, then an 2544 Application Identifier MAY not be needed to the Application 2545 Identifier section. 2547 5. Restructured the Mark Validation Models section to include 2548 the " element" sub-section, the 2549 " element" sub-section, and the Digital Signature 2550 sub-section. 2551 6. Changed "Registries may" to "Registries MAY". 2552 7. Changed "extensed" to "extended" in "Availability Check 2553 Form" section. 2554 8. Broke the mix of create forms in the "EPP Command" 2555 section to a fourth "Mixed Create Form" with its own sub- 2556 section. 2557 9. Removed "displayed or" from "displayed or accepted" in the 2558 description. 2559 10. Replaced "given domain name is supported" with "given domain 2560 name are supported" in the "Create Response" section. 2561 11. Changed the reference of 2303 (object does not exist) in the 2562 "Security Considerations" section to 2201 (authorization 2563 error). 2564 12. Added arrow from "invalid" status to "pendingValidation" 2565 status and "pendingAllocation" status to "rejected" status 2566 in the State Transition Diagram. 2567 4. Added the "C:" and "S:" example prefixes and related text in the 2568 "Conventions Used in This Document" section. 2570 A.11. Change from 10 to 11 2572 1. Moved the claims check response element under 2573 the element instead of the element based on 2574 the request from Francisco Obispo. 2576 A.12. Change from 11 to 12 2578 1. Added support for multiple validator identifiers for claims 2579 notices and marks based on a request and text provided by Mike 2580 O'Connell. 2581 2. Removed domain:exDate element from example in section 3.3.5 based 2582 on a request from Seth Goldman on the provreg list. 2583 3. Added clarifying text for clients not passing the launch 2584 extension on update and delete commands to servers that do not 2585 support launch applications based on a request from Sharon 2586 Wodjenski on the provreg list. 2588 A.13. Change from 12 to EPPEXT 00 2590 1. Changed to eppext working group draft by changing draft-tan-epp- 2591 launchphase to draft-ietf-eppext-launchphase and by changing 2592 references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch- 2593 smd. 2595 A.14. Change EPPEXT 00 to EPPEXT 01 2597 1. Removed text associated with support for the combining of status 2598 values based on feedback from Patrick Mevzek on the provreg 2599 mailing list, discussion on the eppext mailing list, and 2600 discussion at the eppext IETF meeting on March 6, 2014. 2602 A.15. Change EPPEXT 01 to EPPEXT 02 2604 1. Changed the element to be zero or more elements 2605 and the element to be one or more elements in the 2606 Claims Create Form. These changes were needed to be able to 2607 support more than one concurrent claims services. 2609 A.16. Change EPPEXT 02 to EPPEXT 03 2611 1. Added the "Implementation Status" section based on an action item 2612 from the eppext IETF-91 meeting. 2613 2. Moved Section 7 "IANA Considerations" and Section 9 "Security 2614 Considerations" before Section 5 "Acknowledgements". Moved 2615 "Change Log" Section to end. 2616 3. Updated the text for the Claims Check Form and the Claims Create 2617 Form to support checking for the need of the claims notice and 2618 passing the claims notice outside of the "claims" phase. 2619 4. Added the new Trademark Check Form to support determining whether 2620 or not a trademark exists that matches the domain name 2621 independent of whether a claims notice is required on create. 2622 This was based on a request from Trung Tran and a discussion on 2623 the eppext mailing list. 2625 A.17. Change EPPEXT 03 to EPPEXT 04 2627 1. Amended XML Namespace section of IANA Considerations, added EPP 2628 Extension Registry section. 2630 A.18. Change EPPEXT 04 to EPPEXT 05 2632 1. Added a missing comma to the descripton of the 2633 element, based on feedback from Keith Gaughan on the eppext 2634 mailing list. 2635 2. Added the SIDN implementation status information. 2636 3. Fixed a few indentation issues in the samples. 2638 A.19. Change EPPEXT 05 to EPPEXT 06 2640 1. Removed duplicate "TMCH Functional Specification" URIs based on 2641 feedback from Scott Hollenbeck on the eppext mailing list. 2643 2. Changed references of example?.tld to domain?.example to be 2644 consistent with RFC 6761 based on feedback from Scott Hollenbeck 2645 on the eppext mailing list. 2646 3. A template was added to section 5 to register the XML schema in 2647 addition to the namespace based on feedback from Scott Hollenbeck 2648 on the eppext mailing list. 2650 A.20. Change EPPEXT 06 to EPPEXT 07 2652 1. Changed reference of lozano-tmch-func-spec to ietf-eppext-tmch- 2653 func-spec. 2655 A.21. Change from EPPEXT 07 to REGEXT 00 2657 1. Changed to regext working group draft by changing draft-ietf- 2658 eppext-launchphase to draft-ietf-regext-launchphase and by 2659 changing references of draft-ietf-eppext-tmch-func-spec to draft- 2660 ietf-regext-tmch-func-spec. 2662 A.22. Change from REGEXT 00 to REGEXT 01 2664 1. Fixed reference of Claims Check Command to Trademark Check 2665 Command in the Trademark Check Form section. 2666 2. Replaced reference of draft-ietf-eppext-tmch-smd to RFC 7848. 2668 A.23. Change from REGEXT 01 to REGEXT 02 2670 1. Removed the reference to ietf-regext-tmch-func-spec and briefly 2671 described the trademark claims phase that is relavent to draft- 2672 ietf-regext-launchphase. 2674 A.24. Change from REGEXT 02 to REGEXT 03 2676 1. Ping update. 2678 A.25. Change from REGEXT 03 to REGEXT 04 2680 1. Updates based on feedback from Scott Hollenbeck that include: 2682 1. Nit on reference to RFC 7848 in section 1. 2683 2. Added reference to for the request to create 2684 a Launch Application in section 2.1. 2685 3. Removed the second paragraph of section 2.1 describing the 2686 option of creating an application identifier for a Launch 2687 Registration. 2688 4. Provided clarification in section 2.2 on the responsibility 2689 of the server to ensure that the supported validator 2690 identifiers are unique. 2692 5. Updated the text in section 2.5 referencing the domain name 2693 object in RFC 5731. 2694 6. Updated the copyright to 2017 in section 4.1. 2696 A.26. Change from REGEXT 04 to REGEXT 05 2698 1. Updates based on feedback from Ulrich Wisser that include: 2700 1. Updated reference to obsoleted RFC 6982 with RFC 7942. 2701 2. Moved RFC 7451 reference from normative to informative. 2703 A.27. Change from REGEXT 05 to REGEXT 06 2705 1. Updates based on feedback from Adam Roach that include: 2707 1. Added an informative reference to draft-ietf-regext-tmch- 2708 func-spec in section 2.3.1 "Trademark Claims Phase". 2709 2. Added formal definition of a Launch Registration and Launch 2710 Application to section 1.1. 2711 3. Updated the description of the Validator Identifier to 2712 indicate that the uniqueness is based on server policy. 2713 4. Updated "Does Domain have Claims?" "No" and "Yes" branch 2714 labels in Figure 1. 2715 5. Updated the description of the element in the 2716 commands to explicitly specify the return of a 2306 EPP 2717 error result when invalid or referring to section 2.3 for 2718 validation. 2719 6. Fixed indentation of the and 2720 elements in the section 2.5 examples. 2721 7. Updated the description of the element in the 2722 info response. 2723 8. Added returning an EPP error result code of 2306 if the 2724 "type" attribute is incorrect in section 3.3.1, 3.3.2, and 2725 3.3.3. 2726 9. Made small change in the description of the Create Response 2727 in section 3.3.5. 2728 10. Updated the Registrant Contact in section 7 to the IESG. 2730 Authors' Addresses 2732 James Gould 2733 VeriSign, Inc. 2734 12061 Bluemont Way 2735 Reston, VA 20190 2736 US 2738 Email: jgould@verisign.com 2739 URI: http://www.verisigninc.com 2740 Wil Tan 2741 Cloud Registry 2742 Suite 32 Seabridge House 2743 377 Kent St 2744 Sydney, NSW 2000 2745 AU 2747 Phone: +61 414 710899 2748 Email: wil@cloudregistry.net 2749 URI: http://www.cloudregistry.net 2751 Gavin Brown 2752 CentralNic Ltd 2753 35-39 Mooregate 2754 London, England EC2R 6AR 2755 GB 2757 Phone: +44 20 33 88 0600 2758 Email: gavin.brown@centralnic.com 2759 URI: https://www.centralnic.com