draft-ietf-regext-allocation-token-02.txt		draft-ietf-regext-allocation-token-03.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 K. Feher
	Expires: December 25, 2017 Neustar		Expires: January 4, 2018 Neustar
	June 23, 2017		July 3, 2017
	Allocation Token Extension for the Extensible Provisioning Protocol		Allocation Token Extension for the Extensible Provisioning Protocol
	(EPP)		(EPP)
	draft-ietf-regext-allocation-token-02		draft-ietf-regext-allocation-token-03
	Abstract		Abstract
	This document describes an Extensible Provisioning Protocol (EPP)		This document describes an Extensible Provisioning Protocol (EPP)
	extension for including an allocation token or code for allocating an		extension for including an allocation token or code for allocating an
	object like a domain name to the client. The allocation token MAY be		object like a domain name to the client. The allocation token MAY be
	transferred out-of-band to a client to give them authorization to		transferred out-of-band to a client to give them authorization to
	allocate an object using one of the EPP transform commands including		allocate an object using one of the EPP transform commands including
	create, update, and transfer.		create, update, and transfer.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 December 25, 2017.		This Internet-Draft will expire on January 4, 2018.
	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 43 ¶		skipping to change at page 2, line 43 ¶
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
	9. Normative References . . . . . . . . . . . . . . . . . . . . 17		9. Normative References . . . . . . . . . . . . . . . . . . . . 17
	Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18		Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18
	A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18		A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18
	A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18		A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18
	A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18		A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18
	A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18		A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18
	A.5. Change from 04 to REGEXT 00 . . . . . . . . . . . . . . . 18		A.5. Change from 04 to REGEXT 00 . . . . . . . . . . . . . . . 18
	A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 19		A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 19
	A.7. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 19		A.7. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 19
			A.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 19
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
	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], for passing an allocation token one of the EPP transform		[RFC5731], for passing an allocation token one of the EPP transform
	commands including create, update, and transfer. The allocation		commands including create, update, and transfer. The allocation
	token is known to the server to authorize a client that passes a		token is known to the server to authorize a client that passes a
	skipping to change at page 17, line 38 ¶		skipping to change at page 17, line 38 ¶
	7. Security Considerations		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.
	8. 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
			and Sharon Wodjenski.
	9. 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,
	skipping to change at page 19, line 13 ¶		skipping to change at page 19, line 13 ¶
	allocation-token to draft-ietf-regext-allocation-token.		allocation-token to draft-ietf-regext-allocation-token.
	A.6. Change from REGEXT 00 to REGEXT 01		A.6. Change from REGEXT 00 to REGEXT 01
	1. Ping update.		1. Ping update.
	A.7. Change from REGEXT 01 to REGEXT 02		A.7. Change from REGEXT 01 to REGEXT 02
	1. Added the Implementation Status section.		1. Added the Implementation Status section.
			A.8. Change from REGEXT 02 to REGEXT 03
			1. Changed Neustar author to Kal Feher.
	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
	Sharon Wodjenski		Kal Feher
	Neustar		Neustar
	21575 Ridgetop Circle		lvl 8/10 Queens Road
	Sterling, VA 20166		Melbourne, VIC 3004
	US		AU
	Email: Sharon.Wodjenski@neustar.biz		Email: kal.feher@team.neustar
	URI: http://www.neustar.biz		URI: http://www.neustar.biz
End of changes. 9 change blocks.
	11 lines changed or deleted		17 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/