draft-ietf-regext-epp-eai-01.txt		draft-ietf-regext-epp-eai-02.txt
	Network Working Group D. Belyavskiy		Network Working Group D. Belyavskiy
	Internet-Draft		Internet-Draft
	Intended status: Standards Track J. Gould		Intended status: Standards Track J. Gould
	Expires: 26 January 2022 VeriSign, Inc.		Expires: 9 February 2022 VeriSign, Inc.
	25 July 2021		8 August 2021
	Use of Internationalized Email Addresses in EPP protocol		Use of Internationalized Email Addresses in EPP protocol
	draft-ietf-regext-epp-eai-01		draft-ietf-regext-epp-eai-02
	Abstract		Abstract
	This document describes an EPP extension that permits usage of		This document describes an EPP extension that permits usage of
	Internationalized Email Addresses in the EPP protocol and specifies		Internationalized Email Addresses in the EPP protocol and specifies
	the terms when it can be used by EPP clients and servers. The		the terms when it can be used by EPP clients and servers. The
	Extensible Provisioning Protocol (EPP), being developed before		Extensible Provisioning Protocol (EPP), being developed before
	appearing the standards for Internationalized Email Addresses (EAI),		appearing the standards for Internationalized Email Addresses (EAI),
	does not support such email addresses.		does not support such email addresses.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 26 January 2022.		This Internet-Draft will expire on 9 February 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	skipping to change at page 2, line 25 ¶		skipping to change at page 2, line 25 ¶
	2. Migrating to Newer Versions of This Extension . . . . . . . . 3		2. Migrating to Newer Versions of This Extension . . . . . . . . 3
	3. Email Address Specification . . . . . . . . . . . . . . . . . 3		3. Email Address Specification . . . . . . . . . . . . . . . . . 3
	4. Functional Extension . . . . . . . . . . . . . . . . . . . . 4		4. Functional Extension . . . . . . . . . . . . . . . . . . . . 4
	5. Internationalized Email Addresses (EAI) Functional		5. Internationalized Email Addresses (EAI) Functional
	Extension . . . . . . . . . . . . . . . . . . . . . . . . 4		Extension . . . . . . . . . . . . . . . . . . . . . . . . 4
	5.1. Scope of Functional Extension . . . . . . . . . . . . . . 4		5.1. Scope of Functional Extension . . . . . . . . . . . . . . 4
	5.2. Signaling Client and Server Support . . . . . . . . . . . 5		5.2. Signaling Client and Server Support . . . . . . . . . . . 5
	5.3. Functional Extension Behavior . . . . . . . . . . . . . . 5		5.3. Functional Extension Behavior . . . . . . . . . . . . . . 5
	5.3.1. EAI Functional Extension Negotiated . . . . . . . . . 5		5.3.1. EAI Functional Extension Negotiated . . . . . . . . . 5
	5.3.2. EAI Functional Extension Not Negotiated . . . . . . . 6		5.3.2. EAI Functional Extension Not Negotiated . . . . . . . 6
	5.3.3. EAI Placeholder Email Address . . . . . . . . . . . . 7
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 7		6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 7		7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 7
	7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 8		7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 7
	8. Implementation Considerations . . . . . . . . . . . . . . . . 8		8. Implementation Considerations . . . . . . . . . . . . . . . . 8
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
	9.1. Normative References . . . . . . . . . . . . . . . . . . 8		9.1. Normative References . . . . . . . . . . . . . . . . . . 8
	9.2. Informative References . . . . . . . . . . . . . . . . . 9		9.2. Informative References . . . . . . . . . . . . . . . . . 9
	Appendix A. Change History . . . . . . . . . . . . . . . . . . . 10		Appendix A. Change History . . . . . . . . . . . . . . . . . . . 9
	A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 10		A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 9
	A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 10		A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 9
	A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10		A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10
	A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 10		A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11		A.5. Change from 04 to the regext 01 version . . . . . . . . . 10
			A.6. Change from the regext 01 to regext 02 version . . . . . 10
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	[RFC6530] introduced the framework for Internationalized Email		[RFC6530] introduced the framework for Internationalized Email
	Addresses. To make such addresses more widely accepted, the changes		Addresses. To make such addresses more widely accepted, the changes
	to various protocols need to be introduced.		to various protocols need to be introduced.
	This document describes an Extensible Provisioning Protocol (EPP)		This document describes an Extensible Provisioning Protocol (EPP)
	extension that permits usage of Internationalized Email Addresses in		extension that permits usage of Internationalized Email Addresses in
	the EPP protocol and specifies the terms when it can be used by EPP		the EPP protocol and specifies the terms when it can be used by EPP
	skipping to change at page 6, line 28 ¶		skipping to change at page 6, line 28 ¶
	The lack of EAI support can cause data and functional issues, so an		The lack of EAI support can cause data and functional issues, so an
	EAI supporting client or server needs to handle cases where the		EAI supporting client or server needs to handle cases where the
	opposite party doesn't support EAI. Below are the server and client		opposite party doesn't support EAI. Below are the server and client
	obligations when the EAI extension is not negotiated due to the lack		obligations when the EAI extension is not negotiated due to the lack
	of support by the peer.		of support by the peer.
	The EAI supporting server MUST satisfy the following obligations when		The EAI supporting server MUST satisfy the following obligations when
	the client does not support the EAI extension:		the client does not support the EAI extension:
	* When the email property is required in the EPP extension command,		* When the email property is required in the EPP response, the
	the server SHOULD validate the email property sent by the client		server SHOULD validate the email property sent by the client using
	using the ASCII email validation rules.		the ASCII email validation rules.
	* When the email property is optional according the EPP extension		* When the email property is optional according the EPP response, if
	command, if the client supplies the email property the server		the client supplies the email property the server SHOULD validate
	SHOULD validate the email property using the ASCII email		the email property using the ASCII email validation rules.
	validation rules.
	* When the email property is required in the EPP extension response,		* When the email property is required in the EPP response, the
	the server MUST validate whether the email property is an EAI		server MUST validate whether the email property is an EAI address
	address and if so return the predefined placeholder email (see		and if so return the error code 2308 "Data management policy
	below) and otherwise return the email property that has been set.		violation" and otherwise return the email property that has been
			set.
	* When the email property is optional in the EPP extension response,		* When the email property is optional in the EPP response, the
	the server MUST validate whether the email property is an EAI		server MUST validate whether the email property is an EAI address
	address and if so don't return the email property in the response		and if so don't return the email property in the response and
	and otherwise return the email property that has been set based on		otherwise return the email property that has been set based on
	server policy.		server policy.
	The EAI supporting client MUST satisfy the following obligations when		The EAI supporting client MUST satisfy the following obligations when
	the server does not support the EAI extension:		the server does not support the EAI extension:
	* When the email property is required in the EPP extension command		* When the email property is required in the EPP request and the
	and the email property is an EAI address with no alternative ASCII		email property is an EAI address, the client MUST provide the
	address, the client MUST provide the predefined placeholder email		ASCII email address. The provided email address should provide a
	address (see below).		way to contact the registrant. It can be a secondary ASCII email
			address or registrar-provided proxy email address.
	* When the email property is optional in the EPP extension command		* When the email property is optional in the EPP request and the
	and the email property is an EAI address with no alternative ASCII		email property is an EAI address with no alternative ASCII
	address, the client SHOULD omit the email property.		address, the client SHOULD omit the email property.
	5.3.3. EAI Placeholder Email Address
	A valid email value needs to be provided to a non-EAI supporting
	client or server to satisfy a required email property when all that
	is available is an EAI value. To satisfy this requirement, a
	predefined placeholder email needs to be selected that meets the
	requirements:
	* A syntactically valid email address to pass client or server
	validation logic.
	* A non-EAI email address since the client or server doesn't support
	EAI email addresses.
	* A single value that can indicate the lack of EAI support to the
	client or server.
	* An email address that is blackholed and never delivered.
	* Use of the email address will not cause operational issues.
	RFC 7535 [RFC7535] defines a blackholed domain name with
	EMPTY.AS112.ARPA, which can be leveraged for the EAI predefined
	placeholder email. The proposal is to define the predefined
	placeholder email value as EAI@EMPTY.AS112.ARPA.
	6. Security Considerations		6. Security Considerations
	Registries SHOULD validate the domain names in the provided email		Registries SHOULD validate the domain names in the provided email
	addresses. This can be done by validating all code points according		addresses. This can be done by validating all code points according
	to IDNA2008 [RFC5892].		to IDNA2008 [RFC5892].
	7. IANA Considerations		7. IANA Considerations
	7.1. XML Namespace		7.1. XML Namespace
	skipping to change at page 10, line 5 ¶		skipping to change at page 9, line 37 ¶
	2119 Key Words", BCP 14, RFC 8174, DOI 10.27487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.27487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	9.2. Informative References		9.2. Informative References
	[RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and		[RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and
	Internationalized Domain Names for Applications (IDNA)",		Internationalized Domain Names for Applications (IDNA)",
	RFC 5892, DOI 10.27487/RFC5892, August 2010,		RFC 5892, DOI 10.27487/RFC5892, August 2010,
	<https://www.rfc-editor.org/info/rfc5892>.		<https://www.rfc-editor.org/info/rfc5892>.
	[RFC7535] Abley, J., Dickson, B., Kumari, W., and G. Michaelson,
	"AS112 Redirection Using DNAME", RFC 7535,
	DOI 10.17487/RFC7535, May 2015,
	<https://www.rfc-editor.org/info/rfc7535>.
	[RFC8543] Zhou, L., Kong, N., Yao, J., Gould, J., and G. Zhou,		[RFC8543] Zhou, L., Kong, N., Yao, J., Gould, J., and G. Zhou,
	"Extensible Provisioning Protocol (EPP) Organization		"Extensible Provisioning Protocol (EPP) Organization
	Mapping", RFC 8543, DOI 10.27487/RFC8543, March 2019,		Mapping", RFC 8543, DOI 10.27487/RFC8543, March 2019,
	<https://www.rfc-editor.org/info/rfc8543>.		<https://www.rfc-editor.org/info/rfc8543>.
	Appendix A. Change History		Appendix A. Change History
	A.1. Change from 00 to 01		A.1. Change from 00 to 01
	1. Changed from update of RFC 5733 to use the "Placeholder Text and		1. Changed from update of RFC 5733 to use the "Placeholder Text and
	skipping to change at page 11, line 5 ¶		skipping to change at page 10, line 32 ¶
	Extension.		Extension.
	2. The examples are removed		2. The examples are removed
	A.4. Change from 03 to 04		A.4. Change from 03 to 04
	1. More detailed reference to email syntax is provided		1. More detailed reference to email syntax is provided
	2. The shortened eai namespace reference is removed		2. The shortened eai namespace reference is removed
			A.5. Change from 04 to the regext 01 version
			1. Provided the recommended placeholder value
			A.6. Change from the regext 01 to regext 02 version
			1. Removed the concept of the placeholder value
	Authors' Addresses		Authors' Addresses
	Dmitry Belyavskiy		Dmitry Belyavskiy
	8 marta st.		8 marta st.
	Moscow		Moscow
	127083		127083
	Russian Federation		Russian Federation
	Phone: +7 916 262 5593		Phone: +7 916 262 5593
	Email: beldmit@gmail.com		Email: beldmit@gmail.com
End of changes. 16 change blocks.
	62 lines changed or deleted		41 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/