25 Extensible Provisioning Protocol (EPP)

Prototypical answer:

25. Extensible Provisioning Protocol (EPP)

China Internet Network Information Center (CNNIC) provides registrars with a business interface that complies with Request for Comments (RFC) 3735, RFC 5730, RFC 5731, RFC 5732, RFC 5733 and RFC 5734 and has extended simplified, traditional and variant Chinese domain names, and DNS Security Extensions (DNSSEC) in accordance with RFC 3735. CNNIC has also submitted relevant drafts. All human resources, funds and equipment necessary for implementing Extensible Provisioning Protocol (EPP) have been put in place by CNNIC.
　　
25.1 Business Interface between CNNIC and Registrars

Based on EPP, CNNIC provides registrars with a business interface for managing sessions, domain names, hosts, contacts and asynchronous messages. Via the above business interface, a registrar can perform not only complete business operation functions but also their own business workflow.
　　
All the EPP commands given by CNNIC for registrars are listed in the following table.
　　
Please see Table 1 and Table 2 in the attachment of Q25_Attachment_Table.
　　
All the above commands for the registration and management of domain names, hosts and contacts meet the requirements of parameters standardized by EPP. According to RFC 3735 and the business demand of ʺ.公司ʺ, CNNIC has extended the parameters of some of the above commands.
　　
25.2 Compliance with RFC

25.2.1 Compliance with RFC 5730

In accordance with the requirements of RFC 5730, CNNIC has realized session login, logout and hello commands, as well as poll command for asynchronous message reception and confirmation. Meanwhile, the formal syntax of EPP, result code, date format and international support satisfy RFC 5730.
　　
25.2.2 Compliance with RFC 5731

In accordance with the requirements of RFC 5731, CNNIC has supported commands including check, info, create, delete, renew, transfer and update for domain names.
　　
25.2.3 Compliance with RFC 5732

In accordance with the requirements of RFC 5732, CNNIC has supported commands including check, info, create, delete and update for hosts. The host of a particular domain name can be automatically transferred as the domain name is transferred. The IP of the host may be either IPv4 or IPv6.
　　
25.2.4 Compliance with RFC 5733

In accordance with the requirements of RFC 5733, CNNIC has implemented commands including check, info, create, delete, renew, transfer and update for contacts.
　　
25.2.5 Compliance with RFC 5734

In accordance with RFC 5734, CNNIC has implemented EPP mapping and deployed the Secure Sockets Layer (SSL) protocol, both of which are based on TCP. The EPP message format, the TCP connection session, the communication sequence of the client and the server, as well as the monitoring port meet the requirement of RFC 5734.
　　
25.3 Proprietary EPP Extension

Due to the uniqueness of its business, CNNIC has implemented some function extensions of the standard EPP based on RFC 3735. To be specific, these extensions include the extension of traditional, simplified and variant Chinese domain names, and DNSSEC extensions.
　　
25.3.1 Extension of Traditional, Simplified and Variant Chinese Domain Names

25.3.1.1 Overview

According to the characteristics of Chinese domain names, CNNIC has formulated relevant policies for variant registration (refer to the answer to Question 44). To facilitate the implementation of these policies, CNNIC, in accordance with RFC 3735, has extended EPP for traditional, simplified and variant Chinese domain names, making possible bundle registration of variant Chinese domain names.
　　
25.3.1.2 Explanation of Extensions

