Diff: draft-brown-epp-fees-05.txt - draft-brown-epp-fees-06.txt

	< draft-brown-epp-fees-05.txt	draft-brown-epp-fees-06.txt >

	Internet Engineering Task Force G. Brown	Internet Engineering Task Force G. Brown
	Internet-Draft CentralNic Group plc	Internet-Draft CentralNic Group plc

	Intended status: Standards Track August 12, 2015	Intended status: Standards Track J. Frakes
	Expires: February 13, 2016	Expires: May 7, 2016 November 4, 2015

	Registry Fee Extension for the Extensible Provisioning Protocol (EPP)	Registry Fee Extension for the Extensible Provisioning Protocol (EPP)

	draft-brown-epp-fees-05	draft-brown-epp-fees-06

	Abstract	Abstract

	This document describes an Extensible Provisioning Protocol (EPP)	This document describes an Extensible Provisioning Protocol (EPP)
	extension mapping for registry fees.	extension mapping for registry fees.


	Status of this Memo	Status of This Memo

	This Internet-Draft is submitted in full conformance with the	This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.	provisions of BCP 78 and BCP 79.

	Internet-Drafts are working documents of the Internet Engineering	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute	Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-	working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.	Drafts is at http://datatracker.ietf.org/drafts/current/.

	Internet-Drafts are draft documents valid for a maximum of six months	Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any	and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference	time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."	material or to cite them other than as "work in progress."


	This Internet-Draft will expire on February 13, 2016.	This Internet-Draft will expire on May 7, 2016.

	Copyright Notice	Copyright Notice

	Copyright (c) 2015 IETF Trust and the persons identified as the	Copyright (c) 2015 IETF Trust and the persons identified as the
	document authors. All rights reserved.	document authors. All rights reserved.

	This document is subject to BCP 78 and the IETF Trust's Legal	This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents	Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of	(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents	publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect	carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must	to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of	include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as	the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.	described in the Simplified BSD License.

	Table of Contents	Table of Contents


	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Conventions Used in This Document . . . . . . . . . . . . 3	1.1. Conventions Used in This Document . . . . . . . . . . . . 3
	2. Migrating to Newer Versions of This Extension . . . . . . . . 4	2. Migrating to Newer Versions of This Extension . . . . . . . . 4
	3. Extension Elements . . . . . . . . . . . . . . . . . . . . . . 4	3. Extension Elements . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 4	3.1. Supported Objects . . . . . . . . . . . . . . . . . . . . 4
	3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . . 5	3.2. Client Commands . . . . . . . . . . . . . . . . . . . . . 4
	3.3. Validity Periods . . . . . . . . . . . . . . . . . . . . . 5	3.3. Currency Codes . . . . . . . . . . . . . . . . . . . . . 5
	3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . . 5	3.4. Validity Periods . . . . . . . . . . . . . . . . . . . . 5
	3.4.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 6	3.5. Fees and Credits . . . . . . . . . . . . . . . . . . . . 5
	3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 6	3.5.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 6
	3.4.3. Applicability . . . . . . . . . . . . . . . . . . . . 7	3.5.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 6
	3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 7	3.5.3. Correlation between Refundability and Grace Periods . 7
	3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . . 7	3.5.4. Applicability . . . . . . . . . . . . . . . . . . . . 7
	3.7. Classification of Domain Names . . . . . . . . . . . . . . 8	3.6. Account Balance . . . . . . . . . . . . . . . . . . . . . 7
	4. Server Handling of Fee Information . . . . . . . . . . . . . . 8	3.7. Credit Limit . . . . . . . . . . . . . . . . . . . . . . 8
	5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8	3.8. Classification of Objects . . . . . . . . . . . . . . . . 8
	5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 8	4. Server Handling of Fee Information . . . . . . . . . . . . . 8
	5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9	5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 9
	5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . . 13	5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 9
	5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 14	5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9
	5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 14	5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 13
	5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 17	5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 14
	5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 18	5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 14
	5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 20	5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 17
	5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 22	5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 18
	5.3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . 24	5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 29	5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 22
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30	5.3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . 24
	7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 30	6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
	7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . . 30	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
	8. Implementation Status . . . . . . . . . . . . . . . . . . . . 30	7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 30
	8.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . . 31	7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 30
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31	8. Implementation Status . . . . . . . . . . . . . . . . . . . . 31
	10. Change History . . . . . . . . . . . . . . . . . . . . . . . . 32	8.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 31
	10.1. Changes from 00 to 01 . . . . . . . . . . . . . . . . . . 32	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
	10.2. Changes from 01 to 02 . . . . . . . . . . . . . . . . . . 32	10. Change History . . . . . . . . . . . . . . . . . . . . . . . 32
	10.3. Changes from 02 to 03 . . . . . . . . . . . . . . . . . . 33	10.1. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 32
	10.4. Changes from 03 to 04 . . . . . . . . . . . . . . . . . . 33	10.2. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 32
	10.5. Changes from 04 to 05 . . . . . . . . . . . . . . . . . . 34	10.3. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 33
	11. TODO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34	10.4. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 33
	12. Normative References . . . . . . . . . . . . . . . . . . . . . 34	10.5. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 34
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 35	10.6. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 34
		11. Normative References . . . . . . . . . . . . . . . . . . . . 35
		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36

	1. Introduction	1. Introduction

	Historically, domain name registries have applied a simple fee	Historically, domain name registries have applied a simple fee
	structure for billable transactions, namely a basic unit price	structure for billable transactions, namely a basic unit price
	applied to domain <create>, <renew>, <transfer> and RGP [RFC3915]	applied to domain <create>, <renew>, <transfer> and RGP [RFC3915]
	restore commands. Given the relatively small number of EPP servers	restore commands. Given the relatively small number of EPP servers
	to which EPP clients have been required to connect, it has generally	to which EPP clients have been required to connect, it has generally
	been the case that client operators have been able to obtain details	been the case that client operators have been able to obtain details
	of these fees out-of-band by contacting the server operators.	of these fees out-of-band by contacting the server operators.

	skipping to change at page 3, line 37 ¶	skipping to change at page 3, line 37 ¶

	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].	document are to be interpreted as described in RFC 2119 [RFC2119].

	XML is case sensitive. Unless stated otherwise, XML specifications	XML is case sensitive. Unless stated otherwise, XML specifications
	and examples provided in this document MUST be interpreted in the	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.	implementation.


	"fee" is used as an abbreviation for	"fee" is used as an abbreviation for "urn:ietf:params:xml:ns:fee-
	"urn:ietf:params:xml:ns:fee-0.8". The XML namespace prefix "fee" is	0.9". The XML namespace prefix "fee" is used, but implementations
	used, but implementations MUST NOT depend on it and instead employ a	MUST NOT depend on it and instead employ a proper namespace-aware XML
	proper namespace-aware XML parser and serializer to interpret and	parser and serializer to interpret and output the XML documents.
	output the XML documents.

	(Note to RFC Editor: remove the following paragraph before	(Note to RFC Editor: remove the following paragraph before
	publication as an RFC.)	publication as an RFC.)

	The XML namespace prefix above contains a version number,	The XML namespace prefix above contains a version number,

	specifically "0.8". This version number will increment with	specifically "0.9". This version number will increment with
	successive versions of this document, and will reach 1.0 if and when	successive versions of this document, and will reach 1.0 if and when
	this document is published as an RFC. This permits clients to	this document is published as an RFC. This permits clients to
	distinguish which version of the extension a server has implemented.	distinguish which version of the extension a server has implemented.

	2. Migrating to Newer Versions of This Extension	2. Migrating to Newer Versions of This Extension

	(Note to RFC Editor: remove this section before publication as an	(Note to RFC Editor: remove this section before publication as an
	RFC.)	RFC.)

	Servers which implement this extension SHOULD provide a way for	Servers which implement this extension SHOULD provide a way for

	skipping to change at page 4, line 31 ¶	skipping to change at page 4, line 31 ¶
	extension elements, the server SHOULD only include extension elements	extension elements, the server SHOULD only include extension elements
	in the namespace of the newest version of the extension requested by	in the namespace of the newest version of the extension requested by
	the client.	the client.

	When preparing responses to commands which do include extension	When preparing responses to commands which do include extension
	elements, the server SHOULD only include extension elements for the	elements, the server SHOULD only include extension elements for the
	extension versions present in the command.	extension versions present in the command.

	3. Extension Elements	3. Extension Elements


	3.1. Client Commands	3.1. Supported Objects


	The <fee:command> element is used in EPP <check> and <info> commands	By default, this specification assumes that fees and credits will
	to determine the fee which is applicable to the given command.	only be applied for transform commands on domain objects as described
		in [RFC5731]. However, other object types are supported through the
		use of OPTIONAL "objURI" and "element" attributes on the <fee:object>
		and <fee:objId> elements, respectively.

		3.2. Client Commands

		The <fee:command> element is used in the EPP <check> command to
		determine the fee which is applicable to the given command.

	The element values permitted by the server is a matter of repository	The element values permitted by the server is a matter of repository
	policy, but MUST include as a minimum the following values:	policy, but MUST include as a minimum the following values:


	o "create" indicating a <domain:create> command;	o "create" indicating a <create> command;

	o "renew" indicating a <domain:renew> command;


	o "transfer" indicating a <domain:transfer> command;	o "renew" indicating a <renew> command;


		o "transfer" indicating a <transfer> command;
	If the server supports the Registry Grace Period Mapping [RFC3915],	If the server supports the Registry Grace Period Mapping [RFC3915],
	then the server MUST also support the "restore" value.	then the server MUST also support the "restore" value.

	The <fee:command> element MAY have an OPTIONAL "phase" attribute	The <fee:command> element MAY have an OPTIONAL "phase" attribute
	specifying a launch phase as described in	specifying a launch phase as described in
	[draft-ietf-eppext-launchphase]. It may also contain an OPTIONAL	[draft-ietf-eppext-launchphase]. It may also contain an OPTIONAL
	"subphase" attribute identifying the custom or sub-phase as described	"subphase" attribute identifying the custom or sub-phase as described
	in [draft-ietf-eppext-launchphase].	in [draft-ietf-eppext-launchphase].


	3.2. Currency Codes	3.3. Currency Codes

	The <fee:currency> element is used to indicate which currency fees	The <fee:currency> element is used to indicate which currency fees
	are charged in. This value of this element MUST be a three-character	are charged in. This value of this element MUST be a three-character
	currency code from [ISO4217].	currency code from [ISO4217].

	Note that ISO 4217 provides the special "XXX" code, which MAY be used	Note that ISO 4217 provides the special "XXX" code, which MAY be used
	if the server uses a non-currency based system for assessing fees,	if the server uses a non-currency based system for assessing fees,
	such as a system of credits.	such as a system of credits.

	The use of <fee:currency> elements in commands is OPTIONAL: if a	The use of <fee:currency> elements in commands is OPTIONAL: if a
	<fee:currency> element is not present in a command, the server MUST	<fee:currency> element is not present in a command, the server MUST
	determine the currency based on the client's account settings which	determine the currency based on the client's account settings which
	MUST be agreed by the client and server via an out-of-band channel.	MUST be agreed by the client and server via an out-of-band channel.

	However, <fee:currency> element MUST be present in responses.	However, the <fee:currency> element MUST be present in responses.

	Servers SHOULD NOT perform a currency conversion if a client uses an	Servers SHOULD NOT perform a currency conversion if a client uses an
	incorrect currency code. Servers SHOULD return a 2004 error instead.	incorrect currency code. Servers SHOULD return a 2004 error instead.


	3.3. Validity Periods	3.4. Validity Periods


	When querying for fee information using the <check> or <info>	When querying for fee information using the <check> command, the
	commands, the <fee:period> element is used to indicate the units to	<fee:period> element is used to indicate the units to be added to the
	be added to the registration period of domain names by the <create>,	registration period of objects by the <create>, <renew> and
	<renew> and <transfer> commands. This element is derived from the	<transfer> commands. This element is derived from the
	<domain:period> element described in [RFC5731].	<domain:period> element described in [RFC5731].


	The <fee:period> element is OPTIONAL in <check> and <info> commands:	The <fee:period> element is OPTIONAL in <check> commands: if omitted,
	if omitted, the server MUST determine the fee(s) using a validity	the server MUST determine the fee(s) using a validity period of 1
	period of 1 year. The <fee:period> element MUST be present in	year. The <fee:period> element MUST be present in <check> responses.
	<check> and <info> responses.


	3.4. Fees and Credits	3.5. Fees and Credits

	Servers which implement this extension will include elements in	Servers which implement this extension will include elements in
	responses which provide information about the fees and/or credits	responses which provide information about the fees and/or credits
	associated with a given billable transaction.	associated with a given billable transaction.

	The <fee:fee> and <fee:credit> elements are used to provide this	The <fee:fee> and <fee:credit> elements are used to provide this
	information. The presence of a <fee:fee> element in a response	information. The presence of a <fee:fee> element in a response

	indicates a debit against the client's account balance; a <fee:	indicates a debit against the client's account balance; a
	credit> element indicates a credit. A <fee:fee> element MUST have a	<fee:credit> element indicates a credit. A <fee:fee> element MUST
	non-negative value. A <fee:credit> element MUST have a negative	have a non-negative value. A <fee:credit> element MUST have a
	value.	negative value.

	A server MAY respond with multiple <fee:fee> and <fee:credit>	A server MAY respond with multiple <fee:fee> and <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 amount	each of the <fee:fee> and/or <fee:credit> elements. This amount

	applies to the total additional validity period applied to the domain	applies to the total additional validity period applied to the object
	(where applicable) rather than to any incremental unit.	(where applicable) rather than to any incremental unit.

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

	description: an OPTIONAL attribute which provides a human-readable	description: an OPTIONAL attribute which provides a human-readable

	description of the fee. Servers SHOULD provide documentation on	description of the fee. Servers should provide documentation on
	the possible values of this attribute, and their meanings.	the possible values of this attribute, and their meanings.

	refundable: an OPTIONAL boolean attribute indicating whether the fee	refundable: an OPTIONAL boolean attribute indicating whether the fee

	is refundable if the domain name is deleted.	is refundable if the object is deleted.

	grace-period: an OPTIONAL attribute which provides the time period	grace-period: an OPTIONAL attribute which provides the time period
	during which the fee is refundable.	during which the fee is refundable.

	applied: an OPTIONAL attribute indicating when the fee will be	applied: an OPTIONAL attribute indicating when the fee will be
	deducted from the client's account.	deducted from the client's account.

	The <fee:credit> element can take a "description" attribute as	The <fee:credit> element can take a "description" attribute as
	described above. No other attributes are defined for this element.	described above. No other attributes are defined for this element.


	3.4.1. Refunds	3.5.1. Refunds

	<fee:fee> elements MAY have an OPTIONAL "refundable" attribute which	<fee:fee> elements MAY have an OPTIONAL "refundable" attribute which
	takes a boolean value. Fees may be refunded under certain	takes a boolean value. Fees may be refunded under certain
	circumstances, such as when a domain application is rejected (as	circumstances, such as when a domain application is rejected (as

	described in [draft-ietf-eppext-launchphase]) or when a domain name	described in [draft-ietf-eppext-launchphase]) or when an object is
	is deleted during the relevant Grace Period (see below). If the	deleted during the relevant Grace Period (see below).
	"refundable" attribute is omitted, then the default value of "1"
	should be assumed (i.e. the fee is refundable).


	3.4.2. Grace Periods	If the "refundable" attribute is omitted, then clients SHOULD NOT
		make any assumption about the refundability of the fee.

		3.5.2. Grace Periods

	[RFC3915] describes a system of "grace periods", which are time	[RFC3915] describes a system of "grace periods", which are time

	periods following a billable transaction during which, if a domain	periods following a billable transaction during which, if an object
	name is deleted, the client receives a refund.	is deleted, the client receives a refund.

	The "grace-period" attribute MAY be used to indicate the relevant	The "grace-period" attribute MAY be used to indicate 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, it MUST specify the grace period for all relevant	Period extension, it MUST specify the grace period for all relevant

	transactions. If no "grace-period" attribute value is provided, then	transactions.
	no grace period is applicable.
		If the "grace-period" attribute is omitted, then clients SHOULD NOT
		make any assumption about the grace period of the fee.

		3.5.3. Correlation between Refundability and Grace Periods

	If a <fee:fee> element has a "grace-period" attribute then it MUST	If a <fee:fee> element has a "grace-period" attribute then it MUST
	also be refundable. If the "refundable" attribute of a <fee:fee>	also be refundable. If the "refundable" attribute of a <fee:fee>
	element is false then it MUST NOT have a "grace-period" attribute.	element is false then it MUST NOT have a "grace-period" attribute.


	3.4.3. Applicability	3.5.4. Applicability

	Fees may be applied immediately upon receipt of a command from a	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	the processing of applications at the end of a launch phase) has
	taken place.	taken place.

	The "applied" attribute of the <fee:fee> element allows servers to	The "applied" attribute of the <fee:fee> element allows servers to
	indicate whether a fee will be applied immediately, or whether it	indicate whether a fee will be applied immediately, or whether it
	will be applied at some point in the future. This attribute takes	will be applied at some point in the future. This attribute takes
	two possible values: "immediate" (which is the default) or "delayed".	two possible values: "immediate" (which is the default) or "delayed".


	3.5. Account Balance	3.6. Account Balance

	The <fee:balance> element is an OPTIONAL element which MAY be	The <fee:balance> element is an OPTIONAL element which MAY be
	included in server responses to transform commands. If present, it	included in server responses to transform commands. If present, it
	can be used by the client to determine the remaining credit at the	can be used by the client to determine the remaining credit at the
	server.	server.

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

	this element, it MUST be included in responses to all domain	this element, it MUST be included in responses to all "transform"
	"transform" commands (ie <create>, <renew>, <update>, <delete>,	commands (ie <create>, <renew>, <update>, <delete>, <transfer
	<transfer op="request">).	op="request">).

	The value of the <fee:balance> MAY be negative. A negative balance	The value of the <fee:balance> MAY be negative. A negative balance
	indicates that the server has extended a line of credit to the client	indicates that the server has extended a line of credit to the client
	(see below).	(see below).


	When a server includes a <fee:balance> element in response to	If a server includes a <fee:balance> element in response to transform
	transform commands, the value of the element MUST reflect the	commands, the value of the element MUST reflect the client's account
	client's account balance after any fees or credits associated with	balance after any fees or credits associated with that command have
	that command have been applied.	been applied.


	3.6. Credit Limit	3.7. Credit Limit


	As described above, if a server returns a response containing a <fee:	As described above, if a server returns a response containing a
	balance> with a negative value, then the server has extended a line	<fee:balance> with a negative value, then the server has extended a
	of credit to the client. A server MAY also include a <fee:	line of credit to the client. A server MAY also include a
	creditLimit> element in responses which indicates the maximum credit	<fee:creditLimit> element in responses which indicates the maximum
	available to a client. A server MAY reject certain transactions if	credit available to a client. A server MAY reject certain
	the absolute value of the <fee:balance> is equal to or exceeds the	transactions if the absolute value of the <fee:balance> is equal to
	value of the <fee:creditLimit> element.	or exceeds the value of the <fee:creditLimit> element.

	Whether or not the <fee:creditLimit> is included in responses is a	Whether or not the <fee:creditLimit> is included in responses is a
	matter of server policy. However, if a server chooses to offer	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 MUST be included in responses to all

	domain "transform" commands (ie <create>, <renew>, <update>,	"transform" commands (ie <create>, <renew>, <update>, <delete>,
	<delete>, <transfer op="request">).	<transfer op="request">).


	3.7. Classification of Domain Names	3.8. Classification of Objects


	Domain names may be assigned to a particular class, category, or	Objects may be assigned to a particular class, category, or tier,
	tier, each of which has a particular fee or set of fees associated	each of which has a particular fee or set of fees associated with it.
	with it. The <fee:class> element which appears in <check> and <info>	The <fee:class> element which appears in <check> responses is used to
	responses is used to indicate the classification of a domain name.	indicate the classification of an object.


	If a server makes use of this element, it MUST provide clients with a	If a server makes use of this element, it should provide clients with
	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	channel. Servers MUST NOT use values which do not appear on this
	list.	list.

	Servers which make use of this element MUST use a <fee:class> element	Servers which make use of this element MUST use a <fee:class> element

	with the value "standard" for all domains that are subject to the	with the value "standard" for all objects that are subject to the
	standard or default price.	standard or default fee.

	4. Server Handling of Fee Information	4. Server Handling of Fee Information

	Depending on server policy, a client MAY be required to include the	Depending on server policy, a client MAY 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	commands. Servers must provide clear documentation to clients about
	the circumstances in which this extension must be used.	the circumstances in which this extension must be used.

	If a server receives a command from a client which does not include	If a server receives a command from a client which does not include
	the extension elements required by the server for that command, then	the extension elements required by the server for that command, then
	it MUST respond with a 2003 "Required parameter missing" error.	it MUST respond with a 2003 "Required parameter missing" error.

	If the currency or total fee provided by the client do not agree with	If the currency or total fee provided by the client do not agree with
	the server's own calculation of the fee for that command, then the	the server's own calculation of the fee for that command, then the
	server MUST reject the command with a 2004 "Parameter value range"	server MUST reject the command with a 2004 "Parameter value range"
	error.	error.

	skipping to change at page 9, line 12 ¶	skipping to change at page 9, line 22 ¶
	This extension does not add any elements to the EPP <poll> or <info>	This extension does not add any elements to the EPP <poll> or <info>
	commands or responses.	commands or responses.

	5.1.1. EPP <check> Command	5.1.1. EPP <check> Command

	This extension defines additional elements for the EPP <check>	This extension defines additional elements for the EPP <check>
	command.	command.

	The command MAY contain an <extension> element which MAY contain a	The command MAY contain an <extension> element which MAY contain a
	<fee:check> element. The <fee:check> element MUST contain at least	<fee:check> element. The <fee:check> element MUST contain at least

	one <fee:domain> element, with the following child elements:	one <fee:object> element, which has the following child elements:


	o A <fee:name> element. The domain name need not correspond to a	o A <fee:objID> element. This element contains a string which
	<domain:name> element that appears in the <domain:check> element	identifies the object. The <fee:objID> element has an OPTIONAL
	of the main body of the frame.	"element" attribute which identifies the local name of the object
		attribute which is the unique identifier for the object. The
		default value for this attribute is "name".

	o An OPTIONAL <fee:currency> element;	o An OPTIONAL <fee:currency> element;

	o A <fee:command> element;	o A <fee:command> element;

	o An OPTIONAL <fee:period> element.	o An OPTIONAL <fee:period> element.


		The <fee:object> element has an OPTIONAL "objURI" attribute which is
		used to identify the type of the object. The default value for this
		element is "urn:ietf:params:xml:ns:domain-1.0". The value of this
		attribute MUST match the contents of one of the <objURI> elements
		from the server <greeting>

	Example <check> command:	Example <check> command:

	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.org</domain:name>	C: <domain:name>example.org</domain:name>
	C: </domain:check>	C: </domain:check>
	C: </check>	C: </check>
	C: <extension>	C: <extension>
	C: <fee:check	C: <fee:check

	C: xmlns:fee="urn:ietf:params:xml:ns:fee-0.8">	C: xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	C: <fee:domain>	C: <fee:object
	C: <fee:name>example.com</fee:name>	C: objURI="urn:ietf:params:xml:ns:domain-1.0">
		C: <fee:objID element="name">example.com</fee:objID>
	C: <fee:currency>USD</fee:currency>	C: <fee:currency>USD</fee:currency>
	C: <fee:command phase="sunrise">create</fee:command>	C: <fee:command phase="sunrise">create</fee:command>
	C: <fee:period unit="y">1</fee:period>	C: <fee:period unit="y">1</fee:period>

	C: </fee:domain>	C: </fee:object>
	C: <fee:domain>	C: <fee:object>
	C: <fee:name>example.net</fee:name>	C: <fee:objID>example.net</fee:objID>
	C: <fee:currency>EUR</fee:currency>	C: <fee:currency>EUR</fee:currency>
	C: <fee:command phase="claims" subphase="landrush">	C: <fee:command phase="claims" subphase="landrush">
	C: create</fee:command>	C: create</fee:command>
	C: <fee:period unit="y">2</fee:period>	C: <fee:period unit="y">2</fee:period>

	C: </fee:domain>	C: </fee:object>
	C: <fee:domain>	C: <fee:object>
	C: <fee:name>example.org</fee:name>	C: <fee:objID>example.org</fee:objID>
	C: <fee:currency>EUR</fee:currency>	C: <fee:currency>EUR</fee:currency>
	C: <fee:command>transfer</fee:command>	C: <fee:command>transfer</fee:command>

	C: </fee:domain>	C: </fee:object>
	C: <fee:domain>	C: <fee:object>
	C: <fee:name>example.xyz</fee:name>	C: <fee:objID>example.xyz</fee:objID>
	C: <fee:command>restore</fee:command>	C: <fee:command>restore</fee:command>

	C: </fee:domain>	C: </fee:object>
	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>

	When the server receives a <check> command that includes the	When the server receives a <check> command that includes the
	extension elements described above, its response MUST (subject to the	extension elements described above, its response MUST (subject to the
	exception described below) contain an <extension> element, which MUST	exception described below) contain an <extension> element, which MUST
	contain a child <fee:chkData> element. The <fee:chkData> element	contain a child <fee:chkData> element. The <fee:chkData> element

	MUST contain a <fee:cd> element for each <fee:domain> element	MUST contain a <fee:cd> element for each <fee:object> element
	contained in the command. The <fee:cd> MUST contain the following	contained in the command. The <fee:cd> MUST contain the following
	child elements:	child elements:


	o A <fee:name> element that contains a domain name which matches the	o A <fee:objID> element that contains an identifer which matches the
	name in the corresponding <fee:domain> element.	identifier in the corresponding <fee:object> element.

	o A <fee:currency> element that contains same currency code that	o A <fee:currency> element that contains same currency code that

	appeared in the corresponding <fee:domain> element. If no <fee:	appeared in the corresponding <fee:object> element. If no
	currency> element appeared in the corresponding <fee:domain>	<fee:currency> element appeared in the corresponding <fee:object>
	element, then the client's default billing currency should be	element, then the client's default billing currency should be
	used.	used.

	o A <fee:command> element that contains same command that appeared	o A <fee:command> element that contains same command that appeared

	in the corresponding <fee:domain> element. This element MAY have	in the corresponding <fee:object> element. This element MAY have
	the OPTIONAL "phase" and "subphase" elements, which MUST match the	the OPTIONAL "phase" and "subphase" elements, which MUST match the

	same attributes in the corresponding <fee:domain> element.	same attributes in the corresponding <fee:object> element.

	o An OPTIONAL <fee:period> element that contains same unit that	o An OPTIONAL <fee:period> element that contains same unit that

	appeared in the corresponding <fee:domain> element. If the value	appeared in the corresponding <fee:object> element. If the value
	of the preceding <fee:command> element is "restore", this element	of the preceding <fee:command> element is "restore", this element

	MUST NOT be included. Otherwise it MUST be included. If no <fee:	MUST NOT be included. Otherwise it MUST be included. If no
	period> appeared in the corresponding <fee:domain> element (and	<fee:period> appeared in the corresponding <fee:object> element
	the command is not "restore") then this element MUST have a value	(and the command is not "restore") then this element MUST have a
	of 1 year.	value of 1 year.

	o Zero or more <fee:fee> elements.	o Zero or more <fee:fee> elements.

	o Zero or more <fee:credit> elements.	o Zero or more <fee:credit> elements.

	o An OPTIONAL <fee:class> element.	o An OPTIONAL <fee:class> element.

	If no <fee:fee> elements are present in a <fee:cd> element, this	If no <fee:fee> elements are present in a <fee:cd> element, this
	indicates that the requested command is not permitted by server	indicates that the requested command is not permitted by server
	policy.	policy.

	skipping to change at page 12, line 21 ¶	skipping to change at page 12, line 22 ¶
	S: <domain:reason>In use</domain:reason>	S: <domain:reason>In use</domain:reason>
	S: </domain:cd>	S: </domain:cd>
	S: <domain:cd>	S: <domain:cd>
	S: <domain:name avail="0">example.org</domain:name>	S: <domain:name avail="0">example.org</domain:name>
	S: <domain:reason>In use</domain:reason>	S: <domain:reason>In use</domain:reason>
	S: </domain:cd>	S: </domain:cd>
	S: </domain:chkData>	S: </domain:chkData>
	S: </resData>	S: </resData>
	S: <extension>	S: <extension>
	S: <fee:chkData	S: <fee:chkData

	S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.8">	S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	S: <fee:cd>	S: <fee:cd>

	S: <fee:name>example.com</fee:name>	S: <fee:objID>example.com</fee:objID>
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>
	S: <fee:command phase="sunrise">create</fee:command>	S: <fee:command phase="sunrise">create</fee:command>
	S: <fee:period unit="y">1</fee:period>	S: <fee:period unit="y">1</fee:period>
	S: <fee:fee description="Application Fee"	S: <fee:fee description="Application Fee"
	S: refundable="0">5.00</fee:fee>	S: refundable="0">5.00</fee:fee>
	S: <fee:fee description="Registration Fee"	S: <fee:fee description="Registration 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:cd>	S: </fee:cd>
	S: <fee:cd>	S: <fee:cd>

	S: <fee:name>example.net</fee:name>	S: <fee:objID>example.net</fee:objID>
	S: <fee:currency>EUR</fee:currency>	S: <fee:currency>EUR</fee:currency>
	S: <fee:command phase="claims" subphase="landrush">	S: <fee:command phase="claims" subphase="landrush">
	S: create</fee:command>	S: create</fee:command>
	S: <fee:period unit="y">2</fee:period>	S: <fee:period unit="y">2</fee:period>
	S: <fee:fee>5.00</fee:fee>	S: <fee:fee>5.00</fee:fee>
	S: </fee:cd>	S: </fee:cd>
	S: <fee:cd>	S: <fee:cd>

	S: <fee:name>example.org</fee:name>	S: <fee:objID>example.org</fee:objID>
	S: <fee:currency>EUR</fee:currency>	S: <fee:currency>EUR</fee:currency>
	S: <fee:command>transfer</fee:command>	S: <fee:command>transfer</fee:command>
	S: <fee:period unit="y">2</fee:period>	S: <fee:period unit="y">2</fee:period>
	S: <fee:fee description="Transfer Fee"	S: <fee:fee description="Transfer Fee"
	S: refundable="0">2.50</fee:fee>	S: refundable="0">2.50</fee:fee>
	S: <fee:fee description="Renewal Fee"	S: <fee:fee description="Renewal Fee"
	S: refundable="1"	S: refundable="1"

	S: grace-period="P5D">10.00</fee:fee>	S: grace-period="P5D">10.00</fee:fee>
	S: </fee:cd>	S: </fee:cd>
	S: <fee:cd>	S: <fee:cd>

	S: <fee:name>example.xyz</fee:name>	S: <fee:objID>example.xyz</fee:objID>
	S: <fee:currency>GBP</fee:currency>	S: <fee:currency>GBP</fee:currency>
	S: <fee:command>restore</fee:command>	S: <fee:command>restore</fee:command>
	S: <fee:fee description="Restore Fee"	S: <fee:fee description="Restore Fee"
	S: refundable="0">25</fee:fee>	S: refundable="0">25</fee:fee>
	S: <fee:class>premium-tier1</fee:class>	S: <fee:class>premium-tier1</fee:class>
	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>

	skipping to change at page 14, line 24 ¶	skipping to change at page 14, line 24 ¶
	S: <domain:name>example.com</domain:name>	S: <domain:name>example.com</domain:name>
	S: <domain:trStatus>pending</domain:trStatus>	S: <domain:trStatus>pending</domain:trStatus>
	S: <domain:reID>ClientX</domain:reID>	S: <domain:reID>ClientX</domain:reID>
	S: <domain:reDate>2000-06-08T22:00:00.0Z</domain:reDate>	S: <domain:reDate>2000-06-08T22:00:00.0Z</domain:reDate>
	S: <domain:acID>ClientY</domain:acID>	S: <domain:acID>ClientY</domain:acID>
	S: <domain:acDate>2000-06-13T22:00:00.0Z</domain:acDate>	S: <domain:acDate>2000-06-13T22:00:00.0Z</domain:acDate>
	S: <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate>	S: <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate>
	S: </domain:trnData>	S: </domain:trnData>
	S: </resData>	S: </resData>
	S: <extension>	S: <extension>

	S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.8">	S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	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>

	skipping to change at page 16, line 26 ¶	skipping to change at page 16, line 26 ¶
	C: </domain:ns>	C: </domain:ns>
	C: <domain:registrant>jd1234</domain:registrant>	C: <domain:registrant>jd1234</domain:registrant>
	C: <domain:contact type="admin">sh8013</domain:contact>	C: <domain:contact type="admin">sh8013</domain:contact>
	C: <domain:contact type="tech">sh8013</domain:contact>	C: <domain:contact type="tech">sh8013</domain:contact>
	C: <domain:authInfo>	C: <domain:authInfo>
	C: <domain:pw>2fooBAR</domain:pw>	C: <domain:pw>2fooBAR</domain:pw>
	C: </domain:authInfo>	C: </domain:authInfo>
	C: </domain:create>	C: </domain:create>
	C: </create>	C: </create>
	C: <extension>	C: <extension>

	C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.8">	C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	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>

	Example <create> response:	Example <create> response:


	skipping to change at page 17, line 20 ¶	skipping to change at page 17, line 20 ¶
	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>
	S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>	S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
	S: <domain:exDate>2001-04-03T22:00:00.0Z</domain:exDate>	S: <domain:exDate>2001-04-03T22:00:00.0Z</domain:exDate>
	S: </domain:creData>	S: </domain:creData>
	S: </resData>	S: </resData>
	S: <extension>	S: <extension>

	S: <fee:creData xmlns:fee="urn:ietf:params:xml:ns:fee-0.8">	S: <fee:creData xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>
	S: <fee:fee grace-period="P5D">5.00</fee:fee>	S: <fee:fee 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>

	skipping to change at page 17, line 42 ¶	skipping to change at page 17, line 42 ¶
	S: </epp>	S: </epp>

	5.2.2. EPP <delete> Command	5.2.2. EPP <delete> Command

	This extension does not add any elements to the EPP <delete> command,	This extension does not add any elements to the EPP <delete> command,
	but does include elements in the response, when the extension has	but does include elements in the response, when the extension has
	been selected during the <login> command.	been selected during the <login> command.

	When the <delete> command has been processed successfully, and the	When the <delete> command has been processed successfully, and the
	client selected the extension when it logged in, the server MAY	client selected the extension when it logged in, the server MAY

	include in the <extension> section of the EPP response a <fee:	include in the <extension> section of the EPP response a
	delData> element that contains the following child elements:	<fee:delData> element that contains the following child elements:

	o A <fee:currency> element;	o A <fee:currency> element;

	o Zero or more <fee:credit> elements;	o Zero or more <fee:credit> elements;

	o An OPTIONAL <fee:balance> element;	o An OPTIONAL <fee:balance> element;

	o An OPTIONAL <fee:creditLimit> element.	o An OPTIONAL <fee:creditLimit> element.

	If no credit has been assessed by the server for this transaction, a	If no credit has been assessed by the server for this transaction, a

	skipping to change at page 18, line 18 ¶	skipping to change at page 18, line 18 ¶
	Example <delete> response:	Example <delete> response:

	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:fee-0.8">	S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>
	S: <fee:credit description="AGP Credit">-5.00</fee:credit>	S: <fee:credit description="AGP Credit">-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>

	skipping to change at page 18, line 47 ¶	skipping to change at page 18, line 47 ¶
	When submitting a <renew> command to the server, the client MAY	When submitting a <renew> command to the server, the client MAY
	include in the <extension> element a <fee:renew> element which	include in the <extension> element a <fee:renew> element which
	includes the following child elements:	includes the following child elements:

	o An OPTIONAL <fee:currency> element;	o An OPTIONAL <fee:currency> element;

	o One or more <fee:fee> elements.	o One or more <fee:fee> elements.

	When the <renew> command has been processed successfully, and the	When the <renew> command has been processed successfully, and the
	client selected the extension when it logged in, the server MAY	client selected the extension when it logged in, the server MAY

	include in the <extension> section of the EPP response a <fee:	include in the <extension> section of the EPP response a
	renData> element that contains the following child elements:	<fee:renData> element that contains the following child elements:

	o A <fee:currency> element;	o A <fee:currency> element;

	o Zero or more <fee:fee> elements;


		o Zero or more <fee:fee> elements;
	o Zero or more <fee:credit> elements;	o Zero or more <fee:credit> elements;

	o An OPTIONAL <fee:balance> element;	o An OPTIONAL <fee:balance> element;

	o An OPTIONAL <fee:creditLimit> element.	o An OPTIONAL <fee:creditLimit> element.

	If no fee or credit has been assessed by the server for this	If no fee or credit has been assessed by the server for this
	transaction, a <fee:renData> element MUST NOT be included in the	transaction, a <fee:renData> element MUST NOT be included in the
	response.	response.


	skipping to change at page 19, line 30 ¶	skipping to change at page 19, line 28 ¶
	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>2000-04-03</domain:curExpDate>	C: <domain:curExpDate>2000-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:fee-0.8">	C: <fee:renew xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	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>

	Example <renew> response:	Example <renew> response:


	skipping to change at page 20, line 19 ¶	skipping to change at page 20, line 19 ¶
	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>
	S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>	S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
	S: </domain:renData>	S: </domain:renData>
	S: </resData>	S: </resData>
	S: <extension>	S: <extension>

	S: <fee:renData xmlns:fee="urn:ietf:params:xml:ns:fee-0.8">	S: <fee:renData xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>
	S: <fee:fee grace-period="P5D">5.00</fee:fee>	S: <fee:fee 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>

	skipping to change at page 20, line 49 ¶	skipping to change at page 20, line 49 ¶
	When submitting a <transfer> command to the server, the client MAY	When submitting a <transfer> command to the server, the client MAY
	include in the <extension> element a <fee:transfer> element which	include in the <extension> element a <fee:transfer> element which
	includes the following child elements:	includes the following child elements:

	o An OPTIONAL <fee:currency> element;	o An OPTIONAL <fee:currency> element;

	o One or more <fee:fee> elements.	o One or more <fee:fee> elements.

	When the <transfer> command has been processed successfully, and the	When the <transfer> command has been processed successfully, and the
	client selected the extension when it logged in, the server MAY	client selected the extension when it logged in, the server MAY

	include in the <extension> section of the EPP response a <fee:	include in the <extension> section of the EPP response a
	trnData> element that contains the following child elements:	<fee:trnData> element that contains the following child elements:

	o A <fee:currency> element;	o A <fee:currency> element;


	o Zero or more <fee:fee> elements;	o Zero or more <fee:fee> elements;

	o Zero or more <fee:credit> elements;	o Zero or more <fee:credit> elements;

	o An OPTIONAL <fee:balance> element;	o An OPTIONAL <fee:balance> element;

	o An OPTIONAL <fee:creditLimit> element.	o An OPTIONAL <fee:creditLimit> element.

	If no fee or credit has been assessed by the server for this	If no fee or credit has been assessed by the server for this
	transaction, a <fee:trnData> element MUST NOT be included in the	transaction, a <fee:trnData> element MUST NOT be included in the

	skipping to change at page 21, line 35 ¶	skipping to change at page 21, line 32 ¶
	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:fee-0.8">	C: <fee:transfer xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	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>

	Example <transfer> response:	Example <transfer> response:


	skipping to change at page 22, line 24 ¶	skipping to change at page 22, line 24 ¶
	S: <domain:name>example.com</domain:name>	S: <domain:name>example.com</domain:name>
	S: <domain:trStatus>pending</domain:trStatus>	S: <domain:trStatus>pending</domain:trStatus>
	S: <domain:reID>ClientX</domain:reID>	S: <domain:reID>ClientX</domain:reID>
	S: <domain:reDate>2000-06-08T22:00:00.0Z</domain:reDate>	S: <domain:reDate>2000-06-08T22:00:00.0Z</domain:reDate>
	S: <domain:acID>ClientY</domain:acID>	S: <domain:acID>ClientY</domain:acID>
	S: <domain:acDate>2000-06-13T22:00:00.0Z</domain:acDate>	S: <domain:acDate>2000-06-13T22:00:00.0Z</domain:acDate>
	S: <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate>	S: <domain:exDate>2002-09-08T22:00:00.0Z</domain:exDate>
	S: </domain:trnData>	S: </domain:trnData>
	S: </resData>	S: </resData>
	S: <extension>	S: <extension>

	S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.8">	S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	S: <fee:currency>USD</fee:currency>	S: <fee:currency>USD</fee:currency>
	S: <fee:fee grace-period="P5D">5.00</fee:fee>	S: <fee:fee 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>

	skipping to change at page 23, line 35 ¶	skipping to change at page 23, line 36 ¶
	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:fee-0.8">	C: <fee:update xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	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>

	Example <update> response:	Example <update> response:

	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:fee-0.8">	S: <fee:updData xmlns:fee="urn:ietf:params:xml:ns:fee-0.9">
	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>

	skipping to change at page 25, line 17 ¶	skipping to change at page 25, line 17 ¶
	SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT	SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
	LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,	LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
	DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY	DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
	THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT	THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
	(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE	(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
	OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.	OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

	BEGIN	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:fee-0.8"	xmlns:fee="urn:ietf:params:xml:ns:fee-0.9"
	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:fee-0.8"	targetNamespace="urn:ietf:params:xml:ns:fee-0.9"
	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" />

	<annotation>	<annotation>
	<documentation>Extensible Provisioning Protocol	<documentation>Extensible Provisioning Protocol

	v1.0 domain name extension schema for	v1.0 extension schema for fee
	fee information.</documentation>	information.</documentation>
	</annotation>	</annotation>

	<!--	<!--
	Child elements found in EPP commands and responses	Child elements found in EPP commands and responses
	-->	-->
	<element name="check" type="fee:checkType" />	<element name="check" type="fee:checkType" />
	<element name="chkData" type="fee:chkDataType" />	<element name="chkData" type="fee:chkDataType" />
	<element name="create" type="fee:transformCommandType" />	<element name="create" type="fee:transformCommandType" />
	<element name="creData" type="fee:transformResultType" />	<element name="creData" type="fee:transformResultType" />
	<element name="renew" type="fee:transformCommandType" />	<element name="renew" type="fee:transformCommandType" />

	skipping to change at page 26, line 4 ¶	skipping to change at page 26, line 4 ¶
	<element name="trnData" type="fee:transferResultType" />	<element name="trnData" type="fee:transferResultType" />
	<element name="update" type="fee:transformCommandType" />	<element name="update" type="fee:transformCommandType" />
	<element name="updData" type="fee:transformResultType" />	<element name="updData" type="fee:transformResultType" />
	<element name="delData" type="fee:deleteDataType" />	<element name="delData" type="fee:deleteDataType" />

	<!--	<!--
	client <check> command	client <check> command
	-->	-->
	<complexType name="checkType">	<complexType name="checkType">
	<sequence>	<sequence>

	<element name="domain" type="fee:domainCheckType"	<element name="object" type="fee:objectCheckType"
	maxOccurs="unbounded" />	maxOccurs="unbounded" />
	</sequence>	</sequence>
	</complexType>	</complexType>


	<complexType name="domainCheckType">	<complexType name="objectCheckType">
	<sequence>	<sequence>

	<element name="name" type="eppcom:labelType" />	<element name="objID" type="fee:objectIdentifierType" />
	<element name="currency" type="fee:currencyType"	<element name="currency" type="fee:currencyType"
	minOccurs="0" />	minOccurs="0" />
	<element name="command" type="fee:commandType" />	<element name="command" type="fee:commandType" />
	<element name="period" type="domain:periodType"	<element name="period" type="domain:periodType"
	minOccurs="0" />	minOccurs="0" />
	</sequence>	</sequence>

		<attribute name="objURI" type="anyURI"
		default="urn:ietf:params:xml:ns:domain-1.0" />
		</complexType>

		<complexType name="objectIdentifierType">
		<simpleContent>
		<extension base="eppcom:labelType">
		<attribute name="element"
		type="NMTOKEN" default="name" />
		</extension>
		</simpleContent>
	</complexType>	</complexType>

	<!--	<!--
	server <check> result	server <check> result
	-->	-->
	<complexType name="chkDataType">	<complexType name="chkDataType">
	<sequence>	<sequence>

	<element name="cd" type="fee:domainCDType"	<element name="cd" type="fee:objectCDType"
	maxOccurs="unbounded" />	maxOccurs="unbounded" />
	</sequence>	</sequence>
	</complexType>	</complexType>


	<complexType name="domainCDType">	<complexType name="objectCDType">
	<sequence>	<sequence>

	<element name="name" type="eppcom:labelType" />	<element name="objID" type="fee:objectIdentifierType" />
	<element name="currency" type="fee:currencyType" />	<element name="currency" type="fee:currencyType" />
	<element name="command" type="fee:commandType" />	<element name="command" type="fee:commandType" />
	<element name="period" type="domain:periodType"	<element name="period" type="domain:periodType"
	minOccurs="0" maxOccurs="1" />	minOccurs="0" maxOccurs="1" />
	<element name="fee" type="fee:feeType"	<element name="fee" type="fee:feeType"
	minOccurs="0" maxOccurs="unbounded" />	minOccurs="0" maxOccurs="unbounded" />
	<element name="credit" type="fee:creditType"	<element name="credit" type="fee:creditType"
	minOccurs="0" maxOccurs="unbounded" />	minOccurs="0" maxOccurs="unbounded" />


	<element name="class" type="token" minOccurs="0" />	<element name="class" type="token" minOccurs="0" />
	</sequence>	</sequence>

		<attribute name="objURI" type="anyURI"
		default="urn:ietf:params:xml:ns:domain-1.0" />
	</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"

	skipping to change at page 29, line 7 ¶	skipping to change at page 29, line 19 ¶
	<simpleType name="negativeDecimal">	<simpleType name="negativeDecimal">
	<restriction base="decimal">	<restriction base="decimal">
	<maxInclusive value="0" />	<maxInclusive value="0" />
	</restriction>	</restriction>
	</simpleType>	</simpleType>

	<complexType name="feeType">	<complexType name="feeType">
	<simpleContent>	<simpleContent>
	<extension base="fee:nonNegativeDecimal">	<extension base="fee:nonNegativeDecimal">
	<attribute name="description"/>	<attribute name="description"/>

	<attribute name="refundable" type="boolean"	<attribute name="refundable" type="boolean" />
	default="1" />
	<attribute name="grace-period" type="duration" />	<attribute name="grace-period" type="duration" />
	<attribute name="applied" default="immediate">	<attribute name="applied" default="immediate">
	<simpleType>	<simpleType>
	<restriction base="token">	<restriction base="token">
	<enumeration value="immediate" />	<enumeration value="immediate" />
	<enumeration value="delayed" />	<enumeration value="delayed" />
	</restriction>	</restriction>
	</simpleType>	</simpleType>
	</attribute>	</attribute>
	</extension>	</extension>

	skipping to change at page 30, line 13 ¶	skipping to change at page 30, line 21 ¶
	to this specification as well.	to this specification as well.

	7. IANA Considerations	7. IANA Considerations

	7.1. XML Namespace	7.1. XML Namespace

	This document uses URNs to describe XML namespaces and XML schemas	This document uses URNs to describe XML namespaces and XML schemas
	conforming to a registry mechanism described in [RFC3688]. The	conforming to a registry mechanism described in [RFC3688]. The
	following URI assignment is requested of IANA:	following URI assignment is requested of IANA:


	URI: urn:ietf:params:xml:ns:fee-0.8	URI: urn:ietf:params:xml:ns:fee-0.9

	Registrant Contact: See the "Author's Address" section of this	Registrant Contact: See the "Author's Address" section of this
	document.	document.

	XML: See the "Formal Syntax" section of this document.	XML: See the "Formal Syntax" section of this document.

	7.2. EPP Extension Registry	7.2. EPP Extension Registry

	The EPP extension described in this document should be registered by	The EPP extension described in this document should be registered by
	the IANA in the EPP Extension Registry described in [RFC7451]. The	the IANA in the EPP Extension Registry described in [RFC7451]. The

	skipping to change at page 31, line 43 ¶	skipping to change at page 32, line 7 ¶
	Coverage: All aspects of the protocol are implemented.	Coverage: All aspects of the protocol are implemented.

	Licensing: Proprietary In-House software	Licensing: Proprietary In-House software

	Contact: epp@centralnic.com	Contact: epp@centralnic.com

	URL: https://www.centralnic.com	URL: https://www.centralnic.com

	9. Acknowledgements	9. Acknowledgements


	The author wishes to thank the following persons for their feedback	The authors wish to thank the following persons for their feedback
	and suggestions:	and suggestions:

	o James Gould of Verisign	o James Gould of Verisign

	o Luis Munoz of ISC	o Luis Munoz of ISC


	o Michael Young of Architelos	o Michael Young of Architelos

	o Ben Levac and Jeff Eckhaus of Demand Media	o Ben Levac and Jeff Eckhaus of Demand Media

	o Seth Goldman of Google	o Seth Goldman of Google

	o Klaus Malorny and Michael Bauland of Knipp	o Klaus Malorny and Michael Bauland of Knipp

	o Jody Kolker and Roger Carney of Go Daddy	o Jody Kolker and Roger Carney of Go Daddy

	o Michael Holloway of Com Laude	o Michael Holloway of Com Laude

	o Santosh Kalsangrah of Impetus Infotech	o Santosh Kalsangrah of Impetus Infotech


		o Alex Mayrhofer of Nic.at

	10. Change History	10. Change History

	10.1. Changes from 00 to 01	10.1. Changes from 00 to 01

	1. Restore the <check> command extension; either <check> or <info>	1. Restore the <check> command extension; either <check> or <info>
	can be used.	can be used.

	2. added extension elements for <create>, <renew>, <transfer> and	2. added extension elements for <create>, <renew>, <transfer> and
	<update> so that the server can reject the command if the fee is	<update> so that the server can reject the command if the fee is
	incorrect.	incorrect.

	skipping to change at page 34, line 30 ¶	skipping to change at page 34, line 38 ¶
	responses to be zero.	responses to be zero.

	6. Removed the <fee:balance> and <fee:creditLimit> elements from	6. Removed the <fee:balance> and <fee:creditLimit> elements from
	transfer query responses. The reason is that these elements are	transfer query responses. The reason is that these elements are
	defined as containing the values after the transform command has	defined as containing the values after the transform command has
	taken place - which means that it is not appropriate to include	taken place - which means that it is not appropriate to include
	them in a query response.	them in a query response.

	7. Added Implementation Status section.	7. Added Implementation Status section.


	11. TODO	10.6. Changes from 05 to 06


	(Note to RFC Editor: remove this section before publication as an	1. The specification is now object-agnostic, but works with RFC5731
	RFC.)	[RFC5731] domains by default.


	1. Make the extension object-agnostic so it can be used with other	2. Renamed the <fee:domain> element to <fee:object>. Added the
	objects, not just vanilla domains.	"objURI" attribute.


	12. Normative References	3. Removed the default value for the "refundable" attribute of
		<fee:fee> elements, and added text about how clients should
		handle such cases. Added similar text to the documentation of
		the "grace-period" attribute.


	[ISO4217] International Organization for Standardization, "ISO 4217:	4. Removed references to the defunct <info> command syntax.
	2008, Codes for the representation of currencies and
		5. "MUST" requirements regarding documentatio have been changed to
		"must".

		6. Created separate "Correlation between Refundability and Grace
		Periods" section describing how the "refundable" and "grace-
		period" attributes work together.

		11. Normative References

		[draft-ietf-eppext-launchphase]
		Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping
		for the Extensible Provisioning Protocol (EPP)", 2014.

		[ISO4217] International Organization for Standardization, "ISO
		4217:2008, Codes for the representation of currencies and
	funds", 2008.	funds", 2008.

	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/	Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
	RFC2119, March 1997,	RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.	<http://www.rfc-editor.org/info/rfc2119>.

	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	DOI 10.17487/RFC3688, January 2004,	DOI 10.17487/RFC3688, January 2004,
	<http://www.rfc-editor.org/info/rfc3688>.	<http://www.rfc-editor.org/info/rfc3688>.

	[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for	[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for

	the Extensible Provisioning Protocol (EPP)", RFC 3915,	the Extensible Provisioning Protocol (EPP)", RFC 3915, DOI
	DOI 10.17487/RFC3915, September 2004,	10.17487/RFC3915, September 2004,
	<http://www.rfc-editor.org/info/rfc3915>.	<http://www.rfc-editor.org/info/rfc3915>.

	[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",	[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
	STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,	STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
	<http://www.rfc-editor.org/info/rfc5730>.	<http://www.rfc-editor.org/info/rfc5730>.

	[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)	[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
	Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/	Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/
	RFC5731, August 2009,	RFC5731, August 2009,
	<http://www.rfc-editor.org/info/rfc5731>.	<http://www.rfc-editor.org/info/rfc5731>.

	[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running	[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running

	Code: The Implementation Status Section", RFC 6982,	Code: The Implementation Status Section", RFC 6982, DOI
	DOI 10.17487/RFC6982, July 2013,	10.17487/RFC6982, July 2013,
	<http://www.rfc-editor.org/info/rfc6982>.	<http://www.rfc-editor.org/info/rfc6982>.

	[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible	[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
	Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,	Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
	February 2015, <http://www.rfc-editor.org/info/rfc7451>.	February 2015, <http://www.rfc-editor.org/info/rfc7451>.


	[draft-ietf-eppext-launchphase]	Authors' Addresses
	Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping
	for the Extensible Provisioning Protocol (EPP)", 2014.

	Author's Address

	Gavin Brown	Gavin Brown
	CentralNic Group plc	CentralNic Group plc
	35-39 Moorgate	35-39 Moorgate
	London, England EC2R 6AR	London, England EC2R 6AR
	GB	GB

	Phone: +44 20 33 88 0600	Phone: +44 20 33 88 0600
	Email: gavin.brown@centralnic.com	Email: gavin.brown@centralnic.com
	URI: https://www.centralnic.com	URI: https://www.centralnic.com


		Jothan Frakes

		Email: jothan@jothan.com
		URI: http://jothan.com

End of changes. 103 change blocks.
	203 lines changed or deleted	253 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/