idnits 2.17.1 draft-ietf-regext-launchphase-02.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 (October 27, 2016) is 2738 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: April 30, 2017 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 October 27, 2016 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-ietf-regext-launchphase-02 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 April 30, 2017. 37 Copyright Notice 39 Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . 58 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 . . . . . . . . . . . . . . 61 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 . . . . . . . . . . . 62 124 A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 63 125 A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 63 126 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63 128 1. Introduction 130 This document describes an extension mapping for version 1.0 of the 131 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 132 specifies a flexible schema that can be used to implement several 133 common use cases related to the provisioning and management of domain 134 name registrations and applications during the launch of a domain 135 name registry. 137 It is typical for domain registries to operate in special modes 138 during their initial launch to facilitate allocation of domain names, 139 often according to special rules. This document uses the term 140 "launch phase" and the shorter form "launch" to refer to such a 141 period. 143 The EPP domain name mapping [RFC5731] is designed for the steady- 144 state operation of a registry. During a launch period, the model in 145 place may be different from what is defined in the EPP domain name 146 mapping [RFC5731]. For example, registries often accept multiple 147 applications for the same domain name during the "Sunrise" launch 148 phase, referred to as a Launch Application. A Launch Registration 149 refers to a registration made during a launch phase when the server 150 uses a "first-come, first-served" model. Even in a "first-come, 151 first-served" model, additional steps and information might be 152 required, such as trademark information. In addition, the [RFC7848] 153 defines a registry interface for the Trademark Claims or "claims" 154 launch phase that includes support for presenting a Trademark Claims 155 Notice to the Registrant. This document proposes an extension to the 156 domain name mapping in order to provide a uniform interface for the 157 management of Launch Applications and Launch Registrations in launch 158 phases. 160 1.1. Conventions Used in This Document 162 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 163 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 164 document are to be interpreted as described in RFC 2119 [RFC2119]. 166 XML is case sensitive. Unless stated otherwise, XML specifications 167 and examples provided in this document MUST be interpreted in the 168 character case presented in order to develop a conforming 169 implementation. 171 In examples, "C:" represents lines sent by a protocol client and "S:" 172 represents lines returned by a protocol server. Indentation and 173 white space in examples are provided only to illustrate element 174 relationships and are not a REQUIRED feature of this protocol. 176 "launch-1.0" is used as an abbreviation for 177 "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix 178 "launch" is used, but implementations MUST NOT depend on it and 179 instead employ a proper namespace-aware XML parser and serializer to 180 interpret and output the XML documents. 182 "signedMark-1.0" is used as an abbreviation for 183 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [RFC7848]. 184 The XML namespace prefix "smd" is used, but implementations MUST NOT 185 depend on it and instead employ a proper namespace-aware XML parser 186 and serializer to interpret and output the XML documents. 188 "mark-1.0" is used as an abbreviation for 189 "urn:ietf:params:xml:ns:mark-1.0" that is defined in [RFC7848]. The 190 XML namespace prefix "mark" is used, but implementations MUST NOT 191 depend on it and instead employ a proper namespace-aware XML parser 192 and serializer to interpret and output the XML documents. 194 2. Object Attributes 196 This extension adds additional elements to the EPP domain name 197 mapping [RFC5731]. Only those new elements are described here. 199 2.1. Application Identifier 201 Servers MAY allow multiple applications, referred to as a Launch 202 Application, of the same domain name during its launch phase 203 operations. Upon receiving a valid request to create a Launch 204 Application, the server MUST create an application object 205 corresponding to the request, assign an application identifier for 206 the Launch Application, set the [RFC5731] pendingCreate status, and 207 return the application identifier to the client with the 208 element. In order to facilitate correlation, 209 all subsequent launch operations on the Launch Application MUST be 210 qualified by the previously assigned application identifier using the 211 element. 213 If the command processes a request synchronously 214 without the use of an intermediate Launch Application, then an 215 application identifier MAY not be needed. 217 2.2. Validator Identifier 219 The Validator Identifier is the unique identifier for a Trademark 220 Validator that validates marks and has a repository of validated 221 marks. The OPTIONAL "validatorID" attribute is used to define the 222 Validator Identifier of the Trademark Validator. Registries MAY 223 support more than one Third Party Trademark Validator. The Internet 224 Corporation for Assigned Names and Numbers (ICANN) Trademark 225 Clearinghouse (TMCH) is the default Trademark Validator and is 226 reserved the Validator Identifier of "tmch". If the ICANN TMCH is 227 not used or multiple Trademark Validators are used, the Validator 228 Identifier MUST be defined using the "validatorID" attribute. 230 The Validator Identifier MAY be related to one or more issuer 231 identifiers of the element and the element defined 232 in [RFC7848]. Both the Validator Identifier and the Issuer 233 Identifier used MUST be unique. The list of validator identifiers 234 and the relationship to issuer identifiers is out of scope for this 235 document. 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 a domain name of [RFC5731] in "pendingCreate" status, with the launch 458 status values defined in Section 2.4. As a Launch Application or 459 Launch Registration transitions between the status values defined in 460 Section 2.4, the server SHOULD insert poll messages, per [RFC5730], 461 for the applicable intermediate statuses, including the 462 "pendingValidation", "validated", "pendingAllocation, and "invalid" 463 statuses, using the element with the 464 extension. The element MAY contain 465 non-mandatory information, like contact and name server information. 466 Also, further extensions that would normally be included in the 467 response of a command, per [RFC5731], MAY be included. 468 For the final statuses, including the "allocated" and "rejected" 469 statuses, the server MUST insert a poll message, per 470 [RFC5731], with the extension. 472 The following is an example poll message for a Launch Application 473 that has transitioned to the "pendingAllocation" state. 475 S: 476 S: 477 S: 478 S: 479 S: Command completed successfully; ack to dequeue 480 S: 481 S: 482 S: 2013-04-04T22:01:00.0Z 483 S: Application pendingAllocation. 484 S: 485 S: 486 S: 488 S: domain.example 489 S: ... 490 S: 491 S: 492 S: 493 S: 495 S: sunrise 496 S: abc123 497 S: 498 S: 499 S: 500 S: 501 S: ABC-12345 502 S: 54322-XYZ 503 S: 504 S: 505 S: 506 The following is an example poll message for an 507 "allocated" Launch Application. 509 S: 510 S: 511 S: 512 S: 513 S: Command completed successfully; ack to dequeue 514 S: 515 S: 516 S: 2013-04-04T22:01:00.0Z 517 S: Application successfully allocated. 518 S: 519 S: 520 S: 522 S: domain.example 523 S: 524 S: ABC-12345 525 S: 54321-XYZ 526 S: 527 S: 2013-04-04T22:00:00.0Z 528 S: 529 S: 530 S: 531 S: 533 S: sunrise 534 S: abc123 535 S: 536 S: 537 S: 538 S: 539 S: BCD-23456 540 S: 65432-WXY 541 S: 542 S: 543 S: 544 The following is an example poll message for an 545 "allocated" Launch Registration. 547 S: 548 S: 549 S: 550 S: 551 S: Command completed successfully; ack to dequeue 552 S: 553 S: 554 S: 2013-04-04T22:01:00.0Z 555 S: Registration successfully allocated. 556 S: 557 S: 558 S: 560 S: domain.example 561 S: 562 S: ABC-12345 563 S: 54321-XYZ 564 S: 565 S: 2013-04-04T22:00:00.0Z 566 S: 567 S: 568 S: 569 S: 571 S: sunrise 572 S: 573 S: 574 S: 575 S: 576 S: BCD-23456 577 S: 65432-WXY 578 S: 579 S: 580 S: 582 2.6. Mark Validation Models 584 A server MUST support at least one of the following models for 585 validating trademark information: 587 code Use of a mark code by itself to validate that the mark matches 588 the domain name. This model is supported using the 589 element with just the element. 590 mark The mark information is passed without any other validation 591 element. The server will use some custom form of validation to 592 validate that the mark information is authentic. This model is 593 supported using the element with just the 594 (Section 2.6.2) element. 595 code with mark: A code is used along with the mark information by 596 the server to validate the mark utilizing an external party. The 597 code represents some form of secret that matches the mark 598 information passed. This model is supported using the 599 element that contains both the and 600 the (Section 2.6.2) elements. 601 signed mark: The mark information is digitally signed as described 602 in the Digital Signature (Section 2.6.3) section. The digital 603 signature can be directly validated by the server using the public 604 key of the external party that created the signed mark using its 605 private key. This model is supported using the 606 (Section 2.6.3.1) and (Section 2.6.3.2) 607 elements. 609 More than one , (Section 2.6.3.1), 610 or (Section 2.6.3.2) element MAY be 611 specified. The maximum number of marks per domain name is up to 612 server policy. 614 2.6.1. element 616 The element that is used by the "code", "mark", and 617 "code with mark" validation models, has the following child elements: 619 : OPTIONAL mark code used to validate the 620 (Section 2.6.2) information. The mark code is be a mark-specific 621 secret that the server can verify against a third party. The 622 OPTIONAL "validatorID" attribute is the Validator Identifier 623 (Section 2.2) whose value indicates which Trademark Validator that 624 the code originated from, with no default value. 625 : OPTIONAL mark information with child elements defined 626 in the Mark (Section 2.6.2) section. 628 The following is an example element with both a 629 and (Section 2.6.2) element. 631 632 633 49FD46E6C4B45C55D4AC 634 635 ... 636 637 639 2.6.2. element 641 A element describes an applicant's prior right to a given 642 domain name that is used with the "mark", "mark with code", and the 643 "signed mark" validation models. The element is defined 644 in [RFC7848]. A new mark format can be supported by creating a new 645 XML schema for the mark that has an element that substitutes for the 646 element from [RFC7848]. 648 2.6.3. Digital Signature 650 Digital signatures MAY be used by the server to validate either the 651 mark information, when using the "signed mark" validation model with 652 the (Section 2.6.3.1) element or the 653 (Section 2.6.3.2) element. 655 2.6.3.1. element 657 The element contains the digitally signed mark 658 information. The element is defined in [RFC7848]. 659 A new signed mark format can be supported by creating a new XML 660 schema for the signed mark that has an element that substitutes for 661 the element from [RFC7848]. 663 2.6.3.2. element 665 The element contains an encoded form of the 666 digitally signed (Section 2.6.3.1) element. The 667 element is defined in [RFC7848]. A new 668 encoded signed mark format can be supported by creating a new XML 669 schema for the encoded signed mark that has an element that 670 substitutes for the element from [RFC7848]. 672 3. EPP Command Mapping 674 A detailed description of the EPP syntax and semantics can be found 675 in the EPP core protocol specification [RFC5730]. The command 676 mappings described here are specifically for use in the Launch Phase 677 Extension. 679 This mapping is designed to be flexible, requiring only a minimum set 680 of required elements. 682 While it is meant to serve several use cases, it does not prescribe 683 any interpretation by the client or server. Such processing is 684 typically highly policy-dependent and therefore specific to 685 implementations. 687 Operations on application objects are done via one or more of the 688 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 689 Registries MAY choose to support a subset of the operations. 691 3.1. EPP Command 693 There are three forms of the extension to the EPP command: 694 the Claims Check Form (Section 3.1.1), the Availability Check Form 695 (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The 696 element "type" attribute defines the form, with the 697 value of "claims" for the Claims Check Form (Section 3.1.1), with the 698 value of "avail" for the Availability Check Form (Section 3.1.2), and 699 with the value of "trademark" for the Trademark Check Form 700 (Section 3.1.3). The default value of the "type" attribute is 701 "claims". The forms supported by the server is determined by server 702 policy. The server MUST return an EPP error result code of 2307 if 703 it receives a check form that is not supported. 705 3.1.1. Claims Check Form 707 The Claims Check Form defines a new command called the Claims Check 708 Command that is used to determine whether or not there are any 709 matching trademarks, in the specified launch phase, for each domain 710 name passed in the command, that requires the use of the "Claims 711 Create Form" on a Domain Create Command. The availability check 712 information defined in the EPP domain name mapping [RFC5731] MUST NOT 713 be returned for the Claims Check Command. This form is the default 714 form and MAY be explicitly identified by setting the 715 "type" attribute to "claims". 717 Instead of returning whether the domain name is available, the Claims 718 Check Command will return whether or not at least one matching 719 trademark exists for the domain name, that requires the use of the 720 "Claims Create Form" on a Domain Create Command. If there is at 721 least one matching trademark that exists for the domain name, a 722 element is returned. The client MAY then use the 723 value of the element to obtain information needed 724 to generate the Trademark Claims Notice from Trademark Validator 725 based on the Validator Identifier (Section 2.2). The unique notice 726 identifier of the Trademark Claims Notice MUST be passed in the 727 element of the extension to the Create Command 728 (Section 3.3). 730 The elements in the EPP command of EPP domain 731 name mapping [RFC5731] define the domain names to check for matching 732 trademarks. The element contains the following child 733 elements: 735 Contains the value of the active launch phase of the 736 server. The server SHOULD validate the value against the active 737 server launch phase. 739 Example Claims Check command using the domain command and the 740 extension with the "type" explicitly set to "claims", 741 to determine if "domain1.example", "domain2.example", and 742 "domain3.example" require claims notices during the "claims" launch 743 phase: 745 C: 746 C: 747 C: 748 C: 749 C: 751 C: domain1.example 752 C: domain2.example 753 C: domain3.example 754 C: 755 C: 756 C: 757 C: 760 C: claims 761 C: 762 C: 763 C: ABC-12345 764 C: 765 C: 767 If the command has been processed successfully, the EPP 768 MUST contain an element that 769 identifies the launch namespace. The element 770 contains the following child elements: 772 The phase that mirrors the element 773 included in the . 774 One or more elements that contain the 775 following child elements: 777 Contains the fully qualified name of the queried 778 domain name. This element MUST contain an "exists" attribute 779 whose value indicates if a matching trademark exists for the 780 domain name that requires the use of the "Claims Create Form" 781 on a Domain Create Command. A value of "1" (or "true") means 782 that a matching trademark does exist and that the "Claims 783 Create Form" is required on a Domain Create Command. A value 784 of "0" (or "false") means that a matching trademark does not 785 exist or that the "Claims Create Form" is NOT required on a 786 Domain Create Command. 787 Zero or more OPTIONAL claim keys that MAY be 788 passed to a third-party Trademark Validator such as the ICANN 789 Trademark Clearinghouse (TMCH) for querying the information 790 needed to generate a Trademark Claims Notice. The 791 is used as the key for the query in place 792 of the domain name to securely query the service without 793 using a well-known value like a domain name. The OPTIONAL 794 "validatorID" attribute is the Validator Identifier 795 (Section 2.2) whose value indicates which Trademark Validator 796 to query for the Claims Notice information, with the default 797 being the ICANN TMCH. The "validatorID" attribute MAY 798 reference a non-trademark claims clearinghouse identifer to 799 support other forms of claims notices. 801 Example Claims Check response when a claims notice is not required 802 for the domain name domain1.example, a claims notice is required for 803 the domain name domain2.example in the "tmch", and a claims notice is 804 required for the domain name domain3.example in the "tmch" and 805 "custom-tmch", for the "claims" launch phase: 807 S: 808 S: 809 S: 810 S: 811 S: Command completed successfully 812 S: 813 S: 814 S: 816 S: claims 817 S: 818 S: domain1.example 819 S: 820 S: 821 S: domain2.example 822 S: 823 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 824 S: 825 S: 826 S: 827 S: domain3.example 828 S: 829 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 830 S: 831 S: 832 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 833 S: 834 S: 835 S: 836 S: 837 S: 838 S: ABC-12345 839 S: 54321-XYZ 840 S: 841 S: 842 S: 844 3.1.2. Availability Check Form 846 The Availability Check Form defines additional elements to extend the 847 EPP command described in the EPP domain name mapping 848 [RFC5731]. No additional elements are defined for the EPP 849 response. This form MUST be identified by setting the 850 "type" attribute to "avail". 852 The EPP command is used to determine if an object can be 853 provisioned within a repository. Domain names may be made available 854 only in unique launch phases, whilst remaining unavailable for 855 concurrent launch phases. In addition to the elements expressed in 856 the , the command is extended with the 857 element that contains the following child elements: 859 The launch phase to which domain name availability 860 should be determined. 862 Example Availability Check Form command using the domain 863 command and the extension with the "type" set to 864 "avail", to determine the availability of two domain names in the 865 "idn-release" custom launch phase: 867 C: 868 C: 869 C: 870 C: 871 C: 873 C: domain1.example 874 C: domain2.example 875 C: 876 C: 877 C: 878 C: 881 C: custom 882 C: 883 C: 884 C: ABC-12345 885 C: 886 C: 888 The Availability Check Form does not define any extension to the 889 response of an domain command. After processing the command, 890 the server replies with a standard EPP response as defined in the EPP 891 domain name mapping [RFC5731]. 893 3.1.3. Trademark Check Form 895 The Trademark Check Form defines a new command called the Trademark 896 Check Command that is used to determine whether or not there are any 897 matching trademarks for each domain name passed in the command, 898 independent of the active launch phase of the server and whether the 899 "Claims Create Form" is required on a Domain Create Command. The 900 availability check information defined in the EPP domain name mapping 901 [RFC5731] MUST NOT be returned for the Trademark Check Command. This 902 form MUST be identified by setting the "type" 903 attribute to "trademark". 905 Instead of returning whether the domain name is available, the 906 Trademark Check Command will return whether or not at least one 907 matching trademark exists for the domain name. If there is at least 908 one matching trademark that exists for the domain name, a 909 element is returned. The client MAY then use the 910 value of the element to obtain Trademark Claims 911 Notice information from Trademark Validator based on the Validator 912 Identifier (Section 2.2). 914 The elements in the EPP command of EPP domain 915 name mapping [RFC5731] define the domain names to check for matching 916 trademarks. The element does not contain any child 917 elements with the "Trademark Check Form": 919 Example Trademark Check command using the domain command and 920 the extension with the "type" set to "trademark", to 921 determine if "domain1.example", "domain2.example", and 922 "domain3.example" have any matching trademarks: 924 C: 925 C: 926 C: 927 C: 928 C: 930 C: domain1.example 931 C: domain2.example 932 C: domain3.example 933 C: 934 C: 935 C: 936 C: 939 C: 940 C: ABC-12345 941 C: 942 C: 944 If the command has been processed successfully, the EPP 945 MUST contain an element that 946 identifies the launch namespace. The element 947 contains the following child elements: 949 One or more elements that contain the 950 following child elements: 952 Contains the fully qualified name of the queried 953 domain name. This element MUST contain an "exists" attribute 954 whose value indicates if a matching trademark exists for the 955 domain name. A value of "1" (or "true") means that a 956 matching trademark does exist. A value of "0" (or "false") 957 means that a matching trademark does not exist. 958 Zero or more OPTIONAL claim keys that MAY be 959 passed to a third-party Trademark Validator such as the ICANN 960 Trademark Clearinghouse (TMCH) for querying the information 961 needed to generate a Trademark Claims Notice. The 962 is used as the key for the query in place 963 of the domain name to securely query the service without 964 using a well-known value like a domain name. The OPTIONAL 965 "validatorID" attribute is the Validator Identifier 966 (Section 2.2) whose value indicates which Trademark Validator 967 to query for the Claims Notice information, with the default 968 being the ICANN TMCH. The "validatorID" attribute MAY 969 reference a non-trademark claims clearinghouse identifer to 970 support other forms of claims notices. 972 Example Trademark Check response when no matching trademarks are 973 found for the domain name domain1.example, matching trademarks are 974 found for the domain name domain2.example in the "tmch", matching 975 trademarks are found for domain name domain3.example in the "tmch" 976 and "custom-tmch", for the "claims" launch phase: 978 S: 979 S: 980 S: 981 S: 982 S: Command completed successfully 983 S: 984 S: 985 S: 987 S: 988 S: domain1.example 989 S: 990 S: 991 S: domain2.example 992 S: 993 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 994 S: 995 S: 996 S: 997 S: domain3.example 998 S: 999 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 1000 S: 1001 S: 1002 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 1003 S: 1004 S: 1005 S: 1006 S: 1007 S: 1008 S: ABC-12345 1009 S: 54321-XYZ 1010 S: 1011 S: 1012 S: 1014 3.2. EPP Command 1016 This extension defines additional elements to extend the EPP 1017 command and response to be used in conjunction with the EPP domain 1018 name mapping [RFC5731]. 1020 The EPP command is used to retrieve information for a launch 1021 phase registration or application. The Application Identifier 1022 (Section 2.1) returned in the element of the create 1023 response (Section 3.3) is used for retrieving information for a 1024 Launch Application. A element is sent along with the 1025 regular domain command. The element includes an 1026 OPTIONAL "includeMark" boolean attribute, with a default value of 1027 "false", to indicate whether or not to include the mark in the 1028 response. The element contains the following child 1029 elements: 1031 The phase during which the application or 1032 registration was submitted or is associated with. Server policy 1033 defines the phases that are supported. 1034 OPTIONAL application identifier of the Launch 1035 Application. 1037 Example domain command with the extension to 1038 retrieve information for the sunrise application for domain.example 1039 and application identifier "abc123": 1041 C: 1042 C: 1043 C: 1044 C: 1045 C: 1047 C: domain.example 1048 C: 1049 C: 1050 C: 1051 C: 1054 C: sunrise 1055 C: abc123 1056 C: 1057 C: 1058 C: ABC-12345 1059 C: 1060 C: 1061 Example domain command with the extension to 1062 retrieve information for the sunrise registration for domain.example: 1064 C: 1065 C: 1066 C: 1067 C: 1068 C: 1070 C: domain.example 1071 C: 1072 C: 1073 C: 1074 C: 1076 C: sunrise 1077 C: 1078 C: 1079 C: ABC-12345 1080 C: 1081 C: 1083 If the query was successful, the server replies with a 1084 element along with the regular EPP . The 1085 contains the following child elements: 1087 The phase during which the application was submitted, 1088 or is associated with, that matches the associated command 1089 . 1090 OPTIONAL Application Identifier of the Launch 1091 Application. 1092 OPTIONAL status of the Launch Application using one 1093 of the supported status values (Section 2.4). 1094 Zero or more (Section 2.6.2) elements. 1096 Example domain response using the extension 1097 with the mark information: 1099 S: 1100 S: 1101 S: 1102 S: 1103 S: Command completed successfully 1104 S: 1105 S: 1106 S: 1108 S: domain.example 1109 S: EXAMPLE1-REP 1110 S: 1111 S: jd1234 1112 S: sh8013 1113 S: sh8013 1114 S: ClientX 1115 S: ClientY 1116 S: 2012-04-03T22:00:00.0Z 1117 S: 1118 S: 2fooBAR 1119 S: 1120 S: 1121 S: 1122 S: 1123 S: 1125 S: sunrise 1126 S: abc123 1127 S: 1128 S: 1130 S: ... 1131 S: 1132 S: 1133 S: 1134 S: 1135 S: ABC-12345 1136 S: 54321-XYZ 1137 S: 1138 S: 1139 S: 1141 3.3. EPP Command 1143 There are four forms of the extension to the EPP command 1144 that include the Sunrise Create Form (Section 3.3.1), the Claims 1145 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 1146 and the Mixed Create Form (Section 3.3.4). The form is dependent on 1147 the supported launch phases (Section 2.3) as defined below. 1149 sunrise The EPP command with the "sunrise" launch phase is 1150 used to submit a registration with trademark information that can 1151 be verified by the server with the value. The 1152 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 1153 launch phase. 1154 landrush The EPP command with the "landrush" launch phase 1155 MAY use the General Create Form (Section 3.3.3) to explicitly 1156 specify the phase and optionally define the expected type of 1157 object to create. 1158 claims The EPP command with the "claims" launch phase is 1159 used to pass the information associated with the presentation and 1160 acceptance of the Claims Notice. The Claims Create Form 1161 (Section 3.3.2) is used and the General Create Form 1162 (Section 3.3.3) MAY be used for the "claims" launch phase. 1163 open The EPP command with the "open" launch phase is 1164 undefined but the form supported is up to server policy. Use of 1165 the Claims Create Form (Section 3.3.2) MAY be used to pass the 1166 information associated with the presentation and acceptance of the 1167 Claims Notice if required for the domain name. 1168 custom The EPP command with the "custom" launch phase is 1169 undefined but the form supported is up to server policy. 1171 3.3.1. Sunrise Create Form 1173 The Sunrise Create Form of the extension to the EPP domain name 1174 mapping [RFC5731] includes the verifiable trademark information that 1175 the server uses to match against the domain name to authorize the 1176 domain create. A server MUST support one of four models in Claim 1177 Validation Models (Section 2.6) to verify the trademark information 1178 passed by the client. 1180 A element is sent along with the regular 1181 domain command. The element has an OPTIONAL "type" 1182 attribute that defines the expected type of object ("application" or 1183 "registration") to create. The server SHOULD validate the "type" 1184 attribute, when passed, against the type of object that will be 1185 created. The element contains the following child 1186 elements: 1188 The identifier for the launch phase. 1190 or or 1192 Zero or more elements. The 1193 child elements are defined in the 1194 element (Section 2.6.1) section. 1195 Zero or more elements. The 1196 child elements are defined in the 1197 element (Section 2.6.3.1) section. 1198 Zero or more 1199 elements. The child elements are 1200 defined in the element 1201 (Section 2.6.3.2) section. 1203 The following is an example domain command using the 1204 extension, following the "code" validation model, 1205 with multiple sunrise codes: 1207 C: 1208 C: 1209 C: 1210 C: 1211 C: 1213 C: domain.example 1214 C: jd1234 1215 C: sh8013 1216 C: sh8013 1217 C: 1218 C: 2fooBAR 1219 C: 1220 C: 1221 C: 1222 C: 1223 C: 1225 C: sunrise 1226 C: 1227 C: 1228 C: 49FD46E6C4B45C55D4AC 1229 C: 1230 C: 1231 C: 49FD46E6C4B45C55D4AD 1232 C: 1233 C: 1234 C: 1235 C: 49FD46E6C4B45C55D4AE 1236 C: 1237 C: 1238 C: 1239 C: ABC-12345 1240 C: 1241 C: 1242 The following is an example domain command using the 1243 extension, following the "mark" validation model, 1244 with the mark information: 1246 C: 1247 C: 1248 C: 1249 C: 1250 C: 1252 C: domainone.example 1253 C: jd1234 1254 C: sh8013 1255 C: sh8013 1256 C: 1257 C: 2fooBAR 1258 C: 1259 C: 1260 C: 1261 C: 1262 C: 1264 C: sunrise 1265 C: 1266 C: 1268 C: ... 1269 C: 1270 C: 1271 C: 1272 C: 1273 C: ABC-12345 1274 C: 1275 C: 1276 The following is an example domain command using the 1277 extension, following the "code with mark" validation 1278 model, with a code and mark information: 1280 C: 1281 C: 1282 C: 1283 C: 1284 C: 1286 C: domain.example 1287 C: jd1234 1288 C: sh8013 1289 C: sh8013 1290 C: 1291 C: 2fooBAR 1292 C: 1293 C: 1294 C: 1295 C: 1296 C: 1298 C: sunrise 1299 C: 1300 C: 1301 C: 49FD46E6C4B45C55D4AC 1302 C: 1304 C: ... 1305 C: 1306 C: 1307 C: 1308 C: 1309 C: ABC-12345 1310 C: 1311 C: 1312 The following is an example domain command using the 1313 extension, following the "signed mark" validation 1314 model, with the signed mark information for a sunrise application: 1316 C: 1317 C: 1318 C: 1319 C: 1320 C: 1322 C: domainone.example 1323 C: jd1234 1324 C: sh8013 1325 C: sh8013 1326 C: 1327 C: 2fooBAR 1328 C: 1329 C: 1330 C: 1331 C: 1332 C: 1335 C: sunrise 1336 C: 1338 C: ... 1339 C: 1340 C: 1341 C: 1342 C: ABC-12345 1343 C: 1344 C: 1345 The following is an example domain command using the 1346 extension, following the "signed mark" validation 1347 model, with the base64 encoded signed mark information: 1349 C: 1350 C: 1351 C: 1352 C: 1353 C: 1355 C: domainone.example 1356 C: jd1234 1357 C: sh8013 1358 C: sh8013 1359 C: 1360 C: 2fooBAR 1361 C: 1362 C: 1363 C: 1364 C: 1365 C: 1367 C: sunrise 1368 C: 1370 C: ... 1371 C: 1372 C: 1373 C: 1374 C: ABC-12345 1375 C: 1376 C: 1378 3.3.2. Claims Create Form 1380 The Claims Create Form of the extension to the EPP domain name 1381 mapping [RFC5731] includes the information related to the 1382 registrant's acceptance of the Claims Notice. 1384 A element is sent along with the regular 1385 domain command. The element has an OPTIONAL "type" 1386 attribute that defines the expected type of object ("application" or 1387 "registration") to create. The server SHOULD validate the "type" 1388 attribute, when passed, against the type of object that will be 1389 created. The element contains the following child 1390 elements: 1392 Contains the value of the active launch phase of the 1393 server. The server SHOULD validate the value against the active 1394 server launch phase. 1395 One or more elements that contain 1396 the following child elements: 1398 Unique notice identifier for the Claims 1399 Notice. The element has an OPTIONAL 1400 "validatorID" attribute is the Validator Identifier 1401 (Section 2.2) whose value indicates which Trademark Validator 1402 is the source of the claims notice, with the default being 1403 the ICANN TMCH. 1404 Expiry of the claims notice. 1405 Contains the date and time that the claims 1406 notice was accepted. 1408 The following is an example domain command using the 1409 extension with the information for 1410 the "tmch" and the "custom-tmch" validators, for the "claims" launch 1411 phase: 1413 C: 1414 C: 1415 C: 1416 C: 1417 C: 1419 C: domain.example 1420 C: jd1234 1421 C: sh8013 1422 C: sh8013 1423 C: 1424 C: 2fooBAR 1425 C: 1426 C: 1427 C: 1428 C: 1429 C: 1431 C: claims 1432 C: 1433 C: 1434 C: 370d0b7c9223372036854775807 1435 C: 2014-06-19T10:00:00.0Z 1436 C: 1437 C: 2014-06-19T09:00:00.0Z 1438 C: 1439 C: 1440 C: 1441 C: 1442 C: 470d0b7c9223654313275808 1443 C: 2014-06-19T10:00:00.0Z 1444 C: 1445 C: 2014-06-19T09:00:30.0Z 1446 C: 1447 C: 1448 C: 1449 C: 1450 C: ABC-12345 1451 C: 1452 C: 1454 3.3.3. General Create Form 1456 The General Create Form of the extension to the EPP domain name 1457 mapping [RFC5731] includes the launch phase and optionally the object 1458 type to create. The OPTIONAL "type" attribute defines the expected 1459 type of object ("application" or "registration") to create. The 1460 server SHOULD validate the "type" attribute, when passed, against the 1461 type of object that will be created. 1463 A element is sent along with the regular 1464 domain command. The element contains the following 1465 child elements: 1467 Contains the value of the active launch phase of the 1468 server. The server SHOULD validate the value against the active 1469 server launch phase. 1471 The following is an example domain command using the 1472 extension for a "landrush" launch phase application: 1474 C: 1475 C: 1476 C: 1477 C: 1478 C: 1480 C: domain.example 1481 C: jd1234 1482 C: sh8013 1483 C: sh8013 1484 C: 1485 C: 2fooBAR 1486 C: 1487 C: 1488 C: 1489 C: 1490 C: 1493 C: landrush 1494 C: 1495 C: 1496 C: ABC-12345 1497 C: 1498 C: 1500 3.3.4. Mixed Create Form 1502 The Mixed Create Form supports a mix of the create forms, where for 1503 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1504 Form (Section 3.3.2) MAY be supported in a single command by 1505 including both the verified trademark information and the information 1506 related to the registrant's acceptance of the Claims Notice. The 1507 server MAY support the Mixed Create Form. The "custom" launch phase 1508 SHOULD be used when using the Mixed Create Form. 1510 The following is an example domain command using the 1511 extension, with using a mix of the Sunrise Create 1512 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1513 including both a mark and a notice: 1515 C: 1516 C: 1517 C: 1518 C: 1519 C: 1521 C: domainone.example 1522 C: jd1234 1523 C: sh8013 1524 C: sh8013 1525 C: 1526 C: 2fooBAR 1527 C: 1528 C: 1529 C: 1530 C: 1531 C: 1534 C: custom 1535 C: 1536 C: 1538 C: ... 1539 C: 1540 C: 1541 C: 1542 C: 1543 C: 49FD46E6C4B45C55D4AC 1544 C: 1545 C: 2012-06-19T10:00:10.0Z 1546 C: 1547 C: 2012-06-19T09:01:30.0Z 1548 C: 1549 C: 1550 C: 1551 C: 1552 C: ABC-12345 1553 C: 1554 C: 1556 3.3.5. Create Response 1558 If the create was successful, the server MAY reply with the 1559 element along with the regular EPP to 1560 indicate the server generated Application Identifier (Section 2.1), 1561 when multiple applications of a given domain name are supported; 1562 otherwise no extension is included with the regular EPP . 1563 The element contains the following child elements: 1565 The phase of the application that mirrors the 1566 element included in the . 1567 The application identifier of the 1568 application. 1570 An example response when multiple overlapping applications are 1571 supported by the server: 1573 S: 1574 S: 1575 S: 1576 S: 1577 S: Command completed successfully; action pending 1578 S: 1579 S: 1580 S: 1582 S: domain.example 1583 S: 2010-08-10T15:38:26.623854Z 1584 S: 1585 S: 1586 S: 1587 S: 1589 S: sunrise 1590 S: 2393-9323-E08C-03B1 1591 S: 1592 S: 1593 S: 1594 S: 1595 S: ABC-12345 1596 S: 54321-XYZ 1597 S: 1598 S: 1599 S: 1601 3.4. EPP Command 1603 This extension defines additional elements to extend the EPP 1604 command to be used in conjunction with the domain name mapping. 1606 A client MUST NOT pass the extension on an EPP command to a 1607 server that does not support launch applications. A server that does 1608 not support launch applications during its launch phase MUST return 1609 an EPP error result code of 2102 when receiving an EPP 1610 command with the extension. 1612 Registry policies permitting, clients may update an application 1613 object by submitting an EPP command along with a 1614 element to indicate the application object to be 1615 updated. The element contains the following child 1616 elements: 1618 The phase during which the application was submitted 1619 or is associated with. 1620 The application identifier for which the 1621 client wishes to update. 1623 The following is an example domain command with the 1624 extension to add and remove a name server of a 1625 sunrise application with the application identifier "abc123": 1627 C: 1628 C: 1629 C: 1630 C: 1631 C: 1633 C: domain.example 1634 C: 1635 C: 1636 C: ns2.domain.example 1637 C: 1638 C: 1639 C: 1640 C: 1641 C: ns1.domain.example 1642 C: 1643 C: 1644 C: 1645 C: 1646 C: 1647 C: 1649 C: sunrise 1650 C: abc123 1651 C: 1652 C: 1653 C: ABC-12345 1654 C: 1655 C: 1657 This extension does not define any extension to the response of an 1658 domain command. After processing the command, the server 1659 replies with a standard EPP response as defined in the EPP domain 1660 name mapping [RFC5731]. 1662 3.5. EPP Command 1664 This extension defines additional elements to extend the EPP 1665 command to be used in conjunction with the domain name mapping. 1667 A client MUST NOT pass the extension on an EPP command to a 1668 server that does not support launch applications. A server that does 1669 not support launch applications during its launch phase MUST return 1670 an EPP error result code of 2102 when receiving an EPP 1671 command with the extension. 1673 Registry policies permitting, clients MAY withdraw an application by 1674 submitting an EPP command along with a 1675 element to indicate the application object to be deleted. The 1676 element contains the following child elements: 1678 The phase during which the application was submitted 1679 or is associated with. 1680 The application identifier for which the 1681 client wishes to delete. 1683 The following is an example domain command with the 1684 extension: 1686 C: 1687 C: 1688 C: 1689 C: 1690 C: 1692 C: domain.example 1693 C: 1694 C: 1695 C: 1696 C: 1698 C: sunrise 1699 C: abc123 1700 C: 1701 C: 1702 C: ABC-12345 1703 C: 1704 C: 1706 This extension does not define any extension to the response of a 1707 domain command. After processing the command, the server 1708 replies with a standard EPP response as defined in the EPP domain 1709 name mapping [RFC5731]. 1711 3.6. EPP Command 1713 This extension does not define any extension to the EPP 1714 command or response described in the EPP domain name mapping 1715 [RFC5731]. 1717 3.7. EPP Command 1719 This extension does not define any extension to the EPP 1720 command or response described in the EPP domain name mapping 1721 [RFC5731]. 1723 4. Formal Syntax 1725 One schema is presented here that is the EPP Launch Phase Mapping 1726 schema. 1728 The formal syntax presented here is a complete schema representation 1729 of the object mapping suitable for automated validation of EPP XML 1730 instances. The BEGIN and END tags are not part of the schema; they 1731 are used to note the beginning and ending of the schema for URI 1732 registration purposes. 1734 4.1. Launch Schema 1736 Copyright (c) 2012 IETF Trust and the persons identified as authors 1737 of the code. All rights reserved. 1739 Redistribution and use in source and binary forms, with or without 1740 modification, are permitted provided that the following conditions 1741 are met: 1743 o Redistributions of source code must retain the above copyright 1744 notice, this list of conditions and the following disclaimer. 1745 o Redistributions in binary form must reproduce the above copyright 1746 notice, this list of conditions and the following disclaimer in 1747 the documentation and/or other materials provided with the 1748 distribution. 1749 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1750 names of specific contributors, may be used to endorse or promote 1751 products derived from this software without specific prior written 1752 permission. 1754 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1755 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1756 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1757 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1758 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1759 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1760 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1761 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1762 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1763 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1764 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1766 BEGIN 1767 1768 1777 1780 1781 1782 1784 1785 1786 Extensible Provisioning Protocol v1.0 1787 domain name extension schema 1788 for the launch phase processing. 1789 1790 1792 1795 1796 1797 1798 1799 1801 1804 1805 1806 1808 1810 1811 1813 1816 1817 1818 1820 1826 1827 1828 1829 1830 1831 1832 1834 1837 1838 1839 1840 1841 1842 1843 1844 1845 1847 1850 1851 1852 1853 1854 1856 1857 1858 1859 1862 1863 1864 1866 1869 1870 1871 1872 1873 1875 1876 1877 1878 1880 1881 1882 1884 1887 1888 1889 1890 1891 1893 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1908 1911 1912 1913 1914 1916 1918 1919 1920 1921 1923 1927 1928 1929 1931 1933 1934 1936 1939 1940 1941 1942 1943 1945 1947 1949 1950 1953 1954 1955 1957 1960 1961 1962 1963 1964 1965 1967 1970 1971 1972 1973 1974 1975 1976 1978 1981 1982 1983 1985 1986 1988 1990 1994 1995 1996 1997 1998 1999 2000 2001 2004 2005 2006 2007 2010 2011 2013 2015 2018 2019 2020 2022 2025 2026 2027 2029 2031 2032 2034 2035 2036 2037 2039 2040 2042 2043 2044 2045 2047 2048 2050 2052 2053 2054 2055 2057 2058 2059 2061 2064 2065 2066 2067 2070 2072 2074 2075 2077 2078 END 2080 5. IANA Considerations 2082 5.1. XML Namespace 2084 This document uses URNs to describe XML namespaces and XML schemas 2085 conforming to a registry mechanism described in [RFC3688]. 2087 Registration request for the launch namespace: 2089 URI: urn:ietf:params:xml:ns:launch-1.0 2090 Registrant Contact: See the "Author's Address" section of this 2091 document. 2092 XML: None. Namespace URIs do not represent an XML specification. 2094 Registration request for the launch XML schema: 2096 URI: urn:ietf:params:xml:schema:launch-1.0 2097 Registrant Contact: See the "Author's Address" section of this 2098 document. 2099 XML: See the "Formal Syntax" section of this document. 2101 5.2. EPP Extension Registry 2103 The EPP extension described in this document should be registered by 2104 the IANA in the EPP Extension Registry described in [RFC7451]. The 2105 details of the registration are as follows: 2107 Name of Extension: "Launch Phase Mapping for the Extensible 2108 Provisioning Protocol (EPP)" 2110 Document status: Standards Track 2112 Reference: (insert reference to RFC version of this document) 2114 Registrant Name and Email Address: IESG, 2116 TLDs: Any 2118 IPR Disclosure: None 2120 Status: Active 2122 Notes: None 2124 6. Implementation Status 2126 Note to RFC Editor: Please remove this section and the reference to 2127 RFC 6982 [RFC6982] before publication. 2129 This section records the status of known implementations of the 2130 protocol defined by this specification at the time of posting of this 2131 Internet-Draft, and is based on a proposal described in RFC 6982 2132 [RFC6982]. The description of implementations in this section is 2133 intended to assist the IETF in its decision processes in progressing 2134 drafts to RFCs. Please note that the listing of any individual 2135 implementation here does not imply endorsement by the IETF. 2136 Furthermore, no effort has been spent to verify the information 2137 presented here that was supplied by IETF contributors. This is not 2138 intended as, and must not be construed to be, a catalog of available 2139 implementations or their features. Readers are advised to note that 2140 other implementations may exist. 2142 According to RFC 6982 [RFC6982], "this will allow reviewers and 2143 working groups to assign due consideration to documents that have the 2144 benefit of running code, which may serve as evidence of valuable 2145 experimentation and feedback that have made the implemented protocols 2146 more mature. It is up to the individual working groups to use this 2147 information as they see fit". 2149 6.1. Verisign EPP SDK 2151 Organization: Verisign Inc. 2153 Name: Verisign EPP SDK 2155 Description: The Verisign EPP SDK includes both a full client 2156 implementation and a full server stub implementation of draft-ietf- 2157 regext-launchphase. 2159 Level of maturity: Production 2161 Coverage: All aspects of the protocol are implemented. 2163 Licensing: GNU Lesser General Public License 2165 Contact: jgould@verisign.com 2167 URL: http://www.verisigninc.com/en_US/channel-resources/domain- 2168 registry-products/epp-sdks 2170 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 2172 Organization: Verisign Inc. 2174 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 2175 System (SRS) 2177 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 2178 Registry System (SRS) implements the server-side of draft-ietf- 2179 regext-launchphase for a variety of Top Level Domains (TLD's). 2181 Level of maturity: Production 2183 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2184 Form for the EPP Command, the Sunrise and Claims Forms for 2185 the EPP Command of Launch Registrations and Launch 2186 Applications. For Launch Applications the Poll Messaging, the EPP 2187 Command, the EPP Command, and the EPP 2188 Command is covered. 2190 Licensing: Proprietary 2192 Contact: jgould@verisign.com 2194 6.3. Verisign .COM / .NET SRS 2196 Organization: Verisign Inc. 2198 Name: Verisign .COM / .NET Shared Registry System (SRS) 2200 Description: The Verisign Shared Registry System (SRS) for .COM, .NET 2201 and other IDN TLD's implements the server-side of draft-ietf-regext- 2202 launchphase. 2204 Level of maturity: Operational Test Environment (OTE) 2206 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2207 Form for the EPP Command, the Sunrise and Claims Forms for 2208 the EPP Command of Launch Registrations. 2210 Licensing: Proprietary 2212 Contact: jgould@verisign.com 2214 6.4. REngin v3.7 2216 Organization: Domain Name Services (Pty) Ltd 2218 Name: REngin v3.7 2220 Description: Server side implementation only 2222 Level of maturity: Production 2224 Coverage: All features from version 12 have been implemented 2226 Licensing: Proprietary Licensing with Maintenance Contracts 2228 Contact: info@dnservices.co.za 2230 URL: https://www.registry.net.za and soon http://dnservices.co.za 2232 6.5. RegistryEngine EPP Service 2234 Organization: CentralNic 2236 Name: RegistryEngine EPP Service 2238 Description: Generic high-volume EPP service for gTLDs, ccTLDs and 2239 SLDs 2240 Level of maturity: Deployed in CentralNic's production environment as 2241 well as two other gTLD registry systems, and two ccTLD registry 2242 systems. 2244 Coverage: Majority of elements including TMCH sunrise, landrush and 2245 TM claims as well as sunrise applications validated using codes. 2247 Licensing: Proprietary In-House software 2249 Contact: epp@centralnic.com 2251 URL: https://www.centralnic.com 2253 6.6. Neustar EPP SDK 2255 Organization: Neustar 2257 Name: Neustar EPP SDK 2259 Description: The Neustar EPP SDK includes client implementation of 2260 draft-ietf-regext-launchphase in both Java and C++. 2262 Level of maturity: Production 2264 Coverage: All aspects of the protocol are implemented. 2266 Licensing: GNU Lesser General Public License 2268 Contact: trung.tran@neustar.biz 2270 6.7. gTLD Shared Registry System 2272 Organization: Stichting Internet Domeinnaamregistratie Nederland 2273 (SIDN) 2275 Name: gTLD Shared Registry System 2277 Description: The gTLD SRS implements the server side of the draft- 2278 ietf-regext-launchphase. 2280 Level of maturity: (soon) Production 2282 Coverage: The following parts of the draft are supported: 2284 Signed mark validation model using Digital Signature 2285 (Section 2.6.3) 2286 Claims Check Form (Section 3.1.1) 2287 Sunrise Create Form (Section 3.3.1) 2288 Claims Create Form (Section 3.3.2) 2290 The parts of the document not described here are not implemented. 2292 Licensing: Proprietary 2294 Contact: rik.ribbers@sidn.nl 2296 7. Security Considerations 2298 The mapping extensions described in this document do not provide any 2299 security services beyond those described by EPP [RFC5730], the EPP 2300 domain name mapping [RFC5731], and protocol layers used by EPP. The 2301 security considerations described in these other specifications apply 2302 to this specification as well. 2304 Updates to, and deletion of an application object must be restricted 2305 to clients authorized to perform the said operation on the object. 2307 As information contained within an application, or even the mere fact 2308 that an application exists may be confidential. Any attempt to 2309 operate on an application object by an unauthorized client MUST be 2310 rejected with an EPP 2201 (authorization error) return code. Server 2311 policy may allow operation with filtered output by clients 2312 other than the sponsoring client, in which case the 2313 and response SHOULD be filtered to include only 2314 fields that are publicly accessible. 2316 8. Acknowledgements 2318 The authors wish to acknowledge the efforts of the leading 2319 participants of the Community TMCH Model that led to many of the 2320 changes to this document, which include Chris Wright, Jeff Neuman, 2321 Jeff Eckhaus, and Will Shorter. 2323 Special suggestions that have been incorporated into this document 2324 were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Michael 2325 Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus 2326 Malorny, Alexander Mayrhofer, Patrick Mevzek, James Mitchell, 2327 Francisco Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung 2328 Tran, Ulrich Wisser and Sharon Wodjenski. 2330 Some of the description of the Trademark Claims Phase was based on 2331 the work done by Gustavo Lozano in the ICANN TMCH functional 2332 specifications. 2334 9. Normative References 2336 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2337 Requirement Levels", BCP 14, RFC 2119, March 1997. 2339 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2340 January 2004. 2342 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2343 STD 69, RFC 5730, August 2009. 2345 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2346 Domain Name Mapping", STD 69, RFC 5731, August 2009. 2348 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 2349 Code: The Implementation Status Section", RFC 6982, July 2350 2013. 2352 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 2353 Provisioning Protocol", RFC 7451, February 2015. 2355 [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", RFC 2356 7848, DOI 10.17487/RFC7848, June 2016, 2357 . 2359 Appendix A. Change History 2361 A.1. Change from 00 to 01 2363 1. Changed to use camel case for the XML elements. 2364 2. Replaced "cancelled" status to "rejected" status. 2365 3. Added the child elements of the element. 2366 4. Removed the XML schema and replaced with "[TBD]". 2368 A.2. Change from 01 to 02 2370 1. Added support for both the ICANN and ARI/Neustar TMCH models. 2371 2. Changed the namespace URI and prefix to use "launch" instead of 2372 "launchphase". 2373 3. Added definition of multiple claim validation models. 2374 4. Added the and 2375 elements. 2376 5. Added support for Claims Info Command 2378 A.3. Change from 02 to 03 2380 1. Removed XSI namespace per Keith Gaughan's suggestion on the 2381 provreg list. 2382 2. Added extensibility to the launch:status element and added the 2383 pendingAuction status per Trung Tran's feedback on the provreg 2384 list. 2385 3. Added support for the Claims Check Command, updated the location 2386 and contents of the signedNotice, and replaced most references of 2387 Claim to Mark based on the work being done on the ARI/Neustar 2388 launch model. 2390 A.4. Change from 03 to 04 2392 1. Removed references to the ICANN model. 2393 2. Removed support for the Claims Info Command. 2394 3. Removed use of the signedClaim. 2395 4. Revised the method for referring to the signedClaim from the XML 2396 Signature using the IDREF URI. 2397 5. Split the launch-1.0.xsd into three XML schemas including launch- 2398 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 2399 6. Split the "claims" launch phase to the "claims1" and "claims2" 2400 launch phases. 2401 7. Added support for the encodedSignedMark with base64 encoded 2402 signedMark. 2403 8. Changed the elements in the createNoticeType to include the 2404 noticeID, timestamp, and the source elements. 2405 9. Added the class and effectiveDate elements to mark. 2407 A.5. Change from 04 to 05 2409 1. Removed reference to in the example. 2410 2. Incorporated feedback from Bernhard Reutner-Fischer on the 2411 provreg mail list. 2412 3. Added missing launch XML prefix to applicationIDType reference in 2413 the idContainerType of the Launch Schema. 2414 4. Added missing description of the element in the 2415 element. 2416 5. Updated note on replication of the EPP contact mapping elements 2417 in the Mark Contact section. 2419 A.6. Change from 05 to 06 2421 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 2422 replaced with reference to draft-lozano-smd, that contains the 2423 definition for the mark, signed marked, and encoded signed mark. 2424 2. Split the into and 2425 based on feedback from Trung Tran. 2427 3. Added the "includeMark" optional attribute to the 2428 element to enable the client to request whether or not to include 2429 the mark in the info response. 2430 4. Fixed state diagram to remove redundant transition from "invalid" 2431 to "rejected"; thanks Klaus Malorny. 2433 A.7. Change from 06 to 07 2435 1. Proof-read grammar and spelling. 2436 2. Changed "pendingAuction" status to "pendingAllocation", changed 2437 "pending" to "pendingValidation" status, per proposal from Trung 2438 Tran and seconded by Rubens Kuhl. 2439 3. Added text related to the use of RFC 5731 pendingCreate to the 2440 Application Identifier section. 2441 4. Added the Poll Messaging section to define the use of poll 2442 messaging for intermediate state transitions and pending action 2443 poll messaging for final state transitions. 2445 A.8. Change from 07 to 08 2447 1. Added support for use of the launch statuses and poll messaging 2448 for Launch Registrations based on feedback from Sharon Wodjenski 2449 and Trung Tran. 2450 2. Incorporated changes based on updates or clarifications in draft- 2451 lozano-tmch-func-spec-01, which include: 2453 1. Removed the unused element. 2454 2. Removed the element. 2455 3. Added the element based on the required 2456 element. 2458 A.9. Change from 08 to 09 2460 1. Made element optional in to allow 2461 passing just the in per request 2462 from Ben Levac. 2463 2. Added optional "type" attribute in to enable the 2464 client to explicitly define the desired type of object 2465 (application or registration) to create to all forms of the 2466 create extension. 2467 3. Added text that the server SHOULD validate the 2468 element in the Launch Phases section. 2469 4. Add the "General Create Form" to the create command extension to 2470 support the request from Ben Levac. 2471 5. Updated the text for the Poll Messaging section based on feedback 2472 from Klaus Malorny. 2473 6. Replaced the "claims1" and "claims2" phases with the "claims" 2474 phase based on discussion on the provreg list. 2476 7. Added support for a mixed create model (Sunrise Create Model and 2477 Claims Create Model), where a trademark (encoded signed mark, 2478 etc.) and notice can be passed, based on a request from James 2479 Mitchell. 2480 8. Added text for the handling of the overlapping "claims" and 2481 "landrush" launch phases. 2482 9. Added support for two check forms (claims check form and 2483 availability check form) based on a request from James Mitchell. 2484 The availability check form was based on the text in draft-rbp- 2485 application-epp-mapping. 2487 A.10. Change from 09 to 10 2489 1. Changed noticeIDType from base64Binary to token to be compatible 2490 with draft-lozano-tmch-func-spec-05. 2491 2. Changed codeType from base64Binary to token to be more generic. 2492 3. Updated based on feedback from Alexander Mayrhofer, which 2493 include: 2495 1. Changed "extension to the domain name extension" to 2496 "extension to the domain name mapping". 2497 2. Changed use of 2004 return code to 2306 return code when 2498 phase passed mismatches active phase and sub-phase. 2499 3. Changed description of "allocated" and "rejected" statuses. 2500 4. Moved sentence on a synchronous command 2501 without the use of an intermediate application, then an 2502 Application Identifier MAY not be needed to the Application 2503 Identifier section. 2504 5. Restructured the Mark Validation Models section to include 2505 the " element" sub-section, the 2506 " element" sub-section, and the Digital Signature 2507 sub-section. 2508 6. Changed "Registries may" to "Registries MAY". 2509 7. Changed "extensed" to "extended" in "Availability Check 2510 Form" section. 2511 8. Broke the mix of create forms in the "EPP Command" 2512 section to a fourth "Mixed Create Form" with its own sub- 2513 section. 2514 9. Removed "displayed or" from "displayed or accepted" in the 2515 description. 2516 10. Replaced "given domain name is supported" with "given domain 2517 name are supported" in the "Create Response" section. 2518 11. Changed the reference of 2303 (object does not exist) in the 2519 "Security Considerations" section to 2201 (authorization 2520 error). 2521 12. Added arrow from "invalid" status to "pendingValidation" 2522 status and "pendingAllocation" status to "rejected" status 2523 in the State Transition Diagram. 2525 4. Added the "C:" and "S:" example prefixes and related text in the 2526 "Conventions Used in This Document" section. 2528 A.11. Change from 10 to 11 2530 1. Moved the claims check response element under 2531 the element instead of the element based on 2532 the request from Francisco Obispo. 2534 A.12. Change from 11 to 12 2536 1. Added support for multiple validator identifiers for claims 2537 notices and marks based on a request and text provided by Mike 2538 O'Connell. 2539 2. Removed domain:exDate element from example in section 3.3.5 based 2540 on a request from Seth Goldman on the provreg list. 2541 3. Added clarifying text for clients not passing the launch 2542 extension on update and delete commands to servers that do not 2543 support launch applications based on a request from Sharon 2544 Wodjenski on the provreg list. 2546 A.13. Change from 12 to EPPEXT 00 2548 1. Changed to eppext working group draft by changing draft-tan-epp- 2549 launchphase to draft-ietf-eppext-launchphase and by changing 2550 references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch- 2551 smd. 2553 A.14. Change EPPEXT 00 to EPPEXT 01 2555 1. Removed text associated with support for the combining of status 2556 values based on feedback from Patrick Mevzek on the provreg 2557 mailing list, discussion on the eppext mailing list, and 2558 discussion at the eppext IETF meeting on March 6, 2014. 2560 A.15. Change EPPEXT 01 to EPPEXT 02 2562 1. Changed the element to be zero or more elements 2563 and the element to be one or more elements in the 2564 Claims Create Form. These changes were needed to be able to 2565 support more than one concurrent claims services. 2567 A.16. Change EPPEXT 02 to EPPEXT 03 2569 1. Added the "Implementation Status" section based on an action item 2570 from the eppext IETF-91 meeting. 2572 2. Moved Section 7 "IANA Considerations" and Section 9 "Security 2573 Considerations" before Section 5 "Acknowledgements". Moved 2574 "Change Log" Section to end. 2575 3. Updated the text for the Claims Check Form and the Claims Create 2576 Form to support checking for the need of the claims notice and 2577 passing the claims notice outside of the "claims" phase. 2578 4. Added the new Trademark Check Form to support determining whether 2579 or not a trademark exists that matches the domain name 2580 independent of whether a claims notice is required on create. 2581 This was based on a request from Trung Tran and a discussion on 2582 the eppext mailing list. 2584 A.17. Change EPPEXT 03 to EPPEXT 04 2586 1. Amended XML Namespace section of IANA Considerations, added EPP 2587 Extension Registry section. 2589 A.18. Change EPPEXT 04 to EPPEXT 05 2591 1. Added a missing comma to the descripton of the 2592 element, based on feedback from Keith Gaughan on the eppext 2593 mailing list. 2594 2. Added the SIDN implementation status information. 2595 3. Fixed a few indentation issues in the samples. 2597 A.19. Change EPPEXT 05 to EPPEXT 06 2599 1. Removed duplicate "TMCH Functional Specification" URIs based on 2600 feedback from Scott Hollenbeck on the eppext mailing list. 2601 2. Changed references of example?.tld to domain?.example to be 2602 consistent with RFC 6761 based on feedback from Scott Hollenbeck 2603 on the eppext mailing list. 2604 3. A template was added to section 5 to register the XML schema in 2605 addition to the namespace based on feedback from Scott Hollenbeck 2606 on the eppext mailing list. 2608 A.20. Change EPPEXT 06 to EPPEXT 07 2610 1. Changed reference of lozano-tmch-func-spec to ietf-eppext-tmch- 2611 func-spec. 2613 A.21. Change from EPPEXT 07 to REGEXT 00 2615 1. Changed to regext working group draft by changing draft-ietf- 2616 eppext-launchphase to draft-ietf-regext-launchphase and by 2617 changing references of draft-ietf-eppext-tmch-func-spec to draft- 2618 ietf-regext-tmch-func-spec. 2620 A.22. Change from REGEXT 00 to REGEXT 01 2622 1. Fixed reference of Claims Check Command to Trademark Check 2623 Command in the Trademark Check Form section. 2624 2. Replaced reference of draft-ietf-eppext-tmch-smd to RFC 7848. 2626 A.23. Change from REGEXT 01 to REGEXT 02 2628 1. Removed the reference to ietf-regext-tmch-func-spec and briefly 2629 described the trademark claims phase that is relavent to draft- 2630 ietf-regext-launchphase. 2632 Authors' Addresses 2634 James Gould 2635 VeriSign, Inc. 2636 12061 Bluemont Way 2637 Reston, VA 20190 2638 US 2640 Email: jgould@verisign.com 2641 URI: http://www.verisigninc.com 2643 Wil Tan 2644 Cloud Registry 2645 Suite 32 Seabridge House 2646 377 Kent St 2647 Sydney, NSW 2000 2648 AU 2650 Phone: +61 414 710899 2651 Email: wil@cloudregistry.net 2652 URI: http://www.cloudregistry.net 2654 Gavin Brown 2655 CentralNic Ltd 2656 35-39 Mooregate 2657 London, England EC2R 6AR 2658 GB 2660 Phone: +44 20 33 88 0600 2661 Email: gavin.brown@centralnic.com 2662 URI: https://www.centralnic.com