draft-ietf-regext-change-poll-08.txt		draft-ietf-regext-change-poll-09.txt
	Network Working Group J. Gould		Network Working Group J. Gould
	Internet-Draft VeriSign, Inc.		Internet-Draft VeriSign, Inc.
	Intended status: Standards Track K. Feher		Intended status: Standards Track K. Feher
	Expires: November 17, 2018 Neustar		Expires: April 7, 2019 Neustar
	May 16, 2018		October 4, 2018
	Change Poll Extension for the Extensible Provisioning Protocol (EPP)		Change Poll Extension for the Extensible Provisioning Protocol (EPP)
	draft-ietf-regext-change-poll-08		draft-ietf-regext-change-poll-09
	Abstract		Abstract
	This document describes an Extensible Provisioning Protocol (EPP)		This document describes an Extensible Provisioning Protocol (EPP)
	extension for notifying clients of operations on client sponsored		extension for notifying clients of operations on client sponsored
	objects that were not initiated by the client through EPP. These		objects that were not initiated by the client through EPP. These
	operations may include contractual or policy requirements including		operations may include contractual or policy requirements including
	but not limited to regular batch processes, customer support actions,		but not limited to regular batch processes, customer support actions,
	Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid		Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid
	Suspension (URS) actions, court directed actions, and bulk updates		Suspension (URS) actions, court directed actions, and bulk updates
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 November 17, 2018.		This Internet-Draft will expire on April 7, 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 3, line 10 ¶		skipping to change at page 3, line 10 ¶
	9.2. Informative References . . . . . . . . . . . . . . . . . 23		9.2. Informative References . . . . . . . . . . . . . . . . . 23
	Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24		Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24
	A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 24		A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 24
	A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 24		A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 24
	A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 24		A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 24
	A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 24		A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 24
	A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 24		A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 24
	A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 24		A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 24
	A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 24		A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 24
	A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 24		A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 24
	A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 24		A.9. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 25
	A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25		A.10. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 25
	A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 25		A.11. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 25
	A.12. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 25		A.12. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 25
	A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25		A.13. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 25
	A.14. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 26		A.14. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 26
			A.15. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 26
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
	1. Introduction		1. Introduction
	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 mapping, an		Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an
	extension to EPP object mappings like the EPP domain name mapping		extension to EPP object mappings like the EPP domain name mapping
	[RFC5731], is used to notify clients of operations they are not		[RFC5731], is used to notify clients of operations they are not
	directly involved in, on objects that the client sponsors. It is up		directly involved in, on objects that the client sponsors. It is up
	to server policy to determine what transform operations and clients		to server policy to determine what transform operations and clients
	skipping to change at page 3, line 37 ¶		skipping to change at page 3, line 38 ¶
	systems in-sync with the objects stored in the server. When a change		systems in-sync with the objects stored in the server. When a change
	occurs that a client needs to be notified of, a poll message can be		occurs that a client needs to be notified of, a poll message can be
	inserted by the server for consumption by the client using the EPP		inserted by the server for consumption by the client using the EPP
	<poll> command and response defined in [RFC5730]. The extension		<poll> command and response defined in [RFC5730]. The extension
	supports including a "before" operation poll message and an "after"		supports including a "before" operation poll message and an "after"
	operation poll message.		operation poll message.
	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.
	In examples, "C:" represents lines sent by a protocol client and "S:"		In examples, "C:" represents lines sent by a protocol client and "S:"
	represents lines returned by a protocol server. Indentation and		represents lines returned by a protocol server. Indentation and
	white space in examples are provided only to illustrate element		white space in examples are provided only to illustrate element
	relationships and are not a REQUIRED feature of this protocol.		relationships and are not a REQUIRED feature of this protocol.
	skipping to change at page 24, line 5 ¶		skipping to change at page 24, line 5 ¶
	Second Edition", World Wide Web Consortium Recommendation		Second Edition", World Wide Web Consortium Recommendation
	REC-xmlschema-2-20041028, October 2004,		REC-xmlschema-2-20041028, October 2004,
	<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.		<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
	9.2. Informative References		9.2. Informative References
	[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>.
			[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>.
	Appendix A. Change History		Appendix A. Change History
	A.1. Change from 00 to 01		A.1. Change from 00 to 01
	1. Added an optional caseId element that defines the case identifier		1. Added an optional caseId element that defines the case identifier
	from UDRP, URS, or custom case, based on feedback from Michael		from UDRP, URS, or custom case, based on feedback from Michael
	Holloway.		Holloway.
	A.2. Change from 01 to 02		A.2. Change from 01 to 02
	skipping to change at page 26, line 13 ¶		skipping to change at page 26, line 13 ¶
	the operation type, respectively.		the operation type, respectively.
	A.14. Change from REGEXT 07 to REGEXT 08		A.14. Change from REGEXT 07 to REGEXT 08
	1. Updated obsoleted RFC 6982 to RFC 7942.		1. Updated obsoleted RFC 6982 to RFC 7942.
	2. Moved RFC 7451 to an informational reference based on a check		2. Moved RFC 7451 to an informational reference based on a check
	done by the Idnits Tool.		done by the Idnits Tool.
	3. Changed Kal Feher's contact e-mail address.		3. Changed Kal Feher's contact e-mail address.
	4. Changed Neustar's Implementation Status contact e-mail address.		4. Changed Neustar's Implementation Status contact e-mail address.
			A.15. Change from REGEXT 08 to REGEXT 09
			1. Fixed Section 1.1 (Conventions) to contain the updated language
			(e.g. "NOT RECOMMENDED", RFC 8174, BCP 14), based on feedback
			from the Document Shepherd.
	Authors' Addresses		Authors' Addresses
	James Gould		James Gould
	VeriSign, Inc.		VeriSign, Inc.
	12061 Bluemont Way		12061 Bluemont Way
	Reston, VA 20190		Reston, VA 20190
	US		US
	Email: jgould@verisign.com		Email: jgould@verisign.com
	URI: http://www.verisigninc.com		URI: http://www.verisigninc.com
End of changes. 8 change blocks.
	7 lines changed or deleted		20 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/