Diff: rfc8748xml2.original.xml

	rfc8748xml2.original.xml	rfc8748.xml

	<?xml version="1.0" encoding="US-ASCII"?>	<?xml version="1.0" encoding="UTF-8"?>
	<!-- This template is for creating an Internet Draft using xml2rfc,
	which is available here: http://xml.resource.org. -->
	<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
	<!-- One method to get references from the online citation libraries.
	There has to be one entity for each item to be referenced.
	An alternate method (rfc include) is described in the references. -->
	<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.2119.xml">
	<!ENTITY RFC3688 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.3688.xml">
	<!ENTITY RFC3915 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.3915.xml">
	<!ENTITY RFC5730 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5730.xml">
	<!ENTITY RFC5731 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5731.xml">
	<!ENTITY RFC7451 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.7451.xml">
	<!ENTITY RFC7942 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.7942.xml">
	<!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.8174.xml">
	<!ENTITY RFC8334 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.8334.xml">
	<!ENTITY W3C.REC-xmlschema-1-20041028 PUBLIC '' 'http://xml2rfc.ietf.org/public/
	rfc/bibxml4/reference.W3C.REC-xmlschema-1-20041028.xml'>
	<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM "http://xml.resource.o
	rg/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
	]>
	<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
	<!-- used by XSLT processors -->
	<!-- For a complete list and description of processing instructions (PIs),
	please see http://xml.resource.org/authoring/README.html. -->
	<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds
	might want to use.
	(Here they are set differently than their defaults in xml2rfc v1.32) -->
	<?rfc strict="yes" ?>
	<!-- give errors regarding ID-nits and DTD validation -->
	<!-- control the table of contents (ToC) -->
	<?rfc toc="yes"?>
	<!-- generate a ToC -->
	<?rfc tocdepth="4"?>
	<!-- the number of levels of subsections in ToC. default: 3 -->
	<!-- control references -->
	<?rfc symrefs="yes"?>
	<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
	<?rfc sortrefs="yes" ?>
	<!-- sort the reference entries alphabetically -->
	<!-- control vertical white space
	(using these PIs as follows is recommended by the RFC Editor) -->
	<?rfc compact="yes" ?>
	<!-- do not start each main section on a new page -->
	<?rfc subcompact="yes" ?>
	<!-- keep one blank line between list items -->
	<?rfc comments="yes" ?>
	<!-- show cref output -->
	<?rfc inline="yes" ?>
	<!-- inline cref output -->
	<!-- end of list of popular I-D processing instructions -->
	<rfc category="std" docName="draft-ietf-regext-epp-fees-20" ipr="trust200902">
	<!-- category values: std, bcp, info, exp, and historic
	ipr values: full3667, noModification3667, noDerivatives3667
	you can add the attributes updates="NNNN" and obsoletes="NNNN"
	they will automatically be output with "(if approved)" -->


	<!-- *** FRONT MATTER *** -->	<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">


	<front>	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" consensus="true"
	<!-- The abbreviated title is used in the page header - it is only necessary	docName="draft-ietf-regext-epp-fees-20" number="8748" ipr="trust200902" obsolete
	if the	s="" updates="" submissionType="IETF" xml:lang="en" tocInclude="true" tocDepth="
	full title is longer than 39 characters -->	4" symRefs="true" sortRefs="true" version="3">

		<!-- xml2rfc v2v3 conversion 2.35.0 -->


		<front>
	<title abbrev="Registry Fee Extension">	<title abbrev="Registry Fee Extension">
	Registry Fee Extension for the Extensible Provisioning Protocol (EPP)</title >	Registry Fee Extension for the Extensible Provisioning Protocol (EPP)</title >

		<seriesInfo name="RFC" value="8748"/>
	<author fullname="Roger Carney" initials="R.C." surname="Carney">	<author fullname="Roger Carney" initials="R." surname="Carney">
	<organization>GoDaddy Inc.</organization>	<organization>GoDaddy Inc.</organization>


	<address>	<address>
	<postal>	<postal>
	<street>14455 N. Hayden Rd. #219</street>	<street>14455 N. Hayden Rd. #219</street>


	<city>Scottsdale</city>	<city>Scottsdale</city>


	<region>AZ</region>	<region>AZ</region>


	<code>85260</code>	<code>85260</code>

		<country>United States of America</country>
	<country>US</country>
	</postal>	</postal>


	<email>rcarney@godaddy.com</email>	<email>rcarney@godaddy.com</email>


	<uri>http://www.godaddy.com</uri>	<uri>http://www.godaddy.com</uri>
	</address>	</address>
	</author>	</author>


	<author fullname="Gavin Brown" initials="G." surname="Brown">	<author fullname="Gavin Brown" initials="G." surname="Brown">
	<organization>CentralNic Group plc</organization>	<organization>CentralNic Group plc</organization>


	<address>	<address>
	<postal>	<postal>
	<street>35-39 Moorgate</street>	<street>35-39 Moorgate</street>


	<city>London</city>	<city>London</city>

		<region/>
	<region>England</region>

	<code>EC2R 6AR</code>	<code>EC2R 6AR</code>

		<country>United Kingdom</country>
	<country>GB</country>
	</postal>	</postal>


	<phone>+44 20 33 88 0600</phone>	<phone>+44 20 33 88 0600</phone>
	<email>gavin.brown@centralnic.com</email>	<email>gavin.brown@centralnic.com</email>


	<uri>http://www.centralnic.com</uri>	<uri>http://www.centralnic.com</uri>
	</address>	</address>
	</author>	</author>


	<author fullname="Jothan Frakes" initials="J." surname="Frakes">	<author fullname="Jothan Frakes" initials="J." surname="Frakes">
	<organization/>	<organization/>


	<address>	<address>
	<email>jothan@jothan.com</email>	<email>jothan@jothan.com</email>


	<uri>http://jothan.com</uri>	<uri>http://jothan.com</uri>
	</address>	</address>
	</author>	</author>

		<date year="2020" month="March"/>
	<date year="2019"/>

	<!-- Meta-data Declarations -->

	<area>Applications and Real-Time</area>	<area>Applications and Real-Time</area>


	<workgroup>Registration Protocols Extensions</workgroup>	<workgroup>Registration Protocols Extensions</workgroup>

	<abstract>	<abstract>

	<t>Given the expansion of the DNS namespace, and the proliferation of	<t>Given the expansion of the DNS namespace and the proliferation of
	novel business models, it is desirable to provide a method for Extensible	novel business models, it is desirable to provide a method for Extensible
	Provisioning Protocol (EPP) clients to query EPP servers for the fees and	Provisioning Protocol (EPP) clients to query EPP servers for the fees and

	credits and provide expected fees and credits for certain commands and	credits associated with various billable transactions and provide expected fees and credits for certain commands and
	objects. This document describes an EPP extension mapping for registry fee s.	objects. This document describes an EPP extension mapping for registry fee s.
	</t>	</t>
	</abstract>	</abstract>


	</front>	</front>


	<middle>	<middle>

	<section title="Introduction">	<section anchor="intro" numbered="true" toc="default">
		<name>Introduction</name>

	<t>Historically, domain name registries have applied a simple fee	<t>Historically, domain name registries have applied a simple fee
	structure for billable transactions, namely a basic unit price applied to	structure for billable transactions, namely a basic unit price applied to

	domain <create>, <renew>, <transfer> and RGP [RFC3915]	domain <create>, <renew>, <transfer>, and Redemption
		Grace Period (RGP) <xref target="RFC3915" format="default"/>
	restore commands. Given the relatively small number of EPP servers to	restore commands. Given the relatively small number of EPP servers to
	which EPP clients have been required to connect, it has generally been the	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	case that client operators have been able to obtain details of these fees

	out-of-band by contacting the server operators.</t>	out of band by contacting the server operators.</t>
		<t>Given the expansion of the DNS namespace and the proliferation
	<t>Given the expansion of the DNS namespace, and the proliferation
	of novel business models, it is desirable to provide a method for EPP	of novel business models, it is desirable to provide a method for EPP
	clients to query EPP servers for the fees and credits associated with	clients to query EPP servers for the fees and credits associated with

	certain commands and specific objects.</t>	various billable transactions and certain commands and specific objects.</
		t>
	<t>This document describes an extension mapping for version 1.0 of the	<t>This document describes an extension mapping for version 1.0 of the

	Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping	Extensible Provisioning Protocol (EPP) <xref target="RFC5730" format="defa ult"/>. This EPP mapping
	provides a mechanism by which EPP clients may query the fees and credits	provides a mechanism by which EPP clients may query the fees and credits

	associated with various billable transactions, and obtain their	associated with various billable transactions and obtain their
	current account balance.</t>	current account balance.</t>

		<section anchor="conventions" numbered="true" toc="default">
		<name>Conventions Used in This Document</name>
		<t>
		The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
		IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
		"<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDE
		D</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and
		"<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
		described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/>
		when, and only when, they appear in all capitals, as shown here.
		</t>


	<section title="Conventions Used in This Document">	<t>XML is case sensitive. Unless stated otherwise, the XML specification
	<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",	s
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and	and examples provided in this document <bcp14>MUST</bcp14> be interprete
	"OPTIONAL" in this document are to be interpreted as described in BCP 14	d in the
	<xref target="RFC2119"/>
	<xref target="RFC8174"/> when, and only when, they appear
	in all capitals, as shown here.</t>

	<t>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	character case presented in order to develop a conforming
	implementation.</t>	implementation.</t>


	<t>"fee" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:fee- 1.0".	<t>"fee" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:fee- 1.0".

	The XML namespace prefix "fee" is used, but implementations MUST NOT	The XML namespace prefix "fee" is used, but implementations <bcp14>MUST NOT</bcp14>
	depend on it and instead employ a proper namespace-aware XML parser and	depend on it and instead employ a proper namespace-aware XML parser and
	serializer to interpret and output the XML documents.</t>	serializer to interpret and output the XML documents.</t>

		<t>In the examples, "C:" represents lines sent by a protocol client, and
	<t>In examples, "C:" represents lines sent by a protocol client and "S:"	"S:"
	represents lines returned by a protocol server. Indentation and white	represents lines returned by a protocol server. Indentation and white

	space in examples are provided only to illustrate element relationships	space in the examples are provided only to illustrate element relationsh ips
	and are not a required feature of this protocol.	and are not a required feature of this protocol.
	</t>	</t>


	</section>	</section>
	</section>	</section>

		<section anchor="migrating" numbered="true" toc="default">
	<section title="Migrating to Newer Versions of This Extension">	<name>Migrating to Newer Versions of This Extension</name>
	<t>Servers which implement this extension SHOULD provide a way for clients	<t>Servers that implement this extension <bcp14>SHOULD</bcp14> provide a w
		ay for clients
	to progressively update their implementations when a new version of the	to progressively update their implementations when a new version of the
	extension is deployed.</t>	extension is deployed.</t>

		<t>Servers <bcp14>SHOULD</bcp14> (for a temporary migration period) provid
	<t>Servers SHOULD (for a temporary migration period) provide support for	e support for
	older versions of the extension in parallel to the newest version, and	older versions of the extension in parallel to the newest version and
	allow clients to select their preferred version via the <svcExtension&g t;	allow clients to select their preferred version via the <svcExtension&g t;
	element of the <login> command.</t>	element of the <login> command.</t>


	<t>If a client requests multiple versions of the extension at login, then,	<t>If a client requests multiple versions of the extension at login, then,

	when preparing responses to commands which do not include extension	when preparing responses to commands that do not include extension
	elements, the server SHOULD only include extension elements in the	elements, the server <bcp14>SHOULD</bcp14> only include extension elements
		in the
	namespace of the newest version of the extension requested by the client.< /t>	namespace of the newest version of the extension requested by the client.< /t>

		<t>When preparing responses to commands that do include extension
	<t>When preparing responses to commands which do include extension	elements, the server <bcp14>SHOULD</bcp14> only include extension elements
	elements, the server SHOULD only include extension elements for the	for the
	extension versions present in the command.</t>	extension versions present in the command.</t>
	</section>	</section>

		<section anchor="extension-elements" numbered="true" toc="default">
	<section title="Extension Elements">	<name>Extension Elements</name>
	<section title="Client Commands">	<section anchor="client-commands" numbered="true" toc="default">
		<name>Client Commands</name>
	<t>The <fee:command> element is used in the EPP <check>	<t>The <fee:command> element is used in the EPP <check>

	command to determine the fee that is applicable to the given command.</t	command to determine the fee that is applicable to the given
	>	command.</t>

	<t>The use of the <fee:command> keys off the use of the "name"
	attribute to define which transform fees the client is requesting
	information about. Here is the list of possible values for the "name"
	attribute:</t>

	<t><list style="symbols">
	<t>"create" indicating a <create> command as defined in [RFC5730
	];</t>
	<t>"delete" indicating a <delete> command as defined in [RFC5730
	];</t>
	<t>"renew" indicating a <renew> command as defined in [RFC5730];
	</t>
	<t>"update" indicating a <update> command as defined in [RFC5730
	];</t>
	<t>"transfer" indicating a <transfer> command as defined in [RFC
	5730];</t>
	<t>If the server supports the Registry Grace Period Mapping [RFC3915],
	then the server MUST also support the "restore" value as defined in
	[RFC3915];</t>
	<t>"custom" indicating a custom command that MUST set the "customName"
	attribute with custom command name. The possible set of custom command
	name values is up to server policy.</t>
	</list></t>


	<t>The <fee:command> element MAY have an OPTIONAL "phase"	<t>The "name" attribute of the <fee:command> is used to define whi
		ch transform fees the client is requesting
		information about. The possible values for the "name"
		attribute are:</t>
		<ul spacing="normal">
		<li>"create", indicating a <create> command as defined in <xref
		target="RFC5730" format="default"/>.</li>
		<li>"delete", indicating a <delete> command as defined in <xref
		target="RFC5730" format="default"/>.</li>
		<li>"renew", indicating a <renew> command as defined in <xref
		target="RFC5730" format="default"/>.</li>
		<li>"update", indicating a <update> command as defined in <xref
		target="RFC5730" format="default"/>.</li>
		<li>"transfer", indicating a <transfer> command as defined in
		<xref target="RFC5730" format="default"/>.</li>
		<li>If the server supports registry grace period mapping <xref
		target="RFC3915" format="default"/>,
		then the server <bcp14>MUST</bcp14> also support the "restore" value a
		s defined in
		<xref target="RFC3915" format="default"/>.</li>
		<li>"custom", indicating a custom command that <bcp14>MUST</bcp14> set
		the "customName"
		attribute with a custom command name. The possible set of custom comma
		nd
		name values is dictated by the server policy.</li>
		</ul>
		<t>The <fee:command> element <bcp14>MAY</bcp14> have an <bcp14>OPT
		IONAL</bcp14> "phase"
	attribute specifying a launch phase as described in	attribute specifying a launch phase as described in

	[RFC8334]. It may also contain an OPTIONAL	<xref target="RFC8334" format="default"/>. It may also contain an <bcp1
	"subphase" attribute identifying the custom or sub-phase as described in	4>OPTIONAL</bcp14>
	[RFC8334].</t>	"subphase" attribute identifying the custom or subphase as described in
		<xref target="RFC8334" format="default"/>.</t>
	</section>	</section>

		<section anchor="currency-codes" numbered="true" toc="default">
	<section title="Currency Codes">	<name>Currency Codes</name>
	<t>The <fee:currency> element is used to indicate which currency	<t>The <fee:currency> element is used to indicate the currency
	fees are charged in. This value of this element MUST be a	in which fees are charged. The value of this element <bcp14>MUST</bcp14>
	three-character currency code from [ISO4217:2015].</t>	be a
		three-character currency code from <xref target="ISO4217_2015" format="d
	<t>Note that ISO 4217:2015 provides the special "XXX" code, which MAY be	efault"/>.</t>
	used	<t>Note that <xref target="ISO4217_2015" format="default"/> provides the
	if the server uses a non-currency based system for assessing fees, such	special "XXX" code, which <bcp14>MAY</bcp14> be used
		if the server uses a non-currency-based system for assessing fees, such
	as a system of credits.</t>	as a system of credits.</t>

		<t>The use of <fee:currency> elements in client commands is <bcp14
	<t>The use of <fee:currency> elements in client commands is OPTION	>OPTIONAL</bcp14>: if
	AL: if
	a <fee:currency> element is not present in a command, the server	a <fee:currency> element is not present in a command, the server

	MUST determine the currency based on the server default currency or	<bcp14>MUST</bcp14> determine the currency based on the server default c
	based on the client's account settings which are agreed to by the client	urrency or on the client's account settings, which are agreed to by the client
	and server via an out-of-band channel. However, the <fee:currency>	and server via an out-of-band channel. However, the
	element MUST be present in responses.</t>	<fee:currency> element <bcp14>MUST</bcp14> be present in the respon
		ses.</t>
	<t>Servers SHOULD NOT perform a currency conversion if a client uses an	<t>Servers <bcp14>SHOULD NOT</bcp14> perform a currency conversion if a
	incorrect currency code. Servers SHOULD return a 2004 "Parameter value	client uses an
	range" error instead.</t>	incorrect currency code. Servers <bcp14>SHOULD</bcp14> return a 2004 "P
		arameter value
		range error" instead.</t>
	</section>	</section>

		<section anchor="validity-periods" numbered="true" toc="default">
	<section title="Validity Periods">	<name>Validity Periods</name>
	<t>When querying for fee information using the <check> command,	<t>When querying for fee information using the <check> command,

	the <fee:period> element is used to indicate the period measured	the <fee:period> element is used to indicate the validity
	in years or months, with the appropriate units specified using the "unit	period, which is to be added to extend the registration period of
	"	objects by the <create>, <renew>, and <transfer>
	attribute to be added to the registration period of objects by the	commands. Validity periods are measured in years or months, with the
	<create>, <renew> and <transfer> commands. This	appropriate units specified using the "unit" attribute. Valid values
	element is derived from the <domain:period> element described in	for the "unit" attribute are "y" for years and "m" for months.
	[RFC5731].</t>


	<t>The <fee:period> element is OPTIONAL in <check> commands,	This element is derived from the <domain:period> element described in
	if omitted, the server MUST determine the fee(s) using the server	<xref target="RFC5731" format="default"/>.</t>
	default period. The <fee:period> element MUST be present in	<t>The <fee:period> element is <bcp14>OPTIONAL</bcp14> in <chec
		k> commands;
		if omitted, the server <bcp14>MUST</bcp14> determine the fee(s) using th
		e server
		default period. The <fee:period> element <bcp14>MUST</bcp14> be p
		resent in
	<check> responses.</t>	<check> responses.</t>
	</section>	</section>

		<section anchor="fees-credits" numbered="true" toc="default">
	<section title="Fees and Credits">	<name>Fees and Credits</name>
	<t>Servers which implement this extension will include elements in	<t>Servers that implement this extension will include elements in
	responses which provide information about the fees and/or credits	responses that provide information about the fees and/or credits
	associated with a given billable transaction. A fee will result in	associated with a given billable transaction. A fee will result in

	subtracting from the Account Balance (described in Section 3.5) and a	subtracting from the Account Balance (described in <xref
	credit will result in adding to the Account Balance (described in	target="account-balance"/>), and a
	Section 3.5).</t>	credit will result in adding to the Account Balance (described in <xref
		target="account-balance"/>).</t>
	<t>The <fee:fee> and <fee:credit> elements are used to	<t>The <fee:fee> and <fee:credit> elements are used to
	provide this information. The presence of a <fee:fee> element in	provide this information. The presence of a <fee:fee> element in
	a response indicates a debit against the client's account balance; a	a response indicates a debit against the client's account balance; a
	<fee:credit> element indicates a credit. A <fee:fee>	<fee:credit> element indicates a credit. A <fee:fee>

	element MUST have a zero or greater (non-negative) value. A <fee:cre	element <bcp14>MUST</bcp14> have a zero or greater (non-negative) value.
	dit> element	A <fee:credit> element
	MUST have a negative value.</t>	<bcp14>MUST</bcp14> have a negative value.</t>
		<t>A server <bcp14>MAY</bcp14> respond with multiple <fee:fee> and
	<t>A server MAY respond with multiple <fee:fee> and <fee:credit	<fee:credit>
	>
	elements in the same response. In such cases, the net fee or credit	elements in the same response. In such cases, the net fee or credit
	applicable to the transaction is the arithmetic sum of the values of	applicable to the transaction is the arithmetic sum of the values of
	each of the <fee:fee> and/or <fee:credit> elements. This	each of the <fee:fee> and/or <fee:credit> elements. This

	amount applies to the total additional validity period applied to the	amount applies to the total additional validity period for the
	object (where applicable).</t>	object (where applicable).</t>


	<t>The following attributes are defined for the <fee:fee> element.	<t>The following attributes are defined for the <fee:fee> element.
	These are described in detail below:</t>	These are described in detail below:</t>


	<t>description: an OPTIONAL attribute which provides a human-readable	<dl newline="false">
		<dt>description:</dt>
		<dd>an <bcp14>OPTIONAL</bcp14> attribute that provides a human-readable
	description of the fee. Servers should provide documentation on the	description of the fee. Servers should provide documentation on the

	possible values of this attribute, and their meanings. An OPTIONAL	possible values of this attribute and their meanings. An <bcp14>OPTIONAL
	"lang" attribute MAY be present, per the language structure in [RFC5646]	</bcp14>
	,	"lang" attribute <bcp14>MAY</bcp14> be present, per the language structu
		re in <xref
		target="RFC5646" format="default"/>,
	to identify the language of the returned text and has a default value	to identify the language of the returned text and has a default value
	of "en" (English). If the "description" attribute is not present, the	of "en" (English). If the "description" attribute is not present, the

	"lang" attribute can be ignored.</t>	"lang" attribute can be ignored.</dd>
		<dt>refundable:</dt>
	<t>refundable: an OPTIONAL boolean attribute indicating whether the fee	<dd>an <bcp14>OPTIONAL</bcp14> boolean attribute indicating whether the fee
	is refundable if the object is deleted.</t>	is refundable if the object is deleted.</dd>
		<dt>grace-period:</dt> <dd>an <bcp14>OPTIONAL</bcp14> attribute that pro
	<t>grace-period: an OPTIONAL attribute which provides the time period	vides the time period
	during which the fee is refundable.</t>	during which the fee is refundable.</dd>
		<dt>applied:</dt> <dd>an <bcp14>OPTIONAL</bcp14> attribute indicating w
	<t>applied: an OPTIONAL attribute indicating when the fee will be	hen the fee will be
	deducted from the client's account.</t>	deducted from the client's account.</dd></dl>

	<t>The <fee:credit> element can take a "description" attribute as	<t>The <fee:credit> element can take a "description" attribute as

	described above. An OPTIONAL "lang" attribute MAY be present to	described above. An <bcp14>OPTIONAL</bcp14> "lang" attribute <bcp14>M AY</bcp14> be present to
	identify the language of the returned text and has a default value of	identify the language of the returned text and has a default value of
	"en" (English).</t>	"en" (English).</t>


	<section title="Refunds">	<section anchor="refunds" numbered="true" toc="default">
	<t><fee:fee> elements MAY have an OPTIONAL "refundable"	<name>Refunds</name>
	attribute which takes a boolean value. Fees may be refunded under	<t><fee:fee> elements <bcp14>MAY</bcp14> have an <bcp14>OPTIONAL
		</bcp14> "refundable"
		attribute that takes a boolean value. Fees may be refunded under
	certain circumstances, such as when a domain application is rejected	certain circumstances, such as when a domain application is rejected

	(as described in [RFC8334]) or when an object is	(as described in <xref target="RFC8334" format="default"/>) or when an
	deleted during the relevant Grace Period (see below).</t>	object is
		deleted during the relevant grace period (see <xref target="grace-peri
	<t>If the "refundable" attribute is omitted, then clients SHOULD NOT	ods"/>).</t>
	make any assumption about the refundability of the fee.</t>	<t>If the "refundable" attribute is omitted, then clients <bcp14>SHOUL
		D NOT</bcp14>
		make any assumptions about the refundability of the fee.</t>
	</section>	</section>

		<section anchor="grace-periods" numbered="true" toc="default">
	<section title="Grace Periods">	<name>Grace Periods</name>
	<t>[RFC3915] describes a system of "grace periods", which are time	<t><xref target="RFC3915" format="default"/> describes a system of "gr
		ace periods", which are time
	periods following a billable transaction during which, if an object is	periods following a billable transaction during which, if an object is
	deleted, the client receives a refund.</t>	deleted, the client receives a refund.</t>

		<t>The "grace-period" attribute <bcp14>MAY</bcp14> be used to indicate
	<t>The "grace-period" attribute MAY be used to indicate the relevant	the relevant
	grace period for a fee. If a server implements the Registry Grace	grace period for a fee. If a server implements the registry grace
	Period extension [RFC3915], it MUST specify the grace period for all	period extension <xref target="RFC3915" format="default"/>, it <bcp14>
		MUST</bcp14> specify the grace period for all
	relevant transactions.</t>	relevant transactions.</t>

		<t>If the "grace-period" attribute is omitted, then clients <bcp14>SHO
	<t>If the "grace-period" attribute is omitted, then clients SHOULD NOT	ULD NOT</bcp14>
	make any assumption about the grace period of the fee.</t>	make any assumptions about the grace period of the fee.</t>
	</section>	</section>

		<section anchor="correlation-refund-grace" numbered="true" toc="default"
	<section title="Correlation between Refundability and Grace Periods">	>
	<t>If a <fee:fee> element has a "grace-period" attribute then it	<name>Correlation between Refundability and Grace Periods</name>
	MUST also be refundable and the "refundable" attribute MUST be true.	<t>If a <fee:fee> element has a "grace-period" attribute, then i
	If the "refundable" attribute of a <fee:fee> element is false	t
	then it MUST NOT have a "grace-period" attribute.</t>	<bcp14>MUST</bcp14> also be refundable, and the "refundable" attribute
		<bcp14>MUST</bcp14> be true.
		If the "refundable" attribute of a <fee:fee> element is false,
		then it <bcp14>MUST NOT</bcp14> have a "grace-period" attribute.</t>
	</section>	</section>

		<section anchor="applicability" numbered="true" toc="default">
	<section title="Applicability">	<name>Applicability</name>
	<t>Fees may be applied immediately upon receipt of a command from a	<t>Fees may be applied immediately upon receipt of a command from a

	client, or may only be applied once an out-of-band process (such as	client or may only be applied once an out-of-band process (such as
	the processing of applications at the end of a launch phase) has taken	the processing of applications at the end of a launch phase) has taken
	place.</t>	place.</t>


	<t>The "applied" attribute of the <fee:fee> element allows	<t>The "applied" attribute of the <fee:fee> element allows

	servers to indicate whether a fee will be applied immediately, or	servers to indicate whether a fee will be applied immediately or
	whether it will be applied at some point in the future. This	whether it will be applied at some point in the future. This
	attribute takes two possible values: "immediate" or "delayed".</t>	attribute takes two possible values: "immediate" or "delayed".</t>
	</section>	</section>


	</section>	</section>

		<section anchor="account-balance" numbered="true" toc="default">
	<section title="Account Balance">	<name>Account Balance</name>
	<t>The <fee:balance> element is an OPTIONAL element which MAY be	<t>The <fee:balance> element is an <bcp14>OPTIONAL</bcp14> element
		that <bcp14>MAY</bcp14> be
	included in server responses to transform commands. If present, it can	included in server responses to transform commands. If present, it can
	be used by the client to determine the remaining credit at the server.</ t>	be used by the client to determine the remaining credit at the server.</ t>


	<t>Whether or not the <fee:balance> is included in responses is a	<t>Whether or not the <fee:balance> is included in responses is a
	matter of server policy. However, if a server chooses to offer support	matter of server policy. However, if a server chooses to offer support

	for this element, it MUST be included in responses to all "transform" or	for this element, it <bcp14>MUST</bcp14> be included in responses to all
	billable commands (e.g. <create>, <renew>, <update>,	"transform" or
		billable commands (e.g., <create>, <renew>, <update>,
	<delete>, <transfer op="request">).</t>	<delete>, <transfer op="request">).</t>

		<t>The value of the <fee:balance> <bcp14>MAY</bcp14> be negative.
	<t>The value of the <fee:balance> MAY be negative. A negative	A negative
	balance indicates that the server has extended a line of credit to the	balance indicates that the server has extended a line of credit to the

	client (see below).</t>	client (see <xref target="credit-limit"/>).</t>

	<t>If a server includes a <fee:balance> element in response to	<t>If a server includes a <fee:balance> element in response to

	transform commands, the value of the element MUST reflect the client's	transform commands, the value of the element <bcp14>MUST</bcp14> reflect the client's
	account balance after any fees or credits associated with that command	account balance after any fees or credits associated with that command
	have been applied. If the "applied" attribute of the <fee:fee> ele ment	have been applied. If the "applied" attribute of the <fee:fee> ele ment

	is "delayed", then the <fee:balance> MUST reflect the client's acc ount	is "delayed", then the <fee:balance> <bcp14>MUST</bcp14> reflect t he client's account
	balance without any fees or credits associated with that command.</t>	balance without any fees or credits associated with that command.</t>
	</section>	</section>

		<section anchor="credit-limit" numbered="true" toc="default">
		<name>Credit Limit</name>


	<section title="Credit Limit">
	<t>As described above, if a server returns a response containing a	<t>As described above, if a server returns a response containing a
	<fee:balance> with a negative value, then the server has extended	<fee:balance> with a negative value, then the server has extended

	a line of credit to the client. A server MAY also include a	a line of credit to the client. A server <bcp14>MAY</bcp14> also
	<fee:creditLimit> element in responses that indicates the maximum	include in responses a
	credit available to a client. A server MAY reject certain transactions	<fee:creditLimit> element that indicates the maximum
		credit available to a client. A server <bcp14>MAY</bcp14> reject certai
		n transactions
	if the absolute value of the <fee:balance> is equal to or exceeds the	if the absolute value of the <fee:balance> is equal to or exceeds the
	value of the <fee:creditLimit> element.</t>	value of the <fee:creditLimit> element.</t>


	<t>Whether or not the <fee:creditLimit> is included in responses	<t>Whether or not the <fee:creditLimit> is included in responses
	is a matter of server policy. However, if a server chooses to offer	is a matter of server policy. However, if a server chooses to offer

	support for this element, it MUST be included in responses to all	support for this element, it <bcp14>MUST</bcp14> be included in response
	"transform" commands (e.g. <create>, <renew>, <update>	s to all
	,	"transform" commands (e.g., <create>, <renew>, <update&gt
		;,
	<delete>, <transfer op="request">).</t>	<delete>, <transfer op="request">).</t>
	</section>	</section>

		<section anchor="classification-objects" numbered="true" toc="default">
	<section title="Classification of Objects">	<name>Classification of Objects</name>
	<t>Objects may be assigned to a particular class, category, or tier,	<t>Objects may be assigned to a particular class, category, or tier,
	each of which has a particular fee or set of fees associated with it.	each of which has a particular fee or set of fees associated with it.

	The <fee:class> element, which MAY appear in <check> and	The <fee:class> element, which <bcp14>MAY</bcp14> appear in <ch eck> and
	transform responses, is used to indicate the classification of an object .</t>	transform responses, is used to indicate the classification of an object .</t>


	<t>If a server makes use of this element, it should provide clients with	<t>If a server makes use of this element, it should provide clients with
	a list of all the values that the element may take via an out-of-band	a list of all the values that the element may take via an out-of-band

	channel. Servers MUST NOT use values which do not appear on this list.<	channel. Servers <bcp14>MUST NOT</bcp14> use values that do not appear
	/t>	on this list.</t>
		<t>Servers that make use of this element <bcp14>MUST</bcp14> use a <f
	<t>Servers that make use of this element MUST use a <fee:class>	ee:class>
	element with the value "standard" for all objects that are subject to	element with the value "standard" for all objects that are subject to
	the standard or default fee.</t>	the standard or default fee.</t>
	</section>	</section>

		<section anchor="phase-subphase" numbered="true" toc="default">
	<section title="Phase and Subphase Attributes">	<name>"Phase" and "Subphase" Attributes</name>
	<t>The <fee:command> element has two attributes, phase and	<t>The <fee:command> element has two attributes, "phase" and
	subphase, that provide additional information related to a specific	"subphase", that provide additional information related to a specific
	launch phase as described in [RFC8334]. These	launch phase, as described in <xref target="RFC8334" format="default"/>.
		These
	attributes are used as filters that should refine the server processing. </t>	attributes are used as filters that should refine the server processing. </t>

		<t>If the client <fee:command> contains a server-supported
	<t>If the client <fee:command> contains a server supported	combination of phase/subphase, the server <bcp14>MUST</bcp14> return
	combination of phase/subphase the server MUST return fee data (including	the fee data (including
	the phase/subphase attribute(s)) for the specific combination.</t>	the phase/subphase attribute(s)) for the specific combination.</t>

		<t>If the client <fee:command> contains no "phase"/"subphase"
	<t>If the client <fee:command> contains no phase/subphase	attributes and the server has only one active phase/subphase combination
	attributes and the server has only one active phase/subphase combination	,
	the server MUST return data (including the phase/subphase attribute(s))	the server <bcp14>MUST</bcp14> return the data (including the "phase"/"s
		ubphase" attribute(s))
	of the currently active phase/subphase.</t>	of the currently active phase/subphase.</t>


	<t>If the client <fee:command> contains no phase/subphase	<t>If the client <fee:command> contains no phase/subphase
	attributes and the server has more than one active phase/subphase	attributes and the server has more than one active phase/subphase

	combination the server MUST respond with a 2003 "Required	combination, the server <bcp14>MUST</bcp14> respond with a 2003 "Require d
	parameter missing" error.</t>	parameter missing" error.</t>


	<t>If the client <fee:command> contains no phase/subphase	<t>If the client <fee:command> contains no phase/subphase

	attributes and the server is currently in a "quiet period" (e.g. not	attributes and the server is currently in a "quiet period" (e.g., not
	accepting registrations or applications) the server MUST return data	accepting registrations or applications), the server <bcp14>MUST</bcp14>
	consistent with the default general availability phase (e.g. "open" or	return data
	"claims") including the appropriate phase/subphase attribute(s).</t>	consistent with the default general availability phase (e.g., "open" or
		"claims"), including the appropriate phase/subphase attribute(s).</t>
	<t>If the client <fee:command> contains a phase attribute with no	<t>If the client <fee:command> contains a phase attribute with no
	subphase and the server has only one active subphase (or no subphase) of	subphase and the server has only one active subphase (or no subphase) of

	this phase, the server MUST return data (including the phase/subphase	this phase, the server <bcp14>MUST</bcp14> return the data (including th e phase/subphase
	attribute(s)) of the provided phase and currently active subphase.</t>	attribute(s)) of the provided phase and currently active subphase.</t>


	<t>If the client <fee:command> contains a phase attribute with no	<t>If the client <fee:command> contains a phase attribute with no
	subphase and the server has more than one active subphase combination of	subphase and the server has more than one active subphase combination of

	this phase, the server MUST respond with a 2003 "Required parameter	this phase, the server <bcp14>MUST</bcp14> respond with a 2003 "Required parameter
	missing" error.</t>	missing" error.</t>


	<t>If the client <fee:command> contains a subphase with no phase	<t>If the client <fee:command> contains a subphase with no phase

	attribute the server MUST respond with a 2003 "Required parameter	attribute, the server <bcp14>MUST</bcp14> respond with a 2003 "Required parameter
	missing" error.</t>	missing" error.</t>


	<t>If the client <fee:command> contains a phase attribute not	<t>If the client <fee:command> contains a phase attribute not

	defined in [RFC8334] or not supported by server	defined in <xref target="RFC8334" format="default"/> or not supported
	the server MUST respond with a 2004 "Parameter value range" error.</t>	by the server,
		the server <bcp14>MUST</bcp14> respond with a 2004 "Parameter value rang
		e error".</t>
	<t>If the client <fee:command> contains a subphase attribute (or	<t>If the client <fee:command> contains a subphase attribute (or

	phase/subphase combination) not supported by server the server MUST	phase/subphase combination) not supported by the server, the server <bcp
	respond with a 2004 "Parameter value range" error.</t>	14>MUST</bcp14>
		respond with a 2004 "Parameter value range error".</t>
	</section>	</section>

		<section anchor="reason" numbered="true" toc="default">
	<section title="Reason">	<name>Reason</name>
	<t>The <fee:reason> element is used to provide server specific	<t>The <fee:reason> element is used to provide server-specific
	text in an effort to better explain why a <check> command did not	text in an effort to better explain why a <check> command did not

	complete as the client expected. An OPTIONAL "lang" attribute MAY be	complete as the client expected. An <bcp14>OPTIONAL</bcp14> "lang" attri bute <bcp14>MAY</bcp14> be
	present to identify the language, per the language structure in	present to identify the language, per the language structure in

	[RFC5646], of the returned text and has a default value of "en" (English	<xref target="RFC5646" format="default"/>, of the returned text and has
	).</t>	a default value of "en" (English).</t>

	<t>The <fee:reason> element can be used within the server response	<t>The <fee:reason> element can be used within the server response
	<fee:command> element or within the <fee:cd> element. See	<fee:command> element or within the <fee:cd> element. See

	section 5.1.1 for details on the <fee:cd> "check data" element.</t	<xref target="epp-check"/> for details on the <fee:cd> "check data
	>	" element.</t>
		<t>If the server cannot calculate the relevant fees because the object,
	<t>If the server cannot calculate the relevant fees, because the object,	command, currency, period, class, or some combination is invalid per
	command, currency, period, class or some combination is invalid per	server policy, the server has two ways of handling the error processing
	server policy, the server has two ways of handling error processing of	of
	<fee:command> element(s):</t>	<fee:command> element(s):</t>

		<ol spacing="normal" type="1">
	<t><list style="numbers">	<li>
	<t>Fast-fail - The server, upon error identification, MAY stop	<t>Fast-fail: The server, upon error identification, <bcp14>MAY</bcp
	processing <fee:command> elements and return to the client a	14> stop
	<fee:cd> containing the <fee:objID> and a	processing <fee:command> elements and return a
		<fee:cd> to the client containing the <fee:objID> and a
	<fee:reason> element detailing the reason for failure.	<fee:reason> element detailing the reason for failure.

	<figure>	</t>
	<artwork><![CDATA[ S: <fee:cd avail="0">
		<sourcecode name="" type=""><![CDATA[ S: <fee:cd avail="0">
	S: <fee:objID>example.xyz</fee:objID>	S: <fee:objID>example.xyz</fee:objID>
	S: <fee:reason>Only 1 year registration periods are	S: <fee:reason>Only 1 year registration periods are
	S: valid.</fee:reason>	S: valid.</fee:reason>
	S: </fee:cd>	S: </fee:cd>

	]]>	]]></sourcecode>
	</artwork>	</li>
	</figure>	<li>
	</t>	<t>Partial-fail: The server, upon error identification, <bcp14>MAY</
	<t>Partial-fail - The server, upon error identification, MAY continue	bcp14> continue
	processing <fee:command> elements and return to the client a	processing <fee:command> elements and return a
	<fee:cd> containing successfully processed <fee:command>	<fee:cd> to the client containing the successfully processed &lt
		;fee:command>
	elements and failed <fee:command> elements. All returned failed	elements and failed <fee:command> elements. All returned failed

	<fee:command> elements MUST have a <fee:reason>	<fee:command> elements <bcp14>MUST</bcp14> have a <fee:reason
	element detailing the reason for failure, and the server MAY	>
		element detailing the reason for failure, and the server <bcp14>MAY</b
		cp14>
	additionally include a <fee:reason> element at the	additionally include a <fee:reason> element at the
	<fee:cd> level.	<fee:cd> level.

	<figure>	</t>
	<artwork><![CDATA[ S: <fee:cd avail="0">	<sourcecode name="" type=""><![CDATA[ S: <fee:cd avail="0">
	S: <fee:objID>example.xyz</fee:objID>	S: <fee:objID>example.xyz</fee:objID>
	S: <fee:command name="create">	S: <fee:command name="create">
	S: <fee:period unit="y">2</fee:period>	S: <fee:period unit="y">2</fee:period>
	S: <fee:reason>Only 1 year registration periods are	S: <fee:reason>Only 1 year registration periods are
	S: valid.</fee:reason>	S: valid.</fee:reason>
	S: </fee:command>	S: </fee:command>
	S: </fee:cd>	S: </fee:cd>

	]]>	]]></sourcecode>
	</artwork>	</li>
	</figure>	</ol>
	</t>	<t>In either failure scenario, the server <bcp14>MUST</bcp14> set the &l
	</list></t>	t;fee:cd>
		"avail" attribute to false (0), and the server <bcp14>MUST</bcp14> proce
	<t>In either failure scenario the server MUST set the <fee:cd>	ss all objects in
	avail attribute to false (0) and the server MUST process all objects in
	the client request.</t>	the client request.</t>
	</section>	</section>


	</section>	</section>

		<section anchor="server-handling" numbered="true" toc="default">
	<section title="Server Handling of Fee Information">	<name>Server Handling of Fee Information</name>
	<t>Depending on server policy, a client MAY be required to include the	<t>Depending on the server policy, a client <bcp14>MAY</bcp14> be required
		to include the
	extension elements described in this document for certain transform	extension elements described in this document for certain transform
	commands. Servers must provide clear documentation to clients about the	commands. Servers must provide clear documentation to clients about the
	circumstances in which this extension must be used.</t>	circumstances in which this extension must be used.</t>

		<t>The server <bcp14>MUST</bcp14> return avail="0" in its response to a &l
	<t>The server MUST return avail="0" in its response to a <check>	t;check>
	command for any object in the <check> command that does not	command for any object in the <check> command that does not

	include the <fee:check> extension for which the server would	include the <fee:check> extension where the server would
	likewise fail a domain <create> command when no <fee>	fail a domain <create> command when no <fee>
	extension is provided for that same object.</t>	extension is provided for that same object.</t>

		<t>If a server receives a <check> command from a client that
	<t>If a server receives a <check> command from a client, which	results in no possible fee combination, the server <bcp14>MUST</bcp14> set
	results in no possible fee combination, the server MUST set the "avail"	the "avail"
	attribute of the <fee:cd> element to false (0) and provide a	attribute of the <fee:cd> element to false (0) and provide a
	<fee:reason>.</t>	<fee:reason>.</t>

		<t>If a server receives a <check> command from a client that results
	<t>If a server receives a <check> command from a client, which	in an ambiguous result (i.e., multiple possible fee combinations),
	results in an ambiguous result (i.e. multiple possible fee combinations)	the server <bcp14>MUST</bcp14> reject the command with a 2003 "Required pa
	the server MUST reject the command with a 2003 "Required parameter	rameter
	missing" error.</t>	missing" error.</t>

		<t>If a server receives a command from a client that does not include the
	<t>If a server receives a command from a client, which does not include th
	e
	fee extension data elements required by the server for that command, then	fee extension data elements required by the server for that command, then

	the server MUST respond with a 2003 "Required parameter missing" error.</t	the server <bcp14>MUST</bcp14> respond with a 2003 "Required parameter mis
	>	sing" error.</t>

	<t>If the total fee provided by the client is less than the server's own	<t>If the total fee provided by the client is less than the server's own
	calculation of the fee or the server determines the currency is	calculation of the fee or the server determines the currency is

	inappropriate for that command, then the server MUST reject the command	inappropriate for that command, then the server <bcp14>MUST</bcp14> reject
	with a 2004 "Parameter value range" error.</t>	the command
		with a 2004 "Parameter value range error".</t>
	</section>	</section>

		<section anchor="epp-command" numbered="true" toc="default">
	<section title="EPP Command Mapping">	<name>EPP Command Mapping</name>
	<t>A detailed description of the EPP syntax and semantics can be found in	<t>A detailed description of the EPP syntax and semantics can be found in

	[RFC5730].</t>	<xref target="RFC5730" format="default"/>.</t>
		<section anchor="epp-query" numbered="true" toc="default">
	<section title="EPP Query Commands">	<name>EPP Query Commands</name>
	<t>This extension does not add any elements to the EPP <poll> or	<t>This extension does not add any elements to the EPP <poll> or
	<info> commands or responses.</t>	<info> commands or responses.</t>

		<section anchor="epp-check" numbered="true" toc="default">
		<name>EPP <check> Command</name>


	<section title="EPP <check> Command">
	<t>This extension defines a new command called the Fee Check Command	<t>This extension defines a new command called the Fee Check Command
	that defines additional elements for the EPP <check> command to	that defines additional elements for the EPP <check> command to

	provide fee information along with the availability information of the	provide fee information.</t>
	EPP <check> command.</t>	<t>The command <bcp14>MAY</bcp14> contain an <extension> element
		, which <bcp14>MAY</bcp14>
	<t>The command MAY contain an <extension> element which MAY
	contain a <fee:check> element. The <fee:check> element	contain a <fee:check> element. The <fee:check> element

	MAY contain one <fee:currency> element and MUST contain one or	<bcp14>MAY</bcp14> contain one <fee:currency> element and <bcp14 >MUST</bcp14> contain one or
	more <fee:command> elements.</t>	more <fee:command> elements.</t>

		<t>The <fee:command> element(s) <bcp14>MUST</bcp14> contain a "n
	<t>The <fee:command> element(s) MUST contain(s) a "name" attribu	ame" attribute
	te	(see <xref target="client-commands"/>), an <bcp14>OPTIONAL</bcp14> "ph
	(see Section 3.1), an OPTIONAL "phase" attribute, and an OPTIONAL	ase" attribute, and an <bcp14>OPTIONAL</bcp14>
	"subphase" attribute (see Section 3.8). The <fee:command>	"subphase" attribute (see <xref target="phase-subphase"/>). The <fe
	element(s) MAY have the following child elements:</t>	e:command>
		element(s) <bcp14>MAY</bcp14> have the following child elements:</t>
	<t><list style="symbols">	<ul spacing="normal">
	<t>An OPTIONAL <fee:period> element (as described in Section 3	<li>An <bcp14>OPTIONAL</bcp14> <fee:period> element (as descri
	.3).</t>	bed in <xref target="validity-periods"/>).</li>
	</list></t>	</ul>
		<t>Example <check> command:</t>
	<figure>	<sourcecode name="" type=""><![CDATA[
	<preamble>Example <check> command:</preamble>

	<artwork><![CDATA[
	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <check>	C: <check>
	C: <domain:check	C: <domain:check
	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	C: <domain:name>example.com</domain:name>	C: <domain:name>example.com</domain:name>
	C: <domain:name>example.net</domain:name>	C: <domain:name>example.net</domain:name>
	C: <domain:name>example.xyz</domain:name>	C: <domain:name>example.xyz</domain:name>
	C: </domain:check>	C: </domain:check>

	skipping to change at line 617 ¶	skipping to change at line 507 ¶
	C: <fee:command name="create">	C: <fee:command name="create">
	C: <fee:period unit="y">2</fee:period>	C: <fee:period unit="y">2</fee:period>
	C: </fee:command>	C: </fee:command>
	C: <fee:command name="renew"/>	C: <fee:command name="renew"/>
	C: <fee:command name="transfer"/>	C: <fee:command name="transfer"/>
	C: <fee:command name="restore"/>	C: <fee:command name="restore"/>
	C: </fee:check>	C: </fee:check>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>

	C: </epp>]]>	C: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	<t>When the server receives a <check> command that includes the	<t>When the server receives a <check> command that includes the

	extension elements described above, its response MUST contain an	extension elements described above, its response <bcp14>MUST</bcp14> c
	<extension> element, which MUST contain a child	ontain an
	<fee:chkData> element. The <fee:chkData> element MUST	<extension> element, which <bcp14>MUST</bcp14> contain a child
		<fee:chkData> element. The <fee:chkData> element <bcp14>MU
		ST</bcp14>
	contain a <fee:currency> element and a <fee:cd> element	contain a <fee:currency> element and a <fee:cd> element
	for each object referenced in the client <check> command.</t>	for each object referenced in the client <check> command.</t>

		<t>Each <fee:cd> (check data) element <bcp14>MUST</bcp14> contai
	<t>Each <fee:cd> (check data) element MUST contain the following	n the following
	child elements:</t>	child elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>A <fee:objID> element, which <bcp14>MUST</bcp14> match an
	<t>A <fee:objID> element, which MUST match an element	element
	referenced in the client <check> command.</t>	referenced in the client <check> command.</li>
	<t>An OPTIONAL <fee:class> element (as described in Section 3.	<li>An <bcp14>OPTIONAL</bcp14> <fee:class> element (as
	7).</t>	described in <xref target="classification-objects"/>).</li>
	<t>A <fee:command> element matching each <fee:command>	<li>A <fee:command> element matching each <fee:command>
	(unless the "avail" attribute of the <fee:cd> if false) that	(unless the "avail" attribute of the <fee:cd> is false) that
	appeared in the corresponding <fee:check> of the client	appeared in the corresponding <fee:check> of the client

	command. This element MAY have the OPTIONAL "standard" attribute,	command. This element <bcp14>MAY</bcp14> have the <bcp14>OPTIONAL</b cp14> "standard" attribute,
	with a default value of "0" (or "false"), which indicates whether	with a default value of "0" (or "false"), which indicates whether

	the fee matches the fee of the "standard" classification (see	the fee is the standard or default fee (see
	section 3.7). This element MAY have the OPTIONAL "phase" and	<xref target="classification-objects"/>). This element <bcp14>MAY</b
		cp14> have the <bcp14>OPTIONAL</bcp14> "phase" and
	"subphase" attributes, which will match the same attributes in the	"subphase" attributes, which will match the same attributes in the
	corresponding <fee:command> element of the client command if	corresponding <fee:command> element of the client command if

	sent by the client.</t>	sent by the client.</li>
	</list></t>	</ul>
		<t>The <fee:cd> element also has an <bcp14>OPTIONAL</bcp14> "ava
	<t>The <fee:cd> element also has an OPTIONAL "avail"	il"
	attribute which is a boolean. If the value of this attribute evaluates	attribute, which is a boolean. If the value of this attribute evaluate
		s
	to false, this indicates that the server cannot calculate the relevant	to false, this indicates that the server cannot calculate the relevant

	fees, because the object, command, currency, period, class or some	fees because the object, command, currency, period, class, or some
	combination is invalid per server policy. If "avail" is false then the	combination is invalid per server policy. If "avail" is false, then th
	<fee:cd> or the <fee:command> element MUST contain a	e
	<fee:reason> element (as described in Section 3.9) and the	<fee:cd> or the <fee:command> element <bcp14>MUST</bcp14>
	server MAY eliminate some or all of the <fee:command> element(s)	contain a
	.</t>	<fee:reason> element (as described in <xref target="reason"/>),
		and the
	<t>The <fee:command> element(s) MAY have the following child	server <bcp14>MAY</bcp14> eliminate some or all of the <fee:command
		> element(s).</t>
		<t>The <fee:command> element(s) <bcp14>MAY</bcp14> have the foll
		owing child
	elements:</t>	elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>An <bcp14>OPTIONAL</bcp14> <fee:period> element (as descri
	<t>An OPTIONAL <fee:period> element (as described in Section	bed in <xref target="validity-periods"/>), which contains the same unit, if pres
	3.3), which contains the same unit, if present, that appeared in the	ent, that appeared in the
	<fee:period> element of the command. If the value of the paren t	<fee:period> element of the command. If the value of the paren t

	<fee:command> element is "restore", this element MUST NOT be	<fee:command> element is "restore", this element <bcp14>MUST N
	included, otherwise it MUST be included. If no <fee:period>	OT</bcp14> be
	appeared in the client command (and the command is not "restore")	included; otherwise, it <bcp14>MUST</bcp14> be included. If no <f
	then the server MUST return its default period value.</t>	ee:period>
	<t>Zero or more <fee:fee> elements (as described in Section 3.	appeared in the client command (and the command is not "restore"),
	4).</t>	then the server <bcp14>MUST</bcp14> return its default period value.
	<t>Zero or more <fee:credit> elements (as described in Section	</li>
	3.4).</t>	<li>Zero or more <fee:fee> elements (as described in <xref tar
	<t>An OPTIONAL <fee:reason> element (as described in Section 3	get="fees-credits"/>).</li>
	.9).</t>	<li>Zero or more <fee:credit> elements (as described in
	</list></t>	<xref target="fees-credits"/>).</li>
		<li>An <bcp14>OPTIONAL</bcp14> <fee:reason> element (as descri
		bed in <xref target="reason"/>).</li>
		</ul>
	<t>If the "avail" attribute of the <fee:cd> element is true (1) and	<t>If the "avail" attribute of the <fee:cd> element is true (1) and
	if no <fee:fee> elements are present in a <fee:command>	if no <fee:fee> elements are present in a <fee:command>
	element, this indicates that no fee will be assessed by the server for	element, this indicates that no fee will be assessed by the server for
	this command.</t>	this command.</t>


	<t>If the "avail" attribute of the <fee:cd> element is true (1),	<t>If the "avail" attribute of the <fee:cd> element is true (1),

	then the <fee:command> element MUST NOT contain a <fee:reason >	then the <fee:command> element <bcp14>MUST NOT</bcp14> contain a <fee:reason>
	element.</t>	element.</t>

		<t>Example <check> response:</t>
	<figure>	<sourcecode name="" type=""><![CDATA[
	<preamble>Example <check> response:</preamble>

	<artwork><![CDATA[
	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>
	S: <resData>	S: <resData>
	S: <domain:chkData	S: <domain:chkData
	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	S: <domain:cd>	S: <domain:cd>

	skipping to change at line 782 ¶	skipping to change at line 661 ¶
	S: valid.</fee:reason>	S: valid.</fee:reason>
	S: </fee:command>	S: </fee:command>
	S: </fee:cd>	S: </fee:cd>
	S: </fee:chkData>	S: </fee:chkData>
	S: </extension>	S: </extension>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54322-XYZ</svTRID>	S: <svTRID>54322-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>

	S: </epp>]]>	S: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	</section>	</section>

		<section anchor="epp-transfer-query" numbered="true" toc="default">
	<section title="EPP Transfer Query Command">	<name>EPP Transfer Query Command</name>
	<t>This extension does not add any elements to the EPP <transfer&gt ;	<t>This extension does not add any elements to the EPP <transfer&gt ;

	query command, but does include elements in the response, when the	query command, but it does include elements in the response when the
	extension is included in the <login> command service extensions. </t>	extension is included in the <login> command service extensions. </t>


	<t>When the <transfer> query command has been processed	<t>When the <transfer> query command has been processed
	successfully, if the client has included the extension in the <logi n>	successfully, if the client has included the extension in the <logi n>
	command service <svcExtension> element, and if the client is	command service <svcExtension> element, and if the client is
	authorized by the server to view information about the transfer, then	authorized by the server to view information about the transfer, then

	the server MAY include in the <extension> section of the EPP	the server <bcp14>MAY</bcp14> include in the <extension> section of the EPP
	response a <fee:trnData> element, which contains the following	response a <fee:trnData> element, which contains the following
	child elements:</t>	child elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>A <fee:currency> element (as described in <xref target="cu
	<t>A <fee:currency> element (as described in Section 3.2).</t>	rrency-codes"/>).</li>
	<t>A <fee:period> element (as described in Section 3.3).</t>	<li>A <fee:period> element (as described in <xref target="vali
	<t>Zero or more <fee:fee> elements (as described in Section	dity-periods"/>).</li>
	3.4) containing the fees that will be charged to the gaining client.	<li>Zero or more <fee:fee> elements (as described in <xref ta
	</t>	rget="fees-credits"/>) containing the fees that will be charged to the gaining c
	<t>Zero or more <fee:credit> elements (as described in	lient.</li>
	Section 3.4) containing the credits that will be refunded to the	<li>Zero or more <fee:credit> elements (as described in
	losing client.</t>	<xref target="fees-credits"/>) containing the credits that will be r
	</list></t>	efunded to the
		losing client.</li>
	<t>Servers SHOULD omit <fee:credit> when returning a response to	</ul>
	the gaining client, and omit <fee:fee> elements when returning a	<t>Servers <bcp14>SHOULD</bcp14> omit <fee:credit> when returnin
		g a response to
		the gaining client and omit <fee:fee> elements when returning a
	response to the losing client.</t>	response to the losing client.</t>


	<t>If no <fee:trnData> element is included in the response, then	<t>If no <fee:trnData> element is included in the response, then
	no fee will be assessed by the server for the transfer.</t>	no fee will be assessed by the server for the transfer.</t>

		<t>Example <transfer> query response:</t>
	<figure>	<sourcecode name="" type=""><![CDATA[
	<preamble>Example <transfer> query response:</preamble>

	<artwork><![CDATA[
	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1001">	S: <result code="1001">
	S: <msg>Command completed successfully; action pending</msg>	S: <msg>Command completed successfully; action pending</msg>
	S: </result>	S: </result>
	S: <resData>	S: <resData>
	S: <domain:trnData	S: <domain:trnData
	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	S: <domain:name>example.com</domain:name>	S: <domain:name>example.com</domain:name>

	skipping to change at line 852 ¶	skipping to change at line 721 ¶
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>
	S: <fee:period unit="y">1</fee:period>	S: <fee:period unit="y">1</fee:period>
	S: <fee:fee>5.00</fee:fee>	S: <fee:fee>5.00</fee:fee>
	S: </fee:trnData>	S: </fee:trnData>
	S: </extension>	S: </extension>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54322-XYZ</svTRID>	S: <svTRID>54322-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>

	S: </epp>]]>	S: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	</section>	</section>


	</section>	</section>

		<section anchor="epp-transform" numbered="true" toc="default">
	<section title="EPP Transform Commands">	<name>EPP Transform Commands</name>
		<section anchor="epp-create" numbered="true" toc="default">
	<section title="EPP <create> Command">	<name>EPP <create> Command</name>
	<t>This extension adds elements to both the EPP <create> command	<t>This extension adds elements to both the EPP <create> command

	and response, when the extension is included in the <login>	and response when the extension is included in the <login>
	command service extensions.</t>	command service extensions.</t>


	<t>When submitting a <create> command to the server, the client	<t>When submitting a <create> command to the server, the client

	MAY include in the <extension> element a <fee:create>	<bcp14>MAY</bcp14> include in the <extension> element a <fee:
	element which includes the following child elements:</t>	create>
		element, which includes the following child elements:</t>
	<t><list style="symbols">	<ul spacing="normal">
	<t>An OPTIONAL <fee:currency> element (as described in Section	<li>An <bcp14>OPTIONAL</bcp14> <fee:currency> element (as desc
	3.2);</t>	ribed in
	<t>One or more <fee:fee> elements (as described in Section 3.4	<xref target="currency-codes"/>).</li>
	).</t>	<li>One or more <fee:fee> elements (as described in <xref targ
	</list></t>	et="fees-credits"/>).</li>
		</ul>
	<t>When the <create> command has been processed successfully,	<t>When the <create> command has been processed successfully,

	and the client included the extension in the <login> command	the client included the extension in the <login> command
	service extensions, and a fee was assessed by the server for the	service extensions, and a fee was assessed by the server for the

	transaction, the server MUST include in the <extension> section	transaction, the server <bcp14>MUST</bcp14> include in the <extensi on> section
	of the EPP response a <fee:creData> element, which contains the	of the EPP response a <fee:creData> element, which contains the
	following child elements:</t>	following child elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>A <fee:currency> element (as described in <xref target="cu
	<t>A <fee:currency> element (as described in Section 3.2);</t>	rrency-codes"/>).</li>
	<t>Zero or more <fee:fee> elements (as described in Section 3.	<li>Zero or more <fee:fee> elements (as described in <xref tar
	4);</t>	get="fees-credits"/>).</li>
	<t>Zero or more <fee:credit> elements (as described in Section	<li>Zero or more <fee:credit> elements (as described in <xref
	3.4);</t>	target="fees-credits"/>).</li>
	<t>An OPTIONAL <fee:balance> element (as described in Section	<li>An <bcp14>OPTIONAL</bcp14> <fee:balance> element (as descr
	3.5);</t>	ibed in <xref
	<t>An OPTIONAL <fee:creditLimit> element (as described in Sect	target="account-balance"/>).</li>
	ion 3.6).</t>	<li>An <bcp14>OPTIONAL</bcp14> <fee:creditLimit> element (as d
	</list></t>	escribed in <xref target="credit-limit"/>).</li>
		</ul>
	<figure>	<t>Example <create> command:</t>
	<preamble>Example <create> command:</preamble>	<sourcecode name="" type=""><![CDATA[

	<artwork><![CDATA[
	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <create>	C: <create>
	C: <domain:create	C: <domain:create
	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	C: <domain:name>example.com</domain:name>	C: <domain:name>example.com</domain:name>
	C: <domain:period unit="y">2</domain:period>	C: <domain:period unit="y">2</domain:period>
	C: <domain:ns>	C: <domain:ns>
	C: <domain:hostObj>ns1.example.net</domain:hostObj>	C: <domain:hostObj>ns1.example.net</domain:hostObj>

	skipping to change at line 923 ¶	skipping to change at line 784 ¶
	C: </domain:create>	C: </domain:create>
	C: </create>	C: </create>
	C: <extension>	C: <extension>
	C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">	C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
	C: <fee:currency>USD</fee:currency>	C: <fee:currency>USD</fee:currency>
	C: <fee:fee>5.00</fee:fee>	C: <fee:fee>5.00</fee:fee>
	C: </fee:create>	C: </fee:create>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>

	C: </epp>]]>	C: </epp>
	</artwork>	]]></sourcecode>
	</figure>	<t>Example <create> response:</t>
		<sourcecode name="" type=""><![CDATA[
	<figure>
	<preamble>Example <create> response:</preamble>

	<artwork><![CDATA[
	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>
	S: <resData>	S: <resData>
	S: <domain:creData	S: <domain:creData
	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	S: <domain:name>example.com</domain:name>	S: <domain:name>example.com</domain:name>

	skipping to change at line 962 ¶	skipping to change at line 819 ¶
	S: grace-period="P5D">5.00</fee:fee>	S: grace-period="P5D">5.00</fee:fee>
	S: <fee:balance>-5.00</fee:balance>	S: <fee:balance>-5.00</fee:balance>
	S: <fee:creditLimit>1000.00</fee:creditLimit>	S: <fee:creditLimit>1000.00</fee:creditLimit>
	S: </fee:creData>	S: </fee:creData>
	S: </extension>	S: </extension>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54321-XYZ</svTRID>	S: <svTRID>54321-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>

	S: </epp>]]>	S: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	</section>	</section>

		<section anchor="epp-delete" numbered="true" toc="default">
	<section title="EPP <delete> Command">	<name>EPP <delete> Command</name>
	<t>This extension does not add any elements to the EPP <delete>	<t>This extension does not add any elements to the EPP <delete>

	command, but does include elements in the response, when the extension	command, but it does include elements in the response when the extensi on
	is included in the <login> command service extensions.</t>	is included in the <login> command service extensions.</t>

		<t>When the <delete> command has been processed successfully
	<t>When the <delete> command has been processed successfully,
	and the client included the extension in the <login> command	and the client included the extension in the <login> command

	service extensions, the server MAY include in the <extension>	service extensions, the server <bcp14>MAY</bcp14> include in the <e xtension>
	section of the EPP response a <fee:delData> element, which	section of the EPP response a <fee:delData> element, which
	contains the following child elements:</t>	contains the following child elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>A <fee:currency> element (as described in <xref target="cu
	<t>A <fee:currency> element (as described in Section 3.2);</t>	rrency-codes"/>).</li>
	<t>Zero or more <fee:fee> elements (as described in Section 3.	<li>Zero or more <fee:fee> elements (as described in <xref tar
	4);</t>	get="fees-credits"/>).</li>
	<t>Zero or more <fee:credit> elements (as described in Section	<li>Zero or more <fee:credit> elements (as described in <xref
	3.4);</t>	target="fees-credits"/>).</li>
	<t>An OPTIONAL <fee:balance> element (as described in Section	<li>An <bcp14>OPTIONAL</bcp14> <fee:balance> element (as descr
	3.5);</t>	ibed in <xref
	<t>An OPTIONAL <fee:creditLimit> element (as described in Sect	target="account-balance"/>).</li>
	ion 3.6).</t>	<li>An <bcp14>OPTIONAL</bcp14> <fee:creditLimit> element (as d
	</list></t>	escribed in <xref target="credit-limit"/>).</li>
		</ul>
	<figure>	<t>Example <delete> response:</t>
	<preamble>Example <delete> response:</preamble>	<sourcecode name="" type=""><![CDATA[

	<artwork><![CDATA[
	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>
	S: <extension>	S: <extension>
	S: <fee:delData	S: <fee:delData
	S: xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">	S: xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>

	skipping to change at line 1012 ¶	skipping to change at line 863 ¶
	S: description="AGP Credit"	S: description="AGP Credit"
	S: lang="en">-5.00</fee:credit>	S: lang="en">-5.00</fee:credit>
	S: <fee:balance>1005.00</fee:balance>	S: <fee:balance>1005.00</fee:balance>
	S: </fee:delData>	S: </fee:delData>
	S: </extension>	S: </extension>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54321-XYZ</svTRID>	S: <svTRID>54321-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>

	S: </epp>]]>	S: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	</section>	</section>

		<section anchor="epp-renew" numbered="true" toc="default">
	<section title="EPP <renew> Command">	<name>EPP <renew> Command</name>
	<t>This extension adds elements to both the EPP <renew> command	<t>This extension adds elements to both the EPP <renew> command

	and response, when the extension is included in the <login>	and response when the extension is included in the <login>
	command service extensions.</t>	command service extensions.</t>


	<t>When submitting a <renew> command to the server, the client	<t>When submitting a <renew> command to the server, the client

	MAY include in the <extension> element a <fee:renew>	<bcp14>MAY</bcp14> include in the <extension> element a <fee:
	element which includes the following child elements:</t>	renew>
		element, which includes the following child elements:</t>
	<t><list style="symbols">	<ul spacing="normal">
	<t>An OPTIONAL <fee:currency> element (as described in Section	<li>An <bcp14>OPTIONAL</bcp14> <fee:currency> element (as desc
	3.2);</t>	ribed in <xref target="currency-codes"/>).</li>
	<t>One or more <fee:fee> elements (as described in Section 3.4	<li>One or more <fee:fee> elements (as described in <xref targ
	).</t>	et="fees-credits"/>).</li>
	</list></t>	</ul>
		<t>When the <renew> command has been processed successfully and
	<t>When the <renew> command has been processed successfully, and
	the client included the extension in the <login> command service	the client included the extension in the <login> command service

	extensions, the server MAY include in the <extension> section of	extensions, the server <bcp14>MAY</bcp14> include in the <extension > section of
	the EPP response a <fee:renData> element, which contains the	the EPP response a <fee:renData> element, which contains the
	following child elements:</t>	following child elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>A <fee:currency> element (as described in <xref target="cu
	<t>A <fee:currency> element (as described in Section 3.2);</t>	rrency-codes"/>).</li>
	<t>Zero or more <fee:fee> elements (as described in Section 3.	<li>Zero or more <fee:fee> elements (as described in <xref tar
	4);</t>	get="fees-credits"/>).</li>
	<t>Zero or more <fee:credit> elements (as described in Section	<li>Zero or more <fee:credit> elements (as described in <xref
	3.4);</t>	target="fees-credits"/>).</li>
	<t>An OPTIONAL <fee:balance> element (as described in Section	<li>An <bcp14>OPTIONAL</bcp14> <fee:balance> element (as descr
	3.5);</t>	ibed in <xref target="account-balance"/>).</li>
	<t>An OPTIONAL <fee:creditLimit> element (as described in Sect	<li>An <bcp14>OPTIONAL</bcp14> <fee:creditLimit> element (as d
	ion 3.6).</t>	escribed in <xref target="credit-limit"/>).</li>
	</list></t>	</ul>
		<t>Example <renew> command:</t>
	<figure>	<sourcecode name="" type=""><![CDATA[
	<preamble>Example <renew> command:</preamble>

	<artwork><![CDATA[
	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <renew>	C: <renew>
	C: <domain:renew	C: <domain:renew
	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	C: <domain:name>example.com</domain:name>	C: <domain:name>example.com</domain:name>
	C: <domain:curExpDate>2019-04-03</domain:curExpDate>	C: <domain:curExpDate>2019-04-03</domain:curExpDate>
	C: <domain:period unit="y">5</domain:period>	C: <domain:period unit="y">5</domain:period>
	C: </domain:renew>	C: </domain:renew>
	C: </renew>	C: </renew>
	C: <extension>	C: <extension>
	C: <fee:renew xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">	C: <fee:renew xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
	C: <fee:currency>USD</fee:currency>	C: <fee:currency>USD</fee:currency>
	C: <fee:fee>5.00</fee:fee>	C: <fee:fee>5.00</fee:fee>
	C: </fee:renew>	C: </fee:renew>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>

	C: </epp>]]>	C: </epp>
	</artwork>	]]></sourcecode>
	</figure>	<t>Example <renew> response:</t>
		<sourcecode name="" type=""><![CDATA[
	<figure>
	<preamble>Example <renew> response:</preamble>

	<artwork><![CDATA[
	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>
	S: <resData>	S: <resData>
	S: <domain:renData	S: <domain:renData
	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	S: <domain:name>example.com</domain:name>	S: <domain:name>example.com</domain:name>

	skipping to change at line 1104 ¶	skipping to change at line 942 ¶
	S: refundable="1"	S: refundable="1"
	S: grace-period="P5D">5.00</fee:fee>	S: grace-period="P5D">5.00</fee:fee>
	S: <fee:balance>1000.00</fee:balance>	S: <fee:balance>1000.00</fee:balance>
	S: </fee:renData>	S: </fee:renData>
	S: </extension>	S: </extension>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54322-XYZ</svTRID>	S: <svTRID>54322-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>

	S: </epp>]]>	S: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	</section>	</section>

		<section anchor="epp-transfer-command" numbered="true" toc="default">
	<section title="EPP <transfer> Command">	<name>EPP <transfer> Command</name>
	<t>This extension adds elements to both the EPP <transfer>	<t>This extension adds elements to both the EPP <transfer>

	command and response, when the value of the "op" attribute of the	command and response when the value of the "op" attribute of the
	<transfer> command element is "request", and the extension is	<transfer> command element is "request" and the extension is
	included in the <login> command service extensions.</t>	included in the <login> command service extensions.</t>


	<t>When submitting a <transfer> command to the server, the	<t>When submitting a <transfer> command to the server, the

	client MAY include in the <extension> element a	client <bcp14>MAY</bcp14> include in the <extension> element a
	<fee:transfer> element which includes the following child	<fee:transfer> element, which includes the following child
	elements:</t>	elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>An <bcp14>OPTIONAL</bcp14> <fee:currency> element (as desc
	<t>An OPTIONAL <fee:currency> element (as described in Section	ribed in <xref target="currency-codes"/>).</li>
	3.2);</t>	<li>One or more <fee:fee> elements (as described in <xref targ
	<t>One or more <fee:fee> elements (as described in Section 3.4	et="fees-credits"/>).</li>
	).</t>	</ul>
	</list></t>	<t>When the <transfer> command has been processed successfully

	<t>When the <transfer> command has been processed successfully,
	and the client included the extension in the <login> command	and the client included the extension in the <login> command

	service extensions, the server MAY include in the <extension>	service extensions, the server <bcp14>MAY</bcp14> include in the <e xtension>
	section of the EPP response a <fee:trnData> element, which	section of the EPP response a <fee:trnData> element, which
	contains the following child elements:</t>	contains the following child elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>A <fee:currency> element (as described in <xref target="cu
	<t>A <fee:currency> element (as described in Section 3.2);</t>	rrency-codes"/>).</li>
	<t>Zero or more <fee:fee> elements (as described in Section 3.	<li>Zero or more <fee:fee> elements (as described in <xref tar
	4);</t>	get="fees-credits"/>).</li>
	<t>Zero or more <fee:credit> elements (as described in Section	<li>Zero or more <fee:credit> elements (as described in <xref
	3.4);</t>	target="fees-credits"/>).</li>
	<t>An OPTIONAL <fee:balance> element (as described in Section	<li>An <bcp14>OPTIONAL</bcp14> <fee:balance> element (as descr
	3.5);</t>	ibed in <xref target="account-balance"/>).</li>
	<t>An OPTIONAL <fee:creditLimit> element (as described in Sect	<li>An <bcp14>OPTIONAL</bcp14> <fee:creditLimit> element (as d
	ion 3.6).</t>	escribed in <xref target="credit-limit"/>).</li>
	</list></t>	</ul>
		<t>Example <transfer> command:</t>
	<figure>	<sourcecode name="" type=""><![CDATA[
	<preamble>Example <transfer> command:</preamble>

	<artwork><![CDATA[
	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <transfer op="request">	C: <transfer op="request">
	C: <domain:transfer	C: <domain:transfer
	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	C: <domain:name>example.com</domain:name>	C: <domain:name>example.com</domain:name>
	C: <domain:period unit="y">1</domain:period>	C: <domain:period unit="y">1</domain:period>
	C: <domain:authInfo>	C: <domain:authInfo>
	C: <domain:pw roid="JD1234-REP">2fooBAR</domain:pw>	C: <domain:pw roid="JD1234-REP">2fooBAR</domain:pw>
	C: </domain:authInfo>	C: </domain:authInfo>
	C: </domain:transfer>	C: </domain:transfer>
	C: </transfer>	C: </transfer>
	C: <extension>	C: <extension>

	C: <fee:transfer xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">	C: <fee:transfer xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
	C: <fee:currency>USD</fee:currency>	C: <fee:currency>USD</fee:currency>
	C: <fee:fee>5.00</fee:fee>	C: <fee:fee>5.00</fee:fee>
	C: </fee:transfer>	C: </fee:transfer>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>

	C: </epp>]]>	C: </epp>
	</artwork>	]]></sourcecode>
	</figure>	<t>Example <transfer> response:</t>
		<sourcecode name="" type=""><![CDATA[
	<figure>
	<preamble>Example <transfer> response:</preamble>

	<artwork><![CDATA[
	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1001">	S: <result code="1001">
	S: <msg>Command completed successfully; action pending</msg>	S: <msg>Command completed successfully; action pending</msg>
	S: </result>	S: </result>
	S: <resData>	S: <resData>
	S: <domain:trnData	S: <domain:trnData
	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	S: <domain:name>example.com</domain:name>	S: <domain:name>example.com</domain:name>

	skipping to change at line 1204 ¶	skipping to change at line 1029 ¶
	S: <fee:fee	S: <fee:fee
	S: refundable="1"	S: refundable="1"
	S: grace-period="P5D">5.00</fee:fee>	S: grace-period="P5D">5.00</fee:fee>
	S: </fee:trnData>	S: </fee:trnData>
	S: </extension>	S: </extension>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54322-XYZ</svTRID>	S: <svTRID>54322-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>

	S: </epp>]]>	S: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	</section>	</section>

		<section anchor="epp-update" numbered="true" toc="default">
	<section title="EPP <update> Command">	<name>EPP <update> Command</name>
	<t>This extension adds elements to both the EPP <update>	<t>This extension adds elements to both the EPP <update>

	command and response, when the extension is included in the <login& gt;	command and response when the extension is included in the <login&g t;
	command service extensions.</t>	command service extensions.</t>

		<t>When submitting an <update> command to the server, the
	<t>When submitting a <update> command to the server, the	client <bcp14>MAY</bcp14> include in the <extension> element a
	client MAY include in the <extension> element a	<fee:update> element, which includes the following child
	<fee:update> element which includes the following child
	elements:</t>	elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>An <bcp14>OPTIONAL</bcp14> <fee:currency> element (as desc
	<t>An OPTIONAL <fee:currency> element (as described in Section	ribed in <xref target="currency-codes"/>).</li>
	3.2);</t>	<li>One or more <fee:fee> elements (as described in <xref targ
	<t>One or more <fee:fee> elements (as described in Section 3.4	et="fees-credits"/>).</li>
	).</t>	</ul>
	</list></t>	<t>When the <update> command has been processed successfully

	<t>When the <update> command has been processed successfully,
	and the client included the extension in the <login> command	and the client included the extension in the <login> command

	service extensions, the server MAY include in the <extension>	service extensions, the server <bcp14>MAY</bcp14> include in the <e xtension>
	section of the EPP response a <fee:updData> element, which	section of the EPP response a <fee:updData> element, which
	contains the following child elements:</t>	contains the following child elements:</t>

		<ul spacing="normal">
	<t><list style="symbols">	<li>A <fee:currency> element (as described in <xref target="cu
	<t>A <fee:currency> element (as described in Section 3.2);</t>	rrency-codes"/>).</li>
	<t>Zero or more <fee:fee> elements (as described in Section 3.	<li>Zero or more <fee:fee> elements (as described in <xref tar
	4);</t>	get="fees-credits"/>).</li>
	<t>Zero or more <fee:credit> elements (as described in Section	<li>Zero or more <fee:credit> elements (as described in <xref
	3.4);</t>	target="fees-credits"/>).</li>
	<t>An OPTIONAL <fee:balance> element (as described in Section	<li>An <bcp14>OPTIONAL</bcp14> <fee:balance> element (as descr
	3.5);</t>	ibed in <xref target="account-balance"/>).</li>
	<t>An OPTIONAL <fee:creditLimit> element (as described in Sect	<li>An <bcp14>OPTIONAL</bcp14> <fee:creditLimit> element (as d
	ion 3.6).</t>	escribed in <xref target="credit-limit"/>).</li>
	</list></t>	</ul>
		<t>Example <update> command:</t>
	<figure>	<sourcecode name="" type=""><![CDATA[
	<preamble>Example <update> command:</preamble>

	<artwork><![CDATA[
	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>	C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <update>	C: <update>
	C: <domain:update	C: <domain:update
	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	C: <domain:name>example.com</domain:name>	C: <domain:name>example.com</domain:name>
	C: <domain:chg>	C: <domain:chg>
	C: <domain:registrant>sh8013</domain:registrant>	C: <domain:registrant>sh8013</domain:registrant>
	C: </domain:chg>	C: </domain:chg>
	C: </domain:update>	C: </domain:update>
	C: </update>	C: </update>
	C: <extension>	C: <extension>
	C: <fee:update xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">	C: <fee:update xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
	C: <fee:currency>USD</fee:currency>	C: <fee:currency>USD</fee:currency>
	C: <fee:fee>5.00</fee:fee>	C: <fee:fee>5.00</fee:fee>
	C: </fee:update>	C: </fee:update>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>

	C: </epp>]]>	C: </epp>
	</artwork>	]]></sourcecode>
	</figure>	<t>Example <update> response:</t>
		<sourcecode name="" type=""><![CDATA[
	<figure>
	<preamble>Example <update> response:</preamble>

	<artwork><![CDATA[
	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>	S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>
	S: <extension>	S: <extension>
	S: <fee:updData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">	S: <fee:updData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>
	S: <fee:fee>5.00</fee:fee>	S: <fee:fee>5.00</fee:fee>
	S: </fee:updData>	S: </fee:updData>
	S: </extension>	S: </extension>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54321-XYZ</svTRID>	S: <svTRID>54321-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>

	S: </epp>]]>	S: </epp>
	</artwork>	]]></sourcecode>
	</figure>

	</section>	</section>


	</section>	</section>


	</section>	</section>

		<section anchor="syntax" numbered="true" toc="default">
	<section anchor="syntax" title="Formal Syntax">	<name>Formal Syntax</name>
		<t>One schema is presented here -- the EPP Fee Extension schema.</t>
	<t>One schema is presented here that is the EPP Fee Extension schema.</t>

	<t>The formal syntax presented here is a complete schema representation of	<t>The formal syntax presented here is a complete schema representation of

	the object mapping suitable for automated validation of EPP XML instances.	the object mapping suitable for automated validation of EPP XML instances.
	The BEGIN and END tags are not part of the schema; they are used to note t	</t>
	he	<section anchor="fee-extension" numbered="true" toc="default">
	beginning and ending of the schema for URI registration purposes.</t>	<name>Fee Extension Schema</name>
		<t>The formal syntax presented here is a complete schema
	<section title="Fee Extension Schema">	representation <xref target="W3C.REC-xmlschema-1-20041028"/>

	<t>The formal syntax presented here is a complete schema representation
	of the object mapping suitable for automated validation of EPP XML	of the object mapping suitable for automated validation of EPP XML

	instances. The BEGIN and END tags are not part of the schema; they are	instances. The <CODE BEGINS> and <CODE ENDS> tags are not p
	used to note the beginning and ending of the schema for URI registration	art of the schema; they are
		used to note the beginning and end of the schema for URI registration
	purposes.</t>	purposes.</t>

		<sourcecode type="xml" markers="true"><![CDATA[
	<figure>
	<artwork><![CDATA[
	BEGIN
	<?xml version="1.0" encoding="utf-8"?>	<?xml version="1.0" encoding="utf-8"?>
	<schema xmlns="http://www.w3.org/2001/XMLSchema"	<schema xmlns="http://www.w3.org/2001/XMLSchema"
	xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"	xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"
	xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"	xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
	xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"	xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
	targetNamespace="urn:ietf:params:xml:ns:epp:fee-1.0"	targetNamespace="urn:ietf:params:xml:ns:epp:fee-1.0"
	elementFormDefault="qualified">	elementFormDefault="qualified">

	<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />	<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
	<import namespace="urn:ietf:params:xml:ns:domain-1.0" />	<import namespace="urn:ietf:params:xml:ns:domain-1.0" />

	skipping to change at line 1387 ¶	skipping to change at line 1188 ¶
	<sequence>	<sequence>
	<element name="objID" type="fee:objectIdentifierType" />	<element name="objID" type="fee:objectIdentifierType" />
	<element name="class" type="token" minOccurs="0" />	<element name="class" type="token" minOccurs="0" />
	<element name="command" type="fee:commandDataType"	<element name="command" type="fee:commandDataType"
	minOccurs="0" maxOccurs="unbounded" />	minOccurs="0" maxOccurs="unbounded" />
	<element name="reason" type="fee:reasonType" minOccurs="0" />	<element name="reason" type="fee:reasonType" minOccurs="0" />
	</sequence>	</sequence>
	<attribute name="avail" type="boolean" default="1" />	<attribute name="avail" type="boolean" default="1" />
	</complexType>	</complexType>


	<!-- general transform (create, renew, update, transfer) command -->	<!-- general transform (create, renew, update, transfer) command-->
	<complexType name="transformCommandType">	<complexType name="transformCommandType">
	<sequence>	<sequence>
	<element name="currency" type="fee:currencyType"	<element name="currency" type="fee:currencyType"
	minOccurs="0" />	minOccurs="0" />
	<element name="fee" type="fee:feeType"	<element name="fee" type="fee:feeType"
	maxOccurs="unbounded" />	maxOccurs="unbounded" />
	<element name="credit" type="fee:creditType"	<element name="credit" type="fee:creditType"
	minOccurs="0" maxOccurs="unbounded" />	minOccurs="0" maxOccurs="unbounded" />
	</sequence>	</sequence>
	</complexType>	</complexType>

	skipping to change at line 1520 ¶	skipping to change at line 1321 ¶

	<simpleType name="balanceType">	<simpleType name="balanceType">
	<restriction base="decimal" />	<restriction base="decimal" />
	</simpleType>	</simpleType>

	<simpleType name="creditLimitType">	<simpleType name="creditLimitType">
	<restriction base="decimal" />	<restriction base="decimal" />
	</simpleType>	</simpleType>

	</schema>	</schema>

	END]]>	]]></sourcecode>
	</artwork>
	</figure>
	</section>	</section>


	</section>	</section>

		<section anchor="Security" numbered="true" toc="default">
	<section anchor="Security" title="Security Considerations">	<name>Security Considerations</name>
	<t>The mapping extensions described in this document do not provide any	<t>The mapping extensions described in this document do not provide any

	security services beyond those described by EPP [RFC5730], the EPP domain	security services beyond those described by the EPP <xref target="RFC5730"
	name mapping [RFC5731], and protocol layers used by EPP. The security	format="default"/>, the EPP domain
		name mapping <xref target="RFC5731" format="default"/>, and the protocol
		layers used by the EPP. The security
	considerations described in these other specifications apply to this	considerations described in these other specifications apply to this
	specification as well. This extension passes financial information using	specification as well. This extension passes financial information using
	the EPP protocol, so confidentiality and integrity protection must be	the EPP protocol, so confidentiality and integrity protection must be
	provided by the transport mechanism. All transports compliant with	provided by the transport mechanism. All transports compliant with

	[RFC5730] provide the needed level of confidentiality and integrity	<xref target="RFC5730" format="default"/> provide the needed level of conf identiality and integrity
	protections. The server will only provide information, including	protections. The server will only provide information, including
	financial information, that is relevant to the authenticated client.</t>	financial information, that is relevant to the authenticated client.</t>
	</section>	</section>

		<section anchor="IANA" numbered="true" toc="default">
	<section anchor="IANA" title="IANA Considerations">	<name>IANA Considerations</name>
		<section anchor="xml-namespace" numbered="true" toc="default">
	<section title="XML Namespace">	<name>XML Namespace</name>
	<t>This document uses URNs to describe XML namespaces and XML schemas	<t>This document uses URNs to describe XML namespaces and XML schemas

	conforming to a registry mechanism described in <xref target="RFC3688"/>	conforming to a registry mechanism described in <xref target="RFC3688" f
	.</t>	ormat="default"/>.</t>

	<t>Registration request for the fee namespace:</t>	<t>Registration request for the fee namespace:</t>


	<t>URI: urn:ietf:params:xml:ns:epp:fee-1.0</t>	<t>URI: urn:ietf:params:xml:ns:epp:fee-1.0</t>


	<t>Registrant Contact: IESG</t>	<t>Registrant Contact: IESG</t>


	<t>XML: None. Namespace URIs do not represent an XML specification.</t>	<t>XML: None. Namespace URIs do not represent an XML specification.</t>

		<t>Registration request for the fee schema:</t>
	<t>Registration request for the fee schema:</t>	<t>URI: urn:ietf:params:xml:schema:epp:fee-1.0</t>
		<t>Registrant Contact: IESG</t>
	<t>URI: urn:ietf:params:xml:schema:epp:fee-1.0</t>	<t>XML: See <xref target="syntax"/> of this document.</t>
		</section>
	<t>Registrant Contact: IESG</t>	<section anchor="epp-extension-reg" numbered="true" toc="default">
		<name>EPP Extension Registry</name>
	<t>XML: See the "Formal Syntax" section of this document.</t>	<t>The EPP extension described in this document has been registered by
		IANA in the "Extensions for the Extensible Provisioning Protocol (EPP)"
	</section>	registry described in <xref target="RFC7451" format="default"/>. The

	<section title="EPP Extension Registry">
	<t>The EPP extension described in this document should be registered by
	the IANA in the EPP Extension Registry described in [RFC7451]. The
	details of the registration are as follows:</t>	details of the registration are as follows:</t>


	<t>Name of Extension: Registry Fee Extension for the Extensible	<t>Name of Extension: Registry Fee Extension for the Extensible
	Provisioning Protocol (EPP)</t>	Provisioning Protocol (EPP)</t>


	<t>Document status: Standards Track</t>	<t>Document status: Standards Track</t>

		<t>Reference: RFC 8748</t>
	<t>Reference: (insert reference to RFC version of this document)</t>	<t>Registrant Name and Email Address: IESG <iesg@ietf.org></t>

	<t>Registrant Name and Email Address: IESG, <iesg@ietf.org></t>

	<t>TLDs: Any</t>	<t>TLDs: Any</t>


	<t>IPR Disclosure: None</t>	<t>IPR Disclosure: None</t>


	<t>Status: Active</t>	<t>Status: Active</t>


	<t>Notes: None</t>	<t>Notes: None</t>


	</section>	</section>


	</section>	</section>


	<section title="Implementation Status">
	<t>Note to RFC Editor: Please remove this section and the reference to
	[RFC7942] before publication.</t>

	<t>This section records the status of known implementations of the
	protocol defined by this specification at the time of posting of this
	Internet-Draft, and is based on a proposal described in [RFC7942]. The
	description of implementations in this section is intended to assist the
	IETF in its decision processes in progressing drafts to RFCs. Please note
	that the listing of any individual implementation here does not imply
	endorsement by the IETF. Furthermore, no effort has been spent to verify
	the information presented here that was supplied by IETF contributors.
	This is not intended as, and must not be construed to be, a catalog of
	available implementations or their features. Readers are advised to note
	that other implementations may exist.</t>

	<t>According to [RFC7942], "this will allow reviewers and working groups
	to assign due consideration to documents that have the benefit of running
	code, which may serve as evidence of valuable experimentation and feedback
	that have made the implemented protocols more mature. It is up to the
	individual working groups to use this information as they see fit".</t>

	<section title="RegistryEngine EPP Service">
	<t>Organization: CentralNic</t>

	<t>Name: RegistryEngine EPP Service</t>

	<t>Description: Generic high-volume EPP service for gTLDs, ccTLDs and
	SLDs</t>

	<t>Level of maturity: Deployed in CentralNic's production environment as
	well as two other gTLD registry systems, and two ccTLD registry systems.
	</t>

	<t>Coverage: All aspects of the protocol are implemented.</t>

	<t>Licensing: Proprietary In-House software</t>

	<t>Contact: epp@centralnic.com</t>

	<t>URL: https://www.centralnic.com</t>

	</section>

	</section>

	<section title="Acknowledgements">
	<t>The authors wish to thank the following persons for their feedback and
	suggestions:</t>
	<t><list style="symbols">
	<t>James Gould of Verisign Inc</t>
	<t>Luis Munoz of ISC</t>
	<t>Michael Young of Architelos</t>
	<t>Ben Levac and Jeff Eckhaus of Demand Media</t>
	<t>Seth Goldman of Google</t>
	<t>Klaus Malorny and Michael Bauland of Knipp</t>
	<t>Jody Kolker, Joe Snitker and Kevin Allendorf of Go Daddy</t>
	<t>Michael Holloway of Com Laude</t>
	<t>Santosh Kalsangrah of Impetus Infotech</t>
	<t>Alex Mayrhofer of Nic.at</t>
	<t>Thomas Corte of Knipp Medien und Kommunikation GmbH</t>
	</list></t>
	</section>

	<section title="Change History">

	<section title="Change from 18 to 19">
	<t>Added normative reference for XML Schema.</t>
	</section>

	<section title="Change from 18 to 19">
	<t>Updated per IESG review, all updates (except for one schema change)
	were just textual for clarity and correctness. The schema change was to
	require the name attribute of the commandType element.</t>
	</section>

	<section title="Change from 17 to 18">
	<t>Corrected erroneous edit left in place in previous revision (17),
	reverted text back to original text (revision 16) in section 3.4.</t>
	</section>

	<section title="Change from 16 to 17">
	<t>Updated per AD review, all updates were just textual for clarity and
	correctness.</t>
	</section>

	<section title="Change from 15 to 16">
	<t>Updated per AD review and list comments: several grammar corrections;
	clarification text added to section 3.4.3 and 3.5; and a schema
	update for consistency by providing a "lang" attribute to the
	<fee:fee> and <fee:credit> "description" attribute
	detailed in section 3.4.</t>
	</section>

	<section title="Change from 14 to 15">
	<t>Updated schema, moving the "standard" attribute of the "commandDataTy
	pe" inside the <extension> block.</t>
	</section>

	<section title="Change from 13 to 14">
	<t>Moved RFC 7451 reference from Normative to Informative section.</t>
	</section>

	<section title="Change from 12 to 13">
	<t>Updated XML namespace and schema registration to be "epp" scoped -
	global replace of XML namespace from urn:ietf:params:xml:ns:fee-1.0
	to urn:ietf:params:xml:ns:epp:fee-1.0 and the XML schema
	registration from urn:ietf:params:xml:schema:fee-1.0 to
	urn:ietf:params:xml:schema:epp:fee-1.0.</t>
	</section>

	<section title="Change from 11 to 12">
	<t>Updated references to current version of documents and moved the
	"standard" attribute from the check command (commandType) to the
	check response (commandDataType).</t>
	</section>

	<section title="Change from 10 to 11">
	<t>Updated document per Working Group Last Call comments. Made minor
	textual changes throughout for enhanced clarity per WGLC comments.</t>
	</section>

	<section title="Change from 09 to 10">
	<t>Updated document per Working Group Last Call comments. Updated schema
	to version 1.0 in anticipation of standardization, no changes were made
	to the latest, 0.25, schema. Made minor textual changes throughout for
	enhanced clarity per WGLC comments.</t>
	</section>

	<section title="Change from 08 to 09">
	<t>Updated scheme to version 0.25 to allow tighter checking on
	<fee:command> by splitting the client and server definitions,
	moved the class element from the command to the object level and added
	an optional standard attribute to the command element. Also updated
	section 3.1 for clarity on name attribute; updated section 3.9 for
	clarity on uses of <fee:reason>; removed second paragraph in
	section 5.2.1 as it was duplicative of second to last paragraph in 4.0;
	and updated section 5.1.1 to add section references.</t>
	</section>

	<section title="Change from 07 to 08">
	<t>Updated section 3.8 and 5.1.1 to provide clarity on server processing
	and response of various scenarios (i.e. "quiet" period processing).</t>
	</section>

	<section title="Change from 06 to 07">
	<t>Updated section 3.8 and 4.0 to provide clarity on server processing
	and response of various scenarios.</t>
	</section>

	<section title="Change from 05 to 06">
	<t>Updated scheme to version 0.23 to allow the return of no
	<fee:command> element(s) if an error situation occurs. Edited
	section 3.8 extensively after input from interim meeting and REGEXT F2F
	meeting at IETF-99. Added normative reference for
	draft-ietf-eppext-launchphase.</t>
	</section>

	<section title="Change from 04 to 05">
	<t>Updated scheme to version 0.21 to support the lang attribute for the
	reason element of the objectCDType and the commandType types as well as
	to add the update command to the commandEnum type. Updated section 3.1
	to include language for the custom command. Added section 3.9 to provide
	a description of the <fee:reason> element. Fixed typos and added
	clarification text on when client fee is less than server fee in section
	4. Additionally, I added description pointers to appropriate Section 3
	definitions for element clarity throughout the document.</t>
	</section>

	<section title="Change from 03 to 04">
	<t>Updated scheme to version 0.19 to correct typos and to replace the
	commandTypeValue type with the commandEnum type and customName attribute
	for
	stricter validation. Updated various text for grammar and clarity. Added
	text to section 4 clarifying the <check> response when the client
	provided no fee extension but the server was expecting the extension.</t
	>
	</section>

	<section title="Change from 02 to 03">
	<t>Updated scheme to version 0.17 to simplify the check command syntax.
	Moved fee avail to objectCDType to allow fast failing on error
	situations. Removed the objectCheckType as it was no longer being used.
	Updated examples to reflect these scheme changes. Added language for
	server failing a <create> if the <fee:fee> passed by the
	client is less than the server fee.</t>
	</section>

	<section title="Change from 01 to 02">
	<t>Updated scheme to version 0.15 to fix errors in CommandType,
	objectCDType, transformCommandType and transformResultType definitions.<
	/t>
	</section>

	<section title="Change from 00 to 01">
	<t>Added Roger Carney as author to finish draft. Moved Formal Syntax
	section to main level numbering. Various grammar, typos, and
	administrative edits for clarity. Removed default value for the
	"applied" attribute of <fee:fee> so that it can truly be
	optional. Added support for the <delete> command to return a
	<fee:fee> element as well. Modified default response on the
	<check> command for the optional <fee:period> when it was
	not provided in the command, leaving it to the server to provide the
	default period value. Extensive edits were done to the <check>
	command, the <check> response and to the fee extension schema
	(checkType, objectCheckType, objectIdentifierType, objectCDType,
	commandType) to support requesting and returning multiple transformation
	fees in a single call. Added section on Phase/Subphase to provide more
	context on the uses.</t>
	</section>

	<section title="Change from draft-brown-00 to draft-ietf-regext-fees-00">
	<t>Updated to be REGEXT WG document.</t>
	</section>

	</section>

	</middle>	</middle>


	<!-- ***BACK MATTER *** -->

	<back>	<back>

	<!-- References split into informative and normative -->	<references>
		<name>References</name>
	<!-- There are 2 ways to insert reference entries from the citation librarie	<references>
	s:	<name>Normative References</name>
	1. define an ENTITY at the top, and use "ampersand character"RFC2629; here	<reference anchor="ISO4217_2015" target="https://www.iso.org/standard/64
	(as shown)	758.html">
	2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xm	<front>
	l"?> here	<title>Codes for the representation of currencies</title>
	(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.	<seriesInfo name="ISO" value="4217:2015"/>
	xml")	<author>
		<organization>ISO</organization>
	Both are cited textually in the same manner: by using xref elements.	</author>
	If you use the PI option, xml2rfc will, by default, try to find included fi	<date year="2015" month="August"/>
	les in the same	</front>
	directory as the including file. You can also define the XML_LIBRARY enviro	</reference>
	nment variable	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	with a value containing a set of directories to search. These can be eithe	FC.2119.xml"/>
	r in the local	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	filing system or remote ones accessed by http (http://domain/dir/... ).-->	FC.3688.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	<references title="Normative References">	FC.3915.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	<reference anchor='ISO4217:2015' target='https://www.iso.org/standard/6475	FC.5646.xml"/>
	8.html'>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	<front>	FC.5730.xml"/>
	<title>Codes for the representation of currencies</title>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	<author>	FC.5731.xml"/>
	<organization>International Organization for Standardization</organi	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	zation>	FC.8174.xml"/>
	</author>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
	<date year='2015' month='August'/>	FC.8334.xml"/>
	</front>
	</reference>

	&RFC2119;

	&RFC3688;

	&RFC3915;

	&RFC5730;

	&RFC5731;

	&RFC7942;

	&RFC8174;

	&RFC8334;

	&W3C.REC-xmlschema-1-20041028;

	</references>

	<references title="Informative References">

	&RFC7451;


		<reference anchor="W3C.REC-xmlschema-1-20041028" target="http://www.w3.o
		rg/TR/2004/REC-xmlschema-1-20041028" xml:base="https://xml2rfc.ietf.org/public/r
		fc/bibxml4/reference.W3C.REC-xmlschema-1-20041028.xml">
		<front>
		<title>XML Schema Part 1: Structures Second Edition</title>
		<seriesInfo name="World Wide Web Consortium Recommendation" value="R
		EC-xmlschema-1-20041028"/>
		<author initials="H." surname="Thompson" fullname="Henry Thompson">
		<organization/>
		</author>
		<author initials="D." surname="Beech" fullname="David Beech">
		<organization/>
		</author>
		<author initials="M." surname="Maloney" fullname="Murray Maloney">
		<organization/>
		</author>
		<author initials="N." surname="Mendelsohn" fullname="Noah Mendelsohn
		">
		<organization/>
		</author>
		<date month="October" year="2004"/>
		</front>
		</reference>
		</references>
		<references>
		<name>Informative References</name>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.7451.xml"/>
		</references>
	</references>	</references>

		<section anchor="acknowledgements" numbered="false" toc="default">
		<name>Acknowledgements</name>
		<t>The authors wish to thank the following persons for their feedback and
		suggestions:</t>
		<ul spacing="compact">
		<li><t><contact fullname="James Gould"/> of Verisign Inc.</t></li>
		<li><t><contact fullname="Luis Munoz"/> of ISC</t></li>
		<li><t><contact fullname="Michael Young"/></t></li>
		<li><t><contact fullname="Ben Levac"/></t></li>
		<li><t><contact fullname="Jeff Eckhaus"/></t></li>
		<li><t><contact fullname="Seth Goldman"/> of Google</t></li>
		<li><t><contact fullname="Klaus Malorny"/> and <contact fullname="Michae
		l Bauland"/> of Knipp</t></li>
		<li><t><contact fullname="Jody Kolker"/>, <contact fullname="Joe
		Snitker"/>, and <contact fullname="Kevin Allendorf"/> of GoDaddy</t></li>
		<li><t><contact fullname="Michael Holloway"/> of Com Laude</t></li>
		<li><t><contact fullname="Santosh Kalsangrah"/> of Impetus Infotech</t><
		/li>
		<li><t><contact fullname="Alex Mayrhofer"/> of Nic.at</t></li>
		<li><t><contact fullname="Thomas Corte"/> of Knipp Medien und Kommunikat
		ion GmbH</t></li>
		</ul>
		</section>
	</back>	</back>
	</rfc>	</rfc>

End of changes. 228 change blocks.
	1064 lines changed or deleted	727 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/