Launch Phase

Transcription

Launch Phase

GUIDE TECHNIQUE – avril 2014
1
Functional
specifications for the
opening of registrations
of domain names with 1
& 2 characters in the .fr
TLD via EPP
Association Française pour le Nommage Internet en Coopération | www.afnic.fr | [email protected]
Twitter : @AFNIC | Facebook : afnic.fr
2
Contents
1. Preface ............................................................................................... 3
2. How the various phases work .......................................................... 3
2.1.1.
2.1.2.
2.1.3.
2.1.4.
Common specifications ................................................................................................................. 3
Sunrise ........................................................................................................................................... 3
Landrush ........................................................................................................................................ 4
General availability ....................................................................................................................... 4
3. EPP ..................................................................................................... 4
3.1. Production and test EPP servers .................................................................5
3.1.1. Production server ........................................................................................................................... 5
3.1.2. Test server ..................................................................................................................................... 5
3.2. The "Launch Phase" extension ....................................................................5
3.3. Sunrise............................................................................................................5
3.3.1.
3.3.2.
3.3.3.
3.3.4.
3.3.5.
Login ............................................................................................................................................. 5
Checking the availability of a domain name ................................................................................. 6
Sending a domain name application .............................................................................................. 7
Checking the status of an application ............................................................................................ 8
Deleting a domain name application ............................................................................................. 9
3.4. Landrush and general availability .............................................................. 10
3.5. EPP notifications ......................................................................................... 10
3.6. EPP server response codes........................................................................ 11
4. Extranet ............................................................................................ 11
5. Sending supporting documents ..................................................... 11
3
1. 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
2.1.1. Common specifications
2.1.1.1. 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.
2.1.1.2. 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, 9
2.1.1.3. 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
2.1.2. 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
List of application statuses:
Status displayed Corresponding status Description
in
EPP displayed on Extranet
(domain:info)
(application list)
pendingValidation A compléter (To be The application has been sent,
completed)
but
the
supporting
document(s) still need to be
sent via the extranet for the
application to be complete.
pendingValidation En attente de validation The application is complete
(Pending validation)
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.
2.1.3. 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.
2.1.4. General availability
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.
3. EPP
This chapter describes the login parameters and how the launchphase extension is used
for the Sunrise.
5
3.1. Production and test EPP servers
3.1.1. Production server
EPP server:
• epp.nic.fr
• port: 700
3.1.2. Test server
EPP server:
• epp.sandbox.nic.fr
• port: 700
3.2. The "Launch Phase" extension
The Launch Phase Mapping extension is used for managing the Sunrise
(http://tools.ietf.org/html/draft-ietf-eppext-launchphase-01). We invite you to read
the specifications of this extension carefully in order to incorporate it to your EPP client
easily.
3.3. Sunrise
3.3.1. 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="http://www.w3.org/2001/XMLSchema-instance"
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>http://www.afnic.fr/xml/epp/frnic-1.2</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
<clTRID>test-login</clTRID>
</command>
</epp>
3.3.2. 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:name>aa.fr</domain:name>
</domain:check>
</check>
<extension>
<launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
type="avail">
<launch:phase name=”1et2car”>custom</launch:phase>
</launch:check>
</extension>
<clTRID>8d81f30bc2ca9bbf0539e32bd9eab91680001ba2</clTRID>
</command>
</epp>
Response received by the EPP server:
<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>8d81f30bc2ca9bbf0539e32bd9eab91680001ba2</clTRID>
<svTRID>FR-SANDBOX-epp01-7915-151404459363.85108</svTRID>
</trID>
7
</response>
</epp>
3.3.3. 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:
<command>
<create>
<domain:create
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0 domain1.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>
<extension>
<launch:create
xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
type="application">
<launch:phase name="1et2car">custom</launch:phase>
</launch:create>
</extension>
<clTRID>exemple-1et2car-application</clTRID>
</command>
</epp>
Server response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response>
<msg>Command completed successfully; action pending</msg>
</result>
<msgQ count="229" id="54"/>
<resData>
<domain:creData
8
<domain:crDate>2014-07-03T13:03:54Z</domain:crDate>
<domain:exDate>2015-07-03T13:03:54Z</domain:exDate>
</domain:creData>
</resData>
<extension>
<launch:creData
xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
<launch:phase name="1et2car">custom</launch:phase>
<launch:applicationID>
FRS20140703150354GOVIZYPU35723348</launch:applicationID>
</launch:creData>
</extension>
<trID>
<clTRID>exemple-1et2car-application</clTRID>
<svTRID>FR-SANDBOX-epp01-6236-48-1404392606.90141</svTRID>
</trID>
</response>
</epp>
3.3.4. 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:
<command>
<info>
<domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
</domain:info>
</info>
<extension>
<launch:info xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
<launch:applicationID>FRS20140703150354GOVIZYPU35723348
</launch:applicationID>
</launch:info>
</extension>
<clTRID>exemple-1et2car-info</clTRID>
</command>
</epp>
Server response:
<response>
</result>
<msgQ count="235" id="54"/>
<resData>
<domain:infData
9
<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>2014-07-03T13:03:54Z</domain:crDate>
<domain:exDate>2015-07-03T13:03:54Z</domain:exDate>
<domain:upID>-registry-.fr</domain:upID>
<domain:upDate>2014-07-03T13:04:00Z</domain:upDate>
<domain:authInfo>
<domain:pw>test</domain:pw>
</domain:authInfo>
</domain:infData>
</resData>
<extension>
<launch:infData
xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
<launch:status s="pendingValidation"/>
</launch:infData>
</extension>
<trID>
<clTRID>exemple-1et2car-info</clTRID>
</trID>
</response>
</epp>
3.3.5. 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:
<command>
<delete>
<domain:delete
</domain:delete>
</delete>
<extension>
<launch:delete xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
</launch:delete>
</extension>
<clTRID>bc2ade1b460823674647afc5c8acb5d433a71ddf</clTRID>
</command>
10
</epp>
Server response:
<response>
</result>
<trID>
<clTRID>bc2ade1b460823674647afc5c8acb5d433a71ddf</clTRID>
</trID>
</response>
</epp>
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.
3.5. 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:
<response>
<msg>Command completed successfully; ack to dequeue</msg>
</result>
<msgQ count="1" id="4739">
<qDate>2014-08-20T15:53:49.0Z</qDate>
<msg>Application switches to "rejected" state</msg>
</msgQ>
<resData>
<domain:panData
<domain:name paResult="0">pp.fr</domain:name>
<domain:paTRID>
<clTRID>4775f6768d4f58187578e72ce8ee248a8e795338</clTRID>
</domain:paTRID>
<domain:paDate>2014-08-20T15:53:49.0Z</domain:paDate>
</domain:panData>
</resData>
<trID>
<clTRID>9b00d99fefe12bec420ff16cbc59de9290969e66</clTRID>
11
</trID>
</response>
</epp>
3.6. EPP server response codes
The result codes returned by the EPP server are described in RFC 5730.
(http://tools.ietf.org/html/rfc5730#section-3)
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).

Launch Phase

Transcription

Documents pareils

Functional and technical specifications of the developments

11-190 Nordson Corporation ("NDSN") 2-for-1 Stock Split