draft-ietf-regext-org-ext-06.txt		draft-ietf-regext-org-ext-07.txt
	Internet Engineering Task Force L. Zhou		Internet Engineering Task Force L. Zhou
	Internet-Draft N. Kong		Internet-Draft N. Kong
	Intended status: Standards Track J. Wei		Intended status: Standards Track J. Wei
	Expires: November 10, 2018 X. Lee		Expires: December 17, 2018 X. Lee
	CNNIC		CNNIC
	J. Gould		J. Gould
	Verisign, Inc.		Verisign, Inc.
	May 9, 2018		June 15, 2018
	Organization Extension for the Extensible Provisioning Protocol (EPP)		Organization Extension for the Extensible Provisioning Protocol (EPP)
	draft-ietf-regext-org-ext-06		draft-ietf-regext-org-ext-07
	Abstract		Abstract
	This mapping which is an extension to EPP object mappings, is		This document describes an extension to EPP object mappings, which is
	designed to support assigning an organization to any existing object		designed to support assigning an organization to any existing object
	(domain, host, contact) as well as any future objects.		(domain, host, contact) as well as any future objects.
	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.
	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 November 10, 2018.		This Internet-Draft will expire on December 17, 2018.
	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 4, line 6 ¶		skipping to change at page 4, line 6 ¶
	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 specification.		relationships and are not a REQUIRED feature of this specification.
	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 to develop a conforming implementation.		character case presented to develop a conforming implementation.
	orgext-1.0 in this document is used as an abbreviation for		orgext-1.0 in this document is used as an abbreviation for
	urn:ietf:params:xml:ns:orgext-1.0.		urn:ietf:params:xml:ns:orgext-1.0. The XML namespace prefix "orgext"
			is used, but implementations MUST NOT depend on it and instead employ
			a proper namespace-aware XML parser and serializer to interpret and
			output the XML documents.
	3. Object Attributes		3. Object Attributes
	This extension adds additional elements to EPP object mappings like		This extension adds additional elements to EPP object mappings like
	the EPP domain name mapping [RFC5731]. Only the new elements are		the EPP domain name mapping [RFC5731]. Only the new elements are
	described here.		described here.
	3.1. Organization Identifier		3.1. Organization Identifier
	Organization identifier provides the ID of an organization. Its		Organization identifier provides the ID of an organization. Its
	corresponding element is <orgext:id> which refers to the		corresponding element is <orgext:id> which refers to the <org:id>
	<organization:id> element defined in [ID.draft-ietf-regext-org]. All		element defined in [ID.draft-ietf-regext-org]. All organization
	organization objects are identified by a server-unique identifier.		objects are identified by a server-unique identifier.
	4. EPP Command Mapping		4. EPP Command Mapping
	A detailed description of the EPP syntax and semantics can be found		A detailed description of the EPP syntax and semantics can be found
	in the EPP core protocol specification [RFC5730]. The command		in the EPP core protocol specification [RFC5730]. The command
	mappings described here are specifically for use in provisioning and		mappings described here are specifically for assigning organizations
	managing organization information via EPP.		to EPP objects.
	4.1. EPP Query Commands		4.1. EPP Query Commands
	EPP provides three commands to retrieve domain information: <check>		EPP provides three commands to retrieve EPP object information:
	to determine if a domain object can be provisioned within a		<check> to determine if an object can be provisioned within a
	repository, <info> to retrieve detailed information associated with a		repository, <info> to retrieve detailed information associated with
	domain object, and <transfer> to retrieve domain-object transfer		an object, and <transfer> to retrieve object transfer status
	status information.		information.
	4.1.1. EPP <check> Command		4.1.1. EPP <check> Command
	This extension does not add any elements to the EPP <check> command		This extension does not add any elements to the EPP <check> command
	or <check> response described in the EPP domain name mapping		or <check> response described in the EPP object mapping.
	[RFC5731], host mapping [RFC5732] and contact mapping [RFC5733].
	4.1.2. EPP <info> Command		4.1.2. EPP <info> Command
	This extension does not add any element to the EPP <info> command		This extension does not add any element to the EPP <info> command
	described in the EPP domain mapping [RFC5731], host mapping [RFC5732]		described in the EPP object mapping. However, additional elements
	and contact mapping [RFC5733]. However, additional elements are		are defined for the <info> response in the EPP object mapping.
	defined for the <info> response in the EPP domain mapping [RFC5731],
	host mapping [RFC5732] and contact mapping [RFC5733].
	When an <info> command has been processed successfully, the EPP		When an <info> command has been processed successfully, the EPP
	<resData> element MUST contain child elements as described in the EPP		<resData> element MUST contain child elements as described in the EPP
	object extensions. In addition, the EPP <extension> element SHOULD		object extensions. In addition, the EPP <extension> element SHOULD
	contain a child <orgext:infData> element that identifies the		contain a child <orgext:infData> element that identifies the
	extension namespace if the object has data associated with this		extension namespace if the object has data associated with this
	extension and based on server policy. The <orgext:infData> element		extension and based on server policy. The <orgext:infData> element
	contains the following child elements:		contains the following child elements:
	o Zero or more <orgext:id> elements are allowed that contains the		o Zero or more <orgext:id> elements are allowed that contains the
	skipping to change at page 7, line 50 ¶		skipping to change at page 7, line 50 ¶
	S: </trID>		S: </trID>
	S: </response>		S: </response>
	S:</epp>		S:</epp>
	An EPP error response MUST be returned if an <info> command cannot be		An EPP error response MUST be returned if an <info> command cannot be
	processed for any reason.		processed for any reason.
	4.1.3. EPP <transfer> Query Command		4.1.3. EPP <transfer> Query Command
	This extension does not add any elements to the EPP <transfer> query		This extension does not add any elements to the EPP <transfer> query
	command or <transfer> query response described in the EPP domain name		command or <transfer> query response described in the EPP object
	mapping [RFC5731], host mapping [RFC5732] and contact mapping		mapping.
	[RFC5733].
	4.2. EPP Transform Commands		4.2. EPP Transform Commands
	EPP provides five commands to transform domain objects: <create> to		EPP provides five commands to transform EPP objects: <create> to
	create an instance of a domain object, <delete> to delete an instance		create an instance of an object, <delete> to delete an instance of an
	of a domain object, <renew> to extend the validity period of a domain		object, <renew> to extend the validity period of an object,
	object, <transfer> to manage domain object sponsorship changes, and		<transfer> to manage the object sponsorship changes, and <update> to
	<update> to change information associated with a domain object.		change information associated with an object.
	4.2.1. EPP <create> Command		4.2.1. EPP <create> Command
	This extension defines additional elements for the EPP <create>		This extension defines additional elements for the EPP <create>
	command described in the EPP object extensions. No additional		command described in the EPP object extensions. No additional
	elements are defined for the EPP <create> response.		elements are defined for the EPP <create> response.
	The EPP <create> command provides a transform operation that allows a		The EPP <create> command provides a transform operation that allows a
	client to create an object. In addition to the EPP command elements		client to create an object. In addition to the EPP command elements
	described in the EPP object extensions, the command MUST contain an		described in the EPP object extensions, the command MUST contain an
	skipping to change at page 10, line 45 ¶		skipping to change at page 10, line 45 ¶
	When a <create> command has been processed successfully, the EPP		When a <create> command has been processed successfully, the EPP
	response is as described in the EPP object extension.		response is as described in the EPP object extension.
	An EPP error response MUST be returned if a <create> command cannot		An EPP error response MUST be returned if a <create> command cannot
	be processed for any reason.		be processed for any reason.
	4.2.2. EPP <delete> Command		4.2.2. EPP <delete> Command
	This extension does not add any elements to the EPP <delete> command		This extension does not add any elements to the EPP <delete> command
	or <delete> response described in the EPP domain mapping [RFC5731],		or <delete> response described in the EPP object mapping.
	host mapping [RFC5732] and contact mapping [RFC5733].
	4.2.3. EPP <renew> Command		4.2.3. EPP <renew> Command
	This extension does not add any elements to the EPP <renew> command		This extension does not add any elements to the EPP <renew> command
	or <renew> response described in the EPP domain mapping [RFC5731],		or <renew> response described in the EPP object mapping.
	host mapping [RFC5732] and contact mapping [RFC5733].
	4.2.4. EPP <transfer> Command		4.2.4. EPP <transfer> Command
	This extension does not add any elements to the EPP <transfer>		This extension does not add any elements to the EPP <transfer>
	command or <transfer> response described in the EPP domain mapping		command or <transfer> response described in the EPP object mapping,
	[RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but		but after a successful transfer of an object with an assigned
	after a successful transfer of an object with an assigned
	organization, the handling of the assigned organization is dependent		organization, the handling of the assigned organization is dependent
	on the organization roles and server policy.		on the organization roles and server policy.
	4.2.5. EPP <update> Command		4.2.5. EPP <update> Command
	This extension defines additional elements for the EPP <update>		This extension defines additional elements for the EPP <update>
	command described in the EPP domain mapping [RFC5731], host mapping		command described in the EPP domain mapping [RFC5731], host mapping
	[RFC5732] and contact mapping [RFC5733]. No additional elements are		[RFC5732] and contact mapping [RFC5733]. No additional elements are
	defined for the EPP <update> response.		defined for the EPP <update> response.
	The EPP <update> command provides a transform operation that allows a		The EPP <update> command provides a transform operation that allows a
	client to modify the attribute of an object. In addition to the EPP		client to modify the attributes of an object. In addition to the EPP
	<update> command elements, the command MUST contain an <extension>		<update> command elements, the command MUST contain an <extension>
	element, and the <extension> element MUST contain a child		element, and the <extension> element MUST contain a child
	<orgext:update> element that identifies the extension namespace if		<orgext:update> element that identifies the extension namespace if
	the client wants to update the object with data defined in this		the client wants to update the object with data defined in this
	extension. The <orgext:update> element contains the following child		extension. The <orgext:update> element contains the following child
	elements:		elements:
	o An OPTIONAL <orgext:add> element that contains attribute values to		o An OPTIONAL <orgext:add> element that contains attribute values to
	be added to the object.		be added to the object.
	skipping to change at page 17, line 35 ¶		skipping to change at page 17, line 35 ¶
	6. Internationalization Considerations		6. Internationalization Considerations
	EPP is represented in XML, which provides native support for encoding		EPP is represented in XML, which provides native support for encoding
	information using the Unicode character set and its more compact		information using the Unicode character set and its more compact
	representations including UTF-8. Conformant XML processors recognize		representations including UTF-8. Conformant XML processors recognize
	both UTF-8 and UTF-16. Though XML includes provisions to identify		both UTF-8 and UTF-16. Though XML includes provisions to identify
	and use other character encodings through use of an "encoding"		and use other character encodings through use of an "encoding"
	attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.		attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.
	As an extension of the EPP domain name mapping, the elements, element		As an extension of the EPP object mapping, the elements, element
	content described in this document MUST inherit the		content described in this document MUST inherit the
	internationalization conventions used to represent higher-layer		internationalization conventions used to represent higher-layer
	domain and core protocol structures present in an XML instance that		domain and core protocol structures present in an XML instance that
	includes this extension.		includes this extension.
	7. IANA Considerations		7. IANA Considerations
	7.1. XML Namespace		7.1. XML Namespace
	This document uses URNs to describe XML namespaces and XML schemas		This document uses URNs to describe XML namespaces and XML schemas
	skipping to change at page 23, line 29 ¶		skipping to change at page 23, line 29 ¶
	Organization WG document-06:		Organization WG document-06:
	* Updated "Abstraction".		* Updated "Abstraction".
	* Added "Query" for "<Transfer> Query Command".		* Added "Query" for "<Transfer> Query Command".
	* Change "Registrant Contact" to IESG in section 7.1.		* Change "Registrant Contact" to IESG in section 7.1.
	* Modified section 7.2.		* Modified section 7.2.
			Organization WG document-07:
			* Updated "Abstraction".
	Authors' Addresses		Authors' Addresses
	Linlin Zhou		Linlin Zhou
	CNNIC		CNNIC
	4 South 4th Street, Zhongguancun, Haidian District		4 South 4th Street, Zhongguancun, Haidian District
	Beijing, Beijing 100190		Beijing, Beijing 100190
	China		China
	Phone: +86 10 5881 2677		Phone: +86 10 5881 2677
	Email: zhoulinlin@cnnic.cn		Email: zhoulinlin@cnnic.cn
End of changes. 19 change blocks.
	39 lines changed or deleted		39 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/