DOMREG

KTU ITPI

.LT domain registration guidelines

Version 1.0D

Part II EPP system

2012-11-22

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

Change log
2012-11-22 Version 1.0D Add secDNS extension documentation Add info:permit command description Fix contact:create description - <org> and <street> minimum length 2 Fix contact:update description - <street> minimum length 2 Added EPP poll messages renewed and quarantined 2007-04-04 Version 1.0C Corrected errors in EPP command examples. Updated comments to contact object country code (cc) attribute. 2007-02-23 Version 1.0B Updated EPP objects used within KTU ITPI section Added information in Command POLL chapter

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

Table of contents
.LT domain registration guidelines................................................................................. 1 Part II.............................................................................................................................. 1 EPP system..................................................................................................................... 1 Change log......................................................................................................................2 Table of contents.............................................................................................................3 Introduction.................................................................................................................... 4 User ID and password ............................................................................................... 4 About EPP and KTU ITPI .lt domain administration system.....................................4 Transport and security................................................................................................ 4 Versions and ports.......................................................................................................5 XML........................................................................................................................... 5 EPP objects used within KTU ITPI................................................................................ 6 EPP commands in use.....................................................................................................7 Command HELLO / GREETING ............................................................................. 8 Command LOGIN...................................................................................................... 9 Command LOGOUT................................................................................................ 11 Command CREATE CONTACT..............................................................................12 Command UPDATE CONTACT..............................................................................14 Command DELETE CONTACT..............................................................................16 Command INFO CONTACT....................................................................................17 Command CREATE NSGROUP..............................................................................19 Command UPDATE NSGROUP............................................................................. 20 Command DELETE NSGROUP..............................................................................21 Command CHECK NSGROUP............................................................................... 22 Command INFO NSGROUP................................................................................... 24 Command CREATE DOMAIN................................................................................ 25 Command UPDATE DOMAIN................................................................................28 Command DELETE DOMAIN................................................................................ 31 Command TRANSFER DOMAIN...........................................................................32 Command CHECK DOMAIN................................................................................. 35 Command INFO DOMAIN......................................................................................37 Command INFO PERMIT....................................................................................... 40 Command POLL...................................................................................................... 43 Not used EPP commands..............................................................................................46 Command RENEW DOMAIN.................................................................................46 Command CHECK CONTACT............................................................................... 46 Command TRANSFER CONTACT........................................................................ 46

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

Introduction
The document describes EPP system and XML documents, which can be used for work with .lt domain administration system. Synchronous system, implemented with EPP interface proposes dialog possibility with domain administration system. Using this interface, registrar can interconnect his client service system with .lt domain administration system and thus automate domain administration process. Kaunas University of Technology Information Technology Development Institute (KTU ITPI) doesnt provide any client software. It is responsibility of the registrar to create its own interface to communicate with .lt domain administration system, using EPP protocol and XML schemas.

User ID and password

User ID and password must be used to access the EPP system. The user ID is the registrar ID that you have been provided upon registration as a registrar. The password is the one that you have chosen when you activated your account.

About EPP and KTU ITPI .lt domain administration system

EPP protocol is general and has been created insomuch that would be perfect for all top level domain administration models, leaving the possibility of using protocol extensions (if it is necessary). EPP has some fundamental differences with KTU ITPI .lt domain administration system, therefore KTU ITPI uses EPP modification, which is fitted to .lt domain administration system. This EPP modification was created so, that it would differ as less as possible from standard EPP protocol. Documents, describing EPP protocol: RFC3730 Extensible Provisioning Protocol (EPP) RFC3731 Extensible Provisioning Protocol (EPP) Domain Name Mapping RFC3732 Extensible Provisioning Protocol (EPP) Host Mapping RFC3733 Extensible Provisioning Protocol (EPP) Contact Mapping RFC3734 Extensible Provisioning Protocol (EPP) Transport Over TCP RFC5910 Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)

Transport and security

KTU ITPI is providing EPP only on a Secure Socket Layer (SSL) mechanism and Standard TCP/IP sockets. KTU ITPI is providing only connection-oriented EPP service. .LT domain registration guidelines. EPP system. 4

DOMREG

KTU ITPI

Versions and ports

EPP protocol standard determine that (as returned by the greeting and required by the login command) EPP version field should be 1.0. KTU ITPI system uses official EPP system port 700.

XML
XML is case sensitive. All XML instances must begin with 4 bytes indicating the total message size (including the 4 bytes), followed by <?xml?> declaration, using a recognized character set UTF-8 with an XML version of 1.0. All EPP commands are enclosed within an <epp></epp> XML block. The server will parse incoming XML messages on the socket by reading 4 bytes, and then by reading a block of the size indicated by the 4 bytes, less 4. This message is processed and the response is sent back on the socket (also preceded by a 4 byte number in Network order) before the next message can be processed.

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

EPP objects used within KTU ITPI

epp: namespace: urn:ietf:params:xml:ns:eppcom-1.0 schema: epp-1.0.xsd (generic document, containing the root element: <epp>) eppcom: namespace: urn:ietf:params:xml:ns:eppcom-1.0 schema: eppcom-1.0.xsd (generic data definitions) domain: namespace: http://www.domreg.lt/epp/xml/domain-1.0 schema: domreg-domain-1.0.xsd (domain object specific commands) contact: namespace: http://www.domreg.lt/epp/xml/contact-1.0 schema: domreg-contact-1.0.xsd (contact object specific commands) nsgroup: namespace: http://www.domreg.lt/epp/xml/nsgroup-1.0 schema: domreg-nsgroup-1.0.xsd (added to handle DNS servers groups) event: namespace: http://www.domreg.lt/epp/xml/domreg-event-1.0 schema: domreg-event-1.0.xsd (event object specific commands) permit: namespace: http://www.domreg.lt/epp/xml/domreg-permit-1.0 schema: domreg-permit-1.0.xsd (checks if domain transfer/trade/create would be possible) secDNS: namespace: urn:ietf:params:xml:ns:secDNS-1.1 schema: secDNS-1.1.xsd (DNSSEC extensions)

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

EPP commands in use

KTU EPP system uses particular command set: hello login logout create update delete check info transfer poll Some of the commands are used alone, some of them pursuing defined operations with EPP system objects. contact domain nsgroup permit

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

Command HELLO / GREETING

