idnits 2.17.1 draft-ietf-regext-launchphase-07.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 (December 12, 2017) is 2327 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-15) exists of draft-ietf-regext-tmch-func-spec-03 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Gould 3 Internet-Draft VeriSign, Inc. 4 Intended status: Standards Track W. Tan 5 Expires: June 15, 2018 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 December 12, 2017 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-ietf-regext-launchphase-07 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 June 15, 2018. 37 Copyright Notice 39 Copyright (c) 2017 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Conventions Used in This Document . . . . . . . . . . . . 4 56 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 5 57 2.1. Application Identifier . . . . . . . . . . . . . . . . . 5 58 2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5 59 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 6 60 2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 7 61 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9 62 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 10 63 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 12 64 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 15 65 2.6.1. element . . . . . . . . . . . . . . 16 66 2.6.2. element . . . . . . . . . . . . . . . . . 17 67 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 17 68 2.6.3.1. element . . . . . . . . . . . . 17 69 2.6.3.2. element . . . . . . . . . 17 70 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 17 71 3.1. EPP Command . . . . . . . . . . . . . . . . . . . 18 72 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 18 73 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 21 74 3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 23 75 3.2. EPP Command . . . . . . . . . . . . . . . . . . . 26 76 3.3. EPP Command . . . . . . . . . . . . . . . . . . 30 77 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 30 78 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 36 79 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 39 80 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 40 81 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 42 82 3.4. EPP Command . . . . . . . . . . . . . . . . . . 43 83 3.5. EPP Command . . . . . . . . . . . . . . . . . . 44 84 3.6. EPP Command . . . . . . . . . . . . . . . . . . . 45 85 3.7. EPP Command . . . . . . . . . . . . . . . . . 46 86 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46 87 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 46 88 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 89 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 54 90 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 54 91 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 55 92 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 55 93 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 56 94 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 56 95 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 57 96 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 57 97 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 58 98 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 58 99 7. Security Considerations . . . . . . . . . . . . . . . . . . . 58 100 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 59 101 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 59 102 9.1. Normative References . . . . . . . . . . . . . . . . . . 59 103 9.2. Informative References . . . . . . . . . . . . . . . . . 60 104 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 60 105 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 60 106 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 60 107 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 61 108 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 61 109 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 61 110 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 62 111 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 62 112 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 62 113 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 62 114 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 63 115 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 64 116 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 64 117 A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 64 118 A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 64 119 A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 64 120 A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 65 121 A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 65 122 A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 65 123 A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 65 124 A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 65 125 A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 66 126 A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 66 127 A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 66 128 A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 66 129 A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 66 130 A.26. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 66 131 A.27. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 67 132 A.28. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 67 133 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 70 135 1. Introduction 137 This document describes an extension mapping for version 1.0 of the 138 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 139 specifies a flexible schema that can be used to implement several 140 common use cases related to the provisioning and management of domain 141 name registrations and applications during the launch of a domain 142 name registry. 144 It is typical for domain registries to operate in special modes as 145 they begin operation to facilitate allocation of domain names, often 146 according to special rules. This document uses the term "launch 147 phase" and the shorter form "launch" to refer to such a period. 148 Multiple launch phases and multiple models are supported to enable 149 the launch of a domain name registry. What is supported and what is 150 validated is up to server policy. Communication of the server policy 151 is typically performed using an out-of-band mechanism that is not 152 specified in this document. 154 The EPP domain name mapping [RFC5731] is designed for the steady- 155 state operation of a registry. During a launch period, the model in 156 place may be different from what is defined in the EPP domain name 157 mapping [RFC5731]. For example, registries often accept multiple 158 applications for the same domain name during the "Sunrise" launch 159 phase, referred to as a Launch Application. A Launch Registration 160 refers to a registration made during a launch phase when the server 161 uses a "first-come, first-served" model. Even in a "first-come, 162 first-served" model, additional steps and information might be 163 required, such as trademark information. In addition, RFC 7848 164 [RFC7848] defines a registry interface for the Trademark Claims or 165 "claims" launch phase that includes support for presenting a 166 Trademark Claims Notice to the Registrant. This document proposes an 167 extension to the domain name mapping in order to provide a uniform 168 interface for the management of Launch Applications and Launch 169 Registrations in launch phases. 171 1.1. Conventions Used in This Document 173 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 174 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 175 document are to be interpreted as described in RFC 2119 [RFC2119]. 177 XML is case sensitive. Unless stated otherwise, XML specifications 178 and examples provided in this document MUST be interpreted in the 179 character case presented in order to develop a conforming 180 implementation. 182 In examples, "C:" represents lines sent by a protocol client and "S:" 183 represents lines returned by a protocol server. Indentation and 184 white space in examples are provided only to illustrate element 185 relationships and are not a REQUIRED feature of this protocol. The 186 use of "..." is used as shorthand for elements defined outside this 187 document. 189 A Launch Registration is a domain name registration during a launch 190 phase when the server uses a "first-come, first-served" model. Only 191 a single registration for a domain name can exist in the server at a 192 time. 194 A Launch Application represents the intent to register a domain name 195 during a launch phase when the server accepts multiple applications 196 for a domain name and the server later selects one of the 197 applications to allocate as a registration. Many Launch Applications 198 for a domain name can exist in the server at a time. 200 The XML namespace prefix "launch" is used for the namespace 201 "urn:ietf:params:xml:ns:launch-1.0", but implementations MUST NOT 202 depend on it and instead employ a proper namespace-aware XML parser 203 and serializer to interpret and output the XML documents. 205 The XML namespace prefix "smd" is used for the [RFC7848] namespace 206 "urn:ietf:params:xml:ns:signedMark-1.0", but implementations MUST NOT 207 depend on it and instead employ a proper namespace-aware XML parser 208 and serializer to interpret and output the XML documents. 210 The XML namespace prefix "mark" is used for the [RFC7848] namespace 211 "urn:ietf:params:xml:ns:mark-1.0", but implementations MUST NOT 212 depend on it and instead employ a proper namespace-aware XML parser 213 and serializer to interpret and output the XML documents. 215 2. Object Attributes 217 This extension adds additional elements to the EPP domain name 218 mapping [RFC5731]. Only those new elements are described here. 220 2.1. Application Identifier 222 Servers MAY allow multiple applications, referred to as a Launch 223 Application, of the same domain name during its launch phase 224 operations. Upon receiving a valid command to create 225 a Launch Application, the server MUST create an application object 226 corresponding to the request, assign an application identifier for 227 the Launch Application, set the [RFC5731] pendingCreate status, and 228 return the application identifier to the client with the 229 element. In order to facilitate correlation, 230 all subsequent launch operations on the Launch Application MUST be 231 qualified by the previously assigned application identifier using the 232 element. 234 2.2. Validator Identifier 236 The Validator Identifier is the identifier unique to the server, for 237 a Trademark Validator that validates marks and has a repository of 238 validated marks. The OPTIONAL "validatorID" attribute is used to 239 define the Validator Identifier of the Trademark Validator. 240 Registries MAY support more than one Third Party Trademark Validator. 241 The unique set of Validator Identifier values supported by the server 242 is up to server policy. The Internet Corporation for Assigned Names 243 and Numbers (ICANN) Trademark Clearinghouse (TMCH) is the default 244 Trademark Validator and is reserved the Validator Identifier of 245 "tmch". If the ICANN TMCH is not used or multiple Trademark 246 Validators are used, the Validator Identifier MUST be defined using 247 the "validatorID" attribute. 249 The Validator Identifier MAY be related to one or more issuer 250 identifiers of the element and the element defined 251 in [RFC7848]. Both the Validator Identifier and the Issuer 252 Identifier used MUST be unique in the server. If the ICANN TMCH is 253 not used or multiple Trademark Validators are used, the server MUST 254 define the list of supported validator identifiers and MUST make this 255 information available to clients using a mutually acceptable, out-of- 256 band mechanism. 258 The Validator Identifier may define a non-Trademark Validator that 259 supports a form of claims, where claims and a Validator Identifier 260 can be used for purposes beyond trademarks. 262 2.3. Launch Phases 264 The server MAY support multiple launch phases sequentially or 265 simultaneously. The element MUST be included by the 266 client to define the target launch phase of the command. The server 267 SHOULD validate the phase and MAY validate the sub-phase of the 268 element against the active phase and OPTIONAL sub- 269 phase of the server, and return an EPP error result code of 2306 if 270 there is a mismatch. 272 The following launch phase values are defined: 274 sunrise: The phase during which trademark holders can submit 275 registrations or applications with trademark information that can 276 be validated by the server. 277 landrush: A post-Sunrise phase when non-trademark holders are 278 allowed to register domain names with steps taken to address a 279 large volume of initial registrations. 280 claims: The phase, as defined in the Section 2.3.1, in which a 281 Claims Notice must be displayed to a prospective registrant of a 282 domain name that matches trademarks. 283 open: A phase that is also referred to as "steady state". Servers 284 may require additional trademark protection during this phase. 285 custom: A custom server launch phase that is defined using the 286 "name" attribute. 288 For extensibility, the element includes an OPTIONAL 289 "name" attribute that can define a sub-phase, or the full name of the 290 phase when the element has the "custom" value. For 291 example, the "claims" launch phase could have two sub-phases that 292 include "landrush" and "open". 294 Launch phases MAY overlap to support the "claims" launch phase, 295 defined in the Section 2.3.1, and to support a traditional "landrush" 296 launch phase. The overlap of the "claims" and "landrush" launch 297 phases SHOULD be handled by setting "claims" as the 298 value and setting "landrush" as the sub-phase with the "name" 299 attribute. For example, the element should be 300 claims. 302 2.3.1. Trademark Claims Phase 304 The Trademark Claims Phase is when a Claims Notice must be displayed 305 to a prospective registrant of a domain name that matches trademarks. 306 See [I-D.ietf-regext-tmch-func-spec] for additional details of 307 trademark claims handling. The source of the trademarks is a 308 Trademark Validator and the source of the Claims Notice information 309 is a Claim Notice Information Service (CNIS), which may be directly 310 linked to a Trademark Validator. The client interfaces with the 311 server to determine if a trademark exists for a domain name, 312 interfaces with a CNIS to get the Claims Notice information, and 313 interfaces with the server to pass the Claims Notice acceptance 314 information in a create command. This document supports the 315 Trademark Claims Phase in two ways including: 317 Claims Check Form: Is defined in Section 3.1.1 and is used to 318 determine whether or not there are any matching trademarks for a 319 domain name. If there is at least one matching trademark that 320 exists for the domain name, a claims key is returned. The mapping 321 of domain names and the claims keys is based on an out-of-band 322 interface between the server and the Trademark Validator. The 323 CNIS associated with the claims key Validator Identifier 324 (Section 2.2) MUST accept the claims key as the basis for 325 retrieving the claims information. 326 Claims Create Form: Is defined in Section 3.3.2 and is used to pass 327 the Claims Notice acceptance information in a create command. The 328 notice identifier () format, validation rules, 329 and server processing is up to the interface between the server 330 and the Trademark Validator. The CNIS associated with the 331 Validator Identifier (Section 2.2) MUST generate a notice 332 identifier compliant with the element. 334 The following shows the Trademark Claims Phase registration flow: 336 .------------. .--------. .--------. .------. 337 | Registrant | | Client | | Server | | CNIS | 338 '------------' '--------' '--------' '------' 339 | Request Domain | | | 340 | Registration | | | 341 |--------------->| Domain Check | | 342 | |--------------------------->| | 343 | Domain | Domain Unavailable .------------. | 344 | Unavailable |<---------------------( Available? ) | 345 |<---------------| No '------------' | 346 | | Domain Available | Yes | 347 | |<---------------------------| | 348 | | Domain Claims Check | | 349 | |--------------------------->| | 350 | | .---------. | 351 | | Claims Don't Exist / Does \ | 352 | |<--------------------( Domain have ) | 353 | | No \ Claims? / | 354 | | '---------' | 355 | | Domain Create | | Yes | 356 | |--------------------------->| | | 357 | Domain | Domain Registered | | | 358 | Registered |<---------------------------| | | 359 |<---------------| | | 360 | | | 361 | | Claims Exist with Claims Keys | | 362 | |<------------------------------' | 363 | | | 364 .-----. | | Request Claims Info with Claims Key | 365 |Abort| | Display |-------------------------------------->| 366 '-----' | Claims | Return Claims Info | 367 ^ | Notice |<--------------------------------------| 368 | No |<---------------| | 369 | .------. Yes | | 370 '-( Ack? )----------->| Domain Claims Create Form | | 371 '------' |--------------------------->| | 372 | Registration | Error .----------------------. | 373 | Error |<-----------( Validation Successful? ) | 374 |<---------------| No '----------------------' | 375 | | | Yes | 376 | Domain | Domain Registered | | 377 | Registered |<---------------------------| | 378 |<---------------| | | 380 Figure 1 382 2.4. Status Values 384 A Launch Application or Launch Registration object MAY have a launch 385 status value. The element is used to convey the 386 launch status pertaining to the object, beyond what is specified in 387 the object mapping. A Launch Application or Launch Registration MUST 388 set the [RFC5731] "pendingCreate" status if a launch status is 389 supported and the launch status is not one of the final statuses 390 ("allocated" and "rejected"). 392 The following status values are defined using the required "s" 393 attribute: 395 pendingValidation: The initial state of a newly-created application 396 or registration object. The application or registration requires 397 validation, but the validation process has not yet completed. 398 validated: The application or registration meets relevant registry 399 rules. 400 invalid: The application or registration does not validate according 401 to registry rules. Server policies permitting, it may transition 402 back into "pendingValidation" for revalidation, after 403 modifications are made to ostensibly correct attributes that 404 caused the validation failure. 405 pendingAllocation: The allocation of the application or registration 406 is pending based on the results of some out-of-band process (for 407 example, an auction). 408 allocated: The object corresponding to the application or 409 registration has been provisioned. This is a possible end state 410 of an application or registration object. 411 rejected: The application or registration object was not 412 provisioned. This is a possible end state of an application or 413 registration object. 414 custom: A custom status that is defined using the "name" attribute. 416 Each status value MAY be accompanied by a string of human-readable 417 text that describes the rationale for the status applied to the 418 object. The OPTIONAL "lang" attribute, as defined in [RFC5646], MAY 419 be present to identify the language if the negotiated value is 420 something other than the default value of "en" (English). 422 For extensibility the element includes an OPTIONAL 423 "name" attribute that can define a sub-status or the full name of the 424 status when the status value is "custom". The server SHOULD use one 425 of the non-"custom" status values. 427 Status values MAY be skipped. For example, an application or 428 registration MAY immediately start at the "allocated" status or an 429 application or registration MAY skip the "pendingAllocation" status. 431 If the launch phase does not require validation of a request, an 432 application or registration MAY immediately skip to 433 "pendingAllocation". 435 2.4.1. State Transition 436 The transitions between the states is a matter of server policy. 437 This diagram defines one possible set of permitted transitions. 439 | request 440 | 441 | +--------------------------+ 442 | | | 443 v v | 444 +-------------------+ | 445 | | | 446 | pendingValidation +--------------+ | 447 | | | | 448 +---------+---------+ | | 449 | | | 450 | | | 451 v v | 452 +-----------+ +---------+ | 453 | | | | | 454 | validated | | invalid +--+ 455 | | | | 456 +-----+-----+ +----+----+ 457 | | 458 | | 459 v | 460 +-------------------+ | 461 | | | 462 | pendingAllocation +-----------+ | 463 | | | | 464 +---------+---------+ | | 465 | | | 466 | | | 467 | | | 468 | | | 469 | | | 470 v v v 471 +---------+ +--------+ 472 / \ / \ 473 | allocated | | rejected | 474 \ / \ / 475 +---------+ +--------+ 477 Figure 2 479 2.5. Poll Messaging 481 A Launch Application MUST be handled as an EPP domain name object as 482 specified in RFC 5731 [RFC5731], with the "pendingCreate" status and 483 with the launch status values defined in Section 2.4. A Launch 484 Registration MUST be handled as an EPP domain name object as 485 specified in RFC 5731 [RFC5731], with the "pendingCreate" status and 486 with the launch status values defined in Section 2.4 As a Launch 487 Application or Launch Registration transitions between the status 488 values defined in Section 2.4, the server SHOULD insert poll 489 messages, per [RFC5730], for the applicable intermediate statuses, 490 including the "pendingValidation", "validated", "pendingAllocation, 491 and "invalid" statuses, using the element with the 492 extension. The element MAY contain 493 non-mandatory information, like contact and name server information. 494 Also, further extensions that would normally be included in the 495 response of a command, per [RFC5731], MAY be included. 496 For the final statuses, including the "allocated" and "rejected" 497 statuses, the server MUST insert a poll message, per 498 [RFC5731], with the extension. 500 The following is an example poll message for a Launch Application 501 that has transitioned to the "pendingAllocation" state. 503 S: 504 S: 505 S: 506 S: 507 S: Command completed successfully; ack to dequeue 508 S: 509 S: 510 S: 2013-04-04T22:01:00.0Z 511 S: Application pendingAllocation. 512 S: 513 S: 514 S: 516 S: domain.example 517 S: ... 518 S: 519 S: 520 S: 521 S: 523 S: sunrise 524 S: abc123 525 S: 526 S: 527 S: 528 S: 529 S: ABC-12345 530 S: 54322-XYZ 531 S: 532 S: 533 S: 534 The following is an example poll message for an 535 "allocated" Launch Application. 537 S: 538 S: 539 S: 540 S: 541 S: Command completed successfully; ack to dequeue 542 S: 543 S: 544 S: 2013-04-04T22:01:00.0Z 545 S: Application successfully allocated. 546 S: 547 S: 548 S: 550 S: domain.example 551 S: 552 S: ABC-12345 553 S: 54321-XYZ 554 S: 555 S: 2013-04-04T22:00:00.0Z 556 S: 557 S: 558 S: 559 S: 561 S: sunrise 562 S: abc123 563 S: 564 S: 565 S: 566 S: 567 S: BCD-23456 568 S: 65432-WXY 569 S: 570 S: 571 S: 572 The following is an example poll message for an 573 "allocated" Launch Registration. 575 S: 576 S: 577 S: 578 S: 579 S: Command completed successfully; ack to dequeue 580 S: 581 S: 582 S: 2013-04-04T22:01:00.0Z 583 S: Registration successfully allocated. 584 S: 585 S: 586 S: 588 S: domain.example 589 S: 590 S: ABC-12345 591 S: 54321-XYZ 592 S: 593 S: 2013-04-04T22:00:00.0Z 594 S: 595 S: 596 S: 597 S: 599 S: sunrise 600 S: 601 S: 602 S: 603 S: 604 S: BCD-23456 605 S: 65432-WXY 606 S: 607 S: 608 S: 610 2.6. Mark Validation Models 612 A server MUST support at least one of the following models for 613 validating trademark information: 615 code: Use of a mark code by itself to validate that the mark matches 616 the domain name. This model is supported using the 617 element with just the element. 618 mark: The mark information is passed without any other validation 619 element. The server will use some custom form of validation to 620 validate that the mark information is authentic. This model is 621 supported using the element with just the 622 (Section 2.6.2) element. 623 code with mark: A code is used along with the mark information by 624 the server to validate the mark utilizing an external party. The 625 code represents some form of secret that matches the mark 626 information passed. This model is supported using the 627 element that contains both the and 628 the (Section 2.6.2) elements. 629 signed mark: The mark information is digitally signed as described 630 in the Digital Signature (Section 2.6.3) section. The digital 631 signature can be directly validated by the server using the public 632 key of the external party that created the signed mark using its 633 private key. This model is supported using the 634 (Section 2.6.3.1) and (Section 2.6.3.2) 635 elements. 637 More than one , (Section 2.6.3.1), 638 or (Section 2.6.3.2) element MAY be 639 specified. The maximum number of marks per domain name is up to 640 server policy. 642 2.6.1. element 644 The element is used by the "code", "mark", and 645 "code with mark" validation models, has the following child elements: 647 : OPTIONAL mark code used to validate the 648 (Section 2.6.2) information. The mark code is be a mark-specific 649 secret that the server can verify against a third party. The 650 OPTIONAL "validatorID" attribute is the Validator Identifier 651 (Section 2.2) whose value indicates which Trademark Validator that 652 the code originated from, with no default value. 653 : OPTIONAL mark information with child elements defined 654 in the Mark (Section 2.6.2) section. 656 The following is an example element with both a 657 and (Section 2.6.2) element. 659 660 661 49FD46E6C4B45C55D4AC 662 663 ... 664 665 667 2.6.2. element 669 A element describes an applicant's prior right to a given 670 domain name that is used with the "mark", "mark with code", and the 671 "signed mark" validation models. The element is defined 672 in [RFC7848]. A new mark format can be supported by creating a new 673 XML schema for the mark that has an element that substitutes for the 674 element from [RFC7848]. 676 2.6.3. Digital Signature 678 Digital signatures MAY be used by the server to validate the mark 679 information, when using the "signed mark" validation model with the 680 (Section 2.6.3.1) element and the 681 (Section 2.6.3.2) element. When using 682 digital signatures the server MUST validate the digital signature. 684 2.6.3.1. element 686 The element contains the digitally signed mark 687 information. The element is defined in [RFC7848]. 688 A new signed mark format can be supported by creating a new XML 689 schema for the signed mark that has an element that substitutes for 690 the element from [RFC7848]. 692 2.6.3.2. element 694 The element contains an encoded form of the 695 digitally signed (Section 2.6.3.1) element. The 696 element is defined in [RFC7848]. A new 697 encoded signed mark format can be supported by creating a new XML 698 schema for the encoded signed mark that has an element that 699 substitutes for the element from [RFC7848]. 701 3. EPP Command Mapping 703 A detailed description of the EPP syntax and semantics can be found 704 in the EPP core protocol specification [RFC5730]. The command 705 mappings described here are specifically for use in the Launch Phase 706 Extension. 708 This mapping is designed to be flexible, requiring only a minimum set 709 of required elements. 711 While it is meant to serve several use cases, it does not prescribe 712 any interpretation by the client or server. Such processing is 713 typically highly policy-dependent and therefore specific to 714 implementations. 716 Operations on application objects are done via one or more of the 717 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 718 Registries MAY choose to support a subset of the operations. 720 3.1. EPP Command 722 There are three forms of the extension to the EPP command: 723 the Claims Check Form (Section 3.1.1), the Availability Check Form 724 (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The 725 element "type" attribute defines the form, with the 726 value of "claims" for the Claims Check Form (Section 3.1.1), with the 727 value of "avail" for the Availability Check Form (Section 3.1.2), and 728 with the value of "trademark" for the Trademark Check Form 729 (Section 3.1.3). The default value of the "type" attribute is 730 "claims". The forms supported by the server is determined by server 731 policy. The server MUST return an EPP error result code of 2307 if 732 it receives a check form that is not supported. 734 3.1.1. Claims Check Form 736 The Claims Check Form defines a new command called the Claims Check 737 Command that is used to determine whether or not there are any 738 matching trademarks, in the specified launch phase, for each domain 739 name passed in the command, that requires the use of the "Claims 740 Create Form" on a Domain Create Command. The availability check 741 information defined in the EPP domain name mapping [RFC5731] MUST NOT 742 be returned for the Claims Check Command. This form is the default 743 form and MAY be explicitly identified by setting the 744 "type" attribute to "claims". 746 Instead of returning whether the domain name is available, the Claims 747 Check Command will return whether or not at least one matching 748 trademark exists for the domain name, that requires the use of the 749 "Claims Create Form" on a Domain Create Command. If there is at 750 least one matching trademark that exists for the domain name, a 751 element is returned. The client MAY then use the 752 value of the element to obtain information needed 753 to generate the Trademark Claims Notice from Trademark Validator 754 based on the Validator Identifier (Section 2.2). The unique notice 755 identifier of the Trademark Claims Notice MUST be passed in the 756 element of the extension to the Create Command 757 (Section 3.3). 759 The elements in the EPP command of EPP domain 760 name mapping [RFC5731] define the domain names to check for matching 761 trademarks. The element contains the following child 762 elements: 764 : Contains the value of the active launch phase of the 765 server. The server SHOULD validate the value according to 766 Section 2.3. 768 Example Claims Check command using the domain command and the 769 extension with the "type" explicitly set to "claims", 770 to determine if "domain1.example", "domain2.example", and 771 "domain3.example" require claims notices during the "claims" launch 772 phase: 774 C: 775 C: 776 C: 777 C: 778 C: 780 C: domain1.example 781 C: domain2.example 782 C: domain3.example 783 C: 784 C: 785 C: 786 C: 789 C: claims 790 C: 791 C: 792 C: ABC-12345 793 C: 794 C: 796 If the command has been processed successfully, the EPP 797 MUST contain an element that 798 identifies the launch namespace. The element 799 contains the following child elements: 801 : The phase that mirrors the element 802 included in the . 803 : One or more elements that contain the 804 following child elements: 806 : Contains the fully qualified name of the queried 807 domain name. This element MUST contain an "exists" attribute 808 whose value indicates if a matching trademark exists for the 809 domain name that requires the use of the "Claims Create Form" 810 on a Domain Create Command. A value of "1" (or "true") means 811 that a matching trademark does exist and that the "Claims 812 Create Form" is required on a Domain Create Command. A value 813 of "0" (or "false") means that a matching trademark does not 814 exist or that the "Claims Create Form" is NOT required on a 815 Domain Create Command. 816 : Zero or more OPTIONAL claim keys that MAY be 817 passed to a third-party Trademark Validator such as the ICANN 818 Trademark Clearinghouse (TMCH) for querying the information 819 needed to generate a Trademark Claims Notice. The 820 is used as the key for the query in place 821 of the domain name to securely query the service without 822 using a well-known value like a domain name. The OPTIONAL 823 "validatorID" attribute is the Validator Identifier 824 (Section 2.2) whose value indicates which Trademark Validator 825 to query for the Claims Notice information, with the default 826 being the ICANN TMCH. The "validatorID" attribute MAY 827 reference a non-trademark claims clearinghouse identifier to 828 support other forms of claims notices. 830 Example Claims Check response when a claims notice is not required 831 for the domain name domain1.example, a claims notice is required for 832 the domain name domain2.example in the "tmch", and a claims notice is 833 required for the domain name domain3.example in the "tmch" and 834 "custom-tmch", for the "claims" launch phase: 836 S: 837 S: 838 S: 839 S: 840 S: Command completed successfully 841 S: 842 S: 843 S: 845 S: claims 846 S: 847 S: domain1.example 848 S: 849 S: 850 S: domain2.example 851 S: 852 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 853 S: 854 S: 855 S: 856 S: domain3.example 857 S: 858 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 859 S: 860 S: 861 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 862 S: 863 S: 864 S: 865 S: 866 S: 867 S: ABC-12345 868 S: 54321-XYZ 869 S: 870 S: 871 S: 873 3.1.2. Availability Check Form 875 The Availability Check Form defines additional elements to extend the 876 EPP command described in the EPP domain name mapping 877 [RFC5731]. No additional elements are defined for the EPP 878 response. This form MUST be identified by setting the 879 "type" attribute to "avail". 881 The EPP command is used to determine if an object can be 882 provisioned within a repository. Domain names may be made available 883 only in unique launch phases, whilst remaining unavailable for 884 concurrent launch phases. In addition to the elements expressed in 885 the , the command is extended with the 886 element that contains the following child elements: 888 : The launch phase to which domain name availability 889 should be determined. The server SHOULD validate the value and 890 return an EPP error result code of 2306 if it is invalid. 892 Example Availability Check Form command using the domain 893 command and the extension with the "type" set to 894 "avail", to determine the availability of two domain names in the 895 "idn-release" custom launch phase: 897 C: 898 C: 899 C: 900 C: 901 C: 903 C: domain1.example 904 C: domain2.example 905 C: 906 C: 907 C: 908 C: 911 C: custom 912 C: 913 C: 914 C: ABC-12345 915 C: 916 C: 918 The Availability Check Form does not define any extension to the 919 response of an domain command. After processing the command, 920 the server replies with a standard EPP response as defined in the EPP 921 domain name mapping [RFC5731]. 923 3.1.3. Trademark Check Form 925 The Trademark Check Form defines a new command called the Trademark 926 Check Command that is used to determine whether or not there are any 927 matching trademarks for each domain name passed in the command, 928 independent of the active launch phase of the server and whether the 929 "Claims Create Form" is required on a Domain Create Command. The 930 availability check information defined in the EPP domain name mapping 931 [RFC5731] MUST NOT be returned for the Trademark Check Command. This 932 form MUST be identified by setting the "type" 933 attribute to "trademark". 935 Instead of returning whether the domain name is available, the 936 Trademark Check Command will return whether or not at least one 937 matching trademark exists for the domain name. If there is at least 938 one matching trademark that exists for the domain name, a 939 element is returned. The client MAY then use the 940 value of the element to obtain Trademark Claims 941 Notice information from Trademark Validator based on the Validator 942 Identifier (Section 2.2). 944 The elements in the EPP command of EPP domain 945 name mapping [RFC5731] define the domain names to check for matching 946 trademarks. The element does not contain any child 947 elements with the "Trademark Check Form": 949 Example Trademark Check command using the domain command and 950 the extension with the "type" set to "trademark", to 951 determine if "domain1.example", "domain2.example", and 952 "domain3.example" have any matching trademarks: 954 C: 955 C: 956 C: 957 C: 958 C: 960 C: domain1.example 961 C: domain2.example 962 C: domain3.example 963 C: 964 C: 965 C: 966 C: 969 C: 970 C: ABC-12345 971 C: 972 C: 974 If the command has been processed successfully, the EPP 975 MUST contain an element that 976 identifies the launch namespace. The element 977 contains the following child elements: 979 : One or more elements that contain the 980 following child elements: 982 : Contains the fully qualified name of the queried 983 domain name. This element MUST contain an "exists" attribute 984 whose value indicates if a matching trademark exists for the 985 domain name. A value of "1" (or "true") means that a 986 matching trademark does exist. A value of "0" (or "false") 987 means that a matching trademark does not exist. 988 : Zero or more OPTIONAL claim keys that MAY be 989 passed to a third-party Trademark Validator such as the ICANN 990 Trademark Clearinghouse (TMCH) for querying the information 991 needed to generate a Trademark Claims Notice. The 992 is used as the key for the query in place 993 of the domain name to securely query the service without 994 using a well-known value like a domain name. The OPTIONAL 995 "validatorID" attribute is the Validator Identifier 996 (Section 2.2) whose value indicates which Trademark Validator 997 to query for the Claims Notice information, with the default 998 being the ICANN TMCH. The "validatorID" attribute MAY 999 reference a non-trademark claims clearinghouse identifier to 1000 support other forms of claims notices. 1002 Example Trademark Check response when no matching trademarks are 1003 found for the domain name domain1.example, matching trademarks are 1004 found for the domain name domain2.example in the "tmch", matching 1005 trademarks are found for domain name domain3.example in the "tmch" 1006 and "custom-tmch", for the "claims" launch phase: 1008 S: 1009 S: 1010 S: 1011 S: 1012 S: Command completed successfully 1013 S: 1014 S: 1015 S: 1017 S: 1018 S: domain1.example 1019 S: 1020 S: 1021 S: domain2.example 1022 S: 1023 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 1024 S: 1025 S: 1026 S: 1027 S: domain3.example 1028 S: 1029 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 1030 S: 1031 S: 1032 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 1033 S: 1034 S: 1035 S: 1036 S: 1037 S: 1038 S: ABC-12345 1039 S: 54321-XYZ 1040 S: 1041 S: 1042 S: 1044 3.2. EPP Command 1046 This extension defines additional elements to extend the EPP 1047 command and response to be used in conjunction with the EPP domain 1048 name mapping [RFC5731]. 1050 The EPP command is used to retrieve information for a launch 1051 phase registration or application. The Application Identifier 1052 (Section 2.1) returned in the element of the create 1053 response (Section 3.3) can be used for retrieving information for a 1054 Launch Application. A element is sent along with the 1055 regular domain command. The element includes an 1056 OPTIONAL "includeMark" boolean attribute, with a default value of 1057 "false", to indicate whether or not to include the mark in the 1058 response. The element contains the following child 1059 elements: 1061 : The phase during which the application or 1062 registration was submitted or is associated with. Server policy 1063 defines the phases that are supported. The server SHOULD 1064 validate the value and return an EPP error result code of 2306 if 1065 it is invalid. 1066 : OPTIONAL application identifier of the 1067 Launch Application. 1069 Example domain command with the extension to 1070 retrieve information for the sunrise application for domain.example 1071 and application identifier "abc123": 1073 C: 1074 C: 1075 C: 1076 C: 1077 C: 1079 C: domain.example 1080 C: 1081 C: 1082 C: 1083 C: 1086 C: sunrise 1087 C: abc123 1088 C: 1089 C: 1090 C: ABC-12345 1091 C: 1092 C: 1094 Example domain command with the extension to 1095 retrieve information for the sunrise registration for domain.example: 1097 C: 1098 C: 1099 C: 1100 C: 1101 C: 1103 C: domain.example 1104 C: 1105 C: 1106 C: 1107 C: 1109 C: sunrise 1110 C: 1111 C: 1112 C: ABC-12345 1113 C: 1114 C: 1115 If the query was successful, the server replies with a 1116 element along with the regular EPP . The 1117 contains the following child elements: 1119 : The phase during which the application was 1120 submitted, or is associated with, that matches the associated 1121 command . 1122 : OPTIONAL Application Identifier of the 1123 Launch Application. 1124 : OPTIONAL status of the Launch Application using one 1125 of the supported status values (Section 2.4). 1126 : Zero or more (Section 2.6.2) elements only 1127 if the "includeMark" attribute is "true" in the command. 1129 Example domain response using the extension 1130 with the mark information: 1132 S: 1133 S: 1134 S: 1135 S: 1136 S: Command completed successfully 1137 S: 1138 S: 1139 S: 1141 S: domain.example 1142 S: EXAMPLE1-REP 1143 S: 1144 S: jd1234 1145 S: sh8013 1146 S: sh8013 1147 S: ClientX 1148 S: ClientY 1149 S: 2012-04-03T22:00:00.0Z 1150 S: 1151 S: 2fooBAR 1152 S: 1153 S: 1154 S: 1155 S: 1156 S: 1158 S: sunrise 1159 S: abc123 1160 S: 1161 S: 1163 S: ... 1164 S: 1165 S: 1166 S: 1167 S: 1168 S: ABC-12345 1169 S: 54321-XYZ 1170 S: 1171 S: 1172 S: 1174 3.3. EPP Command 1176 There are four forms of the extension to the EPP command 1177 that include the Sunrise Create Form (Section 3.3.1), the Claims 1178 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 1179 and the Mixed Create Form (Section 3.3.4). The form is dependent on 1180 the supported launch phases (Section 2.3) as defined below. 1182 sunrise: The EPP command with the "sunrise" launch phase is 1183 used to submit a registration with trademark information that can 1184 be verified by the server with the value. The 1185 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 1186 launch phase. 1187 landrush: The EPP command with the "landrush" launch phase 1188 MAY use the General Create Form (Section 3.3.3) to explicitly 1189 specify the phase and optionally define the expected type of 1190 object to create. 1191 claims: The EPP command with the "claims" launch phase is 1192 used to pass the information associated with the presentation and 1193 acceptance of the Claims Notice. The Claims Create Form 1194 (Section 3.3.2) is used and the General Create Form 1195 (Section 3.3.3) MAY be used for the "claims" launch phase. 1196 open: The EPP command with the "open" launch phase is 1197 undefined but the form supported is up to server policy. Use of 1198 the Claims Create Form (Section 3.3.2) MAY be used to pass the 1199 information associated with the presentation and acceptance of the 1200 Claims Notice if required for the domain name. 1201 custom: The EPP command with the "custom" launch phase is 1202 undefined but the form supported is up to server policy. 1204 3.3.1. Sunrise Create Form 1206 The Sunrise Create Form of the extension to the EPP domain name 1207 mapping [RFC5731] includes the verifiable trademark information that 1208 the server uses to match against the domain name to authorize the 1209 domain create. A server MUST support one of four models in Claim 1210 Validation Models (Section 2.6) to verify the trademark information 1211 passed by the client. 1213 A element is sent along with the regular 1214 domain command. The element has an OPTIONAL "type" 1215 attribute that defines the expected type of object ("application" or 1216 "registration") to create. The server SHOULD validate the "type" 1217 attribute, when passed, against the type of object that will be 1218 created, and return an EPP error result code of 2306 if the type is 1219 incorrect. The element contains the following child 1220 elements: 1222 : The identifier for the launch phase. The server 1223 SHOULD validate the value according to Section 2.3. 1224 or or : 1226 : Zero or more elements. The 1227 child elements are defined in the 1228 element (Section 2.6.1) section. 1229 : Zero or more elements. The 1230 child elements are defined in the 1231 element (Section 2.6.3.1) section. 1232 : Zero or more 1233 elements. The child elements are 1234 defined in the element 1235 (Section 2.6.3.2) section. 1237 The following is an example domain command using the 1238 extension, following the "code" validation model, 1239 with multiple sunrise codes: 1241 C: 1242 C: 1243 C: 1244 C: 1245 C: 1247 C: domain.example 1248 C: jd1234 1249 C: sh8013 1250 C: sh8013 1251 C: 1252 C: 2fooBAR 1253 C: 1254 C: 1255 C: 1256 C: 1257 C: 1259 C: sunrise 1260 C: 1261 C: 1262 C: 49FD46E6C4B45C55D4AC 1263 C: 1264 C: 1265 C: 49FD46E6C4B45C55D4AD 1266 C: 1267 C: 1268 C: 1269 C: 49FD46E6C4B45C55D4AE 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 "mark" validation model, 1278 with the mark information: 1280 C: 1281 C: 1282 C: 1283 C: 1284 C: 1286 C: domainone.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: 1302 C: ... 1303 C: 1304 C: 1305 C: 1306 C: 1307 C: ABC-12345 1308 C: 1309 C: 1310 The following is an example domain command using the 1311 extension, following the "code with mark" validation 1312 model, with a code and mark information: 1314 C: 1315 C: 1316 C: 1317 C: 1318 C: 1320 C: domain.example 1321 C: jd1234 1322 C: sh8013 1323 C: sh8013 1324 C: 1325 C: 2fooBAR 1326 C: 1327 C: 1328 C: 1329 C: 1330 C: 1332 C: sunrise 1333 C: 1334 C: 1335 C: 49FD46E6C4B45C55D4AC 1336 C: 1338 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 signed mark information for a sunrise application: 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: 1369 C: sunrise 1370 C: 1372 C: ... 1373 C: 1374 C: 1375 C: 1376 C: ABC-12345 1377 C: 1378 C: 1379 The following is an example domain command using the 1380 extension, following the "signed mark" validation 1381 model, with the base64 encoded signed mark information: 1383 C: 1384 C: 1385 C: 1386 C: 1387 C: 1389 C: domainone.example 1390 C: jd1234 1391 C: sh8013 1392 C: sh8013 1393 C: 1394 C: 2fooBAR 1395 C: 1396 C: 1397 C: 1398 C: 1399 C: 1401 C: sunrise 1402 C: 1404 C: ... 1405 C: 1406 C: 1407 C: 1408 C: ABC-12345 1409 C: 1410 C: 1412 3.3.2. Claims Create Form 1414 The Claims Create Form of the extension to the EPP domain name 1415 mapping [RFC5731] includes the information related to the 1416 registrant's acceptance of the Claims Notice. 1418 A element is sent along with the regular 1419 domain command. The element has an OPTIONAL "type" 1420 attribute that defines the expected type of object ("application" or 1421 "registration") to create. The server SHOULD validate the "type" 1422 attribute, when passed, against the type of object that will be 1423 created, and return an EPP error result code of 2306 if the type is 1424 incorrect. The element contains the following child 1425 elements: 1427 : Contains the value of the active launch phase of the 1428 server. The server SHOULD validate the value according to 1429 Section 2.3. 1430 : One or more elements that contain 1431 the following child elements: 1433 : Unique notice identifier for the Claims 1434 Notice. The element has an OPTIONAL 1435 "validatorID" attribute is the Validator Identifier 1436 (Section 2.2) whose value indicates which Trademark Validator 1437 is the source of the claims notice, with the default being 1438 the ICANN TMCH. 1439 : Expiry of the claims notice. 1440 : Contains the date and time that the 1441 claims notice was accepted. 1443 The following is an example domain command using the 1444 extension with the information for 1445 the "tmch" and the "custom-tmch" validators, for the "claims" launch 1446 phase: 1448 C: 1449 C: 1450 C: 1451 C: 1452 C: 1454 C: domain.example 1455 C: jd1234 1456 C: sh8013 1457 C: sh8013 1458 C: 1459 C: 2fooBAR 1460 C: 1461 C: 1462 C: 1463 C: 1464 C: 1466 C: claims 1467 C: 1468 C: 1469 C: 370d0b7c9223372036854775807 1470 C: 2014-06-19T10:00:00.0Z 1471 C: 1472 C: 2014-06-19T09:00:00.0Z 1473 C: 1474 C: 1475 C: 1476 C: 1477 C: 470d0b7c9223654313275808 1478 C: 2014-06-19T10:00:00.0Z 1479 C: 1480 C: 2014-06-19T09:00:30.0Z 1481 C: 1482 C: 1483 C: 1484 C: 1485 C: ABC-12345 1486 C: 1487 C: 1489 3.3.3. General Create Form 1491 The General Create Form of the extension to the EPP domain name 1492 mapping [RFC5731] includes the launch phase and optionally the object 1493 type to create. The OPTIONAL "type" attribute defines the expected 1494 type of object ("application" or "registration") to create. The 1495 server SHOULD validate the "type" attribute, when passed, against the 1496 type of object that will be created, and return an EPP error result 1497 code of 2306 if the type is incorrect. 1499 A element is sent along with the regular 1500 domain command. The element contains the following 1501 child elements: 1503 : Contains the value of the active launch phase of the 1504 server. The server SHOULD validate the value according to 1505 Section 2.3. 1507 The following is an example domain command using the 1508 extension for a "landrush" launch phase application: 1510 C: 1511 C: 1512 C: 1513 C: 1514 C: 1516 C: domain.example 1517 C: jd1234 1518 C: sh8013 1519 C: sh8013 1520 C: 1521 C: 2fooBAR 1522 C: 1523 C: 1524 C: 1525 C: 1526 C: 1529 C: landrush 1530 C: 1531 C: 1532 C: ABC-12345 1533 C: 1534 C: 1536 3.3.4. Mixed Create Form 1538 The Mixed Create Form supports a mix of the create forms, where for 1539 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1540 Form (Section 3.3.2) MAY be supported in a single command by 1541 including both the verified trademark information and the information 1542 related to the registrant's acceptance of the Claims Notice. The 1543 server MAY support the Mixed Create Form. The "custom" launch phase 1544 SHOULD be used when using the Mixed Create Form. 1546 The following is an example domain command using the 1547 extension, with using a mix of the Sunrise Create 1548 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1549 including both a mark and a notice: 1551 C: 1552 C: 1553 C: 1554 C: 1555 C: 1557 C: domainone.example 1558 C: jd1234 1559 C: sh8013 1560 C: sh8013 1561 C: 1562 C: 2fooBAR 1563 C: 1564 C: 1565 C: 1566 C: 1567 C: 1570 C: custom 1571 C: 1572 C: 1574 C: ... 1575 C: 1576 C: 1577 C: 1578 C: 1579 C: 49FD46E6C4B45C55D4AC 1580 C: 1581 C: 2012-06-19T10:00:10.0Z 1582 C: 1583 C: 2012-06-19T09:01:30.0Z 1584 C: 1585 C: 1586 C: 1587 C: 1588 C: ABC-12345 1589 C: 1590 C: 1592 3.3.5. Create Response 1594 If the create was successful, the server MAY add a 1595 element along to the regular EPP to indicate the server 1596 generated Application Identifier (Section 2.1), when multiple 1597 applications of a given domain name are supported; otherwise no 1598 extension is included with the regular EPP . The 1599 element contains the following child elements: 1601 : The phase of the application that mirrors the 1602 element included in the . 1603 : The application identifier of the 1604 application. 1606 An example response when multiple overlapping applications are 1607 supported by the server: 1609 S: 1610 S: 1611 S: 1612 S: 1613 S: Command completed successfully; action pending 1614 S: 1615 S: 1616 S: 1618 S: domain.example 1619 S: 2010-08-10T15:38:26.623854Z 1620 S: 1621 S: 1622 S: 1623 S: 1625 S: sunrise 1626 S: 2393-9323-E08C-03B1 1627 S: 1628 S: 1629 S: 1630 S: 1631 S: ABC-12345 1632 S: 54321-XYZ 1633 S: 1634 S: 1635 S: 1637 3.4. EPP Command 1639 This extension defines additional elements to extend the EPP 1640 command to be used in conjunction with the domain name mapping. 1642 An EPP command with the extension sent to a server that does 1643 not support launch applications will fail. A server that does not 1644 support launch applications during its launch phase MUST return an 1645 EPP error result code of 2102 when receiving an EPP command 1646 with the extension. 1648 Registry policies permitting, clients may update an application 1649 object by submitting an EPP command along with a 1650 element to indicate the application object to be 1651 updated. The element contains the following child 1652 elements: 1654 : The phase during which the application was submitted 1655 or is associated with. The server SHOULD validate the value and 1656 return an EPP error result code of 2306 if it is invalid. 1657 : The application identifier for which the 1658 client wishes to update. 1660 The following is an example domain command with the 1661 extension to add and remove a name server of a 1662 sunrise application with the application identifier "abc123": 1664 C: 1665 C: 1666 C: 1667 C: 1668 C: 1670 C: domain.example 1671 C: 1672 C: 1673 C: ns2.domain.example 1674 C: 1675 C: 1676 C: 1677 C: 1678 C: ns1.domain.example 1679 C: 1680 C: 1681 C: 1682 C: 1683 C: 1684 C: 1686 C: sunrise 1687 C: abc123 1688 C: 1689 C: 1690 C: ABC-12345 1691 C: 1692 C: 1694 This extension does not define any extension to the response of an 1695 domain command. After processing the command, the server 1696 replies with a standard EPP response as defined in the EPP domain 1697 name mapping [RFC5731]. 1699 3.5. EPP Command 1701 This extension defines additional elements to extend the EPP 1702 command to be used in conjunction with the domain name mapping. 1704 A client MUST NOT pass the extension on an EPP command to a 1705 server that does not support launch applications. A server that does 1706 not support launch applications during its launch phase MUST return 1707 an EPP error result code of 2102 when receiving an EPP 1708 command with the extension. 1710 Registry policies permitting, clients MAY withdraw an application by 1711 submitting an EPP command along with a 1712 element to indicate the application object to be deleted. The 1713 element contains the following child elements: 1715 : The phase during which the application was submitted 1716 or is associated with. The server SHOULD validate the value and 1717 return an EPP error result code of 2306 if it is invalid. 1718 : The application identifier for which the 1719 client wishes to delete. 1721 The following is an example domain command with the 1722 extension: 1724 C: 1725 C: 1726 C: 1727 C: 1728 C: 1730 C: domain.example 1731 C: 1732 C: 1733 C: 1734 C: 1736 C: sunrise 1737 C: abc123 1738 C: 1739 C: 1740 C: ABC-12345 1741 C: 1742 C: 1744 This extension does not define any extension to the response of a 1745 domain command. After processing the command, the server 1746 replies with a standard EPP response as defined in the EPP domain 1747 name mapping [RFC5731]. 1749 3.6. EPP Command 1751 This extension does not define any extension to the EPP 1752 command or response described in the EPP domain name mapping 1753 [RFC5731]. 1755 3.7. EPP Command 1757 This extension does not define any extension to the EPP 1758 command or response described in the EPP domain name mapping 1759 [RFC5731]. 1761 4. Formal Syntax 1763 One schema is presented here that is the EPP Launch Phase Mapping 1764 schema. 1766 The formal syntax presented here is a complete schema representation 1767 of the object mapping suitable for automated validation of EPP XML 1768 instances. The BEGIN and END tags are not part of the schema; they 1769 are used to note the beginning and ending of the schema for URI 1770 registration purposes. 1772 4.1. Launch Schema 1774 Copyright (c) 2017 IETF Trust and the persons identified as authors 1775 of the code. All rights reserved. 1777 Redistribution and use in source and binary forms, with or without 1778 modification, are permitted provided that the following conditions 1779 are met: 1781 o Redistributions of source code must retain the above copyright 1782 notice, this list of conditions and the following disclaimer. 1783 o Redistributions in binary form must reproduce the above copyright 1784 notice, this list of conditions and the following disclaimer in 1785 the documentation and/or other materials provided with the 1786 distribution. 1787 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1788 names of specific contributors, may be used to endorse or promote 1789 products derived from this software without specific prior written 1790 permission. 1792 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1793 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1794 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1795 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1796 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1797 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1798 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1799 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1800 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1801 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1802 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1804 BEGIN 1805 1806 1816 1817 1818 1819 1821 1822 1823 Extensible Provisioning Protocol v1.0 1824 domain name 1825 extension schema 1826 for the launch phase processing. 1827 1828 1830 1831 1834 1837 1840 1843 1847 1848 1849 1850 1853 1856 1857 1859 1860 1861 1862 1864 1869 1870 1871 1872 1875 1876 1877 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1890 1891 1892 1893 1894 1895 1897 1898 1899 1900 1904 1905 1906 1908 1909 1910 1911 1912 1913 1915 1916 1917 1918 1922 1923 1924 1926 1927 1928 1929 1930 1931 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1946 1947 1948 1949 1950 1954 1958 1961 1962 1963 1965 1967 1968 1969 1973 1976 1977 1979 1980 1981 1982 1985 1986 1990 1993 1996 1997 2002 2003 2006 2008 2009 2010 2011 2012 2013 2014 2016 2017 2018 2019 2022 2025 2028 2029 2031 2032 2033 2034 2038 2039 2043 2045 2046 2047 2048 2049 2050 2051 2052 2054 2055 2056 2057 2060 2064 2065 2069 2071 2072 2075 2078 2082 2083 2084 2085 2089 2093 2094 2096 2097 2098 2101 2106 2107 2109 2110 2111 2112 2116 2117 2118 2120 2121 2122 2123 2127 2128 2129 2131 2132 2133 2134 2137 2141 2145 2149 2150 2152 2153 END 2155 5. IANA Considerations 2157 5.1. XML Namespace 2159 This document uses URNs to describe XML namespaces and XML schemas 2160 conforming to a registry mechanism described in [RFC3688]. 2162 Registration request for the launch namespace: 2164 URI: urn:ietf:params:xml:ns:launch-1.0 2165 Registrant Contact: IESG 2166 XML: None. Namespace URIs do not represent an XML specification. 2168 Registration request for the launch XML schema: 2170 URI: urn:ietf:params:xml:schema:launch-1.0 2171 Registrant Contact: IESG 2172 XML: See the "Formal Syntax" section of this document. 2174 5.2. EPP Extension Registry 2176 The EPP extension described in this document should be registered by 2177 the IANA in the EPP Extension Registry described in [RFC7451]. The 2178 details of the registration are as follows: 2180 Name of Extension: "Launch Phase Mapping for the Extensible 2181 Provisioning Protocol (EPP)" 2182 Document status: Standards Track 2184 Reference: (insert reference to RFC version of this document) 2186 Registrant Name and Email Address: IESG, 2188 TLDs: Any 2190 IPR Disclosure: None 2192 Status: Active 2194 Notes: None 2196 6. Implementation Status 2198 Note to RFC Editor: Please remove this section and the reference to 2199 RFC 7942 [RFC7942] before publication. 2201 This section records the status of known implementations of the 2202 protocol defined by this specification at the time of posting of this 2203 Internet-Draft, and is based on a proposal described in RFC 7942 2204 [RFC7942]. The description of implementations in this section is 2205 intended to assist the IETF in its decision processes in progressing 2206 drafts to RFCs. Please note that the listing of any individual 2207 implementation here does not imply endorsement by the IETF. 2208 Furthermore, no effort has been spent to verify the information 2209 presented here that was supplied by IETF contributors. This is not 2210 intended as, and must not be construed to be, a catalog of available 2211 implementations or their features. Readers are advised to note that 2212 other implementations may exist. 2214 According to RFC 7942 [RFC7942], "this will allow reviewers and 2215 working groups to assign due consideration to documents that have the 2216 benefit of running code, which may serve as evidence of valuable 2217 experimentation and feedback that have made the implemented protocols 2218 more mature. It is up to the individual working groups to use this 2219 information as they see fit". 2221 6.1. Verisign EPP SDK 2223 Organization: Verisign Inc. 2225 Name: Verisign EPP SDK 2227 Description: The Verisign EPP SDK includes both a full client 2228 implementation and a full server stub implementation of draft-ietf- 2229 regext-launchphase. 2231 Level of maturity: Production 2233 Coverage: All aspects of the protocol are implemented. 2235 Licensing: GNU Lesser General Public License 2237 Contact: jgould@verisign.com 2239 URL: http://www.verisigninc.com/en_US/channel-resources/domain- 2240 registry-products/epp-sdks 2242 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS 2244 Organization: Verisign Inc. 2246 Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry 2247 System (SRS) 2249 Description: The Verisign Consolidated Top Level Domain (CTLD) Shared 2250 Registry System (SRS) implements the server-side of draft-ietf- 2251 regext-launchphase for a variety of Top Level Domains (TLD's). 2253 Level of maturity: Production 2255 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2256 Form for the EPP Command, the Sunrise and Claims Forms for 2257 the EPP Command of Launch Registrations and Launch 2258 Applications. For Launch Applications the Poll Messaging, the EPP 2259 Command, the EPP Command, and the EPP 2260 Command is covered. 2262 Licensing: Proprietary 2264 Contact: jgould@verisign.com 2266 6.3. Verisign .COM / .NET SRS 2268 Organization: Verisign Inc. 2270 Name: Verisign .COM / .NET Shared Registry System (SRS) 2272 Description: The Verisign Shared Registry System (SRS) for .COM, .NET 2273 and other IDN TLD's implements the server-side of draft-ietf-regext- 2274 launchphase. 2276 Level of maturity: Operational Test Environment (OTE) 2277 Coverage: The "signed mark" Mark Validation Model, the Claims Check 2278 Form for the EPP Command, the Sunrise and Claims Forms for 2279 the EPP Command of Launch Registrations. 2281 Licensing: Proprietary 2283 Contact: jgould@verisign.com 2285 6.4. REngin v3.7 2287 Organization: Domain Name Services (Pty) Ltd 2289 Name: REngin v3.7 2291 Description: Server side implementation only 2293 Level of maturity: Production 2295 Coverage: All features from version 12 have been implemented 2297 Licensing: Proprietary Licensing with Maintenance Contracts 2299 Contact: info@dnservices.co.za 2301 URL: https://www.registry.net.za and soon http://dnservices.co.za 2303 6.5. RegistryEngine EPP Service 2305 Organization: CentralNic 2307 Name: RegistryEngine EPP Service 2309 Description: Generic high-volume EPP service for gTLDs, ccTLDs and 2310 SLDs 2312 Level of maturity: Deployed in CentralNic's production environment as 2313 well as two other gTLD registry systems, and two ccTLD registry 2314 systems. 2316 Coverage: Majority of elements including TMCH sunrise, landrush and 2317 TM claims as well as sunrise applications validated using codes. 2319 Licensing: Proprietary In-House software 2321 Contact: epp@centralnic.com 2323 URL: https://www.centralnic.com 2325 6.6. Neustar EPP SDK 2327 Organization: Neustar 2329 Name: Neustar EPP SDK 2331 Description: The Neustar EPP SDK includes client implementation of 2332 draft-ietf-regext-launchphase in both Java and C++. 2334 Level of maturity: Production 2336 Coverage: All aspects of the protocol are implemented. 2338 Licensing: GNU Lesser General Public License 2340 Contact: trung.tran@neustar.biz 2342 6.7. gTLD Shared Registry System 2344 Organization: Stichting Internet Domeinnaamregistratie Nederland 2345 (SIDN) 2347 Name: gTLD Shared Registry System 2349 Description: The gTLD SRS implements the server side of the draft- 2350 ietf-regext-launchphase. 2352 Level of maturity: (soon) Production 2354 Coverage: The following parts of the draft are supported: 2356 Signed mark validation model using Digital Signature 2357 (Section 2.6.3) 2358 Claims Check Form (Section 3.1.1) 2359 Sunrise Create Form (Section 3.3.1) 2360 Claims Create Form (Section 3.3.2) 2362 The parts of the document not described here are not implemented. 2364 Licensing: Proprietary 2366 Contact: rik.ribbers@sidn.nl 2368 7. Security Considerations 2370 The mapping extensions described in this document do not provide any 2371 security services beyond those described by EPP [RFC5730], the EPP 2372 domain name mapping [RFC5731], and protocol layers used by EPP. The 2373 security considerations described in these other specifications apply 2374 to this specification as well. 2376 Updates to, and deletion of an application object MUST be restricted 2377 to clients authorized to perform the said operation on the object. 2379 Information contained within an application, or even the mere fact 2380 that an application exists may be confidential. Any attempt to 2381 operate on an application object by an unauthorized client MUST be 2382 rejected with an EPP 2201 (authorization error) return code. Server 2383 policy may allow operation with filtered output by clients 2384 other than the sponsoring client, in which case the 2385 and response SHOULD be filtered to include only 2386 fields that are publicly accessible. 2388 8. Acknowledgements 2390 The authors wish to acknowledge the efforts of the leading 2391 participants of the Community TMCH Model that led to many of the 2392 changes to this document, which include Chris Wright, Jeff Neuman, 2393 Jeff Eckhaus, and Will Shorter. 2395 Special suggestions that have been incorporated into this document 2396 were provided by Harald Alvestrand, Ben Campbell, Spencer Dawkins, 2397 Jothan Frakes, Keith Gaughan, Seth Goldman, Scott Hollenbeck, Michael 2398 Holloway, Jan Jansen, Rubens Kuhl, Mirja Kuhlewind, Warren Kumari, 2399 Ben Levac, Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Alexey 2400 Melnikov, Patrick Mevzek, James Mitchell, Francisco Obispo, Mike 2401 O'Connell, Eric Rescoria, Bernhard Reutner-Fischer, Sabrina Tanamal, 2402 Trung Tran, Ulrich Wisser and Sharon Wodjenski. 2404 Some of the description of the Trademark Claims Phase was based on 2405 the work done by Gustavo Lozano in the ICANN TMCH functional 2406 specifications. 2408 9. References 2410 9.1. Normative References 2412 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2413 Requirement Levels", BCP 14, RFC 2119, 2414 DOI 10.17487/RFC2119, March 1997, . 2417 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2418 DOI 10.17487/RFC3688, January 2004, . 2421 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 2422 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 2423 September 2009, . 2425 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2426 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 2427 . 2429 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2430 Domain Name Mapping", STD 69, RFC 5731, 2431 DOI 10.17487/RFC5731, August 2009, . 2434 [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", 2435 RFC 7848, DOI 10.17487/RFC7848, June 2016, 2436 . 2438 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 2439 Code: The Implementation Status Section", BCP 205, 2440 RFC 7942, DOI 10.17487/RFC7942, July 2016, 2441 . 2443 9.2. Informative References 2445 [I-D.ietf-regext-tmch-func-spec] 2446 Lozano, G., "ICANN TMCH functional specifications", draft- 2447 ietf-regext-tmch-func-spec-03 (work in progress), July 2448 2017. 2450 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 2451 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 2452 February 2015, . 2454 Appendix A. Change History 2456 A.1. Change from 00 to 01 2458 1. Changed to use camel case for the XML elements. 2459 2. Replaced "cancelled" status to "rejected" status. 2460 3. Added the child elements of the element. 2461 4. Removed the XML schema and replaced with "[TBD]". 2463 A.2. Change from 01 to 02 2465 1. Added support for both the ICANN and ARI/Neustar TMCH models. 2466 2. Changed the namespace URI and prefix to use "launch" instead of 2467 "launchphase". 2468 3. Added definition of multiple claim validation models. 2470 4. Added the and 2471 elements. 2472 5. Added support for Claims Info Command 2474 A.3. Change from 02 to 03 2476 1. Removed XSI namespace per Keith Gaughan's suggestion on the 2477 provreg list. 2478 2. Added extensibility to the launch:status element and added the 2479 pendingAuction status per Trung Tran's feedback on the provreg 2480 list. 2481 3. Added support for the Claims Check Command, updated the location 2482 and contents of the signedNotice, and replaced most references of 2483 Claim to Mark based on the work being done on the ARI/Neustar 2484 launch model. 2486 A.4. Change from 03 to 04 2488 1. Removed references to the ICANN model. 2489 2. Removed support for the Claims Info Command. 2490 3. Removed use of the signedClaim. 2491 4. Revised the method for referring to the signedClaim from the XML 2492 Signature using the IDREF URI. 2493 5. Split the launch-1.0.xsd into three XML schemas including launch- 2494 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 2495 6. Split the "claims" launch phase to the "claims1" and "claims2" 2496 launch phases. 2497 7. Added support for the encodedSignedMark with base64 encoded 2498 signedMark. 2499 8. Changed the elements in the createNoticeType to include the 2500 noticeID, timestamp, and the source elements. 2501 9. Added the class and effectiveDate elements to mark. 2503 A.5. Change from 04 to 05 2505 1. Removed reference to in the example. 2506 2. Incorporated feedback from Bernhard Reutner-Fischer on the 2507 provreg mail list. 2508 3. Added missing launch XML prefix to applicationIDType reference in 2509 the idContainerType of the Launch Schema. 2510 4. Added missing description of the element in the 2511 element. 2512 5. Updated note on replication of the EPP contact mapping elements 2513 in the Mark Contact section. 2515 A.6. Change from 05 to 06 2517 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 2518 replaced with reference to draft-lozano-smd, that contains the 2519 definition for the mark, signed marked, and encoded signed mark. 2520 2. Split the into and 2521 based on feedback from Trung Tran. 2522 3. Added the "includeMark" optional attribute to the 2523 element to enable the client to request whether or not to include 2524 the mark in the info response. 2525 4. Fixed state diagram to remove redundant transition from "invalid" 2526 to "rejected"; thanks Klaus Malorny. 2528 A.7. Change from 06 to 07 2530 1. Proof-read grammar and spelling. 2531 2. Changed "pendingAuction" status to "pendingAllocation", changed 2532 "pending" to "pendingValidation" status, per proposal from Trung 2533 Tran and seconded by Rubens Kuhl. 2534 3. Added text related to the use of RFC 5731 pendingCreate to the 2535 Application Identifier section. 2536 4. Added the Poll Messaging section to define the use of poll 2537 messaging for intermediate state transitions and pending action 2538 poll messaging for final state transitions. 2540 A.8. Change from 07 to 08 2542 1. Added support for use of the launch statuses and poll messaging 2543 for Launch Registrations based on feedback from Sharon Wodjenski 2544 and Trung Tran. 2545 2. Incorporated changes based on updates or clarifications in draft- 2546 lozano-tmch-func-spec-01, which include: 2548 1. Removed the unused element. 2549 2. Removed the element. 2550 3. Added the element based on the required 2551 element. 2553 A.9. Change from 08 to 09 2555 1. Made element optional in to allow 2556 passing just the in per request 2557 from Ben Levac. 2558 2. Added optional "type" attribute in to enable the 2559 client to explicitly define the desired type of object 2560 (application or registration) to create to all forms of the 2561 create extension. 2563 3. Added text that the server SHOULD validate the 2564 element in the Launch Phases section. 2565 4. Add the "General Create Form" to the create command extension to 2566 support the request from Ben Levac. 2567 5. Updated the text for the Poll Messaging section based on feedback 2568 from Klaus Malorny. 2569 6. Replaced the "claims1" and "claims2" phases with the "claims" 2570 phase based on discussion on the provreg list. 2571 7. Added support for a mixed create model (Sunrise Create Model and 2572 Claims Create Model), where a trademark (encoded signed mark, 2573 etc.) and notice can be passed, based on a request from James 2574 Mitchell. 2575 8. Added text for the handling of the overlapping "claims" and 2576 "landrush" launch phases. 2577 9. Added support for two check forms (claims check form and 2578 availability check form) based on a request from James Mitchell. 2579 The availability check form was based on the text in draft-rbp- 2580 application-epp-mapping. 2582 A.10. Change from 09 to 10 2584 1. Changed noticeIDType from base64Binary to token to be compatible 2585 with draft-lozano-tmch-func-spec-05. 2586 2. Changed codeType from base64Binary to token to be more generic. 2587 3. Updated based on feedback from Alexander Mayrhofer, which 2588 include: 2590 1. Changed "extension to the domain name extension" to 2591 "extension to the domain name mapping". 2592 2. Changed use of 2004 return code to 2306 return code when 2593 phase passed mismatches active phase and sub-phase. 2594 3. Changed description of "allocated" and "rejected" statuses. 2595 4. Moved sentence on a synchronous command 2596 without the use of an intermediate application, then an 2597 Application Identifier MAY not be needed to the Application 2598 Identifier section. 2599 5. Restructured the Mark Validation Models section to include 2600 the " element" sub-section, the 2601 " element" sub-section, and the Digital Signature 2602 sub-section. 2603 6. Changed "Registries may" to "Registries MAY". 2604 7. Changed "extensed" to "extended" in "Availability Check 2605 Form" section. 2606 8. Broke the mix of create forms in the "EPP Command" 2607 section to a fourth "Mixed Create Form" with its own sub- 2608 section. 2609 9. Removed "displayed or" from "displayed or accepted" in the 2610 description. 2612 10. Replaced "given domain name is supported" with "given domain 2613 name are supported" in the "Create Response" section. 2614 11. Changed the reference of 2303 (object does not exist) in the 2615 "Security Considerations" section to 2201 (authorization 2616 error). 2617 12. Added arrow from "invalid" status to "pendingValidation" 2618 status and "pendingAllocation" status to "rejected" status 2619 in the State Transition Diagram. 2620 4. Added the "C:" and "S:" example prefixes and related text in the 2621 "Conventions Used in This Document" section. 2623 A.11. Change from 10 to 11 2625 1. Moved the claims check response element under 2626 the element instead of the element based on 2627 the request from Francisco Obispo. 2629 A.12. Change from 11 to 12 2631 1. Added support for multiple validator identifiers for claims 2632 notices and marks based on a request and text provided by Mike 2633 O'Connell. 2634 2. Removed domain:exDate element from example in section 3.3.5 based 2635 on a request from Seth Goldman on the provreg list. 2636 3. Added clarifying text for clients not passing the launch 2637 extension on update and delete commands to servers that do not 2638 support launch applications based on a request from Sharon 2639 Wodjenski on the provreg list. 2641 A.13. Change from 12 to EPPEXT 00 2643 1. Changed to eppext working group draft by changing draft-tan-epp- 2644 launchphase to draft-ietf-eppext-launchphase and by changing 2645 references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch- 2646 smd. 2648 A.14. Change EPPEXT 00 to EPPEXT 01 2650 1. Removed text associated with support for the combining of status 2651 values based on feedback from Patrick Mevzek on the provreg 2652 mailing list, discussion on the eppext mailing list, and 2653 discussion at the eppext IETF meeting on March 6, 2014. 2655 A.15. Change EPPEXT 01 to EPPEXT 02 2657 1. Changed the element to be zero or more elements 2658 and the element to be one or more elements in the 2659 Claims Create Form. These changes were needed to be able to 2660 support more than one concurrent claims services. 2662 A.16. Change EPPEXT 02 to EPPEXT 03 2664 1. Added the "Implementation Status" section based on an action item 2665 from the eppext IETF-91 meeting. 2666 2. Moved Section 7 "IANA Considerations" and Section 9 "Security 2667 Considerations" before Section 5 "Acknowledgements". Moved 2668 "Change Log" Section to end. 2669 3. Updated the text for the Claims Check Form and the Claims Create 2670 Form to support checking for the need of the claims notice and 2671 passing the claims notice outside of the "claims" phase. 2672 4. Added the new Trademark Check Form to support determining whether 2673 or not a trademark exists that matches the domain name 2674 independent of whether a claims notice is required on create. 2675 This was based on a request from Trung Tran and a discussion on 2676 the eppext mailing list. 2678 A.17. Change EPPEXT 03 to EPPEXT 04 2680 1. Amended XML Namespace section of IANA Considerations, added EPP 2681 Extension Registry section. 2683 A.18. Change EPPEXT 04 to EPPEXT 05 2685 1. Added a missing comma to the descripton of the 2686 element, based on feedback from Keith Gaughan on the eppext 2687 mailing list. 2688 2. Added the SIDN implementation status information. 2689 3. Fixed a few indentation issues in the samples. 2691 A.19. Change EPPEXT 05 to EPPEXT 06 2693 1. Removed duplicate "TMCH Functional Specification" URIs based on 2694 feedback from Scott Hollenbeck on the eppext mailing list. 2695 2. Changed references of example?.tld to domain?.example to be 2696 consistent with RFC 6761 based on feedback from Scott Hollenbeck 2697 on the eppext mailing list. 2698 3. A template was added to section 5 to register the XML schema in 2699 addition to the namespace based on feedback from Scott Hollenbeck 2700 on the eppext mailing list. 2702 A.20. Change EPPEXT 06 to EPPEXT 07 2704 1. Changed reference of lozano-tmch-func-spec to ietf-eppext-tmch- 2705 func-spec. 2707 A.21. Change from EPPEXT 07 to REGEXT 00 2709 1. Changed to regext working group draft by changing draft-ietf- 2710 eppext-launchphase to draft-ietf-regext-launchphase and by 2711 changing references of draft-ietf-eppext-tmch-func-spec to draft- 2712 ietf-regext-tmch-func-spec. 2714 A.22. Change from REGEXT 00 to REGEXT 01 2716 1. Fixed reference of Claims Check Command to Trademark Check 2717 Command in the Trademark Check Form section. 2718 2. Replaced reference of draft-ietf-eppext-tmch-smd to RFC 7848. 2720 A.23. Change from REGEXT 01 to REGEXT 02 2722 1. Removed the reference to ietf-regext-tmch-func-spec and briefly 2723 described the trademark claims phase that is relavent to draft- 2724 ietf-regext-launchphase. 2726 A.24. Change from REGEXT 02 to REGEXT 03 2728 1. Ping update. 2730 A.25. Change from REGEXT 03 to REGEXT 04 2732 1. Updates based on feedback from Scott Hollenbeck that include: 2734 1. Nit on reference to RFC 7848 in section 1. 2735 2. Added reference to for the request to create 2736 a Launch Application in section 2.1. 2737 3. Removed the second paragraph of section 2.1 describing the 2738 option of creating an application identifier for a Launch 2739 Registration. 2740 4. Provided clarification in section 2.2 on the responsibility 2741 of the server to ensure that the supported validator 2742 identifiers are unique. 2743 5. Updated the text in section 2.5 referencing the domain name 2744 object in RFC 5731. 2745 6. Updated the copyright to 2017 in section 4.1. 2747 A.26. Change from REGEXT 04 to REGEXT 05 2749 1. Updates based on feedback from Ulrich Wisser that include: 2751 1. Updated reference to obsoleted RFC 6982 with RFC 7942. 2752 2. Moved RFC 7451 reference from normative to informative. 2754 A.27. Change from REGEXT 05 to REGEXT 06 2756 1. Updates based on feedback from Adam Roach that include: 2758 1. Added an informative reference to draft-ietf-regext-tmch- 2759 func-spec in section 2.3.1 "Trademark Claims Phase". 2760 2. Added formal definition of a Launch Registration and Launch 2761 Application to section 1.1. 2762 3. Updated the description of the Validator Identifier to 2763 indicate that the uniqueness is based on server policy. 2764 4. Updated "Does Domain have Claims?" "No" and "Yes" branch 2765 labels in Figure 1. 2766 5. Updated the description of the element in the 2767 commands to explicitly specify the return of a 2306 EPP 2768 error result when invalid or referring to section 2.3 for 2769 validation. 2770 6. Fixed indentation of the and 2771 elements in the section 2.5 examples. 2772 7. Updated the description of the element in the 2773 info response. 2774 8. Added returning an EPP error result code of 2306 if the 2775 "type" attribute is incorrect in section 3.3.1, 3.3.2, and 2776 3.3.3. 2777 9. Made small change in the description of the Create Response 2778 in section 3.3.5. 2779 10. Updated the Registrant Contact in section 7 to the IESG. 2781 A.28. Change from REGEXT 06 to REGEXT 07 2783 1. Updates based on feedback from Mirja Kuhlewind that include: 2785 1. In the Security Considerations section, change must to MUST 2786 in "Updates to, and deletion of an application object MUST be 2787 restricted to clients authorized to perform the said 2788 operation on the object". 2789 2. Updates based on feedback from Warren Kumari that include: 2791 1. Removed the comma from "The Validator Identifier is the 2792 identifier, that is unique..." not needed due to change from 2793 Harald Alvestrand's feedback. 2794 3. Updates based on feedback from Alexey Melnikov that include: 2796 1. Added a Normative Reference to RFC 5646 for the "language" 2797 attribute. 2798 2. Replace identifer with identifier". 2799 3. Remove "for" in "Enumeration of for launch phase values" 2800 4. Updates based on feedback from Harald Alvestrand that include: 2802 1. Removed the references to the unused "launch-1.0", 2803 "signedMark-1.0", and "mark-1.0" abbreviations and revised 2804 the XML namespace prefix definitions for "launch", "smd", and 2805 "mark". 2806 2. Replace "that is unique to the server" to "unique to the 2807 server" in the Validator Identifier section. 2808 3. Replaced ", including the "allocated" and "rejected" 2809 statuses" with "("allocated" and "rejected")" in the Status 2810 Values section. 2811 4. Replaced "Is a possible end state" with "This is a possible 2812 end state" in the definition of the "allocated" and 2813 "rejected" statuses in the Status Values section. 2814 5. Add the preamble "The transitions between the states is a 2815 matter of server policy. This diagram defines one possible 2816 set of permitted transitions." to the State Transition 2817 diagram. 2818 6. Split the first sentence of the Poll Messaging section into 2819 two sentences, one for the Launch Application and one for the 2820 Launch Registration. 2821 7. Remove "either" and replace "or" with an "and" in the first 2822 sentence of the Digital Signature section for clarity and to 2823 be more consistent with the description of the "signed mark" 2824 validation model. 2825 5. Updates based on feedback from Ben Campbell that include: 2827 1. Replacement of "that" with "which" in the first sentence of 2828 the Validator Identifier section not needed due change from 2829 Harald Alvestrand's feedback. 2830 2. Avoid using RFC 2119 in the Launch Phases definitions, which 2831 resulted in change MAY to may in the definition of the 2832 "open" phase and MUST to must in the definition of the 2833 "claims" phase. 2834 3. Change "SHOULD" to "should" in the sentence "For example, 2835 the element SHOULD be claims". 2837 4. Change "MUST" to "must" in the sentence "The Trademark 2838 Claims Phase is when a Claims Notice MUST be displayed to a 2839 prospective registrant of a domain name that matches 2840 trademarks". 2841 5. Change "MAY" to "may" in the sentence "Claim Notice 2842 Information Service (CNIS), which MAY be directly linked to 2843 a Trademark Validator.", where MAY can be lowercase may". 2844 6. Remove "that" from the sentence "The 2845 element that is used by the "code", "mark", and "code with 2846 mark" validation models, has the following child elements". 2847 7. Added the consistent use of colons ":" at the end of the 2848 hangText labels to address adding whitespace between handing 2849 indent list entries. 2851 8. Revised the first sentence, of the second paragraph, of the 2852 "EPP Command" section, to read "An EPP 2853 command with the extension sent to a server that does not 2854 support launch applications will fail.". 2855 9. Revised the "The server SHOULD NOT use the "custom" status 2856 value" to "The server SHOULD use one of the non-"custom" 2857 status values" in the Status Values section. 2858 10. Revised "Both the Validator Identifier and the Issuer 2859 Identifier used MUST be unique" to "Both the Validator 2860 Identifier and the Issuer Identifier used MUST be unique in 2861 the server" in the Validator Identifier section. 2862 11. Revised "The Validator Identifier MAY define a non-Trademark 2863 Validator that supports a form of claims" to "The Validator 2864 Identifier may define a non-Trademark Validator that 2865 supports a form of claims, where claims and a Validator 2866 Identifier can be used for purposes beyond trademarks" in 2867 the Validator Identifier section. 2868 6. Updates based on feedback from Eric Rescoria that include: 2870 1. Replaced the duplicate Claims Check Form and Claims Create 2871 Form in the list of the two ways the document supports the 2872 Trademark Claims Phase, to refer to the section by number 2873 instead of by name. 2874 2. Added "The use of "..." is used as shorthand for elements 2875 defined outside this document" added to the "In examples,..." 2876 paragraph of the Conventions Used in This Document section. 2877 3. Added "When using digital signatures the server MUST validate 2878 the digital signature" to the Digital Signature section. 2879 4. Removed "post-launch" to the description of the "open" phase 2880 in the Launch Phases section. 2881 5. Add the sentences "Multiple launch phases and multiple models 2882 are supported to enable the launch of a domain name registry. 2883 What is supported and what is validated is up to server 2884 policy. Communication of the server policy is typically 2885 performed using an out-of-band mechanism that is not 2886 specified in this document." to the second paragraph of the 2887 Introduction section. 2888 7. Updates based on feedback from Spencer Dawkins that include: 2890 1. Replace "during their initial launch" with "as they begin 2891 operation" in the Introduction section. 2892 8. Updates based on feedback from Sabrina Tanamal that include: 2894 1. Pretty print the XML schema to address inconsistent 2895 indenting. 2897 Authors' Addresses 2899 James Gould 2900 VeriSign, Inc. 2901 12061 Bluemont Way 2902 Reston, VA 20190 2903 US 2905 Email: jgould@verisign.com 2906 URI: http://www.verisigninc.com 2908 Wil Tan 2909 Cloud Registry 2910 Suite 32 Seabridge House 2911 377 Kent St 2912 Sydney, NSW 2000 2913 AU 2915 Phone: +61 414 710899 2916 Email: wil@cloudregistry.net 2917 URI: http://www.cloudregistry.net 2919 Gavin Brown 2920 CentralNic Ltd 2921 35-39 Mooregate 2922 London, England EC2R 6AR 2923 GB 2925 Phone: +44 20 33 88 0600 2926 Email: gavin.brown@centralnic.com 2927 URI: https://www.centralnic.com