CNNIC has extended the response messages for the commands about the domain names mentioned in RFC 5731, including info, transfer, delete and renew and also extended the commands and response messages of update and create. Chinese characters in use have at least two forms, traditional and simplified Chinese characters. Therefore, when creating a domain name, CNNIC generates a full traditional and a full simplified domain name according to the one the registrar submits and store them in the database.
　　
When executing the info command, CNNIC feed the traditional, simplified and variant Chinese domain names and the corresponding A-Label record back to the client.
　　
After the command is extended, the fed back message is as follows:
　　
S:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
S:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
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: 〈domain:name〉xn--fsq270a.xn--55qx5d〈⁄domain:name〉
S: 〈domain:roid〉58812678-domain〈⁄domain:roid〉
S: 〈domain:status s=ʺokʺ⁄〉
S: 〈domain:registrant〉123〈⁄domain:registrant〉
S: 〈domain:contact type=ʺadminʺ〉123〈⁄domain:contact〉
S: 〈domain:contact type=ʺtechʺ〉123〈⁄domain:contact〉
S: 〈domain:ns〉
S: 〈domain:hostObj〉ns1.example.cn〈⁄domain:hostObj〉
S: 〈⁄domain:ns〉
S: 〈domain:clID〉ClientX〈⁄domain:clID〉
S: 〈domain:crID〉ClientY〈⁄domain:crID〉
S: 〈domain:crDate〉2011-04-03T22:00:00.0Z〈⁄domain:crDate〉
S: 〈domain:exDate〉2012-04-03T22:00:00.0Z〈⁄domain:exDate〉
S: 〈domain:authInfo〉
S: 〈domain:pw〉2fooBAR〈⁄domain:pw〉
S: 〈⁄domain:authInfo〉
S: 〈⁄domain:infData〉
S: 〈⁄resData〉
S: 〈extension〉
S: 〈idn:infData
S: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
S: 〈idn:bundle〉
S: 〈idn:oidn uLabel=ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq270a.xn--55qx5d〈⁄idn:oidn〉
S: 〈idn:pidn uLabel=ʺU+5BE6ʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsqz41a.xn--55qx5d〈⁄idn:pidn〉
S: 〈idn:vidn uLabel=ʺU+5B9FʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
S: 〈⁄idn:bundle〉
S: 〈⁄idn:infData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54322-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

Example 〈transfer〉 Response for an authorized client:

S:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
S:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
S: 〈response〉
S: 〈result code=ʺ1000ʺ〉
S: 〈msg〉Command completed successfully〈⁄msg〉
S: 〈⁄result〉
S: 〈resData〉
S: 〈domain:trnData
S: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
S: 〈domain:name〉xn--fsq270a.xn--55qx5d〈⁄domain:name〉
S: 〈domain:trStatus〉pending〈⁄domain:trStatus〉
S: 〈domain:reID〉ClientX〈⁄domain:reID〉
S: 〈domain:reDate〉2010-06-06T22:00:00.0Z〈⁄domain:reDate〉
S: 〈domain:acID〉ClientY〈⁄domain:acID〉
S: 〈domain:acDate〉2011-06-11T22:00:00.0Z〈⁄domain:acDate〉
S: 〈domain:exDate〉2012-09-08T22:00:00.0Z〈⁄domain:exDate〉
S: 〈⁄domain:trnData〉
S: 〈⁄resData〉
S: 〈extension〉
S: 〈idn:trnData
S: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
S: 〈idn:bundle〉
S: 〈idn:oidn uLabel=ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq270a.xn--55qx5d〈⁄idn:oidn〉
S: 〈idn:pidn uLabel=ʺU+5BE6ʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsqz41a.xn--55qx5d〈⁄idn:pidn〉
S: 〈idn:vidn uLabel=ʺU+5B9FʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
S: 〈⁄idn:bundle〉
S: 〈⁄idn:trnData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54322-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

Example 〈create〉 command:

C:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
C:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
C: 〈command〉
C: 〈create〉
C: 〈domain:create
C: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
C: 〈domain:name〉xn--fsq270a.xn--55qx5d〈⁄domain:name〉
C: 〈domain:period unit=ʺyʺ〉2〈⁄domain:period〉
C: 〈domain:registrant〉123〈⁄domain:registrant〉
C: 〈domain:contact type=ʺadminʺ〉123〈⁄domain:contact〉
C: 〈domain:contact type=ʺtechʺ〉123〈⁄domain:contact〉
C: 〈domain:authInfo〉
C: 〈domain:pw〉2fooBAR〈⁄domain:pw〉
C: 〈⁄domain:authInfo〉
C: 〈⁄domain:create〉
C: 〈⁄create〉
C: 〈extension:
C: 〈idn:create
C: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
C: 〈idn:vidn uLabel=ʺU+5B9FʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〉
C: xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
C: 〈⁄idn:create〉
C: 〈⁄extension〉
C: 〈clTRID〉ABC-12345〈⁄clTRID〉
C: 〈⁄command〉
C:〈⁄epp〉

Example 〈create〉 Response for an authorized client:

S:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
S:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
S: 〈response〉
S: 〈result code=ʺ1000ʺ〉
S: 〈msg〉Command completed successfully〈⁄msg〉
S: 〈⁄result〉
S: 〈resData〉
S: 〈domain:creData
S: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
S: 〈domain:name〉xn--fsq270a.xn--55qx5d〈⁄domain:name〉
S: 〈domain:crDate〉1999-04-03T22:00:00.0Z〈⁄domain:crDate〉
S: 〈domain:exDate〉2001-04-03T22:00:00.0Z〈⁄domain:exDate〉
S: 〈⁄domain:creData〉
S: 〈⁄resData〉
S: 〈extension〉
S: 〈idn:creData
S: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
S: 〈idn:bundle〉
S: 〈idn:oidn uLabel=ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq270a.xn--55qx5d〈⁄idn:oidn〉
S: 〈idn:pidn uLabel=ʺU+5BE6ʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsqz41a.xn--55qx5d〈⁄idn:pidn〉
S: 〈idn:vidn uLabel=ʺU+5B9FʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
S: 〈⁄idn:bundle〉
S: 〈⁄idn:creData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54322-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

Example 〈delete〉 response:

S:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
S:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
S: 〈response〉
S: 〈result code=ʺ1000ʺ〉
S: 〈msg〉Command completed successfully〈⁄msg〉
S: 〈⁄result〉
S: 〈extension〉
S: 〈idn:delData
S: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
S: 〈idn:bundle〉
S: 〈idn:oidn〉xn--fsq270a.xn--55qx5d〈⁄idn:oidn〉
S: 〈idn:pidn〉xn--fsqz41a.xn--55qx5d〈⁄idn:pidn〉
S: 〈idn:vidn〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
S: 〈⁄idn:bundle〉
S: 〈⁄idn:delData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54321-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

Example 〈renew〉 response:

S:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
S:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
S: 〈response〉
S: 〈result code=ʺ1000ʺ〉
S: 〈msg〉Command completed successfully〈⁄msg〉
S: 〈⁄result〉
S: 〈resData〉
S: 〈domain:renData
S: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
S: 〈domain:name〉xn--fsq270a.xn--55qx5d〈⁄domain:name〉
S: 〈domain:exDate〉2012-04-03T22:00:00.0Z〈⁄domain:exDate〉
S: 〈⁄domain:renData〉
S: 〈⁄resData〉
S: 〈extension〉
S: 〈idn:renData
S: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
S: 〈idn:bundle〉
S: 〈idn:oidn〉xn--fsq270a.xn--55qx5d〈⁄idn:oidn〉
S: 〈idn:pidn〉xn--fsqz41a.xn--55qx5d〈⁄idn:pidn〉
S: 〈idn:vidn〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
S: 〈⁄idn:bundle〉
S: 〈idn:renData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54322-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

Example 〈transfer〉 Response for an authorized client:

S:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
S:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
S: 〈response〉
S: 〈result code=ʺ1000ʺ〉
S: 〈msg〉Command completed successfully〈⁄msg〉
S: 〈⁄result〉
S: 〈resData〉
S: 〈domain:trnData
S: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
S: 〈domain:name〉xn--fsq270a.xn--55qx5d〈⁄domain:name〉
S: 〈domain:trStatus〉pending〈⁄domain:trStatus〉
S: 〈domain:reID〉ClientX〈⁄domain:reID〉
S: 〈domain:reDate〉2010-06-06T22:00:00.0Z〈⁄domain:reDate〉
S: 〈domain:acID〉ClientY〈⁄domain:acID〉
S: 〈domain:acDate〉2011-06-11T22:00:00.0Z〈⁄domain:acDate〉
S: 〈domain:exDate〉2012-09-08T22:00:00.0Z〈⁄domain:exDate〉
S: 〈⁄domain:trnData〉
S: 〈⁄resData〉
S: 〈extension〉
S: 〈idn:trnData
S: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
S: 〈idn:bundle〉
S: 〈idn:oidn uLabel=ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq270a.xn--55qx5d〈⁄idn:oidn〉
S: 〈idn:pidn uLabel=ʺU+5BE6ʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsqz41a.xn--55qx5d〈⁄idn:pidn〉
S: 〈idn:vidn uLabel=ʺU+5B9FʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ
S: activated=ʺtrueʺ〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
S: 〈⁄idn:bundle〉
S: 〈⁄IDN:trnData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54322-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

Registrants are permitted to add or remove a variant domain name when executing the update command. Example 〈update〉 Command:

C:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
C:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
C: 〈command〉
C: 〈update〉
C: 〈domain:update
C: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
C: 〈domain:name〉xn--fsq270a.xn--55qx5d〈⁄domain:name〉
C: 〈domain:add〉
C: 〈domain:ns〉
C: 〈domain:hostObj〉ns2.example.cn〈⁄domain:hostObj〉
C: 〈⁄domain:ns〉
C: 〈domain:contact type=ʺtechʺ〉234〈⁄domain:contact〉
C: 〈domain:status s=ʺclientHoldʺ
C: lang=ʺenʺ〉Payment overdue.〈⁄domain:status〉
C: 〈⁄domain:add〉
C: 〈domain:rem〉
C: 〈domain:ns〉
C: 〈domain:hostObj〉ns1.example.cn〈⁄domain:hostObj〉
C: 〈⁄domain:ns〉
C: 〈domain:contact type=ʺtechʺ〉123〈⁄domain:contact〉
C: 〈domain:status s=ʺclientUpdateProhibitedʺ⁄〉
C: 〈⁄domain:rem〉
C: 〈domain:chg〉
C: 〈domain:registrant〉234〈⁄domain:registrant〉
C: 〈domain:authInfo〉
C: 〈domain:pw〉2BARfoo〈⁄domain:pw〉
C: 〈⁄domain:authInfo〉
C: 〈⁄domain:chg〉
C: 〈⁄domain:update〉
C: 〈⁄update〉
C: 〈extension〉
C: 〈idn:update
C: xmlns:idn=ʺurn:ietf:params:xml:ns:idnv-1.0ʺ〉
C: 〈idn:add〉
C: 〈idn:vidn〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
C: 〈⁄idn:add〉
C: 〈idn:rem〉
C: 〈idn:vidn〉xn--fsqz41a.xn--55qx5d〈⁄idn:vidn〉
C: 〈⁄idn:rem〉
C: 〈idn:deactivate〉
C: 〈idn:vidn〉xn--fsq470a.xn--55qx5d〈⁄idn:vidn〉
C: 〈⁄idn:deactivate〉
C: 〈⁄idn:update〉
C: 〈⁄extension〉
C: 〈clTRID〉ABC-12345〈⁄clTRID〉
C: 〈⁄command〉
C:〈⁄epp〉

For details, please refer to the link: http:⁄⁄tools.ietf.org⁄html⁄draft-kong-epp-idn-variants-mapping-00.

25.3.2 DNSSEC Extension

25.3.2.1 Overview