PURPOSE: to obtain information from the EPP server that will handle your requests. A client can request a <greeting> form the EPP server by sending <hello> command at any time:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <hello/> </epp>

An EPP server responds to an <hello> command by returning a <greeting>:

<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <greeting> <svID>domreg.lt</svID> <svDate>2006-12-15T17:07:26+02:00</svDate> <svcMenu> <version>1.0</version> <lang>lt</lang> <lang>en</lang> <objURI>urn:ietf:params:xml:ns:epp-1.0</objURI> <objURI>http://www.domreg.lt/epp/xml/domreg-contact-1.0</objURI> <objURI>http://www.domreg.lt/epp/xml/domreg-domain-1.0</objURI> <objURI>http://www.domreg.lt/epp/xml/domreg-nsgroup-1.0</objURI> </svcMenu> <dcp> <access> <all/> </access> <statement> <purpose> <admin/> <prov/> </purpose> <recipient> <ours/> <public/> </recipient> <retention> <stated/> </retention> </statement> </dcp> </greeting> </epp>

Remarks: <svID> contains the name of the server <svDate> contains the server current date and time <svcMenu> contains the services supported by the server <lang> contains the text response language currently supported, as defined in [RFC3066]. Only lt (Lithuanian) and en (English) languages are supported at the moment. <objURI> contains the list of namespace URIs representing extended objects that the server is capable of managing: contact, domain, nsgroup <dcp> contains the information, associated with policy of privacy .LT domain registration guidelines. EPP system. 8

DOMREG

KTU ITPI

Command LOGIN
PURPOSE: is used to authenticate the client/user to the EPP server. It must be sent before any other command (except <hello>). User ID and EPP password will be used to authenticate the party that wants to set up the session with EPP server. Structure of command LOGIN: TAG <epp> <command> <login> <clID> <pw> <newPW> <options> <version> <lang> <svcs> <objURI> <clTRID> Remarks: <clID> contains the registrar ID of the connecting client. <pw> contains the EPP password of the connecting client (registrar). <newPW> this attribute is unusable <version> contains the EPP version the client supports. It has to correspond to suggested version in servers <greeting> command <lang> contains the preferred language of the client for this connection. It has to correspond to suggested language in servers <greeting> command <objURI> contains the list of namespace URI, which are going to be used during the session <clTRID> each transaction can be completed with a user provided transaction ID that can be used to identify a transaction. Example: Client sends to server:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <command> <login> <clID>r000001</clID> <pw>aaaaaa</pw> <options> <version>1.0</version> <lang>en</lang> </options> <svcs>

Occurrences (min-max) 1 1 1 1 0-1 1 1 1 1 1-* 0-1

Size, remarks

3-16 6-16 6-16 Regular expression [1-9]+\.[0-9]+ lt or en Any URI 3-64

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

<objURI>http://www.domreg.lt/epp/xml/domreg-domain-1.0</objURI> </svcs> </login> <clTRID>abc123</clTRID> </command> </epp>

An EPP connection is kept open by the server between a <login> and a <logout> command from the client, using the same socket connection. The EPP connection is closed without logout if the client closes socket. However, to ensure responsible behavior, a client should disconnect the SSL socket only after the EPP <logout> command. The server responds to a <login> command with a result code of 1000 (Command completed successfully.) or 2200 (Authentication error).
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <trID> <clTRID>abc123</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

10

DOMREG

KTU ITPI

Command LOGOUT
PURPOSE: The EPP <logout> command is used to close a session with the EPP server. The transport connection (SSL socket) is closed by the server after the <logout> response is sent. The <logout> is a very easy command and doesnt take any other elements or attributes.
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <command> <logout/> <clTRID>ABC-12345</clTRID> </command> </epp>

The server responds with a result code of 1500 (Command completed successfully; ending session)
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1500"> <msg>Command completed successfully; ending session</msg> </result> <trID> <clTRID>ABC-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

11

DOMREG

KTU ITPI

Command CREATE CONTACT

PURPOSE: to create a registrant or technical contact object. TAG <epp> <command> <create> <postalInfo> <name> <org> <addr> <street> <city> <sp> <pc> <cc> <voice> <fax> <email> <role> <clTRID> Remarks: <name> contains the complete name of the contact to create. <org> contains the company name of the contact, if contact represents legal entity <street> contains the postal street information. <city> contains the city. <sp> contains the state or province. <pc> contains the postal code. <cc> contains the country code, as defined in [ISO3166]. Country code must be in small letters. <voice> contains the telephone number of the contact that is being created. A phone number is a string that must begin with a plus sign (+) followed by a country code, followed by a dot (.), followed by a sequence of digits representing the telephone number. <fax> contains the facsimile number. The syntax is the same as for telephone. <email> contains the e-mail address . The syntax is defined in [RFC2822]. <role> contains role of contact object: registrant or tech. registrant must be specified, when registrant object have to be created. tech must be specified, when registrants technical contact or registrars technical contact have to be created. Example: Client sends to server:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">

Occurrences (min-max) 1 1 1 1 0-1 1 1 1 0-1 0-1 1 1 0-1 1 1 0-1

Size, remarks

2-255 2-255 2-255 2-255 0-255 0-16 2, country code must be in small letters Regular expression (\+[0-9]{1,3}\.[0-9]{1,14})? Regular expression (\+[0-9]{1,3}\.[0-9]{1,14})? RFC2822 format registrant or tech 3-64

.LT domain registration guidelines. EPP system.

12

DOMREG

KTU ITPI

<command> <create> <contact:create xmlns:contact="http://www.domreg.lt/epp/xml/domreg-contact-1.0"> <contact:postalInfo type="loc"> <contact:name>John Doe</contact:name> <contact:org>Example Inc.</contact:org> <contact:addr> <contact:street>New st. 12</contact:street> <contact:city>The new city</contact:city> <contact:sp>VA</contact:sp> <contact:pc>20166-6503</contact:pc> <contact:cc>us</contact:cc> </contact:addr> </contact:postalInfo> <contact:voice>+1.7035555555</contact:voice> <contact:fax>+1.7035555556</contact:fax> <contact:email>jdoe--@example.com</contact:email> <contact:role>registrant</contact:role> </contact:create> </create> <clTRID>client-111</clTRID> </command> </epp>

