draft-ietf-regext-change-poll-01.txt		draft-ietf-regext-change-poll-02.txt
	Network Working Group J. Gould		Network Working Group J. Gould
	Internet-Draft VeriSign, Inc.		Internet-Draft VeriSign, Inc.
	Intended status: Standards Track S. Wodjenski		Intended status: Standards Track S. Wodjenski
	Expires: October 19, 2017 Neustar		Expires: December 25, 2017 Neustar
	April 17, 2017		June 23, 2017
	Change Poll Extension for the Extensible Provisioning Protocol (EPP)		Change Poll Extension for the Extensible Provisioning Protocol (EPP)
	draft-ietf-regext-change-poll-01		draft-ietf-regext-change-poll-02
	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 October 19, 2017.		This Internet-Draft will expire on December 25, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 2, line 38 ¶		skipping to change at page 2, line 38 ¶
	3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 15		3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 15
	3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 15		3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 15
	3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 15		3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 15
	3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 15		3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 15
	3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 15		3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 15
	4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15		4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15
	4.1. Change Poll Extension Schema . . . . . . . . . . . . . . 16		4.1. Change Poll Extension Schema . . . . . . . . . . . . . . 16
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
	5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18		5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18
	5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 19		5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 19
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 19		6. Implementation Status . . . . . . . . . . . . . . . . . . . . 19
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19		6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 20
	8. Normative References . . . . . . . . . . . . . . . . . . . . 19		6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 20
	Appendix A. Change History . . . . . . . . . . . . . . . . . . . 20		6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 20
	A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 20		7. Security Considerations . . . . . . . . . . . . . . . . . . . 21
	A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
	A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20		9. Normative References . . . . . . . . . . . . . . . . . . . . 21
	A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20		Appendix A. Change History . . . . . . . . . . . . . . . . . . . 22
	A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20		A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 22
	A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 21		A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 22
	A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 21		A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 22
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21		A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 22
			A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 22
			A.6. Change from 05 to REGEXT 00 . . . . . . . . . . . . . . . 22
			A.7. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 23
			A.8. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 23
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
	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
	to notify. Using this extension clients can more easily keep their		to notify. Using this extension clients can more easily keep their
	skipping to change at page 19, line 28 ¶		skipping to change at page 19, line 28 ¶
	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
	6. Security Considerations		6. Implementation Status
			Note to RFC Editor: Please remove this section and the reference to
			RFC 6982 [RFC6982] before publication.
			This section records the status of known implementations of the
			protocol defined by this specification at the time of posting of this
			Internet-Draft, and is based on a proposal described in RFC 6982
			[RFC6982]. The description of implementations in this section is
			intended to assist the IETF in its decision processes in progressing
			drafts to RFCs. Please note that the listing of any individual
			implementation here does not imply endorsement by the IETF.
			Furthermore, no effort has been spent to verify the information
			presented here that was supplied by IETF contributors. This is not
			intended as, and must not be construed to be, a catalog of available
			implementations or their features. Readers are advised to note that
			other implementations may exist.
			According to RFC 6982 [RFC6982], "this will allow reviewers and
			working groups to assign due consideration to documents that have the
			benefit of running code, which may serve as evidence of valuable
			experimentation and feedback that have made the implemented protocols
			more mature. It is up to the individual working groups to use this
			information as they see fit".
			6.1. Verisign EPP SDK
			Organization: Verisign Inc.
			Name: Verisign EPP SDK
			Description: The Verisign EPP SDK includes both a full client
			implementation and a full server stub implementation of draft-ietf-
			regext-change-poll.
			Level of maturity: Production
			Coverage: All aspects of the protocol are implemented.
			Licensing: GNU Lesser General Public License
			Contact: jgould@verisign.com
			URL: https://www.verisign.com/en_US/channel-resources/domain-
			registry-products/epp-sdks
			6.2. Verisign Consolidated Top Level Domain (CTLD) SRS
			Organization: Verisign Inc.
			Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry
			System (SRS)
			Description: The Verisign Consolidated Top Level Domain (CTLD) Shared
			Registry System (SRS) implements the server-side of draft-ietf-
			regext-change-poll for a variety of Top Level Domains (TLD's).
			Level of maturity: Production
			Coverage: The "after" state poll message for an "update" transform
			operation of a domain name due to server policy.
			Licensing: Proprietary
			Contact: jgould@verisign.com
			6.3. Verisign .COM / .NET SRS
			Organization: Verisign Inc.
			Name: Verisign .COM / .NET Shared Registry System (SRS)
			Description: The Verisign Shared Registry System (SRS) for .COM and
			.NET implements the server-side of draft-ietf-regext-change-poll.
			Level of maturity: Production
			Coverage: The "after" state poll message for an "update" transform
			operation of a domain name due to server policy.
			Licensing: Proprietary
			Contact: jgould@verisign.com
			7. Security Considerations
	The mapping extensions described in this document do not provide any		The mapping extensions described in this document do not provide any
	security services beyond those described by EPP [RFC5730] and		security services beyond those described by EPP [RFC5730] and
	protocol layers used by EPP. The security considerations described		protocol layers used by EPP. The security considerations described
	in these other specifications apply to this specification as well.		in these other specifications apply to this specification as well.
	7. Acknowledgements		8. Acknowledgements
	The authors wish to acknowledge the original concept for this draft		The authors wish to acknowledge the original concept for this draft
	and the efforts in the initial versions of this draft by Trung Tran.		and the efforts in the initial versions of this draft by Trung Tran.
	Special suggestions that have been incorporated into this document		Special suggestions that have been incorporated into this document
	were provided by Michael Holloway.		were provided by Michael Holloway.
	8. Normative References		9. 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,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://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,
	<http://www.rfc-editor.org/info/rfc3688>.		<http://www.rfc-editor.org/info/rfc3688>.
	skipping to change at page 20, line 19 ¶		skipping to change at page 22, 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,
	<http://www.rfc-editor.org/info/rfc5730>.		<http://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,
	<http://www.rfc-editor.org/info/rfc5731>.		<http://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,
			<http://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, <http://www.rfc-editor.org/info/rfc7451>.		February 2015, <http://www.rfc-editor.org/info/rfc7451>.
	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
	skipping to change at page 21, line 14 ¶		skipping to change at page 23, line 9 ¶
	A.6. Change from 05 to REGEXT 00		A.6. Change from 05 to REGEXT 00
	1. Changed to regext working group draft by changing draft-gould-		1. Changed to regext working group draft by changing draft-gould-
	change-poll to draft-ietf-regext-change-poll.		change-poll to draft-ietf-regext-change-poll.
	A.7. Change from REGEXT 00 to REGEXT 01		A.7. Change from REGEXT 00 to REGEXT 01
	1. Ping update.		1. Ping update.
			A.8. Change from REGEXT 01 to REGEXT 02
			1. Added the Implementation Status section.
	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. 9 change blocks.
	19 lines changed or deleted		116 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/