draft-ietf-regext-epp-fees-11.txt   draft-ietf-regext-epp-fees-12.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: October 12, 2018 CentralNic Group plc Expires: January 26, 2019 CentralNic Group plc
J. Frakes J. Frakes
April 10, 2018 July 25, 2018
Registry Fee Extension for the Extensible Provisioning Protocol (EPP) Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-fees-11 draft-ietf-regext-epp-fees-12
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for registry fees. extension mapping for registry fees.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 October 12, 2018. This Internet-Draft will expire on January 26, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Migrating to Newer Versions of This Extension . . . . . . . . 4 2. Migrating to Newer Versions of This Extension . . . . . . . . 4
3. Extension Elements . . . . . . . . . . . . . . . . . . . . . 4 3. Extension Elements . . . . . . . . . . . . . . . . . . . . . 4
3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 4 3.1. Client Commands . . . . . . . . . . . . . . . . . . . . . 4
3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . 5 3.2. Currency Codes . . . . . . . . . . . . . . . . . . . . . 5
3.3. Validity Periods . . . . . . . . . . . . . . . . . . . . 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.1. Refunds . . . . . . . . . . . . . . . . . . . . . . . 6
3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 6 3.4.2. Grace Periods . . . . . . . . . . . . . . . . . . . . 7
3.4.3. Correlation between Refundability and Grace Periods . 7 3.4.3. Correlation between Refundability and Grace Periods . 7
3.4.4. Applicability . . . . . . . . . . . . . . . . . . . . 7 3.4.4. Applicability . . . . . . . . . . . . . . . . . . . . 7
3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 7 3.5. Account Balance . . . . . . . . . . . . . . . . . . . . . 7
3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . 8 3.6. Credit Limit . . . . . . . . . . . . . . . . . . . . . . 8
3.7. Classification of Objects . . . . . . . . . . . . . . . . 8 3.7. Classification of Objects . . . . . . . . . . . . . . . . 8
3.8. Phase and Subphase Attributes . . . . . . . . . . . . . . 8 3.8. Phase and Subphase Attributes . . . . . . . . . . . . . . 8
3.9. Reason . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.9. Reason . . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Server Handling of Fee Information . . . . . . . . . . . . . 10 4. Server Handling of Fee Information . . . . . . . . . . . . . 11
5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 11 5. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 11
5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 11 5.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 11
5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 11 5.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 11
5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 15 5.1.2. EPP Transfer Query Command . . . . . . . . . . . . . 16
5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 17 5.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 17
5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 17 5.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 17
5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19 5.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19
5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20 5.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20
5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 22 5.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 22
5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 24 5.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 24
6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 26 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 26 6.1. Fee Extension Schema . . . . . . . . . . . . . . . . . . 26
7. Security Considerations . . . . . . . . . . . . . . . . . . . 31 7. Security Considerations . . . . . . . . . . . . . . . . . . . 31
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 31 8.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 31
8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 32 8.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 32
9. Implementation Status . . . . . . . . . . . . . . . . . . . . 32 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 32
9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 33 9.1. RegistryEngine EPP Service . . . . . . . . . . . . . . . 33
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33
11. Change History . . . . . . . . . . . . . . . . . . . . . . . 34 11. Change History . . . . . . . . . . . . . . . . . . . . . . . 34
11.1. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 34 11.1. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 34
11.2. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 34 11.2. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 34
11.3. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34 11.3. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 34
11.4. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 34 11.4. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34
11.5. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 34 11.5. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 34
11.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 34 11.6. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 34
11.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 34 11.7. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 34
11.8. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35 11.8. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 35
11.9. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35 11.9. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35
11.10. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35 11.10. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35
11.11. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 35 11.11. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35
11.12. Change from draft-brown-00 to draft-ietf-regext-fees-00 36 11.12. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 35
11.13. Change from draft-brown-00 to draft-ietf-regext-fees-00 36
12. Normative References . . . . . . . . . . . . . . . . . . . . 36 12. Normative References . . . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37
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]
restore commands. Given the relatively small number of EPP servers restore commands. Given the relatively small number of EPP servers
to which EPP clients have been required to connect, it has generally to which EPP clients have been required to connect, it has generally
been the case that client operators have been able to obtain details been the case that client operators have been able to obtain details
of these fees out-of-band by contacting the server operators. of these fees out-of-band by contacting the server operators.
skipping to change at page 3, line 35 skipping to change at page 3, line 36
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping
provides a mechanism by which EPP clients may query the fees and provides a mechanism by which EPP clients may query the fees and
credits associated with various billable transactions, and obtain credits associated with various billable transactions, and obtain
their current account balance. their current account balance.
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented in order to develop a conforming character case presented in order to develop a conforming
implementation. implementation.
"fee" is used as an abbreviation for "urn:ietf:params:xml:ns:fee- "fee" is used as an abbreviation for "urn:ietf:params:xml:ns:fee-
1.0". 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 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.
skipping to change at page 11, line 44 skipping to change at page 12, line 11
that defines additional elements for the EPP <check> command to that defines additional elements for the EPP <check> command to
provide fee information along with the availability information of provide fee information along with the availability information of
the EPP <check> command. the EPP <check> command.
The command MAY contain an <extension> element which MAY contain a The command MAY contain an <extension> element which MAY contain a
<fee:check> element. The <fee:check> element MAY contain one <fee:check> element. The <fee:check> element MAY contain one
<fee:currency> element and MUST contain one or more <fee:command> <fee:currency> element and MUST contain one or more <fee:command>
elements. elements.
The <fee:command> element(s) contain(s) a "name" attribute (see The <fee:command> element(s) contain(s) a "name" attribute (see
Section 3.1), an OPTIONAL "standard" attribute with a default value Section 3.1), an OPTIONAL "phase" attribute, and an OPTIONAL
of false (0) (see section 3.7), an OPTIONAL "phase" attribute, and an "subphase" attribute (see Section 3.8). The <fee:command> element(s)
OPTIONAL "subphase" attribute (see Section 3.8). The <fee:command> MAY have the following child elements:
element(s) MAY have the following child elements:
o An OPTIONAL <fee:period> element (as described in Section 3.3). o An OPTIONAL <fee:period> element (as described in Section 3.3).
Example <check> command: Example <check> command:
C: <?xml version="1.0" encoding="utf-8" standalone="no"?> C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <check> C: <check>
C: <domain:check C: <domain:check
skipping to change at page 12, line 48 skipping to change at page 13, line 11
<check> command. <check> command.
Each <fee:cd> element MUST contain the following child elements: Each <fee:cd> element MUST contain the following child elements:
o A <fee:objID> element, which MUST match an element referenced in o A <fee:objID> element, which MUST match an element referenced in
the client <check> command. the client <check> command.
o An OPTIONAL <fee:class> element (as described in Section 3.7). o An OPTIONAL <fee:class> element (as described in Section 3.7).
o A <fee:command> element matching each <fee:command> (unless the o A <fee:command> element matching each <fee:command> (unless the
"avail" attribute of the <fee:cd> if false) that appeared in the "avail" attribute of the <fee:cd> if false) that appeared in the
corresponding <fee:check> of the client command. This element MAY corresponding <fee:check> of the client command. This element MAY
have the OPTIONAL "phase" and "subphase" attributes, which SHOULD have the OPTIONAL "standard" attribute, with a default value of
match the same attributes in the corresponding <fee:command> "0" (or "false"), which indicates whether the fee matches the fee
element of the client command if sent by the client. of the "standard" classification (see section 3.7). This element
MAY have the OPTIONAL "phase" and "subphase" attributes, which
SHOULD match the same attributes in the corresponding
<fee:command> element of the client command if sent by the client.
The <fee:cd> element also has an OPTIONAL "avail" attribute which is The <fee:cd> element also has an OPTIONAL "avail" attribute which is
a boolean. If the value of this attribute evaluates to false, this a boolean. If the value of this attribute evaluates to false, this
indicates that the server cannot calculate the relevant fees, because indicates that the server cannot calculate the relevant fees, because
the object, command, currency, period, class or some combination is the object, command, currency, period, class or some combination is
invalid per server policy. If "avail" is false then the <fee:cd> or invalid per server policy. If "avail" is false then the <fee:cd> or
the <fee:command> element MUST contain a <fee:reason> element (as the <fee:command> element MUST contain a <fee:reason> element (as
described in Section 3.9) and the server MAY eliminate some or all of described in Section 3.9) and the server MAY eliminate some or all of
the <fee:command> element(s). the <fee:command> element(s).
skipping to change at page 14, line 27 skipping to change at page 14, line 40
S: <fee:fee S: <fee:fee
S: description="Registration Fee" S: description="Registration Fee"
S: refundable="1" S: refundable="1"
S: grace-period="P5D">10.00</fee:fee> S: grace-period="P5D">10.00</fee:fee>
S: </fee:command> S: </fee:command>
S: <fee:command name="renew"> S: <fee:command name="renew">
S: <fee:period unit="y">1</fee:period> S: <fee:period unit="y">1</fee:period>
S: <fee:fee S: <fee:fee
S: description="Renewal Fee" S: description="Renewal Fee"
S: refundable="1" S: refundable="1"
S: grace-period="P5D">5.00</fee:fee> S: grace-period="P5D">10.00</fee:fee>
S: </fee:command> S: </fee:command>
S: <fee:command name="transfer"> S: <fee:command name="transfer">
S: <fee:period unit="y">1</fee:period> S: <fee:period unit="y">1</fee:period>
S: <fee:fee S: <fee:fee
S: description="Transfer Fee" S: description="Transfer Fee"
S: refundable="1" S: refundable="1"
S: grace-period="P5D">5.00</fee:fee> S: grace-period="P5D">10.00</fee:fee>
S: </fee:command> S: </fee:command>
S: <fee:command name="restore"> S: <fee:command name="restore">
S: <fee:fee S: <fee:fee
S: description="Redemption Fee">5.00</fee:fee> S: description="Redemption Fee">15.00</fee:fee>
S: </fee:command> S: </fee:command>
S: </fee:cd> S: </fee:cd>
S: <fee:cd avail="1"> S: <fee:cd avail="1">
S: <fee:objID>example.net</fee:objID> S: <fee:objID>example.net</fee:objID>
S: <fee:command name="create"> S: <fee:class>standard</fee:class>
S: <fee:command name="create" standard="1">
S: <fee:period unit="y">2</fee:period> S: <fee:period unit="y">2</fee:period>
S: <fee:fee S: <fee:fee
S: description="Registration Fee" S: description="Registration Fee"
S: refundable="1" S: refundable="1"
S: grace-period="P5D">10.00</fee:fee> S: grace-period="P5D">5.00</fee:fee>
S: </fee:command> S: </fee:command>
S: <fee:command name="renew"> S: <fee:command name="renew" standard="1">
S: <fee:period unit="y">1</fee:period> S: <fee:period unit="y">1</fee:period>
S: <fee:fee S: <fee:fee
S: description="Renewal Fee" S: description="Renewal Fee"
S: refundable="1" S: refundable="1"
S: grace-period="P5D">5.00</fee:fee> S: grace-period="P5D">5.00</fee:fee>
S: </fee:command> S: </fee:command>
S: <fee:command name="transfer"> S: <fee:command name="transfer" standard="1">
S: <fee:period unit="y">1</fee:period> S: <fee:period unit="y">1</fee:period>
S: <fee:fee S: <fee:fee
S: description="Transfer Fee" S: description="Transfer Fee"
S: refundable="1" S: refundable="1"
S: grace-period="P5D">5.00</fee:fee> S: grace-period="P5D">5.00</fee:fee>
S: </fee:command> S: </fee:command>
S: <fee:command name="restore"> S: <fee:command name="restore" standard="1">
S: <fee:fee S: <fee:fee
S: description="Redemption Fee">5.00</fee:fee> S: description="Redemption Fee">5.00</fee:fee>
S: </fee:command> S: </fee:command>
S: </fee:cd> S: </fee:cd>
S: <fee:cd avail="0"> S: <fee:cd avail="0">
S: <fee:objID>example.xyz</fee:objID> S: <fee:objID>example.xyz</fee:objID>
S: <fee:command name="create"> S: <fee:command name="create">
S: <fee:period unit="y">2</fee:period> S: <fee:period unit="y">2</fee:period>
S: <fee:reason>Only 1 year registration periods are S: <fee:reason>Only 1 year registration periods are
S: valid.</fee:reason> S: valid.</fee:reason>
skipping to change at page 29, line 38 skipping to change at page 29, line 38
<complexType name="commandType"> <complexType name="commandType">
<sequence> <sequence>
<element name="period" type="domain:periodType" <element name="period" type="domain:periodType"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
</sequence> </sequence>
<attribute name="name" type="fee:commandEnum"/> <attribute name="name" type="fee:commandEnum"/>
<attribute name="customName" type="token"/> <attribute name="customName" type="token"/>
<attribute name="phase" type="token" /> <attribute name="phase" type="token" />
<attribute name="subphase" type="token" /> <attribute name="subphase" type="token" />
<attribute name="standard" type="boolean" default="0" />
</complexType> </complexType>
<complexType name="commandDataType"> <complexType name="commandDataType">
<complexContent> <complexContent>
<extension base="fee:commandType"> <extension base="fee:commandType">
<sequence> <sequence>
<element name="fee" type="fee:feeType" <element name="fee" type="fee:feeType"
minOccurs="0" maxOccurs="unbounded" /> minOccurs="0" maxOccurs="unbounded" />
<element name="credit" type="fee:creditType" <element name="credit" type="fee:creditType"
minOccurs="0" maxOccurs="unbounded" /> minOccurs="0" maxOccurs="unbounded" />
skipping to change at page 30, line 4 skipping to change at page 29, line 51
<complexContent> <complexContent>
<extension base="fee:commandType"> <extension base="fee:commandType">
<sequence> <sequence>
<element name="fee" type="fee:feeType" <element name="fee" type="fee:feeType"
minOccurs="0" maxOccurs="unbounded" /> minOccurs="0" maxOccurs="unbounded" />
<element name="credit" type="fee:creditType" <element name="credit" type="fee:creditType"
minOccurs="0" maxOccurs="unbounded" /> minOccurs="0" maxOccurs="unbounded" />
<element name="reason" type="fee:reasonType" <element name="reason" type="fee:reasonType"
minOccurs="0" /> minOccurs="0" />
</sequence> </sequence>
</extension> </extension>
<attribute name="standard" type="boolean" default="0" />
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="reasonType"> <complexType name="reasonType">
<simpleContent> <simpleContent>
<extension base="token"> <extension base="token">
<attribute name="lang" type="language" default="en"/> <attribute name="lang" type="language" default="en"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
skipping to change at page 32, line 39 skipping to change at page 32, line 39
IPR Disclosure: None IPR Disclosure: None
Status: Active Status: Active
Notes: None Notes: None
9. Implementation Status 9. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
[RFC6982] before publication. [RFC7942] before publication.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC6982]. Internet-Draft, and is based on a proposal described in [RFC7942].
The description of implementations in this section is intended to The description of implementations in this section is intended to
assist the IETF in its decision processes in progressing drafts to assist the IETF in its decision processes in progressing drafts to
RFCs. Please note that the listing of any individual implementation RFCs. Please note that the listing of any individual implementation
here does not imply endorsement by the IETF. Furthermore, no effort here does not imply endorsement by the IETF. Furthermore, no effort
has been spent to verify the information presented here that was has been spent to verify the information presented here that was
supplied by IETF contributors. This is not intended as, and must not supplied by IETF contributors. This is not intended as, and must not
be construed to be, a catalog of available implementations or their be construed to be, a catalog of available implementations or their
features. Readers are advised to note that other implementations may features. Readers are advised to note that other implementations may
exist. exist.
According to [RFC6982], "this will allow reviewers and working groups According to [RFC7942], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature. and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as It is up to the individual working groups to use this information as
they see fit". they see fit".
9.1. RegistryEngine EPP Service 9.1. RegistryEngine EPP Service
Organization: CentralNic Organization: CentralNic
skipping to change at page 34, line 7 skipping to change at page 34, line 7
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 10 to 11 11.1. 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.2. 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.2. Change from 09 to 10 11.3. 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.3. Change from 08 to 09 11.4. 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.4. Change from 07 to 08 11.5. 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.5. Change from 06 to 07 11.6. 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.6. Change from 05 to 06 11.7. 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.7. Change from 04 to 05 11.8. 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.8. Change from 03 to 04 11.9. 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.9. Change from 02 to 03 11.10. 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.10. Change from 01 to 02 11.11. 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.11. Change from 00 to 01 11.12. 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.12. Change from draft-brown-00 to draft-ietf-regext-fees-00 11.13. Change from draft-brown-00 to draft-ietf-regext-fees-00
Updated to be REGEXT WG document. Updated to be REGEXT WG document.
12. Normative References 12. Normative References
[ISO4217] 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 [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,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
skipping to change at page 36, line 34 skipping to change at page 36, line 42
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009, DOI 10.17487/RFC5731, August 2009,
<https://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", RFC 6982,
DOI 10.17487/RFC6982, July 2013,
<https://www.rfc-editor.org/info/rfc6982>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[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 [RFC8334] Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping
for the Extensible Provisioning Protocol (EPP)", RFC 8334, for the Extensible Provisioning Protocol (EPP)", RFC 8334,
DOI 10.17487/RFC8334, March 2018, DOI 10.17487/RFC8334, March 2018,
<https://www.rfc-editor.org/info/rfc8334>. <https://www.rfc-editor.org/info/rfc8334>.
Authors' Addresses Authors' Addresses
Roger Carney Roger Carney
GoDaddy Inc. GoDaddy Inc.
14455 N. Hayden Rd. #219 14455 N. Hayden Rd. #219
Scottsdale, AZ 85260 Scottsdale, AZ 85260
US US
Email: rcarney@godaddy.com Email: rcarney@godaddy.com
URI: http://www.godaddy.com URI: http://www.godaddy.com
Gavin Brown Gavin Brown
 End of changes. 43 change blocks. 
60 lines changed or deleted 80 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/