The server responds with a result code of 1000 (Command completed successfully) and with a message containing the newly created object ID and the creation date.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <contact:creData xmlns:contact="http://www.domreg.lt/epp/xml/domregcontact-1.0"> <contact:id>RN8</contact:id> <contact:crDate>2006-12-21T15:45:06+02:00</contact:crDate> </contact:creData> </resData> <trID> <clTRID>client-111</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

13

DOMREG

KTU ITPI

Command UPDATE CONTACT

PURPOSE: An EPP contact <update> command provides an operation that allows a client to modify the attributes of a contact object. KTU ITPI EPP <update> command version do not use add or rem command. It uses only chg command. To add new attribute, just provide it in <update> command. To delete unwanted attribute just provide this attribute in <update> command without information. All other attributes in <update> command will replace old attribute information with new. Attributes not provided in <update> command will remain unchanged. TAG <epp> <command> <update> <id> <chg> <postalInfo> <name> <org> <addr> <street> <city> <sp> <pc> <cc> <voice> <fax> <email> <clTRID> Remarks: <id> contains the ID of contact object that you want to update. Example: Client sends to server:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <update> <contact:update xmlns:contact="http://www.domreg.lt/epp/xml/domreg-contact-1.0"> <contact:id>RN8</contact:id> <contact:chg> <contact:postalInfo type="loc"> <contact:addr>

Occurrences (min-max) 1 1 1 1 0-1 0-1 0-1 0-1 0-1 0-1 0-1 0-1 0-1 0-1 0-1 0-1 0-1

Size, remarks

3-16 2-255 0-255 2-255 2-255 0-255 0-16 2, country code must be in small letters Regular expression (\+[0-9]{1,3}\.[0-9]{1,14})? Regular expression (\+[0-9]{1,3}\.[0-9]{1,14})? RFC2822 format 3-64

.LT domain registration guidelines. EPP system.

14

DOMREG

KTU ITPI

<contact:street>Good st. 7</contact:street> </contact:addr> </contact:postalInfo> <contact:voice>+1.7030000000</contact:voice> </contact:chg> </contact:update> </update> <clTRID>client-112</clTRID> </command> </epp>

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <clTRID>client-112</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

15

DOMREG

KTU ITPI

Command DELETE CONTACT

PURPOSE: An EPP contact <delete> command provides an operation that allows a client to delete an existing contact object. EPP command <delete> is very simple: TAG <epp> <command> <delete> <id> <clTRID> Remarks: <id> contains the contact object ID that you want to delete. Example: Client sends the command to server to delete contact person object, which ID is RN9:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <delete> <contact:delete xmlns:contact="http://www.domreg.lt/epp/xml/domreg-contact-1.0"> <contact:id>RN9</contact:id> </contact:delete> </delete> <clTRID>DEL-12345</clTRID> </command> </epp>

Occurrences (min-max) 1 1 1 0-1

Size, remarks

3-16 3-64

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <clTRID>DEL-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

16

DOMREG

KTU ITPI

Command INFO CONTACT

PURPOSE: the EPP <info> command is used to retrieve information, associated with a contact object. TAG <epp> <command> <info> <id> <clTRID> Remarks: <id> contains the contact object ID for which you want to obtain the information. Example: Client sends the command to server to get the information about contact person object with ID RN8.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <contact:info xmlns:contact="http://www.domreg.lt/epp/xml/domreg-contact-1.0"> <contact:id>RN8</contact:id> </contact:info> </info> </command> </epp>

Occurrences (min-max) 1 1 1 0-1

Size, remarks

3-16 3-64

The server responds with a result code of 1000 (Command completed successfully) and gives the information about contact person object:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <contact:infData xmlns:contact="http://www.domreg.lt/epp/xml/domregcontact-1.0"> <contact:id>RN8</contact:id> <contact:postalInfo type="loc"> <contact:name>John Doe</contact:name> <contact:org>Example Inc.</contact:org> <contact:addr> <contact:street>Good st. 7</contact:street> <contact:city>The new city</contact:city>

.LT domain registration guidelines. EPP system.

17

DOMREG

KTU ITPI

<contact:sp>VA</contact:sp> <contact:pc>20166-6503</contact:pc> <contact:cc>us</contact:cc> </contact:addr> </contact:postalInfo> <contact:voice>+1.7030000000</contact:voice> <contact:fax>+1.7035555556</contact:fax> <contact:email>jdoe--@example.com</contact:email> <contact:role>registrant</contact:role> <contact:crDate>2006-12-21T15:45:06+02:00</contact:crDate> <contact:upDate>2006-12-28T12:15:51+02:00</contact:upDate> </contact:infData> </resData> <trID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

18

DOMREG

KTU ITPI

Command CREATE NSGROUP

PURPOSE: create a list of DNS servers that can be used as a placeholder on a domain registration. This is KTU ITPI specific extension, documented in the schema domreg-nsgroup1.0.xsd The nsgroup object allows a registrar to group several DNS servers in one object, to facilitate the mapping between domains and DNS servers list. TAG <epp> <command> <create> <name> <ns> <clTRID> Remarks: <name> contains the (chosen) name for the DNS servers group. <ns> contains the name of DNS server address. Example: Client sends the command to server to create a new DNS servers group object, which name is group-1:
<?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"> <command> <create> <nsgroup:create xmlns:nsgroup="http://www.domreg.lt/epp/xml/domreg-nsgroup-1.0"> <nsgroup:name>group-1</nsgroup:name> <nsgroup:ns>ns1.domreg.lt</nsgroup:ns> <nsgroup:ns>ns2.domreg.lt</nsgroup:ns> </nsgroup:create> </create> <clTRID>NS-12345</clTRID> </command> </epp>

Occurrences (min-max) 1 1 1 0-13 0-1

Size, remarks

1-100 1-255 3-64

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <clTRID>NS-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

19

DOMREG

KTU ITPI

Command UPDATE NSGROUP

PURPOSE: to update the contents of a DNS servers group. When updating a DNS servers group, you are replacing all existing DNS servers by the set provided in the update command. So if you want to keep the existing DNS servers and just add another one, you need to respecify the old ones and add the new one. TAG <epp> <command> <update> <name> <ns> <clTRID> Remarks: <name> contains the name of DNS server group object, which information should be changed. <ns> contains the name of DNS server address. Example: Client sends the command to server to create a new DNS servers group object:
<?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"> <command> <update> <nsgroup:update xmlns:nsgroup="http://www.domreg.lt/epp/xml/domreg-nsgroup-1.0"> <nsgroup:name>group-1</nsgroup:name> <nsgroup:ns>ns1.domreg.lt</nsgroup:ns> <nsgroup:ns>ns2.domreg.eu</nsgroup:ns> <nsgroup:ns>ns3.domreg.eu</nsgroup:ns> </nsgroup:update> </update> <clTRID>ZZZ-12345</clTRID> </command> </epp>

