]> CentralNic Group plc

35-39 Moorgate London England EC2R 6AR GB +44 20 33 88 0600 gavin.brown@centralnic.com https://www.centralnic.com

Applications Internet Engineering Task Force EPP, XML This document describes an Extensible Provisioning Protocol (EPP) extension mapping for registry fees.

Historically, domain name registries have applied a simple fee structure for billable transactions, namely a basic unit price applied to domain <create>, <renew>, <transfer> and RGP restore commands. Given the relatively small number of EPP servers to which EPP clients have been required to connect, it has generally been the case that client operators have been able to obtain details of these fees out-of-band by contacting the server operators. Given the imminent expansion of the DNS namespace, and the proliferation of novel business models, it is now desirable to provide a method for EPP clients to query EPP servers for the fees and credits associated with certain commands and specific objects. This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This EPP mapping provides a mechanism by which EPP clients may query the fees and credits associated with various billable transactions.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. "fee" is used as an abbreviation for "urn:ietf:params:xml:ns:fee-&VERSION;". The XML namespace prefix "fee" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. The XML namespace prefix above contains a version number, specifically "&VERSION;". This version number will increment with successive versions of this document, and will reach 1.0 if and when this document is published as an RFC. This permits clients to distinguish which version of the extension a server has implemented.

The <fee:action> element is used in EPP query commands to determine the command to which a fee is applicable. The element values permitted by the server is a matter of repository policy, but MUST include as a minimum the following values: "create" indicating a <domain:create> command; "renew" indicating a <domain:renew> command; "transfer" indicating a <domain:transfer> command; If the server supports the Registry Grace Period Mapping, then the server MUST also support the "restore" value. The <fee:action> element MAY have an OPTIONAL "phase" attribute specifying a launch phase as described in . It may also contain an OPTIONAL "subphase" attribute identifying the custom or sub-phase as described in .

The <fee:currency> element is used to indicate which currency fees are charged in. This value of this element MUST be a three-character currency code from . Note that ISO 4217 provides the special "XXX" code, which may be used if the server uses a non-currency based system for assessing fees, such as a system of credits.

A detailed description of the EPP syntax and semantics can be found in .

This extension does not add any elements to the EPP <poll> command or response.

This extension defines additional elements for the EPP <check> command. The command frame MAY contain an <extension> element which MAY contain one or more child <fee:check> elements with the following child elements: A <domain:name> element that contains a domain name. A <fee:currency> element that contains the currency the fee is charged in. A <fee:action> element identifying the command. A <fee:period> element that contains the number of units to be added to the registration period of the domain object. Example <check> 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: <check> C: <domain:check C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: <domain:name>example.net</domain:name> C: <domain:name>example.org</domain:name> C: </domain:check> C: </check> C: <extension> C: <fee:check C: xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:domain>example.com</fee:domain> C: <fee:currency>USD</fee:currency> C: <fee:action phase="sunrise">create</fee:action> C: <fee:period unit="y">1</fee:period> C: </fee:check> C: <fee:check C: xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:domain>example.net</fee:domain> C: <fee:currency>EUR</fee:currency> C: <fee:action phase="claims" subphase="landrush"> C: create</fee:action> C: <fee:period unit="y">2</fee:period> C: </fee:check> C: <fee:check C: xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:domain>example.org</fee:domain> C: <fee:currency>EUR</fee:currency> C: <fee:action>transfer</fee:action> C: <fee:period unit="y">2</fee:period> C: </fee:check> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C: </epp>

