idnits 2.17.1 draft-ietf-eppext-launchphase-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 25, 2014) is 3493 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 2131 -- Looks like a reference, but probably isn't: '2' on line 2133 == Outdated reference: A later version (-06) exists of draft-ietf-eppext-tmch-smd-00 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Gould 3 Internet-Draft VeriSign, Inc. 4 Intended status: Standards Track W. Tan 5 Expires: March 29, 2015 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 September 25, 2014 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-ietf-eppext-launchphase-02 13 Abstract 15 This document describes an Extensible Provisioning Protocol (EPP) 16 extension mapping for the provisioning and management of domain name 17 registrations and applications during the launch of a domain name 18 registry. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on March 29, 2015. 37 Copyright Notice 39 Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . 4 57 2.1. Application Identifier . . . . . . . . . . . . . . . . . 4 58 2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5 59 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 5 60 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 6 61 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 7 62 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 8 63 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 11 64 2.6.1. element . . . . . . . . . . . . . . 12 65 2.6.2. element . . . . . . . . . . . . . . . . . 13 66 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 13 67 2.6.3.1. element . . . . . . . . . . . . 13 68 2.6.3.2. element . . . . . . . . . 13 69 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 13 70 3.1. EPP Command . . . . . . . . . . . . . . . . . . . 14 71 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 14 72 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 17 73 3.2. EPP Command . . . . . . . . . . . . . . . . . . . 19 74 3.3. EPP Command . . . . . . . . . . . . . . . . . . 22 75 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 22 76 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 28 77 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 31 78 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 32 79 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 34 80 3.4. EPP Command . . . . . . . . . . . . . . . . . . 35 81 3.5. EPP Command . . . . . . . . . . . . . . . . . . 36 82 3.6. EPP Command . . . . . . . . . . . . . . . . . . . 37 83 3.7. EPP Command . . . . . . . . . . . . . . . . . 38 84 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 38 85 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 38 86 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 45 87 6. Change History . . . . . . . . . . . . . . . . . . . . . . . 46 88 6.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 46 89 6.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 46 90 6.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 46 91 6.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 46 92 6.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 47 93 6.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 47 94 6.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 47 95 6.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 47 96 6.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 48 97 6.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 48 98 6.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 49 99 6.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 49 100 6.13. Change from 12 to WG 00 . . . . . . . . . . . . . . . . . 49 101 6.14. Change WG 00 to WG 01 . . . . . . . . . . . . . . . . . . 50 102 6.15. Change WG 01 to WG 02 . . . . . . . . . . . . . . . . . . 50 103 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 104 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 105 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 51 106 9.1. Normative References . . . . . . . . . . . . . . . . . . 51 107 9.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 51 108 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51 110 1. Introduction 112 This document describes an extension mapping for version 1.0 of the 113 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 114 specifies a flexible schema that can be used to implement several 115 common use cases related to the provisioning and management of domain 116 name registrations and applications during the launch of a domain 117 name registry. 119 It is typical for domain registries to operate in special modes 120 during their initial launch to facilitate allocation of domain names, 121 often according to special rules. This document uses the term 122 "launch phase" and the shorter form "launch" to refer to such a 123 period. 125 The EPP domain name mapping [RFC5731] is designed for the steady- 126 state operation of a registry. During a launch period, the model in 127 place may be different from what is defined in the EPP domain name 128 mapping [RFC5731]. For example, registries often accept multiple 129 applications for the same domain name during the "Sunrise" launch 130 phase, referred to as a Launch Application. A Launch Registration 131 refers to a registration made during a launch phase when the server 132 uses a "first-come, first-served" model. Even in a "first-come, 133 first-served" model, additional steps and information might be 134 required, such as trademark information. In addition, the 135 [I-D.ietf-eppext-tmch-smd] defines a registry interface for the 136 Trademark Claims or "claims" launch phase that includes support for 137 presenting a Trademark Claims Notice to the Registrant. This 138 document proposes an extension to the domain name mapping in order to 139 provide a uniform interface for the management of Launch Applications 140 and Launch Registrations in launch phases. 142 1.1. Conventions Used in This Document 144 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 145 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 146 document are to be interpreted as described in RFC 2119 [RFC2119]. 148 XML is case sensitive. Unless stated otherwise, XML specifications 149 and examples provided in this document MUST be interpreted in the 150 character case presented in order to develop a conforming 151 implementation. 153 In examples, "C:" represents lines sent by a protocol client and "S:" 154 represents lines returned by a protocol server. Indentation and 155 white space in examples are provided only to illustrate element 156 relationships and are not a REQUIRED feature of this protocol. 158 "launch-1.0" is used as an abbreviation for 159 "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix 160 "launch" is used, but implementations MUST NOT depend on it and 161 instead employ a proper namespace-aware XML parser and serializer to 162 interpret and output the XML documents. 164 "signedMark-1.0" is used as an abbreviation for 165 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in 166 [I-D.ietf-eppext-tmch-smd]. The XML namespace prefix "smd" is used, 167 but implementations MUST NOT depend on it and instead employ a proper 168 namespace-aware XML parser and serializer to interpret and output the 169 XML documents. 171 "mark-1.0" is used as an abbreviation for 172 "urn:ietf:params:xml:ns:mark-1.0" that is defined in 173 [I-D.ietf-eppext-tmch-smd]. The XML namespace prefix "mark" is used, 174 but implementations MUST NOT depend on it and instead employ a proper 175 namespace-aware XML parser and serializer to interpret and output the 176 XML documents. 178 2. Object Attributes 180 This extension adds additional elements to the EPP domain name 181 mapping [RFC5731]. Only those new elements are described here. 183 2.1. Application Identifier 185 Servers MAY allow multiple applications, referred to as a Launch 186 Application, of the same domain name during its launch phase 187 operations. Upon receiving a valid request to create a Launch 188 Application, the server MUST create an application object 189 corresponding to the request, assign an application identifier for 190 the Launch Application, set the [RFC5731] pendingCreate status, and 191 return the application identifier to the client with the 192 element. In order to facilitate correlation, 193 all subsequent launch operations on the Launch Application MUST be 194 qualified by the previously assigned application identifier using the 195 element. 197 If the command processes a request synchronously 198 without the use of an intermediate Launch Application, then an 199 application identifier MAY not be needed. 201 2.2. Validator Identifier 203 The Validator Identifier is the unique identifier for a Trademark 204 Validator that validates marks and has a repository of validated 205 marks. The OPTIONAL "validatorID" attribute is used to define the 206 Validator Identifier of the Trademark Validator. Registries MAY 207 support more than one Third Party Trademark Validator. The Internet 208 Corporation for Assigned Names and Numbers (ICANN) Trademark 209 Clearinghouse (TMCH) is the default Trademark Validator and is 210 reserved the Validator Identifier of "tmch". If the ICANN TMCH is 211 not used or multiple Trademark Validators are used, the Validator 212 Identifier MUST be defined using the "validatorID" attribute. 214 The Validator Identifier MAY be related to one or more issuer 215 identifiers of the element and the element defined 216 in [I-D.ietf-eppext-tmch-smd]. Both the Validator Identifier and the 217 Issuer Identifier used MUST be unique. The list of validator 218 identifiers and the relationship to issuer identifiers is out of 219 scope for this document. 221 The Validator Identifier MAY define a non-Trademark Validator that 222 supports a form of claims. 224 2.3. Launch Phases 226 The server MAY support multiple launch phases sequentially or 227 simultaneously. The element MUST be included by the 228 client to define the target launch phase of the command. The server 229 SHOULD validate the phase and MAY validate the sub-phase of the 230 element against the active phase and OPTIONAL sub- 231 phase of the server on a create command, and return an EPP error 232 result code of 2306 if there is a mismatch. 234 The following launch phase values are defined: 236 sunrise The phase during which trademark holders can submit 237 registrations or applications with trademark information that can 238 be validated by the server. 239 landrush A post-Sunrise phase when non-trademark holders are allowed 240 to register domain names with steps taken to address a large 241 volume of initial registrations. 242 claims The Trademark Claims phase, as defined in the TMCH Functional 243 Specification [1], in which a Claims Notice must be displayed to a 244 prospective registrant of a domain name that matches trademarks. 245 open A post-launch phase that is also referred to as "steady state". 246 Servers MAY require additional trademark protection during this 247 phase. 248 custom A custom server launch phase that is defined using the "name" 249 attribute. 251 For extensibility, the element includes an OPTIONAL 252 "name" attribute that can define a sub-phase or the full name of the 253 phase when the element has the "custom" value. For 254 example, the "claims" launch phase could have two sub-phases that 255 include "landrush" and "open". 257 Launch phases MAY overlap to support the "claims" launch phase, 258 defined in the TMCH Functional Specification [2], and to support a 259 traditional "landrush" launch phase. The overlap of the "claims" and 260 "landrush" launch phases SHOULD be handled by setting "claims" as the 261 value and setting "landrush" as the sub-phase with the 262 "name" attribute. For example, the element SHOULD be 263 claims. 265 2.4. Status Values 267 A Launch Application or Launch Registration object MAY have a launch 268 status value. The element is used to convey the 269 launch status pertaining to the object, beyond what is specified in 270 the object mapping. A Launch Application or Launch Registration MUST 271 set the [RFC5731] "pendingCreate" status if a launch status is 272 supported and the launch status is not one of the final statuses, 273 including the "allocated" and "rejected" statuses. 275 The following status values are defined using the required "s" 276 attribute: 278 pendingValidation: The initial state of a newly-created application 279 or registration object. The application or registration requires 280 validation, but the validation process has not yet completed. 281 validated: The application or registration meets relevant registry 282 rules. 284 invalid: The application or registration does not validate according 285 to registry rules. Server policies permitting, it may transition 286 back into "pendingValidation" for revalidation, after 287 modifications are made to ostensibly correct attributes that 288 caused the validation failure. 289 pendingAllocation: The allocation of the application or registration 290 is pending based on the results of some out-of-band process (for 291 example, an auction). 292 allocated: The object corresponding to the application or 293 registration has been provisioned. Is a possible end state of an 294 application or registration object. 295 rejected: The application or registration object was not 296 provisioned. Is a possible end state of an application or 297 registration object. 298 custom: A custom status that is defined using the "name" attribute. 300 Each status value MAY be accompanied by a string of human-readable 301 text that describes the rationale for the status applied to the 302 object. The OPTIONAL "lang" attribute MAY be present to identify the 303 language if the negotiated value is something other than the default 304 value of "en" (English). 306 For extensibility the element includes an OPTIONAL 307 "name" attribute that can define a sub-status or the full name of the 308 status when the status value is "custom". The server SHOULD NOT use 309 the "custom" status value. 311 Status values MAY be skipped. For example, an application or 312 registration MAY immediately start at the "allocated" status or an 313 application or registration MAY skip the "pendingAllocation" status. 314 If the launch phase does not require validation of a request, an 315 application or registration MAY immediately skip to 316 "pendingAllocation". 318 2.4.1. State Transition 319 | request 320 | 321 | +--------------------------+ 322 | | | 323 v v | 324 +-------------------+ | 325 | | | 326 | pendingValidation +--------------+ | 327 | | | | 328 +---------+---------+ | | 329 | | | 330 | | | 331 v v | 332 +-----------+ +---------+ | 333 | | | | | 334 | validated | | invalid +--+ 335 | | | | 336 +-----+-----+ +----+----+ 337 | | 338 | | 339 v | 340 +-------------------+ | 341 | | | 342 | pendingAllocation +-----------+ | 343 | | | | 344 +---------+---------+ | | 345 | | | 346 | | | 347 | | | 348 | | | 349 | | | 350 v v v 351 +---------+ +--------+ 352 / \ / \ 353 | allocated | | rejected | 354 \ / \ / 355 +---------+ +--------+ 357 Figure 1 359 2.5. Poll Messaging 361 A Launch Application MUST and a Launch Registration MAY be handled as 362 a domain name of [RFC5731] in "pendingCreate" status, with the launch 363 status values defined in Section 2.4. As a Launch Application or 364 Launch Registration transitions between the status values defined in 365 Section 2.4, the server SHOULD insert poll messages, per [RFC5730], 366 for the applicable intermediate statuses, including the 367 "pendingValidation", "validated", "pendingAllocation, and "invalid" 368 statuses, using the element with the 369 extension. The element MAY contain 370 non-mandatory information, like contact and name server information. 371 Also, further extensions that would normally be included in the 372 response of a command, per [RFC5731], MAY be included. 373 For the final statuses, including the "allocated" and "rejected" 374 statuses, the server MUST insert a poll message, per 375 [RFC5731], with the extension. 377 The following is an example poll message for a Launch Application 378 that has transitioned to the "pendingAllocation" state. 380 S: 381 S: 382 S: 383 S: 384 S: Command completed successfully; ack to dequeue 385 S: 386 S: 387 S: 2013-04-04T22:01:00.0Z 388 S: Application pendingAllocation. 389 S: 390 S: 391 S: 393 S: example.tld 394 S: ... 395 S: 396 S: 397 S: 398 S: 400 S: sunrise 401 S: abc123 402 S: 403 S: 404 S: 405 S: 406 S: ABC-12345 407 S: 54322-XYZ 408 S: 409 S: 410 S: 411 The following is an example poll message for an 412 "allocated" Launch Application. 414 S: 415 S: 416 S: 417 S: 418 S: Command completed successfully; ack to dequeue 419 S: 420 S: 421 S: 2013-04-04T22:01:00.0Z 422 S: Application successfully allocated. 423 S: 424 S: 425 S: 427 S: example.tld 428 S: 429 S: ABC-12345 430 S: 54321-XYZ 431 S: 432 S: 2013-04-04T22:00:00.0Z 433 S: 434 S: 435 S: 436 S: 438 S: sunrise 439 S: abc123 440 S: 441 S: 442 S: 443 S: 444 S: BCD-23456 445 S: 65432-WXY 446 S: 447 S: 448 S: 449 The following is an example poll message for an 450 "allocated" Launch Registration. 452 S: 453 S: 454 S: 455 S: 456 S: Command completed successfully; ack to dequeue 457 S: 458 S: 459 S: 2013-04-04T22:01:00.0Z 460 S: Registration successfully allocated. 461 S: 462 S: 463 S: 465 S: example.tld 466 S: 467 S: ABC-12345 468 S: 54321-XYZ 469 S: 470 S: 2013-04-04T22:00:00.0Z 471 S: 472 S: 473 S: 474 S: 476 S: sunrise 477 S: 478 S: 479 S: 480 S: 481 S: BCD-23456 482 S: 65432-WXY 483 S: 484 S: 485 S: 487 2.6. Mark Validation Models 489 A server MUST support at least one of the following models for 490 validating trademark information: 492 code Use of a mark code by itself to validate that the mark matches 493 the domain name. This model is supported using the 494 element with just the element. 495 mark The mark information is passed without any other validation 496 element. The server will use some custom form of validation to 497 validate that the mark information is authentic. This model is 498 supported using the element with just the 499 (Section 2.6.2) element. 500 code with mark: A code is used along with the mark information by 501 the server to validate the mark utilizing an external party. The 502 code represents some form of secret that matches the mark 503 information passed. This model is supported using the 504 element that contains both the and 505 the (Section 2.6.2) elements. 506 signed mark: The mark information is digitally signed as described 507 in the Digital Signature (Section 2.6.3) section. The digital 508 signature can be directly validated by the server using the public 509 key of the external party that created the signed mark using its 510 private key. This model is supported using the 511 (Section 2.6.3.1) and (Section 2.6.3.2) 512 elements. 514 More than one , (Section 2.6.3.1), 515 or (Section 2.6.3.2) element MAY be 516 specified. The maximum number of marks per domain name is up to 517 server policy. 519 2.6.1. element 521 The element that is used by the "code", "mark", and 522 "code with mark" validation models, has the following child elements: 524 : OPTIONAL mark code used to validate the 525 (Section 2.6.2) information. The mark code is be a mark-specific 526 secret that the server can verify against a third party. The 527 OPTIONAL "validatorID" attribute is the Validator Identifier 528 (Section 2.2) whose value indicates which Trademark Validator that 529 the code originated from, with no default value. 530 : OPTIONAL mark information with child elements defined 531 in the Mark (Section 2.6.2) section. 533 The following is an example element with both a 534 and (Section 2.6.2) element. 536 537 538 49FD46E6C4B45C55D4AC 539 540 ... 541 542 544 2.6.2. element 546 A element describes an applicant's prior right to a given 547 domain name that is used with the "mark", "mark with code", and the 548 "signed mark" validation models. The element is defined 549 in [I-D.ietf-eppext-tmch-smd]. A new mark format can be supported by 550 creating a new XML schema for the mark that has an element that 551 substitutes for the element from 552 [I-D.ietf-eppext-tmch-smd]. 554 2.6.3. Digital Signature 556 Digital signatures MAY be used by the server to validate either the 557 mark information, when using the "signed mark" validation model with 558 the (Section 2.6.3.1) element or the 559 (Section 2.6.3.2) element. 561 2.6.3.1. element 563 The element contains the digitally signed mark 564 information. The element is defined in 565 [I-D.ietf-eppext-tmch-smd]. A new signed mark format can be 566 supported by creating a new XML schema for the signed mark that has 567 an element that substitutes for the element 568 from [I-D.ietf-eppext-tmch-smd]. 570 2.6.3.2. element 572 The element contains an encoded form of the 573 digitally signed (Section 2.6.3.1) element. The 574 element is defined in 575 [I-D.ietf-eppext-tmch-smd]. A new encoded signed mark format can be 576 supported by creating a new XML schema for the encoded signed mark 577 that has an element that substitutes for the 578 element from [I-D.ietf-eppext-tmch-smd]. 580 3. EPP Command Mapping 582 A detailed description of the EPP syntax and semantics can be found 583 in the EPP core protocol specification [RFC5730]. The command 584 mappings described here are specifically for use in the Launch Phase 585 Extension. 587 This mapping is designed to be flexible, requiring only a minimum set 588 of required elements. 590 While it is meant to serve several use cases, it does not prescribe 591 any interpretation by the client or server. Such processing is 592 typically highly policy-dependent and therefore specific to 593 implementations. 595 Operations on application objects are done via one or more of the 596 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 597 Registries MAY choose to support a subset of the operations. 599 3.1. EPP Command 601 There are two forms of the extension to the EPP command: the 602 Claims Check Form (Section 3.1.1) and the Availability Check Form 603 (Section 3.1.2). The element "type" attribute defines 604 the form, with the value of "claims" for the Claims Check Form 605 (Section 3.1.1) and with the value of "avail" for the Availability 606 Check Form (Section 3.1.2). The default value of the "type" 607 attribute is "claims". The forms supported by the server is 608 determined by server policy. The server MUST return an EPP error 609 result code of 2307 if it receives a check form that is not 610 supported. 612 3.1.1. Claims Check Form 614 The Claims Check Form defines a new command called the Claims Check 615 Command that is used to determine whether or not there are any 616 matching trademarks, in the specified launch phase, for each domain 617 name passed in the command. The availability check information 618 defined in the EPP domain name mapping [RFC5731] MUST NOT be returned 619 for the Claims Check Command. This form is the default form and MAY 620 be explicitly identified by setting the "type" 621 attribute to "claims". 623 Instead of returning whether the domain name is available, the Claims 624 Check Command will return whether or not at least one matching 625 trademark exists for the domain name. If there is at least one 626 matching trademark that exists for the domain name, a 627 element is returned. The client MAY then use the 628 value of the element to obtain information needed 629 to generate the Trademark Claims Notice from Trademark Validator 630 based on the Validator Identifier (Section 2.2). The unique notice 631 identifier of the Trademark Claims Notice MUST be passed in the 632 element of the extension to the Create Command 633 (Section 3.3). 635 The elements in the EPP command of EPP domain 636 name mapping [RFC5731] define the domain names to check for matching 637 trademarks. The element contains the following child 638 elements: 640 The launch phase that SHOULD be "claims". 642 Example Claims Check command using the domain command and the 643 extension with the "type" explicitly set to "claims", 644 to determine if "example1.tld" and "example2.tld" have any matching 645 trademarks during the "claims" launch phase: 647 C: 648 C: 649 C: 650 C: 651 C: 653 C: example1.tld 654 C: example2.tld 655 C: 656 C: 657 C: 658 C: 661 C: claims 662 C: 663 C: 664 C: ABC-12345 665 C: 666 C: 668 If the command has been processed successfully, the EPP 669 MUST contain an element that 670 identifies the launch namespace. The element 671 contains the following child elements: 673 The launch phase that SHOULD be "claims". 674 One or more elements that contain the 675 following child elements: 677 Contains the fully qualified name of the queried 678 domain name. This element MUST contain an "exists" attribute 679 whose value indicates if a matching trademark exists for the 680 domain name. A value of "1" (or "true") means that a 681 matching trademark does exist for the claims launch phase. A 682 value of "0" (or "false") means that a matching trademark 683 does not exist. 684 Zero or more OPTIONAL claim keys that MAY be 685 passed to a third-party trademark validator such as the 686 Trademark Clearinghouse (TMCH) for querying the information 687 needed to generate a Trademark Claims Notice. The 688 is used as the key for the query in place 689 of the domain name to securely query the service without 690 using a well-known value like a domain name. The OPTIONAL 691 "validatorID" attribute is the Validator Identifier 692 (Section 2.2) whose value indicates which Trademark Validator 693 to query for the Claims Notice information, with the default 694 being the ICANN TMCH. The "validatorID" attribute MAY 695 reference a non-trademark claims clearinghouse identifer to 696 support other forms of claims notices. 698 Example Claims Check response when no matching trademarks are found 699 for the domain name example1.tld, matching trademarks are found for 700 the domain name example2.tld in the "tmch", matching trademarks are 701 found for domain name example3.tld in the "tmch" and "custom-tmch", 702 for the "claims" launch phase: 704 S: 705 S: 706 S: 707 S: 708 S: Command completed successfully 709 S: 710 S: 711 S: 713 S: claims 714 S: 715 S: example1.tld 716 S: 717 S: 718 S: example2.tld 719 S: 720 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 721 S: 722 S: 723 S: 724 S: example3.tld 725 S: 726 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 727 S: 728 S: 729 S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 730 S: 731 S: 732 S: 733 S: 734 S: 735 S: ABC-12345 736 S: 54321-XYZ 737 S: 738 S: 739 S: 741 3.1.2. Availability Check Form 743 The Availability Check Form defines additional elements to extend the 744 EPP command described in the EPP domain name mapping 745 [RFC5731]. No additional elements are defined for the EPP 746 response. This form MUST be identified by setting the 747 "type" attribute to "avail". 749 The EPP command is used to determine if an object can be 750 provisioned within a repository. Domain names may be made available 751 only in unique launch phases, whilst remaining unavailable for 752 concurrent launch phases. In addition to the elements expressed in 753 the , the command is extended with the 754 element that contains the following child elements: 756 The launch phase to which domain name availability 757 should be determined. 759 Example Availability Check Form command using the domain 760 command and the extension with the "type" set to 761 "avail", to determine the availability of two domain names in the 762 "idn-release" custom launch phase: 764 C: 765 C: 766 C: 767 C: 768 C: 770 C: example1.tld 771 C: example2.tld 772 C: 773 C: 774 C: 775 C: 778 C: custom 779 C: 780 C: 781 C: ABC-12345 782 C: 783 C: 785 The Availability Check Form does not define any extension to the 786 response of an domain command. After processing the command, 787 the server replies with a standard EPP response as defined in the EPP 788 domain name mapping [RFC5731]. 790 3.2. EPP Command 792 This extension defines additional elements to extend the EPP 793 command and response to be used in conjunction with the EPP domain 794 name mapping [RFC5731]. 796 The EPP command is used to retrieve information for a launch 797 phase registration or application. The Application Identifier 798 (Section 2.1) returned in the element of the create 799 response (Section 3.3) is used for retrieving information for a 800 Launch Application. A element is sent along with the 801 regular domain command. The element includes an 802 OPTIONAL "includeMark" boolean attribute, with a default value of 803 "false", to indicate whether or not to include the mark in the 804 response. The element contains the following child 805 elements: 807 The phase during which the application or 808 registration was submitted or is associated with. Server policy 809 defines the phases that are supported. 810 OPTIONAL application identifier of the Launch 811 Application. 813 Example domain command with the extension to 814 retrieve information for the sunrise application for example.tld and 815 application identifier "abc123": 817 C: 818 C: 819 C: 820 C: 821 C: 823 C: example.tld 824 C: 825 C: 826 C: 827 C: 830 C: sunrise 831 C: abc123 832 C: 833 C: 834 C: ABC-12345 835 C: 836 C: 837 Example domain command with the extension to 838 retrieve information for the sunrise registration for example.tld: 840 C: 841 C: 842 C: 843 C: 844 C: 846 C: example.tld 847 C: 848 C: 849 C: 850 C: 852 C: sunrise 853 C: 854 C: 855 C: ABC-12345 856 C: 857 C: 859 If the query was successful, the server replies with a 860 element along with the regular EPP . The 861 contains the following child elements: 863 The phase during which the application was submitted, 864 or is associated with, that matches the associated command 865 . 866 OPTIONAL Application Identifier of the Launch 867 Application. 868 OPTIONAL status of the Launch Application using one 869 of the supported status values (Section 2.4). 870 Zero or more (Section 2.6.2) elements. 872 Example domain response using the extension 873 with the mark information: 875 S: 876 S: 877 S: 878 S: 879 S: Command completed successfully 880 S: 881 S: 882 S: 884 S: example.tld 885 S: EXAMPLE1-REP 886 S: 887 S: jd1234 888 S: sh8013 889 S: sh8013 890 S: ClientX 891 S: ClientY 892 S: 2012-04-03T22:00:00.0Z 893 S: 894 S: 2fooBAR 895 S: 896 S: 897 S: 898 S: 899 S: 901 S: sunrise 902 S: abc123 903 S: 904 S: 906 S: ... 907 S: 908 S: 909 S: 910 S: 911 S: ABC-12345 912 S: 54321-XYZ 913 S: 914 S: 915 S: 917 3.3. EPP Command 919 There are four forms of the extension to the EPP command 920 that include the Sunrise Create Form (Section 3.3.1), the Claims 921 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 922 and the Mixed Create Form (Section 3.3.4). The form is dependent on 923 the supported launch phases (Section 2.3) as defined below. 925 sunrise The EPP command with the "sunrise" launch phase is 926 used to submit a registration with trademark information that can 927 be verified by the server with the value. The 928 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 929 launch phase. 930 landrush The EPP command with the "landrush" launch phase 931 MAY use the General Create Form (Section 3.3.3) to explicitly 932 specify the phase and optionally define the expected type of 933 object to create. 934 claims The EPP command with the "claims" launch phase is 935 used to pass the information associated with the presentation and 936 acceptance of the Claims Notice. The Claims Create Form 937 (Section 3.3.2) is used and the General Create Form 938 (Section 3.3.3) MAY be used for the "claims" launch phase. 939 open The EPP command with the "open" launch phase is 940 undefined but the form supported is up to server policy. 941 custom The EPP command with the "custom" launch phase is 942 undefined but the form supported is up to server policy. 944 3.3.1. Sunrise Create Form 946 The Sunrise Create Form of the extension to the EPP domain name 947 mapping [RFC5731] includes the verifiable trademark information that 948 the server uses to match against the domain name to authorize the 949 domain create. A server MUST support one of four models in Claim 950 Validation Models (Section 2.6) to verify the trademark information 951 passed by the client. 953 A element is sent along with the regular 954 domain command. The element has an OPTIONAL "type" 955 attribute that defines the expected type of object ("application" or 956 "registration") to create. The server SHOULD validate the "type" 957 attribute, when passed, against the type of object that will be 958 created. The element contains the following child 959 elements: 961 The identifier for the launch phase. 962 or or 963 Zero or more elements. The 964 child elements are defined in the 965 element (Section 2.6.1) section. 966 Zero or more elements. The 967 child elements are defined in the 968 element (Section 2.6.3.1) section. 969 Zero or more 970 elements. The child elements are 971 defined in the element 972 (Section 2.6.3.2) section. 974 The following is an example domain command using the 975 extension, following the "code" validation model, 976 with multiple sunrise codes: 978 C: 979 C: 980 C: 981 C: 982 C: 984 C: example.tld 985 C: jd1234 986 C: sh8013 987 C: sh8013 988 C: 989 C: 2fooBAR 990 C: 991 C: 992 C: 993 C: 994 C: 996 C: sunrise 997 C: 998 C: 999 C: 49FD46E6C4B45C55D4AC 1000 C: 1001 C: 1002 C: 49FD46E6C4B45C55D4AD 1003 C: 1004 C: 1005 C: 1006 C: 49FD46E6C4B45C55D4AE 1007 C: 1008 C: 1009 C: 1010 C: ABC-12345 1011 C: 1012 C: 1013 The following is an example domain command using the 1014 extension, following the "mark" validation model, 1015 with the mark information: 1017 C: 1018 C: 1019 C: 1020 C: 1021 C: 1023 C: exampleone.tld 1024 C: jd1234 1025 C: sh8013 1026 C: sh8013 1027 C: 1028 C: 2fooBAR 1029 C: 1030 C: 1031 C: 1032 C: 1033 C: 1035 C: sunrise 1036 C: 1037 C: 1039 C: ... 1040 C: 1041 C: 1042 C: 1043 C: 1044 C: ABC-12345 1045 C: 1046 C: 1047 The following is an example domain command using the 1048 extension, following the "code with mark" validation 1049 model, with a code and mark information: 1051 C: 1052 C: 1053 C: 1054 C: 1055 C: 1057 C: example.tld 1058 C: jd1234 1059 C: sh8013 1060 C: sh8013 1061 C: 1062 C: 2fooBAR 1063 C: 1064 C: 1065 C: 1066 C: 1067 C: 1069 C: sunrise 1070 C: 1071 C: 1072 C: 49FD46E6C4B45C55D4AC 1073 C: 1075 C: ... 1076 C: 1077 C: 1078 C: 1079 C: 1080 C: ABC-12345 1081 C: 1082 C: 1083 The following is an example domain command using the 1084 extension, following the "signed mark" validation 1085 model, with the signed mark information for a sunrise application: 1087 C: 1088 C: 1089 C: 1090 C: 1091 C: 1093 C: exampleone.tld 1094 C: jd1234 1095 C: sh8013 1096 C: sh8013 1097 C: 1098 C: 2fooBAR 1099 C: 1100 C: 1101 C: 1102 C: 1103 C: 1106 C: sunrise 1107 C: 1109 C: ... 1110 C: 1111 C: 1112 C: 1113 C: ABC-12345 1114 C: 1115 C: 1116 The following is an example domain command using the 1117 extension, following the "signed mark" validation 1118 model, with the base64 encoded signed mark information: 1120 C: 1121 C: 1122 C: 1123 C: 1124 C: 1126 C: exampleone.tld 1127 C: jd1234 1128 C: sh8013 1129 C: sh8013 1130 C: 1131 C: 2fooBAR 1132 C: 1133 C: 1134 C: 1135 C: 1136 C: 1138 C: sunrise 1139 C: 1141 C: ... 1142 C: 1143 C: 1144 C: 1145 C: ABC-12345 1146 C: 1147 C: 1149 3.3.2. Claims Create Form 1151 The Claims Create Form of the extension to the EPP domain name 1152 mapping [RFC5731] includes the information related to the 1153 registrant's acceptance of the Claims Notice for the "claims" launch 1154 phase. 1156 A element is sent along with the regular 1157 domain command. The element has an OPTIONAL "type" 1158 attribute that defines the expected type of object ("application" or 1159 "registration") to create. The server SHOULD validate the "type" 1160 attribute, when passed, against the type of object that will be 1161 created. The element contains the following child 1162 elements: 1164 MUST contain the value of "claims" to indicate the 1165 claims launch phase. 1166 One or more elements that contain 1167 the following child elements: 1169 Unique notice identifier for the Claims 1170 Notice. The element has an OPTIONAL 1171 "validatorID" attribute is the Validator Identifier 1172 (Section 2.2) whose value indicates which Trademark Validator 1173 is the source of the Claims Notice, with the default being 1174 the ICANN TMCH. 1175 Expiry of the claims notice. 1176 Contains the date and time that the Claims 1177 Notice was accepted. 1179 The following is an example domain command using the 1180 extension with the information for 1181 the "tmch" and the "custom-tmch" validators, for the "claims" launch 1182 phase: 1184 C: 1185 C: 1186 C: 1187 C: 1188 C: 1190 C: example.tld 1191 C: jd1234 1192 C: sh8013 1193 C: sh8013 1194 C: 1195 C: 2fooBAR 1196 C: 1197 C: 1198 C: 1199 C: 1200 C: 1202 C: claims 1203 C: 1204 C: 1205 C: 370d0b7c9223372036854775807 1206 C: 2014-06-19T10:00:00.0Z 1207 C: 1208 C: 2014-06-19T09:00:00.0Z 1209 C: 1210 C: 1211 C: 1212 C: 1213 C: 470d0b7c9223654313275808 1214 C: 2014-06-19T10:00:00.0Z 1215 C: 1216 C: 2014-06-19T09:00:30.0Z 1217 C: 1218 C: 1219 C: 1220 C: 1221 C: ABC-12345 1222 C: 1223 C: 1225 3.3.3. General Create Form 1227 The General Create Form of the extension to the EPP domain name 1228 mapping [RFC5731] includes the launch phase and optionally the object 1229 type to create. The OPTIONAL "type" attribute defines the expected 1230 type of object ("application" or "registration") to create. The 1231 server SHOULD validate the "type" attribute, when passed, against the 1232 type of object that will be created. 1234 A element is sent along with the regular 1235 domain command. The element contains the following 1236 child elements: 1238 Contains the value of the active launch phase of the 1239 server. The server SHOULD validate the value against the active 1240 server launch phase. 1242 The following is an example domain command using the 1243 extension for a "landrush" launch phase application: 1245 C: 1246 C: 1247 C: 1248 C: 1249 C: 1251 C: example.tld 1252 C: jd1234 1253 C: sh8013 1254 C: sh8013 1255 C: 1256 C: 2fooBAR 1257 C: 1258 C: 1259 C: 1260 C: 1261 C: 1264 C: landrush 1265 C: 1266 C: 1267 C: ABC-12345 1268 C: 1269 C: 1271 3.3.4. Mixed Create Form 1273 The Mixed Create Form supports a mix of the create forms, where for 1274 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1275 Form (Section 3.3.2) MAY be supported in a single command by 1276 including both the verified trademark information and the information 1277 related to the registrant's acceptance of the Claims Notice. The 1278 server MAY support the Mixed Create Form. The "custom" launch phase 1279 SHOULD be used when using the Mixed Create Form. 1281 The following is an example domain command using the 1282 extension, with using a mix of the Sunrise Create 1283 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1284 including both a mark and a notice: 1286 C: 1287 C: 1288 C: 1289 C: 1290 C: 1292 C: exampleone.tld 1293 C: jd1234 1294 C: sh8013 1295 C: sh8013 1296 C: 1297 C: 2fooBAR 1298 C: 1299 C: 1300 C: 1301 C: 1302 C: 1305 C: custom 1306 C: 1307 C: 1309 C: ... 1310 C: 1311 C: 1312 C: 1313 C: 1314 C: 49FD46E6C4B45C55D4AC 1315 C: 1316 C: 2012-06-19T10:00:10.0Z 1317 C: 1318 C: 2012-06-19T09:01:30.0Z 1319 C: 1320 C: 1321 C: 1322 C: 1323 C: ABC-12345 1324 C: 1325 C: 1327 3.3.5. Create Response 1329 If the create was successful, the server MAY reply with the 1330 element along with the regular EPP to 1331 indicate the server generated Application Identifier (Section 2.1), 1332 when multiple applications of a given domain name are supported; 1333 otherwise no extension is included with the regular EPP . 1334 The element contains the following child elements: 1336 The phase of the application that mirrors the 1337 element included in the . 1338 The application identifier of the 1339 application. 1341 An example response when multiple overlapping applications are 1342 supported by the server: 1344 S: 1345 S: 1346 S: 1347 S: 1348 S: Command completed successfully; action pending 1349 S: 1350 S: 1351 S: 1353 S: example.tld 1354 S: 2010-08-10T15:38:26.623854Z 1355 S: 1356 S: 1357 S: 1358 S: 1360 S: sunrise 1361 S: 2393-9323-E08C-03B1 1362 S: 1363 S: 1364 S: 1365 S: 1366 S: ABC-12345 1367 S: 54321-XYZ 1368 S: 1369 S: 1370 S: 1372 3.4. EPP Command 1374 This extension defines additional elements to extend the EPP 1375 command to be used in conjunction with the domain name mapping. 1377 A client MUST NOT pass the extension on an EPP command to a 1378 server that does not support launch applications. A server that does 1379 not support launch applications during its launch phase MUST return 1380 an EPP error result code of 2102 when receiving an EPP 1381 command with the extension. 1383 Registry policies permitting, clients may update an application 1384 object by submitting an EPP command along with a 1385 element to indicate the application object to be 1386 updated. The element contains the following child 1387 elements: 1389 The phase during which the application was submitted 1390 or is associated with. 1391 The application identifier for which the 1392 client wishes to update. 1394 The following is an example domain command with the 1395 extension to add and remove a name server of a 1396 sunrise application with the application identifier "abc123": 1398 C: 1399 C: 1400 C: 1401 C: 1402 C: 1404 C: example.tld 1405 C: 1406 C: 1407 C: ns2.example.tld 1408 C: 1409 C: 1410 C: 1411 C: 1412 C: ns1.example.tld 1413 C: 1414 C: 1415 C: 1416 C: 1417 C: 1418 C: 1420 C: sunrise 1421 C: abc123 1422 C: 1423 C: 1424 C: ABC-12345 1425 C: 1426 C: 1428 This extension does not define any extension to the response of an 1429 domain command. After processing the command, the server 1430 replies with a standard EPP response as defined in the EPP domain 1431 name mapping [RFC5731]. 1433 3.5. EPP Command 1435 This extension defines additional elements to extend the EPP 1436 command to be used in conjunction with the domain name mapping. 1438 A client MUST NOT pass the extension on an EPP command to a 1439 server that does not support launch applications. A server that does 1440 not support launch applications during its launch phase MUST return 1441 an EPP error result code of 2102 when receiving an EPP 1442 command with the extension. 1444 Registry policies permitting, clients MAY withdraw an application by 1445 submitting an EPP command along with a 1446 element to indicate the application object to be deleted. The 1447 element contains the following child elements: 1449 The phase during which the application was submitted 1450 or is associated with. 1451 The application identifier for which the 1452 client wishes to delete. 1454 The following is an example domain command with the 1455 extension: 1457 C: 1458 C: 1459 C: 1460 C: 1461 C: 1463 C: example.tld 1464 C: 1465 C: 1466 C: 1467 C: 1469 C: sunrise 1470 C: abc123 1471 C: 1472 C: 1473 C: ABC-12345 1474 C: 1475 C: 1477 This extension does not define any extension to the response of a 1478 domain command. After processing the command, the server 1479 replies with a standard EPP response as defined in the EPP domain 1480 name mapping [RFC5731]. 1482 3.6. EPP Command 1484 This extension does not define any extension to the EPP 1485 command or response described in the EPP domain name mapping 1486 [RFC5731]. 1488 3.7. EPP Command 1490 This extension does not define any extension to the EPP 1491 command or response described in the EPP domain name mapping 1492 [RFC5731]. 1494 4. Formal Syntax 1496 One schema is presented here that is the EPP Launch Phase Mapping 1497 schema. 1499 The formal syntax presented here is a complete schema representation 1500 of the object mapping suitable for automated validation of EPP XML 1501 instances. The BEGIN and END tags are not part of the schema; they 1502 are used to note the beginning and ending of the schema for URI 1503 registration purposes. 1505 4.1. Launch Schema 1507 Copyright (c) 2012 IETF Trust and the persons identified as authors 1508 of the code. All rights reserved. 1510 Redistribution and use in source and binary forms, with or without 1511 modification, are permitted provided that the following conditions 1512 are met: 1514 o Redistributions of source code must retain the above copyright 1515 notice, this list of conditions and the following disclaimer. 1516 o Redistributions in binary form must reproduce the above copyright 1517 notice, this list of conditions and the following disclaimer in 1518 the documentation and/or other materials provided with the 1519 distribution. 1520 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1521 names of specific contributors, may be used to endorse or promote 1522 products derived from this software without specific prior written 1523 permission. 1525 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1526 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1527 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1528 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1529 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1530 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1531 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1532 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1533 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1534 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1535 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1537 BEGIN 1538 1539 1548 1551 1554 1557 1560 1561 1562 Extensible Provisioning Protocol v1.0 1563 domain name extension schema 1564 for the launch phase processing. 1565 1566 1568 1571 1572 1573 1574 1575 1577 1580 1581 1582 1584 1586 1587 1589 1592 1593 1594 1596 1602 1603 1604 1605 1606 1607 1608 1610 1613 1614 1615 1616 1617 1618 1619 1620 1621 1623 1626 1627 1628 1629 1630 1631 1632 1633 1634 1636 1637 1638 1640 1643 1644 1645 1646 1647 1649 1650 1651 1652 1654 1655 1656 1658 1661 1662 1663 1664 1665 1667 1670 1671 1672 1673 1674 1675 1676 1677 1678 1680 1681 1683 1686 1687 1688 1689 1691 1693 1694 1695 1696 1698 1702 1703 1704 1706 1708 1709 1711 1714 1715 1716 1717 1718 1720 1722 1724 1725 1729 1730 1731 1733 1736 1737 1738 1739 1740 1741 1743 1746 1747 1748 1749 1750 1751 1752 1754 1757 1758 1759 1760 1761 1763 1765 1769 1770 1771 1772 1773 1775 1777 1780 1781 1782 1783 1786 1787 1789 1791 1794 1795 1796 1798 1801 1802 1803 1804 1806 1807 1809 1810 1811 1812 1814 1815 1817 1818 1819 1820 1823 1824 1825 1827 1828 1829 1830 1832 1833 1834 1836 1839 1840 1841 1842 1845 1847 1849 1850 1852 1853 END 1855 5. Acknowledgements 1857 The authors wish to acknowledge the efforts of the leading 1858 participants of the Community TMCH Model that led to many of the 1859 changes to this document, which include Chris Wright, Jeff Neuman, 1860 Jeff Eckhaus, and Will Shorter. 1862 Special suggestions that have been incorporated into this document 1863 were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Jan 1864 Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus Malorny, 1865 Alexander Mayrhofer, Patrick Mevzek, James Mitchell, Francisco 1866 Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung Tran, Ulrich 1867 Wisser and Sharon Wodjenski. 1869 6. Change History 1871 6.1. Change from 00 to 01 1873 1. Changed to use camel case for the XML elements. 1874 2. Replaced "cancelled" status to "rejected" status. 1875 3. Added the child elements of the element. 1876 4. Removed the XML schema and replaced with "[TBD]". 1878 6.2. Change from 01 to 02 1880 1. Added support for both the ICANN and ARI/Neustar TMCH models. 1881 2. Changed the namespace URI and prefix to use "launch" instead of 1882 "launchphase". 1883 3. Added definition of multiple claim validation models. 1884 4. Added the and 1885 elements. 1886 5. Added support for Claims Info Command 1888 6.3. Change from 02 to 03 1890 1. Removed XSI namespace per Keith Gaughan's suggestion on the 1891 provreg list. 1892 2. Added extensibility to the launch:status element and added the 1893 pendingAuction status per Trung Tran's feedback on the provreg 1894 list. 1895 3. Added support for the Claims Check Command, updated the location 1896 and contents of the signedNotice, and replaced most references of 1897 Claim to Mark based on the work being done on the ARI/Neustar 1898 launch model. 1900 6.4. Change from 03 to 04 1902 1. Removed references to the ICANN model. 1903 2. Removed support for the Claims Info Command. 1904 3. Removed use of the signedClaim. 1905 4. Revised the method for referring to the signedClaim from the XML 1906 Signature using the IDREF URI. 1907 5. Split the launch-1.0.xsd into three XML schemas including launch- 1908 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 1909 6. Split the "claims" launch phase to the "claims1" and "claims2" 1910 launch phases. 1911 7. Added support for the encodedSignedMark with base64 encoded 1912 signedMark. 1913 8. Changed the elements in the createNoticeType to include the 1914 noticeID, timestamp, and the source elements. 1915 9. Added the class and effectiveDate elements to mark. 1917 6.5. Change from 04 to 05 1919 1. Removed reference to in the example. 1920 2. Incorporated feedback from Bernhard Reutner-Fischer on the 1921 provreg mail list. 1922 3. Added missing launch XML prefix to applicationIDType reference in 1923 the idContainerType of the Launch Schema. 1924 4. Added missing description of the element in the 1925 element. 1926 5. Updated note on replication of the EPP contact mapping elements 1927 in the Mark Contact section. 1929 6.6. Change from 05 to 06 1931 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 1932 replaced with reference to draft-lozano-smd, that contains the 1933 definition for the mark, signed marked, and encoded signed mark. 1934 2. Split the into and 1935 based on feedback from Trung Tran. 1936 3. Added the "includeMark" optional attribute to the 1937 element to enable the client to request whether or not to include 1938 the mark in the info response. 1939 4. Fixed state diagram to remove redundant transition from "invalid" 1940 to "rejected"; thanks Klaus Malorny. 1942 6.7. Change from 06 to 07 1944 1. Proof-read grammar and spelling. 1945 2. Changed "pendingAuction" status to "pendingAllocation", changed 1946 "pending" to "pendingValidation" status, per proposal from Trung 1947 Tran and seconded by Rubens Kuhl. 1948 3. Added text related to the use of RFC 5731 pendingCreate to the 1949 Application Identifier section. 1950 4. Added the Poll Messaging section to define the use of poll 1951 messaging for intermediate state transitions and pending action 1952 poll messaging for final state transitions. 1954 6.8. Change from 07 to 08 1956 1. Added support for use of the launch statuses and poll messaging 1957 for Launch Registrations based on feedback from Sharon Wodjenski 1958 and Trung Tran. 1959 2. Incorporated changes based on updates or clarifications in draft- 1960 lozano-tmch-func-spec-01, which include: 1962 1. Removed the unused element. 1963 2. Removed the element. 1965 3. Added the element based on the required 1966 element. 1968 6.9. Change from 08 to 09 1970 1. Made element optional in to allow 1971 passing just the in per request 1972 from Ben Levac. 1973 2. Added optional "type" attribute in to enable the 1974 client to explicitly define the desired type of object 1975 (application or registration) to create to all forms of the 1976 create extension. 1977 3. Added text that the server SHOULD validate the 1978 element in the Launch Phases section. 1979 4. Add the "General Create Form" to the create command extension to 1980 support the request from Ben Levac. 1981 5. Updated the text for the Poll Messaging section based on feedback 1982 from Klaus Malorny. 1983 6. Replaced the "claims1" and "claims2" phases with the "claims" 1984 phase based on discussion on the provreg list. 1985 7. Added support for a mixed create model (Sunrise Create Model and 1986 Claims Create Model), where a trademark (encoded signed mark, 1987 etc.) and notice can be passed, based on a request from James 1988 Mitchell. 1989 8. Added text for the handling of the overlapping "claims" and 1990 "landrush" launch phases. 1991 9. Added support for two check forms (claims check form and 1992 availability check form) based on a request from James Mitchell. 1993 The availability check form was based on the text in draft-rbp- 1994 application-epp-mapping. 1996 6.10. Change from 09 to 10 1998 1. Changed noticeIDType from base64Binary to token to be compatible 1999 with draft-lozano-tmch-func-spec-05. 2000 2. Changed codeType from base64Binary to token to be more generic. 2001 3. Updated based on feedback from Alexander Mayrhofer, which 2002 include: 2004 1. Changed "extension to the domain name extension" to 2005 "extension to the domain name mapping". 2006 2. Changed use of 2004 return code to 2306 return code when 2007 phase passed mismatches active phase and sub-phase. 2008 3. Changed description of "allocated" and "rejected" statuses. 2009 4. Moved sentence on a synchronous command 2010 without the use of an intermediate application, then an 2011 Application Identifier MAY not be needed to the Application 2012 Identifier section. 2014 5. Restructured the Mark Validation Models section to include 2015 the " element" sub-section, the 2016 " element" sub-section, and the Digital Signature 2017 sub-section. 2018 6. Changed "Registries may" to "Registries MAY". 2019 7. Changed "extensed" to "extended" in "Availability Check 2020 Form" section. 2021 8. Broke the mix of create forms in the "EPP Command" 2022 section to a fourth "Mixed Create Form" with its own sub- 2023 section. 2024 9. Removed "displayed or" from "displayed or accepted" in the 2025 description. 2026 10. Replaced "given domain name is supported" with "given domain 2027 name are supported" in the "Create Response" section. 2028 11. Changed the reference of 2303 (object does not exist) in the 2029 "Security Considerations" section to 2201 (authorization 2030 error). 2031 12. Added arrow from "invalid" status to "pendingValidation" 2032 status and "pendingAllocation" status to "rejected" status 2033 in the State Transition Diagram. 2034 4. Added the "C:" and "S:" example prefixes and related text in the 2035 "Conventions Used in This Document" section. 2037 6.11. Change from 10 to 11 2039 1. Moved the claims check response element under 2040 the element instead of the element based on 2041 the request from Francisco Obispo. 2043 6.12. Change from 11 to 12 2045 1. Added support for multiple validator identifiers for claims 2046 notices and marks based on a request and text provided by Mike 2047 O'Connell. 2048 2. Removed domain:exDate element from example in section 3.3.5 based 2049 on a request from Seth Goldman on the provreg list. 2050 3. Added clarifying text for clients not passing the launch 2051 extension on update and delete commands to servers that do not 2052 support launch applications based on a request from Sharon 2053 Wodjenski on the provreg list. 2055 6.13. Change from 12 to WG 00 2057 1. Changed to eppext working group draft by changing draft-tan-epp- 2058 launchphase to draft-ietf-eppext-launchphase and by changing 2059 references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch- 2060 smd. 2062 6.14. Change WG 00 to WG 01 2064 1. Removed text associated with support for the combining of status 2065 values based on feedback from Patrick Mevzek on the provreg 2066 mailing list, discussion on the eppext mailing list, and 2067 discussion at the eppext IETF meeting on March 6, 2014. 2069 6.15. Change WG 01 to WG 02 2071 1. Changed the element to be zero or more elements 2072 and the element to be one or more elements in the 2073 Claims Create Form. These changes were needed to be able to 2074 support more than one concurrent claims services. 2076 7. IANA Considerations 2078 This document uses URNs to describe XML namespaces and XML schemas 2079 conforming to a registry mechanism described in [RFC3688]. One URI 2080 assignment has been registered by the IANA. 2082 Registration request for the Launch namespace: 2084 URI: urn:ietf:params:xml:ns:launch-1.0 2085 Registrant Contact: See the "Author's Address" section of this 2086 document. 2087 XML: None. Namespace URIs do not represent an XML specification. 2089 8. Security Considerations 2091 The mapping extensions described in this document do not provide any 2092 security services beyond those described by EPP [RFC5730], the EPP 2093 domain name mapping [RFC5731], and protocol layers used by EPP. The 2094 security considerations described in these other specifications apply 2095 to this specification as well. 2097 Updates to, and deletion of an application object must be restricted 2098 to clients authorized to perform the said operation on the object. 2100 As information contained within an application, or even the mere fact 2101 that an application exists may be confidential. Any attempt to 2102 operate on an application object by an unauthorized client MUST be 2103 rejected with an EPP 2201 (authorization error) return code. Server 2104 policy may allow operation with filtered output by clients 2105 other than the sponsoring client, in which case the 2106 and response SHOULD be filtered to include only 2107 fields that are publicly accessible. 2109 9. References 2111 9.1. Normative References 2113 [I-D.ietf-eppext-tmch-smd] 2114 Lozano, G., "Mark and Signed Mark Objects Mapping", draft- 2115 ietf-eppext-tmch-smd-00 (work in progress), January 2014. 2117 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2118 Requirement Levels", BCP 14, RFC 2119, March 1997. 2120 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2121 January 2004. 2123 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2124 STD 69, RFC 5730, August 2009. 2126 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2127 Domain Name Mapping", STD 69, RFC 5731, August 2009. 2129 9.2. URIs 2131 [1] http://tools.ietf.org/html/draft-lozano-tmch-func-spec 2133 [2] http://tools.ietf.org/html/draft-lozano-tmch-func-spec 2135 Authors' Addresses 2137 James Gould 2138 VeriSign, Inc. 2139 12061 Bluemont Way 2140 Reston, VA 20190 2141 US 2143 Email: jgould@verisign.com 2144 URI: http://www.verisigninc.com 2146 Wil Tan 2147 Cloud Registry 2148 Suite 32 Seabridge House 2149 377 Kent St 2150 Sydney, NSW 2000 2151 AU 2153 Phone: +61 414 710899 2154 Email: wil@cloudregistry.net 2155 URI: http://www.cloudregistry.net 2156 Gavin Brown 2157 CentralNic Ltd 2158 35-39 Mooregate 2159 London, England EC2R 6AR 2160 GB 2162 Phone: +44 20 33 88 0600 2163 Email: gavin.brown@centralnic.com 2164 URI: https://www.centralnic.com