draft-ietf-regext-bundling-registration-02.txt		draft-ietf-regext-bundling-registration-03.txt
	Internet Engineering Task Force N. Kong		Internet Engineering Task Force N. Kong
	Internet-Draft J. Yao, Ed.		Internet-Draft J. Yao, Ed.
	Intended status: Standards Track X. Li		Intended status: Informational X. Li
	Expires: April 29, 2018 CNNIC		Expires: October 30, 2018 CNNIC
	W. Tan		W. Tan
	Cloud Registry		Cloud Registry
	J. Xie		J. Xie
	October 26, 2017		April 28, 2018
	Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for		Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for
	Strict Bundling Registration		Strict Bundling Registration
	draft-ietf-regext-bundling-registration-02		draft-ietf-regext-bundling-registration-03
	Abstract		Abstract
	This document describes an extension of Extensible Provisioning		This document describes an extension of Extensible Provisioning
	Protocol (EPP) domain name mapping for the provisioning and		Protocol (EPP) domain name mapping for the provisioning and
	management of strict bundling registration of domain names.		management of strict bundling registration of domain names.
	Specified in XML, this mapping extends the EPP domain name mapping to		Specified in XML, this mapping extends the EPP domain name mapping to
	provide additional features required for the provisioning of bundled		provide additional features required for the provisioning of bundled
	domain names.		domain names.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 39 ¶
	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 April 29, 2018.		This Internet-Draft will expire on October 30, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 32 ¶		skipping to change at page 2, line 32 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4		3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
	4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5		4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	5. Requirement for Bundling Registration of Names . . . . . . . 5		5. Requirement for Bundling Registration of Names . . . . . . . 5
	6. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6		6. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6
	6.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6		6.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6		6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
	7. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7		7. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7
	7.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7		7.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7
	7.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7		7.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7
	7.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 8		7.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 8
	7.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 10		7.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 10
	7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10		7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10
	7.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11		7.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11
	7.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 12		7.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 12
	7.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 13		7.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 13
	7.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 14		7.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 14
	skipping to change at page 3, line 9 ¶		skipping to change at page 3, line 9 ¶
	11. Security Considerations . . . . . . . . . . . . . . . . . . . 17		11. Security Considerations . . . . . . . . . . . . . . . . . . . 17
	12. Implementation Status . . . . . . . . . . . . . . . . . . . . 17		12. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
	13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17		13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
	14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18		14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18
	14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18		14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18
	14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18		14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18
	14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18		14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18
	14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18		14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18
	14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 18		14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 18
	14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18		14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18
			14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 18
	15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18		15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
	15.1. Normative References . . . . . . . . . . . . . . . . . . 18		15.1. Normative References . . . . . . . . . . . . . . . . . . 18
	15.2. Informative References . . . . . . . . . . . . . . . . . 20		15.2. Informative References . . . . . . . . . . . . . . . . . 20
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
	1. Introduction		1. Introduction
	Bundled domain names are those which share the same TLD but whose		Bundled domain names are those which share the same TLD but whose
	second level labels are variants, or those which has identical second		second level labels are variants, or those which has identical second
	level labels for which certain parameters are shared in different		level labels for which certain parameters are shared in different
	TLDs. For example, Public Interest Registry, request to implement		TLDs. For example, Public Interest Registry, request to implement
	technical bundling of second level domains for .NGO and .ONG. So we		technical bundling of second level domains for .NGO and .ONG. So we
	have two kinds of bundled domain names. First one is in the form of		have two kinds of bundled domain names. First one is in the form of
	"V-label.TLD" in which the second level labels (V-label) are variants		"V-label.TLD" in which the second level labels (V-label) are variants
	sharing the same TLD; Second one is in the form of "LABEL.V-tld" in		sharing the same TLD; Second one is in the form of "LABEL.V-tld" in
	which the second level labels(LABEL) are same ending with the		which the second level labels(LABEL) are same ending with the
	different TLDs (V-tld);		different TLDs (V-tld);
	There are several kinds of bundling. First one is strict bundling,		Bundled domain names normally share some attributes. There are three
	which requires all bundled names to share many same attributes. When		types of bundling. First one is strict bundling, which requires all
	creating, updating, or transfering of any of the bundled domain		bundled names to share many same attributes. When creating,
	names, all bundled domain names will be created, updated or		updating, or transferring of any of the bundled domain names, all
	transferred. Second one is partial bundling, which requires that at		bundled domain names will be created, updated or transferred. Second
	least the bundled domain names if registered should be registered by		one is partial bundling, which requires that at least the bundled
	the same registrant. Third one is relax bundling, which has not		domain names if registered should be registered by the same
	specific requirements to the domain registration. This document		registrant. Third one is relax bundling, which has not specific
	mainly focus on strict bundling names registration.		requirements to the domain registration. This document mainly focus
			on strict bundling names registration.
	For the name variants, some registries adopt the policy that variant		For the name variants, some registries adopt the policy that variant
	IDNs which are identified as equivalent are allocated or delegated to		IDNs which are identified as equivalent are allocated or delegated to
	the same registrant. For example, the specified registration policy		the same registrant. For example, the specified registration policy
	of Chinese Domain Name (CDN) is that a registrant can apply an		of Chinese Domain Name (CDN) is that a registrant can apply an
	original CDN in any forms: Simplified Chinese (SC) form, Traditional		original CDN in any forms: Simplified Chinese (SC) form, Traditional
	Chinese (TC) form, or other variant forms, then the corresponding		Chinese (TC) form, or other variant forms, then the corresponding
	variant CDN in SC form and that in TC form will also be delegated to		variant CDN in SC form and that in TC form will also be delegated to
	the same registrant. All variant names in the same TLD contain same		the same registrant. All variant names in the same TLD contain same
	attributes.		attributes.
	skipping to change at page 18, line 38 ¶		skipping to change at page 18, line 38 ¶
	14.5. draft-ietf-regext-bundle-mapping: Version 01		14.5. draft-ietf-regext-bundle-mapping: Version 01
	o make this document to focus on the restrict bundled domain name		o make this document to focus on the restrict bundled domain name
	registration.		registration.
	14.6. draft-ietf-regext-bundle-mapping: Version 02		14.6. draft-ietf-regext-bundle-mapping: Version 02
	o Update the section of implementation status.		o Update the section of implementation status.
			14.7. draft-ietf-regext-bundle-mapping: Version 03
			o This document is changed to informational category.
			o Refine the text.
	15. References		15. References
	15.1. Normative References		15.1. 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,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://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,
End of changes. 10 change blocks.
	17 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/