When the server receives a <check> command that includes the extension elements described above, its response MUST contain an <extension> element, which MUST contain a child <fee:chkData> element for each <fee:check> element contained in the command. The <fee:chkData> MUST contain the following child elements: A <domain:name> element that contains a domain name which matches the name in the corresponding <fee:check> element. A <fee:currency> element that contains same currency code that appeared in the corresponding <fee:check> element. A <fee:action> element that contains same action that appeared in the corresponding <fee:check> element. This element MAY have the OPTIONAL "phase" and "subphase" elements, which MUST match the same attributes in the corresponding <fee:check> element. A <fee:period> element that contains same unit that appeared in the corresponding <fee:check> element. A <fee:fee> element that contains the fee associated with the specified transaction. Example <check> 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:chkData S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <domain:cd> S: <domain:name avail="1">example.com</domain:name> S: </domain:cd> S: <domain:cd> S: <domain:name avail="0">example.net</domain:name> S: <domain:reason>In use</domain:reason> S: </domain:cd> S: <domain:cd> S: <domain:name avail="0">example.org</domain:name> S: <domain:reason>In use</domain:reason> S: </domain:cd> S: </domain:chkData> S: </resData> S: <extension> S: <fee:chkData S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:domain>example.com</fee:domain> S: <fee:currency>USD</fee:currency> S: <fee:action phase="sunrise">create</fee:action> S: <fee:period unit="y">1</fee:period> S: <fee:fee>10.00</fee:fee> S: </fee:chkData> S: <fee:chkData S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:domain>example.net</fee:domain> S: <fee:currency>EUR</fee:currency> S: <fee:action phase="claims" subphase="landrush"> S: create</fee:action> S: <fee:period unit="y">2</fee:period> S: <fee:fee>5.00</fee:fee> S: </fee:chkData> S: <fee:chkData S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:domain>example.org</fee:domain> S: <fee:currency>EUR</fee:currency> S: <fee:action>transfer</fee:action> S: <fee:period unit="y">2</fee:period> S: <fee:fee>2.50</fee:fee> S: </fee:chkData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S: </epp>

This extension defines additional elements for the EPP <info> command. The command frame MAY contain an <extension> element which contains a <fee:info> element with the following child elements: A <fee:currency> element that contains the currency the fee is charged in. A <fee:action> element identifying the command. A <fee:period> element that contains the number of units to be added to the registration period of the domain object. Example <info> 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: <info> C: <domain:info C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name hosts="all">example.com</domain:name> C: </domain:info> C: </info> C: <extension> C: <fee:info xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:currency>USD</fee:currency> C: <fee:action phase="sunrise">create</fee:action> C: <fee:period unit="y">1</fee:period> C: </fee:info> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C: </epp>

When the server receives an <info> command that includes the extension element described above, its response MUST (subject to the exceptions described below) contain an <extension> element, which MUST contain a child <fee:infData> element. The <fee:infData> MUST contain the following child elements: A <fee:currency> element that contains same currency code that appeared in the original <fee:check> element. A <fee:action> element that contains same action that appeared in the original <fee:check> element. This element MAY have the OPTIONAL "phase" and "subphase" elements, which MUST match the same attributes in the original <fee:check> element. A <fee:period> element that contains same unit that appeared in the original <fee:check> element. A <fee:fee> element that contains the fee associated with the specified transaction. If the domain name requested in the command is invalid, sponsored by another client, or otherwise ineligible for registration, the server MAY choose to omit the <fee:infData> element and return an error instead. Example <info> 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:infData S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <domain:name>example.com</domain:name> S: <domain:roid>EXAMPLE1-REP</domain:roid> S: <domain:status s="ok" /> S: <domain:registrant>jd1234</domain:registrant> S: <domain:contact type="admin">sh8013</domain:contact> S: <domain:contact type="tech">sh8013</domain:contact> S: <domain:ns> S: <domain:hostObj>ns1.example.com</domain:hostObj> S: <domain:hostObj>ns1.example.net</domain:hostObj> S: </domain:ns> S: <domain:host>ns1.example.com</domain:host> S: <domain:host>ns2.example.com</domain:host> S: <domain:clID>ClientX</domain:clID> S: <domain:crID>ClientY</domain:crID> S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate> S: <domain:upID>ClientX</domain:upID> S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate> S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate> S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate> S: <domain:authInfo> S: <domain:pw>2fooBAR</domain:pw> S: </domain:authInfo> S: </domain:infData> S: </resData> S: <extension> S: <fee:infData xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:action phase="sunrise">create</fee:action> S: <fee:period unit="y">1</fee:period> S: <fee:fee>10.00</fee:fee> S: </fee:infData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S: </epp>

Example <info> response where the domain name is not registered:

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="2303"> S: <msg>Object does not exist.</msg> S: </result> S: <extension> S: <fee:infData S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:action phase="sunrise">create</fee:action> S: <fee:period unit="y">1</fee:period> S: <fee:fee>10.00</fee:fee> S: </fee:infData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S: </epp>