Occurrence (min-max) 1 1 1 0-13 0-1

Size, remarks

1-100 1-255 3-64

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <clTRID>ZZZ-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

20

DOMREG

KTU ITPI

Command DELETE NSGROUP

PURPOSE: to delete a DNS server group. In EPP DNS servers group command it is necessary to indicate the name of group object, which should be deleted. TAG <epp> <command> <delete> <name> <clTRID> Remarks: <name> contains the name of the DNS server group that should be deleted. It is not possible to delete a DNS server group that is still used for one or more domains. Example: Client sends the command to server to delete DNS server group object, which name is group-1:
<?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"> <command> <delete> <nsgroup:delete xmlns:nsgroup="http://www.domreg.lt/epp/xml/domreg-nsgroup-1.0"> <nsgroup:name>group-1</nsgroup:name> </nsgroup:delete> </delete> <clTRID>123-12345</clTRID> </command> </epp>

Occurrences (min-max) 1 1 1 0-1

Size, remarks

1-100 3-64

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <clTRID>123-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

21

DOMREG

KTU ITPI

Command CHECK NSGROUP

PURPOSE: command is used to determine would it be possible to define name for new DNS servers group, or this name already in use. TAG <epp> <command> <check> <name> <clTRID> Remarks: <name> contains the name of the DNS servers group, which you want to check. Example: Client sends the command to server to check if it is possible to create DNS servers group objects, which names would be group-1, group-2 and group-3:
<?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"> <command> <check> <nsgroup:check xmlns:nsgroup="http://www.domreg.lt/epp/xml/domreg-nsgroup-1.0"> <nsgroup:name>group-1</nsgroup:name> <nsgroup:name>group-2</nsgroup:name> <nsgroup:name>group-3</nsgroup:name> </nsgroup:check> </check> <clTRID>CHECK-12345</clTRID> </command> </epp>

Occurrence (min-max) 1 1 1-* 0-1

Size, remarks

1-100 3-64

The server responds with a result code of 1000 (Command completed successfully). In response every <nsgroup:name> attribute avail value shows 0 or 1. Value 0 means, that this DNS server group already in use, and cant be used for new DNS servers group. Value 1 means, that there is no DNS servers group with this name. It can be used for new DNS server group name:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <nsgroup:chkData xmlns:nsgroup="http://www.domreg.lt/epp/xml/domregnsgroup-1.0"> <nsgroup:cd>

.LT domain registration guidelines. EPP system.

22

DOMREG

KTU ITPI

<nsgroup:name avail="0">group-1</nsgroup:name> </nsgroup:cd> <nsgroup:cd> <nsgroup:name avail="1">group-2</nsgroup:name> </nsgroup:cd> <nsgroup:cd> <nsgroup:name avail="1">group-3</nsgroup:name> </nsgroup:cd> </nsgroup:chkData> </resData> <trID> <clTRID>CHECK-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

23

DOMREG

KTU ITPI

Command INFO NSGROUP

PURPOSE: allows the registrar to retrieve information about the current information of an existing DNS servers group. TAG <epp> <command> <info> <name> <clTRID> Remarks: <name> contains the name of the DNS servers group, which information you want to get. Example: Client sends the command to server to receive the information about DNS server group object with name group-1:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <nsgroup:info xmlns:nsgroup="http://www.domreg.lt/epp/xml/domreg-nsgroup-1.0"> <nsgroup:name>group-1</nsgroup:name> </nsgroup:info> </info> </command> </epp>

Occurrences (min-max) 1 1 1 0-1

Size, remarks

1-100 3-64

The server responds with a result code of 1000 (Command completed successfully) and gives information about DNS servers group:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <nsgroup:infData xmlns:nsgroup="http://www.domreg.lt/epp/xml/domregnsgroup-1.0"> <nsgroup:name>group-1</nsgroup:name> <nsgroup:ns>ns1.domreg.lt</nsgroup:ns> <nsgroup:ns>ns2.domreg.eu</nsgroup:ns> <nsgroup:ns>ns3.domreg.eu</nsgroup:ns> </nsgroup:infData> </resData> <trID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

24

DOMREG

KTU ITPI

Command CREATE DOMAIN

PURPOSE: command creates domain object. TAG <epp> <command> <create> <name> <onExpire> <ns> <hostGroup> <hostAttr> <hostName> <hostAddr> <registrant> <contact> <clTRID> Remarks: <name> Domain name to be registered. Domain name must be specified with .lt in the end. Domain name can have Latin letters a-z, digits 0-9, - symbol. Domain name can not start or end with - symbol. - symbol can not be in 3rd and 4th position except internationalized domain names (IDN). IDN name can be specified in UTF-8 or ASCII representation with xn-- prefix. Domain name or its IDN representation must be from 2 till 63 symbol length. <onExpire> if this attribute is not indicated, it is treated, that domain will be renewed in the end of the term. It is possible to indicate delete value in this attribute. In this case in the end of current term domain will be deleted. If indicated renew value, it will be renewed in the end of current term. <ns> Must be specified in order to provide domain delegation (authoritative DNS servers for this domain) information. <hostGroup> can be indicated up to 13 DNS servers group. <hostAttr> can be indicated up to 13 DNS servers <hostName> contains DNS server address name. <hostAddr> If necessary, DNS server IP address must be provided in version 4 or version 6 format. Can be provided 1 v4 and one v6 IP addresses. DNS server IP address must be provided if DNS server name is subdomain of domain to be registered. Ex.: <name> is example.lt and <hostName> is ns.example.com. <registrant> contains domain registrant contact person object ID. <contact> contains domain technical contact person object ID. ATTENTION! Number of specified DNS servers in <hostGroup> and <hostAttr> attributes cant be more that 13. Occurrences (min-max) 1 1 1 0-1 0-1 0-13 0-13 1 0-2 1 1-7 0-1 Size, remarks

1-255 delete or renew 1-100 1-255 3-45,possible attribute ip. Values v4 and v6 3-16 3-16 3-64