According to the registration polices for Chinese domain names, the registrant will obtain a full traditional, and a full simplified Chinese domain names when applying for domain name registration. To allow the registrant to apply for Delegation Signer (DS) records for multiple variant Chinese domain names, CNNIC, in accordance with RFC 3735, has implement EPP extension for DNSSEC to support bulk registration of DS records.
　　
25.3.2.2 Explanation of Extensions

CNNIC has implemented the extension of EPP for DNSSEC by extending RFC 5910. DS records can be added to a designated domain name when it is created and updated, and relevant DS data are contained in the response message of info command.
　　
Create message：
　　
C:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
C:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
C: 〈command〉
C: 〈create〉
C: 〈domain:create
C: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
C: 〈domain:name〉
C: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:name〉
C: 〈domain:period unit=ʺyʺ〉2〈⁄domain:period〉
C: 〈domain:registrant〉123〈⁄domain:registrant〉
C: 〈domain:contact type=ʺadminʺ〉123〈⁄domain:contact〉
C: 〈domain:contact type=ʺtechʺ〉123〈⁄domain:contact〉
C: 〈domain:authInfo〉
C: 〈domain:pw〉2fooBAR〈⁄domain:pw〉
C: 〈⁄domain:authInfo〉
C: 〈⁄domain:create〉
C: 〈⁄create〉
C: 〈extension〉
C: 〈secCDNS:create
C: xmlns:secCDNS=ʺurn:ietf:params:xml:ns:secCDNS-1.0ʺ〉
C: 〈secCDNS:maxSigLife〉604800〈⁄secCDNS:maxSigLife〉
C: 〈secCDNS:DS〉
C: 〈secCDNS:CDN〉
C: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄secCDNS:CDN〉
C: 〈secCDNS:dsData〉
C: 〈secCDNS:keyTag〉12345〈⁄secCDNS:keyTag〉
C: 〈secCDNS:alg〉3〈⁄secCDNS:alg〉
C: 〈secCDNS:digestType〉1〈⁄secCDNS:digestType〉
C: 〈secCDNS:digest〉49FD46E6C4B45C55D4AC〈⁄secCDNS:digest〉
C: 〈⁄secCDNS:dsData〉
C: 〈⁄secCDNS:DS〉
C: 〈⁄secCDNS:create〉
C: 〈⁄extension〉
C: 〈trID〉
C: 〈clTRID〉ABC-12345〈⁄clTRID〉
C: 〈svTRID〉54322-XYZ〈⁄svTRID〉
C: 〈⁄trID〉
C: 〈⁄response〉
C:〈⁄epp〉

or：

C:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
C:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ〉
C: 〈command〉
C: 〈create〉
C: 〈domain:create
C: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
C: 〈domain:name〉
C: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:name〉
C: 〈domain:period unit=ʺyʺ〉2〈⁄domain:period〉
C: 〈domain:registrant〉123〈⁄domain:registrant〉
C: 〈domain:contact type=ʺadminʺ〉123〈⁄domain:contact〉
C: 〈domain:contact type=ʺtechʺ〉123〈⁄domain:contact〉
C: 〈domain:authInfo〉
C: 〈domain:pw〉2fooBAR〈⁄domain:pw〉
C: 〈⁄domain:authInfo〉
C: 〈⁄domain:create〉
C: 〈⁄create〉
C: 〈extension〉
C: 〈secCDNS:create
C: xmlns:secCDNS=ʺurn:ietf:params:xml:ns:secCDNS-1.0ʺ〉
C: 〈secCDNS:maxSigLife〉604800〈⁄secCDNS:maxSigLife〉
C: 〈secCDNS:KEY type=ʺallʺ〉
C: 〈secCDNS:keyData〉
C: 〈secCDNS:flags 〉257〈⁄secCDNS:flags〉
C: 〈secCDNS:protocol〉3〈⁄secCDNS:protocol〉
C: 〈secCDNS:alg〉1〈⁄secCDNS:alg〉
C: 〈secCDNS:pubKey〉AQPJ⁄⁄⁄⁄4Q==〈⁄secCDNS:pubKey〉
C: 〈⁄secCDNS:keyData〉
C: 〈⁄secCDNS:KEY〉
C: 〈⁄secCDNS:create〉
C: 〈⁄extension〉
C: 〈trID〉
C: 〈clTRID〉ABC-12345〈⁄clTRID〉
C: 〈svTRID〉54322-XYZ〈⁄svTRID〉
C: 〈⁄trID〉
C: 〈⁄response〉
C:〈⁄epp〉

