--- 1/draft-ietf-regext-epp-fees-07.txt 2017-10-10 05:21:55.130908084 -0700 +++ 2/draft-ietf-regext-epp-fees-08.txt 2017-10-10 05:21:55.194909603 -0700 @@ -1,20 +1,20 @@ Registration Protocols Extensions R. Carney Internet-Draft GoDaddy Inc. Intended status: Standards Track G. Brown -Expires: March 25, 2018 CentralNic Group plc +Expires: April 4, 2018 CentralNic Group plc J. Frakes - September 21, 2017 + October 1, 2017 Registry Fee Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-epp-fees-07 + draft-ietf-regext-epp-fees-08 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension mapping for registry fees. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -22,21 +22,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on March 25, 2018. + This Internet-Draft will expire on April 4, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -48,21 +48,21 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 2. Migrating to Newer Versions of This Extension . . . . . . . . 4 3. Extension Elements . . . . . . . . . . . . . . . . . . . . . 4 3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 4 3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . 5 3.3. Validity Periods . . . . . . . . . . . . . . . . . . . . 5 - 3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . 5 + 3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . 6 3.4.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 6 3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 7 3.4.3. Correlation between Refundability and Grace Periods . 7 3.4.4. Applicability . . . . . . . . . . . . . . . . . . . . 7 3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 7 3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . 8 3.7. Classification of Objects . . . . . . . . . . . . . . . . 8 3.8. Phase and Subphase Attributes . . . . . . . . . . . . . . 8 3.9. Reason . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Server Handling of Fee Information . . . . . . . . . . . . . 10 @@ -80,28 +80,29 @@ 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 26 6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 26 7. Security Considerations . . . . . . . . . . . . . . . . . . . 30 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 30 8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 31 9. Implemntation Status . . . . . . . . . . . . . . . . . . . . 31 9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 32 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32 11. Change History . . . . . . . . . . . . . . . . . . . . . . . 33 - 11.1. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 33 - 11.2. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 33 - 11.3. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 33 - 11.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 33 - 11.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 33 - 11.6. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 34 - 11.7. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 34 - 11.8. Change from draft-brown-00 to draft-ietf-regext-fees-00 34 + 11.1. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 33 + 11.2. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 33 + 11.3. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 33 + 11.4. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 33 + 11.5. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 33 + 11.6. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 33 + 11.7. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 34 + 11.8. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 34 + 11.9. Change from draft-brown-00 to draft-ietf-regext-fees-00 34 12. Normative References . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 1. Introduction Historically, domain name registries have applied a simple fee structure for billable transactions, namely a basic unit price applied to domain , , and RGP [RFC3915] restore commands. Given the relatively small number of EPP servers to which EPP clients have been required to connect, it has generally @@ -385,22 +387,22 @@ MUST return data (including the phase/subphase attribute(s)) of the currently active phase/subphase. If the client contains no phase/subphase attributes and the server has more than one active phase/subphase combination the server MUST respond with a 2003 "Required parameter missing" error. If the client contains no phase/subphase attributes and the server is currently in a "quiet period" (e.g. not accepting registrations or applications) the server MUST return data consistent - with the "open" general availability phase (the default phase) and - the server MUST return "open" as the phase. + with the default general availability phase (e.g. "open" or "claims") + including the appropriate phase/subphase attribute(s). If the client contains a phase attribute with no subphase and the server has only one active subphase (or no subphase) of this phase, the server MUST return data (including the phase/ subphase attribute(s)) of the provided phase and currently active subphase. If the client contains a phase attribute with no subphase and the server has more than one active subphase combination of this phase, the server MUST respond with a 2003 "Required @@ -520,21 +522,21 @@ element and a for each element referenced in the client command. Each element MUST contain the following child elements: o A element, which MUST match an element referenced in the client command. o A element matching each (unless the "avail" attribute of the if false) that appeared in the corresponding of the client command. This element MAY - have the OPTIONAL "phase" and "subphase" attributes, which MUST + have the OPTIONAL "phase" and "subphase" attributes, which SHOULD match the same attributes in the corresponding element of the client command if sent by the client. The element also has an OPTIONAL "avail" attribute which is a boolean. If the value of this attribute evaluates to false, this indicates that the server cannot calculate the relevant fees, because the object, command, currency, period, class or some combination is invalid per server policy. If "avail" is false then the element MUST contain a element (as described in Section 3.9) and the server MAY eliminate some or all of the @@ -1426,87 +1428,92 @@ o Seth Goldman of Google o Klaus Malorny and Michael Bauland of Knipp o Jody Kolker, Joe Snitker and Kevin Allendorf of Go Daddy o Michael Holloway of Com Laude o Santosh Kalsangrah of Impetus Infotech o Alex Mayrhofer of Nic.at o Thomas Corte of Knipp Medien und Kommunikation GmbH 11. Change History -11.1. Change from 06 to 07 +11.1. Change from 07 to 08 + + Updated section 3.8 and 5.1.1 to provide clarity on server processing + and response of various scenarios (i.e. "quiet" period processing). + +11.2. Change from 06 to 07 Updated section 3.8 and 4.0 to provide clarity on server processing and response of various scenarios. -11.2. Change from 05 to 06 +11.3. Change from 05 to 06 Updated scheme to version 0.23 to allow the return of no element(s) if an error situation occurs. Edited section 3.8 extensively after input from interim meeting and REGEXT F2F meeting at IETF-99. Added normative reference for draft-ietf- eppext-launchphase. -11.3. Change from 04 to 05 +11.4. Change from 04 to 05 Updated scheme to version 0.21 to support the lang attribute for the reason element of the objectCDType and the commandType types as well as to add the update command to the commandEnum type. Updated section 3.1 to include language for the custom command. Added section 3.9 to provide a description of the element. Fixed typos and added clarification text on when client fee is less than server fee in section 4. Additionally, I added description pointers to appropriate Section 3 definitions for element clarity throughout the document. -11.4. Change from 03 to 04 +11.5. Change from 03 to 04 Updated scheme to version 0.19 to correct typos and to replace the commandTypeValue type with the commandEnum type and customName attribute for stricter validation. Updated various text for grammar and clarity. Added text to section 4 clarifying the response when the client provided no fee extension but the server was expecting the extension. -11.5. Change from 02 to 03 +11.6. Change from 02 to 03 Updated scheme to version 0.17 to simplify the check command syntax. Moved fee avail to objectCDType to allow fast failing on error situations. Removed the objectCheckType as it was no longer being used. Updated examples to reflect these scheme changes. Added language for server failing a if the passed by the client is less than the server fee. -11.6. Change from 01 to 02 +11.7. Change from 01 to 02 Updated scheme to version 0.15 to fix errors in CommandType, objectCDType, transformCommandType and transformResultType definitions. -11.7. Change from 00 to 01 +11.8. Change from 00 to 01 Added Roger Carney as author to finish draft. Moved Formal Syntax section to main level numbering. Various grammar, typos, and administrative edits for clarity. Removed default value for the "applied" attribute of so that it can truly be optional. Added support for the command to return a element as well. Modified default response on the command for the optional 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 command, the 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. -11.8. Change from draft-brown-00 to draft-ietf-regext-fees-00 +11.9. Change from draft-brown-00 to draft-ietf-regext-fees-00 Updated to be REGEXT WG document. 12. Normative References [I-D.ietf-regext-launchphase] Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)", draft- ietf-regext-launchphase-05 (work in progress), June 2017.