.LT domain registration guidelines. EPP system.

25

DOMREG

KTU ITPI

Example: Client sends to server:

<?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"> <command> <create> <domain:create xmlns:domain="http://www.domreg.lt/epp/xml/domreg-domain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:onExpire>delete</domain:onExpire> <domain:ns> <domain:hostGroup>group-1</domain:hostGroup> <domain:hostAttr> <domain:hostName>ns1.pavardenis.lt</domain:hostName> </domain:hostAttr> <domain:hostAttr> <domain:hostName>ns2.pavardenis.lt</domain:hostName> </domain:hostAttr> <domain:hostAttr> <domain:hostName>ns1.vardenis.lt</domain:hostName> <domain:hostAddr ip="v4">193.219.61.11</domain:hostAddr> <domain:hostAddr ip="v6">2001::10</domain:hostAddr> </domain:hostAttr> <domain:hostAttr> <domain:hostName>ns2.vardenis.lt</domain:hostName> <domain:hostAddr ip="v4">193.219.61.111</domain:hostAddr> </domain:hostAttr> </domain:ns> <domain:registrant>RN8</domain:registrant> <domain:contact>CN9</domain:contact> </domain:create> </create> </command> </epp>

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <domain:creData xmlns:domain="http://www.domreg.lt/epp/xml/domregdomain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:crDate>2012-11-21T15:36:14+02:00</domain:crDate> <domain:exDate>2013-11-22T23:59:59+02:00</domain:exDate> </domain:creData> </resData> <trID> <svTRID>DOMREG-02df1a8f045cc42f0a1a21d74ac60049e</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

26

DOMREG

KTU ITPI

DNSSEC EXTENSION: urn:ietf:params:xml:ns:secDNS-1.1 DNSSEC extension is used with support of DS records. TAG <extension> <secDNS:create> <secDNS:dsData> <secDNS:keyTag> <secDNS:alg> <secDNS:digestType> <secDNS:digest> Example: Client sends domain:create command with one DS record:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <create> <domain:create xmlns:domain="http://www.domreg.lt/epp/xml/domregdomain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:ns> <domain:hostAttr> <domain:hostName>ns1.domreg.lt</domain:hostName> </domain:hostAttr> </domain:ns> <domain:registrant>RN1</domain:registrant> <domain:contact>CN1</domain:contact> </domain:create> </create> <extension> <secDNS:create xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"> <secDNS:dsData> <secDNS:keyTag>4657</secDNS:keyTag> <secDNS:alg>8</secDNS:alg> <secDNS:digestType>1</secDNS:digestType> <secDNS:digest>9b34a992be18eadc35f2e9b57ff3d709dfe303cf</secDNS:dig est> </secDNS:dsData> </secDNS:create> </extension> </command> </epp>

Occurrences (min-max) 1 1 1-4 1 1 1 1

Size, remarks

Up to four DS records DNSSEC Keytag Key algorithm (3,5,6,7,8,10) Digest Type SHA1 or SHA-256 (1,2) Digest (in HEX)

.LT domain registration guidelines. EPP system.

27

DOMREG

KTU ITPI

Command UPDATE DOMAIN

PURPOSE: to change domain object any attribute information. TAG <epp> <command> <update> <name> <add> <ns> <hostGroup> <hostAttr> <hostName> <hostAddr> <contact> <rem> <ns> <hostGroup> <hostAttr> <hostName> <hostAddr> <contact> <chg> <onExpire> <clTRID> Remarks: <name> domain name to update. <add> In this attribute can be provided DNS server objects <ns> or contacts objects <contact> which should be added to domain information. <rem> In this attribute can be provided DNS server objects <ns> or contacts objects <contact> which should be deleted from domain information. <chg> required to indicate and change the value of <onExpire> attribute. ATTENTION! Number of specified DNS servers in <hostGroup> and <hostAttr> attributes added to domain after <update> command cant exceed 13. Number of specified contacts objects in <contact> attribute added to domain after <update> command cant exceed 7. Occurrences (min-max) 1 1 1 0-1 0-1 0-13 0-13 1 0-2 1-7 0-1 0-1 0-13 0-13 1 0-2 0-* 1 0-1 0-1 Size, remarks

1-255 1-100 1-255 3-45,possible attribute ip. Values v4 and v6 3-16 1-100 1-255 3-45,possible attributes ip. Values v4 and v6 3-16 delete or renew 3-64

Example: .LT domain registration guidelines. EPP system. 28

DOMREG

KTU ITPI

Client sends to server:

<?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"> <command> <update> <domain:update xmlns:domain="http://www.domreg.lt/epp/xml/domreg-domain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:add> <domain:ns> <domain:hostAttr> <domain:hostName>ns3.pavardenis.lt</domain:hostName> </domain:hostAttr> </domain:ns> </domain:add> <domain:rem> <domain:ns> <domain:hostGroup>group-1</domain:hostGroup> <domain:hostAttr> <domain:hostName>ns2.pavardenis.lt</domain:hostName> </domain:hostAttr> </domain:ns> </domain:rem> <domain:chg> <domain:onExpire>renew</domain:onExpire> </domain:chg> </domain:update> </update> </command> </epp>

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

29

DOMREG

KTU ITPI

DNSSEC EXTENSION: urn:ietf:params:xml:ns:secDNS-1.1 DNSSEC extension is used with support of DS records. secDNS:chg is not used, since registry does not use maxSigLife element. TAG <extension> <secDNS:update> <secDNS:add> <secDNS:dsData> <secDNS:keyTag> <secDNS:alg> <secDNS:digestType> <secDNS:digest> <secDNS:rem> <secDNS:all> <secDNS:dsData> <secDNS:keyTag> <secDNS:alg> <secDNS:digestType> <secDNS:digest> Example: Client sends command to the server to add additional DS record:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <update> <domain:update xmlns:domain="http://www.domreg.lt/epp/xml/domregdomain-1.0"> <domain:name>test-50add2e003017.lt</domain:name> <domain:add> <domain:ns/> </domain:add> </domain:update> </update> <extension> <secDNS:update xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"> <secDNS:add> <secDNS:dsData> <secDNS:keyTag>44745</secDNS:keyTag> <secDNS:alg>8</secDNS:alg> <secDNS:digestType>1</secDNS:digestType> <secDNS:digest>a18d5ba2ae3fc9c74e5807020dbe721cda09d657</secDNS:d igest> </secDNS:dsData> </secDNS:add> </secDNS:update> </extension> </command> </epp>

