draft-ietf-regext-allocation-token-10.txt		draft-ietf-regext-allocation-token-11.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: February 22, 2019 Neustar		Expires: March 8, 2019 Neustar
	August 21, 2018		September 4, 2018
	Allocation Token Extension for the Extensible Provisioning Protocol		Allocation Token Extension for the Extensible Provisioning Protocol
	(EPP)		(EPP)
	draft-ietf-regext-allocation-token-10		draft-ietf-regext-allocation-token-11
	Abstract		Abstract
	This document describes an Extensible Provisioning Protocol (EPP)		This document describes an Extensible Provisioning Protocol (EPP)
	extension for including an Allocation Token in "query" and		extension for including an Allocation Token in "query" and
	"transform" commands. The Allocation Token is used as a credential		"transform" commands. The Allocation Token is used as a credential
	that authorizes a client to request the allocation of a specific		that authorizes a client to request the allocation of a specific
	object from the server, using one of the EPP transform commands		object from the server, using one of the EPP transform commands
	including create and transfer.		including create 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 February 22, 2019.		This Internet-Draft will expire on March 8, 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 8 ¶		skipping to change at page 3, line 8 ¶
	A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 21		A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 21
	A.7. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 21		A.7. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 21
	A.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 21		A.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 21
	A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 21		A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 21
	A.10. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 21		A.10. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 21
	A.11. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 22		A.11. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 22
	A.12. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 23		A.12. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 23
	A.13. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 23		A.13. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 23
	A.14. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 24		A.14. Change from REGEXT 08 to REGEXT 09 . . . . . . . . . . . 24
	A.15. Change from REGEXT 09 to REGEXT 10 . . . . . . . . . . . 24		A.15. Change from REGEXT 09 to REGEXT 10 . . . . . . . . . . . 24
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25		A.16. Change from REGEXT 10 to REGEXT 11 . . . . . . . . . . . 25
			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], supports passing an Allocation Token as a credential that		[RFC5731], supports passing an Allocation Token as a credential that
	authorizes a client to request the allocation of a specific object		authorizes a client to request the allocation of a specific object
	from the server, using one of the EPP transform commands including		from the server, using one of the EPP transform commands including
	create and transfer.		create and transfer.
	skipping to change at page 9, line 45 ¶		skipping to change at page 9, line 45 ¶
	3.1.2. EPP <info> Command		3.1.2. EPP <info> Command
	This extension defines additional elements to extend the EPP <info>		This extension defines additional elements to extend the EPP <info>
	command of an object mapping like [RFC5731].		command of an object mapping like [RFC5731].
	The EPP <info> command allows a client to request information		The EPP <info> command allows a client to request information
	associated with an existing object. Authorized clients MAY retrieve		associated with an existing object. Authorized clients MAY retrieve
	the Allocation Token (Section 2.1) along with the other object		the Allocation Token (Section 2.1) along with the other object
	information by supplying the <allocationToken:info> element in the		information by supplying the <allocationToken:info> element in the
	command. Authorized clients MAY retrieve the Allocation Token		command. The <allocationToken:info> element is an empty element that
	(Section 2.1) along with the other object information using the		serves as a marker to the server to return the
	<allocationToken:info> element. The <allocationToken:info> element		<allocationToken:allocationToken> element in the info response. If
	is an empty element that serves as a marker to the server to return		the client is not authorized to receive the Allocation Token, the
	the <allocationToken:allocationToken> element in the info response.
	If the client is not authorized to receive the Allocation Token, the
	server MUST return an EPP error result code of 2201. If the client		server MUST return an EPP error result code of 2201. If the client
	is authorized to receive the Allocation Token, but there is no		is authorized to receive the Allocation Token, but there is no
	Allocation Token associated with the object, the server MUST return		Allocation Token associated with the object, the server MUST return
	an EPP error result code of 2303. The authorization is subject to		an EPP error result code of 2303. The authorization is subject to
	server policy.		server policy.
	Example <info> command with the allocationToken:info extension for		Example <info> command with the allocationToken:info extension for
	the allocation.example domain name:		the allocation.example domain name:
	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>		C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	skipping to change at page 25, line 45 ¶		skipping to change at page 25, line 45 ¶
	relationships and are not REQUIRED in the protocol."		relationships and are not REQUIRED in the protocol."
	5. Changed the "Authorized clients MAY retrieve..." sentence in		5. Changed the "Authorized clients MAY retrieve..." sentence in
	the "EPP <info> Command" section.		the "EPP <info> Command" section.
	6. Changed the "If the query was successful..." sentence in the		6. Changed the "If the query was successful..." sentence in the
	"EPP <info> Command" section.		"EPP <info> Command" section.
	7. Added "supplied" to the "If the supplied Allocation Token		7. Added "supplied" to the "If the supplied Allocation Token
	passed..." sentence in the "Allocation Token" section.		passed..." sentence in the "Allocation Token" section.
	8. Removed an extra newline in the <annotation> element in the		8. Removed an extra newline in the <annotation> element in the
	"Allocation Token Extension Schema" section.		"Allocation Token Extension Schema" section.
			A.16. Change from REGEXT 10 to REGEXT 11
			1. Removed the old duplicate "Authorized clients MAY retrieve..."
			sentence from section 3.1.2 "EPP <info> Command".
	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
	Kal Feher		Kal Feher
End of changes. 7 change blocks.
	11 lines changed or deleted		16 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/