idnits 2.17.1 draft-ietf-regext-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 (April 27, 2017) is 2555 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) ** Obsolete normative reference: RFC 6982 (Obsoleted by RFC 7942) ** Downref: Normative reference to an Informational RFC: RFC 7451 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 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: October 29, 2017 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 April 27, 2017 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-ietf-regext-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 October 29, 2017. 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 . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . 28 77 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 28 78 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 34 79 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 37 80 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 38 81 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 40 82 3.4. EPP Command . . . . . . . . . . . . . . . . . . 41 83 3.5. EPP Command . . . . . . . . . . . . . . . . . . 42 84 3.6. EPP Command . . . . . . . . . . . . . . . . . . . 43 85 3.7. EPP Command . . . . . . . . . . . . . . . . . 44 86 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 44 87 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 44 88 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 89 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 51 90 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 52 91 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 52 92 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 53 93 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 53 94 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 54 95 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 54 96 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 54 97 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 55 98 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 55 99 7. Security Considerations . . . . . . . . . . . . . . . . . . . 56 100 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 56 101 9. Normative References . . . . . . . . . . . . . . . . . . . . 57 102 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 57 103 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 57 104 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 57 105 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 58 106 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 58 107 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 58 108 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 59 109 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 59 110 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 59 111 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 59 112 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 60 113 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 61 114 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 61 115 A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 61 116 A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 61 117 A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 61 118 A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 62 119 A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 62 120 A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 62 121 A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 62 122 A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 62 123 A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 63 124 A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 63 125 A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 63 126 A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 63 127 A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 63 128 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63 130 1. Introduction 132 This document describes an extension mapping for version 1.0 of the 133 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 134 specifies a flexible schema that can be used to implement several 135 common use cases related to the provisioning and management of domain 136 name registrations and applications during the launch of a domain 137 name registry. 139 It is typical for domain registries to operate in special modes 140 during their initial launch to facilitate allocation of domain names, 141 often according to special rules. This document uses the term 142 "launch phase" and the shorter form "launch" to refer to such a 143 period. 145 The EPP domain name mapping [RFC5731] is designed for the steady- 146 state operation of a registry. During a launch period, the model in 147 place may be different from what is defined in the EPP domain name 148 mapping [RFC5731]. For example, registries often accept multiple 149 applications for the same domain name during the "Sunrise" launch 150 phase, referred to as a Launch Application. A Launch Registration 151 refers to a registration made during a launch phase when the server 152 uses a "first-come, first-served" model. Even in a "first-come, 153 first-served" model, additional steps and information might be 154 required, such as trademark information. In addition, RFC 7848 155 [RFC7848] defines a registry interface for the Trademark Claims or 156 "claims" launch phase that includes support for presenting a 157 Trademark Claims Notice to the Registrant. This document proposes an 158 extension to the domain name mapping in order to provide a uniform 159 interface for the management of Launch Applications and Launch 160 Registrations in launch phases. 162 1.1. Conventions Used in This Document 164 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 165 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 166 document are to be interpreted as described in RFC 2119 [RFC2119]. 168 XML is case sensitive. Unless stated otherwise, XML specifications 169 and examples provided in this document MUST be interpreted in the 170 character case presented in order to develop a conforming 171 implementation. 173 In examples, "C:" represents lines sent by a protocol client and "S:" 174 represents lines returned by a protocol server. Indentation and 175 white space in examples are provided only to illustrate element 176 relationships and are not a REQUIRED feature of this protocol. 178 "launch-1.0" is used as an abbreviation for 179 "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix 180 "launch" is used, but implementations MUST NOT depend on it and 181 instead employ a proper namespace-aware XML parser and serializer to 182 interpret and output the XML documents. 184 "signedMark-1.0" is used as an abbreviation for 185 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [RFC7848]. 186 The XML namespace prefix "smd" is used, but implementations MUST NOT 187 depend on it and instead employ a proper namespace-aware XML parser 188 and serializer to interpret and output the XML documents. 190 "mark-1.0" is used as an abbreviation for 191 "urn:ietf:params:xml:ns:mark-1.0" that is defined in [RFC7848]. The 192 XML namespace prefix "mark" is used, but implementations MUST NOT 193 depend on it and instead employ a proper namespace-aware XML parser 194 and serializer to interpret and output the XML documents. 196 2. Object Attributes 198 This extension adds additional elements to the EPP domain name 199 mapping [RFC5731]. Only those new elements are described here. 201 2.1. Application Identifier 203 Servers MAY allow multiple applications, referred to as a Launch 204 Application, of the same domain name during its launch phase 205 operations. Upon receiving a valid command to create 206 a Launch Application, the server MUST create an application object 207 corresponding to the request, assign an application identifier for 208 the Launch Application, set the [RFC5731] pendingCreate status, and 209 return the application identifier to the client with the 210 element. In order to facilitate correlation, 211 all subsequent launch operations on the Launch Application MUST be 212 qualified by the previously assigned application identifier using the 213 element. 215 2.2. Validator Identifier 217 The Validator Identifier is the unique identifier for a Trademark 218 Validator that validates marks and has a repository of validated 219 marks. The OPTIONAL "validatorID" attribute is used to define the 220 Validator Identifier of the Trademark Validator. Registries MAY 221 support more than one Third Party Trademark Validator. The Internet 222 Corporation for Assigned Names and Numbers (ICANN) Trademark 223 Clearinghouse (TMCH) is the default Trademark Validator and is 224 reserved the Validator Identifier of "tmch". If the ICANN TMCH is 225 not used or multiple Trademark Validators are used, the Validator 226 Identifier MUST be defined using the "validatorID" attribute. 228 The Validator Identifier MAY be related to one or more issuer 229 identifiers of the element and the element defined 230 in [RFC7848]. Both the Validator Identifier and the Issuer 231 Identifier used MUST be unique. If the ICANN TMCH is not used or 232 multiple Trademark Validators are used, the server MUST define the 233 list of supported validator identifiers and MUST make this 234 information available to clients using a mutually acceptable, out-of- 235 band mechanism. 237 The Validator Identifier MAY define a non-Trademark Validator that 238 supports a form of claims. 240 2.3. Launch Phases 242 The server MAY support multiple launch phases sequentially or 243 simultaneously. The element MUST be included by the 244 client to define the target launch phase of the command. The server 245 SHOULD validate the phase and MAY validate the sub-phase of the 246 element against the active phase and OPTIONAL sub- 247 phase of the server on a create command, and return an EPP error 248 result code of 2306 if there is a mismatch. 250 The following launch phase values are defined: 252 sunrise The phase during which trademark holders can submit 253 registrations or applications with trademark information that can 254 be validated by the server. 255 landrush A post-Sunrise phase when non-trademark holders are allowed 256 to register domain names with steps taken to address a large 257 volume of initial registrations. 258 claims The phase, as defined in the Section 2.3.1, in which a Claims 259 Notice MUST be displayed to a prospective registrant of a domain 260 name that matches trademarks. 261 open A post-launch phase that is also referred to as "steady state". 262 Servers MAY require additional trademark protection during this 263 phase. 264 custom A custom server launch phase that is defined using the "name" 265 attribute. 267 For extensibility, the element includes an OPTIONAL 268 "name" attribute that can define a sub-phase, or the full name of the 269 phase when the element has the "custom" value. For 270 example, the "claims" launch phase could have two sub-phases that 271 include "landrush" and "open". 273 Launch phases MAY overlap to support the "claims" launch phase, 274 defined in the Section 2.3.1, and to support a traditional "landrush" 275 launch phase. The overlap of the "claims" and "landrush" launch 276 phases SHOULD be handled by setting "claims" as the 277 value and setting "landrush" as the sub-phase with the "name" 278 attribute. For example, the element SHOULD be 279 claims. 281 2.3.1. Trademark Claims Phase 283 The Trademark Claims Phase is when a Claims Notice MUST be displayed 284 to a prospective registrant of a domain name that matches trademarks. 285 The source of the trademarks is a Trademark Validator and the source 286 of the Claims Notice information is a Claim Notice Information 287 Service (CNIS), which MAY be directly linked to a Trademark 288 Validator. The client interfaces with the server to determine if a 289 trademark exists for a domain name, interfaces with a CNIS to get the 290 Claims Notice information, and interfaces with the server to pass the 291 Claims Notice acceptance information in a create command. This 292 document supports the Trademark Claims Phase in two ways including: 294 Claims Check Form Claims Check Form (Section 3.1.1) is used to 295 determine whether or not there are any matching trademarks for a 296 domain name. If there is at least one matching trademark that 297 exists for the domain name, a claims key is returned. The mapping 298 of domain names and the claims keys is based on an out-of-band 299 interface between the server and the Trademark Validator. The 300 CNIS associated with the claims key Validator Identifier 301 (Section 2.2) MUST accept the claims key as the basis for 302 retrieving the claims information. 303 Claims Create Form Claims Create Form (Section 3.3.2) is used to 304 pass the Claims Notice acceptance information in a create command. 305 The notice identifier () format, validation 306 rules, and server processing is up to the interface between the 307 server and the Trademark Validator. The CNIS associated with the 308 Validator Identifier (Section 2.2) MUST generate a notice 309 identifier compliant with the element. 311 The following shows the Trademark Claims Phase registration flow: 313 .------------. .--------. .--------. .------. 314 | Registrant | | Client | | Server | | CNIS | 315 '------------' '--------' '--------' '------' 316 | Request Domain | | | 317 | Registration | | | 318 |--------------->| Domain Check | | 319 | |--------------------------->| | 320 | Domain | Domain Unavailable .------------. | 321 | Unavailable |<---------------------( Available? ) | 322 |<---------------| No '------------' | 323 | | Domain Available | Yes | 324 | |<---------------------------| | 325 | | Domain Claims Check | | 326 | |--------------------------->| | 327 | | .---------. | 328 | | / Does \ | 329 | |<--------------------( Domain have ) | 330 | | No \ Claims? / | 331 | | '---------' | 332 | | Domain Create | | Yes | 333 | |--------------------------->| | | 334 | Domain | Domain Registered | | | 335 | Registered |<---------------------------| | | 336 |<---------------| | | 337 | | | 338 | | Claims Key | | 339 | |<------------------------------' | 340 | | | 341 .-----. | | Request Claims Info with Claims Key | 342 |Abort| | Display |-------------------------------------->| 343 '-----' | Claims | Return Claims Info | 344 ^ | Notice |<--------------------------------------| 345 | No |<---------------| | 346 | .------. Yes | | 347 '-( Ack? )----------->| Domain Claims Create Form | | 348 '------' |--------------------------->| | 349 | Registration | Error .----------------------. | 350 | Error |<-----------( Validation Successful? ) | 351 |<---------------| No '----------------------' | 352 | | | Yes | 353 | Domain | Domain Registered | | 354 | Registered |<---------------------------| | 355 |<---------------| | | 357 Figure 1 359 2.4. Status Values 361 A Launch Application or Launch Registration object MAY have a launch 362 status value. The element is used to convey the 363 launch status pertaining to the object, beyond what is specified in 364 the object mapping. A Launch Application or Launch Registration MUST 365 set the [RFC5731] "pendingCreate" status if a launch status is 366 supported and the launch status is not one of the final statuses, 367 including the "allocated" and "rejected" statuses. 369 The following status values are defined using the required "s" 370 attribute: 372 pendingValidation: The initial state of a newly-created application 373 or registration object. The application or registration requires 374 validation, but the validation process has not yet completed. 375 validated: The application or registration meets relevant registry 376 rules. 377 invalid: The application or registration does not validate according 378 to registry rules. Server policies permitting, it may transition 379 back into "pendingValidation" for revalidation, after 380 modifications are made to ostensibly correct attributes that 381 caused the validation failure. 382 pendingAllocation: The allocation of the application or registration 383 is pending based on the results of some out-of-band process (for 384 example, an auction). 385 allocated: The object corresponding to the application or 386 registration has been provisioned. Is a possible end state of an 387 application or registration object. 388 rejected: The application or registration object was not 389 provisioned. Is a possible end state of an application or 390 registration object. 391 custom: A custom status that is defined using the "name" attribute. 393 Each status value MAY be accompanied by a string of human-readable 394 text that describes the rationale for the status applied to the 395 object. The OPTIONAL "lang" attribute MAY be present to identify the 396 language if the negotiated value is something other than the default 397 value of "en" (English). 399 For extensibility the element includes an OPTIONAL 400 "name" attribute that can define a sub-status or the full name of the 401 status when the status value is "custom". The server SHOULD NOT use 402 the "custom" status value. 404 Status values MAY be skipped. For example, an application or 405 registration MAY immediately start at the "allocated" status or an 406 application or registration MAY skip the "pendingAllocation" status. 408 If the launch phase does not require validation of a request, an 409 application or registration MAY immediately skip to 410 "pendingAllocation". 412 2.4.1. State Transition 414 | request 415 | 416 | +--------------------------+ 417 | | | 418 v v | 419 +-------------------+ | 420 | | | 421 | pendingValidation +--------------+ | 422 | | | | 423 +---------+---------+ | | 424 | | | 425 | | | 426 v v | 427 +-----------+ +---------+ | 428 | | | | | 429 | validated | | invalid +--+ 430 | | | | 431 +-----+-----+ +----+----+ 432 | | 433 | | 434 v | 435 +-------------------+ | 436 | | | 437 | pendingAllocation +-----------+ | 438 | | | | 439 +---------+---------+ | | 440 | | | 441 | | | 442 | | | 443 | | | 444 | | | 445 v v v 446 +---------+ +--------+ 447 / \ / \ 448 | allocated | | rejected | 449 \ / \ / 450 +---------+ +--------+ 452 Figure 2 454 2.5. Poll Messaging 456 A Launch Application MUST and a Launch Registration MAY be handled as 457 an EPP domain name object as specified in RFC 5731 [RFC5731] in 458 "pendingCreate" status, with the launch status values defined in 459 Section 2.4. As a Launch Application or Launch Registration 460 transitions between the status values defined in Section 2.4, the 461 server SHOULD insert poll messages, per [RFC5730], for the applicable 462 intermediate statuses, including the "pendingValidation", 463 "validated", "pendingAllocation, and "invalid" statuses, using the 464 element with the extension. The 465 element MAY contain non-mandatory information, like 466 contact and name server information. Also, further extensions that 467 would normally be included in the response of a 468 command, per [RFC5731], MAY be included. For the final statuses, 469 including the "allocated" and "rejected" statuses, the server MUST 470 insert a poll message, per [RFC5731], with the 471 extension. 473 The following is an example poll message for a Launch Application 474 that has transitioned to the "pendingAllocation" state. 476 S: 477 S: 478 S: 479 S: 480 S: Command completed successfully; ack to dequeue 481 S: 482 S: 483 S: 2013-04-04T22:01:00.0Z 484 S: Application pendingAllocation. 485 S: 486 S: 487 S: 489 S: domain.example 490 S: ... 491 S: 492 S: 493 S: 494 S: 496 S: sunrise 497 S: abc123 498 S: 499 S: 500 S: 501 S: 502 S: ABC-12345 503 S: 54322-XYZ 504 S: 505 S: 506 S: 507 The following is an example poll message for an 508 "allocated" Launch Application. 510 S: 511 S: 512 S: 513 S: 514 S: Command completed successfully; ack to dequeue 515 S: 516 S: 517 S: 2013-04-04T22:01:00.0Z 518 S: Application successfully allocated. 519 S: 520 S: 521 S: 523 S: domain.example 524 S: 525 S: ABC-12345 526 S: 54321-XYZ 527 S: 528 S: 2013-04-04T22:00:00.0Z 529 S: 530 S: 531 S: 532 S: 534 S: sunrise 535 S: abc123 536 S: 537 S: 538 S: 539 S: 540 S: BCD-23456 541 S: 65432-WXY 542 S: 543 S: 544 S: 545 The following is an example poll message for an 546 "allocated" Launch Registration. 548 S: 549 S: 550 S: 551 S: 552 S: Command completed successfully; ack to dequeue 553 S: 554 S: 555 S: 2013-04-04T22:01:00.0Z 556 S: Registration successfully allocated. 557 S: 558 S: 559 S: 561 S: domain.example 562 S: 563 S: ABC-12345 564 S: 54321-XYZ 565 S: 566 S: 2013-04-04T22:00:00.0Z 567 S: 568 S: 569 S: 570 S: 572 S: sunrise 573 S: 574 S: 575 S: 576 S: 577 S: BCD-23456 578 S: 65432-WXY 579 S: 580 S: 581 S: 583 2.6. Mark Validation Models 585 A server MUST support at least one of the following models for 586 validating trademark information: 588 code Use of a mark code by itself to validate that the mark matches 589 the domain name. This model is supported using the 590 element with just the element. 591 mark The mark information is passed without any other validation 592 element. The server will use some custom form of validation to 593 validate that the mark information is authentic. This model is 594 supported using the element with just the 595 (Section 2.6.2) element. 596 code with mark: A code is used along with the mark information by 597 the server to validate the mark utilizing an external party. The 598 code represents some form of secret that matches the mark 599 information passed. This model is supported using the 600 element that contains both the and 601 the (Section 2.6.2) elements. 602 signed mark: The mark information is digitally signed as described 603 in the Digital Signature (Section 2.6.3) section. The digital 604 signature can be directly validated by the server using the public 605 key of the external party that created the signed mark using its 606 private key. This model is supported using the 607 (Section 2.6.3.1) and (Section 2.6.3.2) 608 elements. 610 More than one , (Section 2.6.3.1), 611 or (Section 2.6.3.2) element MAY be 612 specified. The maximum number of marks per domain name is up to 613 server policy. 615 2.6.1. element 617 The element that is used by the "code", "mark", and 618 "code with mark" validation models, has the following child elements: 620 : OPTIONAL mark code used to validate the 621 (Section 2.6.2) information. The mark code is be a mark-specific 622 secret that the server can verify against a third party. The 623 OPTIONAL "validatorID" attribute is the Validator Identifier 624 (Section 2.2) whose value indicates which Trademark Validator that 625 the code originated from, with no default value. 626 : OPTIONAL mark information with child elements defined 627 in the Mark (Section 2.6.2) section. 629 The following is an example element with both a 630 and (Section 2.6.2) element. 632 633 634 49FD46E6C4B45C55D4AC 635 636 ... 637 638 640 2.6.2. element 642 A element describes an applicant's prior right to a given 643 domain name that is used with the "mark", "mark with code", and the 644 "signed mark" validation models. The element is defined 645 in [RFC7848]. A new mark format can be supported by creating a new 646 XML schema for the mark that has an element that substitutes for the 647 element from [RFC7848]. 649 2.6.3. Digital Signature 651 Digital signatures MAY be used by the server to validate either the 652 mark information, when using the "signed mark" validation model with 653 the (Section 2.6.3.1) element or the 654 (Section 2.6.3.2) element. 656 2.6.3.1. element 658 The element contains the digitally signed mark 659 information. The element is defined in [RFC7848]. 660 A new signed mark format can be supported by creating a new XML 661 schema for the signed mark that has an element that substitutes for 662 the element from [RFC7848]. 664 2.6.3.2. element 666 The element contains an encoded form of the 667 digitally signed (Section 2.6.3.1) element. The 668 element is defined in [RFC7848]. A new 669 encoded signed mark format can be supported by creating a new XML 670 schema for the encoded signed mark that has an element that 671 substitutes for the element from [RFC7848]. 673 3. EPP Command Mapping 675 A detailed description of the EPP syntax and semantics can be found 676 in the EPP core protocol specification [RFC5730]. The command 677 mappings described here are specifically for use in the Launch Phase 678 Extension. 680 This mapping is designed to be flexible, requiring only a minimum set 681 of required elements. 683 While it is meant to serve several use cases, it does not prescribe 684 any interpretation by the client or server. Such processing is 685 typically highly policy-dependent and therefore specific to 686 implementations. 688 Operations on application objects are done via one or more of the 689 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 690 Registries MAY choose to support a subset of the operations. 692 3.1. EPP Command 694 There are three forms of the extension to the EPP command: 695 the Claims Check Form (Section 3.1.1), the Availability Check Form 696 (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The 697 element "type" attribute defines the form, with the 698 value of "claims" for the Claims Check Form (Section 3.1.1), with the 699 value of "avail" for the Availability Check Form (Section 3.1.2), and 700 with the value of "trademark" for the Trademark Check Form 701 (Section 3.1.3). The default value of the "type" attribute is 702 "claims". The forms supported by the server is determined by server 703 policy. The server MUST return an EPP error result code of 2307 if 704 it receives a check form that is not supported. 706 3.1.1. Claims Check Form 708 The Claims Check Form defines a new command called the Claims Check 709 Command that is used to determine whether or not there are any 710 matching trademarks, in the specified launch phase, for each domain 711 name passed in the command, that requires the use of the "Claims 712 Create Form" on a Domain Create Command. The availability check 713 information defined in the EPP domain name mapping [RFC5731] MUST NOT 714 be returned for the Claims Check Command. This form is the default 715 form and MAY be explicitly identified by setting the 716 "type" attribute to "claims". 718 Instead of returning whether the domain name is available, the Claims 719 Check Command will return whether or not at least one matching 720 trademark exists for the domain name, that requires the use of the 721 "Claims Create Form" on a Domain Create Command. If there is at 722 least one matching trademark that exists for the domain name, a 723 element is returned. The client MAY then use the 724 value of the element to obtain information needed 725 to generate the Trademark Claims Notice from Trademark Validator 726 based on the Validator Identifier (Section 2.2). The unique notice 727 identifier of the Trademark Claims Notice MUST be passed in the 728 element of the extension to the Create Command 729 (Section 3.3). 731 The elements in the EPP command of EPP domain 732 name mapping [RFC5731] define the domain names to check for matching 733 trademarks. The element contains the following child 734 elements: 736 Contains the value of the active launch phase of the 737 server. The server SHOULD validate the value against the active 738 server launch phase. 740 Example Claims Check command using the domain command and the 741 extension with the "type" explicitly set to "claims", 742 to determine if "domain1.example", "domain2.example", and 743 "domain3.example" require claims notices during the "claims" launch 744 phase: 746 C: 747 C: 748 C: 749 C: 750 C: 752 C: domain1.example 753 C: domain2.example 754 C: domain3.example 755 C: 756 C: 757 C: 758 C: 761 C: claims 762 C: 763 C: 764 C: ABC-12345 765 C: 766 C: 768 If the command has been processed successfully, the EPP 769 MUST contain an element that 770 identifies the launch namespace. The element 771 contains the following child elements: 773 The phase that mirrors the element 774 included in the . 775 One or more elements that contain the 776 following child elements: 778 Contains the fully qualified name of the queried 779 domain name. This element MUST contain an "exists" attribute 780 whose value indicates if a matching trademark exists for the 781 domain name that requires the use of the "Claims Create Form" 782 on a Domain Create Command. A value of "1" (or "true") means 783 that a matching trademark does exist and that the "Claims 784 Create Form" is required on a Domain Create Command. A value 785 of "0" (or "false") means that a matching trademark does not 786 exist or that the "Claims Create Form" is NOT required on a 787 Domain Create Command. 788 Zero or more OPTIONAL claim keys that MAY be 789 passed to a third-party Trademark Validator such as the ICANN 790 Trademark Clearinghouse (TMCH) for querying the information 791 needed to generate a Trademark Claims Notice. The 792 is used as the key for the query in place 793 of the domain name to securely query the service without 794 using a well-known value like a domain name. The OPTIONAL 795 "validatorID" attribute is the Validator Identifier 796 (Section 2.2) whose value indicates which Trademark Validator 797 to query for the Claims Notice information, with the default 798 being the ICANN TMCH. The "validatorID" attribute MAY 799 reference a non-trademark claims clearinghouse identifer to 800 support other forms of claims notices. 802 Example Claims Check response when a claims notice is not required 803 for the domain name domain1.example, a claims notice is required for 804 the domain name domain2.example in the "tmch", and a claims notice is 805 required for the domain name domain3.example in the "tmch" and 806 "custom-tmch", for the "claims" launch phase: 808 S: 809 S: 810 S: 811 S: 812 S: Command completed successfully 813 S: 814 S: 815 S: 817 S: claims 818 S: 819 S: domain1.example 820 S: 821 S: 822 S: domain2.example 823 S: 824 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 825 S: 826 S: 827 S: 828 S: domain3.example 829 S: 830 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 831 S: 832 S: 833 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 834 S: 835 S: 836 S: 837 S: 838 S: 839 S: ABC-12345 840 S: 54321-XYZ 841 S: 842 S: 843 S: 845 3.1.2. Availability Check Form 847 The Availability Check Form defines additional elements to extend the 848 EPP command described in the EPP domain name mapping 849 [RFC5731]. No additional elements are defined for the EPP 850 response. This form MUST be identified by setting the 851 "type" attribute to "avail". 853 The EPP command is used to determine if an object can be 854 provisioned within a repository. Domain names may be made available 855 only in unique launch phases, whilst remaining unavailable for 856 concurrent launch phases. In addition to the elements expressed in 857 the , the command is extended with the 858 element that contains the following child elements: 860 The launch phase to which domain name availability 861 should be determined. 863 Example Availability Check Form command using the domain 864 command and the extension with the "type" set to 865 "avail", to determine the availability of two domain names in the 866 "idn-release" custom launch phase: 868 C: 869 C: 870 C: 871 C: 872 C: 874 C: domain1.example 875 C: domain2.example 876 C: 877 C: 878 C: 879 C: 882 C: custom 883 C: 884 C: 885 C: ABC-12345 886 C: 887 C: 889 The Availability Check Form does not define any extension to the 890 response of an domain command. After processing the command, 891 the server replies with a standard EPP response as defined in the EPP 892 domain name mapping [RFC5731]. 894 3.1.3. Trademark Check Form 896 The Trademark Check Form defines a new command called the Trademark 897 Check Command that is used to determine whether or not there are any 898 matching trademarks for each domain name passed in the command, 899 independent of the active launch phase of the server and whether the 900 "Claims Create Form" is required on a Domain Create Command. The 901 availability check information defined in the EPP domain name mapping 902 [RFC5731] MUST NOT be returned for the Trademark Check Command. This 903 form MUST be identified by setting the "type" 904 attribute to "trademark". 906 Instead of returning whether the domain name is available, the 907 Trademark Check Command will return whether or not at least one 908 matching trademark exists for the domain name. If there is at least 909 one matching trademark that exists for the domain name, a 910 element is returned. The client MAY then use the 911 value of the element to obtain Trademark Claims 912 Notice information from Trademark Validator based on the Validator 913 Identifier (Section 2.2). 915 The elements in the EPP command of EPP domain 916 name mapping [RFC5731] define the domain names to check for matching 917 trademarks. The element does not contain any child 918 elements with the "Trademark Check Form": 920 Example Trademark Check command using the domain command and 921 the extension with the "type" set to "trademark", to 922 determine if "domain1.example", "domain2.example", and 923 "domain3.example" have any matching trademarks: 925 C: 926 C: 927 C: 928 C: 929 C: 931 C: domain1.example 932 C: domain2.example 933 C: domain3.example 934 C: 935 C: 936 C: 937 C: 940 C: 941 C: ABC-12345 942 C: 943 C: 945 If the command has been processed successfully, the EPP 946 MUST contain an element that 947 identifies the launch namespace. The element 948 contains the following child elements: 950 One or more elements that contain the 951 following child elements: 953 Contains the fully qualified name of the queried 954 domain name. This element MUST contain an "exists" attribute 955 whose value indicates if a matching trademark exists for the 956 domain name. A value of "1" (or "true") means that a 957 matching trademark does exist. A value of "0" (or "false") 958 means that a matching trademark does not exist. 959 Zero or more OPTIONAL claim keys that MAY be 960 passed to a third-party Trademark Validator such as the ICANN 961 Trademark Clearinghouse (TMCH) for querying the information 962 needed to generate a Trademark Claims Notice. The 963 is used as the key for the query in place 964 of the domain name to securely query the service without 965 using a well-known value like a domain name. The OPTIONAL 966 "validatorID" attribute is the Validator Identifier 967 (Section 2.2) whose value indicates which Trademark Validator 968 to query for the Claims Notice information, with the default 969 being the ICANN TMCH. The "validatorID" attribute MAY 970 reference a non-trademark claims clearinghouse identifer to 971 support other forms of claims notices. 973 Example Trademark Check response when no matching trademarks are 974 found for the domain name domain1.example, matching trademarks are 975 found for the domain name domain2.example in the "tmch", matching 976 trademarks are found for domain name domain3.example in the "tmch" 977 and "custom-tmch", for the "claims" launch phase: 979 S: 980 S: 981 S: 982 S: 983 S: Command completed successfully 984 S: 985 S: 986 S: 988 S: 989 S: domain1.example 990 S: 991 S: 992 S: domain2.example 993 S: 994 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 995 S: 996 S: 997 S: 998 S: domain3.example 999 S: 1000 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 1001 S: 1002 S: 1003 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 1004 S: 1005 S: 1006 S: 1007 S: 1008 S: 1009 S: ABC-12345 1010 S: 54321-XYZ 1011 S: 1012 S: 1013 S: 1015 3.2. EPP Command 1017 This extension defines additional elements to extend the EPP 1018 command and response to be used in conjunction with the EPP domain 1019 name mapping [RFC5731]. 1021 The EPP command is used to retrieve information for a launch 1022 phase registration or application. The Application Identifier 1023 (Section 2.1) returned in the element of the create 1024 response (Section 3.3) is used for retrieving information for a 1025 Launch Application. A element is sent along with the 1026 regular domain command. The element includes an 1027 OPTIONAL "includeMark" boolean attribute, with a default value of 1028 "false", to indicate whether or not to include the mark in the 1029 response. The element contains the following child 1030 elements: 1032 The phase during which the application or 1033 registration was submitted or is associated with. Server policy 1034 defines the phases that are supported. 1035 OPTIONAL application identifier of the Launch 1036 Application. 1038 Example domain command with the extension to 1039 retrieve information for the sunrise application for domain.example 1040 and application identifier "abc123": 1042 C: 1043 C: 1044 C: 1045 C: 1046 C: 1048 C: domain.example 1049 C: 1050 C: 1051 C: 1052 C: 1055 C: sunrise 1056 C: abc123 1057 C: 1058 C: 1059 C: ABC-12345 1060 C: 1061 C: 1062 Example domain command with the extension to 1063 retrieve information for the sunrise registration for domain.example: 1065 C: 1066 C: 1067 C: 1068 C: 1069 C: 1071 C: domain.example 1072 C: 1073 C: 1074 C: 1075 C: 1077 C: sunrise 1078 C: 1079 C: 1080 C: ABC-12345 1081 C: 1082 C: 1084 If the query was successful, the server replies with a 1085 element along with the regular EPP . The 1086 contains the following child elements: 1088 The phase during which the application was submitted, 1089 or is associated with, that matches the associated command 1090 . 1091 OPTIONAL Application Identifier of the Launch 1092 Application. 1093 OPTIONAL status of the Launch Application using one 1094 of the supported status values (Section 2.4). 1095 Zero or more (Section 2.6.2) elements. 1097 Example domain response using the extension 1098 with the mark information: 1100 S: 1101 S: 1102 S: 1103 S: 1104 S: Command completed successfully 1105 S: 1106 S: 1107 S: 1109 S: domain.example 1110 S: EXAMPLE1-REP 1111 S: 1112 S: jd1234 1113 S: sh8013 1114 S: sh8013 1115 S: ClientX 1116 S: ClientY 1117 S: 2012-04-03T22:00:00.0Z 1118 S: 1119 S: 2fooBAR 1120 S: 1121 S: 1122 S: 1123 S: 1124 S: 1126 S: sunrise 1127 S: abc123 1128 S: 1129 S: 1131 S: ... 1132 S: 1133 S: 1134 S: 1135 S: 1136 S: ABC-12345 1137 S: 54321-XYZ 1138 S: 1139 S: 1140 S: 1142 3.3. EPP Command 1144 There are four forms of the extension to the EPP command 1145 that include the Sunrise Create Form (Section 3.3.1), the Claims 1146 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 1147 and the Mixed Create Form (Section 3.3.4). The form is dependent on 1148 the supported launch phases (Section 2.3) as defined below. 1150 sunrise The EPP command with the "sunrise" launch phase is 1151 used to submit a registration with trademark information that can 1152 be verified by the server with the value. The 1153 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 1154 launch phase. 1155 landrush The EPP command with the "landrush" launch phase 1156 MAY use the General Create Form (Section 3.3.3) to explicitly 1157 specify the phase and optionally define the expected type of 1158 object to create. 1159 claims The EPP command with the "claims" launch phase is 1160 used to pass the information associated with the presentation and 1161 acceptance of the Claims Notice. The Claims Create Form 1162 (Section 3.3.2) is used and the General Create Form 1163 (Section 3.3.3) MAY be used for the "claims" launch phase. 1164 open The EPP command with the "open" launch phase is 1165 undefined but the form supported is up to server policy. Use of 1166 the Claims Create Form (Section 3.3.2) MAY be used to pass the 1167 information associated with the presentation and acceptance of the 1168 Claims Notice if required for the domain name. 1169 custom The EPP command with the "custom" launch phase is 1170 undefined but the form supported is up to server policy. 1172 3.3.1. Sunrise Create Form 1174 The Sunrise Create Form of the extension to the EPP domain name 1175 mapping [RFC5731] includes the verifiable trademark information that 1176 the server uses to match against the domain name to authorize the 1177 domain create. A server MUST support one of four models in Claim 1178 Validation Models (Section 2.6) to verify the trademark information 1179 passed by the client. 1181 A element is sent along with the regular 1182 domain command. The element has an OPTIONAL "type" 1183 attribute that defines the expected type of object ("application" or 1184 "registration") to create. The server SHOULD validate the "type" 1185 attribute, when passed, against the type of object that will be 1186 created. The element contains the following child 1187 elements: 1189 The identifier for the launch phase. 1191 or or 1193 Zero or more elements. The 1194 child elements are defined in the 1195 element (Section 2.6.1) section. 1196 Zero or more elements. The 1197 child elements are defined in the 1198 element (Section 2.6.3.1) section. 1199 Zero or more 1200 elements. The child elements are 1201 defined in the element 1202 (Section 2.6.3.2) section. 1204 The following is an example domain command using the 1205 extension, following the "code" validation model, 1206 with multiple sunrise codes: 1208 C: 1209 C: 1210 C: 1211 C: 1212 C: 1214 C: domain.example 1215 C: jd1234 1216 C: sh8013 1217 C: sh8013 1218 C: 1219 C: 2fooBAR 1220 C: 1221 C: 1222 C: 1223 C: 1224 C: 1226 C: sunrise 1227 C: 1228 C: 1229 C: 49FD46E6C4B45C55D4AC 1230 C: 1231 C: 1232 C: 49FD46E6C4B45C55D4AD 1233 C: 1234 C: 1235 C: 1236 C: 49FD46E6C4B45C55D4AE 1237 C: 1238 C: 1239 C: 1240 C: ABC-12345 1241 C: 1242 C: 1243 The following is an example domain command using the 1244 extension, following the "mark" validation model, 1245 with the mark information: 1247 C: 1248 C: 1249 C: 1250 C: 1251 C: 1253 C: domainone.example 1254 C: jd1234 1255 C: sh8013 1256 C: sh8013 1257 C: 1258 C: 2fooBAR 1259 C: 1260 C: 1261 C: 1262 C: 1263 C: 1265 C: sunrise 1266 C: 1267 C: 1269 C: ... 1270 C: 1271 C: 1272 C: 1273 C: 1274 C: ABC-12345 1275 C: 1276 C: 1277 The following is an example domain command using the 1278 extension, following the "code with mark" validation 1279 model, with a code and mark information: 1281 C: 1282 C: 1283 C: 1284 C: 1285 C: 1287 C: domain.example 1288 C: jd1234 1289 C: sh8013 1290 C: sh8013 1291 C: 1292 C: 2fooBAR 1293 C: 1294 C: 1295 C: 1296 C: 1297 C: 1299 C: sunrise 1300 C: 1301 C: 1302 C: 49FD46E6C4B45C55D4AC 1303 C: 1305 C: ... 1306 C: 1307 C: 1308 C: 1309 C: 1310 C: ABC-12345 1311 C: 1312 C: 1313 The following is an example domain command using the 1314 extension, following the "signed mark" validation 1315 model, with the signed mark information for a sunrise application: 1317 C: 1318 C: 1319 C: 1320 C: 1321 C: 1323 C: domainone.example 1324 C: jd1234 1325 C: sh8013 1326 C: sh8013 1327 C: 1328 C: 2fooBAR 1329 C: 1330 C: 1331 C: 1332 C: 1333 C: 1336 C: sunrise 1337 C: 1339 C: ... 1340 C: 1341 C: 1342 C: 1343 C: ABC-12345 1344 C: 1345 C: 1346 The following is an example domain command using the 1347 extension, following the "signed mark" validation 1348 model, with the base64 encoded signed mark information: 1350 C: 1351 C: 1352 C: 1353 C: 1354 C: 1356 C: domainone.example 1357 C: jd1234 1358 C: sh8013 1359 C: sh8013 1360 C: 1361 C: 2fooBAR 1362 C: 1363 C: 1364 C: 1365 C: 1366 C: 1368 C: sunrise 1369 C: 1371 C: ... 1372 C: 1373 C: 1374 C: 1375 C: ABC-12345 1376 C: 1377 C: 1379 3.3.2. Claims Create Form 1381 The Claims Create Form of the extension to the EPP domain name 1382 mapping [RFC5731] includes the information related to the 1383 registrant's acceptance of the Claims Notice. 1385 A element is sent along with the regular 1386 domain command. The element has an OPTIONAL "type" 1387 attribute that defines the expected type of object ("application" or 1388 "registration") to create. The server SHOULD validate the "type" 1389 attribute, when passed, against the type of object that will be 1390 created. The element contains the following child 1391 elements: 1393 Contains the value of the active launch phase of the 1394 server. The server SHOULD validate the value against the active 1395 server launch phase. 1396 One or more elements that contain 1397 the following child elements: 1399 Unique notice identifier for the Claims 1400 Notice. The element has an OPTIONAL 1401 "validatorID" attribute is the Validator Identifier 1402 (Section 2.2) whose value indicates which Trademark Validator 1403 is the source of the claims notice, with the default being 1404 the ICANN TMCH. 1405 Expiry of the claims notice. 1406 Contains the date and time that the claims 1407 notice was accepted. 1409 The following is an example domain command using the 1410 extension with the information for 1411 the "tmch" and the "custom-tmch" validators, for the "claims" launch 1412 phase: 1414 C: 1415 C: 1416 C: 1417 C: 1418 C: 1420 C: domain.example 1421 C: jd1234 1422 C: sh8013 1423 C: sh8013 1424 C: 1425 C: 2fooBAR 1426 C: 1427 C: 1428 C: 1429 C: 1430 C: 1432 C: claims 1433 C: 1434 C: 1435 C: 370d0b7c9223372036854775807 1436 C: 2014-06-19T10:00:00.0Z 1437 C: 1438 C: 2014-06-19T09:00:00.0Z 1439 C: 1440 C: 1441 C: 1442 C: 1443 C: 470d0b7c9223654313275808 1444 C: 2014-06-19T10:00:00.0Z 1445 C: 1446 C: 2014-06-19T09:00:30.0Z 1447 C: 1448 C: 1449 C: 1450 C: 1451 C: ABC-12345 1452 C: 1453 C: 1455 3.3.3. General Create Form 1457 The General Create Form of the extension to the EPP domain name 1458 mapping [RFC5731] includes the launch phase and optionally the object 1459 type to create. The OPTIONAL "type" attribute defines the expected 1460 type of object ("application" or "registration") to create. The 1461 server SHOULD validate the "type" attribute, when passed, against the 1462 type of object that will be created. 1464 A element is sent along with the regular 1465 domain command. The element contains the following 1466 child elements: 1468 Contains the value of the active launch phase of the 1469 server. The server SHOULD validate the value against the active 1470 server launch phase. 1472 The following is an example domain command using the 1473 extension for a "landrush" launch phase application: 1475 C: 1476 C: 1477 C: 1478 C: 1479 C: 1481 C: domain.example 1482 C: jd1234 1483 C: sh8013 1484 C: sh8013 1485 C: 1486 C: 2fooBAR 1487 C: 1488 C: 1489 C: 1490 C: 1491 C: 1494 C: landrush 1495 C: 1496 C: 1497 C: ABC-12345 1498 C: 1499 C: 1501 3.3.4. Mixed Create Form 1503 The Mixed Create Form supports a mix of the create forms, where for 1504 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1505 Form (Section 3.3.2) MAY be supported in a single command by 1506 including both the verified trademark information and the information 1507 related to the registrant's acceptance of the Claims Notice. The 1508 server MAY support the Mixed Create Form. The "custom" launch phase 1509 SHOULD be used when using the Mixed Create Form. 1511 The following is an example domain command using the 1512 extension, with using a mix of the Sunrise Create 1513 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1514 including both a mark and a notice: 1516 C: 1517 C: 1518 C: 1519 C: 1520 C: 1522 C: domainone.example 1523 C: jd1234 1524 C: sh8013 1525 C: sh8013 1526 C: 1527 C: 2fooBAR 1528 C: 1529 C: 1530 C: 1531 C: 1532 C: 1535 C: custom 1536 C: 1537 C: 1539 C: ... 1540 C: 1541 C: 1542 C: 1543 C: 1544 C: 49FD46E6C4B45C55D4AC 1545 C: 1546 C: 2012-06-19T10:00:10.0Z 1547 C: 1548 C: 2012-06-19T09:01:30.0Z 1549 C: 1550 C: 1551 C: 1552 C: 1553 C: ABC-12345 1554 C: 1555 C: 1557 3.3.5. Create Response 1559 If the create was successful, the server MAY reply with the 1560 element along with the regular EPP to 1561 indicate the server generated Application Identifier (Section 2.1), 1562 when multiple applications of a given domain name are supported; 1563 otherwise no extension is included with the regular EPP . 1564 The element contains the following child elements: 1566 The phase of the application that mirrors the 1567 element included in the . 1568 The application identifier of the 1569 application. 1571 An example response when multiple overlapping applications are 1572 supported by the server: 1574 S: 1575 S: 1576 S: 1577 S: 1578 S: Command completed successfully; action pending 1579 S: 1580 S: 1581 S: 1583 S: domain.example 1584 S: 2010-08-10T15:38:26.623854Z 1585 S: 1586 S: 1587 S: 1588 S: 1590 S: sunrise 1591 S: 2393-9323-E08C-03B1 1592 S: 1593 S: 1594 S: 1595 S: 1596 S: ABC-12345 1597 S: 54321-XYZ 1598 S: 1599 S: 1600 S: 1602 3.4. EPP Command 1604 This extension defines additional elements to extend the EPP 1605 command to be used in conjunction with the domain name mapping. 1607 A client MUST NOT pass the extension on an EPP command to a 1608 server that does not support launch applications. A server that does 1609 not support launch applications during its launch phase MUST return 1610 an EPP error result code of 2102 when receiving an EPP 1611 command with the extension. 1613 Registry policies permitting, clients may update an application 1614 object by submitting an EPP command along with a 1615 element to indicate the application object to be 1616 updated. The element contains the following child 1617 elements: 1619 The phase during which the application was submitted 1620 or is associated with. 1621 The application identifier for which the 1622 client wishes to update. 1624 The following is an example domain command with the 1625 extension to add and remove a name server of a 1626 sunrise application with the application identifier "abc123": 1628 C: 1629 C: 1630 C: 1631 C: 1632 C: 1634 C: domain.example 1635 C: 1636 C: 1637 C: ns2.domain.example 1638 C: 1639 C: 1640 C: 1641 C: 1642 C: ns1.domain.example 1643 C: 1644 C: 1645 C: 1646 C: 1647 C: 1648 C: 1650 C: sunrise 1651 C: abc123 1652 C: 1653 C: 1654 C: ABC-12345 1655 C: 1656 C: 1658 This extension does not define any extension to the response of an 1659 domain command. After processing the command, the server 1660 replies with a standard EPP response as defined in the EPP domain 1661 name mapping [RFC5731]. 1663 3.5. EPP Command 1665 This extension defines additional elements to extend the EPP 1666 command to be used in conjunction with the domain name mapping. 1668 A client MUST NOT pass the extension on an EPP command to a 1669 server that does not support launch applications. A server that does 1670 not support launch applications during its launch phase MUST return 1671 an EPP error result code of 2102 when receiving an EPP 1672 command with the extension. 1674 Registry policies permitting, clients MAY withdraw an application by 1675 submitting an EPP command along with a 1676 element to indicate the application object to be deleted. The 1677 element contains the following child elements: 1679 The phase during which the application was submitted 1680 or is associated with. 1681 The application identifier for which the 1682 client wishes to delete. 1684 The following is an example domain command with the 1685 extension: 1687 C: 1688 C: 1689 C: 1690 C: 1691 C: 1693 C: domain.example 1694 C: 1695 C: 1696 C: 1697 C: 1699 C: sunrise 1700 C: abc123 1701 C: 1702 C: 1703 C: ABC-12345 1704 C: 1705 C: 1707 This extension does not define any extension to the response of a 1708 domain command. After processing the command, the server 1709 replies with a standard EPP response as defined in the EPP domain 1710 name mapping [RFC5731]. 1712 3.6. EPP Command 1714 This extension does not define any extension to the EPP 1715 command or response described in the EPP domain name mapping 1716 [RFC5731]. 1718 3.7. EPP Command 1720 This extension does not define any extension to the EPP 1721 command or response described in the EPP domain name mapping 1722 [RFC5731]. 1724 4. Formal Syntax 1726 One schema is presented here that is the EPP Launch Phase Mapping 1727 schema. 1729 The formal syntax presented here is a complete schema representation 1730 of the object mapping suitable for automated validation of EPP XML 1731 instances. The BEGIN and END tags are not part of the schema; they 1732 are used to note the beginning and ending of the schema for URI 1733 registration purposes. 1735 4.1. Launch Schema 1737 Copyright (c) 2017 IETF Trust and the persons identified as authors 1738 of the code. All rights reserved. 1740 Redistribution and use in source and binary forms, with or without 1741 modification, are permitted provided that the following conditions 1742 are met: 1744 o Redistributions of source code must retain the above copyright 1745 notice, this list of conditions and the following disclaimer. 1746 o Redistributions in binary form must reproduce the above copyright 1747 notice, this list of conditions and the following disclaimer in 1748 the documentation and/or other materials provided with the 1749 distribution. 1750 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1751 names of specific contributors, may be used to endorse or promote 1752 products derived from this software without specific prior written 1753 permission. 1755 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1756 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1757 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1758 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1759 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1760 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1761 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1762 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1763 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1764 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1765 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1767 BEGIN 1768 1769 1778 1781 1782 1783 1785 1786 1787 Extensible Provisioning Protocol v1.0 1788 domain name extension schema 1789 for the launch phase processing. 1790 1791 1793 1796 1797 1798 1799 1800 1802 1805 1806 1807 1809 1811 1812 1814 1817 1818 1819 1821 1827 1828 1829 1830 1831 1832 1833 1835 1838 1839 1840 1841 1842 1843 1844 1845 1846 1848 1851 1852 1853 1854 1855 1857 1858 1859 1860 1863 1864 1865 1867 1870 1871 1872 1873 1874 1876 1877 1878 1879 1881 1882 1883 1885 1888 1889 1890 1891 1892 1894 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1909 1912 1913 1914 1915 1917 1919 1920 1921 1922 1924 1928 1929 1930 1932 1934 1935 1937 1940 1941 1942 1943 1944 1946 1948 1950 1951 1954 1955 1956 1958 1961 1962 1963 1964 1965 1966 1968 1971 1972 1973 1974 1975 1976 1977 1979 1982 1983 1984 1986 1987 1989 1991 1995 1996 1997 1998 1999 2000 2001 2002 2005 2006 2007 2008 2011 2012 2014 2016 2019 2020 2021 2023 2026 2027 2028 2030 2032 2033 2035 2036 2037 2038 2040 2041 2043 2044 2045 2046 2048 2049 2051 2053 2054 2055 2056 2058 2059 2060 2062 2065 2066 2067 2068 2071 2073 2075 2076 2078 2079 END 2081 5. IANA Considerations 2083 5.1. XML Namespace 2085 This document uses URNs to describe XML namespaces and XML schemas 2086 conforming to a registry mechanism described in [RFC3688]. 2088 Registration request for the launch namespace: 2090 URI: urn:ietf:params:xml:ns:launch-1.0 2091 Registrant Contact: See the "Author's Address" section of this 2092 document. 2093 XML: None. Namespace URIs do not represent an XML specification. 2095 Registration request for the launch XML schema: 2097 URI: urn:ietf:params:xml:schema:launch-1.0 2098 Registrant Contact: See the "Author's Address" section of this 2099 document. 2100 XML: See the "Formal Syntax" section of this document. 2102 5.2. EPP Extension Registry 2104 The EPP extension described in this document should be registered by 2105 the IANA in the EPP Extension Registry described in [RFC7451]. The 2106 details of the registration are as follows: 2108 Name of Extension: "Launch Phase Mapping for the Extensible 2109 Provisioning Protocol (EPP)" 2111 Document status: Standards Track 2113 Reference: (insert reference to RFC version of this document) 2115 Registrant Name and Email Address: IESG, 2117 TLDs: Any 2119 IPR Disclosure: None 2121 Status: Active 2123 Notes: None 2125 6. Implementation Status 2127 Note to RFC Editor: Please remove this section and the reference to 2128 RFC 6982 [RFC6982] before publication. 2130 This section records the status of known implementations of the 2131 protocol defined by this specification at the time of posting of this 2132 Internet-Draft, and is based on a proposal described in RFC 6982 2133 [RFC6982]. The description of implementations in this section is 2134 intended to assist the IETF in its decision processes in progressing 2135 drafts to RFCs. Please note that the listing of any individual 2136 implementation here does not imply endorsement by the IETF. 2137 Furthermore, no effort has been spent to verify the information 2138 presented here that was supplied by IETF contributors. This is not 2139 intended as, and must not be construed to be, a catalog of available 2140 implementations or their features. Readers are advised to note that 2141 other implementations may exist. 2143 According to RFC 6982 [RFC6982], "this will allow reviewers and 2144 working groups to assign due consideration to documents that have the 2145 benefit of running code, which may serve as evidence of valuable 2146 experimentation and feedback that have made the implemented protocols 2147 more mature. It is up to the individual working groups to use this 2148 information as they see fit". 2150 6.1. Verisign EPP SDK 2152 Organization: Verisign Inc. 2154 Name: Verisign EPP SDK 2156 Description: The Verisign EPP SDK includes both a full client 2157 implementation and a full server stub implementation of draft-ietf- 2158 regext-launchphase. 2160 Level of maturity: Production 2162 Coverage: All aspects of the protocol are implemented. 2164 Licensing: GNU Lesser General Public License 2166 Contact: jgould@verisign.com 2168 URL: http://www.verisigninc.com/en_US/channel-resources/domain- 2169 registry-products/epp-sdks 2171 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 2173 Organization: Verisign Inc. 2175 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 2176 System (SRS) 2178 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 2179 Registry System (SRS) implements the server-side of draft-ietf- 2180 regext-launchphase for a variety of Top Level Domains (TLD's). 2182 Level of maturity: Production 2184 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2185 Form for the EPP Command, the Sunrise and Claims Forms for 2186 the EPP Command of Launch Registrations and Launch 2187 Applications. For Launch Applications the Poll Messaging, the EPP 2188 Command, the EPP Command, and the EPP 2189 Command is covered. 2191 Licensing: Proprietary 2193 Contact: jgould@verisign.com 2195 6.3. Verisign .COM / .NET SRS 2197 Organization: Verisign Inc. 2199 Name: Verisign .COM / .NET Shared Registry System (SRS) 2201 Description: The Verisign Shared Registry System (SRS) for .COM, .NET 2202 and other IDN TLD's implements the server-side of draft-ietf-regext- 2203 launchphase. 2205 Level of maturity: Operational Test Environment (OTE) 2207 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2208 Form for the EPP Command, the Sunrise and Claims Forms for 2209 the EPP Command of Launch Registrations. 2211 Licensing: Proprietary 2213 Contact: jgould@verisign.com 2215 6.4. REngin v3.7 2217 Organization: Domain Name Services (Pty) Ltd 2219 Name: REngin v3.7 2221 Description: Server side implementation only 2223 Level of maturity: Production 2225 Coverage: All features from version 12 have been implemented 2227 Licensing: Proprietary Licensing with Maintenance Contracts 2229 Contact: info@dnservices.co.za 2231 URL: https://www.registry.net.za and soon http://dnservices.co.za 2233 6.5. RegistryEngine EPP Service 2235 Organization: CentralNic 2237 Name: RegistryEngine EPP Service 2239 Description: Generic high-volume EPP service for gTLDs, ccTLDs and 2240 SLDs 2241 Level of maturity: Deployed in CentralNic's production environment as 2242 well as two other gTLD registry systems, and two ccTLD registry 2243 systems. 2245 Coverage: Majority of elements including TMCH sunrise, landrush and 2246 TM claims as well as sunrise applications validated using codes. 2248 Licensing: Proprietary In-House software 2250 Contact: epp@centralnic.com 2252 URL: https://www.centralnic.com 2254 6.6. Neustar EPP SDK 2256 Organization: Neustar 2258 Name: Neustar EPP SDK 2260 Description: The Neustar EPP SDK includes client implementation of 2261 draft-ietf-regext-launchphase in both Java and C++. 2263 Level of maturity: Production 2265 Coverage: All aspects of the protocol are implemented. 2267 Licensing: GNU Lesser General Public License 2269 Contact: trung.tran@neustar.biz 2271 6.7. gTLD Shared Registry System 2273 Organization: Stichting Internet Domeinnaamregistratie Nederland 2274 (SIDN) 2276 Name: gTLD Shared Registry System 2278 Description: The gTLD SRS implements the server side of the draft- 2279 ietf-regext-launchphase. 2281 Level of maturity: (soon) Production 2283 Coverage: The following parts of the draft are supported: 2285 Signed mark validation model using Digital Signature 2286 (Section 2.6.3) 2287 Claims Check Form (Section 3.1.1) 2288 Sunrise Create Form (Section 3.3.1) 2289 Claims Create Form (Section 3.3.2) 2291 The parts of the document not described here are not implemented. 2293 Licensing: Proprietary 2295 Contact: rik.ribbers@sidn.nl 2297 7. Security Considerations 2299 The mapping extensions described in this document do not provide any 2300 security services beyond those described by EPP [RFC5730], the EPP 2301 domain name mapping [RFC5731], and protocol layers used by EPP. The 2302 security considerations described in these other specifications apply 2303 to this specification as well. 2305 Updates to, and deletion of an application object must be restricted 2306 to clients authorized to perform the said operation on the object. 2308 As information contained within an application, or even the mere fact 2309 that an application exists may be confidential. Any attempt to 2310 operate on an application object by an unauthorized client MUST be 2311 rejected with an EPP 2201 (authorization error) return code. Server 2312 policy may allow operation with filtered output by clients 2313 other than the sponsoring client, in which case the 2314 and response SHOULD be filtered to include only 2315 fields that are publicly accessible. 2317 8. Acknowledgements 2319 The authors wish to acknowledge the efforts of the leading 2320 participants of the Community TMCH Model that led to many of the 2321 changes to this document, which include Chris Wright, Jeff Neuman, 2322 Jeff Eckhaus, and Will Shorter. 2324 Special suggestions that have been incorporated into this document 2325 were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Scott 2326 Hollenbeck, Michael Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, 2327 Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Patrick Mevzek, 2328 James Mitchell, Francisco Obispo, Mike O'Connell, Bernhard Reutner- 2329 Fischer, Trung Tran, Ulrich Wisser and Sharon Wodjenski. 2331 Some of the description of the Trademark Claims Phase was based on 2332 the work done by Gustavo Lozano in the ICANN TMCH functional 2333 specifications. 2335 9. Normative References 2337 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2338 Requirement Levels", BCP 14, RFC 2119, 2339 DOI 10.17487/RFC2119, March 1997, 2340 . 2342 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2343 DOI 10.17487/RFC3688, January 2004, 2344 . 2346 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2347 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 2348 . 2350 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2351 Domain Name Mapping", STD 69, RFC 5731, 2352 DOI 10.17487/RFC5731, August 2009, 2353 . 2355 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 2356 Code: The Implementation Status Section", RFC 6982, 2357 DOI 10.17487/RFC6982, July 2013, 2358 . 2360 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 2361 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 2362 February 2015, . 2364 [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", 2365 RFC 7848, DOI 10.17487/RFC7848, June 2016, 2366 . 2368 Appendix A. Change History 2370 A.1. Change from 00 to 01 2372 1. Changed to use camel case for the XML elements. 2373 2. Replaced "cancelled" status to "rejected" status. 2374 3. Added the child elements of the element. 2375 4. Removed the XML schema and replaced with "[TBD]". 2377 A.2. Change from 01 to 02 2379 1. Added support for both the ICANN and ARI/Neustar TMCH models. 2380 2. Changed the namespace URI and prefix to use "launch" instead of 2381 "launchphase". 2382 3. Added definition of multiple claim validation models. 2384 4. Added the and 2385 elements. 2386 5. Added support for Claims Info Command 2388 A.3. Change from 02 to 03 2390 1. Removed XSI namespace per Keith Gaughan's suggestion on the 2391 provreg list. 2392 2. Added extensibility to the launch:status element and added the 2393 pendingAuction status per Trung Tran's feedback on the provreg 2394 list. 2395 3. Added support for the Claims Check Command, updated the location 2396 and contents of the signedNotice, and replaced most references of 2397 Claim to Mark based on the work being done on the ARI/Neustar 2398 launch model. 2400 A.4. Change from 03 to 04 2402 1. Removed references to the ICANN model. 2403 2. Removed support for the Claims Info Command. 2404 3. Removed use of the signedClaim. 2405 4. Revised the method for referring to the signedClaim from the XML 2406 Signature using the IDREF URI. 2407 5. Split the launch-1.0.xsd into three XML schemas including launch- 2408 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 2409 6. Split the "claims" launch phase to the "claims1" and "claims2" 2410 launch phases. 2411 7. Added support for the encodedSignedMark with base64 encoded 2412 signedMark. 2413 8. Changed the elements in the createNoticeType to include the 2414 noticeID, timestamp, and the source elements. 2415 9. Added the class and effectiveDate elements to mark. 2417 A.5. Change from 04 to 05 2419 1. Removed reference to in the example. 2420 2. Incorporated feedback from Bernhard Reutner-Fischer on the 2421 provreg mail list. 2422 3. Added missing launch XML prefix to applicationIDType reference in 2423 the idContainerType of the Launch Schema. 2424 4. Added missing description of the element in the 2425 element. 2426 5. Updated note on replication of the EPP contact mapping elements 2427 in the Mark Contact section. 2429 A.6. Change from 05 to 06 2431 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 2432 replaced with reference to draft-lozano-smd, that contains the 2433 definition for the mark, signed marked, and encoded signed mark. 2434 2. Split the into and 2435 based on feedback from Trung Tran. 2436 3. Added the "includeMark" optional attribute to the 2437 element to enable the client to request whether or not to include 2438 the mark in the info response. 2439 4. Fixed state diagram to remove redundant transition from "invalid" 2440 to "rejected"; thanks Klaus Malorny. 2442 A.7. Change from 06 to 07 2444 1. Proof-read grammar and spelling. 2445 2. Changed "pendingAuction" status to "pendingAllocation", changed 2446 "pending" to "pendingValidation" status, per proposal from Trung 2447 Tran and seconded by Rubens Kuhl. 2448 3. Added text related to the use of RFC 5731 pendingCreate to the 2449 Application Identifier section. 2450 4. Added the Poll Messaging section to define the use of poll 2451 messaging for intermediate state transitions and pending action 2452 poll messaging for final state transitions. 2454 A.8. Change from 07 to 08 2456 1. Added support for use of the launch statuses and poll messaging 2457 for Launch Registrations based on feedback from Sharon Wodjenski 2458 and Trung Tran. 2459 2. Incorporated changes based on updates or clarifications in draft- 2460 lozano-tmch-func-spec-01, which include: 2462 1. Removed the unused element. 2463 2. Removed the element. 2464 3. Added the element based on the required 2465 element. 2467 A.9. Change from 08 to 09 2469 1. Made element optional in to allow 2470 passing just the in per request 2471 from Ben Levac. 2472 2. Added optional "type" attribute in to enable the 2473 client to explicitly define the desired type of object 2474 (application or registration) to create to all forms of the 2475 create extension. 2477 3. Added text that the server SHOULD validate the 2478 element in the Launch Phases section. 2479 4. Add the "General Create Form" to the create command extension to 2480 support the request from Ben Levac. 2481 5. Updated the text for the Poll Messaging section based on feedback 2482 from Klaus Malorny. 2483 6. Replaced the "claims1" and "claims2" phases with the "claims" 2484 phase based on discussion on the provreg list. 2485 7. Added support for a mixed create model (Sunrise Create Model and 2486 Claims Create Model), where a trademark (encoded signed mark, 2487 etc.) and notice can be passed, based on a request from James 2488 Mitchell. 2489 8. Added text for the handling of the overlapping "claims" and 2490 "landrush" launch phases. 2491 9. Added support for two check forms (claims check form and 2492 availability check form) based on a request from James Mitchell. 2493 The availability check form was based on the text in draft-rbp- 2494 application-epp-mapping. 2496 A.10. Change from 09 to 10 2498 1. Changed noticeIDType from base64Binary to token to be compatible 2499 with draft-lozano-tmch-func-spec-05. 2500 2. Changed codeType from base64Binary to token to be more generic. 2501 3. Updated based on feedback from Alexander Mayrhofer, which 2502 include: 2504 1. Changed "extension to the domain name extension" to 2505 "extension to the domain name mapping". 2506 2. Changed use of 2004 return code to 2306 return code when 2507 phase passed mismatches active phase and sub-phase. 2508 3. Changed description of "allocated" and "rejected" statuses. 2509 4. Moved sentence on a synchronous command 2510 without the use of an intermediate application, then an 2511 Application Identifier MAY not be needed to the Application 2512 Identifier section. 2513 5. Restructured the Mark Validation Models section to include 2514 the " element" sub-section, the 2515 " element" sub-section, and the Digital Signature 2516 sub-section. 2517 6. Changed "Registries may" to "Registries MAY". 2518 7. Changed "extensed" to "extended" in "Availability Check 2519 Form" section. 2520 8. Broke the mix of create forms in the "EPP Command" 2521 section to a fourth "Mixed Create Form" with its own sub- 2522 section. 2523 9. Removed "displayed or" from "displayed or accepted" in the 2524 description. 2526 10. Replaced "given domain name is supported" with "given domain 2527 name are supported" in the "Create Response" section. 2528 11. Changed the reference of 2303 (object does not exist) in the 2529 "Security Considerations" section to 2201 (authorization 2530 error). 2531 12. Added arrow from "invalid" status to "pendingValidation" 2532 status and "pendingAllocation" status to "rejected" status 2533 in the State Transition Diagram. 2534 4. Added the "C:" and "S:" example prefixes and related text in the 2535 "Conventions Used in This Document" section. 2537 A.11. Change from 10 to 11 2539 1. Moved the claims check response element under 2540 the element instead of the element based on 2541 the request from Francisco Obispo. 2543 A.12. Change from 11 to 12 2545 1. Added support for multiple validator identifiers for claims 2546 notices and marks based on a request and text provided by Mike 2547 O'Connell. 2548 2. Removed domain:exDate element from example in section 3.3.5 based 2549 on a request from Seth Goldman on the provreg list. 2550 3. Added clarifying text for clients not passing the launch 2551 extension on update and delete commands to servers that do not 2552 support launch applications based on a request from Sharon 2553 Wodjenski on the provreg list. 2555 A.13. Change from 12 to EPPEXT 00 2557 1. Changed to eppext working group draft by changing draft-tan-epp- 2558 launchphase to draft-ietf-eppext-launchphase and by changing 2559 references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch- 2560 smd. 2562 A.14. Change EPPEXT 00 to EPPEXT 01 2564 1. Removed text associated with support for the combining of status 2565 values based on feedback from Patrick Mevzek on the provreg 2566 mailing list, discussion on the eppext mailing list, and 2567 discussion at the eppext IETF meeting on March 6, 2014. 2569 A.15. Change EPPEXT 01 to EPPEXT 02 2571 1. Changed the element to be zero or more elements 2572 and the element to be one or more elements in the 2573 Claims Create Form. These changes were needed to be able to 2574 support more than one concurrent claims services. 2576 A.16. Change EPPEXT 02 to EPPEXT 03 2578 1. Added the "Implementation Status" section based on an action item 2579 from the eppext IETF-91 meeting. 2580 2. Moved Section 7 "IANA Considerations" and Section 9 "Security 2581 Considerations" before Section 5 "Acknowledgements". Moved 2582 "Change Log" Section to end. 2583 3. Updated the text for the Claims Check Form and the Claims Create 2584 Form to support checking for the need of the claims notice and 2585 passing the claims notice outside of the "claims" phase. 2586 4. Added the new Trademark Check Form to support determining whether 2587 or not a trademark exists that matches the domain name 2588 independent of whether a claims notice is required on create. 2589 This was based on a request from Trung Tran and a discussion on 2590 the eppext mailing list. 2592 A.17. Change EPPEXT 03 to EPPEXT 04 2594 1. Amended XML Namespace section of IANA Considerations, added EPP 2595 Extension Registry section. 2597 A.18. Change EPPEXT 04 to EPPEXT 05 2599 1. Added a missing comma to the descripton of the 2600 element, based on feedback from Keith Gaughan on the eppext 2601 mailing list. 2602 2. Added the SIDN implementation status information. 2603 3. Fixed a few indentation issues in the samples. 2605 A.19. Change EPPEXT 05 to EPPEXT 06 2607 1. Removed duplicate "TMCH Functional Specification" URIs based on 2608 feedback from Scott Hollenbeck on the eppext mailing list. 2609 2. Changed references of example?.tld to domain?.example to be 2610 consistent with RFC 6761 based on feedback from Scott Hollenbeck 2611 on the eppext mailing list. 2612 3. A template was added to section 5 to register the XML schema in 2613 addition to the namespace based on feedback from Scott Hollenbeck 2614 on the eppext mailing list. 2616 A.20. Change EPPEXT 06 to EPPEXT 07 2618 1. Changed reference of lozano-tmch-func-spec to ietf-eppext-tmch- 2619 func-spec. 2621 A.21. Change from EPPEXT 07 to REGEXT 00 2623 1. Changed to regext working group draft by changing draft-ietf- 2624 eppext-launchphase to draft-ietf-regext-launchphase and by 2625 changing references of draft-ietf-eppext-tmch-func-spec to draft- 2626 ietf-regext-tmch-func-spec. 2628 A.22. Change from REGEXT 00 to REGEXT 01 2630 1. Fixed reference of Claims Check Command to Trademark Check 2631 Command in the Trademark Check Form section. 2632 2. Replaced reference of draft-ietf-eppext-tmch-smd to RFC 7848. 2634 A.23. Change from REGEXT 01 to REGEXT 02 2636 1. Removed the reference to ietf-regext-tmch-func-spec and briefly 2637 described the trademark claims phase that is relavent to draft- 2638 ietf-regext-launchphase. 2640 A.24. Change from REGEXT 02 to REGEXT 03 2642 1. Ping update. 2644 A.25. Change from REGEXT 03 to REGEXT 04 2646 1. Updates based on feedback from Scott Hollenbeck that include: 2648 1. Nit on reference to RFC 7848 in section 1. 2649 2. Added reference to for the request to create 2650 a Launch Application in section 2.1. 2651 3. Removed the second paragraph of section 2.1 describing the 2652 option of creating an application identifier for a Launch 2653 Registration. 2654 4. Provided clarification in section 2.2 on the responsibility 2655 of the server to ensure that the supported validator 2656 identifiers are unique. 2657 5. Updated the text in section 2.5 referencing the domain name 2658 object in RFC 5731. 2659 6. Updated the copyright to 2017 in section 4.1. 2661 Authors' Addresses 2662 James Gould 2663 VeriSign, Inc. 2664 12061 Bluemont Way 2665 Reston, VA 20190 2666 US 2668 Email: jgould@verisign.com 2669 URI: http://www.verisigninc.com 2671 Wil Tan 2672 Cloud Registry 2673 Suite 32 Seabridge House 2674 377 Kent St 2675 Sydney, NSW 2000 2676 AU 2678 Phone: +61 414 710899 2679 Email: wil@cloudregistry.net 2680 URI: http://www.cloudregistry.net 2682 Gavin Brown 2683 CentralNic Ltd 2684 35-39 Mooregate 2685 London, England EC2R 6AR 2686 GB 2688 Phone: +44 20 33 88 0600 2689 Email: gavin.brown@centralnic.com 2690 URI: https://www.centralnic.com