Occurrences (min-max) 1 1 0-1 1-4 1 1 1 1 0-1 0-1 0-4 1 1 1 1

Size, remarks

Add new DS records Up to four DS records DNSSEC Keytag Key algorithm (3,5,6,7,8,10) Digest Type SHA1 or SHA-256 (1,2) Digest (in HEX) Remove existing DS records Boolean, if 1 all Dses are removed Up to four DS records DNSSEC Keytag Key algorithm (3,5,6,7,8,10) Digest Type SHA1 or SHA-256 (1,2) Digest (in HEX)

.LT domain registration guidelines. EPP system.

30

DOMREG

KTU ITPI

Command DELETE DOMAIN

PURPOSE: to delete a domain name from the registration database. In EPP command domain name object name must be provided. TAG <epp> <command> <delete> <name> <clTRID> Remarks: <name> domain name to delete Example: Client sends the command to server to delete domain object with name vardenis.lt:
<?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"> <command> <delete> <domain:delete xmlns:domain="http://www.domreg.lt/epp/xml/domreg-domain-1.0"> <domain:name>vardenis.lt</domain:name> </domain:delete> </delete> </command> </epp>

Occurrences (min-max) 1 1 1 0-1

Size, remarks

1-255 3-64

The server responds with a result code of 1000 (Command completed successfully):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="lt">Command completed successfully</msg> </result> <trID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

31

DOMREG

KTU ITPI

Command TRANSFER DOMAIN

PURPOSE: to transfer a domain from one registrar to another and change domain name registrant. Using transfer command registrar can change domain name registrar to himself. Also he can change and domain name registrant. In both cases actions to change registrar/registrant must be initiated in advance by registrant. Registrant can initiate domain name transfer when connected to the .lt administrator provided system with his login name and password. TAG <epp> <command> <transfer> <name> <trType> <onExpire> <ns> <hostGroup> <hostAttr> <hostName> <hostAddr> <registrant> <contact> <clTRID> Remarks: <name> domain name to be transferred (with .lt in the end) <onExpire> if this attribute is not indicated, it is treated, that domain will be renewed in the end of the term. It is possible to indicate delete value in this attribute. In this case in the end of current term domain will be deleted. If indicated renew value, it will be renewed in the end of current term. <ns> Must be specified in order to provide domain delegation (authoritative DNS servers for this domain) information. <hostGroup> can be indicated up to 13 DNS servers group. <hostAttr> can be indicated up to 13 DNS servers <hostName> contains DNS server address name. <hostAddr> If necessary, DNS server IP address must be provided in version 4 or version 6 format. Can be provided 1 v4 and one v6 IP addresses. DNS server IP address must be provided if DNS server name is subdomain of domain to be registered. Ex.: <name> is example.lt and <hostName> is ns.example.com. <registrant> contains domain registrant contact person object ID. <contact> contains domain technical contact person object ID. ATTENTION! Number of specified DNS servers in <hostGroup> and <hostAttr> attributes cant be more that 13. .LT domain registration guidelines. EPP system. 32 Occurrences (min-max) 1 1 1 1 0-1 0-1 0-13 0-13 1 0-2 1 1-7 0-1 Size, remarks

Usable only attribute: op=request 1-255 transfer or trade delete or renew 1-100 1-255 3-45,possible attribute ip. Values v4 and v6 3-16 3-16 3-64

DOMREG

KTU ITPI

Example: Client sends to server:

<?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"> <command> <transfer op="request"> <domain:transfer xmlns:domain="http://www.domreg.lt/epp/xml/domreg-domain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:trType>trade</domain:trType> <domain:registrant>RN7</domain:registrant> <domain:contact>CN8</domain:contact> </domain:transfer> </transfer> <clTRID>TRADE-11213</clTRID> </command> </epp>

Server answers with code 1000 (Command completed successfully.), if client initiated registrant change and the new registrant name corresponds with the name, indicated by old registrant.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <clTRID>TRADE-11213</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

If registrant of domain didnt initiated such change, server answers with code 2308 (Registrant change is not possible):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="2308"> <msg lang="en">Registrant change is not possible</msg> </result> <trID> <clTRID>TRADE-11213</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

33

DOMREG

KTU ITPI

DNSSEC EXTENSION: urn:ietf:params:xml:ns:secDNS-1.1 DNSSEC extension is used with support of DS records. TAG <extension> <secDNS:create> <secDNS:dsData> <secDNS:keyTag> <secDNS:alg> <secDNS:digestType> <secDNS:digest> Occurrences (min-max) 1 1 1-4 1 1 1 1 Size, remarks

Up to four DS records DNSSEC Keytag Key algorithm (3,5,6,7,8,10) Digest Type SHA1 or SHA-256 (1,2) Digest (in HEX)

.LT domain registration guidelines. EPP system.

34

DOMREG

KTU ITPI

Command CHECK DOMAIN

PURPOSE: to check the availability of a domain name. TAG <epp> <command> <check> <name> <clTRID> Remarks: <name> domain names to be checked for availability Example: Client sends the command to server to check if it is possible to create domains vardenis.lt, pavardenis.lt and pavyzdenis.lt:
<?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"> <command> <check> <domain:check xmlns:domain="http://www.domreg.lt/epp/xml/domreg-domain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:name>pavardenis.lt</domain:name> <domain:name>pavyzdenis.lt</domain:name> </domain:check> </check> <clTRID>ABC-12345</clTRID> </command> </epp>

Occurrences (min-max) 1 1 1-* 0-1

Size, remarks

1-255 3-64

The server responds with a result code of 1000 (Command completed successfully). In response every <domain:name> attribute avail value shows 0 or 1. Value 0 means, that this domain name cant be registered. Value 1 means, that this domain name is not registered and can be requested for registration.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <domain:chkData xmlns:domain="http://www.domreg.lt/epp/xml/domregdomain-1.0"> <domain:cd>

.LT domain registration guidelines. EPP system.

35

DOMREG

KTU ITPI

<domain:name avail="0">vardenis.lt</domain:name> </domain:cd> <domain:cd> <domain:name avail="1">pavardenis.lt</domain:name> </domain:cd> <domain:cd> <domain:name avail="1">pavyzdenis.lt</domain:name> </domain:cd> </domain:chkData> </resData> <trID> <clTRID>ABC-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

