draft-ietf-regext-epp-fees-13.txt		draft-ietf-regext-epp-fees-14.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: March 11, 2019 CentralNic Group plc		Expires: April 15, 2019 CentralNic Group plc
	J. Frakes		J. Frakes
	September 7, 2018		October 12, 2018
	Registry Fee Extension for the Extensible Provisioning Protocol (EPP)		Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
	draft-ietf-regext-epp-fees-13		draft-ietf-regext-epp-fees-14
	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 March 11, 2019.		This Internet-Draft will expire on April 15, 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 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 12 to 13 . . . . . . . . . . . . . . . . . . 34		11.1. Change from 13 to 14 . . . . . . . . . . . . . . . . . . 34
	11.2. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 34		11.2. Change from 12 to 13 . . . . . . . . . . . . . . . . . . 34
	11.3. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 34		11.3. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 34
	11.4. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 34		11.4. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 34
	11.5. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34		11.5. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 34
	11.6. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 34		11.6. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 34
	11.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 35		11.7. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 34
	11.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 35		11.8. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 35
	11.9. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 35		11.9. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 35
	11.10. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35		11.10. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 35
	11.11. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35		11.11. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35
	11.12. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35		11.12. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35
	11.13. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 36		11.13. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35
	11.14. Change from draft-brown-00 to draft-ietf-regext-fees-00 36		11.14. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 36
	12. Normative References . . . . . . . . . . . . . . . . . . . . 36		11.15. Change from draft-brown-00 to draft-ietf-regext-fees-00 36
			12. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
			12.1. Normative References . . . . . . . . . . . . . . . . . . 36
			12.2. Informative References . . . . . . . . . . . . . . . . . 37
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37		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
	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 12 to 13		11.1. Change from 13 to 14
			Moved RFC 7451 reference from Normative to Informative section.
			11.2. Change from 12 to 13
	Updated XML namespace and schema registration to be "epp" scoped -		Updated XML namespace and schema registration to be "epp" scoped -
	global replace of XML namespace from urn:ietf:params:xml:ns:fee-1.0		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		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		from urn:ietf:params:xml:schema:fee-1.0 to
	urn:ietf:params:xml:schema:epp:fee-1.0.		urn:ietf:params:xml:schema:epp:fee-1.0.
	11.2. Change from 11 to 12		11.3. Change from 11 to 12
	Updated references to current version of documents and moved the		Updated references to current version of documents and moved the
	"standard" attribute from the check command (commandType) to the		"standard" attribute from the check command (commandType) to the
	check response (commandDataType).		check response (commandDataType).
	11.3. Change from 10 to 11		11.4. 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.4. Change from 09 to 10		11.5. 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.5. Change from 08 to 09		11.6. 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.6. Change from 07 to 08		11.7. 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.7. Change from 06 to 07		11.8. 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.8. Change from 05 to 06		11.9. 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.9. Change from 04 to 05		11.10. 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.10. Change from 03 to 04		11.11. 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.11. Change from 02 to 03		11.12. 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.12. Change from 01 to 02		11.13. 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.13. Change from 00 to 01		11.14. 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.14. Change from draft-brown-00 to draft-ietf-regext-fees-00		11.15. 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. References
			12.1. Normative References
	[ISO4217] International Organization for Standardization, "Codes for		[ISO4217] International Organization for Standardization, "Codes for
	the representation of currencies", August 2015,		the representation of currencies", August 2015,
	<https://www.iso.org/standard/64758.html>.		<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>.
	skipping to change at page 37, line 10 ¶		skipping to change at page 37, line 10 ¶
	[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>.
	[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>.
	[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running		[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
	Code: The Implementation Status Section", BCP 205,		Code: The Implementation Status Section", BCP 205,
	RFC 7942, DOI 10.17487/RFC7942, July 2016,		RFC 7942, DOI 10.17487/RFC7942, July 2016,
	<https://www.rfc-editor.org/info/rfc7942>.		<https://www.rfc-editor.org/info/rfc7942>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/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>.
			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		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
End of changes. 22 change blocks.
	38 lines changed or deleted		49 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/