draft-ietf-regext-epp-fees-16.txt   draft-ietf-regext-epp-fees-17.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: November 2, 2019 CentralNic Group plc Expires: March 8, 2020 CentralNic Group plc
J. Frakes J. Frakes
May 1, 2019 September 5, 2019
Registry Fee Extension for the Extensible Provisioning Protocol (EPP) Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-fees-16 draft-ietf-regext-epp-fees-17
Abstract Abstract
Given the expansion of the DNS namespace, and the proliferation of Given the expansion of the DNS namespace, and the proliferation of
novel business models, it is desirable to provide a method for novel business models, it is desirable to provide a method for
Extensible Provisioning Protocol (EPP) clients to query EPP servers Extensible Provisioning Protocol (EPP) clients to query EPP servers
for the fees and credits and provide expected fees and credits for for the fees and credits and provide expected fees and credits for
certain commands and objects. This document describes an EPP certain commands and objects. This document describes an EPP
extension mapping for registry fees. extension mapping for registry fees.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 November 2, 2019. This Internet-Draft will expire on March 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 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
skipping to change at page 2, line 43 skipping to change at page 2, line 43
5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 18 5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 18
5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20 5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20
5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21 5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21
5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 23 5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 23
5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 25 5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 25
6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 27 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 27 6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 32 7. Security Considerations . . . . . . . . . . . . . . . . . . . 32
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 32 8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 32
8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 33 8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 32
9. Implementation Status . . . . . . . . . . . . . . . . . . . . 33 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 33
9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 34 9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 33
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34
11. Change History . . . . . . . . . . . . . . . . . . . . . . . 35 11. Change History . . . . . . . . . . . . . . . . . . . . . . . 34
11.1. Change from 15 to 16 . . . . . . . . . . . . . . . . . . 35 11.1. Change from 16 to 17 . . . . . . . . . . . . . . . . . . 34
11.2. Change from 14 to 15 . . . . . . . . . . . . . . . . . . 35 11.2. Change from 15 to 16 . . . . . . . . . . . . . . . . . . 34
11.3. Change from 13 to 14 . . . . . . . . . . . . . . . . . . 35 11.3. Change from 14 to 15 . . . . . . . . . . . . . . . . . . 35
11.4. Change from 12 to 13 . . . . . . . . . . . . . . . . . . 35 11.4. Change from 13 to 14 . . . . . . . . . . . . . . . . . . 35
11.5. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 35 11.5. Change from 12 to 13 . . . . . . . . . . . . . . . . . . 35
11.6. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 35 11.6. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 35
11.7. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 35 11.7. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 35
11.8. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 36 11.8. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 35
11.9. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 36 11.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 35
11.10. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 36 11.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 36
11.11. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 36 11.11. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 36
11.12. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 36 11.12. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 36
11.13. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 36 11.13. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 36
11.14. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 37 11.14. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 36
11.15. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 37 11.15. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 36
11.16. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 37 11.16. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 37
11.17. Change from draft-brown-00 to draft-ietf-regext-fees-00 37 11.17. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 37
11.18. Change from draft-brown-00 to draft-ietf-regext-fees-00 37
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
12.1. Normative References . . . . . . . . . . . . . . . . . . 37 12.1. Normative References . . . . . . . . . . . . . . . . . . 37
12.2. Informative References . . . . . . . . . . . . . . . . . 38 12.2. Informative References . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 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]
skipping to change at page 4, line 22 skipping to change at page 4, line 22
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
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.
Servers SHOULD (for a temporary migration period) provide support for Servers SHOULD (for a temporary migration period) provide support for
older versions of the extension in parallel to the newest version, older versions of the extension in parallel to the newest version,
and allow clients to select their preferred version via the and allow clients to select their preferred version via the
<svcExtension> element of the <login> command. <svcExtension> element of the <login> command.
If a client requests multiple versions of the extension at login, If a client requests multiple versions of the extension at login,
skipping to change at page 5, line 30 skipping to change at page 5, line 24
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 [RFC8334]. It may also specifying a launch phase as described in [RFC8334]. It may also
contain an OPTIONAL "subphase" attribute identifying the custom or contain an OPTIONAL "subphase" attribute identifying the custom or
sub-phase as described in [RFC8334]. sub-phase as described in [RFC8334].
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:2015].
Note that ISO 4217 provides the special "XXX" code, which MAY be used Note that ISO 4217:2015 provides the special "XXX" code, which MAY be
if the server uses a non-currency based system for assessing fees, used if the server uses a non-currency based system for assessing
such as a system of credits. fees, such as a system of credits.
The use of <fee:currency> elements in client commands is OPTIONAL: if The use of <fee:currency> elements in client commands is OPTIONAL: if
a <fee:currency> element is not present in a command, the server MUST a <fee:currency> element is not present in a command, the server MUST
determine the currency based on the server default currency or based determine the currency based on the server default currency or based
on the client's account settings which are agreed to by the client on the client's account settings which are agreed to by the client
and server via an out-of-band channel. However, the <fee:currency> and server via an out-of-band channel. However, the <fee:currency>
element MUST be present in responses. 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 "Parameter incorrect currency code. Servers SHOULD return a 2004 "Parameter
skipping to change at page 6, line 15 skipping to change at page 6, line 9
<domain: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 the server default period. the server MUST determine the fee(s) using the server default period.
The <fee:period> element MUST be present in <check> responses. 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. A fee will result in
subtracting from the Account Balance (described in Section 3.5) and a
credit will result in adding to the Account Balance (described in
Section 3.5).
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 indicates a debit against the client's account balance; a
<fee:credit> element indicates a credit. A <fee:fee> element MUST <fee:credit> element indicates a credit. A <fee:fee> element MUST
have a non-negative value. A <fee:credit> element MUST have a have a zero or non-negative value. A <fee:credit> element MUST have
negative value. a zero or 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:
skipping to change at page 27, line 37 skipping to change at page 27, line 37
One schema is presented here that is the EPP Fee Extension schema. One schema is presented here that is the EPP Fee Extension schema.
The formal syntax presented here is a complete schema representation The formal syntax presented here is a complete schema representation
of the object mapping suitable for automated validation of EPP XML of the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they 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 are used to note the beginning and ending of the schema for URI
registration purposes. registration purposes.
6.1. Fee Extension Schema 6.1. Fee Extension Schema
Copyright (c) 2018 IETF Trust and the persons identified as authors The formal syntax presented here is a complete schema representation
of the code. All rights reserved. of the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they
Redistribution and use in source and binary forms, with or without are used to note the beginning and ending of the schema for URI
modification, are permitted provided that the following conditions registration purposes.
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="utf-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" <schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0" xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
targetNamespace="urn:ietf:params:xml:ns:epp:fee-1.0" targetNamespace="urn:ietf:params:xml:ns:epp:fee-1.0"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0" /> <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Extensible Provisioning Protocol v1.0 Fee Extension Extensible Provisioning Protocol v1.0 Fee Extension
</documentation> </documentation>
</annotation> </annotation>
<!-- Child elements found in EPP commands and responses --> <!-- Child elements found in EPP commands and responses -->
skipping to change at page 32, line 38 skipping to change at page 32, line 14
</schema> </schema>
END END
7. 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. This extension passes financial
information using the EPP protocol, so confidentiality and integrity
protection must be provided by the transport mechanism. All
transports compliant with [RFC5730] provide the needed level of
confidentiality and integrity protections.
8. IANA Considerations 8. IANA Considerations
8.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]. conforming to a registry mechanism described in [RFC3688].
Registration request for the fee namespace: Registration request for the fee namespace:
skipping to change at page 35, line 7 skipping to change at page 34, line 35
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 15 to 16 11.1. Change from 16 to 17
Updated per AD review, all updates were just textual for clarity and
correctness.
11.2. Change from 15 to 16
Updated per AD review and list comments: several grammar corrections; Updated per AD review and list comments: several grammar corrections;
clarification text added to section 3.4.3 and 3.5; and a schema clarification text added to section 3.4.3 and 3.5; and a schema
update for consistency by providing a "lang" attribute to the update for consistency by providing a "lang" attribute to the
<fee:fee> and <fee:credit> "description" attribute detailed in <fee:fee> and <fee:credit> "description" attribute detailed in
section 3.4. section 3.4.
11.2. Change from 14 to 15 11.3. 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.3. Change from 13 to 14 11.4. Change from 13 to 14
Moved RFC 7451 reference from Normative to Informative section. Moved RFC 7451 reference from Normative to Informative section.
11.4. Change from 12 to 13 11.5. 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.5. Change from 11 to 12 11.6. 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.6. Change from 10 to 11 11.7. 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.7. Change from 09 to 10 11.8. 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.8. Change from 08 to 09 11.9. 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.9. Change from 07 to 08 11.10. 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.10. Change from 06 to 07 11.11. 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.11. Change from 05 to 06 11.12. 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.12. Change from 04 to 05 11.13. 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.13. Change from 03 to 04 11.14. 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.14. Change from 02 to 03 11.15. 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.15. Change from 01 to 02 11.16. 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.16. Change from 00 to 01 11.17. 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.17. Change from draft-brown-00 to draft-ietf-regext-fees-00 11.18. 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:2015]
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>.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://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,
 End of changes. 33 change blocks. 
83 lines changed or deleted 69 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/