Functional specifications for the opening of registrations of domain names with 1 & 2 characters in the.fr TLD via EPP

Transcription

1 GUIDE TECHNIQUE avril Functional specifications for the opening of registrations of domain names with 1 & 2 characters in the.fr TLD via EPP

2 GUIDE TECHNIQUE avril C o n t e n t s 1. Preface How the various phases work Common specifications Sunrise Landrush General availability EPP Production and test EPP servers Production server Test server The "Launch Phase" extension Sunrise Login Checking the availability of a domain name Sending a domain name application Checking the status of an application Deleting a domain name application Landrush and general availability EPP notifications EPP server response codes Extranet Sending supporting documents... 11

3 GUIDE TECHNIQUE avril Preface This document describes how the opening of registrations of domain names with 1 and 2 characters in the.fr TLD operates via the EPP protocol. 2. How the various phases work Common specifications Scope The domain names to be opened to registration are those made up of either: - One alphabetic character; or - One numeric character; or - Two alphanumeric characters The IDN versions of alphabetic characters are provided below Syntactic constraints Accepted characters: a, à, á, â, ã, ä, å, æ, b, c, ç, d, e, è, é, ê, ë, f, g, h, i, ì, í, î, ï, j, k, l, m, n, ñ, o, ò, ó, ô, õ, ö, œ, p, q, r, s, t, u, ù, ú, û, ü, v, w, x, y, ý, ÿ, z, ß, 0, 1, 2, 3, 4, 5, 6, 7, 8, Excluded domain names - Excluded domain names include those made up of national country codes (fr.fr, re.fr, pm.fr, yt.fr, tf.fr, wf.fr, nc.fr, pf.fr, mf.fr, bl.fr, gp.fr, mq.fr, gf.fr) and their IDN version. - The following domain names are also excluded: co.fr, tm.fr, nh.fr Sunrise The Sunrise is an application submission phase that is handled on a first come, first served basis. Applications are stacked and processed as and when they arrive. The supporting documents required to validate an application should be sent via the extranet. If an application is valid and eligible according to the Registration Policy, the domain name is created. This phase lasts two months.

4 GUIDE TECHNIQUE avril List of application statuses: Status displayed Corresponding status in EPP displayed on Extranet (domain:info) (application list) pendingvalidation A compléter (To be completed) pendingvalidation En attente de validation (Pending validation) Description The application has been sent, but the supporting document(s) still need to be sent via the extranet for the application to be complete. The application is complete and is pending validation by Afnic. rejected Rejetée (Rejected) The application has been rejected. Either the application is invalid, or an earlier application has already been allocated according to first come, first served basis. allocated Attribuée (Allocated) The application has been allocated. The domain name has been created Landrush The Landrush is an immediate registration phase that is handled on a first come, first served basis. Domain names applied for during the Sunrise cannot be registered until their respective applications have been processed by Afnic. This phase lasts one month General availability 3. EPP The general availability phase is an immediate registration phase that is handled on a first come, first served basis. Domain names applied for during the Sunrise cannot be registered until their respective applications have been processed by Afnic. This phase has no time limit. This chapter describes the login parameters and how the launchphase extension is used for the Sunrise.

