--- 1/draft-ietf-regext-epp-fees-06.txt 2017-09-22 14:13:27.590848292 -0700 +++ 2/draft-ietf-regext-epp-fees-07.txt 2017-09-22 14:13:27.654849837 -0700 @@ -1,51 +1,51 @@ Registration Protocols Extensions R. Carney Internet-Draft GoDaddy Inc. Intended status: Standards Track G. Brown -Expires: February 4, 2018 CentralNic Group plc +Expires: March 25, 2018 CentralNic Group plc J. Frakes - August 3, 2017 + September 21, 2017 Registry Fee Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-epp-fees-06 + draft-ietf-regext-epp-fees-07 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. 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 http://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 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 February 4, 2018. + This Internet-Draft will expire on March 25, 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 - (http://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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 @@ -62,46 +62,46 @@ 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 5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 10 5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 10 5.1.1. EPP Command . . . . . . . . . . . . . . . . . 10 - 5.1.1.1. Server Handling of Elements . . . . . . . . . . . 14 + 5.1.1.1. Server Handling of Elements . . . . . . . . . . . 15 5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 15 5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16 5.2.1. EPP Command . . . . . . . . . . . . . . . . 16 5.2.2. EPP Command . . . . . . . . . . . . . . . . 19 5.2.3. EPP Command . . . . . . . . . . . . . . . . . 20 5.2.4. EPP Command . . . . . . . . . . . . . . . 22 5.2.5. EPP Command . . . . . . . . . . . . . . . . 24 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 05 to 06 . . . . . . . . . . . . . . . . . . 33 - 11.2. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 33 - 11.3. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 33 - 11.4. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 33 - 11.5. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 33 - 11.6. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 34 - 11.7. Change from draft-brown-00 to draft-ietf-regext-fees-00 34 - + 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 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 @@ -365,39 +365,42 @@ list. Servers which make use of this element MUST use a element with the value "standard" for all objects that are subject to the standard or default fee. 3.8. Phase and Subphase Attributes The element has two attributes, phase and subphase, that provide additional information related to a specific launch - phase as described in [draft-ietf-eppext-launchphase]. + phase as described in [draft-ietf-eppext-launchphase]. These + attributes are used as filters that should refine the server + processing. If the client contains a server supported combination of phase/subphase the server MUST return fee data (including the phase/subphase attribute(s)) for the specific combination. If the client contains no phase/subphase attributes and the server has only one active phase/subphase combination the server 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 general availability phase. + with the "open" general availability phase (the default phase) and + the server MUST return "open" as the phase. 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 @@ -428,20 +431,30 @@ extension elements described in this document for certain transform commands. Servers must provide clear documentation to clients about the circumstances in which this extension must be used. The server MUST return avail="0" in its response to a command for any domain name in the command that does not include the extension for which the server would likewise fail a domain command when no extension is provided for that same domain name. + If a server receives a command from a client which results in + no possible fee combination but where a fee is required, the server + MUST set the "avail" attribute of the element to false and + provide a . + + If a server receives a command from a client which results in + an ambiguous result (i.e. multiple possible fee combinations) the + server MUST reject the command with a 2003 "Required parameter + missing" error. + If a server receives a command from a client which does not include the fee extension data elements required by the server for that command, then the server MUST respond with a 2003 "Required parameter missing" error. If the currency or total fee provided by the client is less than the server's own calculation of the fee for that command, then the server MUST reject the command with a 2004 "Parameter value range" error. 5. EPP Command Mapping @@ -1413,123 +1426,128 @@ 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 05 to 06 +11.1. 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 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.2. Change from 04 to 05 +11.3. 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.3. Change from 03 to 04 +11.4. 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.4. Change from 02 to 03 +11.5. 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.5. Change from 01 to 02 +11.6. Change from 01 to 02 Updated scheme to version 0.15 to fix errors in CommandType, objectCDType, transformCommandType and transformResultType definitions. -11.6. Change from 00 to 01 +11.7. 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.7. Change from draft-brown-00 to draft-ietf-regext-fees-00 +11.8. 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. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, - . + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, - . + . [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, DOI 10.17487/RFC3915, September 2004, - . + . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, - . + . [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, - . + . [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", RFC 6982, DOI 10.17487/RFC6982, July 2013, - . + . [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, - February 2015, . + February 2015, . Authors' Addresses Roger Carney GoDaddy Inc. 14455 N. Hayden Rd. #219 Scottsdale, AZ 85260 US Email: rcarney@godaddy.com