Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-fees-18
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8748.
|
|
---|---|---|---|
Authors | Roger Carney , Gavin Brown , Jothan Frakes | ||
Last updated | 2019-09-19 (Latest revision 2019-09-09) | ||
Replaces | draft-brown-epp-fees | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
SECDIR Telechat review
by Yoav Nir
Has nits
GENART Last Call review
(of
-16)
by Stewart Bryant
Ready w/issues
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | James Gould | ||
Shepherd write-up | Show Last changed 2018-08-06 | ||
IESG | IESG state | Became RFC 8748 (Proposed Standard) | |
Consensus boilerplate | Yes | ||
Telechat date |
(None)
Needs a YES. Needs 7 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Barry Leiba | ||
Send notices to | James Gould <jgould@verisign.com> | ||
IANA | IANA review state | IANA OK - Actions Needed |
draft-ietf-regext-epp-fees-18
gt; element (as described in Section 3.6). Example <update> command: C: <?xml version="1.0" encoding="utf-8" standalone="no"?> C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <update> C: <domain:update C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: <domain:chg> C: <domain:registrant>sh8013</domain:registrant> C: </domain:chg> C: </domain:update> C: </update> C: <extension> C: <fee:update xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"> C: <fee:currency>USD</fee:currency> C: <fee:fee>5.00</fee:fee> C: </fee:update> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C: </epp> Carney, et al. Expires March 11, 2020 [Page 26] Internet-Draft Registry Fee Extension September 2019 Example <update> response: S: <?xml version="1.0" encoding="utf-8" standalone="no"?> S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <extension> S: <fee:updData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"> S: <fee:currency>USD</fee:currency> S: <fee:fee>5.00</fee:fee> S: </fee:updData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S: </epp> 6. Formal Syntax 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 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. BEGIN <?xml version="1.0" encoding="utf-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" targetNamespace="urn:ietf:params:xml:ns:epp:fee-1.0" elementFormDefault="qualified"> Carney, et al. Expires March 11, 2020 [Page 27] Internet-Draft Registry Fee Extension September 2019 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:domain-1.0" /> <annotation> <documentation> Extensible Provisioning Protocol v1.0 Fee Extension </documentation> </annotation> <!-- Child elements found in EPP commands and responses --> <element name="check" type="fee:checkType" /> <element name="chkData" type="fee:chkDataType" /> <element name="create" type="fee:transformCommandType" /> <element name="creData" type="fee:transformResultType" /> <element name="renew" type="fee:transformCommandType" /> <element name="renData" type="fee:transformResultType" /> <element name="transfer" type="fee:transformCommandType" /> <element name="trnData" type="fee:transformResultType" /> <element name="update" type="fee:transformCommandType" /> <element name="updData" type="fee:transformResultType" /> <element name="delData" type="fee:transformResultType" /> <!-- client <check> command --> <complexType name="checkType"> <sequence> <element name="currency" type="fee:currencyType" minOccurs="0" /> <element name="command" type="fee:commandType" minOccurs="1" maxOccurs="unbounded" /> </sequence> </complexType> <complexType name="objectIdentifierType"> <simpleContent> <extension base="eppcom:labelType"> <attribute name="element" type="NMTOKEN" default="name" /> </extension> </simpleContent> </complexType> <!-- server <check> result --> <complexType name="chkDataType"> <sequence> <element name="currency" type="fee:currencyType" /> <element name="cd" type="fee:objectCDType" maxOccurs="unbounded" /> </sequence> Carney, et al. Expires March 11, 2020 [Page 28] Internet-Draft Registry Fee Extension September 2019 </complexType> <complexType name="objectCDType"> <sequence> <element name="objID" type="fee:objectIdentifierType" /> <element name="class" type="token" minOccurs="0" /> <element name="command" type="fee:commandDataType" minOccurs="0" maxOccurs="unbounded" /> <element name="reason" type="fee:reasonType" minOccurs="0" /> </sequence> <attribute name="avail" type="boolean" default="1" /> </complexType> <!-- general transform (create, renew, update, transfer) command --> <complexType name="transformCommandType"> <sequence> <element name="currency" type="fee:currencyType" minOccurs="0" /> <element name="fee" type="fee:feeType" maxOccurs="unbounded" /> <element name="credit" type="fee:creditType" minOccurs="0" maxOccurs="unbounded" /> </sequence> </complexType> <!-- general transform (create, renew, update) result --> <complexType name="transformResultType"> <sequence> <element name="currency" type="fee:currencyType" minOccurs="0" /> <element name="period" type="domain:periodType" minOccurs="0" /> <element name="fee" type="fee:feeType" minOccurs="0" maxOccurs="unbounded" /> <element name="credit" type="fee:creditType" minOccurs="0" maxOccurs="unbounded" /> <element name="balance" type="fee:balanceType" minOccurs="0" /> <element name="creditLimit" type="fee:creditLimitType" minOccurs="0" /> </sequence> </complexType> <!-- common types --> <simpleType name="currencyType"> <restriction base="string"> <pattern value="[A-Z]{3}" /> </restriction> Carney, et al. Expires March 11, 2020 [Page 29] Internet-Draft Registry Fee Extension September 2019 </simpleType> <complexType name="commandType"> <sequence> <element name="period" type="domain:periodType" minOccurs="0" maxOccurs="1" /> </sequence> <attribute name="name" type="fee:commandEnum"/> <attribute name="customName" type="token"/> <attribute name="phase" type="token" /> <attribute name="subphase" type="token" /> </complexType> <complexType name="commandDataType"> <complexContent> <extension base="fee:commandType"> <sequence> <element name="fee" type="fee:feeType" minOccurs="0" maxOccurs="unbounded" /> <element name="credit" type="fee:creditType" minOccurs="0" maxOccurs="unbounded" /> <element name="reason" type="fee:reasonType" minOccurs="0" /> </sequence> <attribute name="standard" type="boolean" default="0" /> </extension> </complexContent> </complexType> <complexType name="reasonType"> <simpleContent> <extension base="token"> <attribute name="lang" type="language" default="en"/> </extension> </simpleContent> </complexType> <simpleType name="commandEnum"> <restriction base="token"> <enumeration value="create"/> <enumeration value="delete"/> <enumeration value="renew"/> <enumeration value="update"/> <enumeration value="transfer"/> <enumeration value="restore"/> <enumeration value="custom"/> </restriction> </simpleType> Carney, et al. Expires March 11, 2020 [Page 30] Internet-Draft Registry Fee Extension September 2019 <simpleType name="nonNegativeDecimal"> <restriction base="decimal"> <minInclusive value="0" /> </restriction> </simpleType> <simpleType name="negativeDecimal"> <restriction base="decimal"> <maxInclusive value="0" /> </restriction> </simpleType> <complexType name="feeType"> <simpleContent> <extension base="fee:nonNegativeDecimal"> <attribute name="description"/> <attribute name="lang" type="language" default="en"/> <attribute name="refundable" type="boolean" /> <attribute name="grace-period" type="duration" /> <attribute name="applied"> <simpleType> <restriction base="token"> <enumeration value="immediate" /> <enumeration value="delayed" /> </restriction> </simpleType> </attribute> </extension> </simpleContent> </complexType> <complexType name="creditType"> <simpleContent> <extension base="fee:negativeDecimal"> <attribute name="description"/> <attribute name="lang" type="language" default="en"/> </extension> </simpleContent> </complexType> <simpleType name="balanceType"> <restriction base="decimal" /> </simpleType> <simpleType name="creditLimitType"> <restriction base="decimal" /> </simpleType> Carney, et al. Expires March 11, 2020 [Page 31] Internet-Draft Registry Fee Extension September 2019 </schema> END 7. Security Considerations The mapping extensions described in this document do not provide any 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. 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.1. XML Namespace This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. Registration request for the fee namespace: URI: urn:ietf:params:xml:ns:epp: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:epp: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: Registry Fee Extension for the Extensible Provisioning Protocol (EPP) Document status: Standards Track Carney, et al. Expires March 11, 2020 [Page 32] Internet-Draft Registry Fee Extension September 2019 Reference: (insert reference to RFC version of this document) Registrant Name and Email Address: IESG, <iesg@ietf.org> TLDs: Any IPR Disclosure: None Status: Active Notes: None 9. Implementation Status Note to RFC Editor: Please remove this section and the reference to [RFC7942] 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 [RFC7942]. 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 here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". 9.1. RegistryEngine EPP Service Organization: CentralNic Name: RegistryEngine EPP Service Description: Generic high-volume EPP service for gTLDs, ccTLDs and SLDs Carney, et al. Expires March 11, 2020 [Page 33] Internet-Draft Registry Fee Extension September 2019 Level of maturity: Deployed in CentralNic's production environment as well as two other gTLD registry systems, and two ccTLD registry systems. Coverage: All aspects of the protocol are implemented. Licensing: Proprietary In-House software Contact: epp@centralnic.com URL: https://www.centralnic.com 10. Acknowledgements The authors wish to thank the following persons for their feedback and suggestions: o James Gould of Verisign Inc o Luis Munoz of ISC o Michael Young of Architelos o Ben Levac and Jeff Eckhaus of Demand Media 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 17 to 18 Corrected erroneous edit left in place in previous revision (17), reverted text back to original text (revision 16) in section 3.4. 11.2. Change from 16 to 17 Updated per AD review, all updates were just textual for clarity and correctness. 11.3. Change from 15 to 16 Updated per AD review and list comments: several grammar corrections; clarification text added to section 3.4.3 and 3.5; and a schema update for consistency by providing a "lang" attribute to the <fee:fee> and <fee:credit> "description" attribute detailed in section 3.4. Carney, et al. Expires March 11, 2020 [Page 34] Internet-Draft Registry Fee Extension September 2019 11.4. Change from 14 to 15 Updated schema, moving the "standard" attribute of the "commandDataType" inside the <extension> block. 11.5. Change from 13 to 14 Moved RFC 7451 reference from Normative to Informative section. 11.6. Change from 12 to 13 Updated XML namespace and schema registration to be "epp" scoped - 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 from urn:ietf:params:xml:schema:fee-1.0 to urn:ietf:params:xml:schema:epp:fee-1.0. 11.7. Change from 11 to 12 Updated references to current version of documents and moved the "standard" attribute from the check command (commandType) to the check response (commandDataType). 11.8. Change from 10 to 11 Updated document per Working Group Last Call comments. Made minor textual changes throughout for enhanced clarity per WGLC comments. 11.9. 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.10. Change from 08 to 09 Updated scheme to version 0.25 to allow tighter checking on <fee:command> 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 <fee:reason>; 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. Carney, et al. Expires March 11, 2020 [Page 35] Internet-Draft Registry Fee Extension September 2019 11.11. 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.12. Change from 06 to 07 Updated section 3.8 and 4.0 to provide clarity on server processing and response of various scenarios. 11.13. Change from 05 to 06 Updated scheme to version 0.23 to allow the return of no <fee:command> 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.14. 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 <fee:reason> 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.15. 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 <check> response when the client provided no fee extension but the server was expecting the extension. 11.16. 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 <create> if the <fee:fee> passed by the client is less than the server fee. Carney, et al. Expires March 11, 2020 [Page 36] Internet-Draft Registry Fee Extension September 2019 11.17. Change from 01 to 02 Updated scheme to version 0.15 to fix errors in CommandType, objectCDType, transformCommandType and transformResultType definitions. 11.18. 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 <fee:fee> so that it can truly be optional. Added support for the <delete> command to return a <fee:fee> element as well. Modified default response on the <check> command for the optional <fee:period> 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 <check> command, the <check> 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.19. Change from draft-brown-00 to draft-ietf-regext-fees-00 Updated to be REGEXT WG document. 12. References 12.1. Normative References [ISO4217:2015] International Organization for Standardization, "Codes for the representation of currencies", August 2015, <https://www.iso.org/standard/64758.html>. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-editor.org/info/rfc3688>. Carney, et al. Expires March 11, 2020 [Page 37] Internet-Draft Registry Fee Extension September 2019 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, DOI 10.17487/RFC3915, September 2004, <https://www.rfc-editor.org/info/rfc3915>. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, <https://www.rfc-editor.org/info/rfc5730>. [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, <https://www.rfc-editor.org/info/rfc5731>. [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, July 2016, <https://www.rfc-editor.org/info/rfc7942>. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>. [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, <https://www.rfc-editor.org/info/rfc8334>. 12.2. Informative References [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, <https://www.rfc-editor.org/info/rfc7451>. Authors' Addresses Roger Carney GoDaddy Inc. 14455 N. Hayden Rd. #219 Scottsdale, AZ 85260 US Email: rcarney@godaddy.com URI: http://www.godaddy.com Carney, et al. Expires March 11, 2020 [Page 38] Internet-Draft Registry Fee Extension September 2019 Gavin Brown CentralNic Group plc 35-39 Moorgate London, England EC2R 6AR GB Phone: +44 20 33 88 0600 Email: gavin.brown@centralnic.com URI: http://www.centralnic.com Jothan Frakes Email: jothan@jothan.com URI: http://jothan.com Carney, et al. Expires March 11, 2020 [Page 39]