idnits 2.17.1 draft-tan-epp-launchphase-12.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 (November 12, 2013) is 3816 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 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: May 16, 2014 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 November 12, 2013 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-tan-epp-launchphase-12 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 May 16, 2014. 37 Copyright Notice 39 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 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.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 7 61 2.4.1. State Transition . . . . . . . . . . . . . . . . . . . 9 62 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . . 10 63 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . . 13 64 2.6.1. element . . . . . . . . . . . . . . 14 65 2.6.2. element . . . . . . . . . . . . . . . . . 15 66 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 15 67 2.6.3.1. element . . . . . . . . . . . . . 15 68 2.6.3.2. element . . . . . . . . . 15 69 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 15 70 3.1. EPP Command . . . . . . . . . . . . . . . . . . . 16 71 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 16 72 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 18 73 3.2. EPP Command . . . . . . . . . . . . . . . . . . . . 19 74 3.3. EPP Command . . . . . . . . . . . . . . . . . . . 23 75 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 23 76 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . . 29 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 . . . . . . . . . . . . . . . . . . . . . . . . 45 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 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 101 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 102 9. Normative References . . . . . . . . . . . . . . . . . . . . . 50 103 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51 105 1. Introduction 107 This document describes an extension mapping for version 1.0 of the 108 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 109 specifies a flexible schema that can be used to implement several 110 common use cases related to the provisioning and management of domain 111 name registrations and applications during the launch of a domain 112 name registry. 114 It is typical for domain registries to operate in special modes 115 during their initial launch to facilitate allocation of domain names, 116 often according to special rules. This document uses the term 117 "launch phase" and the shorter form "launch" to refer to such a 118 period. 120 The EPP domain name mapping [RFC5731] is designed for the steady- 121 state operation of a registry. During a launch period, the model in 122 place may be different from what is defined in the EPP domain name 123 mapping [RFC5731]. For example, registries often accept multiple 124 applications for the same domain name during the "Sunrise" launch 125 phase, referred to as a Launch Application. A Launch Registration 126 refers to a registration made during a launch phase when the server 127 uses a "first-come, first-served" model. Even in a "first-come, 128 first-served" model, additional steps and information might be 129 required, such as trademark information. In addition, the TMCH 130 Functional Specification [1] defines a registry interface for the 131 Trademark Claims or "claims" launch phase that includes support for 132 presenting a Trademark Claims Notice to the Registrant. This 133 document proposes an extension to the domain name mapping in order to 134 provide a uniform interface for the management of Launch Applications 135 and Launch Registrations in launch phases. 137 1.1. Conventions Used in This Document 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 141 document are to be interpreted as described in RFC 2119 [RFC2119]. 143 XML is case sensitive. Unless stated otherwise, XML specifications 144 and examples provided in this document MUST be interpreted in the 145 character case presented in order to develop a conforming 146 implementation. 148 In examples, "C:" represents lines sent by a protocol client and "S:" 149 represents lines returned by a protocol server. Indentation and 150 white space in examples are provided only to illustrate element 151 relationships and are not a REQUIRED feature of this protocol. 153 "launch-1.0" is used as an abbreviation for 154 "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix 155 "launch" is used, but implementations MUST NOT depend on it and 156 instead employ a proper namespace-aware XML parser and serializer to 157 interpret and output the XML documents. 159 "signedMark-1.0" is used as an abbreviation for 160 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in 161 [draft-lozano-smd]. The XML namespace prefix "smd" is used, but 162 implementations MUST NOT depend on it and instead employ a proper 163 namespace-aware XML parser and serializer to interpret and output the 164 XML documents. 166 "mark-1.0" is used as an abbreviation for 167 "urn:ietf:params:xml:ns:mark-1.0" that is defined in 168 [draft-lozano-smd]. The XML namespace prefix "mark" is used, but 169 implementations MUST NOT depend on it and instead employ a proper 170 namespace-aware XML parser and serializer to interpret and output the 171 XML documents. 173 2. Object Attributes 175 This extension adds additional elements to the EPP domain name 176 mapping [RFC5731]. Only those new elements are described here. 178 2.1. Application Identifier 180 Servers MAY allow multiple applications, referred to as a Launch 181 Application, of the same domain name during its launch phase 182 operations. Upon receiving a valid request to create a Launch 183 Application, the server MUST create an application object 184 corresponding to the request, assign an application identifier for 185 the Launch Application, set the [RFC5731] pendingCreate status, and 186 return the application identifier to the client with the element. In order to facilitate correlation, all 188 subsequent launch operations on the Launch Application MUST be 189 qualified by the previously assigned application identifier using the 190 element. 192 If the command processes a request synchronously 193 without the use of an intermediate Launch Application, then an 194 application identifier MAY not be needed. 196 2.2. Validator Identifier 198 The Validator Identifier is the unique identifier for a Trademark 199 Validator that validates marks and has a repository of validated 200 marks. The OPTIONAL "validatorID" attribute is used to define the 201 Validator Identifier of the Trademark Validator. Registries MAY 202 support more than one Third Party Trademark Validator. The Internet 203 Corporation for Assigned Names and Numbers (ICANN) Trademark 204 Clearinghouse (TMCH) is the default Trademark Validator and is 205 reserved the Validator Identifier of "tmch". If the ICANN TMCH is 206 not used or multiple Trademark Validators are used, the Validator 207 Identifier MUST be defined using the "validatorID" attribute. 209 The Validator Identifier MAY be related to one or more issuer 210 identifiers of the element and the element defined 211 in [draft-lozano-smd]. Both the Validator Identifier and the Issuer 212 Identifier used MUST be unique. The list of validator identifiers 213 and the relationship to issuer identifiers is out of scope for this 214 document. 216 2.3. Launch Phases 218 The server MAY support multiple launch phases sequentially or 219 simultaneously. The element MUST be included by the 220 client to define the target launch phase of the command. The server 221 SHOULD validate the phase and MAY validate the sub-phase of the 222 element against the active phase and OPTIONAL sub- 223 phase of the server on a create command, and return an EPP error 224 result code of 2306 if there is a mismatch. 226 The following launch phase values are defined: 227 sunrise The phase during which trademark holders can submit 228 registrations or applications with trademark information that can 229 be validated by the server. 230 landrush A post-Sunrise phase when non-trademark holders are allowed 231 to register domain names with steps taken to address a large 232 volume of initial registrations. 233 claims The Trademark Claims phase, as defined in the TMCH Functional 234 Specification [1], in which a Claims Notice must be displayed to a 235 prospective registrant of a domain name that matches trademarks. 236 open A post-launch phase that is also referred to as "steady state". 237 Servers MAY require additional trademark protection during this 238 phase. 239 custom A custom server launch phase that is defined using the "name" 240 attribute. 242 For extensibility, the element includes an OPTIONAL 243 "name" attribute that can define a sub-phase or the full name of the 244 phase when the element has the "custom" value. For 245 example, the "claims" launch phase could have two sub-phases that 246 include "landrush" and "open". 248 Launch phases MAY overlap to support the "claims" launch phase, 249 defined in the TMCH Functional Specification [1], and to support a 250 traditional "landrush" launch phase. The overlap of the "claims" and 251 "landrush" launch phases SHOULD be handled by setting "claims" as the 252 value and setting "landrush" as the sub-phase with the 253 "name" attribute. For example, the element SHOULD be 254 claims. 256 2.4. Status Values 258 A Launch Application or Launch Registration object MAY have a launch 259 status value. The element is used to convey the 260 launch status pertaining to the object, beyond what is specified in 261 the object mapping. A Launch Application or Launch Registration MUST 262 set the [RFC5731] "pendingCreate" status if a launch status is 263 supported and the launch status is not one of the final statuses, 264 including the "allocated" and "rejected" statuses. 266 The following status values are defined using the required "s" 267 attribute: 268 pendingValidation: The initial state of a newly-created application 269 or registration object. The application or registration requires 270 validation, but the validation process has not yet completed. 271 validated: The application or registration meets relevant registry 272 rules. 273 invalid: The application or registration does not validate according 274 to registry rules. Server policies permitting, it may transition 275 back into "pendingValidation" for revalidation, after 276 modifications are made to ostensibly correct attributes that 277 caused the validation failure. 278 pendingAllocation: The allocation of the application or registration 279 is pending based on the results of some out-of-band process (for 280 example, an auction). 281 allocated: The object corresponding to the application or 282 registration has been provisioned. Is a possible end state of an 283 application or registration object. 284 rejected: The application or registration object was not 285 provisioned. Is a possible end state of an application or 286 registration object. 287 custom: A custom status that is defined using the "name" attribute. 289 Each status value MAY be accompanied by a string of human-readable 290 text that describes the rationale for the status applied to the 291 object. The OPTIONAL "lang" attribute MAY be present to identify the 292 language if the negotiated value is something other than the default 293 value of "en" (English). 295 For extensibility the element includes an OPTIONAL 296 "name" attribute that can define a sub-status or the full name of the 297 status when the status value is "custom". The server SHOULD NOT use 298 the "custom" status value. 300 Certain status values MAY be combined. For example, an application 301 or registration may be both "invalid" and "rejected". Additionally, 302 certain statuses MAY be skipped. For example, an application or 303 registration MAY immediately start at the "allocated" status or an 304 application or registration MAY skip the "pendingAllocation" status. 305 If the launch phase does not require validation of a request, an 306 application or registration MAY immediately skip to 307 "pendingAllocation". 309 2.4.1. State Transition 311 | request 312 | 313 | +--------------------------+ 314 | | | 315 v v | 316 +-------------------+ | 317 | | | 318 | pendingValidation +--------------+ | 319 | | | | 320 +---------+---------+ | | 321 | | | 322 | | | 323 v v | 324 +-----------+ +---------+ | 325 | | | | | 326 | validated | | invalid +--+ 327 | | | | 328 +-----+-----+ +----+----+ 329 | | 330 | | 331 v | 332 +-------------------+ | 333 | | | 334 | pendingAllocation +-----------+ | 335 | | | | 336 +---------+---------+ | | 337 | | | 338 | | | 339 | | | 340 | | | 341 | | | 342 v v v 343 +---------+ +--------+ 344 / \ / \ 345 | allocated | | rejected | 346 \ / \ / 347 +---------+ +--------+ 349 Figure 1 351 2.5. Poll Messaging 353 A Launch Application MUST and a Launch Registration MAY be handled as 354 a domain name of [RFC5731] in "pendingCreate" status, with the launch 355 status values defined in Section 2.4. As a Launch Application or 356 Launch Registration transitions between the status values defined in 357 Section 2.4, the server SHOULD insert poll messages, per [RFC5730], 358 for the applicable intermediate statuses, including the 359 "pendingValidation", "validated", "pendingAllocation, and "invalid" 360 statuses, using the element with the extension. The element MAY contain non- 362 mandatory information, like contact and name server information. 363 Also, further extensions that would normally be included in the 364 response of a command, per [RFC5731], MAY be included. 365 For the final statuses, including the "allocated" and "rejected" 366 statuses, the server MUST insert a poll message, per 367 [RFC5731], with the extension. 369 The following is an example poll message for a Launch Application 370 that has transitioned to the "pendingAllocation" state. 372 S: 373 S: 374 S: 375 S: 376 S: Command completed successfully; ack to dequeue 377 S: 378 S: 379 S: 2013-04-04T22:01:00.0Z 380 S: Application pendingAllocation. 381 S: 382 S: 383 S: 385 S: example.tld 386 S: ... 387 S: 388 S: 389 S: 390 S: 392 S: sunrise 393 S: abc123 394 S: 395 S: 396 S: 397 S: 398 S: ABC-12345 399 S: 54322-XYZ 400 S: 401 S: 402 S: 403 The following is an example poll message for an 404 "allocated" Launch Application. 406 S: 407 S: 408 S: 409 S: 410 S: Command completed successfully; ack to dequeue 411 S: 412 S: 413 S: 2013-04-04T22:01:00.0Z 414 S: Application successfully allocated. 415 S: 416 S: 417 S: 419 S: example.tld 420 S: 421 S: ABC-12345 422 S: 54321-XYZ 423 S: 424 S: 2013-04-04T22:00:00.0Z 425 S: 426 S: 427 S: 428 S: 430 S: sunrise 431 S: abc123 432 S: 433 S: 434 S: 435 S: 436 S: BCD-23456 437 S: 65432-WXY 438 S: 439 S: 440 S: 441 The following is an example poll message for an 442 "allocated" Launch Registration. 444 S: 445 S: 446 S: 447 S: 448 S: Command completed successfully; ack to dequeue 449 S: 450 S: 451 S: 2013-04-04T22:01:00.0Z 452 S: Registration successfully allocated. 453 S: 454 S: 455 S: 457 S: example.tld 458 S: 459 S: ABC-12345 460 S: 54321-XYZ 461 S: 462 S: 2013-04-04T22:00:00.0Z 463 S: 464 S: 465 S: 466 S: 468 S: sunrise 469 S: 470 S: 471 S: 472 S: 473 S: BCD-23456 474 S: 65432-WXY 475 S: 476 S: 477 S: 479 2.6. Mark Validation Models 481 A server MUST support at least one of the following models for 482 validating trademark information: 484 code Use of a mark code by itself to validate that the mark matches 485 the domain name. This model is supported using the element with just the element. 488 mark The mark information is passed without any other validation 489 element. The server will use some custom form of validation to 490 validate that the mark information is authentic. This model is 491 supported using the element with just the (Section 2.6.2) element. 493 code with mark: A code is used along with the mark information by 494 the server to validate the mark utilizing an external party. The 495 code represents some form of secret that matches the mark 496 information passed. This model is supported using the element that contains both the and the 498 (Section 2.6.2) elements. 499 signed mark: The mark information is digitally signed as described 500 in the Digital Signature (Section 2.6.3) section. The digital 501 signature can be directly validated by the server using the public 502 key of the external party that created the signed mark using its 503 private key. This model is supported using the 504 (Section 2.6.3.1) and (Section 2.6.3.2) 505 elements. 507 More than one , (Section 2.6.3.1), 508 or (Section 2.6.3.2) element MAY be 509 specified. The maximum number of marks per domain name is up to 510 server policy. 512 2.6.1. element 514 The element that is used by the "code", "mark", and 515 "code with mark" validation models, has the following child elements: 517 : OPTIONAL mark code used to validate the 518 (Section 2.6.2) information. The mark code is be a mark-specific 519 secret that the server can verify against a third party. The 520 OPTIONAL "validatorID" attribute is the Validator Identifier 521 (Section 2.2) whose value indicates which Trademark Validator that 522 the code originated from, with no default value. 523 : OPTIONAL mark information with child elements defined 524 in the Mark (Section 2.6.2) section. 526 The following is an example element with both a 527 and (Section 2.6.2) element. 529 530 531 49FD46E6C4B45C55D4AC 532 533 ... 534 535 537 2.6.2. element 539 A element describes an applicant's prior right to a given 540 domain name that is used with the "mark", "mark with code", and the 541 "signed mark" validation models. The element is defined 542 in [draft-lozano-smd]. A new mark format can be supported by 543 creating a new XML schema for the mark that has an element that 544 substitutes for the element from 545 [draft-lozano-smd]. 547 2.6.3. Digital Signature 549 Digital signatures MAY be used by the server to validate either the 550 mark information, when using the "signed mark" validation model with 551 the (Section 2.6.3.1) element or the (Section 2.6.3.2) element. 554 2.6.3.1. element 556 The element contains the digitally signed mark 557 information. The element is defined in 558 [draft-lozano-smd]. A new signed mark format can be supported by 559 creating a new XML schema for the signed mark that has an element 560 that substitutes for the element from 561 [draft-lozano-smd]. 563 2.6.3.2. element 565 The element contains an encoded form of the 566 digitally signed (Section 2.6.3.1) element. The 567 element is defined in [draft-lozano-smd]. A 568 new encoded signed mark format can be supported by creating a new XML 569 schema for the encoded signed mark that has an element that 570 substitutes for the element from 571 [draft-lozano-smd]. 573 3. EPP Command Mapping 575 A detailed description of the EPP syntax and semantics can be found 576 in the EPP core protocol specification [RFC5730]. The command 577 mappings described here are specifically for use in the Launch Phase 578 Extension. 580 This mapping is designed to be flexible, requiring only a minimum set 581 of required elements. 583 While it is meant to serve several use cases, it does not prescribe 584 any interpretation by the client or server. Such processing is 585 typically highly policy-dependent and therefore specific to 586 implementations. 588 Operations on application objects are done via one or more of the 589 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 590 Registries MAY choose to support a subset of the operations. 592 3.1. EPP Command 594 There are two forms of the extension to the EPP command: the 595 Claims Check Form (Section 3.1.1) and the Availability Check Form 596 (Section 3.1.2). The element "type" attribute defines 597 the form, with the value of "claims" for the Claims Check Form 598 (Section 3.1.1) and with the value of "avail" for the Availability 599 Check Form (Section 3.1.2). The default value of the "type" 600 attribute is "claims". The forms supported by the server is 601 determined by server policy. The server MUST return an EPP error 602 result code of 2307 if it receives a check form that is not 603 supported. 605 3.1.1. Claims Check Form 607 The Claims Check Form defines a new command called the Claims Check 608 Command that is used to determine whether or not there are any 609 matching trademarks, in the specified launch phase, for each domain 610 name passed in the command. The availability check information 611 defined in the EPP domain name mapping [RFC5731] MUST NOT be returned 612 for the Claims Check Command. This form is the default form and MAY 613 be explicitly identified by setting the "type" 614 attribute to "claims". 616 Instead of returning whether the domain name is available, the Claims 617 Check Command will return whether or not at least one matching 618 trademark exists for the domain name. If there is at least one 619 matching trademark that exists for the domain name, a element is returned. The client MAY then use the value of 621 the element to obtain information needed to 622 generate the Trademark Claims Notice from Trademark Validator based 623 on the Validator Identifier (Section 2.2). The unique notice 624 identifier of the Trademark Claims Notice MUST be passed in the 625 element of the extension to the Create Command 626 (Section 3.3). 628 The elements in the EPP command of EPP domain 629 name mapping [RFC5731] define the domain names to check for matching 630 trademarks. The element contains the following child 631 elements: 633 The launch phase that SHOULD be "claims". 635 Example Claims Check command using the domain command and the 636 extension with the "type" explicitly set to "claims", 637 to determine if "example1.tld" and "example2.tld" have any matching 638 trademarks during the "claims" launch phase: 640 C: 641 C: 642 C: 643 C: 644 C: 646 C: example1.tld 647 C: example2.tld 648 C: 649 C: 650 C: 651 C: 654 C: claims 655 C: 656 C: 657 C: ABC-12345 658 C: 659 C: 661 If the command has been processed successfully, the EPP 662 MUST contain an element that 663 identifies the launch namespace. The element 664 contains the following child elements: 666 The launch phase that SHOULD be "claims". 667 One or more elements that contain the 668 following child elements: 670 Contains the fully qualified name of the queried 671 domain name. This element MUST contain an "exists" attribute 672 whose value indicates if a matching trademark exists for the 673 domain name. A value of "1" (or "true") means that a 674 matching trademark does exist for the claims launch phase. A 675 value of "0" (or "false") means that a matching trademark 676 does not exist. 678 An OPTIONAL claim key that MAY be passed to a 679 third-party trademark validator such as the Trademark 680 Clearinghouse (TMCH) for querying the information needed to 681 generate a Trademark Claims Notice. The is 682 used as the key for the query in place of the domain name to 683 securely query the service without using a well-known value 684 like a domain name. The OPTIONAL "validatorID" attribute is 685 the Validator Identifier (Section 2.2) whose value indicates 686 which Trademark Validator to query for the Claims Notice 687 information, with the default being the ICANN TMCH. 689 Example Claims Check response when no matching trademarks are found 690 for the domain name example1.tld and matching trademarks are found 691 for the domain name example2.tld for the "claims" launch phase: 693 S: 694 S: 695 S: 696 S: 697 S: Command completed successfully 698 S: 699 S: 700 S: 702 S: claims 703 S: 704 S: example1.tld 705 S: 706 S: 707 S: example2.tld 708 S: 709 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 710 S: 711 S: 712 S: 713 S: 714 S: 715 S: ABC-12345 716 S: 54321-XYZ 717 S: 718 S: 719 S: 721 3.1.2. Availability Check Form 723 The Availability Check Form defines additional elements to extend the 724 EPP command described in the EPP domain name mapping 725 [RFC5731]. No additional elements are defined for the EPP 726 response. This form MUST be identified by setting the 727 "type" attribute to "avail". 729 The EPP command is used to determine if an object can be 730 provisioned within a repository. Domain names may be made available 731 only in unique launch phases, whilst remaining unavailable for 732 concurrent launch phases. In addition to the elements expressed in 733 the , the command is extended with the 734 element that contains the following child elements: 736 The launch phase to which domain name availability 737 should be determined. 739 Example Availability Check Form command using the domain 740 command and the extension with the "type" set to 741 "avail", to determine the availability of two domain names in the 742 "idn-release" custom launch phase: 744 C: 745 C: 746 C: 747 C: 748 C: 750 C: example1.tld 751 C: example2.tld 752 C: 753 C: 754 C: 755 C: 758 C: custom 759 C: 760 C: 761 C: ABC-12345 762 C: 763 C: 765 The Availability Check Form does not define any extension to the 766 response of an domain command. After processing the command, 767 the server replies with a standard EPP response as defined in the EPP 768 domain name mapping [RFC5731]. 770 3.2. EPP Command 772 This extension defines additional elements to extend the EPP 773 command and response to be used in conjunction with the EPP domain 774 name mapping [RFC5731]. 776 The EPP command is used to retrieve information for a launch 777 phase registration or application. The Application Identifier 778 (Section 2.1) returned in the element of the create 779 response (Section 3.3) is used for retrieving information for a 780 Launch Application. A element is sent along with the 781 regular domain command. The element includes an 782 OPTIONAL "includeMark" boolean attribute, with a default value of 783 "false", to indicate whether or not to include the mark in the 784 response. The element contains the following child 785 elements: 787 The phase during which the application or 788 registration was submitted or is associated with. Server policy 789 defines the phases that are supported. 790 OPTIONAL application identifier of the Launch 791 Application. 793 Example domain command with the extension to 794 retrieve information for the sunrise application for example.tld and 795 application identifier "abc123": 797 C: 798 C: 799 C: 800 C: 801 C: 803 C: example.tld 804 C: 805 C: 806 C: 807 C: 810 C: sunrise 811 C: abc123 812 C: 813 C: 814 C: ABC-12345 815 C: 816 C: 817 Example domain command with the extension to 818 retrieve information for the sunrise registration for example.tld: 820 C: 821 C: 822 C: 823 C: 824 C: 826 C: example.tld 827 C: 828 C: 829 C: 830 C: 832 C: sunrise 833 C: 834 C: 835 C: ABC-12345 836 C: 837 C: 839 If the query was successful, the server replies with a element along with the regular EPP . The contains the following child elements: 843 The phase during which the application was submitted, 844 or is associated with, that matches the associated command 845 . 846 OPTIONAL Application Identifier of the Launch 847 Application. 848 OPTIONAL status of the Launch Application using one 849 of the supported status values (Section 2.4). 850 Zero or more (Section 2.6.2) elements. 852 Example domain response using the extension 853 with the mark information: 855 S: 856 S: 857 S: 858 S: 859 S: Command completed successfully 860 S: 861 S: 862 S: 864 S: example.tld 865 S: EXAMPLE1-REP 866 S: 867 S: jd1234 868 S: sh8013 869 S: sh8013 870 S: ClientX 871 S: ClientY 872 S: 2012-04-03T22:00:00.0Z 873 S: 874 S: 2fooBAR 875 S: 876 S: 877 S: 878 S: 879 S: 881 S: sunrise 882 S: abc123 883 S: 884 S: 886 S: ... 887 S: 888 S: 889 S: 890 S: 891 S: ABC-12345 892 S: 54321-XYZ 893 S: 894 S: 895 S: 897 3.3. EPP Command 899 There are four forms of the extension to the EPP command 900 that include the Sunrise Create Form (Section 3.3.1), the Claims 901 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 902 and the Mixed Create Form (Section 3.3.4). The form is dependent on 903 the supported launch phases (Section 2.3) as defined below. 905 sunrise The EPP command with the "sunrise" launch phase is 906 used to submit a registration with trademark information that can 907 be verified by the server with the value. The 908 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 909 launch phase. 910 landrush The EPP command with the "landrush" launch phase 911 MAY use the General Create Form (Section 3.3.3) to explicitly 912 specify the phase and optionally define the expected type of 913 object to create. 914 claims The EPP command with the "claims" launch phase is 915 used to pass the information associated with the presentation and 916 acceptance of the Claims Notice. The Claims Create Form 917 (Section 3.3.2) is used and the General Create Form 918 (Section 3.3.3) MAY be used for the "claims" launch phase. 919 open The EPP command with the "open" launch phase is 920 undefined but the form supported is up to server policy. 921 custom The EPP command with the "custom" launch phase is 922 undefined but the form supported is up to server policy. 924 3.3.1. Sunrise Create Form 926 The Sunrise Create Form of the extension to the EPP domain name 927 mapping [RFC5731] includes the verifiable trademark information that 928 the server uses to match against the domain name to authorize the 929 domain create. A server MUST support one of four models in Claim 930 Validation Models (Section 2.6) to verify the trademark information 931 passed by the client. 933 A element is sent along with the regular 934 domain command. The element has an OPTIONAL "type" 935 attribute that defines the expected type of object ("application" or 936 "registration") to create. The server SHOULD validate the "type" 937 attribute, when passed, against the type of object that will be 938 created. The element contains the following child 939 elements: 941 The identifier for the launch phase. 942 or or 943 Zero or more elements. The 944 child elements are defined in the element (Section 2.6.1) section. 946 Zero or more elements. The 947 child elements are defined in the element (Section 2.6.3.1) section. 949 Zero or more 950 elements. The child elements are 951 defined in the element 952 (Section 2.6.3.2) section. 954 The following is an example domain command using the 955 extension, following the "code" validation model, 956 with multiple sunrise codes: 958 C: 959 C: 960 C: 961 C: 962 C: 964 C: example.tld 965 C: jd1234 966 C: sh8013 967 C: sh8013 968 C: 969 C: 2fooBAR 970 C: 971 C: 972 C: 973 C: 974 C: 976 C: sunrise 977 C: 978 C: 979 C: 49FD46E6C4B45C55D4AC 980 C: 981 C: 982 C: 49FD46E6C4B45C55D4AD 983 C: 984 C: 985 C: 986 C: 49FD46E6C4B45C55D4AE 987 C: 988 C: 989 C: 990 C: ABC-12345 991 C: 992 C: 993 The following is an example domain command using the 994 extension, following the "mark" validation model, 995 with the mark information: 997 C: 998 C: 999 C: 1000 C: 1001 C: 1003 C: exampleone.tld 1004 C: jd1234 1005 C: sh8013 1006 C: sh8013 1007 C: 1008 C: 2fooBAR 1009 C: 1010 C: 1011 C: 1012 C: 1013 C: 1015 C: sunrise 1016 C: 1017 C: 1019 C: ... 1020 C: 1021 C: 1022 C: 1023 C: 1024 C: ABC-12345 1025 C: 1026 C: 1027 The following is an example domain command using the 1028 extension, following the "code with mark" validation 1029 model, with a code and mark information: 1031 C: 1032 C: 1033 C: 1034 C: 1035 C: 1037 C: example.tld 1038 C: jd1234 1039 C: sh8013 1040 C: sh8013 1041 C: 1042 C: 2fooBAR 1043 C: 1044 C: 1045 C: 1046 C: 1047 C: 1049 C: sunrise 1050 C: 1051 C: 1052 C: 49FD46E6C4B45C55D4AC 1053 C: 1055 C: ... 1056 C: 1057 C: 1058 C: 1059 C: 1060 C: ABC-12345 1061 C: 1062 C: 1063 The following is an example domain command using the 1064 extension, following the "signed mark" validation 1065 model, with the signed mark information for a sunrise application: 1067 C: 1068 C: 1069 C: 1070 C: 1071 C: 1073 C: exampleone.tld 1074 C: jd1234 1075 C: sh8013 1076 C: sh8013 1077 C: 1078 C: 2fooBAR 1079 C: 1080 C: 1081 C: 1082 C: 1083 C: 1086 C: sunrise 1087 C: 1089 C: ... 1090 C: 1091 C: 1092 C: 1093 C: ABC-12345 1094 C: 1095 C: 1096 The following is an example domain command using the 1097 extension, following the "signed mark" validation 1098 model, with the base64 encoded signed mark information: 1100 C: 1101 C: 1102 C: 1103 C: 1104 C: 1106 C: exampleone.tld 1107 C: jd1234 1108 C: sh8013 1109 C: sh8013 1110 C: 1111 C: 2fooBAR 1112 C: 1113 C: 1114 C: 1115 C: 1116 C: 1118 C: sunrise 1119 C: 1121 C: ... 1122 C: 1123 C: 1124 C: 1125 C: ABC-12345 1126 C: 1127 C: 1129 3.3.2. Claims Create Form 1131 The Claims Create Form of the extension to the EPP domain name 1132 mapping [RFC5731] includes the information related to the 1133 registrant's acceptance of the Claims Notice for the "claims" launch 1134 phase. 1136 A element is sent along with the regular 1137 domain command. The element has an OPTIONAL "type" 1138 attribute that defines the expected type of object ("application" or 1139 "registration") to create. The server SHOULD validate the "type" 1140 attribute, when passed, against the type of object that will be 1141 created. The element contains the following child 1142 elements: 1144 MUST contain the value of "claims" to indicate the 1145 claims launch phase. 1146 1147 Unique notice identifier for the Claims 1148 Notice. The element has an OPTIONAL 1149 "validatorID" attribute is the Validator Identifier 1150 (Section 2.2) whose value indicates which Trademark Validator 1151 is the source of the Claims Notice, with the default being 1152 the ICANN TMCH. 1153 Expiry of the claims notice. 1154 Contains the date and time that the Claims 1155 Notice was accepted. 1157 The following is an example domain command using the 1158 extension with the information for 1159 the "claims" launch phase: 1161 C: 1162 C: 1163 C: 1164 C: 1165 C: 1167 C: example.tld 1168 C: jd1234 1169 C: sh8013 1170 C: sh8013 1171 C: 1172 C: 2fooBAR 1173 C: 1174 C: 1175 C: 1176 C: 1177 C: 1179 C: claims 1180 C: 1181 C: 1182 C: 49FD46E6C4B45C55D4AC 1183 C: 1184 C: 2012-06-19T10:00:10.0Z 1185 C: 1186 C: 2012-06-19T09:01:30.0Z 1187 C: 1188 C: 1189 C: 1190 C: 1191 C: ABC-12345 1192 C: 1193 C: 1195 3.3.3. General Create Form 1197 The General Create Form of the extension to the EPP domain name 1198 mapping [RFC5731] includes the launch phase and optionally the object 1199 type to create. The OPTIONAL "type" attribute defines the expected 1200 type of object ("application" or "registration") to create. The 1201 server SHOULD validate the "type" attribute, when passed, against the 1202 type of object that will be created. 1204 A element is sent along with the regular 1205 domain command. The element contains the following 1206 child elements: 1208 Contains the value of the active launch phase of the 1209 server. The server SHOULD validate the value against the active 1210 server launch phase. 1212 The following is an example domain command using the 1213 extension for a "landrush" launch phase application: 1215 C: 1216 C: 1217 C: 1218 C: 1219 C: 1221 C: example.tld 1222 C: jd1234 1223 C: sh8013 1224 C: sh8013 1225 C: 1226 C: 2fooBAR 1227 C: 1228 C: 1229 C: 1230 C: 1231 C: 1234 C: landrush 1235 C: 1236 C: 1237 C: ABC-12345 1238 C: 1239 C: 1241 3.3.4. Mixed Create Form 1243 The Mixed Create Form supports a mix of the create forms, where for 1244 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1245 Form (Section 3.3.2) MAY be supported in a single command by 1246 including both the verified trademark information and the information 1247 related to the registrant's acceptance of the Claims Notice. The 1248 server MAY support the Mixed Create Form. The "custom" launch phase 1249 SHOULD be used when using the Mixed Create Form. 1251 The following is an example domain command using the 1252 extension, with using a mix of the Sunrise Create 1253 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1254 including both a mark and a notice: 1256 C: 1257 C: 1258 C: 1259 C: 1260 C: 1262 C: exampleone.tld 1263 C: jd1234 1264 C: sh8013 1265 C: sh8013 1266 C: 1267 C: 2fooBAR 1268 C: 1269 C: 1270 C: 1271 C: 1272 C: 1275 C: custom 1276 C: 1277 C: 1279 C: ... 1280 C: 1281 C: 1282 C: 1283 C: 1284 C: 49FD46E6C4B45C55D4AC 1285 C: 1286 C: 2012-06-19T10:00:10.0Z 1287 C: 1288 C: 2012-06-19T09:01:30.0Z 1289 C: 1290 C: 1291 C: 1292 C: 1293 C: ABC-12345 1294 C: 1295 C: 1297 3.3.5. Create Response 1299 If the create was successful, the server MAY reply with the element along with the regular EPP to indicate the 1301 server generated Application Identifier (Section 2.1), when multiple 1302 applications of a given domain name are supported; otherwise no 1303 extension is included with the regular EPP . The element contains the following child elements: 1306 The phase of the application that mirrors the 1307 element included in the . 1308 The application identifier of the 1309 application. 1311 An example response when multiple overlapping applications are 1312 supported by the server: 1314 S: 1315 S: 1316 S: 1317 S: 1318 S: Command completed successfully; action pending 1319 S: 1320 S: 1321 S: 1323 S: example.tld 1324 S: 2010-08-10T15:38:26.623854Z 1325 S: 1326 S: 1327 S: 1328 S: 1330 S: sunrise 1331 S: 2393-9323-E08C-03B1 1332 S: 1333 S: 1334 S: 1335 S: 1336 S: ABC-12345 1337 S: 54321-XYZ 1338 S: 1339 S: 1340 S: 1342 3.4. EPP Command 1344 This extension defines additional elements to extend the EPP 1345 command to be used in conjunction with the domain name mapping. 1347 A client MUST NOT pass the extension on an EPP command to a 1348 server that does not support launch applications. A server that does 1349 not support launch applications during its launch phase MUST return 1350 an EPP error result code of 2102 when receiving an EPP 1351 command with the extension. 1353 Registry policies permitting, clients may update an application 1354 object by submitting an EPP command along with a element to indicate the application object to be updated. 1356 The element contains the following child elements: 1358 The phase during which the application was submitted 1359 or is associated with. 1360 The application identifier for which the 1361 client wishes to update. 1363 The following is an example domain command with the extension to add and remove a name server of a sunrise 1365 application with the application identifier "abc123": 1367 C: 1368 C: 1369 C: 1370 C: 1371 C: 1373 C: example.tld 1374 C: 1375 C: 1376 C: ns2.example.tld 1377 C: 1378 C: 1379 C: 1380 C: 1381 C: ns1.example.tld 1382 C: 1383 C: 1384 C: 1385 C: 1386 C: 1387 C: 1389 C: sunrise 1390 C: abc123 1391 C: 1392 C: 1393 C: ABC-12345 1394 C: 1395 C: 1397 This extension does not define any extension to the response of an 1398 domain command. After processing the command, the server 1399 replies with a standard EPP response as defined in the EPP domain 1400 name mapping [RFC5731]. 1402 3.5. EPP Command 1404 This extension defines additional elements to extend the EPP 1405 command to be used in conjunction with the domain name mapping. 1407 A client MUST NOT pass the extension on an EPP command to a 1408 server that does not support launch applications. A server that does 1409 not support launch applications during its launch phase MUST return 1410 an EPP error result code of 2102 when receiving an EPP 1411 command with the extension. 1413 Registry policies permitting, clients MAY withdraw an application by 1414 submitting an EPP command along with a 1415 element to indicate the application object to be deleted. The 1416 element contains the following child elements: 1418 The phase during which the application was submitted 1419 or is associated with. 1420 The application identifier for which the 1421 client wishes to delete. 1423 The following is an example domain command with the extension: 1426 C: 1427 C: 1428 C: 1429 C: 1430 C: 1432 C: example.tld 1433 C: 1434 C: 1435 C: 1436 C: 1438 C: sunrise 1439 C: abc123 1440 C: 1441 C: 1442 C: ABC-12345 1443 C: 1444 C: 1446 This extension does not define any extension to the response of a 1447 domain command. After processing the command, the server 1448 replies with a standard EPP response as defined in the EPP domain 1449 name mapping [RFC5731]. 1451 3.6. EPP Command 1453 This extension does not define any extension to the EPP 1454 command or response described in the EPP domain name mapping 1455 [RFC5731]. 1457 3.7. EPP Command 1459 This extension does not define any extension to the EPP 1460 command or response described in the EPP domain name mapping 1461 [RFC5731]. 1463 4. Formal Syntax 1465 One schema is presented here that is the EPP Launch Phase Mapping 1466 schema. 1468 The formal syntax presented here is a complete schema representation 1469 of the object mapping suitable for automated validation of EPP XML 1470 instances. The BEGIN and END tags are not part of the schema; they 1471 are used to note the beginning and ending of the schema for URI 1472 registration purposes. 1474 4.1. Launch Schema 1476 Copyright (c) 2012 IETF Trust and the persons identified as authors 1477 of the code. All rights reserved. 1479 Redistribution and use in source and binary forms, with or without 1480 modification, are permitted provided that the following conditions 1481 are met: 1483 o Redistributions of source code must retain the above copyright 1484 notice, this list of conditions and the following disclaimer. 1485 o Redistributions in binary form must reproduce the above copyright 1486 notice, this list of conditions and the following disclaimer in 1487 the documentation and/or other materials provided with the 1488 distribution. 1489 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1490 names of specific contributors, may be used to endorse or promote 1491 products derived from this software without specific prior written 1492 permission. 1494 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1495 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1496 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1497 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1498 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1499 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1500 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1501 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1502 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1503 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1504 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1506 BEGIN 1507 1508 1517 1520 1523 1526 1529 1530 1531 Extensible Provisioning Protocol v1.0 1532 domain name extension schema 1533 for the launch phase processing. 1534 1535 1537 1540 1541 1542 1543 1544 1546 1549 1550 1551 1552 1553 1554 1556 1559 1560 1561 1563 1569 1570 1571 1572 1573 1574 1575 1577 1580 1581 1582 1583 1584 1585 1586 1587 1588 1590 1593 1594 1595 1596 1597 1598 1599 1600 1601 1603 1604 1605 1607 1610 1611 1612 1613 1614 1616 1617 1618 1619 1621 1622 1623 1625 1628 1629 1630 1631 1632 1634 1637 1638 1639 1640 1641 1642 1643 1644 1645 1647 1648 1650 1653 1654 1655 1656 1658 1660 1661 1662 1663 1665 1669 1670 1671 1673 1675 1676 1678 1681 1682 1683 1684 1685 1687 1689 1691 1692 1694 1695 1696 1698 1701 1702 1703 1704 1705 1706 1708 1711 1712 1713 1714 1715 1716 1717 1719 1722 1723 1724 1725 1726 1728 1730 1734 1735 1736 1737 1738 1739 1740 1743 1744 1745 1746 1749 1750 1752 1754 1757 1758 1759 1761 1764 1765 1766 1767 1769 1770 1772 1773 1774 1775 1777 1778 1780 1781 1782 1783 1785 1786 1787 1788 1789 1790 1791 1793 1794 1795 1797 1800 1801 1802 1803 1806 1808 1810 1811 1813 1814 END 1816 5. Acknowledgements 1818 The authors wish to acknowledge the efforts of the leading 1819 participants of the Community TMCH Model that led to many of the 1820 changes to this document, which include Chris Wright, Jeff Neuman, 1821 Jeff Eckhaus, and Will Shorter. 1823 Special suggestions that have been incorporated into this document 1824 were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Jan 1825 Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus Malorny, 1826 Alexander Mayrhofer, Patrick Mevzek, James Mitchell, Francisco 1827 Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung Tran, Ulrich 1828 Wisser and Sharon Wodjenski. 1830 6. Change History 1831 6.1. Change from 00 to 01 1833 1. Changed to use camel case for the XML elements. 1834 2. Replaced "cancelled" status to "rejected" status. 1835 3. Added the child elements of the element. 1836 4. Removed the XML schema and replaced with "[TBD]". 1838 6.2. Change from 01 to 02 1840 1. Added support for both the ICANN and ARI/Neustar TMCH models. 1841 2. Changed the namespace URI and prefix to use "launch" instead of 1842 "launchphase". 1843 3. Added definition of multiple claim validation models. 1844 4. Added the and 1845 elements. 1846 5. Added support for Claims Info Command 1848 6.3. Change from 02 to 03 1850 1. Removed XSI namespace per Keith Gaughan's suggestion on the 1851 provreg list. 1852 2. Added extensibility to the launch:status element and added the 1853 pendingAuction status per Trung Tran's feedback on the provreg 1854 list. 1855 3. Added support for the Claims Check Command, updated the location 1856 and contents of the signedNotice, and replaced most references of 1857 Claim to Mark based on the work being done on the ARI/Neustar 1858 launch model. 1860 6.4. Change from 03 to 04 1862 1. Removed references to the ICANN model. 1863 2. Removed support for the Claims Info Command. 1864 3. Removed use of the signedClaim. 1865 4. Revised the method for referring to the signedClaim from the XML 1866 Signature using the IDREF URI. 1867 5. Split the launch-1.0.xsd into three XML schemas including launch- 1868 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 1869 6. Split the "claims" launch phase to the "claims1" and "claims2" 1870 launch phases. 1871 7. Added support for the encodedSignedMark with base64 encoded 1872 signedMark. 1873 8. Changed the elements in the createNoticeType to include the 1874 noticeID, timestamp, and the source elements. 1875 9. Added the class and effectiveDate elements to mark. 1877 6.5. Change from 04 to 05 1879 1. Removed reference to in the example. 1880 2. Incorporated feedback from Bernhard Reutner-Fischer on the 1881 provreg mail list. 1882 3. Added missing launch XML prefix to applicationIDType reference in 1883 the idContainerType of the Launch Schema. 1884 4. Added missing description of the element in the element. 1886 5. Updated note on replication of the EPP contact mapping elements 1887 in the Mark Contact section. 1889 6.6. Change from 05 to 06 1891 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 1892 replaced with reference to draft-lozano-smd, that contains the 1893 definition for the mark, signed marked, and encoded signed mark. 1894 2. Split the into and 1895 based on feedback from Trung Tran. 1896 3. Added the "includeMark" optional attribute to the 1897 element to enable the client to request whether or not to include 1898 the mark in the info response. 1899 4. Fixed state diagram to remove redundant transition from "invalid" 1900 to "rejected"; thanks Klaus Malorny. 1902 6.7. Change from 06 to 07 1904 1. Proof-read grammar and spelling. 1905 2. Changed "pendingAuction" status to "pendingAllocation", changed 1906 "pending" to "pendingValidation" status, per proposal from Trung 1907 Tran and seconded by Rubens Kuhl. 1908 3. Added text related to the use of RFC 5731 pendingCreate to the 1909 Application Identifier section. 1910 4. Added the Poll Messaging section to define the use of poll 1911 messaging for intermediate state transitions and pending action 1912 poll messaging for final state transitions. 1914 6.8. Change from 07 to 08 1916 1. Added support for use of the launch statuses and poll messaging 1917 for Launch Registrations based on feedback from Sharon Wodjenski 1918 and Trung Tran. 1919 2. Incorporated changes based on updates or clarifications in 1920 draft-lozano-tmch-func-spec-01, which include: 1921 1. Removed the unused element. 1922 2. Removed the element. 1924 3. Added the element based on the required 1925 element. 1927 6.9. Change from 08 to 09 1929 1. Made element optional in to allow 1930 passing just the in per request 1931 from Ben Levac. 1932 2. Added optional "type" attribute in to enable the 1933 client to explicitly define the desired type of object 1934 (application or registration) to create to all forms of the 1935 create extension. 1936 3. Added text that the server SHOULD validate the 1937 element in the Launch Phases section. 1938 4. Add the "General Create Form" to the create command extension to 1939 support the request from Ben Levac. 1940 5. Updated the text for the Poll Messaging section based on feedback 1941 from Klaus Malorny. 1942 6. Replaced the "claims1" and "claims2" phases with the "claims" 1943 phase based on discussion on the provreg list. 1944 7. Added support for a mixed create model (Sunrise Create Model and 1945 Claims Create Model), where a trademark (encoded signed mark, 1946 etc.) and notice can be passed, based on a request from James 1947 Mitchell. 1948 8. Added text for the handling of the overlapping "claims" and 1949 "landrush" launch phases. 1950 9. Added support for two check forms (claims check form and 1951 availability check form) based on a request from James Mitchell. 1952 The availability check form was based on the text in 1953 draft-rbp-application-epp-mapping. 1955 6.10. Change from 09 to 10 1957 1. Changed noticeIDType from base64Binary to token to be compatible 1958 with draft-lozano-tmch-func-spec-05. 1959 2. Changed codeType from base64Binary to token to be more generic. 1960 3. Updated based on feedback from Alexander Mayrhofer, which 1961 include: 1962 1. Changed "extension to the domain name extension" to 1963 "extension to the domain name mapping". 1964 2. Changed use of 2004 return code to 2306 return code when 1965 phase passed mismatches active phase and sub-phase. 1966 3. Changed description of "allocated" and "rejected" statuses. 1967 4. Moved sentence on a synchronous command 1968 without the use of an intermediate application, then an 1969 Application Identifier MAY not be needed to the Application 1970 Identifier section. 1972 5. Restructured the Mark Validation Models section to include 1973 the " element" sub-section, the " element" sub-section, and the Digital Signature sub- 1975 section. 1976 6. Changed "Registries may" to "Registries MAY". 1977 7. Changed "extensed" to "extended" in "Availability Check 1978 Form" section. 1979 8. Broke the mix of create forms in the "EPP Command" 1980 section to a fourth "Mixed Create Form" with its own sub- 1981 section. 1982 9. Removed "displayed or" from "displayed or accepted" in the 1983 description. 1984 10. Replaced "given domain name is supported" with "given domain 1985 name are supported" in the "Create Response" section. 1986 11. Changed the reference of 2303 (object does not exist) in the 1987 "Security Considerations" section to 2201 (authorization 1988 error). 1989 12. Added arrow from "invalid" status to "pendingValidation" 1990 status and "pendingAllocation" status to "rejected" status 1991 in the State Transition Diagram. 1992 4. Added the "C:" and "S:" example prefixes and related text in the 1993 "Conventions Used in This Document" section. 1995 6.11. Change from 10 to 11 1997 1. Moved the claims check response element under 1998 the element instead of the element based on 1999 the request from Francisco Obispo. 2001 6.12. Change from 11 to 12 2003 1. Added support for multiple validator identifiers for claims 2004 notices and marks based on a request and text provided by Mike 2005 O'Connell. 2006 2. Removed domain:exDate element from example in section 3.3.5 based 2007 on a request from Seth Goldman on the provreg list. 2008 3. Added clarifying text for clients not passing the launch 2009 extension on update and delete commands to servers that do not 2010 support launch applications based on a request from Sharon 2011 Wodjenski on the provreg list. 2013 7. IANA Considerations 2015 This document uses URNs to describe XML namespaces and XML schemas 2016 conforming to a registry mechanism described in [RFC3688]. Three URI 2017 assignments have been registered by the IANA. 2019 Registration request for the Launch namespace: 2021 URI: urn:ietf:params:xml:ns:launch-1.0 2022 Registrant Contact: See the "Author's Address" section of this 2023 document. 2024 XML: None. Namespace URIs do not represent an XML specification. 2026 8. Security Considerations 2028 The mapping extensions described in this document do not provide any 2029 security services beyond those described by EPP [RFC5730], the EPP 2030 domain name mapping [RFC5731], and protocol layers used by EPP. The 2031 security considerations described in these other specifications apply 2032 to this specification as well. 2034 Updates to, and deletion of an application object must be restricted 2035 to clients authorized to perform the said operation on the object. 2037 As information contained within an application, or even the mere fact 2038 that an application exists may be confidential. Any attempt to 2039 operate on an application object by an unauthorized client MUST be 2040 rejected with an EPP 2201 (authorization error) return code. Server 2041 policy may allow operation with filtered output by clients 2042 other than the sponsoring client, in which case the 2043 and response SHOULD be filtered to include only 2044 fields that are publicly accessible. 2046 9. Normative References 2048 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2049 Requirement Levels", BCP 14, RFC 2119, March 1997. 2051 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2052 January 2004. 2054 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2055 STD 69, RFC 5730, August 2009. 2057 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2058 Domain Name Mapping", STD 69, RFC 5731, August 2009. 2060 [draft-lozano-smd] 2061 Lozano, G., "Mark and Signed Mark Objects Mapping". 2063 [1] 2065 Authors' Addresses 2067 James Gould 2068 VeriSign, Inc. 2069 12061 Bluemont Way 2070 Reston, VA 20190 2071 US 2073 Email: jgould@verisign.com 2074 URI: http://www.verisigninc.com 2076 Wil Tan 2077 Cloud Registry 2078 Suite 32 Seabridge House 2079 377 Kent St 2080 Sydney, NSW 2000 2081 AU 2083 Phone: +61 414 710899 2084 Email: wil@cloudregistry.net 2085 URI: http://www.cloudregistry.net 2087 Gavin Brown 2088 CentralNic Ltd 2089 35-39 Mooregate 2090 London, England EC2R 6AR 2091 GB 2093 Phone: +44 20 33 88 0600 2094 Email: gavin.brown@centralnic.com 2095 URI: https://www.centralnic.com