1. Introduction

KazNIC's registry system allows registrars to specify a value for the "Registration purpose" field as required by the law.


2. EPP <greeting> Server Response

Response frames for <greeting> server response returned to a client by the KazNIC EPP server contains definition of the server supported extension "kz-law-ext" in the <svcExtension> element.


<?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">
  <greeting>
    <svID>KZ Registry EPP server</svID>
    <svDate>2011-01-05T07:44:50.014Z</svDate>
    <svcMenu>
      <version>1.0</version>
      <lang>en</lang>
      <objURI>urn:ietf:params:xml:ns:domain-1.0</objURI>
      <objURI>urn:ietf:params:xml:ns:contact-1.0</objURI>
      <objURI>urn:ietf:params:xml:ns:host-1.0</objURI>
      <svcExtension>
        ...
	<extURI>urn:kaznic:params:xml:ns:kz-law-ext-1.0</extURI>
        <extURI>http://www.nic.kz/kz-law-ext-1.0</extURI>
      </svcExtension>
    </svcMenu>
  </greeting>
</epp>


3. EPP <info> Command

Response frames for <info> commands for domain names returned to a client by an EPP server that supports this extension MAY have an additional <kz-law-ext:infData> 
element in the <extension> element. The <kz-law-ext:infData> MAY contain a <kz-law-ext:registration-purpose> element containing domain name registration purpose description.

Example <info> response frame with a <kz-law-ext:infData> element:


S:  <?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:  <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S:    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S:    xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
S:    <response>
S:      <result code="1000">
S:        <msg>Command completed successfully.</msg>
S:      </result>
S:      <resData>
S:        <domain:infData
S:          xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S:          xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S:          domain-1.0.xsd">
S:          <domain:name>domain.kz</domain:name>
S:          <domain:roid>CNIC-DO302520</domain:roid>
S:          <domain:status r="ok"/>
S:          <domain:registrant>CONTACT-HANDLE</domain:registrant>
S:          <domain:contact type="tech">CONTACT-HANDLE</domain:contact>
S:          <domain:clID>C11480</domain:clID>
S:          <domain:ns>
S:            <domain:hostObj>ns1.domain.kz</domain:hostObj>
S:            <domain:hostObj>ns2.domain.kz</domain:hostObj>
S:          </domain:ns>
S:          <domain:crDate>1995-01-01T00:00:00.0Z</domain:crDate>
S:          <domain:exDate>2020-01-01T23:59:59.0Z</domain:exDate>
S:          <domain:upDate>2005-05-14T11:15:19.0Z</domain:upDate>
S:        </domain:infData>
S:      </resData>
S:      <extension>
S:	  <kz-law-ext:infData xmlns:kz-law-ext="urn:kaznic:params:xml:ns:kz-law-ext-1.0"
S:	    xsi:schemaLocation="urn:kaznic:params:xml:ns:kz-law-ext-1.0
S:	      kz-law-ext-1.0.xsd">
S:	       <kz-law-ext:registration-purpose>Purpose description</kz-law-ext:registration-purpose>
S:	  </kz-law-ext:infData>
S:      </extension>
S:      <trID>
S:        <clTRID>ABC-12345</clTRID>
S:        <svTRID>CNIC-F29KDFTOEJW4OSKGC00008SKOG8SOO0</svTRID>
S:      </trID>
S:    </response>
S:  </epp>

4. EPP <create> Command

Request frames for <create> commands for domain names sent to an EPP server that supports this extension MAY have 
an additional <kz-law-ext:create> element in the <extension> element. The <kz-law-ext:create> MAY contain a <kz-law-ext:registration-purpose> element 
containing domain name registration purpose description.

Example <create> request frame with a <kz-law-ext:create> element:


<?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>
     <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:name>domain.kz</domain:name>
         <domain:registrant>CONTACT-HANDLE</domain:registrant>
         <domain:contact type="admin">CONTACT-HANDLE</domain:contact>
         <domain:contact type="tech">CONTACT-HANDLE</domain:contact>
         <domain:authInfo>
           <domain:pw>2fooBAR</domain:pw>
         </domain:authInfo>
       </domain:create>
     </create>
     <clTRID>ABC-12345</clTRID>
     <extension>      
	<kz-law-ext:create xmlns:kz-law-ext="urn:kaznic:params:xml:ns:kz-law-ext-1.0"
          xsi:schemaLocation="urn:kaznic:params:xml:ns:kz-law-ext-1.0
          kz-law-ext-1.0.xsd">
	    <kz-law-ext:registration-purpose>Purpose description</kz-law-ext:registration-purpose>
	</kz-law-ext:create>
     </extension>
   </command>
</epp>

5. EPP <update> Command

Request frames for <update> commands for domain names sent to an EPP server that supports this extension MAY have an 
additional <kz-law-ext:update> element in the <extension> element. The <kz-law-ext:create> MAY contain a <kz-law-ext:registration-purpose> element 
containing domain name registration purpose description.

Example <update> request frame with a <kz-law-ext:update> element:
               
                          
<?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>
    <update>
      <domain:update
      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:name>domain.kz</domain:name>
      </domain:update>
    </update>
    <clTRID>ABC-12345</clTRID>
    <extension>
      <kz-law-ext:update xmlns:kz-law-ext="urn:kaznic:params:xml:ns:kz-law-ext-1.0"
       xsi:schemaLocation="urn:kaznic:params:xml:ns:kz-law-ext-1.0
       kz-law-ext-1.0.xsd">
	 <kz-law-ext:registration-purpose>Purpose description</kz-law-ext:registration-purpose>
      </kz-law-ext:update>  
    </extension>
  </command>
</epp>


6. Formal Specification

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns:kz-law-ext="urn:kaznic:params:xml:ns:kz-law-ext-1.0"
  xmlns="http://www.w3.org/2001/XMLSchema"
  targetNamespace="urn:kaznic:params:xml:ns:kz-law-ext-1.0" elementFormDefault="qualified">

  <annotation>
    <documentation>
      Extensible Provisioning Protocol v1.0 domain name
      extension schema for "kz-law-ext" extension.
    </documentation>
  </annotation>

  <!-- Child elements found in EPP commands. -->
  <element name="create" type="kz-law-ext:extData"/>
  <element name="update" type="kz-law-ext:extData"/>
  <element name="infData" type="kz-law-ext:extData"/>

  <complexType name="extData">
    <sequence>
      <element name="registration-purpose" type="kz-law-ext:stringType"/>
    </sequence>
  </complexType>

  <!-- Restricted simpleType -->
  <simpleType name="stringType">
     <restriction base="normalizedString">
       <minLength value="1"/>
       <maxLength value="255"/>
     </restriction>
  </simpleType>

</schema>