idnits 2.17.1 draft-tan-epp-launchphase-11.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 (May 17, 2013) is 3997 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: November 18, 2013 Cloud Registry 6 G. Brown 7 CentralNic Ltd 8 May 17, 2013 10 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) 11 draft-tan-epp-launchphase-11 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 November 18, 2013. 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. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 5 59 2.3. Status Values . . . . . . . . . . . . . . . . . . . . . . 6 60 2.3.1. State Transition . . . . . . . . . . . . . . . . . . . 8 61 2.4. Poll Messaging . . . . . . . . . . . . . . . . . . . . . . 9 62 2.5. Mark Validation Models . . . . . . . . . . . . . . . . . . 12 63 2.5.1. element . . . . . . . . . . . . . . 13 64 2.5.2. element . . . . . . . . . . . . . . . . . 14 65 2.5.3. Digital Signature . . . . . . . . . . . . . . . . . . 14 66 2.5.3.1. element . . . . . . . . . . . . . 14 67 2.5.3.2. element . . . . . . . . . 14 68 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 14 69 3.1. EPP Command . . . . . . . . . . . . . . . . . . . 15 70 3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 15 71 3.1.2. Availability Check Form . . . . . . . . . . . . . . . 17 72 3.2. EPP Command . . . . . . . . . . . . . . . . . . . . 18 73 3.3. EPP Command . . . . . . . . . . . . . . . . . . . 22 74 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 22 75 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . . 28 76 3.3.3. General Create Form . . . . . . . . . . . . . . . . . 30 77 3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 31 78 3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 32 79 3.4. EPP Command . . . . . . . . . . . . . . . . . . . 33 80 3.5. EPP Command . . . . . . . . . . . . . . . . . . . 35 81 3.6. EPP Command . . . . . . . . . . . . . . . . . . . 36 82 3.7. EPP Command . . . . . . . . . . . . . . . . . . 36 83 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 36 84 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 36 85 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43 86 6. Change History . . . . . . . . . . . . . . . . . . . . . . . . 43 87 6.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . . 43 88 6.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . . 43 89 6.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . . 43 90 6.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . . 44 91 6.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . . 44 92 6.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . . 44 93 6.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . . 44 94 6.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . . 45 95 6.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . . 45 96 6.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . . 46 97 6.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . . 46 98 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 99 8. Security Considerations . . . . . . . . . . . . . . . . . . . 47 100 9. Normative References . . . . . . . . . . . . . . . . . . . . . 47 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 48 103 1. Introduction 105 This document describes an extension mapping for version 1.0 of the 106 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 107 specifies a flexible schema that can be used to implement several 108 common use cases related to the provisioning and management of domain 109 name registrations and applications during the launch of a domain 110 name registry. 112 It is typical for domain registries to operate in special modes 113 during their initial launch to facilitate allocation of domain names, 114 often according to special rules. This document uses the term 115 "launch phase" and the shorter form "launch" to refer to such a 116 period. 118 The EPP domain name mapping [RFC5731] is designed for the steady- 119 state operation of a registry. During a launch period, the model in 120 place may be different from what is defined in the EPP domain name 121 mapping [RFC5731]. For example, registries often accept multiple 122 applications for the same domain name during the "Sunrise" launch 123 phase, referred to as a Launch Application. A Launch Registration 124 refers to a registration made during a launch phase when the server 125 uses a "first-come, first-served" model. Even in a "first-come, 126 first-served" model, additional steps and information might be 127 required, such as trademark information. In addition, the TMCH 128 Functional Specification [1] defines a registry interface for the 129 Trademark Claims or "claims" launch phase that includes support for 130 presenting a Trademark Claims Notice to the Registrant. This 131 document proposes an extension to the domain name mapping in order to 132 provide a uniform interface for the management of Launch Applications 133 and Launch Registrations in launch phases. 135 1.1. Conventions Used in This Document 137 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 138 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 139 document are to be interpreted as described in RFC 2119 [RFC2119]. 141 XML is case sensitive. Unless stated otherwise, XML specifications 142 and examples provided in this document MUST be interpreted in the 143 character case presented in order to develop a conforming 144 implementation. 146 In examples, "C:" represents lines sent by a protocol client and "S:" 147 represents lines returned by a protocol server. Indentation and 148 white space in examples are provided only to illustrate element 149 relationships and are not a REQUIRED feature of this protocol. 151 "launch-1.0" is used as an abbreviation for 152 "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix 153 "launch" is used, but implementations MUST NOT depend on it and 154 instead employ a proper namespace-aware XML parser and serializer to 155 interpret and output the XML documents. 157 "signedMark-1.0" is used as an abbreviation for 158 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in 159 [draft-lozano-smd]. The XML namespace prefix "smd" is used, but 160 implementations MUST NOT depend on it and instead employ a proper 161 namespace-aware XML parser and serializer to interpret and output the 162 XML documents. 164 "mark-1.0" is used as an abbreviation for 165 "urn:ietf:params:xml:ns:mark-1.0" that is defined in 166 [draft-lozano-smd]. The XML namespace prefix "mark" is used, but 167 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 2. Object Attributes 173 This extension adds additional elements to the EPP domain name 174 mapping [RFC5731]. Only those new elements are described here. 176 2.1. Application Identifier 178 Servers MAY allow multiple applications, referred to as a Launch 179 Application, of the same domain name during its launch phase 180 operations. Upon receiving a valid request to create a Launch 181 Application, the server MUST create an application object 182 corresponding to the request, assign an application identifier for 183 the Launch Application, set the [RFC5731] pendingCreate status, and 184 return the application identifier to the client with the element. In order to facilitate correlation, all 186 subsequent launch operations on the Launch Application MUST be 187 qualified by the previously assigned application identifier using the 188 element. 190 If the command processes a request synchronously 191 without the use of an intermediate Launch Application, then an 192 application identifier MAY not be needed. 194 2.2. Launch Phases 196 The server MAY support multiple launch phases sequentially or 197 simultaneously. The element MUST be included by the 198 client to define the target launch phase of the command. The server 199 SHOULD validate the phase and MAY validate the sub-phase of the 200 element against the active phase and OPTIONAL sub- 201 phase of the server on a create command, and return an EPP error 202 result code of 2306 if there is a mismatch. 204 The following launch phase values are defined: 205 sunrise The phase during which trademark holders can submit 206 registrations or applications with trademark information that can 207 be validated by the server. 208 landrush A post-Sunrise phase when non-trademark holders are allowed 209 to register domain names with steps taken to address a large 210 volume of initial registrations. 211 claims The Trademark Claims phase, as defined in the TMCH Functional 212 Specification [1], in which a Claims Notice must be displayed to a 213 prospective registrant of a domain name that matches trademarks. 214 open A post-launch phase that is also referred to as "steady state". 215 Servers MAY require additional trademark protection during this 216 phase. 217 custom A custom server launch phase that is defined using the "name" 218 attribute. 220 For extensibility, the element includes an OPTIONAL 221 "name" attribute that can define a sub-phase or the full name of the 222 phase when the element has the "custom" value. For 223 example, the "claims" launch phase could have two sub-phases that 224 include "landrush" and "open". 226 Launch phases MAY overlap to support the "claims" launch phase, 227 defined in the TMCH Functional Specification [1], and to support a 228 traditional "landrush" launch phase. The overlap of the "claims" and 229 "landrush" launch phases SHOULD be handled by setting "claims" as the 230 value and setting "landrush" as the sub-phase with the 231 "name" attribute. For example, the element SHOULD be 232 claims. 234 2.3. Status Values 236 A Launch Application or Launch Registration object MAY have a launch 237 status value. The element is used to convey the 238 launch status pertaining to the object, beyond what is specified in 239 the object mapping. A Launch Application or Launch Registration MUST 240 set the [RFC5731] "pendingCreate" status if a launch status is 241 supported and the launch status is not one of the final statuses, 242 including the "allocated" and "rejected" statuses. 244 The following status values are defined using the required "s" 245 attribute: 247 pendingValidation: The initial state of a newly-created application 248 or registration object. The application or registration requires 249 validation, but the validation process has not yet completed. 250 validated: The application or registration meets relevant registry 251 rules. 252 invalid: The application or registration does not validate according 253 to registry rules. Server policies permitting, it may transition 254 back into "pendingValidation" for revalidation, after 255 modifications are made to ostensibly correct attributes that 256 caused the validation failure. 257 pendingAllocation: The allocation of the application or registration 258 is pending based on the results of some out-of-band process (for 259 example, an auction). 260 allocated: The object corresponding to the application or 261 registration has been provisioned. Is a possible end state of an 262 application or registration object. 263 rejected: The application or registration object was not 264 provisioned. Is a possible end state of an application or 265 registration object. 266 custom: A custom status that is defined using the "name" attribute. 268 Each status value MAY be accompanied by a string of human-readable 269 text that describes the rationale for the status applied to the 270 object. The OPTIONAL "lang" attribute MAY be present to identify the 271 language if the negotiated value is something other than the default 272 value of "en" (English). 274 For extensibility the element includes an OPTIONAL 275 "name" attribute that can define a sub-status or the full name of the 276 status when the status value is "custom". The server SHOULD NOT use 277 the "custom" status value. 279 Certain status values MAY be combined. For example, an application 280 or registration may be both "invalid" and "rejected". Additionally, 281 certain statuses MAY be skipped. For example, an application or 282 registration MAY immediately start at the "allocated" status or an 283 application or registration MAY skip the "pendingAllocation" status. 284 If the launch phase does not require validation of a request, an 285 application or registration MAY immediately skip to 286 "pendingAllocation". 288 2.3.1. State Transition 290 | request 291 | 292 | +--------------------------+ 293 | | | 294 v v | 295 +-------------------+ | 296 | | | 297 | pendingValidation +--------------+ | 298 | | | | 299 +---------+---------+ | | 300 | | | 301 | | | 302 v v | 303 +-----------+ +---------+ | 304 | | | | | 305 | validated | | invalid +--+ 306 | | | | 307 +-----+-----+ +----+----+ 308 | | 309 | | 310 v | 311 +-------------------+ | 312 | | | 313 | pendingAllocation +-----------+ | 314 | | | | 315 +---------+---------+ | | 316 | | | 317 | | | 318 | | | 319 | | | 320 | | | 321 v v v 322 +---------+ +--------+ 323 / \ / \ 324 | allocated | | rejected | 325 \ / \ / 326 +---------+ +--------+ 328 Figure 1 330 2.4. Poll Messaging 332 A Launch Application MUST and a Launch Registration MAY be handled as 333 a domain name of [RFC5731] in "pendingCreate" status, with the launch 334 status values defined in Section 2.3. As a Launch Application or 335 Launch Registration transitions between the status values defined in 336 Section 2.3, the server SHOULD insert poll messages, per [RFC5730], 337 for the applicable intermediate statuses, including the 338 "pendingValidation", "validated", "pendingAllocation, and "invalid" 339 statuses, using the element with the extension. The element MAY contain non- 341 mandatory information, like contact and name server information. 342 Also, further extensions that would normally be included in the 343 response of a command, per [RFC5731], MAY be included. 344 For the final statuses, including the "allocated" and "rejected" 345 statuses, the server MUST insert a poll message, per 346 [RFC5731], with the extension. 348 The following is an example poll message for a Launch Application 349 that has transitioned to the "pendingAllocation" state. 351 S: 352 S: 353 S: 354 S: 355 S: Command completed successfully; ack to dequeue 356 S: 357 S: 358 S: 2013-04-04T22:01:00.0Z 359 S: Application pendingAllocation. 360 S: 361 S: 362 S: 364 S: example.tld 365 S: ... 366 S: 367 S: 368 S: 369 S: 371 S: sunrise 372 S: abc123 373 S: 374 S: 375 S: 376 S: 377 S: ABC-12345 378 S: 54322-XYZ 379 S: 380 S: 381 S: 382 The following is an example poll message for an 383 "allocated" Launch Application. 385 S: 386 S: 387 S: 388 S: 389 S: Command completed successfully; ack to dequeue 390 S: 391 S: 392 S: 2013-04-04T22:01:00.0Z 393 S: Application successfully allocated. 394 S: 395 S: 396 S: 398 S: example.tld 399 S: 400 S: ABC-12345 401 S: 54321-XYZ 402 S: 403 S: 2013-04-04T22:00:00.0Z 404 S: 405 S: 406 S: 407 S: 409 S: sunrise 410 S: abc123 411 S: 412 S: 413 S: 414 S: 415 S: BCD-23456 416 S: 65432-WXY 417 S: 418 S: 419 S: 420 The following is an example poll message for an 421 "allocated" Launch Registration. 423 S: 424 S: 425 S: 426 S: 427 S: Command completed successfully; ack to dequeue 428 S: 429 S: 430 S: 2013-04-04T22:01:00.0Z 431 S: Registration successfully allocated. 432 S: 433 S: 434 S: 436 S: example.tld 437 S: 438 S: ABC-12345 439 S: 54321-XYZ 440 S: 441 S: 2013-04-04T22:00:00.0Z 442 S: 443 S: 444 S: 445 S: 447 S: sunrise 448 S: 449 S: 450 S: 451 S: 452 S: BCD-23456 453 S: 65432-WXY 454 S: 455 S: 456 S: 458 2.5. Mark Validation Models 460 A server MUST support at least one of the following models for 461 validating trademark information: 463 code Use of a mark code by itself to validate that the mark matches 464 the domain name. This model is supported using the element with just the element. 467 mark The mark information is passed without any other validation 468 element. The server will use some custom form of validation to 469 validate that the mark information is authentic. This model is 470 supported using the element with just the (Section 2.5.2) element. 472 code with mark: A code is used along with the mark information by 473 the server to validate the mark utilizing an external party. The 474 code represents some form of secret that matches the mark 475 information passed. This model is supported using the element that contains both the and the 477 (Section 2.5.2) elements. 478 signed mark: The mark information is digitally signed as described 479 in the Digital Signature (Section 2.5.3) section. The digital 480 signature can be directly validated by the server using the public 481 key of the external party that created the signed mark using its 482 private key. This model is supported using the 483 (Section 2.5.3.1) and (Section 2.5.3.2) 484 elements. 486 More than one , (Section 2.5.3.1), 487 or (Section 2.5.3.2) element MAY be 488 specified. The maximum number of marks per domain name is up to 489 server policy. 491 2.5.1. element 493 The element that is used by the "code", "mark", and 494 "code with mark" validation models, has the following child elements: 496 : OPTIONAL mark code used to validate the 497 (Section 2.5.2) information. The mark code is be a mark-specific 498 secret that the server can verify against a third party. 499 : OPTIONAL mark information with child elements defined 500 in the Mark (Section 2.5.2) section. 502 The following is an example element with both a 503 and (Section 2.5.2) element. 505 506 49FD46E6C4B45C55D4AC 507 508 ... 509 510 512 2.5.2. element 514 A element describes an applicant's prior right to a given 515 domain name that is used with the "mark", "mark with code", and the 516 "signed mark" validation models. The element is defined 517 in [draft-lozano-smd]. A new mark format can be supported by 518 creating a new XML schema for the mark that has an element that 519 substitutes for the element from 520 [draft-lozano-smd]. 522 2.5.3. Digital Signature 524 Digital signatures MAY be used by the server to validate either the 525 mark information, when using the "signed mark" validation model with 526 the (Section 2.5.3.1) element or the (Section 2.5.3.2) element. 529 2.5.3.1. element 531 The element contains the digitally signed mark 532 information. The element is defined in 533 [draft-lozano-smd]. A new signed mark format can be supported by 534 creating a new XML schema for the signed mark that has an element 535 that substitutes for the element from 536 [draft-lozano-smd]. 538 2.5.3.2. element 540 The element contains an encoded form of the 541 digitally signed (Section 2.5.3.1) element. The 542 element is defined in [draft-lozano-smd]. A 543 new encoded signed mark format can be supported by creating a new XML 544 schema for the encoded signed mark that has an element that 545 substitutes for the element from 546 [draft-lozano-smd]. 548 3. EPP Command Mapping 550 A detailed description of the EPP syntax and semantics can be found 551 in the EPP core protocol specification [RFC5730]. The command 552 mappings described here are specifically for use in the Launch Phase 553 Extension. 555 This mapping is designed to be flexible, requiring only a minimum set 556 of required elements. 558 While it is meant to serve several use cases, it does not prescribe 559 any interpretation by the client or server. Such processing is 560 typically highly policy-dependent and therefore specific to 561 implementations. 563 Operations on application objects are done via one or more of the 564 existing EPP verbs defined in the EPP domain name mapping [RFC5731]. 565 Registries MAY choose to support a subset of the operations. 567 3.1. EPP Command 569 There are two forms of the extension to the EPP command: the 570 Claims Check Form (Section 3.1.1) and the Availability Check Form 571 (Section 3.1.2). The element "type" attribute defines 572 the form, with the value of "claims" for the Claims Check Form 573 (Section 3.1.1) and with the value of "avail" for the Availability 574 Check Form (Section 3.1.2). The default value of the "type" 575 attribute is "claims". The forms supported by the server is 576 determined by server policy. The server MUST return an EPP error 577 result code of 2307 if it receives a check form that is not 578 supported. 580 3.1.1. Claims Check Form 582 The Claims Check Form defines a new command called the Claims Check 583 Command that is used to determine whether or not there are any 584 matching trademarks, in the specified launch phase, for each domain 585 name passed in the command. The availability check information 586 defined in the EPP domain name mapping [RFC5731] MUST NOT be returned 587 for the Claims Check Command. This form is the default form and MAY 588 be explicitly identified by setting the "type" 589 attribute to "claims". 591 Instead of returning whether the domain name is available, the Claims 592 Check Command will return whether or not at least one matching 593 trademark exists for the domain name. If there is at least one 594 matching trademark that exists for the domain name, a element is returned. The client may then use the value of 596 the element to obtain information needed to 597 generate the trademark Claims Notice from a third-party trademark 598 validator such as the Trademark Clearinghouse (TMCH). The third 599 party trademark validator should also return a unique notice 600 identifier that can be passed in the element of the 601 extension to the Create Command (Section 3.3). 603 The elements in the EPP command of EPP domain 604 name mapping [RFC5731] define the domain names to check for matching 605 trademarks. The element contains the following child 606 elements: 608 The launch phase that SHOULD be "claims". 610 Example Claims Check command using the domain command and the 611 extension with the "type" explicitly set to "claims", 612 to determine if "example1.tld" and "example2.tld" have any matching 613 trademarks during the "claims" launch phase: 615 C: 616 C: 617 C: 618 C: 619 C: 621 C: example1.tld 622 C: example2.tld 623 C: 624 C: 625 C: 626 C: 629 C: claims 630 C: 631 C: 632 C: ABC-12345 633 C: 634 C: 636 If the command has been processed successfully, the EPP 637 MUST contain an element that 638 identifies the launch namespace. The element 639 contains the following child elements: 641 The launch phase that SHOULD be "claims". 642 One or more elements that contain the 643 following child elements: 645 Contains the fully qualified name of the queried 646 domain name. This element MUST contain an "exists" attribute 647 whose value indicates if a matching trademark exists for the 648 domain name. A value of "1" (or "true") means that a 649 matching trademark does exist for the claims launch phase. A 650 value of "0" (or "false") means that a matching trademark 651 does not exist. 653 An OPTIONAL claim key that MAY be passed to a 654 third-party trademark validator such as the Trademark 655 Clearinghouse (TMCH) for querying the information needed to 656 generate a Trademark Claims Notice. The is 657 used as the key for the query in place of the domain name to 658 securely query the service without using a well-known value 659 like a domain name. 661 Example Claims Check response when no matching trademarks are found 662 for the domain name example1.tld and matching trademarks are found 663 for the domain name example2.tld for the "claims" launch phase: 665 S: 666 S: 667 S: 668 S: 669 S: Command completed successfully 670 S: 671 S: 672 S: 674 S: claims 675 S: 676 S: example1.tld 677 S: 678 S: 679 S: example2.tld 680 S: 681 S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 682 S: 683 S: 684 S: 685 S: 686 S: 687 S: ABC-12345 688 S: 54321-XYZ 689 S: 690 S: 691 S: 693 3.1.2. Availability Check Form 695 The Availability Check Form defines additional elements to extend the 696 EPP command described in the EPP domain name mapping 697 [RFC5731]. No additional elements are defined for the EPP 698 response. This form MUST be identified by setting the 699 "type" attribute to "avail". 701 The EPP command is used to determine if an object can be 702 provisioned within a repository. Domain names may be made available 703 only in unique launch phases, whilst remaining unavailable for 704 concurrent launch phases. In addition to the elements expressed in 705 the , the command is extended with the 706 element that contains the following child elements: 708 The launch phase to which domain name availability 709 should be determined. 711 Example Availability Check Form command using the domain 712 command and the extension with the "type" set to 713 "avail", to determine the availability of two domain names in the 714 "idn-release" custom launch phase: 716 C: 717 C: 718 C: 719 C: 720 C: 722 C: example1.tld 723 C: example2.tld 724 C: 725 C: 726 C: 727 C: 730 C: custom 731 C: 732 C: 733 C: ABC-12345 734 C: 735 C: 737 The Availability Check Form does not define any extension to the 738 response of an domain command. After processing the command, 739 the server replies with a standard EPP response as defined in the EPP 740 domain name mapping [RFC5731]. 742 3.2. EPP Command 744 This extension defines additional elements to extend the EPP 745 command and response to be used in conjunction with the EPP domain 746 name mapping [RFC5731]. 748 The EPP command is used to retrieve information for a launch 749 phase registration or application. The Application Identifier 750 (Section 2.1) returned in the element of the create 751 response (Section 3.3) is used for retrieving information for a 752 Launch Application. A element is sent along with the 753 regular domain command. The element includes an 754 OPTIONAL "includeMark" boolean attribute, with a default value of 755 "false", to indicate whether or not to include the mark in the 756 response. The element contains the following child 757 elements: 759 The phase during which the application or 760 registration was submitted or is associated with. Server policy 761 defines the phases that are supported. 762 OPTIONAL application identifier of the Launch 763 Application. 765 Example domain command with the extension to 766 retrieve information for the sunrise application for example.tld and 767 application identifier "abc123": 769 C: 770 C: 771 C: 772 C: 773 C: 775 C: example.tld 776 C: 777 C: 778 C: 779 C: 782 C: sunrise 783 C: abc123 784 C: 785 C: 786 C: ABC-12345 787 C: 788 C: 789 Example domain command with the extension to 790 retrieve information for the sunrise registration for example.tld: 792 C: 793 C: 794 C: 795 C: 796 C: 798 C: example.tld 799 C: 800 C: 801 C: 802 C: 804 C: sunrise 805 C: 806 C: 807 C: ABC-12345 808 C: 809 C: 811 If the query was successful, the server replies with a element along with the regular EPP . The contains the following child elements: 815 The phase during which the application was submitted, 816 or is associated with, that matches the associated command 817 . 818 OPTIONAL Application Identifier of the Launch 819 Application. 820 OPTIONAL status of the Launch Application using one 821 of the supported status values (Section 2.3). 822 Zero or more (Section 2.5.2) elements. 824 Example domain response using the extension 825 with the mark information: 827 S: 828 S: 829 S: 830 S: 831 S: Command completed successfully 832 S: 833 S: 834 S: 836 S: example.tld 837 S: EXAMPLE1-REP 838 S: 839 S: jd1234 840 S: sh8013 841 S: sh8013 842 S: ClientX 843 S: ClientY 844 S: 2012-04-03T22:00:00.0Z 845 S: 846 S: 2fooBAR 847 S: 848 S: 849 S: 850 S: 851 S: 853 S: sunrise 854 S: abc123 855 S: 856 S: 858 S: ... 859 S: 860 S: 861 S: 862 S: 863 S: ABC-12345 864 S: 54321-XYZ 865 S: 866 S: 867 S: 869 3.3. EPP Command 871 There are four forms of the extension to the EPP command 872 that include the Sunrise Create Form (Section 3.3.1), the Claims 873 Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), 874 and the Mixed Create Form (Section 3.3.4). The form is dependent on 875 the supported launch phases (Section 2.2) as defined below. 877 sunrise The EPP command with the "sunrise" launch phase is 878 used to submit a registration with trademark information that can 879 be verified by the server with the value. The 880 Sunrise Create Form (Section 3.3.1) is used for the "sunrise" 881 launch phase. 882 landrush The EPP command with the "landrush" launch phase 883 MAY use the General Create Form (Section 3.3.3) to explictly 884 specify the phase and optionally define the expected type of 885 object to create. 886 claims The EPP command with the "claims" launch phase is 887 used to pass the information associated with the presentation and 888 acceptance of the Claims Notice. The Claims Create Form 889 (Section 3.3.2) is used and the General Create Form 890 (Section 3.3.3) MAY be used for the "claims" launch phase. 891 open The EPP command with the "open" launch phase is 892 undefined but the form supported is up to server policy. 893 custom The EPP command with the "custom" launch phase is 894 undefined but the form supported is up to server policy. 896 3.3.1. Sunrise Create Form 898 The Sunrise Create Form of the extension to the EPP domain name 899 mapping [RFC5731] includes the verifiable trademark information that 900 the server uses to match against the domain name to authorize the 901 domain create. A server MUST support one of four models in Claim 902 Validation Models (Section 2.5) to verify the trademark information 903 passed by the client. 905 A element is sent along with the regular 906 domain command. The element has an OPTIONAL "type" 907 attribute that defines the expected type of object ("application" or 908 "registration") to create. The server SHOULD validate the "type" 909 attribute, when passed, against the type of object that will be 910 created. The element contains the following child 911 elements: 913 The identifier for the launch phase. 914 or or 915 Zero or more elements. The 916 child elements are defined in the element (Section 2.5.1) section. 918 Zero or more elements. The 919 child elements are defined in the element (Section 2.5.3.1) section. 921 Zero or more 922 elements. The child elements are 923 defined in the element 924 (Section 2.5.3.2) section. 926 The following is an example domain command using the 927 extension, following the "code" validation model, 928 with multiple sunrise codes: 930 C: 931 C: 932 C: 933 C: 934 C: 936 C: example.tld 937 C: jd1234 938 C: sh8013 939 C: sh8013 940 C: 941 C: 2fooBAR 942 C: 943 C: 944 C: 945 C: 946 C: 948 C: sunrise 949 C: 950 C: 49FD46E6C4B45C55D4AC 951 C: 952 C: 953 C: 49FD46E6C4B45C55D4AD 954 C: 955 C: 956 C: 49FD46E6C4B45C55D4AE 957 C: 958 C: 959 C: 960 C: ABC-12345 961 C: 962 C: 963 The following is an example domain command using the 964 extension, following the "mark" validation model, 965 with the mark information: 967 C: 968 C: 969 C: 970 C: 971 C: 973 C: exampleone.tld 974 C: jd1234 975 C: sh8013 976 C: sh8013 977 C: 978 C: 2fooBAR 979 C: 980 C: 981 C: 982 C: 983 C: 985 C: sunrise 986 C: 987 C: 989 C: ... 990 C: 991 C: 992 C: 993 C: 994 C: ABC-12345 995 C: 996 C: 997 The following is an example domain command using the 998 extension, following the "code with mark" validation 999 model, with a code and mark information: 1001 C: 1002 C: 1003 C: 1004 C: 1005 C: 1007 C: example.tld 1008 C: jd1234 1009 C: sh8013 1010 C: sh8013 1011 C: 1012 C: 2fooBAR 1013 C: 1014 C: 1015 C: 1016 C: 1017 C: 1019 C: sunrise 1020 C: 1021 C: 49FD46E6C4B45C55D4AC 1022 C: 1024 C: ... 1025 C: 1026 C: 1027 C: 1028 C: 1029 C: ABC-12345 1030 C: 1031 C: 1032 The following is an example domain command using the 1033 extension, following the "signed mark" validation 1034 model, with the signed mark information for a sunrise application: 1036 C: 1037 C: 1038 C: 1039 C: 1040 C: 1042 C: exampleone.tld 1043 C: jd1234 1044 C: sh8013 1045 C: sh8013 1046 C: 1047 C: 2fooBAR 1048 C: 1049 C: 1050 C: 1051 C: 1052 C: 1055 C: sunrise 1056 C: 1058 C: ... 1059 C: 1060 C: 1061 C: 1062 C: ABC-12345 1063 C: 1064 C: 1065 The following is an example domain command using the 1066 extension, following the "signed mark" validation 1067 model, with the base64 encoded signed mark information: 1069 C: 1070 C: 1071 C: 1072 C: 1073 C: 1075 C: exampleone.tld 1076 C: jd1234 1077 C: sh8013 1078 C: sh8013 1079 C: 1080 C: 2fooBAR 1081 C: 1082 C: 1083 C: 1084 C: 1085 C: 1087 C: sunrise 1088 C: 1090 C: ... 1091 C: 1092 C: 1093 C: 1094 C: ABC-12345 1095 C: 1096 C: 1098 3.3.2. Claims Create Form 1100 The Claims Create Form of the extension to the EPP domain name 1101 mapping [RFC5731] includes the information related to the 1102 registrant's acceptance of the Claims Notice for the "claims" launch 1103 phase. 1105 A element is sent along with the regular 1106 domain command. The element has an OPTIONAL "type" 1107 attribute that defines the expected type of object ("application" or 1108 "registration") to create. The server SHOULD validate the "type" 1109 attribute, when passed, against the type of object that will be 1110 created. The element contains the following child 1111 elements: 1113 MUST contain the value of "claims" to indicate the 1114 claims launch phase. 1115 1116 Unique notice identifier generated by the 1117 source of the Claims Notice information. 1118 Expiry of the claims notice. 1119 Contains the date and time that the Claims 1120 Notice was accepted. 1122 The following is an example domain command using the 1123 extension with the information for 1124 the "claims" launch phase: 1126 C: 1127 C: 1128 C: 1129 C: 1130 C: 1132 C: example.tld 1133 C: jd1234 1134 C: sh8013 1135 C: sh8013 1136 C: 1137 C: 2fooBAR 1138 C: 1139 C: 1140 C: 1141 C: 1142 C: 1144 C: claims 1145 C: 1146 C: 49FD46E6C4B45C55D4AC 1147 C: 2012-06-19T10:00:10.0Z 1148 C: 1149 C: 2012-06-19T09:01:30.0Z 1150 C: 1151 C: 1152 C: 1153 C: 1154 C: ABC-12345 1155 C: 1156 C: 1158 3.3.3. General Create Form 1160 The General Create Form of the extension to the EPP domain name 1161 mapping [RFC5731] includes the launch phase and optionally the object 1162 type to create. The OPTIONAL "type" attribute defines the expected 1163 type of object ("application" or "registration") to create. The 1164 server SHOULD validate the "type" attribute, when passed, against the 1165 type of object that will be created. 1167 A element is sent along with the regular 1168 domain command. The element contains the following 1169 child elements: 1171 Contains the value of the active launch phase of the 1172 server. The server SHOULD validate the value against the active 1173 server launch phase. 1175 The following is an example domain command using the 1176 extension for a "landrush" launch phase application: 1178 C: 1179 C: 1180 C: 1181 C: 1182 C: 1184 C: example.tld 1185 C: jd1234 1186 C: sh8013 1187 C: sh8013 1188 C: 1189 C: 2fooBAR 1190 C: 1191 C: 1192 C: 1193 C: 1194 C: 1197 C: landrush 1198 C: 1199 C: 1200 C: ABC-12345 1201 C: 1202 C: 1204 3.3.4. Mixed Create Form 1206 The Mixed Create Form supports a mix of the create forms, where for 1207 example the Sunrise Create Form (Section 3.3.1) and the Claims Create 1208 Form (Section 3.3.2) MAY be supported in a single command by 1209 including both the verified trademark information and the information 1210 related to the registrant's acceptance of the Claims Notice. The 1211 server MAY support the Mixed Create Form. The "custom" launch phase 1212 SHOULD be used when using the Mixed Create Form. 1214 The following is an example domain command using the 1215 extension, with using a mix of the Sunrise Create 1216 Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) by 1217 including both a mark and a notice: 1219 C: 1220 C: 1221 C: 1222 C: 1223 C: 1225 C: exampleone.tld 1226 C: jd1234 1227 C: sh8013 1228 C: sh8013 1229 C: 1230 C: 2fooBAR 1231 C: 1232 C: 1233 C: 1234 C: 1235 C: 1238 C: custom 1239 C: 1240 C: 1242 C: ... 1243 C: 1244 C: 1245 C: 1246 C: 49FD46E6C4B45C55D4AC 1247 C: 2012-06-19T10:00:10.0Z 1248 C: 1249 C: 2012-06-19T09:01:30.0Z 1250 C: 1251 C: 1252 C: 1253 C: 1254 C: ABC-12345 1255 C: 1256 C: 1258 3.3.5. Create Response 1260 If the create was successful, the server MAY reply with the element along with the regular EPP to indicate the 1262 server generated Application Identifier (Section 2.1), when multiple 1263 applications of a given domain name are supported; otherwise no 1264 extension is included with the regular EPP . The element contains the following child elements: 1267 The phase of the application that mirrors the 1268 element included in the . 1269 The application identifier of the 1270 application. 1272 An example response when multiple overlapping applications are 1273 supported by the server: 1275 S: 1276 S: 1277 S: 1278 S: 1279 S: Command completed successfully; action pending 1280 S: 1281 S: 1282 S: 1284 S: example.tld 1285 S: 2010-08-10T15:38:26.623854Z 1286 S: 2012-08-10T15:38:26.623854Z 1287 S: 1288 S: 1289 S: 1290 S: 1292 S: sunrise 1293 S: 2393-9323-E08C-03B1 1294 S: 1295 S: 1296 S: 1297 S: 1298 S: ABC-12345 1299 S: 54321-XYZ 1300 S: 1301 S: 1302 S: 1304 3.4. EPP Command 1306 This extension defines additional elements to extend the EPP 1307 command to be used in conjunction with the domain name mapping. 1309 A server that does not support multiple applications of a given 1310 domain name with an Application Identifier (Section 2.1) during its 1311 launch phase operations MUST return an EPP error result code of 2102. 1313 Registry policies permitting, clients may update an application 1314 object by submitting an EPP command along with a element to indicate the application object to be updated. 1316 The element contains the following child elements: 1318 The phase during which the application was submitted 1319 or is associated with. 1320 The application identifier for which the 1321 client wishes to update. 1323 The following is an example domain command with the extension to add and remove a name server of a sunrise 1325 application with the application identifier "abc123": 1327 C: 1328 C: 1329 C: 1330 C: 1331 C: 1333 C: example.tld 1334 C: 1335 C: 1336 C: ns2.example.tld 1337 C: 1338 C: 1339 C: 1340 C: 1341 C: ns1.example.tld 1342 C: 1343 C: 1344 C: 1345 C: 1346 C: 1347 C: 1349 C: sunrise 1350 C: abc123 1351 C: 1352 C: 1353 C: ABC-12345 1354 C: 1355 C: 1357 This extension does not define any extension to the response of an 1358 domain command. After processing the command, the server 1359 replies with a standard EPP response as defined in the EPP domain 1360 name mapping [RFC5731]. 1362 3.5. EPP Command 1364 This extension defines additional elements to extend the EPP 1365 command to be used in conjunction with the domain name mapping. 1367 A server that does not support multiple applications of a given 1368 domain name with an Application Identifier (Section 2.1) during its 1369 launch phase operations MUST return an EPP error result code of 2102. 1371 Registry policies permitting, clients MAY withdraw an application by 1372 submitting an EPP command along with a 1373 element to indicate the application object to be deleted. The 1374 element contains the following child elements: 1376 The phase during which the application was submitted 1377 or is associated with. 1378 The application identifier for which the 1379 client wishes to delete. 1381 The following is an example domain command with the extension: 1384 C: 1385 C: 1386 C: 1387 C: 1388 C: 1390 C: example.tld 1391 C: 1392 C: 1393 C: 1394 C: 1396 C: sunrise 1397 C: abc123 1398 C: 1399 C: 1400 C: ABC-12345 1401 C: 1402 C: 1404 This extension does not define any extension to the response of a 1405 domain command. After processing the command, the server 1406 replies with a standard EPP response as defined in the EPP domain 1407 name mapping [RFC5731]. 1409 3.6. EPP Command 1411 This extension does not define any extension to the EPP 1412 command or response described in the EPP domain name mapping 1413 [RFC5731]. 1415 3.7. EPP Command 1417 This extension does not define any extension to the EPP 1418 command or response described in the EPP domain name mapping 1419 [RFC5731]. 1421 4. Formal Syntax 1423 One schema is presented here that is the EPP Launch Phase Mapping 1424 schema. 1426 The formal syntax presented here is a complete schema representation 1427 of the object mapping suitable for automated validation of EPP XML 1428 instances. The BEGIN and END tags are not part of the schema; they 1429 are used to note the beginning and ending of the schema for URI 1430 registration purposes. 1432 4.1. Launch Schema 1434 Copyright (c) 2012 IETF Trust and the persons identified as authors 1435 of the code. All rights reserved. 1437 Redistribution and use in source and binary forms, with or without 1438 modification, are permitted provided that the following conditions 1439 are met: 1441 o Redistributions of source code must retain the above copyright 1442 notice, this list of conditions and the following disclaimer. 1443 o Redistributions in binary form must reproduce the above copyright 1444 notice, this list of conditions and the following disclaimer in 1445 the documentation and/or other materials provided with the 1446 distribution. 1447 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1448 names of specific contributors, may be used to endorse or promote 1449 products derived from this software without specific prior written 1450 permission. 1452 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1453 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1454 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1455 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1456 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1457 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1458 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1459 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1460 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1461 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1462 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1464 BEGIN 1465 1466 1475 1478 1481 1484 1487 1488 1489 Extensible Provisioning Protocol v1.0 1490 domain name extension schema 1491 for the launch phase processing. 1492 1493 1495 1498 1499 1500 1501 1502 1504 1507 1508 1509 1510 1511 1512 1514 1517 1518 1519 1521 1527 1528 1529 1530 1531 1532 1533 1535 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1550 1551 1552 1553 1554 1556 1559 1560 1561 1562 1563 1565 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1580 1583 1584 1585 1586 1588 1590 1591 1592 1593 1594 1598 1599 1600 1602 1604 1605 1607 1610 1611 1612 1613 1614 1616 1618 1620 1621 1623 1624 1625 1627 1630 1631 1632 1633 1634 1635 1637 1640 1641 1642 1643 1644 1645 1646 1648 1651 1652 1653 1654 1655 1657 1659 1663 1664 1665 1666 1667 1668 1670 1673 1674 1675 1676 1679 1680 1682 1684 1688 1689 1690 1692 1695 1696 1697 1698 1700 1701 1703 1704 1705 1706 1708 1709 1711 1712 1713 1714 1716 1717 1718 1720 1723 1724 1725 1726 1729 1731 1733 1734 1736 1737 END 1739 5. Acknowledgements 1741 The authors wish to acknowledge the efforts of the leading 1742 participants of the Community TMCH Model that led to many of the 1743 changes to this document, which include Chris Wright, Jeff Neuman, 1744 Jeff Eckhaus, and Will Shorter. 1746 Special suggestions that have been incorporated into this document 1747 were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Jan 1748 Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus Malorny, 1749 Alexander Mayrhofer, Patrick Mevzek, James Mitchell, Francisco 1750 Obispo, Bernhard Reutner-Fischer, Trung Tran, Ulrich Wisser and 1751 Sharon Wodjenski. 1753 6. Change History 1755 6.1. Change from 00 to 01 1757 1. Changed to use camel case for the XML elements. 1758 2. Replaced "cancelled" status to "rejected" status. 1759 3. Added the child elements of the element. 1760 4. Removed the XML schema and replaced with "[TBD]". 1762 6.2. Change from 01 to 02 1764 1. Added support for both the ICANN and ARI/Neustar TMCH models. 1765 2. Changed the namespace URI and prefix to use "launch" instead of 1766 "launchphase". 1767 3. Added definition of multiple claim validation models. 1768 4. Added the and 1769 elements. 1770 5. Added support for Claims Info Command 1772 6.3. Change from 02 to 03 1774 1. Removed XSI namespace per Keith Gaughan's suggestion on the 1775 provreg list. 1776 2. Added extensibility to the launch:status element and added the 1777 pendingAuction status per Trung Tran's feedback on the provreg 1778 list. 1779 3. Added support for the Claims Check Command, updated the location 1780 and contents of the signedNotice, and replaced most references of 1781 Claim to Mark based on the work being done on the ARI/Neustar 1782 launch model. 1784 6.4. Change from 03 to 04 1786 1. Removed references to the ICANN model. 1787 2. Removed support for the Claims Info Command. 1788 3. Removed use of the signedClaim. 1789 4. Revised the method for referring to the signedClaim from the XML 1790 Signature using the IDREF URI. 1791 5. Split the launch-1.0.xsd into three XML schemas including launch- 1792 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 1793 6. Split the "claims" launch phase to the "claims1" and "claims2" 1794 launch phases. 1795 7. Added support for the encodedSignedMark with base64 encoded 1796 signedMark. 1797 8. Changed the elements in the createNoticeType to include the 1798 noticeID, timestamp, and the source elements. 1799 9. Added the class and effectiveDate elements to mark. 1801 6.5. Change from 04 to 05 1803 1. Removed reference to in the example. 1804 2. Incorporated feedback from Bernhard Reutner-Fischer on the 1805 provreg mail list. 1806 3. Added missing launch XML prefix to applicationIDType reference in 1807 the idContainerType of the Launch Schema. 1808 4. Added missing description of the element in the element. 1810 5. Updated note on replication of the EPP contact mapping elements 1811 in the Mark Contact section. 1813 6.6. Change from 05 to 06 1815 1. Removed the definition of the mark-1.0 and signedMark-1.0 and 1816 replaced with reference to draft-lozano-smd, that contains the 1817 definition for the mark, signed marked, and encoded signed mark. 1818 2. Split the into and 1819 based on feedback from Trung Tran. 1820 3. Added the "includeMark" optional attribute to the 1821 element to enable the client to request whether or not to include 1822 the mark in the info response. 1823 4. Fixed state diagram to remove redundant transition from "invalid" 1824 to "rejected"; thanks Klaus Malorny. 1826 6.7. Change from 06 to 07 1827 1. Proof-read grammar and spelling. 1828 2. Changed "pendingAuction" status to "pendingAllocation", changed 1829 "pending" to "pendingValidation" status, per proposal from Trung 1830 Tran and seconded by Rubens Kuhl. 1831 3. Added text related to the use of RFC 5731 pendingCreate to the 1832 Application Identifier section. 1833 4. Added the Poll Messaging section to define the use of poll 1834 messaging for intermediate state transitions and pending action 1835 poll messaging for final state transitions. 1837 6.8. Change from 07 to 08 1839 1. Added support for use of the launch statuses and poll messaging 1840 for Launch Registrations based on feedback from Sharon Wodjenski 1841 and Trung Tran. 1842 2. Incorporated changes based on updates or clarifications in 1843 draft-lozano-tmch-func-spec-01, which include: 1844 1. Removed the unused element. 1845 2. Removed the element. 1846 3. Added the element based on the required 1847 element. 1849 6.9. Change from 08 to 09 1851 1. Made element optional in to allow 1852 passing just the in per request 1853 from Ben Levac. 1854 2. Added optional "type" attribute in to enable the 1855 client to explicitly define the desired type of object 1856 (application or registration) to create to all forms of the 1857 create extension. 1858 3. Added text that the server SHOULD validate the 1859 element in the Launch Phases section. 1860 4. Add the "General Create Form" to the create command extension to 1861 support the request from Ben Levac. 1862 5. Updated the text for the Poll Messaging section based on feedback 1863 from Klaus Malorny. 1864 6. Replaced the "claims1" and "claims2" phases with the "claims" 1865 phase based on discussion on the provreg list. 1866 7. Added support for a mixed create model (Sunrise Create Model and 1867 Claims Create Model), where a trademark (encoded signed mark, 1868 etc.) and notice can be passed, based on a request from James 1869 Mitchell. 1870 8. Added text for the handling of the overlapping "claims" and 1871 "landrush" launch phases. 1872 9. Added support for two check forms (claims check form and 1873 availability check form) based on a request from James Mitchell. 1874 The availability check form was based on the text in 1876 6.10. Change from 09 to 10 1878 1. Changed noticeIDType from base64Binary to token to be compatible 1879 with draft-lozano-tmch-func-spec-05. 1880 2. Changed codeType from base64Binary to token to be more generic. 1881 3. Updated based on feedback from Alexander Mayrhofer, which 1882 include: 1883 1. Changed "extension to the domain name extension" to 1884 "extension to the domain name mapping". 1885 2. Changed use of 2004 return code to 2306 return code when 1886 phase passed mismatches active phase and sub-phase. 1887 3. Changed description of "allocated" and "rejected" statuses. 1888 4. Moved sentence on a synchronous command 1889 without the use of an intermediate application, then an 1890 Application Identifier MAY not be needed to the Application 1891 Identifier section. 1892 5. Restructured the Mark Validation Models section to include 1893 the " element" sub-section, the " element" sub-section, and the Digital Signature sub- 1895 section. 1896 6. Changed "Registries may" to "Registries MAY". 1897 7. Changed "extensed" to "extended" in "Availability Check 1898 Form" section. 1899 8. Broke the mix of create forms in the "EPP Command" 1900 section to a fourth "Mixed Create Form" with its own sub- 1901 section. 1902 9. Removed "displayed or" from "displayed or accepted" in the 1903 description. 1904 10. Replaced "given domain name is supported" with "given domain 1905 name are supported" in the "Create Response" section. 1906 11. Changed the reference of 2303 (object does not exist) in the 1907 "Security Considerations" section to 2201 (authorization 1908 error). 1909 12. Added arrow from "invalid" status to "pendingValidation" 1910 status and "pendingAllocation" status to "rejected" status 1911 in the State Transition Diagram. 1912 4. Added the "C:" and "S:" example prefixes and related text in the 1913 "Conventions Used in This Document" section. 1915 6.11. Change from 10 to 11 1917 1. Moved the claims check response element under 1918 the element instead of the element based on 1919 the request from Francisco Obispo. 1921 7. IANA Considerations 1923 This document uses URNs to describe XML namespaces and XML schemas 1924 conforming to a registry mechanism described in [RFC3688]. Three URI 1925 assignments have been registered by the IANA. 1927 Registration request for the Launch namespace: 1929 URI: urn:ietf:params:xml:ns:launch-1.0 1930 Registrant Contact: See the "Author's Address" section of this 1931 document. 1932 XML: None. Namespace URIs do not represent an XML specification. 1934 8. Security Considerations 1936 The mapping extensions described in this document do not provide any 1937 security services beyond those described by EPP [RFC5730], the EPP 1938 domain name mapping [RFC5731], and protocol layers used by EPP. The 1939 security considerations described in these other specifications apply 1940 to this specification as well. 1942 Updates to, and deletion of an application object must be restricted 1943 to clients authorized to perform the said operation on the object. 1945 As information contained within an application, or even the mere fact 1946 that an application exists may be confidential. Any attempt to 1947 operate on an application object by an unauthorized client MUST be 1948 rejected with an EPP 2201 (authorization error) return code. Server 1949 policy may allow operation with filtered output by clients 1950 other than the sponsoring client, in which case the 1951 and response SHOULD be filtered to include only 1952 fields that are publicly accessible. 1954 9. Normative References 1956 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1957 Requirement Levels", BCP 14, RFC 2119, March 1997. 1959 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1960 January 2004. 1962 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1963 STD 69, RFC 5730, August 2009. 1965 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1966 Domain Name Mapping", STD 69, RFC 5731, August 2009. 1968 [draft-lozano-smd] 1969 Lozano, G., "Mark and Signed Mark Objects Mapping". 1971 [1] 1973 Authors' Addresses 1975 James Gould 1976 VeriSign, Inc. 1977 12061 Bluemont Way 1978 Reston, VA 20190 1979 US 1981 Email: jgould@verisign.com 1982 URI: http://www.verisigninc.com 1984 Wil Tan 1985 Cloud Registry 1986 Suite 32 Seabridge House 1987 377 Kent St 1988 Sydney, NSW 2000 1989 AU 1991 Phone: +61 414 710899 1992 Email: wil@cloudregistry.net 1993 URI: http://www.cloudregistry.net 1995 Gavin Brown 1996 CentralNic Ltd 1997 35-39 Mooregate 1998 London, England EC2R 6AR 1999 GB 2001 Phone: +44 20 33 88 0600 2002 Email: gavin.brown@centralnic.com 2003 URI: https://www.centralnic.com