draft-ietf-regext-epp-fees-00.txt   draft-ietf-regext-epp-fees-01.txt 
Internet Engineering Task Force G. Brown Registration Protocols Extensions R. Carney
Internet-Draft CentralNic Group plc Internet-Draft GoDaddy Inc.
Intended status: Standards Track J. Frakes Intended status: Standards Track G. Brown
Expires: December 30, 2016 June 28, 2016 Expires: September 4, 2017 CentralNic Group plc
J. Frakes
March 3, 2017
Registry Fee Extension for the Extensible Provisioning Protocol (EPP) Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-fees-00 draft-ietf-regext-epp-fees-01
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 December 30, 2016. This Internet-Draft will expire on September 4, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 4 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Migrating to Newer Versions of This Extension . . . . . . . . 5 2. Migrating to Newer Versions of This Extension . . . . . . . . 4
3. Extension Elements . . . . . . . . . . . . . . . . . . . . . . 5 3. Extension Elements . . . . . . . . . . . . . . . . . . . . . 4
3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 5 3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 4
3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . 5
3.3. Validity Periods . . . . . . . . . . . . . . . . . . . . . 6 3.3. Validity Periods . . . . . . . . . . . . . . . . . . . . 5
3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . . 6 3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . 5
3.4.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 7 3.4.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 6
3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 7 3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 6
3.4.3. Correlation between Refundability and Grace Periods . 8 3.4.3. Correlation between Refundability and Grace Periods . 7
3.4.4. Applicability . . . . . . . . . . . . . . . . . . . . 8 3.4.4. Applicability . . . . . . . . . . . . . . . . . . . . 7
3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 8 3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 7
3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . . 8 3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . 7
3.7. Classification of Objects . . . . . . . . . . . . . . . . 9 3.7. Classification of Objects . . . . . . . . . . . . . . . . 8
4. Server Handling of Fee Information . . . . . . . . . . . . . . 9 3.8. Phase and Subphase Attributes . . . . . . . . . . . . . . 8
5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 9 4. Server Handling of Fee Information . . . . . . . . . . . . . 9
5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 10 5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 9
5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 10 5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 9
5.1.1.1. Server Handling of <fee:class> Elements . . . . . 13 5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9
5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . . 14 5.1.1.1. Server Handling of Elements . . . . . . . . . . . 14
5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 15 5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 15
5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 15 5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16
5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 18 5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16
5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 19 5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19
5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 21 5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20
5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 23 5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 22
5.3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . 25 5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 26
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 26
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 31 7. Security Considerations . . . . . . . . . . . . . . . . . . . 30
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . . 31 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 31 8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 31
8.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . . 32 8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 31
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32 9. Implemntation Status . . . . . . . . . . . . . . . . . . . . 31
10. Change History . . . . . . . . . . . . . . . . . . . . . . . . 33 9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 32
10.1. Changes from 00 to 01 . . . . . . . . . . . . . . . . . . 33 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
10.2. Changes from 01 to 02 . . . . . . . . . . . . . . . . . . 33 11. Change History . . . . . . . . . . . . . . . . . . . . . . . 33
10.3. Changes from 02 to 03 . . . . . . . . . . . . . . . . . . 34 11.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 33
10.4. Changes from 03 to 04 . . . . . . . . . . . . . . . . . . 34 11.2. Change from draft-brown-00 to draft-ietf-regext-fees-00 33
10.5. Changes from 04 to 05 . . . . . . . . . . . . . . . . . . 35 12. Normative References . . . . . . . . . . . . . . . . . . . . 33
10.6. Changes from 05 to 06 . . . . . . . . . . . . . . . . . . 35 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
10.7. Changes from 06 to 07 . . . . . . . . . . . . . . . . . . 36
10.8. Changes from draft-brown-epp-fees-00 to
draft-ietf-regext-epp-fees-00 . . . . . . . . . . . . . . 36
11. Normative References . . . . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37
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 4, 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.11". The XML namespace prefix "fee" is 0.13". 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.
In examples, "C:" represents lines sent by a protocol client and "S:"
represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element
relationships and are not a REQUIRED feature of this protocol.
(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.11". This version number will increment with specifically "0.1". 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 5, line 36 skipping to change at page 4, line 38
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. Client Commands
The <fee:command> element is used in the EPP <check> command to The <fee:command> element is used in the EPP <check> command to
determine the fee which is applicable to the given command. determine the fee which is applicable to the given command.
The element values permitted by the server is a matter of repository The list of values include:
policy, but MUST include as a minimum the following values:
o "create" indicating a <create> command;
o "renew" indicating a <renew> command;
o "transfer" indicating a <transfer> command;
If the server supports the Registry Grace Period Mapping [RFC3915], o "create" indicating a <create> command as defined in [RFC5730];
then the server MUST also support the "restore" value. o "delete" indicating a <delete> command as defined in [RFC5730];
o "renew" indicating a <renew> command as defined in [RFC5730];
o "update" indicating a <update> command as defined in [RFC5730];
o "transfer" indicating a <transfer> command as defined in
[RFC5730];
o If the server supports the Registry Grace Period Mapping
[RFC3915], then the server MUST also support the "restore" value
as defined in [RFC3915].
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-
[draft-ietf-eppext-launchphase]. It may also contain an OPTIONAL launchphase]. It may also contain an OPTIONAL "subphase" attribute
"subphase" attribute identifying the custom or sub-phase as described identifying the custom or sub-phase as described in [draft-ietf-
in [draft-ietf-eppext-launchphase]. eppext-launchphase].
3.2. Currency Codes 3.2. 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, the <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 "Parameter
value range" error instead.
3.3. Validity Periods 3.3. Validity Periods
When querying for fee information using the <check> command, the When querying for fee information using the <check> command, the
<fee:period> element is used to indicate the units to be added to the <fee:period> element is used to indicate the units to be added to the
registration period of objects by the <create>, <renew> and registration period of objects by the <create>, <renew> and
<transfer> commands. This element is derived from the <domain: <transfer> commands. This element is derived from the
period> element described in [RFC5731]. <domain:period> element described in [RFC5731].
The <fee:period> element is OPTIONAL in <check> commands: if omitted, The <fee:period> element is OPTIONAL in <check> commands: if omitted,
the server MUST determine the fee(s) using a validity period of 1 the server MUST determine the fee(s) using a validity period of 1
year. The <fee:period> element MUST be present in <check> responses. year. The <fee:period> element MUST be present in <check> responses.
3.4. Fees and Credits 3.4. 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 object 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
the possible values of this attribute, and their meanings. 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 object 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.4.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 an object is described in [draft-ietf-eppext-launchphase]) or when an object is
skipping to change at page 8, line 21 skipping to change at page 7, line 24
3.4.4. Applicability 3.4.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" or "delayed".
3.5. Account Balance 3.5. 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 "transform" this element, it MUST be included in responses to all "transform" or
commands (ie <create>, <renew>, <update>, <delete>, <transfer billable commands (ie <create>, <renew>, <update>, <delete>,
op="request">). <transfer 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).
If a server includes a <fee:balance> element in response to transform If a server includes a <fee:balance> element in response to transform
commands, the value of the element MUST reflect the client's account commands, the value of the element MUST reflect the client's account
balance after any fees or credits associated with that command have balance after any fees or credits associated with that command have
been applied. been applied.
3.6. Credit Limit 3.6. 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
"transform" commands (ie <create>, <renew>, <update>, <delete>, "transform" commands (ie <create>, <renew>, <update>, <delete>,
<transfer op="request">). <transfer op="request">).
3.7. Classification of Objects 3.7. Classification of Objects
Objects may be assigned to a particular class, category, or tier, Objects may be assigned to a particular class, category, or tier,
skipping to change at page 9, line 28 skipping to change at page 8, line 31
If a server makes use of this element, it should provide clients with 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 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 objects that are subject to the with the value "standard" for all objects that are subject to the
standard or default fee. standard or default fee.
3.8. Phase and Subphase Attributes
The <fee:command> element has two attributes, phase and subphase,
that provide additional information related to a specific launch
phase as described in [draft-ietf-eppext-launchphase].
If the client <fee:command> contains no phase attribute the server
SHOULD return data (including the phase/subphase attribute(s)) for
all valid server combinations of currently active phase(s) and active
subphase(s).
If the client <fee:command> contains a server supported combination
of phase/subphase the server MUST return fee data (including the
phase/subphase attribute(s)) for the specific combination(s).
If the client <fee:command> contains a phase attribute with no
subphase, the server SHOULD return data (including the phase/subphase
attribute(s)) for all valid server combinations of provided phase and
available subphase(s).
If the client <fee:command> contains a subphase with no phase
attribute the server MUST respond with a 2003 "Required parameter
missing" error.
If the client <fee:command> contains a phase attribute not defined in
[draft-ietf-eppext-launchphase] or not supported by server the server
MUST respond with a 2004 "Parameter value range" error.
If the client <fee:command> contains a subphase attribute (or phase/
subphase combination) not supported by server the server MUST respond
with a 2004 "Parameter value range" error.
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.
skipping to change at page 10, line 16 skipping to change at page 9, line 49
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 contains the following <fee:check> element. The <fee:check> element MUST contain one or
child elements: more <fee:object> elements containing the following child elements:
o A <fee:command> element; o A <fee:objID> element that MUST match one and only one of the
domain names in the <domain:check>;
o An OPTIONAL <fee:currency> element. If the server does not
support <fee:currency> value, it MUST return a 2306 error
response;
o One or more <fee:command> element(s) with a "name" attribute, an
OPTIONAL "phase" attribute, and an OPTIONAL "subphase" attribute.
o An OPTIONAL <fee:currency> element; The <fee:command> element(s) MAY have the following child elements:
o An OPTIONAL <fee:period> element. o An OPTIONAL <fee:period> element.
o An OPTIONAL <fee:class> element. o An OPTIONAL <fee:class> element.
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">
skipping to change at page 10, line 41 skipping to change at page 11, line 19
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>
C: </check> C: </check>
C: <extension> C: <extension>
C: <fee:check xmlns:fee="urn:ietf:params:xml:ns:fee-0.11"> C: <fee:check xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
C: <fee:command>create</fee:command> C: <fee:object>
C: <fee:currency>USD</fee:currency> C: <fee:objID>example.com</fee:objID>
C: <fee:currency>USD</fee:currency>
C: <fee:command name="create">
C: <fee:period unit="y">2</fee:period>
C: </fee:command>
C: <fee:command name="renew"/>
C: <fee:command name="transfer"/>
C: <fee:command name="restore"/>
C: </fee:object>
C: <fee:object>
C: <fee:objID>example.net</fee:objID>
C: <fee:currency>USD</fee:currency>
C: <fee:command name="create">
C: <fee:period unit="y">11</fee:period>
C: </fee:command>
C: <fee:command name="renew"/>
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 contain an
exception described below) contain an <extension> element, which MUST <extension> element, which MUST contain a child <fee:chkData>
contain a child <fee:chkData> element. The <fee:chkData> element element. The <fee:chkData> element MUST contain a <fee:cd> element
MUST contain a <fee:cd> element for each object referenced in the for each object <fee:object> element referenced in the <fee:check>
<check> element in the command. element of the client command.
The <fee:cd> element has an OPTIONAL "avail" atribute which is a
boolean. If the value of this attribute evalutes to false, this
indicates that the server cannot calculate the relevant fees, because
the object, command, currency, period or class is invalid according
to server policy.
The <fee:cd> contains the following child elements:
o A <fee:object> element, which contains a copy of the child element
of the <check> element of the command, to which the fee
information relates.
o A <fee:command> element, which contains the same command that Each <fee:cd> element MUST contain the following child elements:
appeared in the corresponding <fee:object> element. This element
MAY have the OPTIONAL "phase" and "subphase" elements, which MUST
match the same attributes in the corresponding <fee:object>
element.
o A <fee:objID> element, which MUST match a <fee:objID> from the
client command.
o A <fee:currency> element, which contains the same currency code o A <fee:currency> element, which contains the same currency code
that appeared in the <fee:currency> element of the command. If no that appeared in the <fee:currency> element of the command. If no
<fee:currency> element appeared in the command, then the client's <fee:currency> element appeared in the command, then the client's
default billing currency should be used. default billing currency should be used.
o A <fee:command> element matching each <fee:command> that appeared
in the corresponding <fee:object> of the command. If a
<fee:object> element in the client command contains no
<fee:command> element the server SHOULD return a <fee:command>
element for each server billable transaction combination of the
<fee:object>. This element MAY have the OPTIONAL "phase" and
"subphase" attributes, which MUST match the same attributes in the
corresponding <fee:object> element of the client command.
o An OPTIONAL <fee:period> element, which contains the same unit The <fee:command> element also has an OPTIONAL "avail" attribute
that appeared in the <fee:currency> element of the command. If which is a boolean. If the value of this attribute evaluates to
the value of the preceding <fee:command> element is "restore", false, this indicates that the server cannot calculate the relevant
this element MUST NOT be included. Otherwise it MUST be included. fees, because the object, command, currency, period or class is
If no <fee:period> appeared in command (and the command is not invalid according to server policy.
"restore") then this element MUST have a value of 1 year.
o Zero or more <fee:fee> elements. The <fee:command> element(s) MAY have the following child elements:
o An OPTIONAL <fee:period> element, which contains the same unit
that appeared in the <fee:period> element of the command. If the
value of the preceding <fee:command> element is "restore", this
element MUST NOT be included. Otherwise it MUST be included. If
no <fee:period> appeared in command (and the command is not
"restore") then the server MUST return its default period value.
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.
o An OPTIONAL <fee:reason> element. o An OPTIONAL <fee:reason> 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 no fee will be assessed by the server for this indicates that no fee will be assessed by the server for this
command. command.
If the "avail" attribute of the <fee:cd> element is false, then the If the "avail" attribute of the <fee:command> element is false, then
<fee:cd> element MUST NOT contain any <fee:fee> or <fee:credit> child the <fee:command> element MUST NOT contain any <fee:fee> or
elements. If the "avail" attribute is true, then the <fee:cd> <fee:credit> child elements. If the "avail" attribute is true, then
element MUST NOT contain a <fee:reason> element. the <fee:command> element MUST NOT contain a <fee:reason> element.
Example <check> response: Example <check> 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: <resData> S: <resData>
skipping to change at page 12, line 31 skipping to change at page 13, line 23
S: <domain:cd> S: <domain:cd>
S: <domain:name avail="1">example.net</domain:name> S: <domain:name avail="1">example.net</domain:name>
S: </domain:cd> S: </domain:cd>
S: <domain:cd> S: <domain:cd>
S: <domain:name avail="1">example.xyz</domain:name> S: <domain:name avail="1">example.xyz</domain:name>
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.11" S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.13"
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <fee:cd avail="1"> S: <fee:cd>
S: <fee:object> S: <fee:objID>example.com</fee:objID>
S: <domain:name>example.com</domain:name>
S: </fee:object>
S: <fee:command>create</fee:command>
S: <fee:currency>USD</fee:currency>
S: <fee:period unit="y">1</fee:period>
S: <fee:fee
S: description="Registration Fee"
S: refundable="1"
S: grace-period="P5D">5.00</fee:fee>
S: </fee:cd>
S: <fee:cd avail="1">
S: <fee:object>
S: <domain:name>example.com</domain:name>
S: </fee:object>
S: <fee:command>create</fee:command>
S: <fee:currency>USD</fee:currency> S: <fee:currency>USD</fee:currency>
S: <fee:period unit="y">1</fee:period> S: <fee:command name="create">
S: <fee:fee S: <fee:period unit="y">2</fee:period>
S: description="Registration Fee" S: <fee:fee
S: refundable="1" S: description="Registration Fee"
S: grace-period="P5D">5.00</fee:fee> S: refundable="1"
S: grace-period="P5D">10.00</fee:fee>
S: </fee:command>
S: <fee:command name="renew">
S: <fee:period unit="y">1</fee:period>
S: <fee:fee
S: description="Renewal Fee"
S: refundable="1"
S: grace-period="P5D">5.00</fee:fee>
S: </fee:command>
S: <fee:command name="transfer">
S: <fee:period unit="y">1</fee:period>
S: <fee:fee
S: description="Transfer Fee"
S: refundable="1"
S: grace-period="P5D">5.00</fee:fee>
S: </fee:command>
S: <fee:command name="restore">
S: <fee:fee
S: description="Redemption Fee">5.00</fee:fee>
S: </fee:command>
S: </fee:cd> S: </fee:cd>
S: <fee:cd avail="0"> S: <fee:cd>
S: <fee:object> S: <fee:objID>example.net</fee:objID>
S: <domain:name>example.com</domain:name>
S: </fee:object>
S: <fee:command>create</fee:command>
S: <fee:currency>USD</fee:currency> S: <fee:currency>USD</fee:currency>
S: <fee:period unit="y">1</fee:period> S: <fee:command avail="0" name="create">
S: <fee:reason> S: <fee:reason>Maximum period is 10 years</fee:reason>
S: minimum period is 2 years. S: </fee:command>
S: </fee:reason> S: <fee:command name="renew">
S: <fee:period unit="y">1</fee:period>
S: <fee:fee
S: description="Renewal Fee"
S: refundable="1"
S: grace-period="P5D">5.00</fee:fee>
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>
5.1.1.1. Server Handling of <fee:class> Elements 5.1.1.1. Server Handling of Elements
Clients MAY include a <fee:class> in the <fee:check> element. There Clients MAY include a <fee:class> in the <fee:command> element.
are three ways in which servers may handle this element: There are three ways in which servers may handle this element:
1. If the server supports the concept of tiers or classes of 1. If the server supports the concept of tiers or classes of
objects, then the value of this element MUST be validated. If objects, then the value of this element MUST be validated. If
incorrect for the specified object, the "avail" attribute of the incorrect for the specified object, the "avail" attribute of the
corresponding <fee:cd> element MUST be false. corresponding <fee:command> element MUST be false.
2. If the server supports different "types" of object registrations 2. If the server supports different "types" of object registrations
(such as a "blocking" registration which does not resolve, or (such as a "blocking" registration which does not resolve, or
where a registry provides a value-added service that requires an where a registry provides a value-added service that requires an
opt-out to disable), then, as with the first model, the server opt-out to disable), then, as with the first model, the server
MUST valudate the value of the element. If the value is MUST validate the value of the element. If the value is
incorrect, the "avail" attribute of the corresponding <fee:cd> incorrect, the "avail" attribute of the corresponding
element MUST be false. <fee:command> element MUST be false.
3. If the server supports neither of the above models, the element 3. If the server supports neither of the above models, the element
MUST be ignored. MUST be ignored.
Server operators must provide clear documentation to client operators Server operators must provide clear documentation to client operators
which of the above models it supports. which of the above models it supports.
5.1.2. EPP Transfer Query Command 5.1.2. EPP Transfer Query Command
This extension does not add any elements to the EPP <transfer> query This extension does not add any elements to the EPP <transfer> query
command, but does include elements in the response, when the command, but does include elements in the response, when the
skipping to change at page 15, line 24 skipping to change at page 16, line 26
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.11"> S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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>
5.2. EPP Transform Commands 5.2. EPP Transform Commands
5.2.1. EPP <create> Command 5.2.1. EPP <create> Command
This extension adds elements to both the EPP <create> command and This extension adds elements to both the EPP <create> command and
response, when the extension has been selected during a <login> response, when the extension has been selected during a <login>
command. command.
If a <create> command is received with no <fee:create> extension and
the server requires a <fee:create> extension for the <domain:name>
the server MUST respond with a 2003 "Required parameter missing"
error.
When submitting a <create> command to the server, the client MAY When submitting a <create> command to the server, the client MAY
include in the <extension> element a <fee:create> element which include in the <extension> element a <fee:create> 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 <create> command has been processed successfully, and the When the <create> command has been processed successfully, and the
client selected the extension when it logged in, and a fee was client selected the extension when it logged in, and a fee was
assessed by the server for the transaction, the server MUST include assessed by the server for the transaction, the server MUST include
in the <extension> section of the EPP response a <fee:creData> in the <extension> section of the EPP response a <fee:creData>
element, which contains the following child elements: element, which 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
transaction, a <fee:creData> element MUST NOT be included in the
response.
Example <create> command: Example <create> 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: <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>
skipping to change at page 17, line 26 skipping to change at page 18, line 28
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.11"> C: <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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:
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
skipping to change at page 18, line 20 skipping to change at page 19, line 21
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.11"> S: <fee:creData xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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
S: description="Registration Fee"
S: refundable="1"
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>
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, which contains the following child elements: <fee:delData> element, which 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: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
<fee:delData> element MUST NOT be included in the response.
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.11"> S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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 19, line 42 skipping to change at page 20, line 41
This extension adds elements to both the EPP <renew> command and This extension adds elements to both the EPP <renew> command and
response, when the extension has been selected during a <login> response, when the extension has been selected during a <login>
command. command.
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, which contains the following child elements: <fee:renData> element, which 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
transaction, a <fee:renData> element MUST NOT be included in the
response.
Example <renew> command: Example <renew> 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: <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.11"> C: <fee:renew xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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:
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
skipping to change at page 21, line 19 skipping to change at page 22, line 20
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.11"> S: <fee:renData xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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
S: refundable="1"
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>
skipping to change at page 21, line 44 skipping to change at page 22, line 47
This extension adds elements to both the EPP <transfer> command and This extension adds elements to both the EPP <transfer> command and
response, when the value of the "op" attribute of the <transfer> response, when the value of the "op" attribute of the <transfer>
command element is "request", and the extension has been selected command element is "request", and the extension has been selected
during the <login> command. during the <login> command.
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, which contains the following child elements: <fee:trnData> element, which 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
transaction, a <fee:trnData> element MUST NOT be included in the
response.
Example <transfer> command: Example <transfer> 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: <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:fee-0.11"> C: <fee:transfer xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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:
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
skipping to change at page 23, line 24 skipping to change at page 24, line 25
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.11"> S: <fee:trnData xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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
S: refundable="1"
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>
5.2.5. EPP <update> Command 5.2.5. EPP <update> Command
This extension adds elements to both the EPP <update> command and This extension adds elements to both the EPP <update> command and
response, when the extension has been selected during a <login> has response, when the extension has been selected during the <login>
been selected during the <login> command. command.
When submitting a <update> command to the server, the client MAY When submitting a <update> command to the server, the client MAY
include in the <extension> element a <fee:update> element which include in the <extension> element a <fee:update> 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 <update> command has been processed successfully, and the When the <update> 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:upData> include in the <extension> section of the EPP response a
element, which contains the following child elements: <fee:updData> element, which 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
transaction, a <fee:upData> element MUST NOT be included in the
response.
Example <update> command: Example <update> 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: <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.11"> C: <fee:update xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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.11"> S: <fee:updData xmlns:fee="urn:ietf:params:xml:ns:fee-0.13">
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>
5.3. Formal Syntax 6. Formal Syntax
An EPP object mapping is specified in XML Schema notation. The
formal syntax presented here is a complete schema representation of
the object mapping suitable for automated validation of EPP XML
instances.
Copyright (c) 2014 IETF Trust and the persons identified as authors One schema is presented here that is the EPP Fee Extension schema.
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without The formal syntax presented here is a complete schema representation
modification, are permitted provided that the following conditions of the object mapping suitable for automated validation of EPP XML
are met: instances. The BEGIN and END tags are not part of the schema; they
are used to note the beginning and ending of the schema for URI
registration purposes.
o Redistributions of source code must retain the above copyright 6.1. Fee Extension Schema
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright BEGIN
notice, this list of conditions and the following disclaimer in <?xml version="1.0" encoding="utf-8"?>
the documentation and/or other materials provided with the <schema xmlns="http://www.w3.org/2001/XMLSchema"
distribution. xmlns:fee="urn:ietf:params:xml:ns:fee-0.13"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
targetNamespace="urn:ietf:params:xml:ns:fee-0.13"
elementFormDefault="qualified">
o Neither the name of Internet Society, IETF or IETF Trust, nor the <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
names of specific contributors, may be used to endorse or promote <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS <annotation>
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT <documentation>
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR Extensible Provisioning Protocol v1.0 Fee Extension
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN </documentation>
<?xml version="1.0" encoding="utf-8"?> </annotation>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:fee="urn:ietf:params:xml:ns:fee-0.11"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
targetNamespace="urn:ietf:params:xml:ns:fee-0.11"
elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <!-- Child elements found in EPP commands and responses -->
<import namespace="urn:ietf:params:xml:ns:domain-1.0" /> <element name="check" type="fee:checkType" />
<element name="chkData" type="fee:chkDataType" />
<element name="create" type="fee:transformCommandType" />
<element name="creData" type="fee:transformResultType" />
<element name="renew" type="fee:transformCommandType" />
<element name="renData" type="fee:transformResultType" />
<element name="transfer" type="fee:transformCommandType" />
<element name="trnData" type="fee:transferResultType" />
<element name="update" type="fee:transformCommandType" />
<element name="updData" type="fee:transformResultType" />
<element name="delData" type="fee:transformResultType" />
<annotation> <!-- client <check> command -->
<documentation>Extensible Provisioning Protocol <complexType name="checkType">
v1.0 extension schema for fee <sequence>
information.</documentation> <element name="object" type="fee:objectCheckType"
</annotation> maxOccurs="unbounded" />
</sequence>
</complexType>
<!-- <complexType name="objectCheckType">
Child elements found in EPP commands and responses <sequence>
--> <element name="objID" type="fee:objectIdentifierType" />
<element name="check" type="fee:checkType" /> <element name="currency" type="fee:currencyType"
<element name="chkData" type="fee:chkDataType" /> minOccurs="0" />
<element name="create" type="fee:transformCommandType" /> <element name="command" type="fee:commandType" maxOccurs="unbounded" />
<element name="creData" type="fee:transformResultType" /> </sequence>
<element name="renew" type="fee:transformCommandType" /> </complexType>
<element name="renData" type="fee:transformResultType" />
<element name="transfer" type="fee:transformCommandType" />
<element name="trnData" type="fee:transferResultType" />
<element name="update" type="fee:transformCommandType" />
<element name="updData" type="fee:transformResultType" />
<element name="delData" type="fee:deleteDataType" />
<!-- <complexType name="objectIdentifierType">
client <check> command <simpleContent>
--> <extension base="eppcom:labelType">
<complexType name="checkType"> <attribute name="element"
<sequence> type="NMTOKEN" default="name" />
<element name="command" type="fee:commandType" /> </extension>
<element name="currency" type="fee:currencyType" </simpleContent>
minOccurs="0" /> </complexType>
<element name="period" type="domain:periodType"
minOccurs="0" />
<element name="class" type="token"
minOccurs="0" />
</sequence>
</complexType>
<!-- <!-- server <check> result -->
server <check> result <complexType name="chkDataType">
--> <sequence>
<complexType name="chkDataType"> <element name="cd" type="fee:objectCDType"
<sequence> maxOccurs="unbounded" />
<element name="cd" type="fee:objectCDType" </sequence>
maxOccurs="unbounded" />
</sequence>
</complexType>
<complexType name="objectCDType"> </complexType>
<sequence>
<element name="object">
<complexType>
<sequence>
<any namespace="##other" processContents="lax"/>
</sequence>
</complexType>
</element>
<element name="command" type="fee:commandType" />
<element name="currency" type="fee:currencyType" />
<element name="period" type="domain:periodType"
minOccurs="0" maxOccurs="1" />
<element name="fee" type="fee:feeType"
minOccurs="0" maxOccurs="unbounded" />
<element name="credit" type="fee:creditType"
minOccurs="0" maxOccurs="unbounded" />
<element name="class" type="token" minOccurs="0" />
<element name="reason" type="token" minOccurs="0" />
</sequence>
<attribute name="avail" type="boolean" default="1" />
</complexType>
<!-- <complexType name="objectCDType">
general transform (create, renew, update, transfer) command <sequence>
--> <element name="objID" type="fee:objectIdentifierType" />
<complexType name="transformCommandType"> <element name="currency" type="fee:currencyType" />
<sequence> <element name="command" type="fee:commandType" />
<element name="currency" type="fee:currencyType" </sequence>
minOccurs="0" /> </complexType>
<element name="fee" type="fee:feeType"
maxOccurs="unbounded" />
<element name="credit" type="fee:creditType"
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
<!-- <!-- general transform (create, renew, update, transfer) command -->
general transform (create, renew, update) result <complexType name="transformCommandType">
--> <sequence>
<complexType name="transformResultType"> <element name="fee" type="fee:feeType"
<sequence> maxOccurs="unbounded" />
<element name="currency" type="fee:currencyType" /> <element name="credit" type="fee:creditType"
<element name="fee" type="fee:feeType" minOccurs="0" maxOccurs="unbounded" />
minOccurs="0" maxOccurs="unbounded" /> </sequence>
<element name="credit" type="fee:creditType" </complexType>
minOccurs="0" maxOccurs="unbounded" />
<element name="balance" type="fee:balanceType"
minOccurs="0" />
<element name="creditLimit" type="fee:creditLimitType"
minOccurs="0" />
</sequence>
</complexType>
<!-- <!-- general transform (create, renew, update) result -->
transfer result <complexType name="transformResultType">
--> <sequence>
<complexType name="transferResultType"> <element name="fee" type="fee:feeType"
<sequence> minOccurs="0" maxOccurs="unbounded" />
<element name="currency" type="fee:currencyType" /> <element name="credit" type="fee:creditType"
minOccurs="0" maxOccurs="unbounded" />
<element name="balance" type="fee:balanceType"
minOccurs="0" />
<element name="creditLimit" type="fee:creditLimitType"
minOccurs="0" />
</sequence>
</complexType>
<!-- only used op="query" responses --> <!-- transfer result -->
<element name="period" type="domain:periodType" <complexType name="transferResultType">
minOccurs="0" /> <sequence>
<element name="currency" type="fee:currencyType" />
<element name="fee" type="fee:feeType" <!-- only used op="query" responses -->
maxOccurs="unbounded" /> <element name="period" type="domain:periodType"
<element name="credit" type="fee:creditType" minOccurs="0" />
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
<!-- <element name="fee" type="fee:feeType"
delete result maxOccurs="unbounded" />
--> <element name="credit" type="fee:creditType"
<complexType name="deleteDataType"> minOccurs="0" maxOccurs="unbounded" />
<sequence> </sequence>
<element name="currency" type="fee:currencyType" />
<element name="credit" type="fee:creditType"
minOccurs="0" maxOccurs="unbounded" />
<element name="balance" type="fee:balanceType"
minOccurs="0" />
<element name="creditLimit" type="fee:creditLimitType"
minOccurs="0" />
</sequence>
</complexType>
<!-- </complexType>
common types
-->
<simpleType name="currencyType">
<restriction base="string">
<pattern value="[A-Z]{3}" />
</restriction>
</simpleType>
<complexType name="commandType"> <!-- common types -->
<simpleContent> <simpleType name="currencyType">
<extension base="fee:commandTypeValue"> <restriction base="string">
<attribute name="phase" type="token" /> <pattern value="[A-Z]{3}" />
<attribute name="subphase" type="token" /> </restriction>
</extension> </simpleType>
</simpleContent>
</complexType>
<simpleType name="commandTypeValue"> <complexType name="commandType">
<restriction base="token"> <sequence>
<minLength value="3"/> <element name="currency" type="fee:currencyType" />
<maxLength value="16"/> <element name="period" type="domain:periodType"
</restriction> minOccurs="0" maxOccurs="1" />
</simpleType> <element name="fee" type="fee:feeType"
minOccurs="0" maxOccurs="unbounded" />
<element name="credit" type="fee:creditType"
minOccurs="0" maxOccurs="unbounded" />
<element name="class" type="token" minOccurs="0" />
<element name="reason" type="token" minOccurs="0" />
</sequence>
<simpleContent>
<attribute name="name" type=extension base="fee:commandTypeValue"/>
<attribute name="phase" type="token" />
<attribute name="subphase" type="token" />
</extension>
</simpleContent>
<attribute name="avail" type="boolean" default="1" />
</complexType>
<simpleType name="nonNegativeDecimal"> <simpleType name="commandTypeValue">
<restriction base="decimal"> <restriction base="token">
<minInclusive value="0" /> <minLength value="3"/>
</restriction> <maxLength value="16"/>
</simpleType> </restriction>
</simpleType>
<simpleType name="negativeDecimal"> <simpleType name="nonNegativeDecimal">
<restriction base="decimal"> <restriction base="decimal">
<maxInclusive value="0" /> <minInclusive value="0" />
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="feeType">
<simpleContent>
<extension base="fee:nonNegativeDecimal">
<attribute name="description"/>
<attribute name="refundable" type="boolean" />
<attribute name="grace-period" type="duration" />
<attribute name="applied" default="immediate">
<simpleType>
<restriction base="token">
<enumeration value="immediate" />
<enumeration value="delayed" />
</restriction>
</simpleType>
</attribute>
</extension>
</simpleContent>
</complexType>
<complexType name="creditType"> <simpleType name="negativeDecimal">
<simpleContent> <restriction base="decimal">
<extension base="fee:negativeDecimal"> <maxInclusive value="0" />
<attribute name="description"/> </restriction>
</extension> </simpleType>
</simpleContent> <complexType name="feeType">
</complexType> <simpleContent>
<extension base="fee:nonNegativeDecimal">
<attribute name="description"/>
<attribute name="refundable" type="boolean" />
<attribute name="grace-period" type="duration" />
<attribute name="applied">
<simpleType>
<restriction base="token">
<enumeration value="immediate" />
<enumeration value="delayed" />
</restriction>
</simpleType>
</attribute>
</extension>
</simpleContent>
</complexType>
<simpleType name="balanceType"> <complexType name="creditType">
<restriction base="decimal" /> <simpleContent>
</simpleType> <extension base="fee:negativeDecimal">
<attribute name="description"/>
</extension>
</simpleContent>
</complexType>
<simpleType name="creditLimitType"> <simpleType name="balanceType">
<restriction base="decimal" /> <restriction base="decimal" />
</simpleType> </simpleType>
</schema> <simpleType name="creditLimitType">
<restriction base="decimal" />
</simpleType>
END </schema>
END
6. Security Considerations 7. Security Considerations
The mapping extensions described in this document do not provide any The mapping extensions described in this document do not provide any
security services beyond those described by EPP [RFC5730], the EPP security services beyond those described by EPP [RFC5730], the EPP
domain name mapping [RFC5731], and protocol layers used by EPP. The domain name mapping [RFC5731], and protocol layers used by EPP. The
security considerations described in these other specifications apply security considerations described in these other specifications apply
to this specification as well. to this specification as well.
7. IANA Considerations 8. IANA Considerations
7.1. XML Namespace 8.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.11 URI: ietf:params:xml:ns:fee-0.13
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 8.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
details of the registration are as follows: details of the registration are as follows:
Name of Extension: EPP Fee Extension Name of Extension: EPP Fee Extension
Document status: Standards Track Document status: Standards Track
Reference: (insert reference to RFC version of this document) Reference: (insert reference to RFC version of this document)
skipping to change at page 31, line 43 skipping to change at page 31, line 43
of this document. of this document.
TLDs: any TLDs: any
IPR Disclosure: none IPR Disclosure: none
Status: active Status: active
Notes: none Notes: none
8. Implementation Status 9. Implemntation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
[RFC6982] before publication. [RFC6982] before publication.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC6982]. Internet-Draft, and is based on a proposal described in [RFC6982].
The description of implementations in this section is intended to The description of implementations in this section is intended to
assist the IETF in its decision processes in progressing drafts to assist the IETF in its decision processes in progressing drafts to
RFCs. Please note that the listing of any individual implementation RFCs. Please note that the listing of any individual implementation
skipping to change at page 32, line 20 skipping to change at page 32, line 19
features. Readers are advised to note that other implementations may features. Readers are advised to note that other implementations may
exist. exist.
According to [RFC6982], "this will allow reviewers and working groups According to [RFC6982], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature. and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as It is up to the individual working groups to use this information as
they see fit". they see fit".
8.1. RegistryEngine EPP Service 9.1. RegistryEngine EPP Service
Organization: CentralNic Organization: CentralNic
Name: RegistryEngine EPP Service Name: RegistryEngine EPP Service
Description: Generic high-volume EPP service for gTLDs, ccTLDs and Description: Generic high-volume EPP service for gTLDs, ccTLDs and
SLDs SLDs
Level of maturity: Deployed in CentralNic's production environment as Level of maturity: Deployed in CentralNic's production environment as
well as two other gTLD registry systems, and two ccTLD registry well as two other gTLD registry systems, and two ccTLD registry
systems. systems.
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 10. Acknowledgements
The authors wish 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 Inc
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, Joe Snitker and Kevin Allendorf 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 o Alex Mayrhofer of Nic.at
10. Change History 11. Change History
10.1. Changes from 00 to 01
1. Restore the <check> command extension; either <check> or <info>
can be used.
2. added extension elements for <create>, <renew>, <transfer> and
<update> so that the server can reject the command if the fee is
incorrect.
10.2. Changes from 01 to 02
1. Use Internet-Draft version number rather than XML namespace
version number in this section.
2. Support for multiple <fee:fee> and <fee:credit> elements.
3. Added the "description" attribute to <fee:fee> and <fee:credit>
elements.
4. Added the <fee:balance> element.
5. Added the <fee:creditLimit> element.
6. Updated reference to [draft-ietf-eppext-launchphase].
7. Use <fee:command> instead of <fee:action>.
8. Use a single child element of <fee:chkData> instead of multiple
elements for each domain. This also requires using a different
name (<fee:name>) for the domain name.
9. Added the "refundable" attribute to <fee:fee> elements.
10. Added the "grace-period" attribute to <fee:fee> elements.
10.3. Changes from 02 to 03
1. Added the "applied" attribute to to <fee:fee> elements.
2. Simplified the wording in relation to when a server can return an
error for extended <info> commands.
3. Added the <fee:period> element to transfer query responses.
4. Removed wording about how servers behave when receiving incorrect
fee information from transform commands, and put it into a single
section at the top of the document.
5. Allow servers to omit <fee:fee> elements from <fee:cd> elements
if the command specified by the client is forbidden.
10.4. Changes from 03 to 04
1. Changed Intended Status to Standards Track.
2. As per suggestion from Michael Bauland, the <fee:period> element
is no longer included in <check> and <info> responses for
"restore" commands. It's still mandatory for all other commands.
3. Added summary of the attributes for the <fee:fee> element.
4. Clarified that the "refundable" and "grace-period" attributes of
the <fee:fee> elements are dependant on each other and cannot
appear on their own.
5. Removed the option of returning a 1001 response when the fee is
incorrect.
6. Forbidden the inclusion of extension elements in transform
responses if no fee/credit has been assessed.
7. Made the <fee:currency> element optional in transform commands.
8. Amended XML Namespace section of IANA Considerations, added EPP
Extension Registry section.
10.5. Changes from 04 to 05
1. Removed the extended <info> command. The <check> command is the
only command that can be used now.
2. Introduced a mandatory-to-implement "standard" class for non-
premium domains.
3. The decision was made to keep availability info in <check>
responses as registrars have indicated that it is very useful as
it avoids unnecessary round trips to the server.
4. Allow <fee:credit> elements to be present in <check> responses.
5. Allow the number of <fee:fee> which can appear in transform
responses to be zero.
6. Removed the <fee:balance> and <fee:creditLimit> elements from
transfer query responses. The reason is that these elements are
defined as containing the values after the transform command has
taken place - which means that it is not appropriate to include
them in a query response.
7. Added Implementation Status section.
10.6. Changes from 05 to 06
1. The specification is now object-agnostic, but works with RFC5731
[RFC5731] domains by default.
2. Renamed the <fee:domain> element to <fee:object>. Added the
"objURI" attribute.
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.
4. Removed references to the defunct <info> command syntax.
5. "MUST" requirements regarding documentation 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.
10.7. Changes from 06 to 07
1. Changed the syntax of the <check> form to be simpler: a single
set of <fee:command>, <fee:currency> etc elements is applied to
the objects specified in the main body of the <check> command.
2. Simplified the object-agnosticism to simply copy the element from
the <check> command into the <fee:cd> element.
3. Added the "avail" attribute to the <fee:cd> element and added
commentary about its semantics.
4. Added the <fee:reason> element to the <check> response so servers 11.1. Change from 00 to 01
can indicate why fee information is not available.
10.8. Changes from draft-brown-epp-fees-00 to Added Roger Carney as author to finish draft. Moved Formal Syntax
draft-ietf-regext-epp-fees-00 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.
1. Updated to be a WG document. 11.2. Change from draft-brown-00 to draft-ietf-regext-fees-00
11. Normative References Updated to be REGEXT WG document.
[ISO4217] International Organization for Standardization, "ISO 4217: 12. Normative References
2008, Codes for the representation of currencies and
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,
RFC2119, March 1997, DOI 10.17487/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 10.17487/RFC3915, September 2004, DOI 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,
RFC5731, August 2009, DOI 10.17487/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 10.17487/RFC6982, July 2013, DOI 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]
Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping
for the Extensible Provisioning Protocol (EPP)", 2014.
Authors' Addresses Authors' Addresses
Roger Carney
GoDaddy Inc.
14455 N. Hayden Rd. #219
Scottsdale, AZ 85260
US
Email: rcarney@godaddy.com
URI: http://www.godaddy.com
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: http://www.centralnic.com
Jothan Frakes Jothan Frakes
Email: jothan@jothan.com Email: jothan@jothan.com
URI: http://jothan.com URI: http://jothan.com
 End of changes. 152 change blocks. 
654 lines changed or deleted 505 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/