gmane.ietf.provreg http://blog.gmane.org/gmane.ietf.provreg hourly 1 1901-01-01T00:00+00:00 Gmane http://gmane.org/img/gmane-25t.png http://gmane.org Launch Phase EPP Extension Version 11 http://comments.gmane.org/gmane.ietf.provreg/2952 <pre>Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension Mapping to Version 11. You can find the draft at the URL http://tools.ietf.org/html/draft-tan-epp-launchphase-11. This version includes the following change: 1. Moved the claims check response &lt;launch:chkData&gt; element under the &lt;extension&gt; element instead of the &lt;resData&gt; element based on the request from Francisco Obispo. Thanks, JG James F. Gould Verisign "This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately." _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-05-17T19:40:44 gtld-tech mailing list http://comments.gmane.org/gmane.ietf.provreg/2951 <pre>Colleagues, This is to let you know that we are launching a public, open mailing list for technical discussions regarding gTLD registries and registrars. The intention is to provide a forum for discussion of issues that may appear during ongoing operation and particularly with the upcoming launch of new gTLDs. You can subscribe to the list at: https://mm.icann.org/mailman/listinfo/gtld-tech Regards, </pre> Francisco Arias 2013-05-16T23:29:40 Custom phases with claims http://comments.gmane.org/gmane.ietf.provreg/2949 <pre>Jim, You have long been a proponent for having clients provide "claims" and "landrush" in the phase element (to my disagreement). Since you require clients specify both, how would you represent a "custom" phase that requires claims processing given the "name" attribute cannot be used to specify the sub-phase? My preference is to remove "claims" as a phase as it provides _zero_ value to the protocol, and retire the need to provide sub-phase information during claims. Claims information may be provided with other phases (landrush, open) without explicitly providing a "claims" phase value, and servers have to code for missing claims information regardless (e.g. It is possible to provide "sunrise" with claims information, and "claims" with mark information). I also dislike the use of the term "custom" - registries will operate sunrises differently; those different sunrises are by definition custom. IMO the schema-level restriction on phase values provides no value to the protocol itself. I would like to see the phase enumeration removed, replaced instead with unrestricted "token" strings. The mapping document can reserve the existing values (sunrise, landrush, open) as having special meaning if you feel it is necessary. Regards, James _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> James Mitchell 2013-05-16T05:23:05 Path to standard? http://comments.gmane.org/gmane.ietf.provreg/2944 <pre>How are we going to pursue standardization of the Launchphase and IDN drafts? I'm in the process of registering the namespace for the IDN extension, but I'm thinking about how to make sure it all stays "current" after the draft expires. Can someone explain what is the process? Francisco Obispo Director of Applications and Services - ISC email: fobispo&lt; at &gt;isc.org Phone: +1 650 423 1374 || INOC-DBA *3557* NOC PGP KeyID = B38DB1BE _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Francisco Obispo 2013-05-11T15:44:34 Launchphase and <check> http://comments.gmane.org/gmane.ietf.provreg/2942 <pre>We're currently implementing the launchphase extentension. In my opinion the Claims Check system should use the &lt;extension&gt; section and not the &lt;resData&gt; The reason for my reasoning has to do with RFC5730 and: 2.9.2.1. EPP &lt;check&gt; Command The EPP &lt;check&gt; command is used to determine if an object can be provisioned within a repository. It provides a hint that allows a client to anticipate the success or failure of provisioning an object using the &lt;create&gt; command as object-provisioning requirements are ultimately a matter of server policy. Referring to "Objects", however launch-1.0 is an extension, or at least is handled in EPP like one, so my belief is that the response should go into the &lt;extension&gt; section: S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; S: &lt;response&gt; S: &lt;result code="1000"&gt; S: &lt;msg&gt;Command completed successfully&lt;/msg&gt; S: &lt;/result&gt; S: &lt;resData&gt; S: &lt;launch:chkData S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; S: &lt;launch:phase&gt;claims&lt;/launch:phase&gt; S: &lt;launch:cd&gt; S: &lt;launch:name exists="0"&gt;example1.tld&lt;/launch:name&gt; S: &lt;/launch:cd&gt; S: &lt;launch:cd&gt; S: &lt;launch:name exists="1"&gt;example2.tld&lt;/launch:name&gt; S: &lt;launch:claimKey&gt;abc123&lt;/launch:claimKey&gt; S: &lt;/launch:cd&gt; S: &lt;/launch:chkData&gt; S: &lt;/resData&gt; S: &lt;trID&gt; S: &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; S: &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; S: &lt;/trID&gt; S: &lt;/response&gt; S:&lt;/epp&gt; SHOULD BE: S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; S: &lt;response&gt; S: &lt;result code="1000"&gt; S: &lt;msg&gt;Command completed successfully&lt;/msg&gt; S: &lt;/result&gt; S: &lt;extension&gt; S: &lt;launch:chkData S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; S: &lt;launch:phase&gt;claims&lt;/launch:phase&gt; S: &lt;launch:cd&gt; S: &lt;launch:name exists="0"&gt;example1.tld&lt;/launch:name&gt; S: &lt;/launch:cd&gt; S: &lt;launch:cd&gt; S: &lt;launch:name exists="1"&gt;example2.tld&lt;/launch:name&gt; S: &lt;launch:claimKey&gt;abc123&lt;/launch:claimKey&gt; S: &lt;/launch:cd&gt; S: &lt;/launch:chkData&gt; S: &lt;/extension&gt; S: &lt;trID&gt; S: &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; S: &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; S: &lt;/trID&gt; S: &lt;/response&gt; S:&lt;/epp&gt; The main reasoning behind this, is that some systems (including ours) expect extensions to write on the &lt;extension&gt; section and NOT in the rest of the document. Having extensions that behave like "objects" could lead to unnecessary processing and confusion. Does anyone feel the same? Francisco Obispo Director of Applications and Services - ISC email: fobispo&lt; at &gt;isc.org Phone: +1 650 423 1374 || INOC-DBA *3557* NOC PGP KeyID = B38DB1BE _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Francisco Obispo 2013-05-10T05:07:25 Launch EPP SDK 2.1.0.0 Preview http://comments.gmane.org/gmane.ietf.provreg/2940 <pre>Verisign has released the third release of a preview version of the Launch EPP SDK, named Launch EPP SDK 2.1.0.0. This SDK fully implements draft-tan-epp-launchphase-10 ( http://tools.ietf.org/html/draft-tan-epp-launchphase-10 ) and draft-lozano-tmch-smd-02 ( http://tools.ietf.org/html/draft-lozano-tmch-smd-02 ), referred to simply as 10/02, and includes the following features that can be of use to multiple stakeholders: 1. Packet encoder / decoder (CODEC) that will encode the XML from objects and decode the objects from XML. 2. Creation and validation code for signed marks (SMD) using an XML signed mark or a base64 encoded signed mark that complies with draft-lozano-tmch-smd-02. 3. Use of a test CA issued certificate that is included in the signed mark or base64 encoded signed mark that is chained to the test CA certificate by the EPP Stub Server. A test certificate in a test Certificate Revocation List (CRL) is also validated by the EPP Stub Server. 4. Sample of poll messaging compliant with draft-tan-epp-launchphase-10 in the EPP Stub Server. 5. A client API that utilizes the packet encoder / decoder (CODEC) along with other code (e.g. transport, configuration, XML parsing pooling) to interface with an EPP server. 6. An EPP Stub Server that includes pre-defined responses to support the client tests. The EPP Stub Server behavior can be easily customized to suite your testing needs. The Launch EPP SDK includes support for RFC 5730, 5731, 5732, 5733, 5734, 3915, and 5910. Verisign will be integrating the preview of the Launch Phase EPP Extension into its Verisign Bundle EPP SDK. The Launch EPP SDK is open source, requires Java 6 or higher, and below are the distributions and documents: * Unix Binary Distribution (.tar.gz) - http://www.verisigninc.com/assets/2-1-0-0/epp-launch-bundle-2.1.0.0-bin.tar.gz * Unix Source Distribution (.tag.gz) - http://www.verisigninc.com/assets/2-1-0-0/epp-launch-bundle-2.1.0.0-src.tar.gz * Windows Binary Distribution (.zip) - http://www.verisigninc.com/assets/2-1-0-0/epp-launch-bundle-2.1.0.0-bin.zip * Windows Source Distribution (.zip) - http://www.verisigninc.com/assets/2-1-0-0/epp-launch-bundle-2.1.0.0-src.zip * Readme File - http://www.verisigninc.com/assets/2-1-0-0/epp-launch.README * Install Instructions - http://www.verisigninc.com/assets/2-1-0-0/epp-launch.INSTALL * Change Log - http://www.verisigninc.com/assets/2-1-0-0/changelog.txt -- JG [cid:922F2D86-FC79-472E-A0CF-F88984FFA29E] James Gould Principal Software Engineer jgould&lt; at &gt;verisign.com&lt;mailto:jgould&lt; at &gt;verisign.com&gt; 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com "This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately." _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-05-08T14:43:51 Implementation of EPP AuthInfo http://comments.gmane.org/gmane.ietf.provreg/2930 <pre>All, Please share your thoughts regarding the implementation of the Contact AuthInfo for the approval of initiated contact updates. Our current process looks to have the registrant provide the code as an indication of approval regarding the update of their information, completing the update instantly. Updates that are not provided with the code will not execute. Further to this, we are looking to implement the Domain AuthInfo code as a definite measure for approving registrant changes to a linked domain. In this instance the current registrant must provide the Domain AuthInfo code as approval of the registrant change. Regards, Vlad Dinculescu -------------------------------- Domain Name Services _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Vlad Dinculescu 2013-05-07T06:23:37 Launch Phase EPP Extension Version 10 http://comments.gmane.org/gmane.ietf.provreg/2924 <pre>Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension Mapping to Version 10. You can find the draft at the URL http://tools.ietf.org/html/draft-tan-epp-launchphase-10. This version includes the following changes: 1. Changed noticeIDType from base64Binary to token to be compatible with draft-lozano-tmch-func-spec-05&lt;http://tools.ietf.org/html/draft-lozano-tmch-func-spec-05&gt;. 2. Changed codeType from base64Binary to token to be more generic. 3. Updated based on feedback from Alexander Mayrhofer, which include: 1. Changed "extension to the domain name extension" to "extension to the domain name mapping". 2. Changed use of 2004 return code to 2306 return code when phase passed mismatches active phase and sub-phase. 3. Changed description of "allocated" and "rejected" statuses. 4. Moved sentence on a synchronous &lt;domain:create&gt; command without the use of an intermediate application, then an Application Identifier MAY not be needed to the Application Identifier section. 5. Restructured the Mark Validation Models section to include the "&lt;launch:codeMark&gt; element" sub-section, the "&lt;mark: mark&gt; element" sub-section, and the Digital Signature sub- section. 6. Changed "Registries may" to "Registries MAY". 7. Changed "extensed" to "extended" in "Availability Check Form" section. 8. Broke the mix of create forms in the "EPP &lt;create&gt; Command" section to a fourth "Mixed Create Form" with its own sub- section. 9. Removed "displayed or" from "displayed or accepted" in the &lt;launch:acceptedDate&gt; description. 10. Replaced "given domain name is supported" with "given domain name are supported" in the "Create Response" section. 11. Changed the reference of 2303 (object does not exist) in the "Security Considerations" section to 2201 (authorization error). 12. Added arrow from "invalid" status to "pendingValidation" status and "pendingAllocation" status to "rejected" status in the State Transition Diagram. 4. Added the "C:" and "S:" example prefixes and related text in the "Conventions Used in This Document" section. We are hoping that the draft stabilizes with this version. Please reply with any feedback. Thanks, JG James F. Gould Verisign "This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately." _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-05-01T12:32:56 Biggest Fake Conference in Computer Science http://comments.gmane.org/gmane.ietf.provreg/2920 <pre>Biggest Fake Conference in Computer Science We are researchers from different parts of the world and conducted a study on the world’s biggest bogus computer science conference WORLDCOMP ( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia from University of Georgia, USA. We submitted a fake paper to WORLDCOMP 2011 and again (the same paper with a modified title) to WORLDCOMP 2012. This paper had numerous fundamental mistakes. Sample statements from that paper include: (1). Binary logic is fuzzy logic and vice versa (2). Pascal developed fuzzy logic (3). Object oriented languages do not exhibit any polymorphism or inheritance (4). TCP and IP are synonyms and are part of OSI model (5). Distributed systems deal with only one computer (6). Laptop is an example for a super computer (7). Operating system is an example for computer hardware Also, our paper did not express any conceptual meaning. However, it was accepted both the times without any modifications (and without any reviews) and we were invited to submit the final paper and a payment of $500+ fee to present the paper. We decided to use the fee for better purposes than making Prof. Hamid Arabnia (Chairman of WORLDCOMP) rich. After that, we received few reminders from WORLDCOMP to pay the fee but we never responded. We MUST say that you should look at the above website if you have any thoughts to submit a paper to WORLDCOMP. DBLP and other indexing agencies have stopped indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of http://sites.google.com/site/dumpconf for comments from well-known researchers about WORLDCOMP. The status of your WORLDCOMP papers can be changed from scientific to other (i.e., junk or non-technical) at any time. Better not to have a paper than having it in WORLDCOMP and spoil the resume and peace of mind forever! Our study revealed that WORLDCOMP is a money making business, using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing out a small chunk of that money (around 20 dollars per paper published in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) who publicizes WORLDCOMP and also defends it at various forums, using fake/anonymous names. The puppet uses fake names and defames other conferences to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). That is, the puppet does all his best to get a maximum number of papers published at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has refused to provide the venue for WORLDCOMP’13 because of the fears of their image being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 is taking place at a different resort. WORLDCOMP will not be held after 2013. The draft paper submission deadline is over but still there are no committee members, no reviewers, and there is no conference Chairman. The only contact details available on WORLDCOMP’s website is just an email address! Let us make a direct request to Prof. Hamid arabnia: publish all reviews for all the papers (after blocking identifiable details) since 2000 conference. Reveal the names and affiliations of all the reviewers (for each year) and how many papers each reviewer had reviewed on average. We also request him to look at the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 Sorry for posting to multiple lists. Spreading the word is the only way to stop this bogus conference. Please forward this message to other mailing lists and people. We are shocked with Prof. Hamid Arabnia and his puppet’s activities http://worldcomp-fake-bogus.blogspot.com Search Google using the keyword worldcomp fake for additional links. _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> johnsonhammond1< at >hushmail.com 2013-04-27T17:27:16 Review of draft-lozano-tmch-func-spec-05 http://comments.gmane.org/gmane.ietf.provreg/2913 <pre>Hi, i've reviewed draft-lozano-tmch-func-spec, here are my comments: - Abstract: The text contains "Domain Name Registry" as well as "domain name Registry" - is this intentional? - Introduction: Why is "Data Formats" capitalized? - 5.2.1 / 5.2.2 (Sunrise domain registration): I understand that "registration" in the sense of executing a sunrise "create" command could either be direct "Allocation", or the creation of an "Application". Some text that clarifies these options would be good, because "registration" could be mis-interpreted as "direct, immediate allocation". - page 27 (5.2.3): Theres a broken literal "xref" in bullet 4. - 6.1 (DNL List): I understand that the DNL is always a "full" list, containing all DNLs that match a PRM? Clarifying text would be appreciated here. - 6.2 (SMD revocation): I do assume it would always include all revoked SMDs. Also "Version 1 MUST always be present" could maybe be changed to "MUST be set to '1' for this version of the specification".. Same in Section 6.3 and Section 6.3.1 - 6.3 (LORDN file): should a LORDN file contain only domains effectively allocated since the last accepted LORDN file, or should it always contain the domains of the current day, or should it contain all domains allocated since the start of the Sunrise period? I suppose either the second option - some text clarifying this would be good (unless i've missed it?). - 6.3: &lt;DN registered&gt;: mention that the A-Label is to be used, eg. "The domain name that was allocated in A-Label representation". - Section 6.3.1: The "first line" specification of the LORDN log file has a missing comma between &lt;LORDN Log creation datetime&gt; and &gt;LORDN file creation datetime&gt;. - 6.3.1.1: I understand that a single "err" class outcome in the LORDN logfile indicates that the whole file was rejected, and the Registry shall repeat with a corrected file? Clarification would be good here as well.. - 6.3.1.1: I understand that since "ROID notified earlier" is just a warning, a LORDN file can effectively contain domain names that have been reported earlier wihout processing to fail... tia, Alex _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Alexander Mayrhofer 2013-04-23T11:54:33 comments on draft-tan-epp-launchphase-09 http://comments.gmane.org/gmane.ietf.provreg/2912 <pre>Hi, i've done a more thorough review of the current version of the launchphase documents. Generally, i think the draft is pretty mature, and that the document could proceed to publication, i haven't found any *really* major issues that would prevent implementation - thanks for the great work so far. The few issues that i found are listed below (disclaimer: Some of them might have been discussed in past conf calls or mailing list discussions that i have missed - if that is the case, please disregard them). I also haven't looked at the schema definition itself, but i assume that would be done during a final NITS review. Here we go: - Introduction: The last paragraph says "extension to the domain name extension" - i suppose that should read "extension to the domain name mapping". - Section 2.2: I think that 2004 is an inappropriate response code for this case, since the value might not be "outside the range of values specified by the protocol" - it actually *is* a valid value, just not appropriate at that certain time. Therefore, i think that 2306 might be more appropriate. - Section 2.2: Is the server allowed to validate names of sub-phases? I think some text like "Servers MAY validate the sub-phase elements, and respond with 2306 if a sub-phase is required that is not active" would do good. I wouldn't make it required, though. - Section 2.3, description of "allocated" and "rejected": Swap the two sentences in each description - first describe what it is, and then describe that it's one of the two possible states. - Section 2.3, last sentence ("If the domain:create command processes...") - why is that sentence in this section? If required at all, it would be more appropriate in Section 2.1. Also, remove the "along with the application status" from this sentence? - Section 2.3.1: The bottom horizontal line connecting pendingAllocation, invalid, allocated and rejected confuses the hell out of me - What is the directionality of that transition, and what are the decisions where it connects to the other lines? - Section 2.6 / 2.7: Document structure: I think those would be more appropriate as sub-sections of 2.5 (e.g. 2.5.2 and 2.5.3), since both are "Mark Validation Models" (Title of 2.5), and 2.5 only contains one sub-section. - Section 3, last paragraph before 3.1: I would like to see an RFC2119-style MAY at "Registries MAY choose".. - Section 3.1.1: The first two paragraphs both start with "The Claims Check Form defines", and therefore those two definitions contradict each other a bit. Maybe they could be merged into a single definition. - Section 3.1.1: Why is returning normal availability information a MUST NOT? I don't see a reason why i shouldn't return the availability information together with the mark exists information. Can we change that to "MAY be excluded"? I can understand that availability information would be ambigious *if* the server would return also information for future phases - but see my comment for 3.1.2 below.. - Section 3.1.1: Name of "Trademark exists" attribute: I find "&lt;launch:name exists=..&gt; a bit misleading, because it could be interpreted as "the name itself exists"... Rename it to "tmExists=.." or "trademark=.."? - Section 3.1.2: Typo in second paragraph "extensed".. Also, related to my point above, why is there an explicit "availability" check if there is a "base" availability check already in the check command? - Section 3.1.2: I would like to see text like "Servers MAY reject availability checks for launch phases that are not currently active" (or even a SHOULD?), because i think it doesn't make much sense to "look into the future"... Maybe there are use cases i haven't thought of yet, though..? I understand that might be the reason to disallow the server to return "unqualified" (without phase designation) availability information? - Section 3.2: Why not make both "launch:phase" and "launch:applicationID" optional, and require that at least one of them has to be provided? I don't see the value of requiring the launch phase identifier if an applicationID is given - unless someone plans to re-use application identifiers across applications of multiple phases (which i doubt someone would?) - Section 3.2: It could be useful to include text, that the server MAY refuse to respond to info commands issues by a client that didn't create the application? There might be security / privacy issues with exposing applications of a different client, particularly the mark information (Addendum: I can see some text is contained in the Security Considerations section - so that is probably enough). - Section 3.3: I think the text &amp; example of a "mixed" create command deserves its own section at the end of 3.3. ("3.5. Mixed Create Form"). It would appear more logical to me to explain the "mixed" variant after the "basic" ones have been explained. - Section 3.3.2: Description of "launch:acceptedDate": I think it's imprecise to allow that field to contain when the notice was "displayed or accepted", since those are different things. Let's keep it with the "accepted" data, since i might very well "display" the notice without the registrant "accepting" it (which might not be intended). - Section 3.3.4: "applications of a given domain name are supported" instead of "is supported"? - Section 8. Rather then returning 2303 (which is just plain "lying" in case the object exists), 2201 would be a better choice. I think we can still return 2201 not matter whether the application exists or not - 2308 would be another option. tia, Alex Mayrhofer nic.at _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Alexander Mayrhofer 2013-04-22T20:45:47 Launch Phase EPP Extension Version 09 http://comments.gmane.org/gmane.ietf.provreg/2908 <pre>Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension Mapping to Version 09. You can find the draft at the URL http://tools.ietf.org/html/draft-tan-epp-launchphase-09. This version includes the following changes: 1. Made &lt;choice&gt; element optional in &lt;launch:create&gt; to allow passing just the &lt;launch:phase&gt; in &lt;launch:create&gt; per request from Ben Levac. 2. Added optional "type" attribute in &lt;launch:create&gt; to enable the client to explicitly define the desired type of object (application or registration) to create to all forms of the create extension. 3. Added text that the server SHOULD validate the &lt;launch:phase&gt; element in the Launch Phases section. 4. Add the "General Create Form" to the create command extension to support the request from Ben Levac. 5. Updated the text for the Poll Messaging section based on feedback from Klaus Malorny. 6. Replaced the "claims1" and "claims2" phases with the "claims" phase based on discussion on the provreg list. 7. Added support for a mixed create model (Sunrise Create Model and Claims Create Model), where a trademark (encoded signed mark, etc.) and notice can be passed, based on a request from James Mitchell. 8. Added text for the handling of the overlapping "claims" and "landrush" launch phases. 9. Added support for two check forms (claims check form and availability check form) based on a request from James Mitchell. The availability check form was based on the text in draft-rbp-application-epp-mapping. We are hoping that the draft stabilizes with this version. Please reply with any feedback. Thanks, JG James F. Gould Verisign “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.” _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-04-17T12:48:08 Launch: check command use beyond claims http://comments.gmane.org/gmane.ietf.provreg/2899 <pre>Jim et al, The check command text should be updated to allow for checking availability of names available to a particular phase. One example is the phased-launch of an IDN table post general registration, where registrars can provide a phase, e.g. ZH-release, and the list of names they require availability for. The registrar would feed this information back to the registrant prior to their selection of names for submission in create commands. This should not require any change to the schema. I can provide text if required. Regards, James _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> James Mitchell 2013-04-09T15:28:15 Launch: availability and claims information http://comments.gmane.org/gmane.ietf.provreg/2898 <pre>Jim et al, It is my opinion that claims and name availability information should be available in one command/response. Registrars may want to know claims information at the time of availability (register a new domain search page) to 1) indicate a different price if claims is present or 2) indicate the name is subject to claims acknowledgement/extra processing, or 3) withhold the name from their name spinner because they have chosen not support claims. I suggest the claims check command be extended to include an "standalone" attribute with boolean value true indicating availability information is not required, and false indicating that availability information is desired in addition to claims. Servers may choose to support only standalone=true, servers that support standalone=false must support standalone=true. I'm not too keen on the "standalone" name, so please make other suggestions. I can contribute text if required. Regards, James _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> James Mitchell 2013-04-09T15:16:14 Recombining the claims1 and claims2 phases to the claims phase in draft-tan-epp-launchphase? http://comments.gmane.org/gmane.ietf.provreg/2889 <pre>We are currently working on the draft-tan-epp-launchphase-09 updates and wanted to know what the list felt about replacing the "claims1" and "claims2" phases with simply the "claims" phase. The split of "claims" to "claims1" and "claims2" occurred after the LA meeting in the 04 draft. Since draft-lozano-tmch-func-spec doesn't reference claims2, it doesn't seem to make sense to continue to reference it within draft-tan-epp-launchphase and recombine "claims1" and "claims2" into "claims". Please post your thoughts to the list or privately on this potential change. Thanks, -- JG [cid:E9E1A0E2-F675-4A16-8884-13946BB85239] James Gould Principal Software Engineer jgould&lt; at &gt;verisign.com 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com "This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately." _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-04-08T19:28:52 Launch Phase EPP Extension Version 08 http://comments.gmane.org/gmane.ietf.provreg/2840 <pre>Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension Mapping to Version 08. You can find the draft at the URL http://tools.ietf.org/html/draft-tan-epp-launchphase-08. This version includes the following changes: 1. Added support for use of the launch statuses and poll messaging for Launch Registrations based on feedback from Sharon Wodjenski and Trung Tran. 2. Incorporated changes based on updates or clarifications in draft-lozano-tmch-func-spec-01 &lt;http://tools.ietf.org/html/draft-lozano-tmch-func-spec-01&gt;, which include: 1. Removed the unused &lt;launch:generatedDate&gt; element. 2. Removed the &lt;launch:source&gt; element. 3. Added the &lt;launch:notAfter&gt; element based on the required &lt;tmNotice:notAfter&gt; element. We are hoping that the draft can be stabilized to help with the implementations. Please reply with any feedback. Thanks, JG James F. Gould Verisign _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-03-28T13:58:02 Launch EPP SDK 2.0.0.2 Preview http://comments.gmane.org/gmane.ietf.provreg/2837 <pre>Verisign has released the second release of a preview version of the Launch EPP SDK, named Launch EPP SDK 2.0.0.2. This SDK fully implements draft-tan-epp-launchphase-07 ( http://tools.ietf.org/html/draft-tan-epp-launchphase-07 ) and draft-lozano-tmch-smd-00 ( http://tools.ietf.org/html/draft-lozano-tmch-smd-00 ), referred to simply as 07/00, and includes the following features that can be of use to multiple stakeholders: 1. Packet encoder / decoder (CODEC) that will encode the XML from objects and decode the objects from XML. 2. Creation and validation code for signed marks (SMD) using an XML signed mark or a base64 encoded signed mark that complies with draft-lozano-tmch-smd-00. 3. Use of a test CA issued certificate that is included in the signed mark or base64 encoded signed mark that is chained to the test CA certificate by the EPP Stub Server. A test certificate in a test Certificate Revocation List (CRL) is also validated by the EPP Stub Server. 4. Sample of poll messaging compliant with draft-tan-epp-launchphase-07 in the EPP Stub Server. 5. A client API that utilizes the packet encoder / decoder (CODEC) along with other code (e.g. transport, configuration, XML parsing pooling) to interface with an EPP server. 6. An EPP Stub Server that includes pre-defined responses to support the client tests. The EPP Stub Server behavior can be easily customized to suite your testing needs. The Launch EPP SDK includes support for RFC 5730, 5731, 5732, 5733, and 5734. Verisign will be integrating the preview of the Launch Phase EPP Extension into its NameStore / SRS Bundle EPP SDK, at which time updates will not be made to the Launch EPP SDK. The Launch EPP SDK is open source, requires Java 6 or higher, and below are the distributions and documents: * Unix Binary Distribution (.tar.gz) - http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-bin.tar.gz * Unix Source Distribution (.tag.gz) - http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-src.tar.gz * Windows Binary Distribution (.zip) - http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-bin.zip * Windows Source Distribution (.zip) - http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-src.zip * Readme File - http://www.verisigninc.com/assets/2-0-0-2/epp-launch.README * Install Instructions - http://www.verisigninc.com/assets/2-0-0-2/epp-launch.INSTALL -- JG [cid:922F2D86-FC79-472E-A0CF-F88984FFA29E] James Gould Principal Software Engineer jgould&lt; at &gt;verisign.com&lt;mailto:jgould&lt; at &gt;verisign.com&gt; 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-03-14T12:46:01 TMCH function spec I-D (draft-lozano-tmch-func-spec-00)published http://comments.gmane.org/gmane.ietf.provreg/2836 <pre>Given it's of relevance to work on the Launchphase extension, the first version of the TMCH function specifications I-D is available at: http://tools.ietf.org/html/draft-lozano-tmch-func-spec-00 There's a call for comment on the ICANN tmch-tech list by March 19th. K. </pre> Keith Gaughan 2013-03-13T11:16:35 Launch Phase EPP Extension Version 07 http://comments.gmane.org/gmane.ietf.provreg/2828 <pre>Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension Mapping to Version 07. The IETF Internet-Draft Submission page is suspended until 2013-03-11, so the draft is attached in TXT and HTML format. We will post the draft once the IETF Internet-Draft Submission page opens. This version includes the following changes: 1. Proof-read grammar and spelling. 2. Changed "pendingAuction" status to "pendingAllocation", changed "pending" to "pendingValidation" status, per proposal from Trung Tran and seconded by Rubens Kuhl. 3. Added text related to the use of RFC 5731 pendingCreate to the Application Identifier section. 4. Added the Poll Messaging section to define the use of poll messaging for intermediate state transitions and pending action poll messaging for final state transitions. Please reply with any feedback. Thanks, JG James F. Gould Verisign Internet Engineering Task Force W. Tan Internet-Draft Cloud Registry Intended status: Standards Track G. Brown Expires: September 5, 2013 CentralNic Ltd J. Gould VeriSign, Inc. March 4, 2013 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) draft-tan-epp-launchphase-07 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name applications during the launch of a domain name registry. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 5, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as Tan, et al. Expires September 5, 2013 [Page 1] Internet-Draft Launch Phase Mapping for EPP March 2013 described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Application Identifier . . . . . . . . . . . . . . . . . . 4 2.2. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 4 2.3. Status Values . . . . . . . . . . . . . . . . . . . . . . 5 2.3.1. State Transition . . . . . . . . . . . . . . . . . . . 7 2.4. Poll Messaging . . . . . . . . . . . . . . . . . . . . . . 8 2.5. Mark Validation Models . . . . . . . . . . . . . . . . . . 9 2.5.1. &lt;launch:codeMark&gt; element . . . . . . . . . . . . . . 10 2.6. Mark . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.7. Digital Signature . . . . . . . . . . . . . . . . . . . . 11 2.7.1. &lt;smd:signedMark&gt; element . . . . . . . . . . . . . . . 11 2.7.2. &lt;smd:encodedSignedMark&gt; element . . . . . . . . . . . 11 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 11 3.1. EPP &lt;check&gt; Command . . . . . . . . . . . . . . . . . . . 12 3.2. EPP &lt;info&gt; Command . . . . . . . . . . . . . . . . . . . . 16 3.3. EPP &lt;create&gt; Command . . . . . . . . . . . . . . . . . . . 20 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 20 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . . 26 3.4. EPP &lt;update&gt; Command . . . . . . . . . . . . . . . . . . . 28 3.5. EPP &lt;delete&gt; Command . . . . . . . . . . . . . . . . . . . 30 3.6. EPP &lt;renew&gt; Command . . . . . . . . . . . . . . . . . . . 31 3.7. EPP &lt;transfer&gt; Command . . . . . . . . . . . . . . . . . . 31 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 32 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 32 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 38 6. Change History . . . . . . . . . . . . . . . . . . . . . . . . 38 6.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . . 38 6.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . . 38 6.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . . 39 6.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . . 39 6.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . . 39 6.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . . 39 6.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . . 40 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 8. Security Considerations . . . . . . . . . . . . . . . . . . . 40 9. Normative References . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 Tan, et al. Expires September 5, 2013 [Page 2] Internet-Draft Launch Phase Mapping for EPP March 2013 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping specifies a flexible schema that can be used to implement several common use cases related to the provisioning and management of domain name applications during the launch of a domain name registry. It is typical for domain registries to operate in special modes during their initial launch to facilitate allocation of domain names, often according to special rules. This document uses the term "launch phase" and the shorter form "launch" to refer to such a period. The EPP domain name mapping [RFC5731] is designed for the steady- state operation of a registry. During a launch period, the model in place may be different from what is defined in EPP domain name mapping [RFC5731]. For example, registries often accept multiple applications for the same domain name during the "Sunrise" launch phase, referred to as a Launch Application. A Launch Registration refers to a registration made during a launch phase when the server uses a "first-come, first-served" model. Even in a "first-come, first-served" model, additional steps and information might be required to support an application, such as trademark information. In addition, the Proposed Trademark Claims Model [1] defines a registry interface for the Trademark Claims or "claims" launch phase that includes support for presenting a Trademark Claims Notice to the Registrant. This document proposes an extension to the domain name extension in order to unambiguously manage the various launch phases known. 1.1. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. "launch-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix "launch" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. Tan, et al. Expires September 5, 2013 [Page 3] Internet-Draft Launch Phase Mapping for EPP March 2013 "signedMark-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [draft-lozano-smd]. The XML namespace prefix "smd" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. "mark-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:mark-1.0" that is defined in [draft-lozano-smd]. The XML namespace prefix "mark" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. 2. Object Attributes This extension adds additional elements to the EPP domain name mapping [RFC5731]. Only those new elements are described here. 2.1. Application Identifier Servers MAY allow multiple applications, referred to as a Launch Application, of the same domain name during its launch phase operations. Upon receiving a valid request to create a Launch Application, the server MUST create an application object corresponding to the request, assign an application identifier for the Launch Application, set the [RFC5731] pendingCreate status, and return the application identifier to the client with the &lt;launch: applicationID&gt; element. In order to facilitate correlation, all subsequent launch operations on the Launch Application MUST be qualified by the previously assigned application identifier using the &lt;launch:applicationID&gt; element. 2.2. Launch Phases The server MAY support multiple launch phases sequentially or simultaneously. The &lt;launch:phase&gt; element MUST be included by the client to define the target launch phase of the command. The following launch phase values are defined: sunrise The phase during which trademark holders can submit registrations or applications with trademark information that can be validated by the server. Tan, et al. Expires September 5, 2013 [Page 4] Internet-Draft Launch Phase Mapping for EPP March 2013 landrush A post-Sunrise phase when non-trademark holders are allowed to register domain names with steps taken to address a large volume of initial registrations. claims1 The Trademark Claims Phase 1, as defined by Trademark Clearinghouse model, in which a full, detailed Claims Notice must be displayed to prospective registrants of domain names that match trademarks. claims2 The Trademark Claims Phase 2, as defined by Trademark Clearinghouse model, in which a short, educational Claims Notice must be displayed to prospective registrants of domain names that match trademarks that have opted in. open A post-launch phase that is also referred to as "steady state". Servers MAY require additional trademark protection during this phase. custom A custom server launch phase that is defined using the "name" attribute. For extensibility, the &lt;launch:phase&gt; element includes an OPTIONAL "name" attribute that can define a sub-phase or the full name of the phase when the &lt;launch:phase&gt; element has the "custom" value. For example, the "claims1" launch phase could have two sub-phases that include "landrush" and "open". 2.3. Status Values A Launch Application object MAY have a status value. The &lt;launch: status&gt; element is used to convey extended status pertaining to the application object, beyond what is specified in the object mapping for this application object. The following status values are defined using the required "s" attribute: pendingValidation: The initial state of a newly-created application object. The application requires validation, but the validation process has not yet completed. validated: The application meets relevant registry rules. invalid: The application does not validate according to registry rules. pendingAllocation: The allocation of the application is pending based on the results of some out-of-band process (for example, an auction). allocated: One of two possible end states of an application object; the object corresponding to the application has been provisioned. rejected: The other possible end state; the object was not provisioned. Tan, et al. Expires September 5, 2013 [Page 5] Internet-Draft Launch Phase Mapping for EPP March 2013 custom: A custom status that is defined using the "name" attribute. Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object. The OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English). For extensibility the &lt;launch:status&gt; element includes an OPTIONAL "name" attribute that can define a sub-status or the full name of the status when the status value is "custom". The server SHOULD NOT use the "custom" status value. Certain status values MAY be combined. For example, an application may be both invalid and rejected. Additionally, certain statuses MAY be skipped. For example, an application MAY immediately start at the "allocated" status or an application MAY skip the "pendingAllocation" status if the server uses a "first-come, first served" model. If the launch phase does not require validation of a request, an application MAY immediately skip to "pendingAllocation". If the &lt;domain:create&gt; command processes a request synchronously without the use of an intermediate application, then an Application Identifier (Section 2.1) is not needed along with the application status. Tan, et al. Expires September 5, 2013 [Page 6] Internet-Draft Launch Phase Mapping for EPP March 2013 2.3.1. State Transition | request | v +-------------------+ | | | pendingValidation | | | +---------+---------+ | | +-----------+-----------+ | | | | v v +-----------+ +---------+ | | | | | validated | | invalid | | | | | +-----+-----+ +----+----+ | | | | v | +-------------------+ | | | | | pendingAllocation | | | | | +-------------------+ | | | | | +-----------------------+ | | | | v v +---------+ +--------+ / \ / \ | allocated | | rejected | \ / \ / +---------+ +--------+ Figure 1 Tan, et al. Expires September 5, 2013 [Page 7] Internet-Draft Launch Phase Mapping for EPP March 2013 2.4. Poll Messaging A Launch Application is handled as a domain name of [RFC5731] in "pendingCreate" status, with the Launch Application status values defined in Section 2.3. As a Launch Application transitions between the status values defined in Section 2.3, the server SHOULD insert poll messages, per [RFC5730], for the applicable intermediate statuses, including the "pendingValidation", "validated", "pendingAllocation, and "invalid" statuses, using the &lt;domain: infData&gt; element with the &lt;launch:infData&gt; extension. The server MUST insert a &lt;domain:panData&gt; poll message, per [RFC5731], with the &lt;launch:infData&gt; extension for the final statuses, including the "allocated" and "rejected" statuses. The following is an example poll message for a Launch Application that has transitioned to the "pendingAllocation" state. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1301"&gt; &lt;msg&gt;Command completed successfully; ack to dequeue&lt;/msg&gt; &lt;/result&gt; &lt;msgQ count="5" id="12345"&gt; &lt;qDate&gt;2013-04-04T22:01:00.0Z&lt;/qDate&gt; &lt;msg&gt;Application pendingAllocation.&lt;/msg&gt; &lt;/msgQ&gt; &lt;resData&gt; &lt;domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; ... &lt;/domain:infData&gt; &lt;/resData&gt; &lt;extension&gt; &lt;launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;launch:status s="pendingAllocation"/&gt; &lt;/launch:infData&gt; &lt;/extension&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 8] Internet-Draft Launch Phase Mapping for EPP March 2013 The following is an example &lt;domain:panData&gt; poll message for an "allocated" Launch Application. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1301"&gt; &lt;msg&gt;Command completed successfully; ack to dequeue&lt;/msg&gt; &lt;/result&gt; &lt;msgQ count="5" id="12345"&gt; &lt;qDate&gt;2013-04-04T22:01:00.0Z&lt;/qDate&gt; &lt;msg&gt;Application successfully allocated.&lt;/msg&gt; &lt;/msgQ&gt; &lt;resData&gt; &lt;domain:panData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name paResult="1"&gt;example.tld&lt;/domain:name&gt; &lt;domain:paTRID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/domain:paTRID&gt; &lt;domain:paDate&gt;2013-04-04T22:00:00.0Z&lt;/domain:paDate&gt; &lt;/domain:panData&gt; &lt;/resData&gt; &lt;extension&gt; &lt;launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;launch:status s="allocated"/&gt; &lt;/launch:infData&gt; &lt;/extension&gt; &lt;trID&gt; &lt;clTRID&gt;BCD-23456&lt;/clTRID&gt; &lt;svTRID&gt;65432-WXY&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 2.5. Mark Validation Models A server MUST support at least one of the following models for validating trademark information: Tan, et al. Expires September 5, 2013 [Page 9] Internet-Draft Launch Phase Mapping for EPP March 2013 code Use of a mark code by itself to validate that the mark matches the domain name. This model is supported using the &lt;launch: codeMark&gt; element with just the &lt;launch:code&gt; element. mark The mark information is passed without any other validation element. The server will use some custom form of validation to validate that the mark information is authentic. This model is supported using the &lt;launch:codeMark&gt; element with just the &lt;mark: mark&gt; (Section 2.6) element. code with mark: A code is used along with the mark information by the server to validate the mark utilizing an external party. The code represents some form of secret that matches the mark information passed. This model is supported using the &lt;launch: codeMark&gt; element that contains both the &lt;launch:code&gt; and the &lt;mark:mark&gt; (Section 2.6) elements. signed mark: The mark information is digitally signed as described in the Digital Signature (Section 2.7) section. The digital signature can be directly validated by the server using the public key of the external party that created the signed mark using its private key. This model is supported using the &lt;smd:signedMark&gt; (Section 2.7.1) and &lt;smd:encodedSignedMark&gt; (Section 2.7.2) elements. More than one &lt;launch:codeMark&gt;, &lt;smd:signedMark&gt; (Section 2.7.1), or &lt;smd:encodedSignedMark&gt; (Section 2.7.2) element MAY be specified. The maximum number of marks per domain name is up to server policy. 2.5.1. &lt;launch:codeMark&gt; element The &lt;launch:codeMark&gt; element that is used by the "code", "mark", and "code with mark" validation models, has the following child elements: &lt;launch:code&gt;: OPTIONAL mark code used to validate the &lt;mark:mark&gt; (Section 2.6) information. The mark code is be a mark-specific secret that the server can verify against a third party. &lt;mark:mark&gt;: OPTIONAL mark information with child elements defined in the Mark (Section 2.6) section. The following is an example &lt;launch:codeMark&gt; element with both a &lt;launch:code&gt; and &lt;mark:mark&gt; (Section 2.6) element. &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AC&lt;/launch:code&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:codeMark&gt; Tan, et al. Expires September 5, 2013 [Page 10] Internet-Draft Launch Phase Mapping for EPP March 2013 2.6. Mark A &lt;mark:mark&gt; element describes an applicant's prior right to a given domain name that is used with the "mark", "mark with code", and the "signed mark" validation models. The &lt;mark:mark&gt; element is defined in [draft-lozano-smd]. A new mark format can be supported by creating a new XML schema for the mark that has an element that substitutes for the &lt;mark:abstractMark&gt; element from [draft-lozano-smd]. 2.7. Digital Signature Digital signatures MAY be used by the server to validate either the mark information, when using the "signed mark" validation model with the &lt;smd:signedMark&gt; (Section 2.7.1) element or the &lt;smd: encodedSignedMark&gt; (Section 2.7.2) element. 2.7.1. &lt;smd:signedMark&gt; element The &lt;smd:signedMark&gt; element contains the digitally signed mark information. The &lt;smd:signedMark&gt; element is defined in [draft-lozano-smd]. A new signed mark format can be supported by creating a new XML schema for the signed mark that has an element that substitutes for the &lt;smd:abstractSignedMark&gt; element from [draft-lozano-smd]. 2.7.2. &lt;smd:encodedSignedMark&gt; element The &lt;smd:encodedSignedMark&gt; element contains an encoded form of the digitally signed &lt;smd:signedMark&gt; (Section 2.7.1) element. The &lt;smd: encodedSignedMark&gt; element is defined in [draft-lozano-smd]. A new encoded signed mark format can be supported by creating a new XML schema for the encoded signed mark that has an element that substitutes for the &lt;smd:encodedSignedMark&gt; element from [draft-lozano-smd]. 3. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in the Launch Phase Extension. This mapping is designed to be flexible, requiring only a minimum set of required elements. While it is meant to serve several use cases, it does not prescribe Tan, et al. Expires September 5, 2013 [Page 11] Internet-Draft Launch Phase Mapping for EPP March 2013 any interpretation by the client or server. Such processing is typically highly policy-dependent and therefore specific to implementations. Operations on application objects are done via one or more of the existing EPP verbs defined in the EPP domain name mapping [RFC5731]. Registries may choose to support a subset of the operations. 3.1. EPP &lt;check&gt; Command This extension defines additional elements to extend the EPP &lt;check&gt; command and response to be used in conjunction with the EPP domain name mapping [RFC5731]. This extension defines a new command called the Claims Check Command that is used to determine whether or not there are any matching trademarks, in the specified launch phase, for each domain name passed in the command. The availability check information defined in the EPP domain name mapping [RFC5731] MUST NOT be returned for the Claims Check Command. Instead of returning whether the domain name is available, the Claims Check Command will return whether or not at least one matching trademark exists for the domain name. If there is at least one matching trademark that exists for the domain name, a &lt;launch: claimKey&gt; element is returned. The client may then use the value of the &lt;launch:claimKey&gt; element to obtain information needed to generate the trademark Claims Notice from a third-party trademark validator such as the Trademark Clearinghouse (TMCH). The third party trademark validator should also return a unique notice identifier that can be passed in the &lt;launch:noticeID&gt; element of the extension to the Create Command (Section 3.3). The &lt;domain:name&gt; elements in the EPP &lt;check&gt; command of EPP domain name mapping [RFC5731] define the domain names to check for matching trademarks. The &lt;launch:check&gt; element contains the following child elements: &lt;launch:phase&gt; The launch phase, with a value of either "claims1" or "claims2" to indicate that the command is a Claims Check Command. The "claims1" Claims Check Command will match the &lt;domain:name&gt; against the full list of trademark labels. The "claims2" Claims Check Command will match the &lt;domain:name&gt; against the list of trademark labels that opted into the "claims2" launch phase. Tan, et al. Expires September 5, 2013 [Page 12] Internet-Draft Launch Phase Mapping for EPP March 2013 Example Claims Check command using the &lt;check&gt; domain command and the &lt;launch:check&gt; extension to determine if "example1.tld" and "example2.tld" have any matching trademarks during the "claims1" launch phase: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;check&gt; &lt;domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example1.tld&lt;/domain:name&gt; &lt;domain:name&gt;example2.tld&lt;/domain:name&gt; &lt;/domain:check&gt; &lt;/check&gt; &lt;extension&gt; &lt;launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims1&lt;/launch:phase&gt; &lt;/launch:check&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Example Claims Check Command using the &lt;check&gt; domain command and the &lt;launch:check&gt; extension to determine if "example3.tld" and "example4.tld" have any matching trademarks that opted into the "claims2" launch phase: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;check&gt; &lt;domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example3.tld&lt;/domain:name&gt; &lt;domain:name&gt;example4.tld&lt;/domain:name&gt; &lt;/domain:check&gt; &lt;/check&gt; &lt;extension&gt; &lt;launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims2&lt;/launch:phase&gt; &lt;/launch:check&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; Tan, et al. Expires September 5, 2013 [Page 13] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;/epp&gt; If the &lt;check&gt; command has been processed successfully, the EPP &lt;resData&gt; element MUST contain a child &lt;launch:chkData&gt; element that identifies the launch namespace. The &lt;launch:chkData&gt; element contains the following child elements: &lt;launch:phase&gt; The launch phase, with a value of either "claims1" or "claims2", which matches the associated Claims Check Command &lt;launch:phase&gt;. &lt;launch:cd&gt; One or more &lt;launch:cd&gt; elements that contain the following child elements: &lt;launch:name&gt; Contains the fully qualified name of the queried domain name. This element MUST contain an "exists" attribute whose value indicates if a matching trademark exists for the domain name. A value of "1" (or "true") means that a matching trademark does exist for the claims launch phase. A value of "0" (or "false") means that a matching trademark does not exist. &lt;launch:claimKey&gt; An OPTIONAL claim key that MAY be passed to a third-party trademark validator such as the Trademark Clearinghouse (TMCH) for querying the information needed to generate a Trademark Claims Notice. The &lt;launch:claimKey&gt; is used as the key for the query in place of the domain name to securely query the service without using a well-known value like a domain name. Tan, et al. Expires September 5, 2013 [Page 14] Internet-Draft Launch Phase Mapping for EPP March 2013 Example Claims Check response when no matching trademarks are found for the domain name example1.tld and matching trademarks are found for the domain name example2.tld for the "claims1" launch phase: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;launch:chkData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims1&lt;/launch:phase&gt; &lt;launch:cd&gt; &lt;launch:name exists="0"&gt;example1.tld&lt;/launch:name&gt; &lt;/launch:cd&gt; &lt;launch:cd&gt; &lt;launch:name exists="1"&gt;example2.tld&lt;/launch:name&gt; &lt;launch:claimKey&gt;abc123&lt;/launch:claimKey&gt; &lt;/launch:cd&gt; &lt;/launch:chkData&gt; &lt;/resData&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 15] Internet-Draft Launch Phase Mapping for EPP March 2013 Example Claims Check response when no matching trademarks are found for the domain name example3.tld and matching trademarks are found for the domain name example4.tld for the "claims2" launch phase: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;launch:chkData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims2&lt;/launch:phase&gt; &lt;launch:cd&gt; &lt;launch:name exists="0"&gt;example3.tld&lt;/launch:name&gt; &lt;/launch:cd&gt; &lt;launch:cd&gt; &lt;launch:name exists="1"&gt;example4.tld&lt;/launch:name&gt; &lt;launch:claimKey&gt;abc123&lt;/launch:claimKey&gt; &lt;/launch:cd&gt; &lt;/launch:chkData&gt; &lt;/resData&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.2. EPP &lt;info&gt; Command This extension defines additional elements to extend the EPP &lt;info&gt; command and response to be used in conjunction with the EPP domain name mapping [RFC5731]. The EPP &lt;info&gt; command is used to retrieve information for a launch phase registration or application. The Application Identifier (Section 2.1) returned in the &lt;launch:creData&gt; element of the create response (Section 3.3) is used for retrieving information for a Launch Application. A &lt;launch:info&gt; element is sent along with the regular &lt;info&gt; domain command. The &lt;launch:info&gt; element includes an OPTIONAL "includeMark" boolean attribute, with a default value of "false", to indicate whether or not to include the mark in the response. The &lt;launch:info&gt; element contains the following child elements: Tan, et al. Expires September 5, 2013 [Page 16] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;launch:phase&gt; The phase during which the application or registration was submitted or is associated with. Server policy defines the phases that are supported. &lt;launch:applicationID&gt; OPTIONAL application identifier of the Launch Application. Example &lt;info&gt; domain command with the &lt;launch:info&gt; extension to retrieve information for the sunrise application for example.tld and application identifier "abc123": &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;info&gt; &lt;domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;/domain:info&gt; &lt;/info&gt; &lt;extension&gt; &lt;launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" includeMark="true"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;/launch:info&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 17] Internet-Draft Launch Phase Mapping for EPP March 2013 Example &lt;info&gt; domain command with the &lt;launch:info&gt; extension to retrieve information for the sunrise registration for example.tld: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;info&gt; &lt;domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;/domain:info&gt; &lt;/info&gt; &lt;extension&gt; &lt;launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;/launch:info&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; If the query was successful, the server replies with a &lt;launch: infData&gt; element along with the regular EPP &lt;resData&gt;. The &lt;launch: infData&gt; contains the following child elements: &lt;launch:phase&gt; The phase during which the application was submitted, or is associated with, that matches the associated &lt;info&gt; command &lt;launch:phase&gt;. &lt;launch:applicationID&gt; OPTIONAL Application Identifier of the Launch Application. &lt;launch:status&gt; OPTIONAL status of the Launch Application using one of the supported status values (Section 2.3). &lt;mark:mark&gt; Zero or more &lt;mark:mark&gt; (Section 2.6) elements. Tan, et al. Expires September 5, 2013 [Page 18] Internet-Draft Launch Phase Mapping for EPP March 2013 Example &lt;info&gt; domain response using the &lt;launch:infData&gt; extension with the mark information: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:roid&gt;EXAMPLE1-REP&lt;/domain:roid&gt; &lt;domain:status s="pendingCreate"/&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:clID&gt;ClientX&lt;/domain:clID&gt; &lt;domain:crID&gt;ClientY&lt;/domain:crID&gt; &lt;domain:crDate&gt;2012-04-03T22:00:00.0Z&lt;/domain:crDate&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:infData&gt; &lt;/resData&gt; &lt;extension&gt; &lt;launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;launch:status s="pendingValidation"/&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:infData&gt; &lt;/extension&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 19] Internet-Draft Launch Phase Mapping for EPP March 2013 3.3. EPP &lt;create&gt; Command There are two forms of the extension to the EPP &lt;create&gt; command that are dependent on the supported launch phases (Section 2.2) as defined below: sunrise The EPP &lt;create&gt; command with the "sunrise" launch phase is used to submit a registration with trademark information that can be verified by the server with the &lt;domain:name&gt; value. The Sunrise Create Form (Section 3.3.1) is used for the "sunrise" launch phase. Optionally, the server can support multiple overlapping applications that are chosen asynchronously with a server generated Application Identifier (Section 2.1) for later reference. landrush The EPP &lt;create&gt; command with the "landrush" launch phase is undefined but the form supported is up to server policy. claims1 The EPP &lt;create&gt; command with the "claims1" launch phase is used to pass the information associated with the presentation and acceptance of the "claims1" Claims Notice. The Claims Create Form (Section 3.3.2) is used for the "claims1" launch phase. claims2 The EPP &lt;create&gt; command with the "claims2" launch phase is used to pass the information associated with the presentation of the "claims2" Claims Notice. The Claims Create Form (Section 3.3.2) is used for the "claims2" launch phase. open The EPP &lt;create&gt; command with the "open" launch phase is undefined but the form supported is up to server policy. custom The EPP &lt;create&gt; command with the "custom" launch phase is undefined but the form supported is up to server policy. 3.3.1. Sunrise Create Form The Sunrise Create Form of the extension to the EPP domain name mapping [RFC5731] includes the verifiable trademark information that the server uses to match against the domain name to authorize the domain create. A server MUST support one of four models in Claim Validation Models (Section 2.5) to verify the trademark information passed by the client. A &lt;launch:create&gt; element is sent along with the regular &lt;create&gt; domain command. The &lt;launch:create&gt; element contains the following child elements: &lt;launch:phase&gt; The identifier for the launch phase. &lt;launch:codeMark&gt; or &lt;smd:signedMark&gt; or &lt;smd:encodedSignedMark&gt; Tan, et al. Expires September 5, 2013 [Page 20] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;launch:codeMark&gt; Zero or more &lt;launch:codeMark&gt; elements. The &lt;launch:codeMark&gt; child elements are defined in the &lt;launch: codeMark&gt; element (Section 2.5.1) section. &lt;smd:signedMark&gt; Zero or more &lt;smd:signedMark&gt; elements. The &lt;smd:signedMark&gt; child elements are defined in the &lt;smd: signedMark&gt; element (Section 2.7.1) section. &lt;smd:encodedSignedMark&gt; Zero or more &lt;smd:encodedSignedMark&gt; elements. The &lt;smd:encodedSignedMark&gt; child elements are defined in the &lt;smd:encodedSignedMark&gt; element (Section 2.7.2) section. The following is an example &lt;create&gt; domain command using the &lt;launch:create&gt; extension, following the "code" validation model, with multiple sunrise codes: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AC&lt;/launch:code&gt; &lt;/launch:codeMark&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AD&lt;/launch:code&gt; &lt;/launch:codeMark&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AE&lt;/launch:code&gt; &lt;/launch:codeMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 21] Internet-Draft Launch Phase Mapping for EPP March 2013 The following is an example &lt;create&gt; domain command using the &lt;launch:create&gt; extension, following the "mark" validation model, with the mark information: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;exampleone.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:codeMark&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:codeMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 22] Internet-Draft Launch Phase Mapping for EPP March 2013 The following is an example &lt;create&gt; domain command using the &lt;launch:create&gt; extension, following the "code with mark" validation model, with a code and mark information: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AC&lt;/launch:code&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:codeMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 23] Internet-Draft Launch Phase Mapping for EPP March 2013 The following is an example &lt;create&gt; domain command using the &lt;launch:create&gt; extension, following the "signed mark" validation model, with the signed mark information: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;exampleone.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;smd:signedMark id="signedMark" xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"&gt; ... &lt;/smd:signedMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 24] Internet-Draft Launch Phase Mapping for EPP March 2013 The following is an example &lt;create&gt; domain command using the &lt;launch:create&gt; extension, following the "signed mark" validation model, with the base64 encoded signed mark information: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;exampleone.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;smd:encodedSignedMark xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"&gt; ... &lt;/smd:encodedSignedMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; If the create was successful, the server MAY reply with the &lt;launch: creData&gt; element along with the regular EPP &lt;resData&gt; to indicate the server generated Application Identifier (Section 2.1), when multiple applications of a given domain name is supported; otherwise no extension is included with the regular EPP &lt;resData&gt;. The &lt;launch: creData&gt; element contains the following child elements: &lt;launch:phase&gt; The phase of the application that mirrors the &lt;launch:phase&gt; element included in the &lt;launch:create&gt;. &lt;launch:applicationID&gt; The application identifier of the application. Tan, et al. Expires September 5, 2013 [Page 25] Internet-Draft Launch Phase Mapping for EPP March 2013 An example response when multiple overlapping applications are supported by the server: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1001"&gt; &lt;msg&gt;Command completed successfully; action pending&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;domain:creData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:crDate&gt;2010-08-10T15:38:26.623854Z&lt;/domain:crDate&gt; &lt;domain:exDate&gt;2012-08-10T15:38:26.623854Z&lt;/domain:exDate&gt; &lt;/domain:creData&gt; &lt;/resData&gt; &lt;extension&gt; &lt;launch:creData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;2393-9323-E08C-03B1 &lt;/launch:applicationID&gt; &lt;/launch:creData&gt; &lt;/extension&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.3.2. Claims Create Form The Claims Create Form of the extension to the EPP domain name mapping [RFC5731] includes the information related to the registrant's acceptance of the Claims Notice for the "claims1" launch phase and the display of the Claims Notice for the "claims2" launch phase. A &lt;launch:create&gt; element is sent along with the regular &lt;create&gt; domain command. The &lt;launch:create&gt; element contains the following child elements: Tan, et al. Expires September 5, 2013 [Page 26] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;launch:phase&gt; MUST contain the value of "claims1" or "claim2" to indicate the claims launch phase. &lt;launch:notice&gt; &lt;launch:noticeID&gt; Unique notice identifier generated by the source of the Claims Notice information such as the Claims Notice Information Service (CNIS). &lt;launch:generatedDate&gt; Contains the date and time that the Claims Notice was generated. &lt;launch:acceptedDate&gt; Contains the date and time that the Claims Notice was displayed or accepted. &lt;launch:source&gt; Contains the source information of the end-user client that was shown, or that accepted, the Claims Notice, such the end-user client's IP address. The following is an example &lt;create&gt; domain command using the &lt;launch:create&gt; extension with the &lt;launch:notice&gt; information for the "claims1" claims launch phase: Tan, et al. Expires September 5, 2013 [Page 27] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims1&lt;/launch:phase&gt; &lt;launch:notice&gt; &lt;launch:noticeID&gt;49FD46E6C4B45C55D4AC&lt;/launch:noticeID&gt; &lt;launch:generatedDate&gt;2012-06-19T09:00:10.0Z &lt;/launch:generatedDate&gt; &lt;launch:acceptedDate&gt;2012-06-19T09:01:30.0Z &lt;/launch:acceptedDate&gt; &lt;launch:source&gt;192.0.2.29&lt;/launch:source&gt; &lt;/launch:notice&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; This extension does not define any extension to the response of a &lt;create&gt; domain command for the Claims Create Form. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731]. 3.4. EPP &lt;update&gt; Command This extension defines additional elements to extend the EPP &lt;update&gt; command to be used in conjunction with the domain name mapping. A server that does not support multiple applications of a given domain name with an Application Identifier (Section 2.1) during its launch phase operations MUST return an EPP error result code of 2102. Registry policies permitting, clients may update an application Tan, et al. Expires September 5, 2013 [Page 28] Internet-Draft Launch Phase Mapping for EPP March 2013 object by submitting an EPP &lt;update&gt; command along with a &lt;launch: update&gt; element to indicate the application object to be updated. The &lt;launch:update&gt; element contains the following child elements: &lt;launch:phase&gt; The phase during which the application was submitted or is associated with. &lt;launch:applicationID&gt; The application identifier for which the client wishes to update. This extension does not define any extension to the response of an &lt;update&gt; domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731]. The following is an example &lt;update&gt; domain command with the &lt;launch: update&gt; extension to add and remove a name server of a sunrise application with the application identifier "abc123": &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;update&gt; &lt;domain:update xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:add&gt; &lt;domain:ns&gt; &lt;domain:hostObj&gt;ns2.example.tld&lt;/domain:hostObj&gt; &lt;/domain:ns&gt; &lt;/domain:add&gt; &lt;domain:rem&gt; &lt;domain:ns&gt; &lt;domain:hostObj&gt;ns1.example.tld&lt;/domain:hostObj&gt; &lt;/domain:ns&gt; &lt;/domain:rem&gt; &lt;/domain:update&gt; &lt;/update&gt; &lt;extension&gt; &lt;launch:update xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;/launch:update&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires September 5, 2013 [Page 29] Internet-Draft Launch Phase Mapping for EPP March 2013 An example response that corresponds to the above command: &lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.5. EPP &lt;delete&gt; Command This extension defines additional elements to extend the EPP &lt;delete&gt; command to be used in conjunction with the domain name mapping. A server that does not support multiple applications of a given domain name with an Application Identifier (Section 2.1) during its launch phase operations MUST return an EPP error result code of 2102. Registry policies permitting, clients MAY withdraw an application by submitting an EPP &lt;delete&gt; command along with a &lt;launch:delete&gt; element to indicate the application object to be deleted. The &lt;launch:delete&gt; element contains the following child elements: &lt;launch:phase&gt; The phase during which the application was submitted or is associated with. &lt;launch:applicationID&gt; The application identifier for which the client wishes to delete. This extension does not define any extension to the response of a &lt;delete&gt; domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731]. Tan, et al. Expires September 5, 2013 [Page 30] Internet-Draft Launch Phase Mapping for EPP March 2013 The following is an example &lt;delete&gt; domain command with the &lt;launch: delete&gt; extension: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;delete&gt; &lt;domain:delete xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;/domain:delete&gt; &lt;/delete&gt; &lt;extension&gt; &lt;launch:delete xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;/launch:delete&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; An example response that corresponds to the above command: &lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.6. EPP &lt;renew&gt; Command This extension does not define any extension to the EPP &lt;renew&gt; command or response described in the EPP domain name mapping [RFC5731]. 3.7. EPP &lt;transfer&gt; Command This extension does not define any extension to the EPP &lt;transfer&gt; command or response described in the EPP domain name mapping Tan, et al. Expires September 5, 2013 [Page 31] Internet-Draft Launch Phase Mapping for EPP March 2013 [RFC5731]. 4. Formal Syntax One schema is presented here that is the EPP Launch Phase Mapping schema. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. 4.1. Launch Schema Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BEGIN &lt;?xml version="1.0" encoding="UTF-8"?&gt; Tan, et al. Expires September 5, 2013 [Page 32] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;schema targetNamespace="urn:ietf:params:xml:ns:launch-1.0" xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:mark="urn:ietf:params:xml:ns:mark-1.0" xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"&gt; &lt;!-- Import common element types. --&gt; &lt;import namespace="urn:ietf:params:xml:ns:eppcom-1.0" schemaLocation="eppcom-1.0.xsd"/&gt; &lt;import namespace="urn:ietf:params:xml:ns:mark-1.0" schemaLocation="mark-1.0.xsd"/&gt; &lt;import namespace="urn:ietf:params:xml:ns:signedMark-1.0" schemaLocation="signedMark-1.0.xsd"/&gt; &lt;annotation&gt; &lt;documentation&gt; Extensible Provisioning Protocol v1.0 domain name extension schema for the launch phase processing. &lt;/documentation&gt; &lt;/annotation&gt; &lt;!-- Child elements found in EPP commands. --&gt; &lt;element name="check" type="launch:checkType"/&gt; &lt;element name="info" type="launch:infoType"/&gt; &lt;element name="create" type="launch:createType"/&gt; &lt;element name="update" type="launch:idContainerType"/&gt; &lt;element name="delete" type="launch:idContainerType"/&gt; &lt;!-- Common container of id (identifier) element --&gt; &lt;complexType name="idContainerType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;element name="applicationID" type="launch:applicationIDType"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; Tan, et al. Expires September 5, 2013 [Page 33] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;!-- Definition for application identifier --&gt; &lt;simpleType name="applicationIDType"&gt; &lt;restriction base="token"/&gt; &lt;/simpleType&gt; &lt;!-- Definition for launch phase. Name is an optional attribute used to extend the phase type. For example, when using the phase type value of &amp;qt;custom&amp;gt;, the name can be used to specify the custom phase. --&gt; &lt;complexType name="phaseType"&gt; &lt;simpleContent&gt; &lt;extension base="launch:phaseTypeValue"&gt; &lt;attribute name="name" type="token"/&gt; &lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;!-- Enumeration of for launch phase values. --&gt; &lt;simpleType name="phaseTypeValue"&gt; &lt;restriction base="token"&gt; &lt;enumeration value="sunrise"/&gt; &lt;enumeration value="landrush"/&gt; &lt;enumeration value="claims1"/&gt; &lt;enumeration value="claims2"/&gt; &lt;enumeration value="open"/&gt; &lt;enumeration value="custom"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Definition for the sunrise code --&gt; &lt;simpleType name="codeType"&gt; &lt;restriction base="base64Binary"&gt; &lt;minLength value="1"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Definition for the notice identifier --&gt; Tan, et al. Expires September 5, 2013 [Page 34] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;simpleType name="noticeIDType"&gt; &lt;restriction base="base64Binary"&gt; &lt;minLength value="1"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Possible status values for sunrise application --&gt; &lt;simpleType name="statusValueType"&gt; &lt;restriction base="token"&gt; &lt;enumeration value="pendingValidation"/&gt; &lt;enumeration value="validated"/&gt; &lt;enumeration value="invalid"/&gt; &lt;enumeration value="pendingAllocation"/&gt; &lt;enumeration value="allocated"/&gt; &lt;enumeration value="rejected"/&gt; &lt;enumeration value="custom"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Status type definition --&gt; &lt;complexType name="statusType"&gt; &lt;simpleContent&gt; &lt;extension base="normalizedString"&gt; &lt;attribute name="s" type="launch:statusValueType" use="required"/&gt; &lt;attribute name="lang" type="language" default="en"/&gt; &lt;attribute name="name" type="token"/&gt; &lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;!-- codeMark Type that contains an optional code with mark information. --&gt; &lt;complexType name="codeMarkType"&gt; &lt;sequence&gt; &lt;element name="code" type="launch:codeType" minOccurs="0"/&gt; &lt;element ref="mark:abstractMark" minOccurs="0"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; Tan, et al. Expires September 5, 2013 [Page 35] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;!-- Child elements for the create command --&gt; &lt;complexType name="createType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;choice&gt; &lt;element name="codeMark" type="launch:codeMarkType" maxOccurs="unbounded"/&gt; &lt;element ref="smd:abstractSignedMark" maxOccurs="unbounded"/&gt; &lt;element ref="smd:encodedSignedMark" maxOccurs="unbounded"/&gt; &lt;element name="notice" type="launch:createNoticeType"/&gt; &lt;/choice&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;!-- Child elements of the create notice element. --&gt; &lt;complexType name="createNoticeType"&gt; &lt;sequence&gt; &lt;element name="noticeID" type="launch:noticeIDType"/&gt; &lt;element name="generatedDate" type="dateTime"/&gt; &lt;element name="acceptedDate" type="dateTime"/&gt; &lt;element name="source" type="token"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;!-- Child elements of check (Claims Check Command). --&gt; &lt;complexType name="checkType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;!-- Child elements of info command. --&gt; &lt;complexType name="infoType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; Tan, et al. Expires September 5, 2013 [Page 36] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;element name="applicationID" type="launch:applicationIDType" minOccurs="0"/&gt; &lt;/sequence&gt; &lt;attribute name="includeMark" type="boolean" default="false"/&gt; &lt;/complexType&gt; &lt;!-- Child response elements. --&gt; &lt;element name="chkData" type="launch:chkDataType"/&gt; &lt;element name="creData" type="launch:idContainerType"/&gt; &lt;element name="infData" type="launch:infDataType"/&gt; &lt;!-- &lt;check&gt; response elements. --&gt; &lt;complexType name="chkDataType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;element name="cd" type="launch:cdType" maxOccurs="unbounded"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;complexType name="cdType"&gt; &lt;sequence&gt; &lt;element name="name" type="launch:cdNameType"/&gt; &lt;element name="claimKey" type="token" minOccurs="0"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;complexType name="cdNameType"&gt; &lt;simpleContent&gt; &lt;extension base="eppcom:labelType"&gt; &lt;attribute name="exists" type="boolean" use="required"/&gt; &lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;!-- &lt;info&gt; response elemenets --&gt; &lt;complexType name="infDataType"&gt; &lt;sequence&gt; Tan, et al. Expires September 5, 2013 [Page 37] Internet-Draft Launch Phase Mapping for EPP March 2013 &lt;element name="phase" type="launch:phaseType"/&gt; &lt;element name="applicationID" type="launch:applicationIDType" minOccurs="0"/&gt; &lt;element name="status" type="launch:statusType" minOccurs="0"/&gt; &lt;element ref="mark:abstractMark" minOccurs="0" maxOccurs="unbounded"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;/schema&gt; END 5. Acknowledgements The authors wish to acknowledge the efforts of the leading participants of the Community TMCH Model that led to many of the changes to this document, which include Chris Wright, Jeff Neuman, Jeff Eckhaus, and Will Shorter. Special suggestions that have been incorporated into this document were provided by Jothan Frakes, Keith Gaughan, Jan Jansen, Rubens Kuhl, Gustavo Lozano, Klaus Malorny, Patrick Mevzek, Bernhard Reutner-Fischer, Trung Tran, Ulrich Wisser and Sharon Wodjenski. 6. Change History 6.1. Change from 00 to 01 1. Changed to use camel case for the XML elements. 2. Replaced "cancelled" status to "rejected" status. 3. Added the child elements of the &lt;claim&gt; element. 4. Removed the XML schema and replaced with "[TBD]". 6.2. Change from 01 to 02 1. Added support for both the ICANN and ARI/Neustar TMCH models. 2. Changed the namespace URI and prefix to use "launch" instead of "launchphase". 3. Added definition of multiple claim validation models. 4. Added the &lt;launch:signedClaim&gt; and &lt;launch:signedNotice&gt; elements. 5. Added support for Claims Info Command Tan, et al. Expires September 5, 2013 [Page 38] Internet-Draft Launch Phase Mapping for EPP March 2013 6.3. Change from 02 to 03 1. Removed XSI namespace per Keith Gaughan's suggestion on the provreg list. 2. Added extensibility to the launch:status element and added the pendingAuction status per Trung Tran's feedback on the provreg list. 3. Added support for the Claims Check Command, updated the location and contents of the signedNotice, and replaced most references of Claim to Mark based on the work being done on the ARI/Neustar launch model. 6.4. Change from 03 to 04 1. Removed references to the ICANN model. 2. Removed support for the Claims Info Command. 3. Removed use of the signedClaim. 4. Revised the method for referring to the signedClaim from the XML Signature using the IDREF URI. 5. Split the launch-1.0.xsd into three XML schemas including launch- 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 6. Split the "claims" launch phase to the "claims1" and "claims2" launch phases. 7. Added support for the encodedSignedMark with base64 encoded signedMark. 8. Changed the elements in the createNoticeType to include the noticeID, timestamp, and the source elements. 9. Added the class and effectiveDate elements to mark. 6.5. Change from 04 to 05 1. Removed reference to &lt;smd:zone&gt; in the &lt;smd:signedMark&gt; example. 2. Incorporated feedback from Bernhard Reutner-Fischer on the provreg mail list. 3. Added missing launch XML prefix to applicationIDType reference in the idContainerType of the Launch Schema. 4. Added missing description of the &lt;mark:pc&gt; element in the &lt;mark: addr&gt; element. 5. Updated note on replication of the EPP contact mapping elements in the Mark Contact section. 6.6. Change from 05 to 06 1. Removed the definition of the mark-1.0 and signedMark-1.0 and replaced with reference to draft-lozano-smd, that contains the definition for the mark, signed marked, and encoded signed mark. Tan, et al. Expires September 5, 2013 [Page 39] Internet-Draft Launch Phase Mapping for EPP March 2013 2. Split the &lt;launch:timestamp&gt; into &lt;launch:generatedDate&gt; and &lt;launch:acceptedDate&gt; based on feedback from Trung Tran. 3. Added the "includeMark" optional attribute to the &lt;launch:info&gt; element to enable the client to request whether or not to include the mark in the info response. 4. Fixed state diagram to remove redundant transition from "invalid" to "rejected"; thanks Klaus Malorny. 6.7. Change from 06 to 07 1. Proof-read grammar and spelling. 2. Changed "pendingAuction" status to "pendingAllocation", changed "pending" to "pendingValidation" status, per proposal from Trung Tran and seconded by Rubens Kuhl. 3. Added text related to the use of RFC 5731 pendingCreate to the Application Identifier section. 4. Added the Poll Messaging section to define the use of poll messaging for intermediate state transitions and pending action poll messaging for final state transitions. 7. IANA Considerations This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. Three URI assignments have been registered by the IANA. Registration request for the Launch namespace: URI: urn:ietf:params:xml:ns:launch-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. 8. Security Considerations The mapping extensions described in this document do not provide any security services beyond those described by EPP [RFC5730], the EPP domain name mapping [RFC5731], and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. Updates to, and deletion of an application object must be restricted to clients authorized to perform the said operation on the object. As information contained within an application, or even the mere fact that an application exists may be confidential. Any attempt to Tan, et al. Expires September 5, 2013 [Page 40] Internet-Draft Launch Phase Mapping for EPP March 2013 operate on an application object by an unauthorized client MUST be rejected with an EPP 2303 (object does not exist) or an appropriate auhorization error. Server policy may allow &lt;info&gt; operation with filtered output by clients other than the sponsoring client, in which case the &lt;domain:infData&gt; and &lt;launch:infData&gt; response SHOULD be filtered to include only fields that are publicly accessible. 9. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009. [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, August 2009. [draft-lozano-smd] Lozano, G., "Mark and Signed Mark Objects Mapping". [1] &lt;http://newgtlds.icann.org/en/about/trademark-clearinghouse/ claims-model-26sep12-en.pdf&gt; Authors' Addresses Wil Tan Cloud Registry Suite 32 Seabridge House 377 Kent St Sydney, NSW 2000 AU Phone: +61 414 710899 Email: wil&lt; at &gt;cloudregistry.net URI: http://www.cloudregistry.net Tan, et al. Expires September 5, 2013 [Page 41] Internet-Draft Launch Phase Mapping for EPP March 2013 Gavin Brown CentralNic Ltd 35-39 Mooregate London, England EC2R 6AR GB Phone: +44 20 33 88 0600 Email: gavin.brown&lt; at &gt;centralnic.com URI: https://www.centralnic.com James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould&lt; at &gt;verisign.com URI: http://www.verisigninc.com Tan, et al. Expires September 5, 2013 [Page 42] _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-03-04T15:07:40 Uniform Poll Responses for Launch Phase Results http://comments.gmane.org/gmane.ietf.provreg/2811 <pre>_______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> jbushlack< at >godaddy.com 2013-02-28T17:15:30 Launch Phase EPP Extension Version 06 http://comments.gmane.org/gmane.ietf.provreg/2792 <pre>Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension Mapping to Version 06. The IETF Internet-Draft Submission page is suspended until 2013-03-11, so the draft is attached in TXT and HTML format. We will post the draft once the IETF Internet-Draft Submission page opens. This version includes the following changes: 1. Removed the definition of the mark-1.0 and signedMark-1.0 and replaced with reference to draft-lozano-smd, that contains the definition for the mark, signed marked, and encoded signed mark. 2. Split the &lt;launch:timestamp&gt; into &lt;launch:generatedDate&gt; and &lt;launch:acceptedDate&gt; based on feedback from Trung Tran. 3. Added the "includeMark" optional attribute to the &lt;launch:info&gt; element to enable the client to request whether or not to include the mark in the info response. 4. Fixed state diagram to remove redundant transition from "invalid" to "rejected"; thanks Klaus Malorny. Please reply with any feedback. Thanks, JG James Gould Verisign Internet Engineering Task Force W. Tan Internet-Draft Cloud Registry Intended status: Standards Track G. Brown Expires: August 30, 2013 CentralNic Ltd J. Gould VeriSign, Inc. February 26, 2013 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) draft-tan-epp-launchphase-06 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain names during the launch phase of a domain name registry. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on August 30, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as Tan, et al. Expires August 30, 2013 [Page 1] Internet-Draft Launch Phase Mapping for EPP February 2013 described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Application Identifiers . . . . . . . . . . . . . . . . . 4 2.2. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 4 2.3. Status Values . . . . . . . . . . . . . . . . . . . . . . 5 2.3.1. State Transition . . . . . . . . . . . . . . . . . . . 6 2.4. Mark Validation Models . . . . . . . . . . . . . . . . . . 7 2.4.1. &lt;launch:codeMark&gt; element . . . . . . . . . . . . . . 7 2.5. Mark . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.6. Digital Signature . . . . . . . . . . . . . . . . . . . . 8 2.6.1. &lt;smd:signedMark&gt; element . . . . . . . . . . . . . . . 8 2.6.2. &lt;smd:encodedSignedMark&gt; element . . . . . . . . . . . 8 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 9 3.1. EPP &lt;check&gt; Command . . . . . . . . . . . . . . . . . . . 9 3.2. EPP &lt;info&gt; Command . . . . . . . . . . . . . . . . . . . . 13 3.3. EPP &lt;create&gt; Command . . . . . . . . . . . . . . . . . . . 17 3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 17 3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . . 23 3.4. EPP &lt;update&gt; Command . . . . . . . . . . . . . . . . . . . 25 3.5. EPP &lt;delete&gt; Command . . . . . . . . . . . . . . . . . . . 27 3.6. EPP &lt;renew&gt; Command . . . . . . . . . . . . . . . . . . . 28 3.7. EPP &lt;transfer&gt; Command . . . . . . . . . . . . . . . . . . 28 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 29 4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 29 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35 6. Change History . . . . . . . . . . . . . . . . . . . . . . . . 35 6.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . . 35 6.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . . 35 6.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . . 36 6.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . . 36 6.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . . 36 6.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . . 36 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 8. Security Considerations . . . . . . . . . . . . . . . . . . . 37 9. Normative References . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38 Tan, et al. Expires August 30, 2013 [Page 2] Internet-Draft Launch Phase Mapping for EPP February 2013 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping specifies a flexible schema that can be used to implement several common use cases related to the provisioning and management of launch phase extension in a domain name registry. It is typical for domain registries to operate in special modes within certain periods of time to facilitate allocation of domain names. This document uses the term "launch phase" and the shorter form "launch" to refer to such a period. The EPP domain name mapping [RFC5731] is designed for the steady state operation of a registry. During the launch, the interface used at each phase of the launch could be different from what is defined in EPP domain name mapping [RFC5731]. for example, registries typically accept multiple applications for a given domain name during the "sunrise" launch phase, referred to as a launch application. A launch registration is used to refer to a registration made during a launch phase when the server uses a first-come-first-serve model. Even in a first-come-first-serve model additional steps and information might be required to support a launch phase, like the passing of trademark information on a create. In addition, the Proposed Trademark Claims Model [1] defines a registry interface for the Trademark Claims or "claims" launch phase that includes support for presenting a Trademark Claims Notice to the Registrant. This document proposes an extension to the domain name extension in order to unambiguously manage the various launch phases known. 1.1. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. "launch-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix "launch" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. "signedMark-1.0" is used as an abbreviation for Tan, et al. Expires August 30, 2013 [Page 3] Internet-Draft Launch Phase Mapping for EPP February 2013 "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [draft-lozano-smd]. The XML namespace prefix "smd" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. "mark-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:mark-1.0" that is defined in [draft-lozano-smd]. The XML namespace prefix "mark" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. 2. Object Attributes This extension adds additional elements to the EPP domain name mapping [RFC5731]. Only those new elements are described here. 2.1. Application Identifiers Servers MAY allow multiple applications, referred to as a launch application, of a given domain name during its launch phase operations. Upon receiving a request to create a domain name, the server creates an application object corresponding to the request and assigns an application identifier for the application and returns it to the client with the &lt;launch:applicationID&gt; element. In order to facilitate correlation, all subsequent launch operations on the application object MUST be qualified by the previously assigned application identifier using the &lt;launch:applicationID&gt; element. 2.2. Launch Phases The server MAY support multiple launch phases sequentially or simultaneously. The &lt;launch:phase&gt; element MUST be included by the client to define the target launch phase of the command. The following launch phase values are defined: sunrise Phase when trademark holders can submit registrations or applications with trademark information that can be validated by the server. landrush Post sunrise phase when non-trademark holders are allowed to register domain names with steps taken to address a large volume of initial registrations. Tan, et al. Expires August 30, 2013 [Page 4] Internet-Draft Launch Phase Mapping for EPP February 2013 claims1 Trademark claims phase 1 as defined by Trademark Clearinghouse model of displaying a full, detailed claims notice to clients for domain names that match trademarks. claims2 Trademark claims phase 2 as defined by Trademark Clearinghouse model of displaying a short, educational claims notice to clients for domain names that match trademarks that opt into the service. open Post launch phase that is also referred to as "steady state". Servers MAY require additional trademark protection with this phase. custom A custom server launch phase that is defined using the "name" attribute. For extensibility the &lt;launch:phase&gt; element includes an OPTIONAL "name" attribute that can define a sub-phase or the full name of the phase when the &lt;launch:phase&gt; element has the "custom" value. For example, the "claims1" launch phase could have two sub-phases that include "landrush" and "open". 2.3. Status Values A launch application object MAY have a status value. The &lt;launch: status&gt; element is used to convey extended status pertaining to the application object, beyond what is specified in the object mapping for this application object. The following status values are defined using the required "s" attribute: pending: The initial state of a newly-created application object. validated: The application meets relevant registry rules. invalid: The application does not validate according to registry rules. pendingAuction: The application is pending based on results of an auction. allocated: One of two possible end states of an application object; the object corresponding to the application has been provisioned. rejected: The other possible end state; the object was not provisioned. custom: A custom status that is defined using the "name" attribute. Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object. The OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English). For extensibility the &lt;launch:status&gt; element includes an OPTIONAL "name" attribute that can define a sub-status or the full name of the Tan, et al. Expires August 30, 2013 [Page 5] Internet-Draft Launch Phase Mapping for EPP February 2013 status when the status value is "custom". The server SHOULD NOT use the "custom" status value. Certain status values MAY be combined. For example, an application can be invalid and rejected. Additionally certain statuses MAY be skipped. For example, an application MAY immediately start at the allocated status or an application MAY skip the pendingAuction status if the server does not support an auction. If a &lt;domain:create&gt; processes a request synchronously without the use of an intermediate application, than an Application Identifier (Section 2.1) is not needed along with the application status. 2.3.1. State Transition | request v +---------+ | pending | +----+----+ | | +--------------+-----+-----------+--------------+ | | | | v v v v +-----------+ +---------+ +-------+ +-------+ | | | | / \ / \ | validated | | invalid +-----&gt;| rejected | | allocated | | | | | \ / \ / +----+------+ +----+----+ +-------+ +-------+ | ^ ^ | | | | | | | | | +---------------------------------+ | | | | | | | | +--------+-------+ | | | | | +-----------------------&gt;| pendingAuction +------+ | | +----------------+ Figure 1 Tan, et al. Expires August 30, 2013 [Page 6] Internet-Draft Launch Phase Mapping for EPP February 2013 2.4. Mark Validation Models A server MUST support at least one of the following models for validating the trademark information: code Use of a mark code by itself to validate that the mark matches the domain name. This model is supported using the &lt;launch: codeMark&gt; element with just the &lt;launch:code&gt; element. mark The mark information is passed without any other validation element. The server will use some custom form of validation to validate that the mark information is authentic. This model is supported using the &lt;launch:codeMark&gt; element with just the &lt;mark: mark&gt; (Section 2.5) element. code with mark: A code is used along with the mark information by the server to validate the mark utilizing an external party. The code represents some form of secret that matches the mark information passed. This model is supported using the &lt;launch: codeMark&gt; element that contains both the &lt;launch:code&gt; and the &lt;mark:mark&gt; (Section 2.5) elements. signed mark: The mark information is digitally signed as described in the Digital Signature (Section 2.6) section. The digital signature can be directly validated by the server using the public key of the external party that created the signed mark using it's private key. This model is supported using the &lt;smd:signedMark&gt; (Section 2.6.1) and &lt;smd:encodedSignedMark&gt; (Section 2.6.2) elements. More than one &lt;launch:codeMark&gt;, &lt;smd:signedMark&gt; (Section 2.6.1), or &lt;smd:encodedSignedMark&gt; (Section 2.6.2) element MAY be specified. The maximum number of marks per domain name is up to server policy. 2.4.1. &lt;launch:codeMark&gt; element The &lt;launch:codeMark&gt; element that is used by the "code", "mark", and "code with mark" validation models, has the following child elements: &lt;launch:code&gt;: OPTIONAL mark code used to validate the &lt;mark:mark&gt; (Section 2.5) information. The mark code can be a mark specific secret value that the server can verify against a third party. &lt;mark:mark&gt;: OPTIONAL mark information with child elements defined in the Mark (Section 2.5) section. Tan, et al. Expires August 30, 2013 [Page 7] Internet-Draft Launch Phase Mapping for EPP February 2013 The following is an example &lt;launch:codeMark&gt; element with both a &lt;launch:code&gt; and &lt;mark:mark&gt; (Section 2.5) element. &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AC&lt;/launch:code&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:codeMark&gt; 2.5. Mark A &lt;mark:mark&gt; element describes an applicant's prior right to a given domain name that is used with the "mark", "mark with code", and the "signed mark" validation models. The &lt;mark:mark&gt; element is defined in [draft-lozano-smd]. A new mark format can be supported by creating a new XML schema for the mark that has an element that substitutes for the &lt;mark:abstractMark&gt; element from [draft-lozano-smd]. 2.6. Digital Signature Digital signatures MAY be used by the server to validate either the mark information, when using the "signed mark" validation model with the &lt;smd:signedMark&gt; (Section 2.6.1) element or the &lt;smd: encodedSignedMark&gt; (Section 2.6.2) element. 2.6.1. &lt;smd:signedMark&gt; element The &lt;smd:signedMark&gt; element contains the digitally signed mark information. The &lt;smd:signedMark&gt; element is defined in [draft-lozano-smd]. A new signed mark format can be supported by creating a new XML schema for the signed mark that has an element that substitutes for the &lt;smd:abstractSignedMark&gt; element from [draft-lozano-smd]. 2.6.2. &lt;smd:encodedSignedMark&gt; element The &lt;smd:encodedSignedMark&gt; element contains an encoded form of the digitally signed &lt;smd:signedMark&gt; (Section 2.6.1) element. The &lt;smd: encodedSignedMark&gt; element is defined in [draft-lozano-smd]. A new encoded signed mark format can be supported by creating a new XML schema for the encoded signed mark that has an element that substitutes for the &lt;smd:encodedSignedMark&gt; element from [draft-lozano-smd]. Tan, et al. Expires August 30, 2013 [Page 8] Internet-Draft Launch Phase Mapping for EPP February 2013 3. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in the Launch Phase Extension. This mapping is designed to be flexible, requiring only a minimum set of required elements. While it is meant to serve several use cases, it does not prescribe any interpretation by the client or server. Such processing is typically highly policy-dependent and therefore specific to implementations. Operations on application objects are done via one or more of the existing EPP verbs defined in the EPP domain name mapping [RFC5731]. Registries may choose to support a subset of the operations. 3.1. EPP &lt;check&gt; Command This extension defines additional elements to extend the EPP &lt;check&gt; command and response to be used in conjunction with the EPP domain name mapping [RFC5731]. This extension defines a new command called the Claims Check Command that is used to determine whether or not there are any matching trademarks, in the specified launch phase, for each domain name passed in the command. The availability check information defined in the EPP domain name mapping [RFC5731] MUST NOT be returned for the Claims Check Command. Instead of returning whether the domain name is available the Claims Check Command will return whether or not at least one matching trademark exists for the domain name. If there is at least one matching trademark that exists for the domain name a &lt;launch:claimKey&gt; element is returned. The value of the &lt;launch: claimKey&gt; element can be used with an info service of a third party trademark provider like the Trademark Clearinghouse (TMCH) for getting the information needed to generate the trademark claims notice. The third party trademark provider should also return a unique notice identifier that can be passed in the &lt;launch:noticeID&gt; element of the extension to the Create Command (Section 3.3). The &lt;domain:name&gt; elements in the EPP &lt;check&gt; command of EPP domain name mapping [RFC5731] define the domain names to check for matching trademarks. The &lt;launch:check&gt; element contains the following child elements: Tan, et al. Expires August 30, 2013 [Page 9] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;launch:phase&gt; The phase with the value of "claims1" or "claims2" to indicate it as a Claims Check Command. The "claims1" Claims Check Command will match the &lt;domain:name&gt; against the full list of trademark labels and the "claims2" Claims Check Command will match the &lt;domain:name&gt; against the list of trademark labels that opted into the "claims2" launch phase. Example Claims Check Command using the &lt;check&gt; domain command and the &lt;launch:check&gt; extension to determine if "example1.tld" and "example2.tld" have any matching trademarks during the "claims1" launch phase. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;check&gt; &lt;domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example1.tld&lt;/domain:name&gt; &lt;domain:name&gt;example2.tld&lt;/domain:name&gt; &lt;/domain:check&gt; &lt;/check&gt; &lt;extension&gt; &lt;launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims1&lt;/launch:phase&gt; &lt;/launch:check&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 10] Internet-Draft Launch Phase Mapping for EPP February 2013 Example Claims Check Command using the &lt;check&gt; domain command and the &lt;launch:check&gt; extension to determine if "example3.tld" and "example4.tld" have any matching trademarks that opted into the "claims2" launch phase. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;check&gt; &lt;domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example3.tld&lt;/domain:name&gt; &lt;domain:name&gt;example4.tld&lt;/domain:name&gt; &lt;/domain:check&gt; &lt;/check&gt; &lt;extension&gt; &lt;launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims2&lt;/launch:phase&gt; &lt;/launch:check&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; If the &lt;check&gt; command has been processed successfully, the EPP &lt;resData&gt; element MUST contains a child &lt;launch:chkData&gt; element that identifies the launch namespace. The &lt;launch:chkData&gt; element contains the following child elements: &lt;launch:phase&gt; The phase with a value of "claims1" or "claims2" that matches the associated Claims Check Command &lt;launch:phase&gt;. &lt;launch:cd&gt; One or more &lt;launch:cd&gt; elements that contain the following child elements: &lt;launch:name&gt; Contains the fully qualified name of the queried domain name. This element MUST contain an "exists" attribute whose value indicates if a matching trademark exists for the domain name. A value of "1" or "true" means that a matching trademark does exist for the claims launch phase. A value of "0" or "false" means that a matching trademark does not exist. &lt;launch:claimKey&gt; An OPTIONAL claim key that MAY be passed to an info service of a third party trademark provider like the Trademark Clearinghouse (TMCH) for getting the information needed to generate the trademark claims notice. The &lt;launch: claimKey&gt; is used as the key for the query in place of the domain name to securely query the service without using a Tan, et al. Expires August 30, 2013 [Page 11] Internet-Draft Launch Phase Mapping for EPP February 2013 well-known value like a domain name. Example Claims Check Response when no matching trademarks are found for the domain name example1.tld and matching trademarks are found for the domain name example2.tld for the "claims1" launch phase. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;launch:chkData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims1&lt;/launch:phase&gt; &lt;launch:cd&gt; &lt;launch:name exists="0"&gt;example1.tld&lt;/launch:name&gt; &lt;/launch:cd&gt; &lt;launch:cd&gt; &lt;launch:name exists="1"&gt;example2.tld&lt;/launch:name&gt; &lt;launch:claimKey&gt;abc123&lt;/launch:claimKey&gt; &lt;/launch:cd&gt; &lt;/launch:chkData&gt; &lt;/resData&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 12] Internet-Draft Launch Phase Mapping for EPP February 2013 Example Claims Check Response when no matching trademarks are found for the domain name example3.tld and matching trademarks are found for the domain name example4.tld for the "claims2" launch phase. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;launch:chkData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims2&lt;/launch:phase&gt; &lt;launch:cd&gt; &lt;launch:name exists="0"&gt;example3.tld&lt;/launch:name&gt; &lt;/launch:cd&gt; &lt;launch:cd&gt; &lt;launch:name exists="1"&gt;example4.tld&lt;/launch:name&gt; &lt;launch:claimKey&gt;abc123&lt;/launch:claimKey&gt; &lt;/launch:cd&gt; &lt;/launch:chkData&gt; &lt;/resData&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.2. EPP &lt;info&gt; Command This extension defines additional elements to extend the EPP &lt;info&gt; command and response to be used in conjunction with the EPP domain name mapping [RFC5731]. The EPP &lt;info&gt; command is used to retrieve information for a launch phase registration or application. The Application Identifier (Section 2.1) returned in the &lt;launch:creData&gt; element of the Create Response (Section 3.3) is used for retrieving information for a launch application. A &lt;launch:info&gt; element is sent along with the regular &lt;info&gt; domain command. The &lt;launch:info&gt; element includes an OPTIONAL "includeMark" boolean attribute, with a default value of "false", to indicate whether or not to include the mark in the response. The &lt;launch:info&gt; element contains the following child elements: Tan, et al. Expires August 30, 2013 [Page 13] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;launch:phase&gt; The phase during which the application or registration was submitted or is associated with. Server policy defines the phases that are supported. &lt;launch:applicationID&gt; OPTIONAL application identifier of the launch application. Example &lt;info&gt; domain command with the &lt;launch:info&gt; extension to retrieve information for the sunrise application for example.tld and application identifier "abc123". &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;info&gt; &lt;domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;/domain:info&gt; &lt;/info&gt; &lt;extension&gt; &lt;launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" includeMark="true"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;/launch:info&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 14] Internet-Draft Launch Phase Mapping for EPP February 2013 Example &lt;info&gt; domain command with the &lt;launch:info&gt; extension to retrieve information for the sunrise registration for example.tld. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;info&gt; &lt;domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;/domain:info&gt; &lt;/info&gt; &lt;extension&gt; &lt;launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;/launch:info&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; If the query was successful, the server replies with a &lt;launch: infData&gt; element along with the regular EPP &lt;resData&gt;. The &lt;launch: infData&gt; contains the following child elements: &lt;launch:phase&gt; The phase during which the application was submitted or is associated with that matches the associated &lt;info&gt; command &lt;launch:phase&gt;. &lt;launch:applicationID&gt; OPTIONAL application identifier of the launch application. &lt;launch:status&gt; OPTIONAL status of the launch application using one of the supported status values (Section 2.3). &lt;mark:mark&gt; Zero or more &lt;mark:mark&gt; (Section 2.5) elements. Tan, et al. Expires August 30, 2013 [Page 15] Internet-Draft Launch Phase Mapping for EPP February 2013 Example &lt;info&gt; domain response using the &lt;launch:infData&gt; extension with the mark information. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:roid&gt;EXAMPLE1-REP&lt;/domain:roid&gt; &lt;domain:status s="pendingCreate"/&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:clID&gt;ClientX&lt;/domain:clID&gt; &lt;domain:crID&gt;ClientY&lt;/domain:crID&gt; &lt;domain:crDate&gt;2012-04-03T22:00:00.0Z&lt;/domain:crDate&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:infData&gt; &lt;/resData&gt; &lt;extension&gt; &lt;launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;launch:status s="pending"/&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:infData&gt; &lt;/extension&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 16] Internet-Draft Launch Phase Mapping for EPP February 2013 3.3. EPP &lt;create&gt; Command There are two forms of the extension to the EPP &lt;create&gt; command that are dependent on the supported launch phases (Section 2.2) as defined below: sunrise The EPP &lt;create&gt; command with the "sunrise" launch phase is used to submit a registration with trademark information that can be verified by the server with the &lt;domain:name&gt; value. The Sunrise Create Form (Section 3.3.1) is used for the "sunrise" launch phase. Optionally, the server can support multiple overlapping applications that are chosen asynchronously with a server generated Application Identifier (Section 2.1) for later reference. landrush The EPP &lt;create&gt; command with the "landrush" launch phase is undefined but the form supported is up to server policy. claims1 The EPP &lt;create&gt; command with the "claims1" launch phase is used to pass the information associated with the presentation and acceptance of the "claims1" claims notice. The Claims Create Form (Section 3.3.2) is used for the "claims1" launch phase. claims2 The EPP &lt;create&gt; command with the "claims2" launch phase is used to pass the information associated with the presentation of the "claims1" claims notice. The Claims Create Form (Section 3.3.2) is used for the "claims2" launch phase. open The EPP &lt;create&gt; command with the "open" launch phase is undefined but the form supported is up to server policy. custom The EPP &lt;create&gt; command with the "custom" launch phase is undefined but the form supported is up to server policy. 3.3.1. Sunrise Create Form The Sunrise Create Form of the extension to the EPP domain name mapping [RFC5731] includes the verifiable trademark information that the server uses to match against the domain name to authorize the domain create. A server MUST support one of four models in Claim Validation Models (Section 2.4) to verify the trademark information passed by the client. A &lt;launch:create&gt; element is sent along with the regular &lt;create&gt; domain command. The &lt;launch:create&gt; element contains the following child elements: &lt;launch:phase&gt; The launch phase for the create like the "sunrise" launch phase. Tan, et al. Expires August 30, 2013 [Page 17] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;launch:codeMark&gt; or &lt;smd:signedMark&gt; or &lt;smd:encodedSignedMark&gt; &lt;launch:codeMark&gt; Zero or more &lt;launch:codeMark&gt; elements. The &lt;launch:codeMark&gt; child elements are defined in the &lt;launch: codeMark&gt; element (Section 2.4.1) section. &lt;smd:signedMark&gt; Zero or more &lt;smd:signedMark&gt; elements. The &lt;smd:signedMark&gt; child elements are defined in the &lt;smd: signedMark&gt; element (Section 2.6.1) section. &lt;smd:encodedSignedMark&gt; Zero or more &lt;smd:encodedSignedMark&gt; elements. The &lt;smd:encodedSignedMark&gt; child elements are defined in the &lt;smd:encodedSignedMark&gt; element (Section 2.6.2) section. Following is an example &lt;create&gt; domain command using the &lt;launch: create&gt; extension, following the "code" validation model, with multiple sunrise codes. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AC&lt;/launch:code&gt; &lt;/launch:codeMark&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AD&lt;/launch:code&gt; &lt;/launch:codeMark&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AE&lt;/launch:code&gt; &lt;/launch:codeMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; Tan, et al. Expires August 30, 2013 [Page 18] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;/epp&gt; Following is an example &lt;create&gt; domain command using the &lt;launch: create&gt; extension, following the "mark" validation model, with the mark information. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;exampleone.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:codeMark&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:codeMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 19] Internet-Draft Launch Phase Mapping for EPP February 2013 Following is an example &lt;create&gt; domain command using the &lt;launch: create&gt; extension, following the "code with mark" validation model, with a code and mark information. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:codeMark&gt; &lt;launch:code&gt;49FD46E6C4B45C55D4AC&lt;/launch:code&gt; &lt;mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"&gt; ... &lt;/mark:mark&gt; &lt;/launch:codeMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 20] Internet-Draft Launch Phase Mapping for EPP February 2013 Following is an example &lt;create&gt; domain command using the &lt;launch: create&gt; extension, following the "signed mark" validation model, with the signed mark information. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;exampleone.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;smd:signedMark id="signedMark" xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"&gt; ... &lt;/smd:signedMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 21] Internet-Draft Launch Phase Mapping for EPP February 2013 Following is an example &lt;create&gt; domain command using the &lt;launch: create&gt; extension, following the "signed mark" validation model, with the base64 encoded signed mark information. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;exampleone.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;smd:encodedSignedMark xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"&gt; ... &lt;/smd:encodedSignedMark&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; If the create was successful, the server MAY reply with the &lt;launch: creData&gt; element along with the regular EPP &lt;resData&gt; to indicate the server generated Application Identifier (Section 2.1) when multiple applications of a given domain name is supported; otherwise no extension is included with the regular EPP &lt;resData&gt;. The &lt;launch: creData&gt; element contains the following child elements: &lt;launch:phase&gt; The phase of the application that mirrors the &lt;launch:phase&gt; element included in the &lt;launch:create&gt;. &lt;launch:applicationID&gt; The application identifier of the application. Tan, et al. Expires August 30, 2013 [Page 22] Internet-Draft Launch Phase Mapping for EPP February 2013 An example response when multiple overlapping applications are supported by the server. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1001"&gt; &lt;msg&gt;Command completed successfully; action pending&lt;/msg&gt; &lt;/result&gt; &lt;resData&gt; &lt;domain:creData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:crDate&gt;2010-08-10T15:38:26.623854Z&lt;/domain:crDate&gt; &lt;domain:exDate&gt;2012-08-10T15:38:26.623854Z&lt;/domain:exDate&gt; &lt;/domain:creData&gt; &lt;/resData&gt; &lt;extension&gt; &lt;launch:creData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;2393-9323-E08C-03B1 &lt;/launch:applicationID&gt; &lt;/launch:creData&gt; &lt;/extension&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.3.2. Claims Create Form The Claims Create Form of the extension to the EPP domain name mapping [RFC5731] includes the information related to the acceptance of the claims notice for the "claims1" launch phase and the display of the claims notice for the "claims2" launch phase. A &lt;launch:create&gt; element is sent along with the regular &lt;create&gt; domain command. The &lt;launch:create&gt; element contains the following child elements: &lt;launch:phase&gt; MUST contain the value of "claims1" or "claim2" to indicate the claims launch phase. Tan, et al. Expires August 30, 2013 [Page 23] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;launch:notice&gt; &lt;launch:noticeID&gt; Unique notice identifier generated by the source of the claims notice information like the Claims Notice Information Service (CNIS). &lt;launch:generatedDate&gt; Contains the date and time that the claims notice was generated. &lt;launch:acceptedDate&gt; Contains the date and time that the claims notice was displayed or accepted. &lt;launch:source&gt; Contains the source information of the client that was displayed or that accepted the claims notice like the client IP address. Following is an example &lt;create&gt; domain command using the &lt;launch: create&gt; extension with the &lt;launch:notice&gt; information for the "claims1" claims launch phase. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;create&gt; &lt;domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt; &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:contact type="tech"&gt;sh8013&lt;/domain:contact&gt; &lt;domain:authInfo&gt; &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt; &lt;/domain:authInfo&gt; &lt;/domain:create&gt; &lt;/create&gt; &lt;extension&gt; &lt;launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;claims1&lt;/launch:phase&gt; &lt;launch:notice&gt; &lt;launch:noticeID&gt;49FD46E6C4B45C55D4AC&lt;/launch:noticeID&gt; &lt;launch:generatedDate&gt;2012-06-19T09:00:10.0Z &lt;/launch:generatedDate&gt; &lt;launch:acceptedDate&gt;2012-06-19T09:01:30.0Z &lt;/launch:acceptedDate&gt; &lt;launch:source&gt;192.0.2.29&lt;/launch:source&gt; &lt;/launch:notice&gt; &lt;/launch:create&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 24] Internet-Draft Launch Phase Mapping for EPP February 2013 This extension does not define any extension to the response of a &lt;create&gt; domain command for the Claims Create Form. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731]. 3.4. EPP &lt;update&gt; Command This extension defines additional elements to extend the EPP &lt;update&gt; command to be used in conjunction with the domain name mapping. A server that does not support multiple applications of a given domain name with an Application Identifier (Section 2.1) during its launch phase operations MUST return an EPP error result code of 2102. Registry policies permitting, clients may update an application object by submitting an EPP &lt;update&gt; command along with a &lt;launch: update&gt; element to indicate the application object to be updated. The &lt;launch:update&gt; element contains the following child elements: &lt;launch:phase&gt; The phase during which the application was submitted or is associated with. &lt;launch:applicationID&gt; The application identifier for which the client wishes to update. This extension does not define any extension to the response of an &lt;update&gt; domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731]. Tan, et al. Expires August 30, 2013 [Page 25] Internet-Draft Launch Phase Mapping for EPP February 2013 Following is an example &lt;update&gt; domain command with the &lt;launch: update&gt; extension to add and remove a name server of a sunrise application with the application identifier "abc123". &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;update&gt; &lt;domain:update xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;domain:add&gt; &lt;domain:ns&gt; &lt;domain:hostObj&gt;ns2.example.tld&lt;/domain:hostObj&gt; &lt;/domain:ns&gt; &lt;/domain:add&gt; &lt;domain:rem&gt; &lt;domain:ns&gt; &lt;domain:hostObj&gt;ns1.example.tld&lt;/domain:hostObj&gt; &lt;/domain:ns&gt; &lt;/domain:rem&gt; &lt;/domain:update&gt; &lt;/update&gt; &lt;extension&gt; &lt;launch:update xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;/launch:update&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; Tan, et al. Expires August 30, 2013 [Page 26] Internet-Draft Launch Phase Mapping for EPP February 2013 An example response that corresponds to the above command. &lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.5. EPP &lt;delete&gt; Command This extension defines additional elements to extend the EPP &lt;delete&gt; command to be used in conjunction with the domain name mapping. A server that does not support multiple applications of a given domain name with an Application Identifier (Section 2.1) during its launch phase operations MUST return an EPP error result code of 2102. Registry policies permitting, clients MAY withdraw an application by submitting an EPP &lt;delete&gt; command along with a &lt;launch:delete&gt; element to indicate the application object to be deleted. The &lt;launch:delete&gt; element contains the following child elements: &lt;launch:phase&gt; The phase during which the application was submitted or is associated with. &lt;launch:applicationID&gt; The application identifier for which the client wishes to delete. This extension does not define any extension to the response of a &lt;delete&gt; domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731]. Tan, et al. Expires August 30, 2013 [Page 27] Internet-Draft Launch Phase Mapping for EPP February 2013 Following is an example &lt;delete&gt; domain command with the &lt;launch: delete&gt; extension. &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;command&gt; &lt;delete&gt; &lt;domain:delete xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt; &lt;domain:name&gt;example.tld&lt;/domain:name&gt; &lt;/domain:delete&gt; &lt;/delete&gt; &lt;extension&gt; &lt;launch:delete xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"&gt; &lt;launch:phase&gt;sunrise&lt;/launch:phase&gt; &lt;launch:applicationID&gt;abc123&lt;/launch:applicationID&gt; &lt;/launch:delete&gt; &lt;/extension&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;/command&gt; &lt;/epp&gt; An example response that corresponds to the above command. &lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt; &lt;response&gt; &lt;result code="1000"&gt; &lt;msg&gt;Command completed successfully&lt;/msg&gt; &lt;/result&gt; &lt;trID&gt; &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt; &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt; &lt;/trID&gt; &lt;/response&gt; &lt;/epp&gt; 3.6. EPP &lt;renew&gt; Command This extension does not define any extension to the EPP &lt;renew&gt; command or response described in the EPP domain name mapping [RFC5731]. 3.7. EPP &lt;transfer&gt; Command This extension does not define any extension to the EPP &lt;transfer&gt; command or response described in the EPP domain name mapping Tan, et al. Expires August 30, 2013 [Page 28] Internet-Draft Launch Phase Mapping for EPP February 2013 [RFC5731]. 4. Formal Syntax One schema is presented here that is the EPP Launch Phase Mapping schema. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. 4.1. Launch Schema Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BEGIN &lt;?xml version="1.0" encoding="UTF-8"?&gt; Tan, et al. Expires August 30, 2013 [Page 29] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;schema targetNamespace="urn:ietf:params:xml:ns:launch-1.0" xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:mark="urn:ietf:params:xml:ns:mark-1.0" xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"&gt; &lt;!-- Import common element types. --&gt; &lt;import namespace="urn:ietf:params:xml:ns:eppcom-1.0" schemaLocation="eppcom-1.0.xsd"/&gt; &lt;import namespace="urn:ietf:params:xml:ns:mark-1.0" schemaLocation="mark-1.0.xsd"/&gt; &lt;import namespace="urn:ietf:params:xml:ns:signedMark-1.0" schemaLocation="signedMark-1.0.xsd"/&gt; &lt;annotation&gt; &lt;documentation&gt; Extensible Provisioning Protocol v1.0 domain name extension schema for the launch phase processing. &lt;/documentation&gt; &lt;/annotation&gt; &lt;!-- Child elements found in EPP commands. --&gt; &lt;element name="check" type="launch:checkType"/&gt; &lt;element name="info" type="launch:infoType"/&gt; &lt;element name="create" type="launch:createType"/&gt; &lt;element name="update" type="launch:idContainerType"/&gt; &lt;element name="delete" type="launch:idContainerType"/&gt; &lt;!-- Common container of id (identifier) element --&gt; &lt;complexType name="idContainerType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;element name="applicationID" type="launch:applicationIDType"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; Tan, et al. Expires August 30, 2013 [Page 30] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;!-- Definition for application identifier --&gt; &lt;simpleType name="applicationIDType"&gt; &lt;restriction base="token"/&gt; &lt;/simpleType&gt; &lt;!-- Definition for launch phase. Name is an optional attribute used to extend the phase type. For example, when using the phase type value of &amp;qt;custom&amp;gt;, the name can be used to specify the custom phase. --&gt; &lt;complexType name="phaseType"&gt; &lt;simpleContent&gt; &lt;extension base="launch:phaseTypeValue"&gt; &lt;attribute name="name" type="token"/&gt; &lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;!-- Enumeration of for launch phase values. --&gt; &lt;simpleType name="phaseTypeValue"&gt; &lt;restriction base="token"&gt; &lt;enumeration value="sunrise"/&gt; &lt;enumeration value="landrush"/&gt; &lt;enumeration value="claims1"/&gt; &lt;enumeration value="claims2"/&gt; &lt;enumeration value="open"/&gt; &lt;enumeration value="custom"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Definition for the sunrise code --&gt; &lt;simpleType name="codeType"&gt; &lt;restriction base="base64Binary"&gt; &lt;minLength value="1"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Definition for the notice identifier --&gt; Tan, et al. Expires August 30, 2013 [Page 31] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;simpleType name="noticeIDType"&gt; &lt;restriction base="base64Binary"&gt; &lt;minLength value="1"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Possible status values for sunrise application --&gt; &lt;simpleType name="statusValueType"&gt; &lt;restriction base="token"&gt; &lt;enumeration value="pending"/&gt; &lt;enumeration value="validated"/&gt; &lt;enumeration value="invalid"/&gt; &lt;enumeration value="pendingAuction"/&gt; &lt;enumeration value="allocated"/&gt; &lt;enumeration value="rejected"/&gt; &lt;enumeration value="custom"/&gt; &lt;/restriction&gt; &lt;/simpleType&gt; &lt;!-- Status type definition --&gt; &lt;complexType name="statusType"&gt; &lt;simpleContent&gt; &lt;extension base="normalizedString"&gt; &lt;attribute name="s" type="launch:statusValueType" use="required"/&gt; &lt;attribute name="lang" type="language" default="en"/&gt; &lt;attribute name="name" type="token"/&gt; &lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;!-- codeMark Type that contains an optional code with mark information. --&gt; &lt;complexType name="codeMarkType"&gt; &lt;sequence&gt; &lt;element name="code" type="launch:codeType" minOccurs="0"/&gt; &lt;element ref="mark:abstractMark" minOccurs="0"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; Tan, et al. Expires August 30, 2013 [Page 32] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;!-- Child elements for the create command --&gt; &lt;complexType name="createType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;choice&gt; &lt;element name="codeMark" type="launch:codeMarkType" maxOccurs="unbounded"/&gt; &lt;element ref="smd:abstractSignedMark" maxOccurs="unbounded"/&gt; &lt;element ref="smd:encodedSignedMark" maxOccurs="unbounded"/&gt; &lt;element name="notice" type="launch:createNoticeType"/&gt; &lt;/choice&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;!-- Child elements of the create notice element. --&gt; &lt;complexType name="createNoticeType"&gt; &lt;sequence&gt; &lt;element name="noticeID" type="launch:noticeIDType"/&gt; &lt;element name="generatedDate" type="dateTime"/&gt; &lt;element name="acceptedDate" type="dateTime"/&gt; &lt;element name="source" type="token"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;!-- Child elements of check (Claims Check Command). --&gt; &lt;complexType name="checkType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;!-- Child elements of info command. --&gt; &lt;complexType name="infoType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; Tan, et al. Expires August 30, 2013 [Page 33] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;element name="applicationID" type="launch:applicationIDType" minOccurs="0"/&gt; &lt;/sequence&gt; &lt;attribute name="includeMark" type="boolean" default="false"/&gt; &lt;/complexType&gt; &lt;!-- Child response elements. --&gt; &lt;element name="chkData" type="launch:chkDataType"/&gt; &lt;element name="creData" type="launch:idContainerType"/&gt; &lt;element name="infData" type="launch:infDataType"/&gt; &lt;!-- &lt;check&gt; response elements. --&gt; &lt;complexType name="chkDataType"&gt; &lt;sequence&gt; &lt;element name="phase" type="launch:phaseType"/&gt; &lt;element name="cd" type="launch:cdType" maxOccurs="unbounded"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;complexType name="cdType"&gt; &lt;sequence&gt; &lt;element name="name" type="launch:cdNameType"/&gt; &lt;element name="claimKey" type="token" minOccurs="0"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;complexType name="cdNameType"&gt; &lt;simpleContent&gt; &lt;extension base="eppcom:labelType"&gt; &lt;attribute name="exists" type="boolean" use="required"/&gt; &lt;/extension&gt; &lt;/simpleContent&gt; &lt;/complexType&gt; &lt;!-- &lt;info&gt; response elemenets --&gt; &lt;complexType name="infDataType"&gt; &lt;sequence&gt; Tan, et al. Expires August 30, 2013 [Page 34] Internet-Draft Launch Phase Mapping for EPP February 2013 &lt;element name="phase" type="launch:phaseType"/&gt; &lt;element name="applicationID" type="launch:applicationIDType" minOccurs="0"/&gt; &lt;element name="status" type="launch:statusType" minOccurs="0"/&gt; &lt;element ref="mark:abstractMark" minOccurs="0" maxOccurs="unbounded"/&gt; &lt;/sequence&gt; &lt;/complexType&gt; &lt;/schema&gt; END 5. Acknowledgements The authors wish to acknowledge the efforts of the leading participants of the Community TMCH Model that led to many of the changes to this document, which include Chris Wright, Jeff Neuman, Jeff Eckhaus, and Will Shorter. Special suggestions that have been incorporated into this document were provided by Jothan Frakes, Keith Gaughan, Jan Jansen, Gustavo Lozano, Klaus Malorny, Patrick Mevzek, Bernhard Reutner-Fischer, Trung Tran, Ulrich Wisser and Sharon Wodjenski. 6. Change History 6.1. Change from 00 to 01 1. Changed to use camel case for the XML elements. 2. Replaced "cancelled" status to "rejected" status. 3. Added the child elements of the &lt;claim&gt; element. 4. Removed the XML schema and replaced with "[TBD]". 6.2. Change from 01 to 02 1. Added support for both the ICANN and ARI/Neustar TMCH models. 2. Changed the namespace URI and prefix to use "launch" instead of "launchphase". 3. Added definition of multiple claim validation models. 4. Added the &lt;launch:signedClaim&gt; and &lt;launch:signedNotice&gt; elements. 5. Added support for Claims Info Command Tan, et al. Expires August 30, 2013 [Page 35] Internet-Draft Launch Phase Mapping for EPP February 2013 6.3. Change from 02 to 03 1. Removed XSI namespace per Keith Gaughan's suggestion on the provreg list. 2. Added extensibility to the launch:status element and added the pendingAuction status per Trung Tran's feedback on the provreg list. 3. Added support for the Claims Check Command, updated the location and contents of the signedNotice, and replaced most references of Claim to Mark based on the work being done on the ARI/Neustar launch model. 6.4. Change from 03 to 04 1. Removed references to the ICANN model. 2. Removed support for the Claims Info Command. 3. Removed use of the signedClaim. 4. Revised the method for referring to the signedClaim from the XML Signature using the IDREF URI. 5. Split the launch-1.0.xsd into three XML schemas including launch- 1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. 6. Split the "claims" launch phase to the "claims1" and "claims2" launch phases. 7. Added support for the encodedSignedMark with base64 encoded signedMark. 8. Changed the elements in the createNoticeType to include the noticeID, timestamp, and the source elements. 9. Added the class and effectiveDate elements to mark. 6.5. Change from 04 to 05 1. Removed reference to &lt;smd:zone&gt; in the &lt;smd:signedMark&gt; example. 2. Incorporated feedback from Bernhard Reutner-Fischer on the provreg mail list. 3. Added missing launch XML prefix to applicationIDType reference in the idContainerType of the Launch Schema. 4. Added missing description of the &lt;mark:pc&gt; element in the &lt;mark: addr&gt; element. 5. Updated note on replication of the EPP contact mapping elements in the Mark Contact section. 6.6. Change from 05 to 06 1. Removed the definition of the mark-1.0 and signedMark-1.0 and replaced with reference to draft-lozano-smd, that contains the definition for the mark, signed marked, and encoded signed mark. Tan, et al. Expires August 30, 2013 [Page 36] Internet-Draft Launch Phase Mapping for EPP February 2013 2. Split the &lt;launch:timestamp&gt; into &lt;launch:generatedDate&gt; and &lt;launch:acceptedDate&gt; based on feedback from Trung Tran. 3. Added the "includeMark" optional attribute to the &lt;launch:info&gt; element to enable the client to request whether or not to include the mark in the info response. 4. Fixed state diagram to remove redundant transition from "invalid" to "rejected"; thanks Klaus Malorny. 7. IANA Considerations This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. Three URI assignments have been registered by the IANA. Registration request for the Launch namespace: URI: urn:ietf:params:xml:ns:launch-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. 8. Security Considerations The mapping extensions described in this document do not provide any security services beyond those described by EPP [RFC5730], the EPP domain name mapping [RFC5731], and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. Updates to, and deletion of an application object must be restricted to clients authorized to perform the said operation on the object. As information contained within an application, or even the mere fact that an application exists may be confidential. Any attempt to operate on an application object by an unauthorized client MUST be rejected with an EPP 2303 (object does not exist) or an appropriate auhorization error. Server policy may allow &lt;info&gt; operation with filtered output by clients other than the sponsoring client, in which case the &lt;domain:infData&gt; and &lt;launch:infData&gt; response SHOULD be filtered to include only fields that are publicly accessible. 9. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Tan, et al. Expires August 30, 2013 [Page 37] Internet-Draft Launch Phase Mapping for EPP February 2013 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009. [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, August 2009. [draft-lozano-smd] Lozano, G., "Mark and Signed Mark Objects Mapping". [1] &lt;http://newgtlds.icann.org/en/about/trademark-clearinghouse/ claims-model-26sep12-en.pdf&gt; Authors' Addresses Wil Tan Cloud Registry Suite 32 Seabridge House 377 Kent St Sydney, NSW 2000 AU Phone: +61 414 710899 Email: wil&lt; at &gt;cloudregistry.net URI: http://www.cloudregistry.net Gavin Brown CentralNic Ltd 35-39 Mooregate London, England EC2R 6AR GB Phone: +44 8700 170 900 Email: gavin.brown&lt; at &gt;centralnic.com URI: http://www.centralnic.com Tan, et al. Expires August 30, 2013 [Page 38] Internet-Draft Launch Phase Mapping for EPP February 2013 James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould&lt; at &gt;verisign.com URI: http://www.verisigninc.com Tan, et al. Expires August 30, 2013 [Page 39] _______________________________________________ provreg mailing list provreg&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/provreg </pre> Gould, James 2013-02-26T14:30:27 Search Engine Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.ietf.provreg