Update message：
　　
C:〈?xml version=ʺ1.0ʺ encoding=ʺUTF-8ʺ standalone=ʺnoʺ?〉
C:〈epp xmlns=ʺurn:ietf:params:xml:ns:epp-1.0ʺ
C: xmlns:xsi=ʺhttp:⁄⁄www.w3.org⁄2001⁄XMLSchema-instanceʺ〉
C: 〈command〉
C: 〈update〉
C: 〈domain:update
C: xmlns:domain=ʺurn:ietf:params:xml:ns:domain-1.0ʺ〉
C: 〈domain:name〉 ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:name〉
C: 〈⁄domain:update〉
C: 〈⁄update〉
C: 〈extension〉
C: 〈secDNS:update
C: xmlns:secCDNS=ʺurn:ietf:params:xml:ns:secCDNS-1.0ʺ〉
C: 〈secDNS:rem〉
C: 〈secCDNS:DS〉
C: 〈secCDNS:CDN〉
C: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄secCDNS:CDN〉
C: 〈secCDNS:dsData〉
C: 〈secCDNS:keyTag〉12345〈⁄secCDNS:keyTag〉
C: 〈secCDNS:alg〉3〈⁄secCDNS:alg〉
C: 〈secCDNS:digestType〉1〈⁄secCDNS:digestType〉
C: 〈secCDNS:digest〉49FD46E6C4B45C55D4AC〈⁄secCDNS:digest〉
C: 〈⁄secCDNS:dsData〉
C: 〈⁄secCDNS:DS〉
C: 〈⁄secCDNS:rem〉
C: 〈secCDNS:add〉
C: 〈secCDNS:DS〉
C: 〈secCDNS:CDN〉
C: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄secCDNS:CDN〉
C: 〈secCDNS:dsData〉
C: 〈secCDNS:keyTag〉12345〈⁄secCDNS:keyTag〉
C: 〈secCDNS:alg〉3〈⁄secCDNS:alg〉
C: 〈secCDNS:digestType〉1〈⁄secCDNS:digestType〉
C: 〈secCDNS:digest〉49FD46E6C4B45C55D4AC〈⁄secCDNS:digest〉
C: 〈⁄secCDNS:dsData〉
C: 〈⁄secCDNS:DS〉
C: 〈⁄secCDNS:add〉
C: 〈⁄secCDNS:update〉
C: 〈⁄extension〉
C: 〈clTRID〉ABC-12345〈⁄clTRID〉
C: 〈⁄command〉
C:〈⁄epp〉

