Launch Phase


The following section outlines the format of the EPP LAUNCH commands required to process registrations in the Launch Phase.

The Launch Phase will allow both Sunrise and Landrush Applications.

 

Table of Contents

1. Domain Check Command
2. Domain Info Command
3. Domain Create Command
4. Domain Update Command
5. Domain Delete Command
6. Poll Messages

 

Domain Check Command


Notes


1. The Check command may include multiple domain names

2. The <launch:check> extension must be used

3. The attribute "type" for the <launch:check> element must have a value of "avail" for Sunrise Checks

4. The attribute "type" for the <launch:check> element must have a value of "claims" for Landrush Checks

5. If the request is to check for a Sunrise Check, the sunrise phase must be specified in the <launch:phase> element

6. If the request is to check for a Landrush Check, the claims phase must be specified in the <launch:phase> element, and the element must have the attribute ' name="landrush-[X]"', where X is 1,2,3 or 4. Eg: name=landrush-1 


COMMANDS

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
      <check>
       <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
         <domain:name>exampledomain1.gtld</domain:name>
         <domain:name>exampledomain2.gtld</domain:name>
       </domain:check>
      </check>
      <extension>
       <launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" type="avail">
          <launch:phase>sunrise</launch:phase>
       </launch:check>
      </extension>
     </command>
   </epp>

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
      <check>
       <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
         <domain:name>exampledomain1.gtld</domain:name>
         <domain:name>exampledomain2.gtld</domain:name>
       </domain:check>
      </check>
      <extension>
       <launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" type="claims">
         <launch:phase name="landrush-[X]">claims</launch:phase>
       </launch:check>
      </extension>
     </command>
   </epp>



RESPONSES


<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <result code="1000">
      <epp:msg>Domain Check Command completed successfully</epp:msg>
    </result>
    <resData>
      <domain:chkData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
        <domain:cd>
          <domain:name avail="1">exampledomain1.gtld</domain:name>
        </domain:cd>
        <domain:cd>
          <domain:name avail="0">exampledomain2.gtld</domain:name>
          <domain:reason>Domain reserved. Reason: 'Legal'</domain:reason>
        </domain:cd>
      </domain:chkData>
    </resData>
  </response>
</epp>


<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1000">
        <msg>Command completed successfully</msg>
       </result>
<resData>
     <domain:chkData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
       <domain:cd>
         <domain:name avail="1">exampledomain1.gtld</domain:name>
     </domain:cd>       
<domain:cd>
         <domain:name avail="1">exampledomain2.gtld</domain:name>
     </domain:cd>
   </domain:chkData>
   </resData> <extension> <launch:chkData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> <launch:phase name="landrush-[X]">claims</launch:phase> <launch:cd> <launch:name exists="0">exampledomain1.gtld</launch:name> </launch:cd> <launch:cd> <launch:name exists="1">exampledomain2.gtld</launch:name> <launch:claimKey> [UNIQUE CLAIM KEY] </launch:claimKey> </launch:cd> </launch:chkData> </extension> </response> </epp>

 

Sunrise Check Response

- If the "avail" attribute in the response has a value of "1" it means that the associated domain name is available for registration
- If the "avail" attribute in the response has a value of "0" it means that the associated domain names is not available for registration. The reason will be outlined in the <domain:reason> element


Landrush Check Response

- If the "exist" attribute in the response has a value of "0" it means that there is no prior claim to the name. This means that the domain name may be registered using the General Create Method outlined below
- If the "exist" attribute in the response has a value of "1" it means that there is a prior claim to the name. This means that the domain name may not be applied for until a Claims Notice has been issued to the Applicant, and the Claims Notice acknowledged. The registrar must use the value provided in the <launch:claimKey> element to obtain a Claims Notice from the Validator as well as a Notice ID that must be used for the application of the domain.
 

Domain Info Command


Notes


1. The Domain Info command returns the information pertaining to a Successful Application during the Launch Phase

2. The <launch:info> extension must be used

3. If the request is for a Sunrise Application, the sunrise phase must be specified in the <launch:phase> element

4. If the request is for a Landrush Application, the claims phase must be specified in the <launch:phase> element, and the element must have the attribute ' name="landrush-[X]"', where X is 1,2,3 or 4. Eg: name=landrush-1 

5. For Sunrise Info, registrars may make use of the "includeMark" attribute with a value of "true" in the <launch:info> element to obtain the mark information in the response