This extension does not add any elements to the EPP <transfer> query command, but does include elements in the response, when the extension has been selected during a <login> command. When the <transfer> query command has been processed successfully, the client selected the extension when it logged in, and the client is authorised by the server to view information about the transfer, the server MAY include in the <extension> section of the EPP response a <fee:trnData> element that contains a <fee:fee> element containing the fee associated with this command. If no <fee:trnData> element is included in the response, then no fee has been assessed by the server for this transaction. Example <transfer> query 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="1001"> S: <msg>Command completed successfully; action pending</msg> S: </result> S: <resData> S: <domain:trnData S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <domain:name>example.com</domain:name> S: <domain:trStatus>pending</domain:trStatus> S: <domain:reID>ClientX</domain:reID> S: <domain:reDate>2000-06-08T22:00:00.0Z</domain:reDate> S: <domain:acID>ClientY</domain:acID> S: <domain:acDate>2000-06-13T22:00:00.0Z</domain:acDate> S: <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate> S: </domain:trnData> S: </resData> S: <extension> S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:fee>5.00</fee:fee> S: </fee:trnData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S: </epp>

This extension adds elements to both the EPP <create> command and response, when the extension has been selected during a <login> command. When submitting a <create> command to the server, the client MAY include in the <extension> element a <fee:create> element which includes the following child elements: A <fee:currency> element containing the currency of the fee that the command will result in. A <fee:fee> element that contains the fee associated with the command. Depending on server policy, the server MAY choose to accept or refuse the command depending on whether the currency and fee provided by the client agrees with the server's own calculation of the fee. If the server chooses to refuse the command due to an incorrect fee, it MUST respond with a 2004 "Parameter value range error". When the <create> command has been processed successfully, and the client selected the extension when it logged in, the server MAY include in the <extension> section of the EPP response a <fee:creData> element that contains the following child elements: A <fee:currency> element containing the currency of the fee. A <fee:fee> element that contains the fee. If no <fee:creData> element is included in the response, then no fee has been assessed by the server for this transaction. 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>example.com</domain:name> C: <domain:period unit="y">2</domain:period> C: <domain:ns> C: <domain:hostObj>ns1.example.net</domain:hostObj> C: <domain:hostObj>ns2.example.net</domain:hostObj> C: </domain:ns> C: <domain:registrant>jd1234</domain:registrant> C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:authInfo> C: <domain:pw>2fooBAR</domain:pw> C: </domain:authInfo> C: </domain:create> C: </create> C: <extension> C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:currency>USD</fee:currency> C: <fee:fee>5.00</fee:fee> C: </fee:create> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C: </epp>

Example <create> 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:creData S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <domain:name>example.com</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: <fee:creData xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:fee>5.00</fee:fee> S: </fee:creData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S: </epp>

This extension does not add any elements to the EPP <delete> command, but does include elements in the response, when the extension has been selected during the <login> command. When the <delete> command has been processed successfully, and the client selected the extension when it logged in, the server MAY include in the <extension> section of the EPP response a <fee:delData> element that contains the following child elements: A <fee:currency> element containing the currency of the credit. A <fee:credit> element that contains the credit associated with the deletion of the domain. If no <fee:delData> element is included in the response, then no credit has been assessed by the server for this transaction. 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: <fee:delData xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:credit>5.00</fee:credit> S: </fee:delData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S: </epp>

This extension adds elements to both the EPP <renew> command and response, when the extension has been selected during a <login> command. When submitting a <renew> command to the server, the client MAY include in the <extension> element a <fee:renew> element which includes the following child elements: A <fee:currency> element containing the currency of the fee that the command will result in. A <fee:fee> element that contains the fee associated with the command. Depending on server policy, the server MAY choose to accept or refuse the command depending on whether the currency and fee provided by the client agrees with the server's own calculation of the fee. If the server chooses to refuse the command due to an incorrect fee, it MUST respond with a 2004 "Parameter value range error". When the <renew> command has been processed successfully, and the client selected the extension when it logged in, the server MAY include in the <extension> section of the EPP response a <fee:renData> element that contains the following child elements: A <fee:currency> element containing the currency of the fee. A <fee:fee> element that contains the fee. If no <fee:renData> element is included in the response, then no fee has been assessed by the server for this transaction. Example <renew> 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: <renew> C: <domain:renew C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: <domain:curExpDate>2000-04-03</domain:curExpDate> C: <domain:period unit="y">5</domain:period> C: </domain:renew> C: </renew> C: <extension> C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:currency>USD</fee:currency> C: <fee:fee>5.00</fee:fee> C: </fee:create> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C: </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>example.com</domain:name> S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate> S: </domain:renData> S: </resData> S: <extension> S: <fee:renData xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:fee>5.00</fee:fee> S: </fee:renData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S: </epp>