Example 〈info〉 Response for a Secure Delegation Using the DS Data Interface:

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: 〈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: 〈domain:name〉
S: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:name〉
S: 〈domain:roid〉123456-domain〈⁄domain:roid〉
S: 〈domain:status s=ʺokʺ⁄〉
S: 〈domain:registrant〉123CN〈⁄domain:registrant〉
S: 〈domain:contact type=ʺadminʺ〉helloChina〈⁄domain:contact〉
S: 〈domain:contact type=ʺtechʺ〉 helloChina〈⁄domain:contact〉
S: 〈domain:ns〉
S: 〈domain:hostObj〉ns1.china 〈⁄domain:hostObj〉
S: 〈domain:hostObj〉ns2.china 〈⁄domain:hostObj〉
S: 〈⁄domain:ns〉
S: 〈domain:host〉
S: ns1.ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:host〉
S: 〈domain:host〉
S: ns2.ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:host〉
S: 〈domain:clID〉ClientX〈⁄domain:clID〉
S: 〈domain:crID〉ClientY〈⁄domain:crID〉
S: 〈domain:crDate〉2010-04-03T22:00:00.0Z〈⁄domain:crDate〉
S: 〈domain:upID〉ClientX〈⁄domain:upID〉
S: 〈domain:upDate〉2010-12-03T09:00:00.0Z〈⁄domain:upDate〉
S: 〈domain:exDate〉2012-04-03T22:00:00.0Z〈⁄domain:exDate〉
S: 〈domain:trDate〉2011-02-08T09:00:00.0Z〈⁄domain:trDate〉
S: 〈domain:authInfo〉
S: 〈domain:pw〉abc123〈⁄domain:pw〉
S: 〈⁄domain:authInfo〉
S: 〈⁄domain:infData〉
S: 〈⁄resData〉
S: 〈extension〉
S: 〈secCDNS:infData
S: xmlns:secCDNS=ʺurn:ietf:params:xml:ns:secCDNS-1.0ʺ〉
S: 〈secCDNS:maxSigLife〉604800〈⁄secCDNS:maxSigLife〉
S: 〈secCDNS:DS〉
S: 〈secCDNS:CDN〉
S: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄secCDNS:CDN〉
S: 〈secCDNS:dsData〉
S: 〈secCDNS:keyTag〉12345〈⁄secCDNS:keyTag〉
S: 〈secCDNS:alg〉3〈⁄secCDNS:alg〉
S: 〈secCDNS:digestType〉1〈⁄secCDNS:digestType〉
S: 〈secCDNS:digest〉DVF46E6C4B45C55D4AC〈⁄secCDNS:digest〉
S: 〈⁄secCDNS:dsData〉
S: 〈⁄secCDNS:DS〉
S: 〈secCDNS:CDN〉
S: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄secCDNS:CDN〉
S: 〈secCDNS:dsData〉
S: 〈secCDNS:keyTag〉12345〈⁄secCDNS:keyTag〉
S: 〈secCDNS:alg〉3〈⁄secCDNS:alg〉
S: 〈secCDNS:digestType〉1〈⁄secCDNS:digestType〉
S: 〈secCDNS:digest〉59FD46E6C4B45C55D4AC〈⁄secCDNS:digest〉
S: 〈⁄secCDNS:dsData〉
S: 〈secCDNS:dsData〉
S: 〈secCDNS:keyTag〉12345〈⁄secCDNS:keyTag〉
S: 〈secCDNS:alg〉3〈⁄secCDNS:alg〉
S: 〈secCDNS:digestType〉1〈⁄secCDNS:digestType〉
S: 〈secCDNS:digest〉80FD46E6C4B45C55D4AC〈⁄secCDNS:digest〉
S: 〈⁄secCDNS:dsData〉
S: 〈⁄secCDNS:DS〉
S: 〈⁄secCDNS:infData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54322-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