36

DOMREG

KTU ITPI

Command INFO DOMAIN

PURPOSE: to retrieve the current information about a domain name TAG <epp> <command> <info> <name> <clTRID> Remarks: <name> contains the name of domain, which information you want to get. Example: Client sends the command to server to get the information about domain name vardenis.lt object:
<?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"> <command> <info> <domain:info xmlns:domain="http://www.domreg.lt/epp/xml/domreg-domain-1.0"> <domain:name>vardenis.lt</domain:name> </domain:info> </info> <clTRID>ABC-12345</clTRID> </command> </epp>

Occurrences (min-max) 1 1 1 0-1

Size, remarks

1-100 3-64

The server responds with a result code of 1000 (Command completed successfully) and gives the information about the domain object.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <domain:infData xmlns:domain="http://www.domreg.lt/epp/xml/domregdomain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:roid>DOMREG-5</domain:roid> <domain:onExpire>renew</domain:onExpire> <domain:status s="pendingDelete"/> <domain:registrant>RN8</domain:registrant> <domain:contact>CN9</domain:contact> <domain:ns>

.LT domain registration guidelines. EPP system.

37

DOMREG

KTU ITPI

<domain:hostAttr> <domain:hostName>ns1.pavardenis.lt</domain:hostName> </domain:hostAttr> <domain:hostAttr> <domain:hostName>ns1.vardenis.lt</domain:hostName> <domain:hostAddr ip="v4">193.219.61.11</domain:hostAddr> <domain:hostAddr ip="v6">2001::10</domain:hostAddr> </domain:hostAttr> <domain:hostAttr> <domain:hostName>ns2.vardenis.lt</domain:hostName> <domain:hostAddr ip="v4">193.219.61.111</domain:hostAddr> </domain:hostAttr> <domain:hostAttr> <domain:hostName>ns3.pavardenis.lt</domain:hostName> </domain:hostAttr> </domain:ns> <domain:crDate>2006-12-29T15:09:33+02:00</domain:crDate> <domain:upDate>2006-12-29T16:39:43+02:00</domain:upDate> <domain:exDate>2007-12-30T23:59:59+02:00</domain:exDate> </domain:infData> </resData> <trID> <clTRID>ABC-12345</clTRID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

DNSSEC EXTENSION: urn:ietf:params:xml:ns:secDNS-1.1 DNSSEC extension is used with support of DS records. domain:info response will return DS records in extention section if any are present. This can only be tha case if registrar has added DS records via domain:create or domain:update commands (or non-EPP interfaces). Example: Client has send info command to server to get information about domain with DS records, received response:
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <domain:infData xmlns:domain="http://www.domreg.lt/epp/xml/domregdomain-1.0"> <domain:name>vardenis.lt</domain:name> <domain:roid>DOMREG-91606</domain:roid> <domain:onExpire>renew</domain:onExpire> <domain:status s="pendingCreate"/> <domain:registrant>RN1</domain:registrant> <domain:contact>CN1</domain:contact> <domain:ns> <domain:hostAttr> <domain:hostName>ns1.domreg.lt</domain:hostName> </domain:hostAttr> </domain:ns> <domain:crDate>2012-11-22T09:27:23+02:00</domain:crDate>

.LT domain registration guidelines. EPP system.

38

DOMREG

KTU ITPI

<domain:upDate>2012-11-22T09:27:23+02:00</domain:upDate> <domain:exDate>2013-11-23T23:59:59+02:00</domain:exDate> </domain:infData> </resData> <extension> <secDNS:infData xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"> <secDNS:dsData> <secDNS:keyTag>4657</secDNS:keyTag> <secDNS:alg>8</secDNS:alg> <secDNS:digestType>1</secDNS:digestType> <secDNS:digest>9B34A992BE18EADC35F2E9B57FF3D709DFE303CF</secDNS:dig est> </secDNS:dsData> <secDNS:dsData> <secDNS:keyTag>44745</secDNS:keyTag> <secDNS:alg>8</secDNS:alg> <secDNS:digestType>1</secDNS:digestType> <secDNS:digest>A18D5BA2AE3FC9C74E5807020DBE721CDA09D657</secDNS:dig

est>

</secDNS:dsData> </secDNS:infData> </extension> <trID> <svTRID>DOMREG-08046b0a14b81b912aa7a9bc06a8952a7</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

39

DOMREG

KTU ITPI

Command INFO PERMIT

PURPOSE: to check if domain could be transferred, traded, restored from quarantine or reserved domain label registered using given parameters (registrant name, organization name, email). TAG <epp> <command> <info> <permit> <permit:domain> <permit:op> Occurrences (min-max) 1 1 1 1 1 Size, remarks

<permit:name> <permit:org> <permit:email> <clTRID> Remarks:

0-1 0-1 0-1 0-1

1-255 transfer trade restore regReserved 2-255 0-255 RFC2822 format 3-64

<domain> contains the name of domain for which operation should be checked <op> operation to check, either trade (registrant change), transfer (registrar change), restore from quarantine or registration of reserved domain. <name> registrant name (if future registrant is natural person) <org> registrant organization name (if future registrant is legal entity) <email> registrant email (only for trade operations checks) RESPONSE: on success contains resData with domain, status and optional exDate elements. status can be one of: valid operation is valid (its execution should be succeed) notInitialized transfer operation for domain is not possible because it is not initialized selfNotAllowed transfer from the same registrar is not allowed (blocked by registry) mismatchOrg specified <org> does not contain expected registrant organization name mismatchName specified <name> does not contain expected registrant name mismatchEmail specified <email> does not contain expected registrant email address generalReserve reserved domain cannot be registered because it is not reserved to the specific registrant Example: Client sends the command to server to check if domain vardenis.lt could be restored from quarantine, if registrar would send domain:create command with the registrant organization UAB Vardenis. .LT domain registration guidelines. EPP system. 40

DOMREG

KTU ITPI

<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <permit:info xmlns:permit="http://www.domreg.lt/epp/xml/domreg-permit-1.0"> <permit:domain>vardenis.lt</permit:domain> <permit:op>restore</permit:op> <permit:org>UAB &quot;Vardenis&quot;</permit:org> </permit:info> </info> </command> </epp>