6. The application ID; as provided from a successful create command; must be specified in the <launch:applicationID> element


COMMANDS
 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
      <info>
       <domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
         <domain:name>exampledomain.gtld</domain:name>
       </domain:info>
      </info>
      <extension>
       <launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" includeMark="true">
         <launch:phase>sunrise</launch:phase>
<launch:applicationID>UniqueApplicationID</launch:applicationID> </launch:info> </extension> </command> </epp>

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
      <info>
       <domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
         <domain:name>exampledomain.gtld</domain:name>
       </domain:info>
      </info>
      <extension>
       <launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
         <launch:phase name="landrush-[X]">claims</launch:phase>
<launch:applicationID>UniqueApplicationID</launch:applicationID> </launch:info> </extension> </command> </epp>



RESPONSES

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1000">
         <msg>Command completed successfully</msg>
       </result>
       <resData>
         <domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name>exampledomain.gtld</domain:name>
           <domain:roid>DomainRoid</domain:roid>
           <domain:status s="pendingCreate"/>
           <domain:registrant>RegistrantID</domain:registrant>
           <domain:clID>YourRegistrarID</domain:clID>
         </domain:infData>
       </resData>
       <extension>
         <launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
           <launch:phase>sunrise</launch:phase>
             <launch:applicationID>ProvidedApplicationID</launch:applicationID>
             <launch:status s="pendingValidation"/>
<mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
[MARK INFO HERE]
</mark:mark> </launch:infData> </extension> </response> </epp>

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1000">
         <msg>Command completed successfully</msg>
       </result>
       <resData>
         <domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name>exampledomain.gtld</domain:name>
           <domain:roid>DomainRoid</domain:roid>
           <domain:status s="pendingCreate"/>
           <domain:registrant>RegistrantID</domain:registrant>
           <domain:clID>RegistrarID</domain:clID>
         </domain:infData>
       </resData>
       <extension>
         <launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
           <launch:phase name="landrush-[X]">claims</launch:phase>
<launch:applicationID>UniqueApplicationID</launch:applicationID> <launch:status s="pendingAllocation"/> </launch:infData> </extension> <trID> </response> </epp>


Sunrise Info Response

- A status of "pendingCreate" will be set to all Sunrise Applications. This status will reflect in the <domain:status> element
- The <launch:applicationID> element will have a value matching the application ID provided to the registrar on Successful Application
- A status of "pendingValidation" will be set on the domain at Successful Application. The <launch:status> element will reflect this status
- The mark information will only be shown to the sponsoring registrar


Landrush Info Response

- A status of "pendingCreate" will be set to all Landrush Applications. This status will reflect in the <domain:status> element
- A status of "pendingAllocation" will be set on the domain at Successful Application. The <launch:status> element will reflect this status

 

Domain Create Command


Notes


1. For Sunrise Applications
    
- The sunrise phase must be specified in the <launch:phase> element
     - The registry makes use of the "signed mark" validation model, requiring the base64 encoded signed mark information. For more information on this type of SMD, please see Section 2.5 and Section 6.4  of the draft-lozano-tmch-smd specification.
     - The provided base64 SMD must be included in the <smd:encodedSignedMark> element

2. For Landrush Applications
     - The claims phase must be specified in the <launch:phase> element, and the element must have the attribute ' name="landrush-[X]"', where X is 1,2,3 or 4. Eg: name=landrush-1
     - The <launch:notice> element must be used to specify the information retrieved from the Claims Notice, if a Claims Notice was issued.
     - The Claims Notice would have been acquired using the Claims Key from the Domain Check command
     - The <launch:create> element may include the attribute "type". Registrars that include this element must assign a value of "application".
     - If the registry uses more that 1 validator, the value of the "validatorID" attribute of the <launch:noticeID> element must be that of the validator that provided the notice ID. This element may be omitted if the registry makes use of a single validator.
     - For registrations that do not have prior rights, the General Create Method must be used as outlined below

3. All associated information such as nameservers and associated contacts is required for application

4. Associated Contacts must be created in accordance to the specification outlined here. The Reseller contact declaration is OPTIONAL.

5. The specified nameservers do not have to be configured

6. The domain authorisation password must be specified