This extension adds elements to both the EPP <transfer> command and response, when the value of the "op" attribute of the <transfer> command element is "request", and the extension has been selected during the <login> command. When submitting a <transfer> command to the server, the client MAY include in the <extension> element a <fee:transfer> element which includes the following child elements: A <fee:currency> element containing the currency of the fee that the command will result in. A <fee:fee> element that contains the fee associated with the command. Depending on server policy, the server MAY choose to accept or refuse the command depending on whether the currency and fee provided by the client agrees with the server's own calculation of the fee. If the server chooses to refuse the command due to an incorrect fee, it MUST respond with a 2004 "Parameter value range error". When the <transfer> command has been processed successfully, and the client selected the extension when it logged in, the server MAY include in the <extension> section of the EPP response a <fee:trnData> element that contains the following child elements: A <fee:currency> element containing the currency of the fee. A <fee:fee> element that contains the fee. If no <fee:transfData> element is included in the response, then no fee has been assessed by the server for this transaction. Example <transfer> 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: <transfer op="request"> C: <domain:transfer C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: <domain:period unit="y">1</domain:period> C: <domain:authInfo> C: <domain:pw roid="JD1234-REP">2fooBAR</domain:pw> C: </domain:authInfo> C: </domain:transfer> C: </transfer> C: <extension> C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:currency>USD</fee:currency> C: <fee:fee>5.00</fee:fee> C: </fee:create> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C: </epp>

Example <transfer> 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="1001"> S: <msg>Command completed successfully; action pending</msg> S: </result> S: <resData> S: <domain:trnData S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <domain:name>example.com</domain:name> S: <domain:trStatus>pending</domain:trStatus> S: <domain:reID>ClientX</domain:reID> S: <domain:reDate>2000-06-08T22:00:00.0Z</domain:reDate> S: <domain:acID>ClientY</domain:acID> S: <domain:acDate>2000-06-13T22:00:00.0Z</domain:acDate> S: <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate> S: </domain:trnData> S: </resData> S: <extension> S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:fee>5.00</fee:fee> S: </fee:trnData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S: </epp>

This extension adds elements to both the EPP <update> command and response, when the extension has been selected during a <login> has been selected during the <login> command. When submitting a <update> command to the server, the client MAY include in the <extension> element a <fee:update> element which includes the following child elements: A <fee:currency> element containing the currency of the fee that the command will result in. A <fee:fee> element that contains the fee associated with the command. Depending on server policy, the server MAY choose to accept or refuse the command depending on whether the currency and fee provided by the client agrees with the server's own calculation of the fee. If the server chooses to refuse the command due to an incorrect fee, it MUST respond with a 2004 "Parameter value range error". When the <update> command has been processed successfully, and the client selected the extension when it logged in, the server MAY include in the <extension> section of the EPP response a <fee:upData> element that contains the following child elements: A <fee:currency> element containing the currency of the fee. A <fee:fee> element that contains the fee. If no <fee:upData> element is included in the response, then no fee has been assessed by the server for this transaction. 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>example.com</domain:name> C: <domain:chg> C: <domain:registrant>sh8013</domain:registrant> C: </domain:chg> C: </domain:update> C: </update> C: <extension> C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> C: <fee:currency>USD</fee:currency> C: <fee:fee>5.00</fee:fee> C: </fee:create> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C: </epp>

Example <update> 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: <fee:updData xmlns:fee="urn:ietf:params:xml:ns:fee-0.4"> S: <fee:currency>USD</fee:currency> S: <fee:fee>5.00</fee:fee> S: </fee:updData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S: </epp>

