draft-ietf-regext-epp-fees-15.txt   draft-ietf-regext-epp-fees-16.txt 
Registration Protocols Extensions R. Carney Registration Protocols Extensions R. Carney
Internet-Draft GoDaddy Inc. Internet-Draft GoDaddy Inc.
Intended status: Standards Track G. Brown Intended status: Standards Track G. Brown
Expires: May 8, 2019 CentralNic Group plc Expires: November 2, 2019 CentralNic Group plc
J. Frakes J. Frakes
November 4, 2018 May 1, 2019
Registry Fee Extension for the Extensible Provisioning Protocol (EPP) Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-fees-15 draft-ietf-regext-epp-fees-16
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) Given the expansion of the DNS namespace, and the proliferation of
novel business models, it is desirable to provide a method for
Extensible Provisioning Protocol (EPP) clients to query EPP servers
for the fees and credits and provide expected fees and credits for
certain commands and objects. This document describes an 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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 May 8, 2019. This Internet-Draft will expire on November 2, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 15 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Migrating to Newer Versions of This Extension . . . . . . . . 4 2. Migrating to Newer Versions of This Extension . . . . . . . . 4
3. Extension Elements . . . . . . . . . . . . . . . . . . . . . 4 3. Extension Elements . . . . . . . . . . . . . . . . . . . . . 4
3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 4 3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 4
3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . 5 3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . 5
3.3. Validity Periods . . . . . . . . . . . . . . . . . . . . 5 3.3. Validity Periods . . . . . . . . . . . . . . . . . . . . 5
3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . 6 3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . 6
3.4.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 6 3.4.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 7
3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 7 3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 7
3.4.3. Correlation between Refundability and Grace Periods . 7 3.4.3. Correlation between Refundability and Grace Periods . 7
3.4.4. Applicability . . . . . . . . . . . . . . . . . . . . 7 3.4.4. Applicability . . . . . . . . . . . . . . . . . . . . 7
3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 7 3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 8
3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . 8 3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . 8
3.7. Classification of Objects . . . . . . . . . . . . . . . . 8 3.7. Classification of Objects . . . . . . . . . . . . . . . . 8
3.8. Phase and Subphase Attributes . . . . . . . . . . . . . . 8 3.8. Phase and Subphase Attributes . . . . . . . . . . . . . . 9
3.9. Reason . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.9. Reason . . . . . . . . . . . . . . . . . . . . . . . . . 10
4. Server Handling of Fee Information . . . . . . . . . . . . . 11 4. Server Handling of Fee Information . . . . . . . . . . . . . 11
5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 11 5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 12
5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 11 5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 12
5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 11 5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 12
5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 16 5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 16
5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 17 5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 18
5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 17 5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 18
5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19 5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20
5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20 5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21
5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 22 5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 23
5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 24 5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 25
6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 26 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 26 6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 31 7. Security Considerations . . . . . . . . . . . . . . . . . . . 32
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 31 8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 32
8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 32 8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 33
9. Implementation Status . . . . . . . . . . . . . . . . . . . . 32 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 33
9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 33 9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 34
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34
11. Change History . . . . . . . . . . . . . . . . . . . . . . . 34 11. Change History . . . . . . . . . . . . . . . . . . . . . . . 35
11.1. Change from 14 to 15 . . . . . . . . . . . . . . . . . . 34 11.1. Change from 15 to 16 . . . . . . . . . . . . . . . . . . 35
11.2. Change from 13 to 14 . . . . . . . . . . . . . . . . . . 34 11.2. Change from 14 to 15 . . . . . . . . . . . . . . . . . . 35
11.3. Change from 12 to 13 . . . . . . . . . . . . . . . . . . 34 11.3. Change from 13 to 14 . . . . . . . . . . . . . . . . . . 35
11.4. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 34 11.4. Change from 12 to 13 . . . . . . . . . . . . . . . . . . 35
11.5. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 34 11.5. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 35
11.6. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 34 11.6. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 35
11.7. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34 11.7. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 35
11.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 35 11.8. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 36
11.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 35 11.9. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 36
11.10. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 35 11.10. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 36
11.11. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 35 11.11. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 36
11.12. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35 11.12. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 36
11.13. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35 11.13. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 36
11.14. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 36 11.14. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 37
11.15. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 36 11.15. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 37
11.16. Change from draft-brown-00 to draft-ietf-regext-fees-00 36 11.16. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 37
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 11.17. Change from draft-brown-00 to draft-ietf-regext-fees-00 37
12.1. Normative References . . . . . . . . . . . . . . . . . . 36 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
12.2. Informative References . . . . . . . . . . . . . . . . . 37 12.1. Normative References . . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 12.2. Informative References . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
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.
Given the recent expansion of the DNS namespace, and the Given the expansion of the DNS namespace, and the proliferation of
proliferation of novel business models, it is now desirable to novel business models, it is desirable to provide a method for EPP
provide a method for EPP clients to query EPP servers for the fees clients to query EPP servers for the fees and credits associated with
and credits associated with certain commands and specific objects. certain commands and specific objects.
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping
provides a mechanism by which EPP clients may query the fees and provides a mechanism by which EPP clients may query the fees and
credits associated with various billable transactions, and obtain credits associated with various billable transactions, and obtain
their current account balance. their current account balance.
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 4, line 13 skipping to change at page 4, line 18
implementation. implementation.
"fee" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:fee- "fee" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:fee-
1.0". The XML namespace prefix "fee" is used, but implementations 1.0". The XML namespace prefix "fee" is used, but implementations
MUST NOT depend on it and instead employ a proper namespace-aware XML MUST NOT depend on it and instead employ a proper namespace-aware XML
parser and serializer to interpret and output the XML documents. parser and serializer to interpret and output the XML documents.
In examples, "C:" represents lines sent by a protocol client and "S:" In examples, "C:" represents lines sent by a protocol client and "S:"
represents lines returned by a protocol server. Indentation and represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element white space in examples are provided only to illustrate element
relationships and are not a REQUIRED feature of this protocol. relationships and are not a required feature of this protocol.
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
clients to progressively update their implementations when a new clients to progressively update their implementations when a new
version of the extension is deployed. version of the extension is deployed.
skipping to change at page 4, line 44 skipping to change at page 4, line 49
When preparing responses to commands which do include extension When preparing responses to commands which do include extension
elements, the server SHOULD only include extension elements for the elements, the server SHOULD only include extension elements for the
extension versions present in the command. extension versions present in the command.
3. Extension Elements 3. Extension Elements
3.1. Client Commands 3.1. 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 that is applicable to the given command.
The use of the <fee:command> keys off the use of the "name" attribute The use of the <fee:command> keys off the use of the "name" attribute
to define which transform fees the client is requesting information to define which transform fees the client is requesting information
about. Here is the list of possible values for the "name" attribute: about. Here is the list of possible values for the "name" attribute:
o "create" indicating a <create> command as defined in [RFC5730]; o "create" indicating a <create> command as defined in [RFC5730];
o "delete" indicating a <delete> command as defined in [RFC5730]; o "delete" indicating a <delete> command as defined in [RFC5730];
o "renew" indicating a <renew> 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 "update" indicating a <update> command as defined in [RFC5730];
o "transfer" indicating a <transfer> command as defined in o "transfer" indicating a <transfer> command as defined in
skipping to change at page 6, line 30 skipping to change at page 6, line 36
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 the description of the fee. Servers should provide documentation on the
possible values of this attribute, and their meanings. possible values of this attribute, and their meanings. An OPTIONAL
"lang" attribute MAY be present to identify the language of the
returned text and has a default value of "en" (English).
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. An OPTIONAL "lang" attribute MAY be present to
identify the language of the returned text and has a default value of
"en" (English).
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 [RFC8334]) or when an object is deleted during the described in [RFC8334]) or when an object is deleted during the
relevant Grace Period (see below). relevant Grace Period (see below).
If the "refundable" attribute is omitted, then clients SHOULD NOT If the "refundable" attribute is omitted, then clients SHOULD NOT
skipping to change at page 7, line 25 skipping to change at page 7, line 35
grace period for a fee. If a server implements the Registry Grace grace period for a fee. If a server implements the Registry Grace
Period extension [RFC3915], it MUST specify the grace period for all Period extension [RFC3915], it MUST specify the grace period for all
relevant transactions. relevant transactions.
If the "grace-period" attribute is omitted, then clients SHOULD NOT If the "grace-period" attribute is omitted, then clients SHOULD NOT
make any assumption about the grace period of the fee. make any assumption about the grace period of the fee.
3.4.3. Correlation between Refundability and Grace Periods 3.4.3. Correlation between Refundability and Grace Periods
If a <fee:fee> element has a "grace-period" attribute then it MUST If a <fee:fee> element has a "grace-period" attribute then it MUST
also be refundable. If the "refundable" attribute of a <fee:fee> also be refundable and the "refundable" attribute MUST be true. If
element is false then it MUST NOT have a "grace-period" attribute. the "refundable" attribute of a <fee:fee> element is false then it
MUST NOT have a "grace-period" attribute.
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
skipping to change at page 8, line 12 skipping to change at page 8, line 25
billable commands (e.g. <create>, <renew>, <update>, <delete>, billable commands (e.g. <create>, <renew>, <update>, <delete>,
<transfer 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. If the "applied" attribute of the <fee:fee> element is
"delayed", then the <fee:balance> MUST reflect the client's account
balance without any fees or credits associated with that command.
3.6. Credit Limit 3.6. Credit Limit
As described above, if a server returns a response containing a As described above, if a server returns a response containing a
<fee:balance> with a negative value, then the server has extended a <fee:balance> with a negative value, then the server has extended a
line of credit to the client. A server MAY also include a line of credit to the client. A server MAY also include a
<fee:creditLimit> element in responses which indicates the maximum <fee:creditLimit> element in responses that indicates the maximum
credit available to a client. A server MAY reject certain credit available to a client. A server MAY reject certain
transactions if the absolute value of the <fee:balance> is equal to transactions if the absolute value of the <fee:balance> is equal to
or exceeds the 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 (e.g. <create>, <renew>, <update>, <delete>, "transform" commands (e.g. <create>, <renew>, <update>, <delete>,
<transfer op="request">). <transfer op="request">).
skipping to change at page 8, line 42 skipping to change at page 9, line 10
Objects may be assigned to a particular class, category, or tier, Objects may be assigned to a particular class, category, or tier,
each of which has a particular fee or set of fees associated with it. each of which has a particular fee or set of fees associated with it.
The <fee:class> element, which MAY appear in <check> and transform The <fee:class> element, which MAY appear in <check> and transform
responses, is used to indicate the classification of an object. responses, is used to indicate the classification of an object.
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 that 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 3.8. Phase and Subphase Attributes
The <fee:command> element has two attributes, phase and subphase, The <fee:command> element has two attributes, phase and subphase,
that provide additional information related to a specific launch that provide additional information related to a specific launch
phase as described in [RFC8334]. These attributes are used as phase as described in [RFC8334]. These attributes are used as
filters that should refine the server processing. filters that should refine the server processing.
skipping to change at page 19, line 25 skipping to change at page 20, line 25
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:epp:fee-1.0"> S: <fee:creData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
S: <fee:currency>USD</fee:currency> S: <fee:currency>USD</fee:currency>
S: <fee:fee S: <fee:fee
S: description="Registration Fee" S: description="Registration Fee"
S: lang="en"
S: refundable="1" S: refundable="1"
S: grace-period="P5D">5.00</fee:fee> S: grace-period="P5D">5.00</fee:fee>
S: <fee:balance>-5.00</fee:balance> S: <fee:balance>-5.00</fee:balance>
S: <fee:creditLimit>1000.00</fee:creditLimit> S: <fee:creditLimit>1000.00</fee:creditLimit>
S: </fee:creData> S: </fee:creData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
skipping to change at page 20, line 21 skipping to change at page 21, line 22
S: <?xml version="1.0" encoding="utf-8" standalone="no"?> S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <fee:delData S: <fee:delData
S: xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"> S: xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
S: <fee:currency>USD</fee:currency> S: <fee:currency>USD</fee:currency>
S: <fee:credit description="AGP Credit">-5.00</fee:credit> S: <fee:credit
S: description="AGP Credit"
S: lang="en">-5.00</fee:credit>
S: <fee:balance>1005.00</fee:balance> S: <fee:balance>1005.00</fee:balance>
S: </fee:delData> S: </fee:delData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S: </epp> S: </epp>
skipping to change at page 30, line 45 skipping to change at page 31, line 45
<simpleType name="negativeDecimal"> <simpleType name="negativeDecimal">
<restriction base="decimal"> <restriction base="decimal">
<maxInclusive value="0" /> <maxInclusive value="0" />
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="feeType"> <complexType name="feeType">
<simpleContent> <simpleContent>
<extension base="fee:nonNegativeDecimal"> <extension base="fee:nonNegativeDecimal">
<attribute name="description"/> <attribute name="description"/>
<attribute name="lang" type="language" default="en"/>
<attribute name="refundable" type="boolean" /> <attribute name="refundable" type="boolean" />
<attribute name="grace-period" type="duration" /> <attribute name="grace-period" type="duration" />
<attribute name="applied"> <attribute name="applied">
<simpleType> <simpleType>
<restriction base="token"> <restriction base="token">
<enumeration value="immediate" /> <enumeration value="immediate" />
<enumeration value="delayed" /> <enumeration value="delayed" />
</restriction>
</restriction>
</simpleType> </simpleType>
</attribute> </attribute>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<complexType name="creditType"> <complexType name="creditType">
<simpleContent> <simpleContent>
<extension base="fee:negativeDecimal"> <extension base="fee:negativeDecimal">
<attribute name="description"/> <attribute name="description"/>
<attribute name="lang" type="language" default="en"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<simpleType name="balanceType"> <simpleType name="balanceType">
<restriction base="decimal" /> <restriction base="decimal" />
</simpleType> </simpleType>
<simpleType name="creditLimitType"> <simpleType name="creditLimitType">
<restriction base="decimal" /> <restriction base="decimal" />
skipping to change at page 34, line 7 skipping to change at page 35, line 7
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, Joe Snitker and Kevin Allendorf 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
o Thomas Corte of Knipp Medien und Kommunikation GmbH o Thomas Corte of Knipp Medien und Kommunikation GmbH
11. Change History 11. Change History
11.1. Change from 14 to 15 11.1. Change from 15 to 16
Updated per AD review and list comments: several grammar corrections;
clarification text added to section 3.4.3 and 3.5; and a schema
update for consistency by providing a "lang" attribute to the
<fee:fee> and <fee:credit> "description" attribute detailed in
section 3.4.
11.2. Change from 14 to 15
Updated schema, moving the "standard" attribute of the Updated schema, moving the "standard" attribute of the
"commandDataType" inside the <extension> block. "commandDataType" inside the <extension> block.
11.2. Change from 13 to 14 11.3. Change from 13 to 14
Moved RFC 7451 reference from Normative to Informative section. Moved RFC 7451 reference from Normative to Informative section.
11.3. Change from 12 to 13 11.4. Change from 12 to 13
Updated XML namespace and schema registration to be "epp" scoped - Updated XML namespace and schema registration to be "epp" scoped -
global replace of XML namespace from urn:ietf:params:xml:ns:fee-1.0 global replace of XML namespace from urn:ietf:params:xml:ns:fee-1.0
to urn:ietf:params:xml:ns:epp:fee-1.0 and the XML schema registration to urn:ietf:params:xml:ns:epp:fee-1.0 and the XML schema registration
from urn:ietf:params:xml:schema:fee-1.0 to from urn:ietf:params:xml:schema:fee-1.0 to
urn:ietf:params:xml:schema:epp:fee-1.0. urn:ietf:params:xml:schema:epp:fee-1.0.
11.4. Change from 11 to 12 11.5. Change from 11 to 12
Updated references to current version of documents and moved the Updated references to current version of documents and moved the
"standard" attribute from the check command (commandType) to the "standard" attribute from the check command (commandType) to the
check response (commandDataType). check response (commandDataType).
11.5. Change from 10 to 11 11.6. Change from 10 to 11
Updated document per Working Group Last Call comments. Made minor Updated document per Working Group Last Call comments. Made minor
textual changes throughout for enhanced clarity per WGLC comments. textual changes throughout for enhanced clarity per WGLC comments.
11.6. Change from 09 to 10 11.7. Change from 09 to 10
Updated document per Working Group Last Call comments. Updated Updated document per Working Group Last Call comments. Updated
schema to version 1.0 in anticipation of standardization, no changes schema to version 1.0 in anticipation of standardization, no changes
were made to the latest, 0.25, schema. Made minor textual changes were made to the latest, 0.25, schema. Made minor textual changes
throughout for enhanced clarity per WGLC comments. throughout for enhanced clarity per WGLC comments.
11.7. Change from 08 to 09 11.8. Change from 08 to 09
Updated scheme to version 0.25 to allow tighter checking on Updated scheme to version 0.25 to allow tighter checking on
<fee:command> by splitting the client and server definitions, moved <fee:command> by splitting the client and server definitions, moved
the class element from the command to the object level and added an the class element from the command to the object level and added an
optional standard attribute to the command element. Also updated optional standard attribute to the command element. Also updated
section 3.1 for clarity on name attribute; updated section 3.9 for section 3.1 for clarity on name attribute; updated section 3.9 for
clarity on uses of <fee:reason>; removed second paragraph in section clarity on uses of <fee:reason>; removed second paragraph in section
5.2.1 as it was duplicative of second to last paragraph in 4.0; and 5.2.1 as it was duplicative of second to last paragraph in 4.0; and
updated section 5.1.1 to add section references. updated section 5.1.1 to add section references.
11.8. Change from 07 to 08 11.9. Change from 07 to 08
Updated section 3.8 and 5.1.1 to provide clarity on server processing Updated section 3.8 and 5.1.1 to provide clarity on server processing
and response of various scenarios (i.e. "quiet" period processing). and response of various scenarios (i.e. "quiet" period processing).
11.9. Change from 06 to 07 11.10. Change from 06 to 07
Updated section 3.8 and 4.0 to provide clarity on server processing Updated section 3.8 and 4.0 to provide clarity on server processing
and response of various scenarios. and response of various scenarios.
11.10. Change from 05 to 06 11.11. Change from 05 to 06
Updated scheme to version 0.23 to allow the return of no Updated scheme to version 0.23 to allow the return of no
<fee:command> element(s) if an error situation occurs. Edited <fee:command> element(s) if an error situation occurs. Edited
section 3.8 extensively after input from interim meeting and REGEXT section 3.8 extensively after input from interim meeting and REGEXT
F2F meeting at IETF-99. Added normative reference for draft-ietf- F2F meeting at IETF-99. Added normative reference for draft-ietf-
eppext-launchphase. eppext-launchphase.
11.11. Change from 04 to 05 11.12. Change from 04 to 05
Updated scheme to version 0.21 to support the lang attribute for the Updated scheme to version 0.21 to support the lang attribute for the
reason element of the objectCDType and the commandType types as well reason element of the objectCDType and the commandType types as well
as to add the update command to the commandEnum type. Updated as to add the update command to the commandEnum type. Updated
section 3.1 to include language for the custom command. Added section 3.1 to include language for the custom command. Added
section 3.9 to provide a description of the <fee:reason> element. section 3.9 to provide a description of the <fee:reason> element.
Fixed typos and added clarification text on when client fee is less Fixed typos and added clarification text on when client fee is less
than server fee in section 4. Additionally, I added description than server fee in section 4. Additionally, I added description
pointers to appropriate Section 3 definitions for element clarity pointers to appropriate Section 3 definitions for element clarity
throughout the document. throughout the document.
11.12. Change from 03 to 04 11.13. Change from 03 to 04
Updated scheme to version 0.19 to correct typos and to replace the Updated scheme to version 0.19 to correct typos and to replace the
commandTypeValue type with the commandEnum type and customName commandTypeValue type with the commandEnum type and customName
attribute for stricter validation. Updated various text for grammar attribute for stricter validation. Updated various text for grammar
and clarity. Added text to section 4 clarifying the <check> response and clarity. Added text to section 4 clarifying the <check> response
when the client provided no fee extension but the server was when the client provided no fee extension but the server was
expecting the extension. expecting the extension.
11.13. Change from 02 to 03 11.14. Change from 02 to 03
Updated scheme to version 0.17 to simplify the check command syntax. Updated scheme to version 0.17 to simplify the check command syntax.
Moved fee avail to objectCDType to allow fast failing on error Moved fee avail to objectCDType to allow fast failing on error
situations. Removed the objectCheckType as it was no longer being situations. Removed the objectCheckType as it was no longer being
used. Updated examples to reflect these scheme changes. Added used. Updated examples to reflect these scheme changes. Added
language for server failing a <create> if the <fee:fee> passed by the language for server failing a <create> if the <fee:fee> passed by the
client is less than the server fee. client is less than the server fee.
11.14. Change from 01 to 02 11.15. Change from 01 to 02
Updated scheme to version 0.15 to fix errors in CommandType, Updated scheme to version 0.15 to fix errors in CommandType,
objectCDType, transformCommandType and transformResultType objectCDType, transformCommandType and transformResultType
definitions. definitions.
11.15. Change from 00 to 01 11.16. Change from 00 to 01
Added Roger Carney as author to finish draft. Moved Formal Syntax Added Roger Carney as author to finish draft. Moved Formal Syntax
section to main level numbering. Various grammar, typos, and section to main level numbering. Various grammar, typos, and
administrative edits for clarity. Removed default value for the administrative edits for clarity. Removed default value for the
"applied" attribute of <fee:fee> so that it can truly be optional. "applied" attribute of <fee:fee> so that it can truly be optional.
Added support for the <delete> command to return a <fee:fee> element Added support for the <delete> command to return a <fee:fee> element
as well. Modified default response on the <check> command for the as well. Modified default response on the <check> command for the
optional <fee:period> when it was not provided in the command, optional <fee:period> when it was not provided in the command,
leaving it to the server to provide the default period value. leaving it to the server to provide the default period value.
Extensive edits were done to the <check> command, the <check> Extensive edits were done to the <check> command, the <check>
response and to the fee extension schema (checkType, objectCheckType, response and to the fee extension schema (checkType, objectCheckType,
objectIdentifierType, objectCDType, commandType) to support objectIdentifierType, objectCDType, commandType) to support
requesting and returning multiple transformation fees in a single requesting and returning multiple transformation fees in a single
call. Added section on Phase/Subphase to provide more context on the call. Added section on Phase/Subphase to provide more context on the
uses. uses.
11.16. Change from draft-brown-00 to draft-ietf-regext-fees-00 11.17. Change from draft-brown-00 to draft-ietf-regext-fees-00
Updated to be REGEXT WG document. Updated to be REGEXT WG document.
12. References 12. References
12.1. Normative References 12.1. Normative References
[ISO4217] International Organization for Standardization, "Codes for [ISO4217] International Organization for Standardization, "Codes for
the representation of currencies", August 2015, the representation of currencies", August 2015,
<https://www.iso.org/standard/64758.html>. <https://www.iso.org/standard/64758.html>.
 End of changes. 42 change blocks. 
80 lines changed or deleted 105 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/