Diff: draft-ietf-regext-org-05.txt - draft-ietf-regext-org-06.txt

	draft-ietf-regext-org-05.txt	draft-ietf-regext-org-06.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 G. Zhou	Intended status: Standards Track G. Zhou

	Expires: November 8, 2018 X. Lee	Expires: November 10, 2018 X. Lee
	CNNIC	CNNIC
	J. Gould	J. Gould
	Verisign, Inc.	Verisign, Inc.

	May 7, 2018	May 9, 2018

	Extensible Provisioning Protocol (EPP) Organization Mapping	Extensible Provisioning Protocol (EPP) Organization Mapping

	draft-ietf-regext-org-05	draft-ietf-regext-org-06

	Abstract	Abstract

	This document describes an Extensible Provisioning Protocol (EPP)	This document describes an Extensible Provisioning Protocol (EPP)
	mapping for provisioning and management of organization objects	mapping for provisioning and management of organization objects
	stored in a shared central repository. Specified in Extensible	stored in a shared central repository. Specified in Extensible
	Markup Language (XML), this extended mapping is applied to provide	Markup Language (XML), this extended mapping is applied to provide
	additional features required for the provisioning of organizations.	additional features required for the provisioning of organizations.

	Status of This Memo	Status of This Memo

	skipping to change at page 1, line 38 ¶	skipping to change at page 1, line 38 ¶
	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 8, 2018.	This Internet-Draft will expire on November 10, 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 2, line 41 ¶	skipping to change at page 2, line 41 ¶
	3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5	3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5
	3.4. Organization Status Values . . . . . . . . . . . . . . . 5	3.4. Organization Status Values . . . . . . . . . . . . . . . 5
	3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6	3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6
	3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7	3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7
	3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7	3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
	3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 7	3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 7
	4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7	4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7
	4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7	4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7
	4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8	4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8
	4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 9	4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 9

	4.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 15	4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 15
	4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15	4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15
	4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 15	4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 15
	4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19	4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19
	4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20	4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20
	4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20	4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20
	4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21	4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21
	5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25	5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25
	6. Internationalization Considerations . . . . . . . . . . . . . 33	6. Internationalization Considerations . . . . . . . . . . . . . 33
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
	7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 33	7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 33
	7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 34	7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 34
	7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 34	7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 34
	7.3.1. Registration Template . . . . . . . . . . . . . . . . 34	7.3.1. Registration Template . . . . . . . . . . . . . . . . 34

	7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 35	7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 34
	8. Implementation Status . . . . . . . . . . . . . . . . . . . . 35	8. Implementation Status . . . . . . . . . . . . . . . . . . . . 35
	8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 36	8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 36
	8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 36	8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 36
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 36	9. Security Considerations . . . . . . . . . . . . . . . . . . . 36
	10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 37	10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 37
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
	11.1. Normative References . . . . . . . . . . . . . . . . . . 37	11.1. Normative References . . . . . . . . . . . . . . . . . . 37
	11.2. Informative References . . . . . . . . . . . . . . . . . 38	11.2. Informative References . . . . . . . . . . . . . . . . . 38
	Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 38	Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 38
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40

	skipping to change at page 7, line 50 ¶	skipping to change at page 7, line 50 ¶
	mappings described here are specifically for use in provisioning and	mappings described here are specifically for use in provisioning and
	managing organization information via EPP.	managing organization information via EPP.

	4.1. EPP Query Commands	4.1. EPP Query Commands

	EPP provides two commands to retrieve organization information:	EPP provides two commands to retrieve organization information:
	<check> to determine if an organization object can be provisioned	<check> to determine if an organization object can be provisioned
	within a repository, and <info> to retrieve detailed information	within a repository, and <info> to retrieve detailed information
	associated with an organization object. This document does not	associated with an organization object. This document does not
	define a mapping for the EPP <transfer> command to retrieve	define a mapping for the EPP <transfer> command to retrieve

	organization-object transfer status information..	organization-object transfer status information.

	4.1.1. EPP <check> Command	4.1.1. EPP <check> Command

	The EPP <check> command is used to determine if an object can be	The EPP <check> command is used to determine if an object can be
	provisioned within a repository. It provides a hint that allows a	provisioned within a repository. It provides a hint that allows a
	client to anticipate the success or failure of provisioning an object	client to anticipate the success or failure of provisioning an object
	using the <create> command, as object-provisioning requirements are	using the <create> command, as object-provisioning requirements are
	ultimately a matter of server policy.	ultimately a matter of server policy.

	In addition to the standard EPP command elements, the <check> command	In addition to the standard EPP command elements, the <check> command

	skipping to change at page 12, line 36 ¶	skipping to change at page 12, line 36 ¶

	o A <org:upID> element that contains the identifier of the client	o A <org:upID> element that contains the identifier of the client
	that last updated the organization object. This element MUST NOT	that last updated the organization object. This element MUST NOT
	be present if the organization has never been modified.	be present if the organization has never been modified.

	o A <org:upDate> element that contains the date and time of the most	o A <org:upDate> element that contains the date and time of the most
	recent organization object modification. This element MUST NOT be	recent organization object modification. This element MUST NOT be
	present if the organization object has never been modified.	present if the organization object has never been modified.

	Example <info> response for "Example Registrar Inc." organization	Example <info> response for "Example Registrar Inc." organization

	object with registrar identifier "1362":	organization object with identifier "registrar1362":

	S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>
	S: <resData>	S: <resData>
	S: <org:infData	S: <org:infData
	S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">	S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">

	skipping to change at page 13, line 41 ¶	skipping to change at page 13, line 41 ¶
	S: </org:infData>	S: </org:infData>
	S: </resData>	S: </resData>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54322-XYZ</svTRID>	S: <svTRID>54322-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>
	S:</epp>	S:</epp>

	Example <info> response for "Example Reseller Inc." organization	Example <info> response for "Example Reseller Inc." organization

	object of reseller type managed by registrar identifier "1362":	object of reseller type managed by identifier "registrar1362":

	S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>
	S: <resData>	S: <resData>
	S: <org:infData	S: <org:infData
	S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">	S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">

	skipping to change at page 14, line 37 ¶	skipping to change at page 14, line 37 ¶
	S: <org:street>Suite 100</org:street>	S: <org:street>Suite 100</org:street>
	S: <org:city>Dulles</org:city>	S: <org:city>Dulles</org:city>
	S: <org:sp>VA</org:sp>	S: <org:sp>VA</org:sp>
	S: <org:pc>20166-6503</org:pc>	S: <org:pc>20166-6503</org:pc>
	S: <org:cc>US</org:cc>	S: <org:cc>US</org:cc>
	S: </org:addr>	S: </org:addr>
	S: </org:postalInfo>	S: </org:postalInfo>
	S: <org:fax>+1.7035555556</org:fax>	S: <org:fax>+1.7035555556</org:fax>
	S: <org:url>http://organization.example</org:url>	S: <org:url>http://organization.example</org:url>
	S: <org:contact type="admin">sh8013</org:contact>	S: <org:contact type="admin">sh8013</org:contact>

	S: <org:clID>1362</org:crID>	S: <org:clID>1362</org:clID>
	S: <org:crID>ClientX</org:crID>	S: <org:crID>ClientX</org:crID>
	S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate>	S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate>
	S: <org:upID>ClientX</org:upID>	S: <org:upID>ClientX</org:upID>
	S: <org:upDate>1999-12-03T09:00:00.0Z</org:upDate>	S: <org:upDate>1999-12-03T09:00:00.0Z</org:upDate>
	S: </org:infData>	S: </org:infData>
	S: </resData>	S: </resData>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54322-XYZ</svTRID>	S: <svTRID>54322-XYZ</svTRID>
	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> Command	4.1.3. EPP <transfer> Query Command

	The transfer semantics does not apply to organization object. No EPP	The transfer semantics does not apply to organization object. No EPP

	<transfer> command is defined in this document.	<transfer> query command is defined in this document.

	4.2. EPP Transform Commands	4.2. EPP Transform Commands

	This document provides three commands to transform organization	This document provides three commands to transform organization
	object information: <create> to create an instance of an organization	object information: <create> to create an instance of an organization
	object, <delete> to delete an instance of an organization object, and	object, <delete> to delete an instance of an organization object, and
	<update> to change information associated with an organization	<update> to change information associated with an organization
	object. This document does not define a mapping for the EPP	object. This document does not define a mapping for the EPP
	<transfer> and <renew> command.	<transfer> and <renew> command.


	skipping to change at page 24, line 24 ¶	skipping to change at page 24, line 24 ¶
	C: <org:role>	C: <org:role>
	C: <org:type>privacyproxy</org:type>	C: <org:type>privacyproxy</org:type>
	C: <org:status>clientLinkProhibited</org:status>	C: <org:status>clientLinkProhibited</org:status>
	C: </org:role>	C: </org:role>
	C: <org:status>clientLinkProhibited</org:status>	C: <org:status>clientLinkProhibited</org:status>
	C: </org:add>	C: </org:add>
	C: <org:rem>	C: <org:rem>
	C: <org:contact type="billing">sh8014</org:contact>	C: <org:contact type="billing">sh8014</org:contact>
	C: <org:role>	C: <org:role>
	C: <org:type>reseller</org:type>	C: <org:type>reseller</org:type>

	C: <org:status>clientDeleteProhibited</org:status>
	C: </org:role>	C: </org:role>
	C: </org:rem>	C: </org:rem>
	C: <org:chg>	C: <org:chg>
	C: <org:postalInfo type="int">	C: <org:postalInfo type="int">
	C: <org:addr>	C: <org:addr>
	C: <org:street>124 Example Dr.</org:street>	C: <org:street>124 Example Dr.</org:street>
	C: <org:street>Suite 200</org:street>	C: <org:street>Suite 200</org:street>
	C: <org:city>Dulles</org:city>	C: <org:city>Dulles</org:city>
	C: <org:sp>VA</org:sp>	C: <org:sp>VA</org:sp>
	C: <org:pc>20166-6503</org:pc>	C: <org:pc>20166-6503</org:pc>

	skipping to change at page 33, line 43 ¶	skipping to change at page 33, line 43 ¶
	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
	conforming to a registry mechanism described in [RFC3688]. IANA is	conforming to a registry mechanism described in [RFC3688]. IANA is
	requested to assignment the following URI.	requested to assignment the following URI.

	Registration request for the organization namespace:	Registration request for the organization namespace:

	URI: urn:ietf:params:xml:ns:org-1.0	URI: urn:ietf:params:xml:ns:org-1.0


	Registrant Contact: See the "Author's Address" section of this	Registrant Contact: IESG
	document.

	XML: None. Namespace URIs do not represent an XML specification.	XML: None. Namespace URIs do not represent an XML specification.

	Registration request for the organization XML schema:	Registration request for the organization XML schema:

	URI: urn:ietf:params:xml:ns:org-1.0	URI: urn:ietf:params:xml:ns:org-1.0

	Registrant Contact: See the "Author's Address" section of this
	document.


		Registrant Contact: IESG
	XML: See the "Formal Syntax" section of this document.	XML: See the "Formal Syntax" section of this document.

	7.2. EPP Extension Registry	7.2. EPP Extension Registry

	The EPP extension described in this document should be registered by	The EPP extension described in this document should be registered by
	the IANA in the EPP Extension Registry described in [RFC7451]. The	the IANA in the EPP Extension Registry described in [RFC7451]. The
	details of the registration are as follows:	details of the registration are as follows:


	Name of Extension: Organization Object Extension	Name of Extension: Extensible Provisioning Protocol (EPP)
		Organization Mapping
	Document status: Standards Track

	Reference: (insert reference to RFC version of this document)


	Registrant Name and Email Address: IESG	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

	7.3. Role Values Registry	7.3. Role Values Registry

	The following values should be registered by the IANA in the "EPP	The following values should be registered by the IANA in the "EPP
	Organization Role Values" registry. The registration policy for this	Organization Role Values" registry. The registration policy for this
	registry is "Expert Review" [RFC8126].	registry is "Expert Review" [RFC8126].

	7.3.1. Registration Template	7.3.1. Registration Template

	Value: the string value being registered.	Value: the string value being registered.

	skipping to change at page 40, line 18 ¶	skipping to change at page 40, line 12 ¶

	Organization WG document-05:	Organization WG document-05:

	* Updated the description of <org:status> of a role.	* Updated the description of <org:status> of a role.

	* Removed the third paragraph of "Implementation Status".	* Removed the third paragraph of "Implementation Status".

	* Remove the Informative Reference to draft-ietf-regext-reseller	* Remove the Informative Reference to draft-ietf-regext-reseller
	from the draft.	from the draft.


		Organization WG document-06:

		* Updated typos.

		* Added "Query" for "<Transfer> Query Command".

		* Change "Registrant Contact" to IESG in section 7.1.

		* Modified section 7.2.

	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

	skipping to change at page 41, line 10 ¶	skipping to change at page 41, line 10 ¶
	China	China

	Phone: +86 10 5881 2692	Phone: +86 10 5881 2692
	Email: zhouguiqing@cnnic.cn	Email: zhouguiqing@cnnic.cn
	Xiaodong Lee	Xiaodong Lee
	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 3020
	Email: xl@cnnic.cn	Email: xl@cnnic.cn

	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

End of changes. 24 change blocks.
	28 lines changed or deleted	31 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/