An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BEGIN <?xml version="1.0" encoding="utf-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:fee="urn:ietf:params:xml:ns:fee-0.4" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" targetNamespace="urn:ietf:params:xml:ns:fee-0.4" elementFormDefault="qualified"> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:domain-1.0" /> <annotation> <documentation>Extensible Provisioning Protocol v1.0 domain name extension schema for fee information.</documentation> </annotation> <!-- Child elements found in EPP commands and responses --> <element name="check" type="fee:checkType" /> <element name="chkData" type="fee:chkDataType" /> <element name="info" type="fee:infoType" /> <element name="infData" type="fee:infDataType" /> <element name="create" type="fee:transformCommandType" /> <element name="creData" type="fee:transformResultType" /> <element name="renew" type="fee:transformCommandType" /> <element name="renData" type="fee:transformResultType" /> <element name="transfer" type="fee:transformCommandType" /> <element name="trnData" type="fee:transformResultType" /> <element name="update" type="fee:transformCommandType" /> <element name="updData" type="fee:transformResultType" /> <element name="delData" type="fee:deleteDataType" /> <!-- client <check> command --> <complexType name="checkType"> <sequence> <element name="domain" type="eppcom:labelType" /> <element name="currency" type="fee:currencyType" /> <element name="action" type="fee:actionType" /> <element name="period" type="domain:periodType" /> </sequence> </complexType> <!-- server <check> result --> <complexType name="chkDataType"> <sequence> <element name="domain" type="eppcom:labelType" /> <element name="currency" type="fee:currencyType" /> <element name="action" type="fee:actionType" /> <element name="period" type="domain:periodType" /> <element name="fee" type="fee:feeType" /> </sequence> </complexType> <!-- client <info> command --> <complexType name="infoType"> <sequence> <element name="currency" type="fee:currencyType" /> <element name="action" type="fee:actionType" /> <element name="period" type="domain:periodType" /> </sequence> </complexType> <!-- server <info> result --> <complexType name="infDataType"> <sequence> <element name="currency" type="fee:currencyType" /> <element name="action" type="fee:actionType" /> <element name="period" type="domain:periodType" /> <element name="fee" type="fee:feeType" /> </sequence> </complexType> <!-- general transform (create, renew, update, transfer) command --> <complexType name="transformCommandType"> <sequence> <element name="currency" type="fee:currencyType" /> <element name="fee" type="fee:feeType" /> </sequence> </complexType> <!-- general transform (create, renew, update, transfer) result --> <complexType name="transformResultType"> <sequence> <element name="currency" type="fee:currencyType" /> <element name="fee" type="fee:feeType" /> </sequence> </complexType> <!-- delete result --> <complexType name="deleteDataType"> <sequence> <element name="currency" type="fee:currencyType" /> <element name="credit" type="fee:feeType" /> </sequence> </complexType> <!-- common types --> <simpleType name="currencyType"> <restriction base="string"> <pattern value="[A-Z]{3}" /> </restriction> </simpleType> <complexType name="actionType"> <simpleContent> <extension base="fee:actionTypeValue"> <attribute name="phase" type="token" /> <attribute name="subphase" type="token" /> </extension> </simpleContent> </complexType> <simpleType name="actionTypeValue"> <restriction base="token"> <minLength value="3"/> <maxLength value="16"/> </restriction> </simpleType> <simpleType name="feeType"> <restriction base="decimal" /> </simpleType> </schema> END

The mapping extensions described in this document do not provide any security services beyond those described by EPP, the EPP domain name mapping, and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well.

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . Two URI assignments were requested and have been registered by the IANA. Registration request for the digital signature namespace: URI: urn:ietf:params:xml:ns:fee-&VERSION; Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the EPP fee XML schema: URI: urn:ietf:params:xml:ns:fee-&VERSION; Registrant Contact: See the "Author's Address" section of this document. XML: See the "Formal Syntax" section of this document.

The author wishes to thank the following persons for their feedback and suggestions: James Gould of Verisign Luis Muñoz of ISC Michael Young of Architelos Ben Levac and Jeff Eckhaus of Demand Media

Added note about the use of the "XXX" code for non-currency transactions. Added phase attribute to the <fee:action> element, and normative reference to . Added description of extension to transform and transfer query commands. Added Acknowledgements and Change History sections.

Added the subphase attribute to the <fee:action> element. Removed the enumeration for the <fee:action> element so any token may be used. Moved the fee lookup command from <check> to <info>. Added an extension to the <delete> command to return credit information. Changed MUSTs to MAYs so that the response extension elements can be omitted where no fee is applicable. Update of introductory text.

Restore the <check> command extension; either <check> or <info> can be used. added extension elements for <create>, <renew>, <transfer> and <update> so that the server can reject the command if the fee is incorrect.

&RFC2119; &RFC3688; &RFC3915; &RFC5730; &RFC5731; International Organization for Standardization