The server responds with result code of 1000 (Command completed successfully) and gives status valid, domain could be restored to registrant UAB Vardenis, exDate contains date until domain is expected to be in the quarantine.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <permit:infData xmlns:permit="http://www.domreg.lt/epp/xml/domreg-permit1.0"> <permit:domain>vardenis.lt</permit:domain> <permit:status>valid</permit:status> <permit:exDate>2008-12-29T23:59:59+02:00</permit:exDate> </permit:infData> </resData> <trID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

Client sends the command to server to check if domain vardenis.lt could be traded to the registrant Vardenis Pavardenis with email address vardenis@pavardenis.lt
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <permit:info xmlns:permit="http://www.domreg.lt/epp/xml/domreg-permit-1.0"> <permit:domain>trade-domain.lt</permit:domain> <permit:op>trade</permit:op> <permit:name>Vardenis Pavardenis</permit:name> <permit:email>vardenis@pavardenis.lt</permit:email> </permit:info> </info> </command> </epp>

Server gives status mismatchEmail, trade operation would not be successful if registrant email would be vardenis@pavardenis.lt
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000">

.LT domain registration guidelines. EPP system.

41

DOMREG

KTU ITPI

<msg lang="en">Command completed successfully</msg> </result> <resData> <permit:infData xmlns:permit="http://www.domreg.lt/epp/xml/domreg-permit1.0"> <permit:domain>vardenis.lt</permit:domain> <permit:status>mismatchEmail</permit:status> </permit:infData> </resData> <trID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

Client sends the command to the server to check if transfer of domain vardenis.lt to registrant (legal entity) UAB Vardenis would succeed.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <permit:info xmlns:permit="http://www.domreg.lt/epp/xml/domreg-permit-1.0"> <permit:domain>vardenis.lt</permit:domain> <permit:op>transfer</permit:op> <permit:org>UAB &quot;Vardenis&quot;</permit:org> </permit:info> </info> </command> </epp>

Server gives status mismatchOrg, transfer operation would not be successful if registrant organization would be UAB Vardenis.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <permit:infData xmlns:permit="http://www.domreg.lt/epp/xml/domreg-permit1.0"> <permit:domain>vardenis.lt</permit:domain> <permit:status>mismatchOrg</permit:status> </permit:infData> </resData> <trID> <svTRID>DOMREG-0</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

42

DOMREG

KTU ITPI

Command POLL
PURPOSE: to store messages in a queue that can be emptied by the registrar upon his request. TAG <epp> <command> <poll> Occurrences (min-max) 1 1 Size, remarks Attributes: op = ack|req msgID, message ID if op=ack

Remarks: Event scheme: http://www.domreg.lt/epp/xml/domreg-event-1.0 obType object global domain domain domain domain domain domain credit notice balance low Description Registrar credit warning. Requested domain successfully registered Requested domain not registered. Domain auto-renewed Domain placed into quarantine Registrant initiated domain registrant change. Message is sent to current domain registrar. Registrant aborted domain registrant change. Domain registrant stays unchanged. Message is sent to current domain registrar. Registrant initiated domain registrar change. Message is sent to current domain registrar. Registrant aborted request to change domain registrar. Domain registrar stays unchanged. Message is sent to current domain registrar. Domain registrant successfully changed. Message is sent to domain registrar who administered domain before changes. Domain registrar successfully changed. Message is sent to domain registrar who administered domain before changes. 43

<domain> activated <domain> rejected <domain> renewed <domain> quarantined <domain> trade initiated <domain> trade aborted

domain domain

<domain> transfer initiated <domain> transfer aborted <domain> traded

domain

domain

<domain> transferred

.LT domain registration guidelines. EPP system.

DOMREG

KTU ITPI

Example: Client checks queue for messages:

<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> <poll op="req"/> <clTRID>ABC-12345</clTRID> </command> </epp>

The server responds with a result code of 1301 (Command completed successfully; acknowledge response to delete the message) and provides information, that 1272 messages are in queue and returns oldest message (domain domreg.lt activated):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1301"> <msg lang="en">Command completed successfully; acknowledge response to delete the message</msg> </result> <msgQ count="1272" id="10"> <qDate>2007-02-22T17:33:42+02:00</qDate> </msgQ> <resData> <event:eventData xmlns:event="http://www.domreg.lt/epp/xml/domregevent-1.0"> <event:obType>domain</event:obType> <event:object>domreg.lt</event:object> <event:notice>activated</event:notice> </event:eventData> </resData> <trID> <clTRID>ABC-12345</clTRID> <svTRID>DOMREG-11722198489147071428846114</svTRID> </trID> </response> </epp>

Client acknowledges reception of message:

<?xml version="1.0" encoding="UTF-8" standalone="no"?> <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> <poll op="ack" msgID="10" /> <clTRID>ABC-12345</clTRID> </command> </epp>

.LT domain registration guidelines. EPP system.

44

DOMREG

KTU ITPI

The server responds with a result code of 1000 (Command completed successfully) Server acknowledges message deletion from the queue and informs about number of left messages in the queue and ID of the oldest one.
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <msgQ count="1271" id="11"/> <trID> <clTRID>ABC-12345</clTRID> <svTRID>DOMREG-11722200366879341595280369</svTRID> </trID> </response> </epp>

Server response to queue check when queue is empty with code 1300 (Command completed successfully; registrar message queue is empty):
<?xml version="1.0" encoding="UTF-8"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1300"> <msg lang="en">Command completed successfully; registrar message queue is empty</msg> </result> <trID> <clTRID>SOMEID-12223</clTRID> <svTRID>DOMREG-117222022664246210687932</svTRID> </trID> </response> </epp>

.LT domain registration guidelines. EPP system.

45

DOMREG

KTU ITPI

Not used EPP commands

Command RENEW DOMAIN
PURPOSE: to renew domain for next term. The EPP protocol contains the possibility to renew the registrar of a domain name. As the renewal is automatic in .lt registration system, this command is not implemented. If you dont want to renew domain, use attribute <onExpire>delete</onExpire>.

Command CHECK CONTACT

PURPOSE: command checks if it is possible to create contact person object with indicated ID This command in KTU ITPI system is not implemented, because KTU ITPI EPP system creates unique ID for all new contact person objects.

Command TRANSFER CONTACT

PURPOSE: command to change registrar for contact person object If another registrar wants to use the same contact person object, he has to create a new contact person object, with the same information. Registrars can specify and administrate contact person object, which they created.

.LT domain registration guidelines. EPP system.

46