7. The <domain:period> element may be specified. If it is, a value between one (1) and ten (10) may be specified. If the element is not declared, the registry will default both application types to one (1) year. The Launch Polies pertaining to gTLDs, TLDs and SLDs will clearly outline the required period if there are constraints on registration periods.

8. If the <domain:period> element is specified, the registry will automatically set the renewal period to the value specified in the element. This means that any subsequent Domain Renew command that do not contain the domain period declaration will renew for an amount of years equal to the renewal period.



COMMANDS

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
       <create>
         <domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name>exampledomain.gtld</domain:name> 
<domain:period unit="y">2</domain:period>
        <domain:ns>
             <domain:hostAttr>
                 <domain:hostName>ns1.exampledomain.gtld</domain:hostName>
                  <domain:hostAddr ip="v4">x.x.x.x</domain:hostAddr>
                 <domain:hostAddr ip="v6">ff02::1</domain:hostAddr>
            </domain:hostAttr>
            <domain:hostAttr>
                 <domain:hostName>ns1.otherdomain.gtld</domain:hostName>
            </domain:hostAttr>
        </domain:ns>
<domain:registrant>RegistrantID</domain:registrant>
<domain:contact type="admin">AdminID</domain:contact>
<domain:contact type="tech">TechID</domain:contact>
        <domain:contact type="billing">BillingID</domain:contact>
<domain:contact type="reseller">ResellerContID</domain:contact>
<domain:authInfo>
          <domain:pw>TransferPassword</domain:pw>
        </domain:authInfo> </domain:create> </create> <extension> <launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> <launch:phase>sunrise</launch:phase> <smd:encodedSignedMark xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"> [SMD KEY HERE] </smd:encodedSignedMark> </launch:create> </extension> </command> </epp>

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
       <create>
         <domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name>exampledomain.gtld</domain:name>
<domain:period unit="y">1</domain:period>
        <domain:ns>
             <domain:hostAttr>
                 <domain:hostName>ns1.exampledomain.gtld</domain:hostName>
                  <domain:hostAddr ip="v4">x.x.x.x</domain:hostAddr>
                 <domain:hostAddr ip="v6">ff02::1</domain:hostAddr>
            </domain:hostAttr>
            <domain:hostAttr>
                 <domain:hostName>ns1.otherdomain.gtld</domain:hostName>
            </domain:hostAttr>
        </domain:ns>
<domain:registrant>RegistrantID</domain:registrant>
<domain:contact type="admin">AdminID</domain:contact>
<domain:contact type="tech">TechID</domain:contact>
        <domain:contact type="billing">BillingID</domain:contact>
<domain:contact type="reseller">ResellerContID</domain:contact>
<domain:authInfo>
          <domain:pw>TransferPassword</domain:pw>
        </domain:authInfo> </domain:create> </create> <extension> <launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" type="application"> <launch:phase name="landrush-[X]">claims</launch:phase>
<launch:notice>
<launch:noticeID validatorID="[tmch/mvs]">ABC4321</launch:noticeID> <launch:notAfter>2014-06-01T10:00:00Z</launch:notAfter>
<launch:acceptedDate>2014-05-01T10:10:00Z</launch:acceptedDate>
</launch:notice> </launch:create> </extension> </command> </epp>

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
       <create>
         <domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name>exampledomain.gtld</domain:name>
        <domain:ns>
             <domain:hostAttr>
                 <domain:hostName>ns1.exampledomain.gtld</domain:hostName>
                  <domain:hostAddr ip="v4">x.x.x.x</domain:hostAddr>
                 <domain:hostAddr ip="v6">ff02::1</domain:hostAddr>
            </domain:hostAttr>
            <domain:hostAttr>
                 <domain:hostName>ns1.otherdomain.gtld</domain:hostName>
            </domain:hostAttr>
        </domain:ns>
<domain:registrant>RegistrantID</domain:registrant>
<domain:contact type="admin">AdminID</domain:contact>
<domain:contact type="tech">TechID</domain:contact>
        <domain:contact type="billing">BillingID</domain:contact>
<domain:contact type="reseller">ResellerContID</domain:contact>
<domain:authInfo>
          <domain:pw>TransferPassword</domain:pw>
        </domain:authInfo> </domain:create> </create> <extension> <launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
type="application"> <launch:phase name="landrush-[X]">claims</launch:phase> </launch:create> </extension> </command> </epp>