Example 〈info〉 Response for a Secure Delegation Using the Key Data Interface:

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: 〈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: 〈domain:name〉
S: ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:name〉
S: 〈domain:roid〉123456-domain〈⁄domain:roid〉
S: 〈domain:status s=ʺokʺ⁄〉
S: 〈domain:registrant〉123CN〈⁄domain:registrant〉
S: 〈domain:contact type=ʺadminʺ〉helloChina〈⁄domain:contact〉
S: 〈domain:contact type=ʺtechʺ〉 helloChina〈⁄domain:contact〉
S: 〈domain:ns〉
S: 〈domain:hostObj〉ns1.china 〈⁄domain:hostObj〉
S: 〈domain:hostObj〉ns2.china 〈⁄domain:hostObj〉
S: 〈⁄domain:ns〉
S: 〈domain:host〉
S: ns1.ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:host〉
S: 〈domain:host〉
S: ns2.ʺU+5B9EʺʺU+4F8Bʺ.ʺU+516CʺʺU+53F8ʺ〈⁄domain:host〉
S: 〈domain:clID〉ClientX〈⁄domain:clID〉
S: 〈domain:crID〉ClientY〈⁄domain:crID〉
S: 〈domain:crDate〉2010-04-03T22:00:00.0Z〈⁄domain:crDate〉
S: 〈domain:upID〉ClientX〈⁄domain:upID〉
S: 〈domain:upDate〉2010-12-03T09:00:00.0Z〈⁄domain:upDate〉
S: 〈domain:exDate〉2012-04-03T22:00:00.0Z〈⁄domain:exDate〉
S: 〈domain:trDate〉2011-02-08T09:00:00.0Z〈⁄domain:trDate〉
S: 〈domain:authInfo〉
S: 〈domain:pw〉abc123〈⁄domain:pw〉
S: 〈⁄domain:authInfo〉
S: 〈⁄domain:infData〉
S: 〈⁄resData〉
S: 〈extension〉
S: 〈secCDNS:infData
S: xmlns:secCDNS=ʺurn:ietf:params:xml:ns:secCDNS-1.0ʺ〉
S: 〈secCDNS:KEY type=ʺallʺ〉
S: 〈secCDNS:keyData〉
S: 〈secCDNS:flags 〉257〈⁄secCDNS:flags〉
S: 〈secCDNS:protocol〉3〈⁄secCDNS:protocol〉
S: 〈secCDNS:alg〉1〈⁄secCDNS:alg〉
S: 〈secCDNS:pubKey〉AQPJ⁄⁄⁄⁄4Q==〈⁄secCDNS:pubKey〉
S: 〈⁄secCDNS:keyData〉
S: 〈⁄secCDNS:KEY〉
S: 〈⁄secCDNS:infData〉
S: 〈⁄extension〉
S: 〈trID〉
S: 〈clTRID〉ABC-12345〈⁄clTRID〉
S: 〈svTRID〉54322-XYZ〈⁄svTRID〉
S: 〈⁄trID〉
S: 〈⁄response〉
S:〈⁄epp〉

For details, please refer to the link: http:⁄⁄tools.ietf.org⁄html⁄draft-kong-epp-cdn-dnssec-mapping-00.

25.4 The EPP Schema of Business Interface between CNNIC and Registrars

The EPP Schema used by CNNIC includes two parts; one is the EPP XML Schema defined by RFC and the other is the EPP XML Schema of customized extension.
　　
25.4.1 The EPP XML Schema Defined by RFC

(1) urn:ietf:params:xml:ns:eppcom-1.0 (Refer to RFC 5730)

(2) urn:ietf:params:xml:ns:epp-1.0 (Refer to RFC 5730)

(3) urn:ietf:params:xml:ns:domain-1.0 (Refer to RFC 5731)

(4) urn:ietf:params:xml:ns:host-1.0 (Refer to RFC 5732)

(5) urn:ietf:params:xml:ns:contact-1.0 (Refer to RFC 5733)

(6) urn:ietf:params:xml:ns:rgp-1.0 (Refer to RFC 3915)

25.4.2 The EPP XML Schema of Customized Extension

(1) urn:ietf:params:xml:ns:idn-1.0 (Refer to draft-kong-epp-idn-variants-mapping-00)

(2) urn:ietf:params:xml:ns:secCDNS-1.0 (Refer to draft-kong-epp-cdn-dnssec-mapping-00)

25.5 Resource Allocation

25.5.1 Human Resources

EPP-related posts involve 2 software engineers who are responsible for EPP consistency analysis and for extending EPP in accordance with RFC 3735. Refer to the answer to Question 31.
　　
25.5.2 Funds

Funds and human resources have been put in place. Refer to the answer to Question 46 for the source and use of these funds.

Similar gTLD applications: (1)