draft-ietf-regext-org-04.txt		draft-ietf-regext-org-05.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 5, 2018 X. Lee		Expires: November 8, 2018 X. Lee
	CNNIC		CNNIC
	J. Gould		J. Gould
	Verisign, Inc.		Verisign, Inc.
	May 4, 2018		May 7, 2018
	Extensible Provisioning Protocol (EPP) Organization Mapping		Extensible Provisioning Protocol (EPP) Organization Mapping
	draft-ietf-regext-org-04		draft-ietf-regext-org-05
	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 5, 2018.		This Internet-Draft will expire on November 8, 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 3, line 11 ¶		skipping to change at page 3, line 11 ¶
	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 . . . . . . . . . . . . . . 35
	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
	8.3. Reseller Extension . . . . . . . . . . . . . . . . . . . 37		9. Security Considerations . . . . . . . . . . . . . . . . . . . 36
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 37
	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
	1. Introduction		1. Introduction
	There are many entities, such as registrars, resellers, DNS service		There are many entities, such as registrars, resellers, DNS service
	skipping to change at page 10, line 43 ¶		skipping to change at page 10, line 43 ¶
	o A <org:roid> element that contains the Repository Object		o A <org:roid> element that contains the Repository Object
	IDentifier assigned to the organization object when the object was		IDentifier assigned to the organization object when the object was
	created.		created.
	o One or more <org:role> elements that contains the role type, role		o One or more <org:role> elements that contains the role type, role
	statuses and optional role id of the organization.		statuses and optional role id of the organization.
	* A <org:type> element that contains the type of the		* A <org:type> element that contains the type of the
	organization, as defined in Section 3.2.		organization, as defined in Section 3.2.
	* Zero or more <org:status> elements that contains the role type.		* One or more <org:status> elements that contains the role
	The values of the role status are defined in Section 3.5.		statuses. The values of the role status are defined in
			Section 3.5.
	* An OPTIONAL <org:roleid> element that contains a third party		* An OPTIONAL <org:roleid> element that contains a third party
	assigned identifier, such as IANA ID for registrars, as defined		assigned identifier, such as IANA ID for registrars, as defined
	in Section 3.2.3.		in Section 3.2.3.
	o Zero or more <org:status> elements that contains the operational		o Zero or more <org:status> elements that contains the operational
	status of the organization, as defined in Section 3.4.		status of the organization, as defined in Section 3.4.
	o An OPTIONAL <org:parentId> element that contains the identifier of		o An OPTIONAL <org:parentId> element that contains the identifier of
	the parent object, as defined in Section 3.6.		the parent object, as defined in Section 3.6.
	skipping to change at page 16, line 8 ¶		skipping to change at page 16, line 8 ¶
	o A <org:id> element that contains the desired server-unique		o A <org:id> element that contains the desired server-unique
	identifier for the organization to be created, as defined in		identifier for the organization to be created, as defined in
	Section 3.1.		Section 3.1.
	o One or more <org:role> elements that contains the role type, role		o One or more <org:role> elements that contains the role type, role
	statuses and optional role id of the organization.		statuses and optional role id of the organization.
	* A <org:type> element that contains the type of the		* A <org:type> element that contains the type of the
	organization, as defined in Section 3.2.		organization, as defined in Section 3.2.
	* Zero or more <org:status> elements that contains the role type.		* Zero or more <org:status> elements that contains the role
	The values of the role status are defined in Section 3.5.		statuses. The values of the role status are defined in
			Section 3.5.
	* An OPTIONAL <org:roleid> element that contains a third party		* An OPTIONAL <org:roleid> element that contains a third party
	assigned identifier, such as IANA ID for registrars, as defined		assigned identifier, such as IANA ID for registrars, as defined
	in Section 3.2.3.		in Section 3.2.3.
	o Zero of more <org:status> element that contains the operational		o Zero of more <org:status> element that contains the operational
	status of the organization, as defined in Section 3.4.		status of the organization, as defined in Section 3.4.
	o An OPTIONAL <org:parentId> element that contains the identifier of		o An OPTIONAL <org:parentId> element that contains the identifier of
	the parent object, as defined in Section 3.6.		the parent object, as defined in Section 3.6.
	skipping to change at page 21, line 43 ¶		skipping to change at page 21, line 43 ¶
	organization object. Contact object identifiers MUST be known to		organization object. Contact object identifiers MUST be known to
	the server before the contact object can be associated with the		the server before the contact object can be associated with the
	organization object.		organization object.
	o Zero or more <org:role> elements that contains the role type, role		o Zero or more <org:role> elements that contains the role type, role
	statuses and optional role id of the organization.		statuses and optional role id of the organization.
	* A <org:type> element that contains the type of the		* A <org:type> element that contains the type of the
	organization, as defined in Section 3.2.		organization, as defined in Section 3.2.
	* Zero or more <org:status> elements that contains the role type.		* Zero or more <org:status> elements that contains the role
	The values of the role status are defined in Section 3.5.		statuses. The values of the role status are defined in
			Section 3.5.
	* An OPTIONAL <org:roleid> element that contains a third party		* An OPTIONAL <org:roleid> element that contains a third party
	assigned identifier, such as IANA ID for registrars, as defined		assigned identifier, such as IANA ID for registrars, as defined
	in Section 3.2.3.		in Section 3.2.3.
	o Zero or more <org:status> element that contains the operational		o Zero or more <org:status> element that contains the operational
	status of the organization.		status of the organization.
	A OPTIONAL <org:chg> element contains the following child elements,		An OPTIONAL <org:chg> element contains the following child elements,
	where at least one child element MUST be present:		where at least one child element MUST be present:
	o An OPTIONAL <org:parentId> element that contains the identifier of		o An OPTIONAL <org:parentId> element that contains the identifier of
	the parent object.		the parent object.
	o Zero to two <org:postalInfo> elements that contain postal-address		o Zero to two <org:postalInfo> elements that contain postal-address
	information. Two elements are provided so that address		information. Two elements are provided so that address
	information can be provided in both internationalized and		information can be provided in both internationalized and
	localized forms; a "type" attribute is used to identify the two		localized forms; a "type" attribute is used to identify the two
	forms. If an internationalized form (type="int") is provided,		forms. If an internationalized form (type="int") is provided,
	skipping to change at page 36, line 12 ¶		skipping to change at page 36, line 12 ¶
	be, a catalog of available implementations or their features.		be, a catalog of available implementations or their features.
	Readers are advised to note that other implementations may exist.		Readers are advised to note that other implementations may exist.
	According to [RFC7942], "this will allow reviewers and working groups		According to [RFC7942], "this will allow reviewers and working groups
	to assign due consideration to documents that have the benefit of		to assign due consideration to documents that have the benefit of
	running code, which may serve as evidence of valuable experimentation		running code, which may serve as evidence of valuable experimentation
	and feedback that have made the implemented protocols more mature.		and feedback that have made the implemented protocols more mature.
	It is up to the individual working groups to use this information as		It is up to the individual working groups to use this information as
	they see fit".		they see fit".
	Verisign has already implemented this object mapping. CNNIC and
	Net::DRI (Patrick Mevzek) are in the process of development research
	to update organization objecct from reseller object. Dns Belgium is
	planning to implement it after the publication of this document.
	8.1. Verisign EPP SDK		8.1. Verisign EPP SDK
	Organization: Verisign Inc.		Organization: Verisign Inc.
	Name: Verisign EPP SDK		Name: Verisign EPP SDK
	Description: The Verisign EPP SDK includes both a full client		Description: The Verisign EPP SDK includes both a full client
	implementation and a full server stub implementation of draft-ietf-		implementation and a full server stub implementation of draft-ietf-
	regext-org.		regext-org.
	skipping to change at page 37, line 5 ¶		skipping to change at page 36, line 48 ¶
	Description: CNNIC is trying to update EPP organization mapping from		Description: CNNIC is trying to update EPP organization mapping from
	previous reseller mapping according to this document.		previous reseller mapping according to this document.
	Level of maturity: Development		Level of maturity: Development
	Coverage: EPP organization mapping		Coverage: EPP organization mapping
	Contact: zhouguiqing@cnnic.cn		Contact: zhouguiqing@cnnic.cn
	8.3. Reseller Extension
	This document was updated from [ID.draft-ietf-regext-reseller].
	CNNIC, Verisign and Net::DRI (Patrick Mevzek) have already
	implemented the reseller mapping.
	9. Security Considerations		9. Security Considerations
	The object mapping extension described in this document does not		The object mapping extension described in this document does not
	provide any other security services or introduce any additional		provide any other security services or introduce any additional
	considerations beyond those described by [RFC5730] or those caused by		considerations beyond those described by [RFC5730] or those caused by
	the protocol layers used by EPP. The security considerations		the protocol layers used by EPP. The security considerations
	described in these other specifications apply to this specification		described in these other specifications apply to this specification
	as well.		as well.
	10. Acknowledgment		10. Acknowledgment
	skipping to change at page 38, line 27 ¶		skipping to change at page 38, line 20 ¶
	<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.		<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
	[W3C.REC-xmlschema-2-20041028]		[W3C.REC-xmlschema-2-20041028]
	Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes		Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes
	Second Edition", World Wide Web Consortium Recommendation		Second Edition", World Wide Web Consortium Recommendation
	REC-xmlschema-2-20041028", October 2004,		REC-xmlschema-2-20041028", October 2004,
	<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.		<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
	11.2. Informative References		11.2. Informative References
	[ID.draft-ietf-regext-reseller]
	Zhou, L., Kong, N., Guiqing, G., Lee, X., and J. Gould,
	"Extensible Provisioning Protocol (EPP) Reseller Mapping",
	Dec 2016,
	<http://tools.ietf.org/html/draft-ietf-regext-reseller>.
	[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, <https://www.rfc-editor.org/info/rfc7451>.		February 2015, <https://www.rfc-editor.org/info/rfc7451>.
	Appendix A. Change Log		Appendix A. Change Log
	Initial -00: Individual document submitted.		Initial -00: Individual document submitted.
	-01:		-01:
	skipping to change at page 40, line 21 ¶		skipping to change at page 40, line 9 ¶
	Organization WG document-04:		Organization WG document-04:
	* Updated section 3.2, changed the structure of organization		* Updated section 3.2, changed the structure of organization
	role.		role.
	* Updated references.		* Updated references.
	* Updated section 8 of implementation status.		* Updated section 8 of implementation status.
			Organization WG document-05:
			* Updated the description of <org:status> of a role.
			* Removed the third paragraph of "Implementation Status".
			* Remove the Informative Reference to draft-ietf-regext-reseller
			from the draft.
	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. 13 change blocks.
	30 lines changed or deleted		24 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/