--- 1/draft-ietf-regext-epp-fees-09.txt 2018-03-05 15:14:25.535691507 -0800 +++ 2/draft-ietf-regext-epp-fees-10.txt 2018-03-05 15:14:25.603693135 -0800 @@ -1,20 +1,20 @@ Registration Protocols Extensions R. Carney Internet-Draft GoDaddy Inc. Intended status: Standards Track G. Brown -Expires: July 23, 2018 CentralNic Group plc +Expires: September 6, 2018 CentralNic Group plc J. Frakes - January 19, 2018 + March 5, 2018 Registry Fee Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-epp-fees-09 + draft-ietf-regext-epp-fees-10 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 July 23, 2018. + This Internet-Draft will expire on September 6, 2018. Copyright Notice Copyright (c) 2018 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,64 +48,64 @@ 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 . . . . . . . . . . . . . . . . . . . . 6 + 3.4. Fees and Credits . . . . . . . . . . . . . . . . . . . . 5 3.4.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 6 - 3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 7 + 3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 6 3.4.3. Correlation between Refundability and Grace Periods . 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 . . . . . . . . . . . . . 11 + 4. Server Handling of Fee Information . . . . . . . . . . . . . 10 5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 11 5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 11 5.1.1. EPP Command . . . . . . . . . . . . . . . . . 11 - 5.1.1.1. Server Handling of Elements . . . . . . . . . . . 15 - 5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 16 + 5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 15 5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 17 5.2.1. EPP Command . . . . . . . . . . . . . . . . 17 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 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 31 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 31 - 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 08 to 09 . . . . . . . . . . . . . . . . . . 33 - 11.2. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 33 - 11.3. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 33 - 11.4. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 33 - 11.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 33 - 11.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 34 - 11.7. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 34 - 11.8. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 34 - 11.9. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 34 - 11.10. Change from draft-brown-00 to draft-ietf-regext-fees-00 35 - 12. Normative References . . . . . . . . . . . . . . . . . . . . 35 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 + 8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 32 + 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 32 + 9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 33 + 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33 + 11. Change History . . . . . . . . . . . . . . . . . . . . . . . 34 + 11.1. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 34 + 11.2. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34 + 11.3. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 34 + 11.4. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 34 + 11.5. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 34 + 11.6. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 34 + 11.7. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35 + 11.8. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35 + 11.9. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35 + 11.10. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 35 + 11.11. Change from draft-brown-00 to draft-ietf-regext-fees-00 36 + 12. Normative References . . . . . . . . . . . . . . . . . . . . 36 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 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 been the case that client operators have been able to obtain details of these fees out-of-band by contacting the server operators. @@ -126,38 +126,29 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. "fee" is used as an abbreviation for "urn:ietf:params:xml:ns:fee- - 0.25". 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 parser and serializer to interpret and output the XML documents. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol. - (Note to RFC Editor: remove the following paragraph before - publication as an RFC.) - - The XML namespace prefix above contains a version number, - specifically "0.25". This version number will increment with - successive versions of this document, and will reach 1.0 if and when - this document is published as an RFC. This permits clients to - distinguish which version of the extension a server has implemented. - 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 clients to progressively update their implementations when a new version of the extension is deployed. Servers SHOULD (for a temporary migration period) provide support for @@ -188,44 +179,44 @@ o "create" indicating a command as defined in [RFC5730]; o "delete" indicating a command as defined in [RFC5730]; o "renew" indicating a command as defined in [RFC5730]; o "update" indicating a command as defined in [RFC5730]; o "transfer" indicating a command as defined in [RFC5730]; o If the server supports the Registry Grace Period Mapping [RFC3915], then the server MUST also support the "restore" value as defined in [RFC3915]; - o "custom" indicating a custom command that uses the customName + o "custom" indicating a custom command that uses the "customName" attribute to define the custom operation. The element MAY have an OPTIONAL "phase" attribute - specifying a launch phase as described in [draft-ietf-eppext- - launchphase]. It may also contain an OPTIONAL "subphase" attribute - identifying the custom or sub-phase as described in [draft-ietf- - eppext-launchphase]. + specifying a launch phase as described in [RFC8334]. It may also + contain an OPTIONAL "subphase" attribute identifying the custom or + sub-phase as described in [RFC8334]. 3.2. Currency Codes The element is used to indicate which currency fees are charged in. This value of this element MUST be a three-character currency code from [ISO4217]. Note that ISO 4217 provides the special "XXX" code, which MAY be used if the server uses a non-currency based system for assessing fees, such as a system of credits. The use of elements in client commands is OPTIONAL: if a element is not present in a command, the server MUST - determine the currency based on the client's account settings which - MUST be agreed by the client and server via an out-of-band channel. - However, the element MUST be present in responses. + determine the currency based on the server default currency or based + on the client's account settings which are agreed to by the client + and server via an out-of-band channel. However, the + element MUST be present in responses. Servers SHOULD NOT perform a currency conversion if a client uses an incorrect currency code. Servers SHOULD return a 2004 "Parameter value range" error instead. 3.3. Validity Periods When querying for fee information using the command, the element is used to indicate the units to be added to the registration period of objects by the , and @@ -273,36 +264,36 @@ deducted from the client's account. The element can take a "description" attribute as described above. No other attributes are defined for this element. 3.4.1. Refunds elements MAY have an OPTIONAL "refundable" attribute which takes a boolean value. Fees may be refunded under certain circumstances, such as when a domain application is rejected (as - described in [draft-ietf-eppext-launchphase]) or when an object is - deleted during the relevant Grace Period (see below). + described in [RFC8334]) or when an object is deleted during the + relevant Grace Period (see below). If the "refundable" attribute is omitted, then clients SHOULD NOT make any assumption about the refundability of the fee. 3.4.2. Grace Periods [RFC3915] describes a system of "grace periods", which are time periods following a billable transaction during which, if an object is deleted, the client receives a refund. The "grace-period" attribute MAY be used to indicate the relevant grace period for a fee. If a server implements the Registry Grace - Period extension, it MUST specify the grace period for all relevant - transactions. + Period extension [RFC3915], it MUST specify the grace period for all + relevant transactions. If the "grace-period" attribute is omitted, then clients SHOULD NOT make any assumption about the grace period of the fee. 3.4.3. Correlation between Refundability and Grace Periods If a element has a "grace-period" attribute then it MUST also be refundable. If the "refundable" attribute of a element is false then it MUST NOT have a "grace-period" attribute. @@ -321,21 +312,21 @@ 3.5. Account Balance The element is an OPTIONAL element which MAY be included in server responses to transform commands. If present, it can be used by the client to determine the remaining credit at the server. Whether or not the is included in responses is a matter of server policy. However, if a server chooses to offer support for this element, it MUST be included in responses to all "transform" or - billable commands (ie , , , , + billable commands (e.g. , , , , ). The value of the MAY be negative. A negative balance indicates that the server has extended a line of credit to the client (see below). If a server includes a element in response to transform commands, the value of the element MUST reflect the client's account balance after any fees or credits associated with that command have been applied. @@ -346,21 +337,21 @@ with a negative value, then the server has extended a line of credit to the client. A server MAY also include a element in responses which indicates the maximum credit available to a client. A server MAY reject certain transactions if the absolute value of the is equal to or exceeds the value of the element. Whether or not the is included in responses is a matter of server policy. However, if a server chooses to offer support for this element, it MUST be included in responses to all - "transform" commands (ie , , , , + "transform" commands (e.g. , , , , ). 3.7. Classification of Objects 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. The element, which MAY appear in and transform responses, is used to indicate the classification of an object. If a server makes use of this element, it should provide clients with @@ -369,23 +360,22 @@ 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]. These - attributes are used as filters that should refine the server - processing. + phase as described in [RFC8334]. 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. @@ -408,34 +398,34 @@ 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 parameter missing" error. If the client contains a subphase with no phase attribute the server MUST respond with a 2003 "Required parameter missing" error. If the client contains a phase attribute not defined in - [draft-ietf-eppext-launchphase] or not supported by server the server - MUST respond with a 2004 "Parameter value range" error. + [RFC8334] or not supported by server the server MUST respond with a + 2004 "Parameter value range" error. If the client contains a subphase attribute (or phase/ subphase combination) not supported by server the server MUST respond with a 2004 "Parameter value range" error. 3.9. Reason The element is used to provide server specific text in an effort to better explain why a command did not complete as the client expected. An OPTIONAL "lang" attribute MAY be present to identify the language of the returned text and has a default value of - "en" English. + "en" (English). The element can be used within the server response element or within the element. If the server cannot calculate the relevant fees, because the object, command, currency, period, class or some combination is invalid per server policy, the server has two ways of handling error processing of element(s): 1. Fast-fail - The server, upon error identification, MAY stop @@ -474,33 +464,33 @@ Depending on server policy, a client MAY be required to include the 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. + same domain object. - 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 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 + 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 + 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 @@ -518,41 +508,42 @@ that defines additional elements for the EPP command to provide fee information along with the availability information of the EPP command. The command MAY contain an element which MAY contain a element. The element MAY contain one element and MUST contain one or more elements. The element(s) contain(s) a "name" attribute (see - Section 3.1), an OPTIONAL "phase" attribute, and an OPTIONAL + Section 3.1), an OPTIONAL "standard" attribute with a default value + of false (0), an OPTIONAL "phase" attribute, and an OPTIONAL "subphase" attribute (see Section 3.8). The element(s) MAY have the following child elements: o An OPTIONAL element (as described in Section 3.3). Example command: C: C: C: C: C: C: example.com C: example.net C: example.xyz C: C: C: - C: + C: C: USD C: C: 2 C: C: C: C: C: C: C: ABC-12345 @@ -625,24 +616,25 @@ S: S: example.net S: S: S: example.xyz S: S: S: S: S: + S: xmlns:fee="urn:ietf:params:xml:ns:fee-1.0"> S: USD S: S: example.com + S: Premium S: S: 2 S: 10.00 S: S: S: 1 S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: -5.1.1.1. Server Handling of Elements - - Clients MAY include a in the element. There are - two ways in which servers may handle this element: - - 1. If the server supports the concept of tiers or classes of - objects, then the value of this element MUST be validated. If - incorrect for the specified object, the "avail" attribute of the - corresponding element MUST be false. - 2. If the server supports different "types" of object registrations - (such as a "blocking" registration which does not resolve, or - where a registry provides a value-added service that requires an - opt-out to disable), then, as with the first model, the server - MUST validate the value of the element. If the value is - incorrect, the "avail" attribute of the corresponding - element MUST be false, and a element (as described - in Section 3.9) MUST be provided. - - Server operators must provide clear documentation to client operators - which of the above models it supports. - 5.1.2. EPP Transfer Query Command This extension does not add any elements to the EPP query command, but does include elements in the response, when the - extension has been selected during a command. + extension is included in the command service extensions. When the query command has been processed successfully, - the client selected the extension when it logged in, and the client - is authorized by the server to view information about the transfer, - the server MAY include in the section of the EPP response - a element, which contains the following child elements: + the client included the extension in the command service + extensions, and the client is authorized by the server to view + information about the transfer, the server MAY include in the + section of the EPP response a element, + which contains the following child elements: o A element (as described in Section 3.2). + o A element (as described in Section 3.3). o Zero or more elements (as described in Section 3.4) containing the fees that will be charged to the gaining client. o Zero or more elements (as described in Section 3.4) containing the credits that will be refunded to the losing client. Servers SHOULD omit when returning a response to the gaining client, and omit elements when returning a response to the losing client. @@ -768,56 +741,57 @@ S: example.com S: pending S: ClientX S: 2000-06-08T22:00:00.0Z S: ClientY S: 2000-06-13T22:00:00.0Z S: 2002-09-08T22:00:00.0Z S: S: S: - S: + S: S: USD S: 1 S: 5.00 S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 5.2. EPP Transform Commands 5.2.1. EPP Command This extension adds elements to both the EPP command and - response, when the extension has been selected during a - command. + response, when the extension is included in the command + service extensions. When submitting a command to the server, the client MAY include in the element a element which includes the following child elements: o An OPTIONAL element (as described in Section 3.2); o One or more elements (as described in Section 3.4). The server MUST fail the command if the provided by the client is less than the server fee. When the command has been processed successfully, and the - client selected the extension when it logged in, and a fee was - assessed by the server for the transaction, the server MUST include - in the section of the EPP response a - element, which contains the following child elements: + client included the extension in the command service + extensions, and a fee was assessed by the server for the transaction, + the server MUST include in the section of the EPP + response a element, which contains the following child + elements: o A element (as described in Section 3.2); o Zero or more elements (as described in Section 3.4); o Zero or more elements (as described in Section 3.4); o An OPTIONAL element (as described in Section 3.5); o An OPTIONAL element (as described in Section 3.6). Example command: @@ -835,21 +809,21 @@ C: C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: - C: + C: C: USD C: 5.00 C: C: C: ABC-12345 C: C: Example response: S: @@ -860,95 +834,97 @@ S: S: S: S: example.com S: 1999-04-03T22:00:00.0Z S: 2001-04-03T22:00:00.0Z S: S: S: - S: + S: S: USD S: 5.00 S: -5.00 S: 1000.00 S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: 5.2.2. EPP Command This extension does not add any elements to the EPP command, - but does include elements in the response, when the extension has - been selected during the command. + but does include elements in the response, when the extension is + included in the command service extensions. When the command has been processed successfully, and the - client selected the extension when it logged in, the server MAY - include in the section of the EPP response a - element, which contains the following child elements: + client included the extension in the command service + extensions, the server MAY include in the section of the + EPP response a element, which contains the following + child elements: o A element (as described in Section 3.2); o Zero or more elements (as described in Section 3.4); o Zero or more elements (as described in Section 3.4); o An OPTIONAL element (as described in Section 3.5); o An OPTIONAL element (as described in Section 3.6). Example response: S: S: S: S: S: Command completed successfully S: S: S: + S: xmlns:fee="urn:ietf:params:xml:ns:fee-1.0"> S: USD S: -5.00 S: 1005.00 S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: 5.2.3. EPP Command This extension adds elements to both the EPP command and - response, when the extension has been selected during a - command. + response, when the extension is included in the command + service extensions. When submitting a command to the server, the client MAY include in the element a element which includes the following child elements: o An OPTIONAL element (as described in Section 3.2); o One or more elements (as described in Section 3.4). When the command has been processed successfully, and the - client selected the extension when it logged in, the server MAY - include in the section of the EPP response a - element, which contains the following child elements: + client included the extension in the command service + extensions, the server MAY include in the section of the + EPP response a element, which contains the following + child elements: o A element (as described in Section 3.2); o Zero or more elements (as described in Section 3.4); o Zero or more elements (as described in Section 3.4); o An OPTIONAL element (as described in Section 3.5); o An OPTIONAL element (as described in Section 3.6). Example command: @@ -957,21 +933,21 @@ C: C: C: C: example.com C: 2000-04-03 C: 5 C: C: C: - C: + C: C: USD C: 5.00 C: C: C: ABC-12345 C: C: Example response: S: @@ -981,53 +957,54 @@ S: Command completed successfully S: S: S: S: example.com S: 2005-04-03T22:00:00.0Z S: S: S: - S: + S: S: USD S: 5.00 S: 1000.00 S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 5.2.4. EPP Command This extension adds elements to both the EPP command and response, when the value of the "op" attribute of the - command element is "request", and the extension has been selected - during the command. + command element is "request", and the extension is included in the + command service extensions. When submitting a command to the server, the client MAY include in the element a element which includes the following child elements: o An OPTIONAL element (as described in Section 3.2); o One or more elements (as described in Section 3.4). When the command has been processed successfully, and the - client selected the extension when it logged in, the server MAY - include in the section of the EPP response a - element, which contains the following child elements: + client included the extension in the command service + extensions, the server MAY include in the section of the + EPP response a element, which contains the following + child elements: o A element (as described in Section 3.2); o Zero or more elements (as described in Section 3.4); o Zero or more elements (as described in Section 3.4); o An OPTIONAL element (as described in Section 3.5); o An OPTIONAL element (as described in Section 3.6). Example command: @@ -1038,21 +1015,21 @@ C: C: example.com C: 1 C: C: 2fooBAR C: C: C: C: - C: + C: C: USD C: 5.00 C: C: C: ABC-12345 C: C: Example response: S: @@ -1067,51 +1044,52 @@ S: example.com S: pending S: ClientX S: 2000-06-08T22:00:00.0Z S: ClientY S: 2000-06-13T22:00:00.0Z S: 2002-09-08T22:00:00.0Z S: S: S: - S: + S: S: USD S: 5.00 S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 5.2.5. EPP Command This extension adds elements to both the EPP command and - response, when the extension has been selected during the - command. + response, when the extension is included in the command + service extensions. When submitting a command to the server, the client MAY include in the element a element which includes the following child elements: o An OPTIONAL element (as described in Section 3.2); o One or more elements (as described in Section 3.4). When the command has been processed successfully, and the - client selected the extension when it logged in, the server MAY - include in the section of the EPP response a - element, which contains the following child elements: + client included the extension in the command service + extensions, the server MAY include in the section of the + EPP response a element, which contains the following + child elements: o A element (as described in Section 3.2); o Zero or more elements (as described in Section 3.4); o Zero or more elements (as described in Section 3.4); o An OPTIONAL element (as described in Section 3.5); o An OPTIONAL element (as described in Section 3.6). Example command: @@ -1121,38 +1099,38 @@ C: C: C: example.com C: C: sh8013 C: C: C: C: - C: + C: C: USD C: 5.00 C: C: C: ABC-12345 C: C: Example response: S: S: S: S: S: Command completed successfully S: S: - S: + S: S: USD S: 5.00 S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: @@ -1162,36 +1140,65 @@ One schema is presented here that is the EPP Fee Extension schema. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. 6.1. Fee Extension Schema + Copyright (c) 2018 IETF Trust and the persons identified as authors + of the code. All rights reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + 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 Extensible Provisioning Protocol v1.0 Fee Extension - @@ -1379,54 +1387,62 @@ security services beyond those described by EPP [RFC5730], the EPP domain name mapping [RFC5731], and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. 8. IANA Considerations 8.1. XML Namespace This document uses URNs to describe XML namespaces and XML schemas - conforming to a registry mechanism described in [RFC3688]. The - following URI assignment is requested of IANA: + conforming to a registry mechanism described in [RFC3688]. - URI: ietf:params:xml:ns:fee-0.25 + Registration request for the fee namespace: - Registrant Contact: See the "Author's Address" section of this - document. + URI: urn:ietf:params:xml:ns:fee-1.0 + + Registrant Contact: IESG. + + XML: None. Namespace URIs do not represent an XML specification. + + Registration request for the fee schema: + + URI: urn:ietf:params:xml:schema:fee-1.0 + + Registrant Contact: IESG. XML: See the "Formal Syntax" section of this document. 8.2. EPP Extension Registry The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in [RFC7451]. The details of the registration are as follows: - Name of Extension: EPP Fee Extension + Name of Extension: Registry Fee Extension for the Extensible + Provisioning Protocol (EPP) Document status: Standards Track Reference: (insert reference to RFC version of this document) - Registrant Name and Email Address: See the "Author's Address" section - of this document. + Registrant Name and Email Address: IESG, . TLDs: any IPR Disclosure: none Status: active Notes: none -9. Implemntation Status +9. Implementation Status Note to RFC Editor: Please remove this section and the reference to [RFC6982] before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in [RFC6982]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation @@ -1477,113 +1493,115 @@ 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 08 to 09 +11.1. Change from 09 to 10 + + Updated document per Working Group Last Call comments. Updated + schema to version 1.0 in anticipation of standardization, no changes + were made to the latest, 0.25, schema. Made minor textual changes + throughout for enhanced clarity per WGLC comments. + +11.2. Change from 08 to 09 Updated scheme to version 0.25 to allow tighter checking on by splitting the client and server definitions, moved the class element from the command to the object level and added an optional standard attribute to the command element. Also updated section 3.1 for clarity on name attribute; updated section 3.9 for clarity on uses of ; removed second paragraph in section 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. -11.2. Change from 07 to 08 +11.3. 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.3. Change from 06 to 07 +11.4. Change from 06 to 07 Updated section 3.8 and 4.0 to provide clarity on server processing and response of various scenarios. -11.4. Change from 05 to 06 +11.5. 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.5. Change from 04 to 05 +11.6. 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.6. Change from 03 to 04 +11.7. 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.7. Change from 02 to 03 +11.8. 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.8. Change from 01 to 02 +11.9. Change from 01 to 02 Updated scheme to version 0.15 to fix errors in CommandType, objectCDType, transformCommandType and transformResultType definitions. -11.9. Change from 00 to 01 +11.10. 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.10. Change from draft-brown-00 to draft-ietf-regext-fees-00 +11.11. 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 @@ -1602,20 +1620,25 @@ [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, . + [RFC8334] Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping + for the Extensible Provisioning Protocol (EPP)", RFC 8334, + DOI 10.17487/RFC8334, March 2018, + . + Authors' Addresses Roger Carney GoDaddy Inc. 14455 N. Hayden Rd. #219 Scottsdale, AZ 85260 US Email: rcarney@godaddy.com URI: http://www.godaddy.com