Diff: rfc9873.original.xml

	rfc9873.original.xml	rfc9873.xml

	<?xml version='1.0' encoding='utf-8'?>	<?xml version='1.0' encoding='UTF-8'?>

	<!DOCTYPE rfc [	<!DOCTYPE rfc [

	<!-- One method to get references from the online citation libraries.	<!ENTITY nbsp " ">
	There has to be one entity for each item to be referenced.	<!ENTITY zwsp "">
	An alternate method (rfc include) is described in the references. -->	<!ENTITY nbhy "‑">
	<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC	<!ENTITY wj "⁠">
	.2119.xml">
	<!ENTITY RFC3688 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.3688.xml">
	<!ENTITY RFC5198 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5198.xml">
	<!ENTITY RFC5321 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5321.xml">
	<!ENTITY RFC5322 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5322.xml">
	<!ENTITY RFC5730 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5730.xml">
	<!ENTITY RFC5733 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5733.xml">
	<!ENTITY RFC5890 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5890.xml">
	<!ENTITY RFC6530 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.6530.xml">
	<!ENTITY RFC6531 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.6531.xml">
	<!ENTITY RFC6532 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.6532.xml">
	<!ENTITY RFC7451 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.7451.xml">
	<!ENTITY RFC7942 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.7942.xml">
	<!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.8174.xml">
	<!ENTITY W3C.xmlschema-1 SYSTEM "http://xml.resource.org/public/rfc/bibxml4/refe
	rence.W3C.REC-xmlschema-1-20041028.xml">
	<!ENTITY W3C.xmlschema-2 SYSTEM "http://xml.resource.org/public/rfc/bibxml4/refe
	rence.W3C.REC-xmlschema-2-20041028.xml">
	]>	]>

	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-regext-epp-e
	ai-27"	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-regext-epp-e
	category="std" ipr="trust200902" obsoletes="" updates=""	ai-27" number="9873" category="std" ipr="trust200902" obsoletes="" updates="" su
	submissionType="IETF" xml:lang="en" symRefs="true" sortRefs="false"	bmissionType="IETF" xml:lang="en" symRefs="true" sortRefs="false" tocInclude="tr
	tocInclude="true" version="3" consensus="true">	ue" version="3" consensus="true">
	<!-- xml2rfc v2v3 conversion 2.47.0 -->
	<front>	<front>
	<title abbrev="EPP Additional Email Address Extension">Additional Email Addr ess Extension for the Extensible Provisioning Protocol (EPP)</title>	<title abbrev="EPP Additional Email Address Extension">Additional Email Addr ess Extension for the Extensible Provisioning Protocol (EPP)</title>

		<seriesInfo name="RFC" value="9873"/>
	<author fullname="Dmitry Belyavskiy" initials="D." surname="Belyavskiy">	<author fullname="Dmitry Belyavskiy" initials="D." surname="Belyavskiy">
	<address>	<address>
	<postal>	<postal>
	<street>Karpatska 241/3</street>	<street>Karpatska 241/3</street>
	<city>Brno</city>	<city>Brno</city>
	<code>62500</code>	<code>62500</code>
	<country>Czech Republic</country>	<country>Czech Republic</country>
	</postal>	</postal>
	<phone>+420 603 261 036</phone>	<phone>+420 603 261 036</phone>
	<email>beldmit@gmail.com</email>	<email>beldmit@gmail.com</email>
	</address>	</address>
	</author>	</author>
	<author fullname="James Gould" surname="Gould">	<author fullname="James Gould" surname="Gould">
	<organization>VeriSign, Inc.</organization>	<organization>VeriSign, Inc.</organization>
	<address>	<address>
	<postal>	<postal>
	<street>12061 Bluemont Way</street>	<street>12061 Bluemont Way</street>
	<city>Reston</city>	<city>Reston</city>
	<region>VA</region>	<region>VA</region>
	<code>20190</code>	<code>20190</code>

	<country>US</country>	<country>United States of America</country>
	</postal>	</postal>
	<email>jgould@verisign.com</email>	<email>jgould@verisign.com</email>

	<uri>http://www.verisigninc.com</uri>	<uri>https://www.verisigninc.com</uri>
	</address>	</address>
	</author>	</author>
	<author initials="S." surname="Hollenbeck" fullname="Scott Hollenbeck">	<author initials="S." surname="Hollenbeck" fullname="Scott Hollenbeck">
	<organization>Verisign Labs</organization>	<organization>Verisign Labs</organization>
	<address>	<address>
	<postal>	<postal>
	<street>12061 Bluemont Way</street>	<street>12061 Bluemont Way</street>
	<city>Reston</city>	<city>Reston</city>
	<region>VA</region>	<region>VA</region>
	<code>20190</code>	<code>20190</code>

	<country>USA</country>	<country>United States of America</country>
	</postal>	</postal>
	<email>shollenbeck@verisign.com</email>	<email>shollenbeck@verisign.com</email>
	<uri>https://www.verisignlabs.com/</uri>	<uri>https://www.verisignlabs.com/</uri>
	</address>	</address>
	</author>	</author>

		<date month="September" year="2025"/>
		<area>ART</area>
		<workgroup>regext</workgroup>

		<!-- [rfced] Please insert any keywords (beyond those that appear in
		the title) for use on https://www.rfc-editor.org/search. -->

		<keyword>example</keyword>

	<abstract>	<abstract>
	<t>The Extensible Provisioning Protocol (EPP) does not natively support in ternationalized email addresses because the specifications for these addresses d id not exist when EPP was developed. This document describes a command-response extension that adds support for associating an additional email address with an EPP contact object. That additional email address can be either an international ized email address or an all-ASCII address.</t>	<t>The Extensible Provisioning Protocol (EPP) does not natively support in ternationalized email addresses because the specifications for these addresses d id not exist when EPP was developed. This document describes a command-response extension that adds support for associating an additional email address with an EPP contact object. That additional email address can be either an international ized email address or an all-ASCII address.</t>
	</abstract>	</abstract>
	</front>	</front>
	<middle>	<middle>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Introduction</name>	<name>Introduction</name>

	<t>The framework for internationalized email addresses is described in <xr ef target="RFC6530" format="default"/>. This document describes an Extens ible Provisioning Protocol (EPP) <xref target="RFC5730" format="default"/> comma nd-response extension that adds support for adding a second email address to the EPP contact object <xref target="RFC5733" format="default"/> mapping. The synta x for the email address associated with the base contact object is described in Section 2.6 of <xref target="RFC5733" format="default"/>. The second email addre ss can be either an ASCII-only email address or an internationalized, SMTPUTF8 < xref target="RFC6530" format="default"/> email address. This second address can be used to identify an alternate ASCII-only email address for use in case of pri mary address delivery issues. It can also be used to identify an SMTPUTF8 addres s for contact purposes, in which case the ASCII-only address can be used in case of SMTPUTF8 address delivery issues.</t>	<t>The framework for internationalized email addresses is described in <xr ef target="RFC6530" format="default"/>. This document describes an Extens ible Provisioning Protocol (EPP) <xref target="RFC5730" format="default"/> comma nd-response extension that adds support for adding a second email address to the EPP contact object mapping <xref target="RFC5733" format="default"/>. The synta x for the email address associated with the base contact object is described in <xref target="RFC5733" section="2.6"/>. The second email address can be either a n ASCII-only email address or an internationalized SMTPUTF8 email address <xref target="RFC6530" format="default"/>. This second address can be used to identify an alternate ASCII-only email address for use in case of primary address delive ry issues. It can also be used to identify an SMTPUTF8 address for contact purpo ses, in which case the ASCII-only address can be used in case of SMTPUTF8 addres s delivery issues.</t>


	<t>While this extension adds support for an additional email address to contact objects, and that additional email address can be an SMTPUTF8 address, it does not in any way update or change any other EPP extension that includes an email address. Adding support for SMTPUTF8 addresses to those extensions will r equire an update to the relevant extension specifications. In cases where a cont act object contains two email addresses, all users of these addresses should be aware that either address may be forwarded to the other. This implies that a mes sage sent to an all-ASCII address may receive a reply from an SMTPUTF8 address, or vice versa.</t>	<t>While this extension adds support for an additional email address to contact objects, and that additional email address can be an SMTPUTF8 address, it does not in any way update or change any other EPP extension that includes an email address. Adding support for SMTPUTF8 addresses to those extensions will r equire an update to the relevant extension specifications. In cases where a cont act object contains two email addresses, all users of these addresses should be aware that either address may be forwarded to the other. This implies that a mes sage sent to an all-ASCII address may receive a reply from an SMTPUTF8 address o r vice versa.</t>

	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Conventions Used in This Document</name>	<name>Conventions Used in This Document</name>

	<t> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",	<t>
	"SHOULD", "SHOULD NOT",	The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
	"RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are t	IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
	o be interpreted	NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
	as described in BCP 14 <xref target="RFC2119" format="default"/> <xref target=	RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
	"RFC8174" format="default"/> when, and only when,	"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
	they appear in all capitals, as shown here.</t>	be interpreted as
		described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/>
		when, and only when, they appear in all capitals, as shown here.
		</t>

	<t>XML is case sensitive. Unless stated otherwise, XML specifications	<t>XML is case sensitive. Unless stated otherwise, XML specifications
	and examples provided in this document <bcp14>MUST</bcp14> be interpreted in t he	and examples provided in this document <bcp14>MUST</bcp14> be interpreted in t he
	character case presented in order to develop a conforming	character case presented in order to develop a conforming
	implementation.</t>	implementation.</t>


	<t>In examples, "C:" represents lines sent by a protocol client and "S:" repre sents lines returned by a protocol server.	<t>In examples, "C:" represents lines sent by a protocol client, and "S:" repr esents lines returned by a protocol server.
	Indentation and white space in the examples are provided only to	Indentation and white space in the examples are provided only to

	illustrate element relationships and are not REQUIRED in the protocol.</t>	illustrate element relationships and are not <bcp14>REQUIRED</bcp14> in the pr
		otocol.</t>

		<!-- [rfced] Should "employ" be updated to "MUST employ" (parallel structure
		with "MUST NOT depend")? Or is the current correct?

		Original:
		The XML namespace prefix "addlEmail" is used for the namespace
		"urn:ietf:params:xml:ns:epp:addlEmail-1.0", 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.

		Perhaps:
		The XML namespace prefix "addlEmail" is used for the namespace
		"urn:ietf:params:xml:ns:epp:addlEmail-1.0", but implementations MUST
		NOT depend on it and instead MUST employ a proper namespace-aware
		XML parser and serializer to interpret and output the XML documents.
		-->

	<t>The XML namespace prefix "addlEmail" is used for the namespace	<t>The XML namespace prefix "addlEmail" is used for the namespace
	"urn:ietf:params:xml:ns:epp:addlEmail-1.0", but implementations <bcp14>MUST NOT< /bcp14> depend on	"urn:ietf:params:xml:ns:epp:addlEmail-1.0", but implementations <bcp14>MUST NOT< /bcp14> depend on
	it and instead employ	it and instead employ
	a proper namespace-aware XML parser and serializer to interpret and	a proper namespace-aware XML parser and serializer to interpret and
	output the XML documents.</t>	output the XML documents.</t>

	</section>	</section>
	</section>	</section>
	<section anchor="emailAddressSpec" numbered="true" toc="default">	<section anchor="emailAddressSpec" numbered="true" toc="default">
	<name>Email Address Specification</name>	<name>Email Address Specification</name>

	<t>The EPP contact object mapping <xref target="RFC5733" format="defaul
	t"/> normatively references <xref target="RFC5322" format="default"/> as the spe	<!-- [rfced] This sentence is a bit hard to follow because of the many
	cification for email address syntax. That specification does not include support	commas. We added parentheses rather than commas around the "defined in"
	for internationalized email addresses. <xref target="RFC6530" format="default">	phrases and added "to support" before "U-label" in this sentence. Please
	RFC 6530</xref> provides an overview and describes the framework for internation	let us know any concerns.
	alized email. SMTPUTF8 email address syntax is described in Section 3.3 of <xref
	target="RFC6531" format="default"/>. <xref target="RFC6531" format="default"/>	Original:
	extends the Mailbox, Local-part and Domain ABNF rules in <xref target="RFC5321"	[RFC6531] extends the
	format="default"/> to support "UTF8-non-ascii", defined in Section 3.1 of <xref	Mailbox, Local-part and Domain ABNF rules in [RFC5321] to support
	target="RFC6532" format="default"/>, for the local-part and U-label, defined in	"UTF8-non-ascii", defined in Section 3.1 of [RFC6532], for the local-
	Section 2.3.2.1 of <xref target="RFC5890" format="default"/>, for the domain. Th	part and U-label, defined in Section 2.3.2.1 of [RFC5890], for the
	e validation rules described in RFC 6531 <bcp14>MUST</bcp14> be followed when pr	domain.
	ocessing internationalized email addresses associated with this extension.</t>
		Current:
		[RFC6531] extends the
		Mailbox, Local-part, and Domain ABNF rules in [RFC5321] to support
		"UTF8-non-ascii" (defined in Section 3.1 of [RFC6532]) for the local-
		part and to support U-label (defined in Section 2.3.2.1 of [RFC5890]) for the
		domain.
		-->

		<t>The EPP contact object mapping <xref target="RFC5733" format="default"/> norm
		atively references <xref target="RFC5322" format="default"/> as the specificatio
		n for email address syntax. That specification does not include support for inte
		rnationalized email addresses. <xref target="RFC6530" format="default"/> provide
		s an overview and describes the framework for internationalized email. SMTPUTF8
		email address syntax is described in <xref target="RFC6531" section="3.3"/>. <xr
		ef target="RFC6531" format="default"/> extends the Mailbox, Local-part, and Doma
		in ABNF rules in <xref target="RFC5321" format="default"/> to support "UTF8-non-
		ascii" (defined in <xref target="RFC6532" section="3.1"/>) for the local-part an
		d to support U-label (defined in <xref target="RFC5890" section="2.3.2.1"/>) for
		the domain. The validation rules described in <xref target="RFC6531" format="de
		fault"/> <bcp14>MUST</bcp14> be followed when processing internationalized email
		addresses associated with this extension.</t>
	</section>	</section>
	<section anchor="addlEmailElement" numbered="true" toc="default">	<section anchor="addlEmailElement" numbered="true" toc="default">
	<name>Additional Email Address Element</name>	<name>Additional Email Address Element</name>
	<t>A second email address can be set using the <addlEmail:addlEmail> element	<t>A second email address can be set using the <addlEmail:addlEmail> element
	with the command and response extensions defined in <xref target="commands "/>. The <addlEmail:addlEmail> element contains the following child eleme nt:</t>	with the command and response extensions defined in <xref target="commands "/>. The <addlEmail:addlEmail> element contains the following child eleme nt:</t>
	<dl newline="false" indent="4">	<dl newline="false" indent="4">
	<dt><addlEmail:email>:</dt>	<dt><addlEmail:email>:</dt>
	<dd>An element following the syntax in <xref target="emailAddressSpec" /> for defining a second ASCII or SMTPUTF8 address. An empty <addlEmail:emai l/> element unsets	<dd>An element following the syntax in <xref target="emailAddressSpec" /> for defining a second ASCII or SMTPUTF8 address. An empty <addlEmail:emai l/> element unsets

	the second email address in the <xref target="updateCommand">Update Co mmand</xref> and indicates the second email is not set in the <xref target="info Command">Info Response</xref>.	the second email address in the Update Command (<xref target="updateCo mmand"></xref>) and indicates the second email is not set in the Info Response ( <xref target="infoCommand"></xref>).
	The <addlEmail:email> element contains an <bcp14>OPTIONAL </bcp14> "primary" attribute that can be used to indicate that the extension ema il address should be treated as the	The <addlEmail:email> element contains an <bcp14>OPTIONAL </bcp14> "primary" attribute that can be used to indicate that the extension ema il address should be treated as the
	primary email address for the extended contact object. The "pri mary" attribute <bcp14>MUST NOT</bcp14> be present if the <addlEmail:email&gt ; is empty.</dd>	primary email address for the extended contact object. The "pri mary" attribute <bcp14>MUST NOT</bcp14> be present if the <addlEmail:email&gt ; is empty.</dd>
	</dl>	</dl>
	<t>Additional email address considerations:</t>	<t>Additional email address considerations:</t>
	<ul>	<ul>

	<li>The value set for the <contact:disclose><contact:email/&g	<li>The value set for the <contact:disclose><contact:email/&g
	t; "flag" attribute (described in Section 2.9 of RFC 5733 <xref target="RFC5733"	t; "flag" attribute (described in <xref target="RFC5733" section="2.9"/>) <bcp14
	format="default"/>) MUST also be applied to all additional email addresses that	>MUST</bcp14> also be applied to all additional email addresses that are added b
	are added by a contact extension.</li>	y a contact extension.</li>
	<li>Any address included in an extension is intended to be an a
	dditional address that's associated only with the primary <contact:email>	<!-- [rfced] Should "that support" here be updated to just "support"? Is is
	address, and that support for any other additional email addresses MUST explicit	another meaning intended?
	ly describe how the additional addresses are associated with the existing addres
	ses.</li>	Original:
		* Any address included in an extension is intended to be an
		additional address that's associated only with the primary
		<contact:email> address, and that support for any other additional
		email addresses MUST explicitly describe how the additional
		addresses are associated with the existing addresses.

		Perhaps:
		* Any address included in an extension is intended to be an
		additional address that is associated only with the primary
		<contact:email> address, and support for any other additional
		email addresses MUST explicitly describe how the additional
		addresses are associated with the existing addresses.
		-->

		<li>Any address included in an extension is intended to be an additiona
		l address that is associated only with the primary <contact:email> address
		, and that support for any other additional email addresses <bcp14>MUST</bcp14>
		explicitly describe how the additional addresses are associated with the existin
		g addresses.</li>
	</ul>	</ul>
	</section>	</section>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Extension Considerations</name>	<name>Extension Considerations</name>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Signaling Client and Server Support</name>	<name>Signaling Client and Server Support</name>
	<t>	<t>

	As described in Section 2.4 of <xref target="RFC5730" format="default	As described in <xref target="RFC5730" section="2.4"/>, the client an
	"/>, the client and the server can signal support for the extension using a	d the server can signal support for the extension using a
	namespace URI in the login and greeting extension services respective	namespace URI in the login and greeting extension services, respectiv
	ly. The	ely. The
	namespace URI "urn:ietf:params:xml:ns:epp:addlEmail-1.0" is used to s ignal support for the extension.	namespace URI "urn:ietf:params:xml:ns:epp:addlEmail-1.0" is used to s ignal support for the extension.
	The client includes the namespace URI in an <svcExtension> <extURI> element of	The client includes the namespace URI in an <svcExtension> <extURI> element of

	the <xref target="RFC5730" format="default"/> <login> Command.	the <login> command <xref target="RFC5730" format="default"/>.
	The server includes the namespace URI	The server includes the namespace URI
	in an <svcExtension> <extURI> element of the <xref target	in an <svcExtension> <extURI> element of the greeting <xr
	="RFC5730" format="default"/> greeting.	ef target="RFC5730" format="default"/>.
	</t>	</t>
	</section>	</section>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Extension Behavior</name>	<name>Extension Behavior</name>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Extension Negotiated</name>	<name>Extension Negotiated</name>
	<t>	<t>
	If both client and server have indicated support for SMTPUTF8 addresses during session establishment,	If both client and server have indicated support for SMTPUTF8 addresses during session establishment,
	they <bcp14>MUST</bcp14> be able to process an SMTPUTF8 addre ss in any extended contact object during the established EPP session. Server and client obligations when this extension has been successfully negotiated in the EPP session are described below.	they <bcp14>MUST</bcp14> be able to process an SMTPUTF8 addre ss in any extended contact object during the established EPP session. Server and client obligations when this extension has been successfully negotiated in the EPP session are described below.
	</t>	</t>
	<t>The server <bcp14>MUST</bcp14> satisfy the following obligations w hen support for this extension has been negotiated:</t>	<t>The server <bcp14>MUST</bcp14> satisfy the following obligations w hen support for this extension has been negotiated:</t>
	<ul>	<ul>

	<li>Accept SMTPUTF8 compliant addresses for the extended contact obje	<li>Accept SMTPUTF8-compliant addresses for the extended contact obje
	ct in the EPP session.</li>	ct in the EPP session.</li>
	<li>Support email address validation based on SMTPUTF8 validation	<li>Support email address validation based on the SMTPUTF8 validation
	rules defined in <xref target="emailAddressSpec" format="default"/></li>	rules defined in <xref target="emailAddressSpec" format="default"/>.</li>
	<li>Storage of email properties that support internationalized ch
	aracters.</li>	<!-- [rfced] In the first bulleted list in Section 4.2.1, the list items all
	<li>Return SMTPUTF8 compliant addresses for the extended contact	begin with a verb except for the following one. How may we update this
	object in EPP responses.</li>	one to create parallel structure?
	<li>Support the SMTP extension for internationalized emai
	l described in <xref target="RFC6531" format="default"/> when sending or receivi	Original:
	ng email.</li>	* Storage of email properties that support internationalized
		characters.

		Perhaps:
		* Store email properties that support internationalized
		characters.

		Or:
		* Maintain storage of email properties that support internationalized
		characters.
		-->

		<li>Storage of email properties that support internationalized charac
		ters.</li>
		<li>Return SMTPUTF8-compliant addresses for the extended contact obje
		ct in EPP responses.</li>
		<li>Support the SMTP extension for internationalized email described
		in <xref target="RFC6531" format="default"/> when sending or receiving email.</l
		i>
	</ul>	</ul>

	<t>The client <bcp14>MUST</bcp14> satisfy the following obligations wh en support for this extension has been negotiated:</t>	<t>The client <bcp14>MUST</bcp14> satisfy the following obligations wh en support for this extension has been negotiated:</t>
	<ul>	<ul>

	<li>Provide SMTPUTF8 compliant addresses for the extended contact obj	<li>Provide SMTPUTF8-compliant addresses for the extended contact obj
	ect in the EPP session.</li>	ect in the EPP session.</li>
	<li>Accept SMTPUTF8 compliant addresses for the extended contact obje	<li>Accept SMTPUTF8-compliant addresses for the extended contact obje
	ct in EPP responses.</li>	ct in EPP responses.</li>
	<li>Support the SMTP extension for internationalized emai	<li>Support the SMTP extension for internationalized email described
	l described in <xref target="RFC6531" format="default"/> when sending or receivi	in <xref target="RFC6531" format="default"/> when sending or receiving email.</l
	ng email.</li>	i>
	</ul>	</ul>
	</section>	</section>

	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Extension Not Negotiated</name>	<name>Extension Not Negotiated</name>
	<t>An extended contact object <bcp14>MUST NOT</bcp14> be provided or r eturned by either an EPP client or an EPP server when support for this extension is not successfully negotiated at the start of an EPP session.</t>	<t>An extended contact object <bcp14>MUST NOT</bcp14> be provided or r eturned by either an EPP client or an EPP server when support for this extension is not successfully negotiated at the start of an EPP session.</t>
	</section>	</section>
	</section>	</section>
	</section>	</section>


	<section anchor="commands" title="EPP Command Mapping">	<section anchor="commands">
		<name>EPP Command Mapping</name>
	<t>A detailed description of the EPP syntax and semantics can be found	<t>A detailed description of the EPP syntax and semantics can be found
	in the EPP core protocol specification <xref target="RFC5730"/>.	in the EPP core protocol specification <xref target="RFC5730"/>.
	This section defines the provisioning of an alternate email address.</t>	This section defines the provisioning of an alternate email address.</t>


	<section anchor="queryCommands" title="EPP Query Commands">	<section anchor="queryCommands">
		<name>EPP Query Commands</name>

	<t>EPP provides three commands to retrieve object information: <check > to determine	<t>EPP provides three commands to retrieve object information: <check > to determine
	if an object can be provisioned, <info> to retrieve information a ssociated	if an object can be provisioned, <info> to retrieve information a ssociated
	with an object, and <transfer> to retrieve object-transfer status information.</t>	with an object, and <transfer> to retrieve object-transfer status information.</t>


	<section anchor="checkCommand" title="EPP <check> Command">	<section anchor="checkCommand">
		<name>EPP <check> Command</name>

	<t>This extension does not add any elements to the EPP <check> com mand	<t>This extension does not add any elements to the EPP <check> com mand
	or <check> response described in <xref target="RFC5730"/>.</t>	or <check> response described in <xref target="RFC5730"/>.</t>

	</section>	</section>


	<!-- end CHECK command -->	<section anchor="infoCommand">
		<name>EPP <info> Command</name>
	<section anchor="infoCommand" title="EPP <info> Command">

	<t>This extension does not add any elements to the EPP <info> comm and	<t>This extension does not add any elements to the EPP <info> comm and
	response described in <xref target="RFC5730"/>.</t>	response described in <xref target="RFC5730"/>.</t>

	<t>	<t>

	If the query was successful, the server replies with an <xref target=" addlEmailElement"><addlEmail:addlEmail> element</xref>	If the query is successful, the server replies with an <addlEmail:a ddlEmail> element (<xref target="addlEmailElement"></xref>)
	along with the regular EPP <resData>.	along with the regular EPP <resData>.
	</t>	</t>


		<!-- [rfced] This document includes 8 figures. For each of them, the text
		introducing the figure and the figure title are almost identical. We
		suggest removing the intro text and keeping the figure title to avoid
		redundancy. Let us know your thoughts.

		Example:

		The following is an example <info> contact response using the
		<addlEmail:addlEmail> extension with no alternate email address:
		...
		Figure 1: Example <info> Contact Response Using the
		<addlEmail:addlEmail> Extension with No Alternate Email Address
		-->

	<t>The following is an example <info> contact response using the	<t>The following is an example <info> contact response using the
	<addlEmail:addlEmail> extension with no alternate email address: </t>	<addlEmail:addlEmail> extension with no alternate email address: </t>
	<figure>	<figure>

	<name>Example <info> contact response using the	<name>Example <info> Contact Response Using the
	<addlEmail:addlEmail> extension with no alternate email addres	<addlEmail:addlEmail> Extension with No Alternate Email Addres
	s</name>	s</name>
	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	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: <contact:infData	S: <contact:infData
	S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">

	skipping to change at line 267 ¶	skipping to change at line 354 ¶
	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>]]></sourcecode>	S:</epp>]]></sourcecode>
	</figure>	</figure>

	<t>The following is an example <info> contact response using the	<t>The following is an example <info> contact response using the
	<addlEmail:addlEmail> extension with an ASCII alternate email ad dress:</t>	<addlEmail:addlEmail> extension with an ASCII alternate email ad dress:</t>
	<figure>	<figure>

	<name>Example <info> contact response using the	<name>Example <info> Contact Response Using the
	<addlEmail:addlEmail> extension with an ASCII alternate email	<addlEmail:addlEmail> Extension with an ASCII Alternate Email
	address</name>	Address</name>
	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	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: <contact:infData	S: <contact:infData
	S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">

	skipping to change at line 330 ¶	skipping to change at line 417 ¶
	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>]]></sourcecode>	S:</epp>]]></sourcecode>
	</figure>	</figure>

	<t>The following is an example <info> contact response using the	<t>The following is an example <info> contact response using the
	<addlEmail:addlEmail> extension with an SMTPUTF8 primary email a ddress:</t>	<addlEmail:addlEmail> extension with an SMTPUTF8 primary email a ddress:</t>
	<figure>	<figure>

	<name>Example <info> contact response using the	<name>Example <info> Contact Response Using the
	<addlEmail:addlEmail> extension with an SMTPUTF8 primary email	<addlEmail:addlEmail> Extension with an SMTPUTF8 Primary Email
	address</name>	Address</name>
	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	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: <contact:infData	S: <contact:infData
	S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">

	skipping to change at line 392 ¶	skipping to change at line 479 ¶
	S: </extension>	S: </extension>
	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>]]></sourcecode>	S:</epp>]]></sourcecode>
	</figure>	</figure>

	</section>	</section>

	<!-- end INFO command -->


	<section anchor="transferQueryCommand" title="EPP <transfer> Query C	<!-- [rfced] Should the title of Section 5.1.3 be updated from "Query Command"
	ommand">	to just "Command" for consistency with the other titles in this section?

		Original:
		5.1. EPP Query Commands
		5.1.1. EPP <check> Command
		5.1.2. EPP <info> Command
		5.1.3. EPP <transfer> Query Command

		Perhaps:
		5.1. EPP Query Commands
		5.1.1. EPP <check> Command
		5.1.2. EPP <info> Command
		5.1.3. EPP <transfer> Command
		-->

		<section anchor="transferQueryCommand">
		<name>EPP <transfer> Query Command</name>

	<t>This extension does not add any elements to the EPP <transfer> q uery command	<t>This extension does not add any elements to the EPP <transfer> q uery command
	or <transfer> query response described in <xref target="RFC5730"/>. </t>	or <transfer> query response described in <xref target="RFC5730"/>. </t>

	</section>	</section>

	<!-- end TRANSFER QUERY command -->

	</section>	</section>


	<section anchor="transformCommands" title="EPP Transform Commands">	<section anchor="transformCommands">
		<name>EPP Transform Commands</name>

	<t>EPP provides five commands to transform objects: <create> to cr eate an instance of an object,	<t>EPP provides five commands to transform objects: <create> to cr eate an instance of an object,
	<delete> to delete an instance of an object, <renew> to exte nd the validity period of an object,	<delete> to delete an instance of an object, <renew> to exte nd the validity period of an object,
	<transfer> to manage object sponsorship changes, and <update&gt ; to change information associated	<transfer> to manage object sponsorship changes, and <update&gt ; to change information associated
	with an object.</t>	with an object.</t>


	<section anchor="createCommand" title="EPP <create> Command">	<section anchor="createCommand">
		<name>EPP <create> Command</name>

		<!-- [rfced] How may we update "an object mapping like [RFC5733]" for clarity
		in these sentences? Is the intended meaning "an object mapping like the
		one described in [RFC5733]" or something else?

		Original:
		This extension defines additional elements to extend the EPP <create>
		command of an object mapping like [RFC5733].
		...
		In addition to the EPP
		command elements described in an object mapping like [RFC5733], the
		command MUST contain a child <addlEmail:addlEmail> element
		(Section 3) for the client to set an alternate email address.
		...
		This extension defines additional elements to extend the EPP <update>
		command of an object mapping like [RFC5733].
		...
		In addition to the EPP
		command elements described in an object mapping like [RFC5733], the
		command MUST contain a child <addlEmail:addlEmail> element
		(Section 3) for the client to set or unset an alternate email
		address.

		Perhaps:
		This extension defines additional elements to extend the EPP <create>
		command of an object mapping like the one described in [RFC5733].
		...
		In addition to the EPP
		command elements described in an object mapping
		(like the one in [RFC5733]), the
		command MUST contain a child <addlEmail:addlEmail> element
		(Section 3) for the client to set an alternate email address.
		...
		This extension defines additional elements to extend the EPP <update>
		command of an object mapping like the one described in [RFC5733].
		...
		In addition to the EPP
		command elements described in an object mapping
		(like the one in [RFC5733]), the
		command MUST contain a child <addlEmail:addlEmail> element
		(Section 3) for the client to set or unset an alternate email
		address.
		-->

	<t>This extension defines additional elements to extend the EPP	<t>This extension defines additional elements to extend the EPP
	<create> command of an object mapping like <xref target="RFC5733"/ >.</t>	<create> command of an object mapping like <xref target="RFC5733"/ >.</t>

	<t>The EPP <create> command provides a transform operation that all ows a client to create an instance of an object.	<t>The EPP <create> command provides a transform operation that all ows a client to create an instance of an object.
	In addition to the EPP command elements described in an object mapping li ke <xref target="RFC5733"/>, the command <bcp14>MUST</bcp14> contain a	In addition to the EPP command elements described in an object mapping li ke <xref target="RFC5733"/>, the command <bcp14>MUST</bcp14> contain a

	child <xref target="addlEmailElement"><addlEmail:addlEmail> element </xref> for the client to set an alternate email address.</t>	child <addlEmail:addlEmail> element (<xref target="addlEmailElement "></xref>) for the client to set an alternate email address.</t>

	<t>The following is an example <create> command to create a contact object with an alternate ASCII email address:</t>	<t>The following is an example <create> command to create a contact object with an alternate ASCII email address:</t>
	<figure>	<figure>

	<name>Example <create> command to create a contact object with an alternate ASCII email address</name>	<name>Example <create> Command to Create a Contact Object with an Alternate ASCII Email Address</name>

	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <create>	C: <create>
	C: <contact:create	C: <contact:create
	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
	C: <contact:id>sh8013</contact:id>	C: <contact:id>sh8013</contact:id>
	C: <contact:postalInfo type="int">	C: <contact:postalInfo type="int">

	skipping to change at line 469 ¶	skipping to change at line 616 ¶
	C: <addlEmail:email>jdoe-alt@example.net</addlEmail:email>	C: <addlEmail:email>jdoe-alt@example.net</addlEmail:email>
	C: </addlEmail:addlEmail>	C: </addlEmail:addlEmail>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>]]></sourcecode>	C:</epp>]]></sourcecode>
	</figure>	</figure>

	<t>The following is an example <create> command to create a contact object with a primary SMTPUTF8 email address:</t>	<t>The following is an example <create> command to create a contact object with a primary SMTPUTF8 email address:</t>
	<figure>	<figure>

	<name>Example <create> command to create a contact object with a primary SMTPUTF8 email address</name>	<name>Example <create> Command to Create a Contact Object with a Primary SMTPUTF8 Email Address</name>

	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <create>	C: <create>
	C: <contact:create	C: <contact:create
	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
	C: <contact:id>sh8013</contact:id>	C: <contact:id>sh8013</contact:id>
	C: <contact:postalInfo type="int">	C: <contact:postalInfo type="int">

	skipping to change at line 517 ¶	skipping to change at line 664 ¶
	primary="true">麥克風@example.com</addlEmail:email>	primary="true">麥克風@example.com</addlEmail:email>
	C: </addlEmail:addlEmail>	C: </addlEmail:addlEmail>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>]]></sourcecode>	C:</epp>]]></sourcecode>
	</figure>	</figure>

	<t>This extension does not add any elements to the EPP <create> res ponse described	<t>This extension does not add any elements to the EPP <create> res ponse described
	in <xref target="RFC5730"/>.</t>	in <xref target="RFC5730"/>.</t>


	</section>	</section>

	<!-- end CREATE command -->

	<section anchor="deleteCommand" title="EPP <delete> Command">


		<section anchor="deleteCommand">
		<name>EPP <delete> Command</name>
	<t>This extension does not add any elements to the EPP <delete> com mand	<t>This extension does not add any elements to the EPP <delete> com mand
	or <delete> response described in <xref target="RFC5730"/>.</t>	or <delete> response described in <xref target="RFC5730"/>.</t>


	</section>	</section>

	<!-- end DELETE command -->

	<section anchor="renewCommand" title="EPP <renew> Command">


		<section anchor="renewCommand">
		<name>EPP <renew> Command</name>
	<t>This extension does not add any elements to the EPP <renew> comm and	<t>This extension does not add any elements to the EPP <renew> comm and
	or <renew> response described in <xref target="RFC5730"/>.</t>	or <renew> response described in <xref target="RFC5730"/>.</t>


	</section>	</section>

	<!-- end RENEW command -->

	<section anchor="transferCommand" title="EPP <transfer> Command">


		<section anchor="transferCommand">
		<name>EPP <transfer> Command</name>
	<t>This extension does not add any elements to the EPP <transfer> command	<t>This extension does not add any elements to the EPP <transfer> command
	or <transfer> response described in <xref target="RFC5730"/>.</t>	or <transfer> response described in <xref target="RFC5730"/>.</t>


	</section>	</section>

	<!-- end TRANSFER command -->

	<section anchor="updateCommand" title="EPP <update> Command">


		<section anchor="updateCommand">
		<name>EPP <update> Command</name>
	<t>This extension defines additional elements to extend the EPP	<t>This extension defines additional elements to extend the EPP
	<update> command of an object mapping like <xref target="RFC5733" />.</t>	<update> command of an object mapping like <xref target="RFC5733" />.</t>

	<t>The EPP <update> command provides a transform operation that al lows a client to update an instance of an object.	<t>The EPP <update> command provides a transform operation that al lows a client to update an instance of an object.
	In addition to the EPP command elements described in an object mapping l ike <xref target="RFC5733"/>, the command <bcp14>MUST</bcp14> contain a	In addition to the EPP command elements described in an object mapping l ike <xref target="RFC5733"/>, the command <bcp14>MUST</bcp14> contain a

	child <xref target="addlEmailElement"><addlEmail:addlEmail> elemen t</xref> for the client to set or unset an alternate email address.	child <addlEmail:addlEmail> element (<xref target="addlEmailElemen t"></xref>) for the client to set or unset an alternate email address.
	If the alternate email address cannot be applied to the object, the serv er <bcp14>MUST</bcp14> return an EPP error result code of 2201.</t>	If the alternate email address cannot be applied to the object, the serv er <bcp14>MUST</bcp14> return an EPP error result code of 2201.</t>

	<t>The following is an example <update> command to set a contact o bject with an alternate ASCII email address:</t>	<t>The following is an example <update> command to set a contact o bject with an alternate ASCII email address:</t>
	<figure>	<figure>

	<name>Example <update> command to set a contact object with a n alternate ASCII email address</name>	<name>Example <update> Command to Set a Contact Object with a n Alternate ASCII Email Address</name>

	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <update>	C: <update>
	C: <contact:update	C: <contact:update
	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
	C: <contact:id>sh8013</contact:id>	C: <contact:id>sh8013</contact:id>
	C: </contact:update>	C: </contact:update>

	skipping to change at line 582 ¶	skipping to change at line 721 ¶
	C: <addlEmail:email>jdoe-alt@example.net</addlEmail:email>	C: <addlEmail:email>jdoe-alt@example.net</addlEmail:email>
	C: </addlEmail:addlEmail>	C: </addlEmail:addlEmail>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>]]></sourcecode>	C:</epp>]]></sourcecode>
	</figure>	</figure>

	<t>The following is an example <update> command to set a contact o bject with an alternate SMTPUTF8 email address:</t>	<t>The following is an example <update> command to set a contact o bject with an alternate SMTPUTF8 email address:</t>
	<figure>	<figure>

	<name>Example <update> command to set a contact object with a n alternate SMTPUTF8 email address</name>	<name>Example <update> Command to Set a Contact Object with a n Alternate SMTPUTF8 Email Address</name>

	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <update>	C: <update>
	C: <contact:update	C: <contact:update
	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
	C: <contact:id>sh8013</contact:id>	C: <contact:id>sh8013</contact:id>
	C: </contact:update>	C: </contact:update>

	skipping to change at line 607 ¶	skipping to change at line 746 ¶
	C: <addlEmail:email>麥克風@example.com</addlEmail:email>	C: <addlEmail:email>麥克風@example.com</addlEmail:email>
	C: </addlEmail:addlEmail>	C: </addlEmail:addlEmail>
	C: </extension>	C: </extension>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>]]></sourcecode>	C:</epp>]]></sourcecode>
	</figure>	</figure>

	<t>The following is an example <update> command to unset a contact object alternate email address:</t>	<t>The following is an example <update> command to unset a contact object alternate email address:</t>
	<figure>	<figure>

	<name>Example <update> command to unset a contact object alte rnate email address</name>	<name>Example <update> Command to Unset a Contact Object Alte rnate Email Address</name>

	<sourcecode type="xml" markers="false"><![CDATA[	<sourcecode type="xml" markers="false"><![CDATA[
	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>
	C: <update>	C: <update>
	C: <contact:update	C: <contact:update
	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">	C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
	C: <contact:id>sh8013</contact:id>	C: <contact:id>sh8013</contact:id>
	C: </contact:update>	C: </contact:update>

	skipping to change at line 643 ¶	skipping to change at line 782 ¶
	</section>	</section>
	<!-- end UPDATE command -->	<!-- end UPDATE command -->

	</section>	</section>

	</section>	</section>

	<section anchor="syntax" numbered="true" toc="default">	<section anchor="syntax" numbered="true" toc="default">
	<name>Formal Syntax</name>	<name>Formal Syntax</name>
	<t>The EPP Additional Email Address Extension schema is presented here.</t >	<t>The EPP Additional Email Address Extension schema is presented here.</t >

	<t>The formal syntax shown here is a complete XML Schema (<xref target="W3 C.REC-xmlschema-1-20041028"/>, <xref target="W3C.REC-xmlschema-2-20041028"/>) re presentation of the object	<t>The formal syntax shown here is a complete XML Schema <xref target="W3C .REC-xmlschema-1-20041028"/> <xref target="W3C.REC-xmlschema-2-20041028"/> repre sentation of the object
	mapping suitable for automated validation of EPP XML instances. The &lt ;CODE BEGINS>	mapping suitable for automated validation of EPP XML instances. The &lt ;CODE BEGINS>
	and <CODE ENDS> tags are not part of the XML Schema; they are use d to note the	and <CODE ENDS> tags are not part of the XML Schema; they are use d to note the
	beginning and ending of the XML Schema for URI registration purposes.</ t>	beginning and ending of the XML Schema for URI registration purposes.</ t>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>EPP Additional Email Address Extension Schema</name>	<name>EPP Additional Email Address Extension Schema</name>
	<sourcecode type="xml" markers="true"><![CDATA[	<sourcecode type="xml" markers="true"><![CDATA[
	<?xml version="1.0" encoding="UTF-8"?>	<?xml version="1.0" encoding="UTF-8"?>
	<schema xmlns="http://www.w3.org/2001/XMLSchema"	<schema xmlns="http://www.w3.org/2001/XMLSchema"
	xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"	xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"
	targetNamespace="urn:ietf:params:xml:ns:epp:addlEmail-1.0"	targetNamespace="urn:ietf:params:xml:ns:epp:addlEmail-1.0"

	skipping to change at line 687 ¶	skipping to change at line 826 ¶
	End of schema.	End of schema.
	-->	-->
	</schema>]]></sourcecode>	</schema>]]></sourcecode>
	</section>	</section>
	</section>	</section>

	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>IANA Considerations</name>	<name>IANA Considerations</name>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>XML Namespace</name>	<name>XML Namespace</name>


		<!-- [rfced] Should this sentence be updated to include "XML schemas"? We ask be
		cause we see this in other RFCs (e.g., RFCs 9167, 9095, 9022).

		Original:
		This document uses URNs to describe XML namespaces conforming to a
		registry mechanism described in RFC 3688 [RFC3688].

		Perhaps:
		This document uses URNs to describe XML namespaces and XML schemas
		conforming to a
		registry mechanism described in [RFC3688].
		-->

	<t> This document uses URNs to describe XML namespaces	<t> This document uses URNs to describe XML namespaces

	conforming to a registry mechanism described in <xref target="RFC3688" forma	conforming to a registry mechanism described in <xref target="RFC3688" forma
	t="default">RFC 3688</xref>. The	t="default"/>. The following URI assignments have been made by IANA:
	following URI assignment should be made by IANA:</t>	</t>
	<t>Registration request for the addlEmail namespace:</t>	<t>Registration for the addlEmail namespace:</t>
	<dl newline="false" spacing="compact">	<dl newline="false" spacing="compact">
	<dt>URI:</dt>	<dt>URI:</dt>
	<dd>urn:ietf:params:xml:ns:epp:addlEmail-1.0</dd>	<dd>urn:ietf:params:xml:ns:epp:addlEmail-1.0</dd>
	<dt>Registrant Contact:</dt>	<dt>Registrant Contact:</dt>
	<dd>IESG</dd>	<dd>IESG</dd>
	<dt>XML:</dt>	<dt>XML:</dt>
	<dd>None. Namespace URIs do not represent an XML specification.</dd>	<dd>None. Namespace URIs do not represent an XML specification.</dd>
	</dl>	</dl>

	<t>Registration request for the addlEmail XML Schema:</t>	<t>Registration for the addlEmail XML Schema:</t>
	<dl newline="false" spacing="compact">	<dl newline="false" spacing="compact">
	<dt>URI:</dt>	<dt>URI:</dt>
	<dd>urn:ietf:params:xml:schema:epp:addlEmail-1.0</dd>	<dd>urn:ietf:params:xml:schema:epp:addlEmail-1.0</dd>
	<dt>Registrant Contact:</dt>	<dt>Registrant Contact:</dt>
	<dd>IESG</dd>	<dd>IESG</dd>
	<dt>XML:</dt>	<dt>XML:</dt>

	<dd>See the "Formal Syntax" section of this document.</dd>	<dd>See <xref target="syntax"/> of this document.</dd>
	</dl>	</dl>
	</section>	</section>
	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>EPP Extension Registry</name>	<name>EPP Extension Registry</name>
	<t>	<t>

	The EPP extension described in this document should be registered by	The EPP extension described in this document have been registered by
	IANA in the "Extensions for the Extensible Provisioning Protocol	IANA in the "Extensions for the Extensible Provisioning Protocol

	(EPP)" registry described in RFC 7451 <xref target="RFC7451" format="default" />. The details of the	(EPP)" registry described in <xref target="RFC7451" format="default"/>. The details of the
	registration are as follows:	registration are as follows:
	</t>	</t>
	<dl newline="false" spacing="compact">	<dl newline="false" spacing="compact">
	<dt>Name of Extension:</dt>	<dt>Name of Extension:</dt>

	<dd>"Additional Email Address Extension for the Extensible Provis	<dd>Additional Email Address Extension for the Extensible Provisi
	ioning Protocol (EPP)"</dd>	oning Protocol (EPP)</dd>
	<dt>Document status:</dt>	<dt>Document Status:</dt>
	<dd>Standards Track</dd>	<dd>Standards Track</dd>
	<dt>Reference:</dt>	<dt>Reference:</dt>

	<dd>(This specification)</dd>	<dd>RFC 9873</dd>
	<dt>Registrant Name and Email Address:</dt>	<dt>Registrant Name and Email Address:</dt>
	<dd>IESG, <iesg@ietf.org></dd>	<dd>IESG, <iesg@ietf.org></dd>

	<dt>Top-Level Domains(TLDs):</dt>	<dt>TLDs:</dt>
	<dd>Any</dd>	<dd>Any</dd>
	<dt>IPR Disclosure:</dt>	<dt>IPR Disclosure:</dt>
	<dd>None</dd>	<dd>None</dd>
	<dt>Status:</dt>	<dt>Status:</dt>
	<dd>Active</dd>	<dd>Active</dd>
	<dt>Notes:</dt>	<dt>Notes:</dt>
	<dd>None</dd>	<dd>None</dd>
	</dl>	</dl>
	</section>	</section>
	</section>	</section>


	<section anchor="Implementation" numbered="true" toc="default">
	<name>Implementation Status</name>
	<t>Note to RFC Editor: Please remove this section and the reference to
	<xref target="RFC7942" format="default">RFC 7942</xref> before publicat
	ion.</t>
	<t>This section records the status of known implementations of the
	protocol defined by this specification at the time of posting of
	this Internet-Draft, and is based on a proposal described in <xref target=
	"RFC7942" format="default">RFC
	7942</xref>. The description of implementations in this section is
	intended to assist the IETF in its decision processes in
	progressing drafts to RFCs. Please note that the listing of any
	individual implementation here does not imply endorsement by the
	IETF. Furthermore, no effort has been spent to verify the
	information presented here that was supplied by IETF contributors.
	This is not intended as, and must not be construed to be, a
	catalog of available implementations or their features. Readers
	are advised to note that other implementations may exist.</t>

	<t>According to <xref target="RFC7942" format="default">RFC 7942</xref>, "
	this will allow reviewers and working
	groups to assign due consideration to documents that have the
	benefit of running code, which may serve as evidence of valuable
	experimentation and feedback that have made the implemented
	protocols more mature. It is up to the individual working groups
	to use this information as they see fit".</t>

	<section numbered="true" toc="default">
	<name>Verisign EPP SDK</name>
	<t>Organization: Verisign Inc.</t>
	<t>Name: Verisign EPP SDK</t>
	<t>Description: The Verisign EPP SDK includes both a full client impleme
	ntation
	and a full server stub implementation of draft-ietf-regext-epp-eai.</t>
	<t>Level of maturity: Development</t>
	<t>Coverage: All aspects of the protocol are implemented.</t>
	<t>Licensing: GNU Lesser General Public License</t>
	<t>Contact: jgould@verisign.com</t>
	<t>URL: https://www.verisign.com/en_US/channel-resources/domain-registry
	-products/epp-sdks</t>
	</section>

	</section>

	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Security Considerations</name>	<name>Security Considerations</name>

	<t>As is noted in Section 10.1 and Section 13 of <xref target="RFC6530" fo rmat="default"/>,	<t>As noted in Sections <xref target="RFC6530" section="10.1" sectionForma t="bare"/> and <xref target="RFC6530" section="13" sectionFormat="bare"/> of <xr ef target="RFC6530" format="default"/>,
	unconstrained Unicode in email addresses can introduce a class of	unconstrained Unicode in email addresses can introduce a class of
	security threats that do not exist with all-ASCII email addresses.	security threats that do not exist with all-ASCII email addresses.
	As EPP exists in ecosystems where email addresses passed in EPP are	As EPP exists in ecosystems where email addresses passed in EPP are

	displayed in RDAP and other services, and copy-and-paste of these	displayed in the Registration Data Access Protocol (RDAP) and other services, and copy-and-paste of these
	email addresses is common for businesses transferring domains via	email addresses is common for businesses transferring domains via
	EPP, there should be safeguards against these threats. Therefore,	EPP, there should be safeguards against these threats. Therefore,
	use of the SMTPUTF8 email addresses as described in this document	use of the SMTPUTF8 email addresses as described in this document
	<bcp14>SHOULD</bcp14> be done with policies that disallow the use of unconstr ained	<bcp14>SHOULD</bcp14> be done with policies that disallow the use of unconstr ained

	Unicode. The domain-part of these SMTPUTF8 email addresses SHOULD	Unicode.

		<!-- [rfced] Would including a citation for "IDNA2008" be helpful for
		readers? Perhaps to [RFC5895]? Also, how may we clarify what the
		domain-part should conform to?

		Original:
		The domain-part of these SMTPUTF8 email addresses SHOULD
		conform to IDNA2008.

		Perhaps:
		The domain-part of these SMTPUTF8 email addresses SHOULD
		conform to the guidelines in IDNA2008 [RFC5895].
		-->

		The domain-part of these SMTPUTF8 email addresses <bcp14>SHOULD</bcp14>
	conform to IDNA2008. The local-part of these SMTPUTF8 email	conform to IDNA2008. The local-part of these SMTPUTF8 email
	addresses <bcp14>SHOULD</bcp14> be restricted to Unicode that does not introd uce the	addresses <bcp14>SHOULD</bcp14> be restricted to Unicode that does not introd uce the
	threats noted in <xref target="RFC6530" format="default"/>. One such possibl e solution would be to	threats noted in <xref target="RFC6530" format="default"/>. One such possibl e solution would be to
	disallow characters outside of Unicode Annex 31 <xref target="Unicode-UAX31" format="default"/>.</t>	disallow characters outside of Unicode Annex 31 <xref target="Unicode-UAX31" format="default"/>.</t>

	<t>
	As email address is often a primary end user contact, and an invalid emai
	l address may put communication with the end user at risk when such contact is n
	ecessary. In case of an invalid domain name in the email address a malicious act
	or can register a valid domain name with similar U-label (homograph attack) and
	assume control over the domain name associated with the contact using social eng
	ineering techniques. To reduce the risk of the use of invalid domain names in em
	ail addresses, registries <bcp14>SHOULD</bcp14> validate the domain name syntax
	in provided email addresses and validate whether the domain name consists of the
	code points allowed by <eref target="https://www.iana.org/assignments/idna-tabl
	es">IDNA Rules and Derived Property Values</eref>.</t>


	<t>Note that the syntax for internationalized email localparts is very li	<!-- [rfced] May we revise "of the code points allowed by IDNA Rules and
	beral. Domains are normalized during MX lookup, while localparts are unconstrain	Derived Property Values" in one of the following ways?
	ed. Implementers may wish to test that their database is able to store difficult
	localparts such as U+0061 U+0300 U+00E0. For more on normalization and these th	Original:
	ree code points, see <xref target="RFC5198" format="default"/> Section 3.</t>	To reduce the risk of the use of invalid domain names in email
		addresses, registries SHOULD validate the domain name syntax in
		provided email addresses and validate whether the domain name
		consists of the code points allowed by IDNA Rules and Derived
		Property Values (https://www.iana.org/assignments/idna-tables).

		Perhaps:
		To reduce the risk of the use of invalid domain names in email
		addresses, registries SHOULD validate the domain name syntax in
		provided email addresses and validate whether the domain name
		consists of the code points listed in the "IDNA Rules and Derived
		Property Values" registry (https://www.iana.org/assignments/idna-tables).

		Or:
		To reduce the risk of the use of invalid domain names in email
		addresses, registries SHOULD validate the domain name syntax in
		provided email addresses and validate whether the domain name
		consists of the allowed code points, i.e., those allocated in the
		"IDNA Rules and Derived Property Values" registry
		(https://www.iana.org/assignments/idna-tables).
		-->

		<t>
		As an email address is often a primary end user contact, an invalid email
		address may put communication with the end user at risk when such contact is ne
		cessary. In case of an invalid domain name in the email address, a malicious act
		or can register a valid domain name with a similar U-label (homograph attack) an
		d assume control over the domain name associated with the contact using social e
		ngineering techniques. To reduce the risk of the use of invalid domain names in
		email addresses, registries <bcp14>SHOULD</bcp14> validate the domain name synta
		x in the provided email addresses and validate whether the domain name consists
		of the code points allowed by <eref target="https://www.iana.org/assignments/idn
		a-tables">"IDNA Rules and Derived Property Values"</eref>.</t>

		<t>Note that the syntax for internationalized email localparts is very li
		beral.
		Domains are normalized during MX lookup, while localparts are unconstrained. Imp
		lementers may wish to test that their database is able to store difficult localp
		arts such as U+0061 U+0300 U+00E0. For more on normalization and these three cod
		e points, see <xref target="RFC5198" section="3" sectionFormat="comma"/>.</t>
	</section>	</section>

	<section numbered="true" toc="default">	<section numbered="true" toc="default">
	<name>Privacy Considerations</name>	<name>Privacy Considerations</name>
	<t>The content of <addlEmail:email> elements can be processed by EPP clients and servers in the same way that <contact:email> elements are processed, including publication in directory services such as RDAP <xref target ="STD95" format="default"/>. Many data protection regulations recognize email ad dresses as personal data, so any policies governing the collection, transmission , and processing of contact information by EPP clients and servers should apply equally to <addlEmail:email> elements.</t>	<t>The content of <addlEmail:email> elements can be processed by EPP clients and servers in the same way that <contact:email> elements are processed, including publication in directory services such as RDAP <xref target ="STD95" format="default"/>. Many data protection regulations recognize email ad dresses as personal data, so any policies governing the collection, transmission , and processing of contact information by EPP clients and servers should apply equally to <addlEmail:email> elements.</t>
	</section>	</section>


	<section numbered="true" toc="default">
	<name>Acknowledgments</name>
	<t>The authors would like to thank
	Alexander Mayrhofer,
	Chris Lonvick,
	Gustavo Lozano,
	Jody Kolker,
	John C Klensin,
	John Levine,
	Klaus Malorny,
	Marc Blanchet,
	Marco Schrieck,
	Mario Loffredo,
	Murray S. Kucherawy,
	Patrick Mevzek,
	Pete Resnick,
	Takahiro Nemoto,
	Taras Heichenko,
	Arnt Gulbrandsen,
	Thomas Corte,
	Gavin Brown, and Andrew Newton for their careful review and valua
	ble comments.</t>
	</section>
	</middle>	</middle>
	<back>	<back>


		<!-- [rfced] Would you like the references to be alphabetized
		or left in their current order?
		-->

	<references>	<references>
	<name>References</name>	<name>References</name>
	<references>	<references>
	<name>Normative References</name>	<name>Normative References</name>

	&RFC2119;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
	&RFC3688;	119.xml"/>
	&RFC5321;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
	&RFC5322;	688.xml"/>
	&RFC5730;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
	&RFC5733;	321.xml"/>
	&RFC5890;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
	&RFC6530;	322.xml"/>
	&RFC6531;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
	&RFC6532;	730.xml"/>
	&RFC8174;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
	&W3C.xmlschema-1;	733.xml"/>
	&W3C.xmlschema-2;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
		890.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
		530.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
		531.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
		532.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
		174.xml"/>
		<reference anchor="W3C.REC-xmlschema-1-20041028" target="https://www.w3.o
		rg/TR/2004/REC-xmlschema-1-20041028/">
		<front>
		<title>XML Schema Part 1: Structures Second Edition</title>
		<author fullname="David Beech" role="editor"/>
		<author fullname="Henry Thompson" role="editor"/>
		<author fullname="Murray Maloney" role="editor"/>
		<author fullname="Noah Mendelsohn" role="editor"/>
		<date day="28" month="October" year="2004"/>
		</front>
		<refcontent>W3C Recommendation</refcontent>
		</reference>
		<reference anchor="W3C.REC-xmlschema-2-20041028" target="https://www.w3.o
		rg/TR/2004/REC-xmlschema-2-20041028">
		<front>
		<title>XML Schema Part 2: Datatypes Second Edition</title>
		<author fullname="Ashok Malhotra" role="editor"/>
		<author fullname="Paul V. Biron" role="editor"/>
		<date day="28" month="October" year="2004"/>
		</front>
		<refcontent>W3C Recommendation</refcontent>
		</reference>
	</references>	</references>
	<references>	<references>
	<name>Informative References</name>	<name>Informative References</name>

	&RFC5198;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.51
	&RFC7451;	98.xml"/>
	&RFC7942;	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
	<referencegroup anchor="STD95" target="https://www.rfc-editor.org	451.xml"/>
	/info/std95">	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.STD.
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC	0095.xml"/>
	.7480.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC	<reference anchor="Unicode-UAX31" target="https://www.unicode.org/reports
	.7481.xml"/>	/tr31/tr31-41.html">
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC	<front>
	.9082.xml"/>	<title>Unicode Identifiers and Syntax</title>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC	<author fullname="Mark Davis" role="editor"/>
	.9083.xml"/>	<author fullname="Robin Leroy" role="editor"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC	<date month="September" year="2024"/>
	.9224.xml"/>	</front>
	</referencegroup>	<refcontent>Version 16.0.0</refcontent>
	<reference anchor="Unicode-UAX31" target="https://unicode.org/rep	<seriesInfo name="Unicode Standard Annex" value="#31"/>
	orts/tr31/">	<annotation>Latest version available at
	<front>	<eref brackets="angle" target="https://www.unicode.org/reports/tr31/"/
	<title>Unicode Standard Annex #31: Unicode Identifiers and Syntax	>.</annotation>
	</title>	</reference>
	<author>
	<organization>The Unicode Consortium</organization>
	</author>
	<date month="September" year="2024"/>
	</front>
	</reference>
	</references>	</references>
	</references>	</references>

	<section numbered="true" toc="default" removeInRFC="true">
	<name>Change History</name>	<section numbered="false" toc="default">
	<section anchor="change-00-to-01" numbered="true" toc="default">	<name>Acknowledgments</name>
	<name>Change from 00 to 01</name>	<t>The authors would like to thank <contact fullname="Alexander
	<ol spacing="normal" type="1">	Mayrhofer"/>, <contact fullname="Chris Lonvick"/>, <contact
	<li>Changed from update of RFC 5733 to use the "Placeholder Text and a	fullname="Gustavo Lozano"/>, <contact fullname="Jody Kolker"/>, <contact
	New Email Element" EPP Extension approach.</li>	fullname="John C. Klensin"/>, <contact fullname="John Levine"/>, <contact
	</ol>	fullname="Klaus Malorny"/>, <contact fullname="Marc Blanchet"/>,
	</section>	<contact fullname="Marco Schrieck"/>, <contact fullname="Mario
	<section anchor="change-01-to-02" numbered="true" toc="default">	Loffredo"/>, <contact fullname="Murray S. Kucherawy"/>, <contact
	<name>Change from 01 to 02</name>	fullname="Patrick Mevzek"/>, <contact fullname="Pete Resnick"/>,
	<ol spacing="normal" type="1">	<contact fullname="Takahiro Nemoto"/>, <contact fullname="Taras
	<li>Fixed the XML schema and the XML examples based on validating them	Heichenko"/>, <contact fullname="Arnt Gulbrandsen"/>, <contact
	.</li>	fullname="Thomas Corte"/>, <contact fullname="Gavin Brown"/>, and
	<li>Added James Gould as co-author.</li>	<contact fullname="Andrew Newton"/> for their careful review and
	<li>Updated the language to apply to any EPP object mapping and to use	valuable comments.</t>
	the EPP contact mapping as an example.</li>
	<li>Updated the structure of document to be consistent with the other
	Command-Response Extensions.</li>
	<li>Replaced the use of "eppEAI" in the XML namespace and the XML name
	space prefix with "eai".</li>
	<li>Changed to use a pointed XML namespace with "0.2" instead of "1.0"
	.</li>
	</ol>
	</section>
	<section anchor="change-02-to-03" numbered="true" toc="default">
	<name>Change from 02 to 03</name>
	<ol spacing="normal" type="1">
	<li>The approach has changed to use the concept of Functional EPP Exten
	sion.</li>
	<li>The examples are removed</li>
	</ol>
	</section>
	<section anchor="change-03-to-04" numbered="true" toc="default">
	<name>Change from 03 to 04</name>
	<ol spacing="normal" type="1">
	<li>More detailed reference to email syntax is provided</li>
	<li>The shortened eai namespace reference is removed</li>
	</ol>
	</section>
	<section anchor="change-04-to-ietf-01" numbered="true" toc="default">
	<name>Change from 04 to the regext 01 version</name>
	<ol spacing="normal" type="1">
	<li>Provided the recommended placeholder value</li>
	</ol>
	</section>
	<section anchor="change-ietf-01-to-ietf-02" numbered="true" toc="default">
	<name>Change from the regext 01 to regext 02 version</name>
	<ol spacing="normal" type="1">
	<li>Removed the concept of the placeholder value</li>
	</ol>
	</section>
	<section anchor="change-ietf-02-to-ietf-03" numbered="true" toc="default">
	<name>Change from the regext 02 to regext 03 version</name>
	<ol spacing="normal" type="1">
	<li>Changed to use a pointed XML namespace with "0.3" instead of "0.2"
	.</li>
	<li>Some wording improvements</li>
	</ol>
	</section>
	<section anchor="change-ietf-03-to-ietf-04" numbered="true" toc="default">
	<name>Change from the regext 03 to regext 04 version</name>
	<ol spacing="normal" type="1">
	<li>Some nitpicking</li>
	</ol>
	</section>
	<section anchor="change-ietf-04-to-ietf-05" numbered="true" toc="default">
	<name>Change from the regext 04 to regext 05 version</name>
	<ol spacing="normal" type="1">
	<li>Some nitpicking</li>
	<li>The "Implementation considerations" section is removed</li>
	</ol>
	</section>
	<section anchor="change-ietf-05-to-ietf-06" numbered="true" toc="default">
	<name>Change from the regext 05 to regext 06 version</name>
	<ol spacing="normal" type="1">
	<li>Some nitpicking</li>
	</ol>
	</section>
	<section anchor="change-ietf-06-to-ietf-07" numbered="true" toc="default">
	<name>Change from the regext 06 to regext 07 version</name>
	<ol spacing="normal" type="1">
	<li>Namespace version set to 1.0</li>
	</ol>
	</section>
	<section anchor="change-ietf-07-to-ietf-08" numbered="true" toc="default">
	<name>Change from the regext 07 to regext 08 version</name>
	<ol spacing="normal" type="1">
	<li>Information about implementations is provided.</li>
	<li>Acknowledgments section is added.</li>
	<li>Reference to RFC 7451 is moved to Informative.</li>
	<li>IPR information is provided</li>
	<li>Sections are reordered to align with the other regext documen
	ts</li>
	</ol>
	</section>
	<section anchor="change-ietf-08-to-ietf-09" numbered="true" toc="default">
	<name>Change from the regext 08 to regext 09 version</name>
	<ol spacing="normal" type="1">
	<li>Nitpicking according to Murray S. Kucherawy review</li>
	</ol>
	</section>
	<section anchor="change-ietf-09-to-ietf-10" numbered="true" toc="default">
	<name>Change from the regext 09 to regext 10 version</name>
	<ol spacing="normal" type="1">
	<li>Some nitpicking in the security considerations.</li>
	</ol>
	</section>
	<section anchor="change-ietf-10-to-ietf-11" numbered="true" toc="default">
	<name>Change from the regext 10 to regext 11 version</name>
	<ol spacing="normal" type="1">
	<li>Nitpicking according mostly GenArt review.</li>
	</ol>
	</section>
	<section anchor="change-ietf-11-to-ietf-12" numbered="true" toc="default">
	<name>Change from the regext 11 to regext 12 version</name>
	<ol spacing="normal" type="1">
	<li>XML schema registration request removed.</li>
	</ol>
	</section>
	<section anchor="change-ietf-12-to-ietf-13" numbered="true" toc="default">
	<name>Change from the regext 12 to regext 13 version</name>
	<ol spacing="normal" type="1">
	<li>Document updated according to SecDir and ART-ART review.</li>
	</ol>
	</section>
	<section anchor="change-ietf-13-to-ietf-14" numbered="true" toc="default">
	<name>Change from the regext 13 to regext 14 version</name>
	<ol spacing="normal" type="1">
	<li>Document updated according the IANA review #1231866.</li>
	</ol>
	</section>
	<section anchor="change-ietf-14-to-ietf-15" numbered="true" toc="default">
	<name>Change from the regext 14 to regext 15 version</name>
	<ol spacing="normal" type="1">
	<li>Document updated according to ART-ART review.</li>
	</ol>
	</section>
	<section anchor="change-ietf-15-to-ietf-16" numbered="true" toc="default">
	<name>Change from the regext 15 to regext 16 version</name>
	<ol spacing="normal" type="1">
	<li>Document removed the definition of the concept of a functional extension a
	nd updated to use a command-response extension, based on the feedback from John
	C Klensin.</li>
	<li>Document removed the EAI abbreviation and uses SMTPUTF8 as umbrella term i
	nstead, based on the feedback from John C Klensin.</li>
	</ol>
	</section>
	<section anchor="change-ietf-16-to-ietf-17" numbered="true" toc="default">
	<name>Change from the regext 16 to regext 17 version</name>
	<ol spacing="normal" type="1">
	<li>Added support for an alternate email during a transition period, based on
	feedback from John C Klensin.</li>
	</ol>
	</section>
	<section anchor="change-ietf-17-to-ietf-18" numbered="true" toc="default">
	<name>Change from the regext 17 to regext 18 version</name>
	<ol spacing="normal" type="1">
	<li>Roll back to approach in -16 with the Cardinality of One Option, posted to
	and supported on the mailing list.</li>
	<li>Replaced references of eai to smtputf8, based on feedback from John C Klen
	sin.</li>
	<li>Revised the Security Considerations section based on feedback and text fro
	m Andy Newton.</li>
	</ol>
	</section>
	<section anchor="change-ietf-18-to-ietf-19" numbered="true" toc="default">
	<name>Change from the regext 18 to regext 19 version</name>
	<ol spacing="normal" type="1">
	<li>Reverted back to -17 with support for one or two email addresses using eit
	her ASCII or SMTPUTF8 and remove any reference to the requirement for an ASCII e
	mail address and remove the concept of a transition period.</li>
	</ol>
	</section>
	<section anchor="change-ietf-19-to-ietf-20" numbered="true" toc="default">
	<name>Change from the regext 19 to regext 20 version</name>
	<ol spacing="normal" type="1">
	<li>Reverted Security Considerations section back to the content in -18 based
	on feedback from Andy Newton.</li>
	</ol>
	</section>
	<section anchor="change-ietf-20-to-ietf-21" numbered="true" toc="default">
	<name>Change from the regext 20 to regext 21 version</name>
	<ol spacing="normal" type="1">
	<li>Added Scott Hollenbeck as a document editor. Rewrote the draft to require
	ASCII-only email addresses in the base contact object mapping, allowing either A
	SCII-only or SMTPUTF8 addresses in the extension.</li>
	<li>Replaced "eai" with "addlEmail" in the extension-identifying URNs and sche
	ma elements.</li>
	</ol>
	</section>
	<section anchor="change-ietf-21-to-ietf-22" numbered="true" toc="default">
	<name>Change from the regext 21 to regext 22 version</name>
	<ol spacing="normal" type="1">
	<li>Fixed XML schema to use correct complexType.</li>
	<li>Added Implementation Status section.</li>
	<li>Example line formatting to fit within 72 characters.</li>
	</ol>
	</section>
	<section anchor="change-ietf-22-to-ietf-23" numbered="true" toc="default">
	<name>Change from the regext 22 to regext 23 version</name>
	<ol spacing="normal" type="1">
	<li>Second WG last call updates.</li>
	</ol>
	</section>
	<section anchor="change-ietf-23-to-ietf-24" numbered="true" toc="default">
	<name>Change from the regext 23 to regext 24 version</name>
	<ol spacing="normal" type="1">
	<li>Second IETF last call updates:</li>
	<li>Changed document name to reflect change from focus on SMTPUTF8 addresses t
	o an additional email address that can be either an SMTPUTF8 address or an all-A
	SCII address.</li>
	<li>Added additional mail address considerations.</li>
	</ol>
	</section>
	<section anchor="change-ietf-24-to-ietf-25" numbered="true" toc="default">
	<name>Change from the regext 24 to regext 25 version</name>
	<ol spacing="normal" type="1">
	<li>IESG Evaluation updates:</li>
	<li>Updated Dmitry's address.</li>
	</ol>
	</section>
	<section anchor="change-ietf-25-to-ietf-26" numbered="true" toc="default">
	<name>Change from the regext 25 to regext 26 version</name>
	<ol spacing="normal" type="1">
	<li>IESG Evaluation updates. Revised text to describe email address syntax in
	the Introduction. This was inadvertently missed in -25.</li>
	</ol>
	</section>
	<section anchor="change-ietf-26-to-ietf-27" numbered="true" toc="default">
	<name>Change from the regext 26 to regext 27 version</name>
	<ol spacing="normal" type="1">
	<li>IESG Evaluation updates. Added reference to RFC 5730 in Section 4.1. Fixed
	extension name in the IANA Considerations section.</li>
	</ol>
	</section>	</section>

	</section>
	</back>	</back>


		<!-- [rfced] We note inconsistencies in the terms below throughout the
		text. Should these be uniform? If so, please let us know which form is
		preferred.

		command-response extension
		command and response extension

		local-part
		localpart

		ASCII alternate email address
		alternate ASCII email address

		all-ASCII
		ASCII-only
		-->

		<!-- [rfced] FYI - We have added expansions for the following
		abbreviation(s) per Section 3.6 of RFC 7322 ("RFC Style Guide").
		Please review each expansion in the document carefully to ensure
		correctness.

		Registration Data Access Protocol (RDAP)
		-->

		<!-- [rfced] Please review the "Inclusive Language" portion of the online
		Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
		and let us know if any changes are needed. Updates of this nature typically
		result in more precise language, which is helpful for readers.

		For example, please consider whether "natively" should be updated:

		Original:
		The Extensible Provisioning Protocol (EPP) does not natively support
		internationalized email addresses because the specifications for
		these addresses did not exist when the EPP was developed.
		-->

	</rfc>	</rfc>

End of changes. 76 change blocks.
	526 lines changed or deleted	491 lines changed or added
This html diff was produced by rfcdiff 1.48.