RESPONSES


   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1001">
         <msg>Command completed successfully; validation pending</msg>
       </result>
       <resData>
         <domain:creData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
          <domain:name>exampledomain.gtld</domain:name>
          <domain:crDate>2014-03-01T10:00:00Z</domain:crDate>
         </domain:creData>
       </resData>
       <extension>
         <launch:creData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
           <launch:phase>sunrise</launch:phase>
           <launch:applicationID>UniqueApplicationID</launch:applicationID>
         </launch:creData>
       </extension>
     </response>
   </epp>

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1001">
         <msg>Command completed successfully; validation pending</msg>
       </result>
       <resData>
         <domain:creData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
          <domain:name>exampledomain.gtld</domain:name>
          <domain:crDate>2013-04-01T10:00:00Z</domain:crDate>
         </domain:creData>
       </resData>
       <extension>
         <launch:creData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
           <launch:phase name="landrush-[X]">claims</launch:phase>
           <launch:applicationID>UniqueApplicationID</launch:applicationID>
         </launch:creData>
       </extension>
     </response>
   </epp>


Sunrise Create Response

- The response will contain the date of the application in the <domain:crDate> element
- A unique Application Identifier will be provided in the response. The Application ID must be used for the Domain Info command
- The domain status will be set to "pendingCreate" on the domain until the end of the Sunrise Period. This will reflect in the <domain:status> element
- The launch application status will be set to "pendingValidation". This will reflect in the <launch:status> element


Landrush Create Response

- The response will contain confirmation that the domain has been applied for in the Landrush Period through the <launch:phase> element
- The response will contain a unique application ID that must be used in the Info command
- The status of the domain will be set to "pendingCreate". This status will be removed at the end of the Landrush Period
- The status "pendingAllocation" will be set in the <launch:status> element, indicating that the application is still pending review
- Domains that have been applied for may only become usable at the end of the Landrush Period if they are successfully delegated
- The registry will not perform checks on the provided nameservers until the current period concludes
- The registry will perform integrity checks on the provided contacts

Domain Update Command


The ZACR does not support the updating of Applications during the Launch Phase. Applicants must ensure that information is as accurate as possible prior to applying for the domain name.

It is recommended that for necessary amendments the Registrant instruct the Registrar to delete the application and reapply for the domain. Deletions are instant to allow for quick reapplication.

The deletion and reapplication for a domain name during the Launch Phase has no effect on the validation and allocation process for a domain name to its rightful Right Holder.

Approved applications will be able to be amended from the conclusion of the Launch Phase onwards.

 

Domain Delete Command


Notes


1. The <launch:delete> extension must be used

2. For Sunrise Applications, the sunrise phase must be specified in the <launch:phase> element

3. For Landrush Applications, the claims phase must be specified in the <launch:phase> element, and the element must have the attribute ' name="landrush-[X]"', where X is 1,2,3 or 4. Eg: name=landrush-1
4. The corresponding Application ID must be specified in the <launch:applicationID> element

5. The deletion of a domain during the Launch Phase will remove the application entirely

6. Applications that have been deleted during the Launch Phase may be reapplied for so long as the Launch Phase is still active


COMMAND

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
      <delete>
       <domain:delete xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
         <domain:name>exampledomain.gtld</domain:name>
       </domain:delete>
      </delete>
      <extension>
       <launch:delete xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
         <launch:phase>sunrise</launch:phase>
         <launch:applicationID>UniqueApplicationID</launch:applicationID>
       </launch:delete>
      </extension>
     </command>
   </epp>

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <command>
      <delete>
       <domain:delete xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
         <domain:name>exampledomain.gtld</domain:name>
       </domain:delete>
      </delete>
      <extension>
       <launch:delete xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
         <launch:phase name='landrush-[X]'>claims</launch:phase>
         <launch:applicationID>UniqueApplicationID</launch:applicationID>
       </launch:delete>
      </extension>
     </command>
   </epp>

 

RESPONSE


  <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1000">
         <msg>Command completed successfully</msg>
       </result>
</response>
</epp>


Poll Messages


Notes


1. Poll messages will be provided on any change to the application

2. Applications that enter the auction phase will receive a poll message

3. Applications that conclude an auction process will only receive a poll message indicating allocation or rejection of the application

 

Application Successful Poll Message


1. If the message in the <msg> element states "Application 'XYZ' for 'exampledomain.gtld' successfully allocated." it means that the application was successful and the domain name will soon be delegated. The <launch:phase> element will indicate the phase in which the application was made.

