draft-ietf-regext-epp-fees-10.txt   draft-ietf-regext-epp-fees-11.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: September 6, 2018 CentralNic Group plc Expires: October 12, 2018 CentralNic Group plc
J. Frakes J. Frakes
March 5, 2018 April 10, 2018
Registry Fee Extension for the Extensible Provisioning Protocol (EPP) Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-fees-10 draft-ietf-regext-epp-fees-11
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 September 6, 2018. This Internet-Draft will expire on October 12, 2018.
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 45 skipping to change at page 2, line 45
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 09 to 10 . . . . . . . . . . . . . . . . . . 34 11.1. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 34
11.2. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34 11.2. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 34
11.3. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 34 11.3. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34
11.4. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 34 11.4. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 34
11.5. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 34 11.5. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 34
11.6. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 34 11.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 34
11.7. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35 11.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 34
11.8. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35 11.8. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35
11.9. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35 11.9. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35
11.10. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 35 11.10. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35
11.11. Change from draft-brown-00 to draft-ietf-regext-fees-00 36 11.11. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 35
11.12. 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 . . . . . . . . . . . . . . . . . . . . . . . 36
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
skipping to change at page 9, line 11 skipping to change at page 9, line 11
the server has only one active phase/subphase combination the server the server has only one active phase/subphase combination the server
MUST return data (including the phase/subphase attribute(s)) of the MUST return data (including the phase/subphase attribute(s)) of the
currently active phase/subphase. currently active phase/subphase.
If the client <fee:command> contains no phase/subphase attributes and If the client <fee:command> contains no phase/subphase attributes and
the server has more than one active phase/subphase combination the the server has more than one active phase/subphase combination the
server MUST respond with a 2003 "Required parameter missing" error. server MUST respond with a 2003 "Required parameter missing" error.
If the client <fee:command> contains no phase/subphase attributes and If the client <fee:command> contains no phase/subphase attributes and
the server is currently in a "quiet period" (e.g. not accepting the server is currently in a "quiet period" (e.g. not accepting
registrations or applications)the server MUST return data consistent registrations or applications) the server MUST return data consistent
with the default general availability phase (e.g. "open" or "claims") with the default general availability phase (e.g. "open" or "claims")
including the appropriate phase/subphase attribute(s). including the appropriate phase/subphase attribute(s).
If the client <fee:command> contains a phase attribute with no If the client <fee:command> contains a phase attribute with no
subphase and the server has only one active subphase (or no subphase) subphase and the server has only one active subphase (or no subphase)
of this phase, the server MUST return data (including the phase/ of this phase, the server MUST return data (including the phase/
subphase attribute(s)) of the provided phase and currently active subphase attribute(s)) of the provided phase and currently active
subphase. subphase.
If the client <fee:command> contains a phase attribute with no If the client <fee:command> contains a phase attribute with no
skipping to change at page 10, line 20 skipping to change at page 10, line 20
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:reason>Only 1 year registration periods are S: <fee:reason>Only 1 year registration periods are
S: valid.</fee:reason> S: valid.</fee:reason>
S: </fee:cd> S: </fee:cd>
2. Partial-fail - The server, upon error identification, MAY 2. Partial-fail - The server, upon error identification, MAY
continue processing <fee:command> elements and return to the continue processing <fee:command> elements and return to the
client a <fee:cd> containing successfully processed <fee:command> client a <fee:cd> containing successfully processed <fee:command>
elements and failed <fee:command> elements. All returned failed elements and failed <fee:command> elements. All returned failed
<fee:command> elements that MUST have a <fee:reason> element <fee:command> elements MUST have a <fee:reason> element detailing
detailing the reason for failure, and the server MAY additionally the reason for failure, and the server MAY additionally include a
include a <fee:reason> element at the <fee:cd> level. <fee:reason> element at the <fee:cd> level.
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>
S: </fee:command> S: </fee:command>
S: </fee:cd> S: </fee:cd>
In either failure scenario the server MUST set the <fee:cd> avail In either failure scenario the server MUST set the <fee:cd> avail
attribute to false (0) and the server MUST process all domain names attribute to false (0) and the server MUST process all objects in the
in the client request. client request.
4. Server Handling of Fee Information 4. Server Handling of Fee Information
Depending on server policy, a client MAY be required to include the Depending on server policy, a client MAY be required to include the
extension elements described in this document for certain transform extension elements described in this document for certain transform
commands. Servers must provide clear documentation to clients about commands. Servers must provide clear documentation to clients about
the circumstances in which this extension must be used. the circumstances in which this extension must be used.
The server MUST return avail="0" in its response to a <check> command The server MUST return avail="0" in its response to a <check> command
for any domain name in the <check> command that does not include the for any object in the <check> command that does not include the
<fee:check> extension for which the server would likewise fail a <fee:check> extension for which the server would likewise fail a
domain <create> command when no <fee> extension is provided for that domain <create> command when no <fee> extension is provided for that
same domain object. same object.
If a server receives a <check> command from a client, which results If a server receives a <check> command from a client, which results
in no possible fee combination but where a fee is required, the in no possible fee combination but where a fee is required, the
server MUST set the "avail" attribute of the <fee:cd> element to server MUST set the "avail" attribute of the <fee:cd> element to
false and provide a <fee:reason>. false and provide a <fee:reason>.
If a server receives a <check> command from a client, which results If a server receives a <check> command from a client, which results
in an ambiguous result (i.e. multiple possible fee combinations) the in an ambiguous result (i.e. multiple possible fee combinations) the
server MUST reject the command with a 2003 "Required parameter server MUST reject the command with a 2003 "Required parameter
missing" error. missing" error.
skipping to change at page 11, line 45 skipping to change at page 11, line 45
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 "standard" attribute with a default value
of false (0), 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 15, line 44 skipping to change at page 15, line 44
S: </trID> S: </trID>
S: </response> S: </response>
S: </epp> S: </epp>
5.1.2. EPP Transfer Query Command 5.1.2. EPP Transfer Query Command
This extension does not add any elements to the EPP <transfer> query This extension does not add any elements to the EPP <transfer> query
command, but does include elements in the response, when the command, but does include elements in the response, when the
extension is included in the <login> command service extensions. extension is included in the <login> command service extensions.
When the <transfer> query command has been processed successfully, When the <transfer> query command has been processed successfully, if
the client included the extension in the <login> command service the client has included the extension in the <login> command service
extensions, and the client is authorized by the server to view <svcExtension> element, and if the client is authorized by the server
information about the transfer, the server MAY include in the to view information about the transfer, then the server MAY include
<extension> section of the EPP response a <fee:trnData> element, in the <extension> section of the EPP response a <fee:trnData>
which contains the following child elements: element, which contains the following child elements:
o A <fee:currency> element (as described in Section 3.2). o A <fee:currency> element (as described in Section 3.2).
o A <fee:period> element (as described in Section 3.3). o A <fee:period> element (as described in Section 3.3).
o Zero or more <fee:fee> elements (as described in Section 3.4) o Zero or more <fee:fee> elements (as described in Section 3.4)
containing the fees that will be charged to the gaining client. containing the fees that will be charged to the gaining client.
o Zero or more <fee:credit> elements (as described in Section 3.4) o Zero or more <fee:credit> elements (as described in Section 3.4)
containing the credits that will be refunded to the losing client. containing the credits that will be refunded to the losing client.
Servers SHOULD omit <fee:credit> when returning a response to the Servers SHOULD omit <fee:credit> when returning a response to the
skipping to change at page 31, line 49 skipping to change at page 31, line 49
8.1. XML Namespace 8.1. XML Namespace
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. conforming to a registry mechanism described in [RFC3688].
Registration request for the fee namespace: Registration request for the fee namespace:
URI: urn:ietf:params:xml:ns:fee-1.0 URI: urn:ietf:params:xml:ns:fee-1.0
Registrant Contact: IESG. Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the fee schema: Registration request for the fee schema:
URI: urn:ietf:params:xml:schema:fee-1.0 URI: urn:ietf:params:xml:schema:fee-1.0
Registrant Contact: IESG. Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of this document.
8.2. EPP Extension Registry 8.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows: details of the registration are as follows:
Name of Extension: Registry Fee Extension for the Extensible Name of Extension: Registry Fee Extension for the Extensible
Provisioning Protocol (EPP) Provisioning Protocol (EPP)
Document status: Standards Track Document status: Standards Track
Reference: (insert reference to RFC version of this document) Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: IESG, <iesg@ietf.org>. Registrant Name and Email Address: IESG, <iesg@ietf.org>
TLDs: any TLDs: Any
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. [RFC6982] 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 [RFC6982].
The description of implementations in this section is intended to The description of implementations in this section is intended to
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 09 to 10 11.1. 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.2. 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.2. Change from 08 to 09 11.3. 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.3. Change from 07 to 08 11.4. 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.4. Change from 06 to 07 11.5. 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.5. Change from 05 to 06 11.6. 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.6. Change from 04 to 05 11.7. 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.7. Change from 03 to 04 11.8. 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.8. Change from 02 to 03 11.9. 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.9. Change from 01 to 02 11.10. 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.10. Change from 00 to 01 11.11. 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.11. Change from draft-brown-00 to draft-ietf-regext-fees-00 11.12. 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
[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>.
 End of changes. 30 change blocks. 
50 lines changed or deleted 56 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/