5 GUIDE TECHNIQUE avril Production and test EPP servers Production server EPP server: epp.nic.fr port: Test server EPP server: epp.sandbox.nic.fr port: The "Launch Phase" extension The Launch Phase Mapping extension is used for managing the Sunrise ( We invite you to read the specifications of this extension carefully in order to incorporate it to your EPP client easily Sunrise Login As indicated by the <greeting> from the EPP server, the Launch Phase extension must be declared in the <login> command if you wish to apply for a domain name with 1 or 2 characters during the Sunrise. Example of a login request: <?xml version="1.0" encoding="utf-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"> <command> <login> <clid>-test-.fr</clid> <pw>motdepasse</pw> <options> <version>1.0</version> <lang>en</lang> </options> <svcs> <objuri>urn:ietf:params:xml:ns:domain-1.0</objuri> <objuri>urn:ietf:params:xml:ns:contact-1.0</objuri> <svcextension> <exturi> <exturi>urn:ietf:params:xml:ns:rgp-1.0</exturi> <exturi>urn:ietf:params:xml:ns:secdns-1.1</exturi> <exturi>urn:ietf:params:xml:ns:launch-1.0</exturi> </svcextension> </svcs> </login>

6 GUIDE TECHNIQUE avril <cltrid>test-login</cltrid> </command> Checking the availability of a domain name You can check the availability of a domain name with 1 or 2 characters throughout the duration of the Sunrise. Given that we use the LaunchPhase extension, you must indicate the <launch:check> type (i.e. 'avail'), and the <launch:phase> values (i.e. 'custom' / name= '1et2car'). This command may contain up to seven domain names. Example of a request sent during the Sunrise: <?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>po.fr</domain:name> </domain:check> </check> <launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" type="avail"> <launch:phase name= 1et2car >custom</launch:phase> </launch:check> <cltrid>8d81f30bc2ca9bbf0539e32bd9eab ba2</cltrid> </command> Response received by the EPP server: <?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"> <domain:cd> <domain:name avail="1">po.fr</domain:name> </domain:cd> <domain:cd> <domain:name avail="1">aa.fr</domain:name> </domain:cd> </domain:chkdata> </resdata> <trid> <cltrid>8d81f30bc2ca9bbf0539e32bd9eab ba2</cltrid> <svtrid>fr-sandbox-epp </svtrid> </trid>

7 GUIDE TECHNIQUE avril </response> Sending a domain name application To send a domain name application during the Sunrise, you must specify the <launch:create> type (i.e. 'application'), and the <launch:phase> values (i.e. 'custom' / name='1et2car'). The server will return an application number (applicationid). Example of a request sent: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"> <command> <create> <domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xsi:schemalocation="urn:ietf:params:xml:ns:domain-1.0 domain- 1.0.xsd"> <domain:period unit="y">1</domain:period> <domain:registrant>jj100</domain:registrant> <domain:contact type="admin">jj100</domain:contact> <domain:contact type="tech">jj100</domain:contact> <domain:authinfo> <domain:pw>test</domain:pw> </domain:authinfo> </domain:create> </create> <launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" type="application"> <launch:phase name="1et2car">custom</launch:phase> </launch:create> <cltrid>exemple-1et2car-application</cltrid> </command> Server response: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"> <response> <result code="1001"> <msg>command completed successfully; action pending</msg> </result> <msgq count="229" id="54"/> <resdata> <domain:credata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">

8 GUIDE TECHNIQUE avril <domain:crdate> t13:03:54z</domain:crdate> <domain:exdate> t13:03:54z</domain:exdate> </domain:credata> </resdata> <launch:credata xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> <launch:phase name="1et2car">custom</launch:phase> <launch:applicationid> FRS GOVIZYPU </launch:applicationID> </launch:credata> <trid> <cltrid>exemple-1et2car-application</cltrid> <svtrid>fr-sandbox-epp </svtrid> </trid> </response> Checking the status of an application Once your applications have been sent, you can check their status using the applicationid received after sending them. Example of a request sent: <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:info> </info> <launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> <launch:phase name= 1et2car >custom</launch:phase> <launch:applicationid>frs govizypu </launch:applicationid> </launch:info> <cltrid>exemple-1et2car-info</cltrid> </command> Server response: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"> <response> <result code="1001"> <msg>command completed successfully</msg> </result> <msgq count="235" id="54"/> <resdata> <domain:infdata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">

9 GUIDE TECHNIQUE avril <domain:roid/> <domain:status s="inactive"/> <domain:status s="pendingcreate"/> <domain:registrant>jj100</domain:registrant> <domain:contact type="admin">jj100</domain:contact> <domain:contact type="tech">jj100</domain:contact> <domain:clid>>-test-.fr</domain:clid> <domain:crid>>-test-.fr</domain:crid> <domain:crdate> t13:03:54z</domain:crdate> <domain:exdate> t13:03:54z</domain:exdate> <domain:upid>-registry-.fr</domain:upid> <domain:update> t13:04:00z</domain:update> <domain:authinfo> <domain:pw>test</domain:pw> </domain:authinfo> </domain:infdata> </resdata> <launch:infdata xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> <launch:phase name= 1et2car >custom</launch:phase> <launch:applicationid>frs govizypu </launch:applicationid> <launch:status s="pendingvalidation"/> </launch:infdata> <trid> <cltrid>exemple-1et2car-info</cltrid> <svtrid>fr-sandbox-epp </svtrid> </trid> </response> Deleting a domain name application The application can only be deleted if it is not in "allocated" or "rejected" status. Deletion will move the application to the "rejected" status, after which the application cannot be restored. Example of a request to delete an application: <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:delete> </delete> <launch:delete xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"> <launch:phase name= 1et2car >custom</launch:phase> <launch:applicationid>frs govizypu </launch:applicationid> </launch:delete> <cltrid>bc2ade1b afc5c8acb5d433a71ddf</cltrid> </command>

10 GUIDE TECHNIQUE avril Server 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> <trid> <cltrid>bc2ade1b afc5c8acb5d433a71ddf</cltrid> <svtrid>fr-sandbox-epp </svtrid> </trid> </response> 3.4. Landrush and general availability For both phases, the "Launch Phase" extension is not required in <create> commands. Simply send domain name <create> requests without the extension EPP notifications An EPP notification is stacked in your poll queue every time the application status changes. Simply unstack your poll queue to view the status change of the application in question. Example of a notification received when an application is rejected: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"> <response> <result code="1301"> <msg>command completed successfully; ack to dequeue</msg> </result> <msgq count="1" id="4739"> <qdate> t15:53:49.0z</qdate> <msg>application switches to "rejected" state</msg> </msgq> <resdata> <domain:pandata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> <domain:name paresult="0">pp.fr</domain:name> <domain:patrid> <cltrid>4775f6768d4f e72ce8ee248a8e795338</cltrid> <svtrid>fr-sandbox-epp </svtrid> </domain:patrid> <domain:padate> t15:53:49.0z</domain:padate> </domain:pandata> </resdata> <trid> <cltrid>9b00d99fefe12bec420ff16cbc59de e66</cltrid>

11 GUIDE TECHNIQUE avril <svtrid>fr-sandbox-epp </svtrid> </trid> </response> 3.6. EPP server response codes The result codes returned by the EPP server are described in RFC ( If a problem occurs, EPP server responses generally include a <msg> element containing relevant information for debugging purposes. 4. Extranet You will be able to send your applications directly via the Extranet. A second application form dedicated to the Sunrise will be available in the "Mes formulaires" (My Forms) section. 5. Sending supporting documents This section only pertains to the Sunrise. As the EPP server (and the application form on the Extranet) cannot provide all the types of supporting documents required in order to validate your domain name applications, a Web interface has been developed within your Extranet. This interface will enable you to: - View all the applications received and accepted by the EPP server (or by the Extranet), along with their status, - Add supporting documents to your applications received and accepted by the EPP server (or by the Extranet).