2. If the message in the <msg> element states "Application 'XYZ' for 'exampledomain.gtld' successfully allocated by auction." it means that the application was successful, having been the winning bid in an auction, and the doman name will soon be delegated. The <launch:phase> element will indicate the phase in which the application was made.

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1301">
         <msg>Command completed successfully; ack to dequeue</msg>
       </result>
         <qDate>2014-03-01T10:00:00.0Z</qDate>
         <msg>MESSAGE AS ABOVE</msg>
       </msgQ>
       <resData>
         <domain:panData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name paResult="1">exampledomain.gtld</domain:name>
           <domain:paTRID>
             <clTRID>ABC-12345</clTRID>
             <svTRID>54321-XYZ</svTRID>
           </domain:paTRID>
           <domain:paDate>2013-03-01T08:00:00.0Z</domain:paDate>
         </domain:panData>
       </resData>
       <extension>
         <launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
           <launch:phase>[SUNRISE/CLAIMS]</launch:phase>
             <launch:applicationID>UniqueApplicationID</launch:applicationID>
             <launch:status s="allocated"/>
         </launch:infData>
       </extension>
     </response>
   </epp>

 

Application Rejected Poll Messages


1. If the message in the <msg> element states "Application 'XYZ' for 'exampledomain.gtld' rejected: Contended application with a higher priority exists" it means that at the end of the Launch Phase the application did not have the highest priority. Therefore the application was not allocated, and an application with a higher priority was allocated.

This poll message will have an associated status message in the <launch:status> element of "Contended application with a higher priority exists" .

2. If the message in the <msg> element states "Application 'XYZ' rejected: Domain 'exampledomain.gtld' allocated in Sunrise" it means that the domain name underwent a Sunrise Dispute Resolution Process and was allocated to a Sunrise Application that prevailed.

This poll message will have an associated status message in the <launch:status> element of "Contended application allocated in Sunrise" .

3. If the message in the <msg> element states "Application 'XYZ' for 'exampledomain.gtld' outbid in auction." it means that the application was part of an auction process and was not the winning bid.

This poll message will have an associated status message in the <launch:status> element of "Application outbid in auction" .

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1301">
         <msg>Command completed successfully; ack to dequeue</msg>
       </result>
         <qDate>2014-03-01T10:00:00.0Z</qDate>
         <msg>MESSAGE AS ABOVE</msg>
       </msgQ>
       <resData>
         <domain:panData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name paResult="1">exampledomain.gtld</domain:name>
           <domain:paTRID>
             <clTRID>ABC-12345</clTRID>
             <svTRID>54321-XYZ</svTRID>
           </domain:paTRID>
           <domain:paDate>2013-03-01T08:00:00.0Z</domain:paDate>
         </domain:panData>
       </resData>
       <extension>
         <launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
           <launch:phase>[SUNRISE/CLAIMS]</launch:phase>
             <launch:applicationID>UniqueApplicationID</launch:applicationID>
             <launch:status s="rejected">STATUS AS ABOVE</launch:status>
         </launch:infData>
       </extension>
     </response>
   </epp>

Application In Auction Poll Message


1. The poll message will be queued if an application is being contested by another application for the same domain name, and has been marked to proceed to auction

2. The <launch:status> element will indicate a custom status of "pendingAuction" and a value of "DATE", where DATE is the date when the Sunrise Auction Process begins. DATE will be in UTC

 

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
     <response>
       <result code="1301">
         <msg>Command completed successfully; ack to dequeue</msg>
       </result>
         <qDate>2013-03-01T10:00:00.0Z</qDate>
         <msg>Application 'XYZ' for exampledomain.gtld has been queued auction.</msg>
       </msgQ>
       <resData>
         <domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
           <domain:name>example.tld</domain:name>
<domain:registrant>NewRegistrantID</domain:registrant> </domain:infData> </resData> <extension> <launch:infData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> <launch:phase>[SUNRISE/CLAIMS]</launch:phase> <launch:applicationID>UniqueApplicationID</launch:applicationID> <launch:status s="custom" name="pendingAuction">Auction commencing on [DATE]
</launch:status> </launch:infData> </extension> </response> </epp>

 

Last update: 04-04-2017 11:10:54

日日摸夜夜添夜夜添无码_最新亚洲中文字幕一区在线_尹人香蕉视频在线观看