<?xml version='1.0'encoding='utf-8'?>encoding='UTF-8'?> <!DOCTYPE rfc [<!-- One method to get references from the online citation libraries. There has to be one entity for each item to be referenced. An alternate method (rfc include) is described in the references. --> <!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.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"><!ENTITYRFC5890 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml">nbsp " "> <!ENTITYRFC6530 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6530.xml">zwsp "​"> <!ENTITYRFC6531 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6531.xml">nbhy "‑"> <!ENTITYRFC6532 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/reference.W3C.REC-xmlschema-1-20041028.xml"> <!ENTITY W3C.xmlschema-2 SYSTEM "http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-xmlschema-2-20041028.xml">wj "⁠"> ]> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-regext-epp-eai-27" number="9873" category="std" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en" symRefs="true" sortRefs="false" tocInclude="true" version="3" consensus="true"><!-- xml2rfc v2v3 conversion 2.47.0 --><front> <title abbrev="EPP Additional Email Address Extension">Additional Email Address Extension for the Extensible Provisioning Protocol (EPP)</title> <seriesInfo name="RFC" value="9873"/> <author fullname="Dmitry Belyavskiy" initials="D." surname="Belyavskiy"> <address> <postal> <street>Karpatska 241/3</street> <city>Brno</city> <code>62500</code> <country>Czech Republic</country> </postal> <phone>+420 603 261 036</phone> <email>beldmit@gmail.com</email> </address> </author> <author fullname="James Gould" surname="Gould"> <organization>VeriSign, Inc.</organization> <address> <postal> <street>12061 Bluemont Way</street> <city>Reston</city> <region>VA</region> <code>20190</code><country>US</country><country>United States of America</country> </postal> <email>jgould@verisign.com</email><uri>http://www.verisigninc.com</uri><uri>https://www.verisigninc.com</uri> </address> </author> <author initials="S." surname="Hollenbeck" fullname="Scott Hollenbeck"> <organization>Verisign Labs</organization> <address> <postal> <street>12061 Bluemont Way</street> <city>Reston</city> <region>VA</region> <code>20190</code><country>USA</country><country>United States of America</country> </postal> <email>shollenbeck@verisign.com</email> <uri>https://www.verisignlabs.com/</uri> </address> </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> <t>The Extensible Provisioning Protocol (EPP) does not natively support internationalized email addresses because the specifications for these addresses did 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 internationalized email address or an all-ASCII address.</t> </abstract> </front> <middle> <section numbered="true" toc="default"> <name>Introduction</name> <t>The framework for internationalized email addresses is described in <xref target="RFC6530" format="default"/>. This document describes an Extensible Provisioning Protocol (EPP) <xref target="RFC5730" format="default"/> command-response extension that adds support for adding a second email address to the EPP contact object mapping <xref target="RFC5733"format="default"/> mapping.format="default"/>. The syntax for the email address associated with the base contact object is described inSection 2.6 of<xref target="RFC5733"format="default"/>.section="2.6"/>. The second email address can be either an ASCII-only email address or aninternationalized,internationalized SMTPUTF8 email address <xref target="RFC6530"format="default"/> email address.format="default"/>. This second address can be used to identify an alternate ASCII-only email address for use in case of primary address delivery issues. It can also be used to identify an SMTPUTF8 address for contact purposes, in which case the ASCII-only address can be used in case of SMTPUTF8 address 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 require an update to the relevant extension specifications. In cases where a contact 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 message sent to an all-ASCII address may receive a reply from an SMTPUTF8address,address or vice versa.</t> <section numbered="true" toc="default"> <name>Conventions Used in This Document</name> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xreftarget="RFC2119" format="default"/>target="RFC2119"/> <xreftarget="RFC8174" format="default"/>target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t>here. </t> <t>XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document <bcp14>MUST</bcp14> be interpreted in the character case presented in order to develop a conforming implementation.</t> <t>In examples, "C:" represents lines sent by a protocolclientclient, and "S:" represents lines returned by a protocol server. Indentation and white space in the examples are provided only to illustrate element relationships and are notREQUIRED<bcp14>REQUIRED</bcp14> in the protocol.</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 "urn:ietf:params:xml:ns:epp:addlEmail-1.0", but implementations <bcp14>MUST NOT</bcp14> depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.</t> </section> </section> <section anchor="emailAddressSpec" numbered="true" toc="default"> <name>Email Address Specification</name> <!-- [rfced] This sentence is a bit hard to follow because of the many commas. We added parentheses rather than commas around the "defined in" phrases and added "to support" before "U-label" in this sentence. Please let us know any concerns. Original: [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 U-label, defined in Section 2.3.2.1 of [RFC5890], for the domain. 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"/> normatively references <xref target="RFC5322" format="default"/> as the specification for email address syntax. That specification does not include support for internationalized email addresses. <xref target="RFC6530"format="default">RFC 6530</xref>format="default"/> provides an overview and describes the framework for internationalized email. SMTPUTF8 email address syntax is described inSection 3.3 of<xref target="RFC6531"format="default"/>.section="3.3"/>. <xref target="RFC6531" format="default"/> extends the Mailbox,Local-partLocal-part, and Domain ABNF rules in <xref target="RFC5321" format="default"/> to support"UTF8-non-ascii", defined"UTF8-non-ascii" (defined inSection 3.1 of<xref target="RFC6532"format="default"/>,section="3.1"/>) for the local-part andU-label, definedto support U-label (defined inSection 2.3.2.1 of<xref target="RFC5890"format="default"/>,section="2.3.2.1"/>) for the domain. The validation rules described inRFC 6531<xref target="RFC6531" format="default"/> <bcp14>MUST</bcp14> be followed when processing internationalized email addresses associated with this extension.</t> </section> <section anchor="addlEmailElement" numbered="true" toc="default"> <name>Additional Email Address Element</name> <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 element:</t> <dl newline="false" indent="4"> <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:email/> element unsets the second email address in the<xref target="updateCommand">Update Command</xref>Update Command (<xref target="updateCommand"></xref>) and indicates the second email is not set in the<xref target="infoCommand">Info Response</xref>.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 email address should be treated as the primary email address for the extended contact object. The "primary" attribute <bcp14>MUST NOT</bcp14> be present if the <addlEmail:email> is empty.</dd> </dl> <t>Additional email address considerations:</t> <ul> <li>The value set for the <contact:disclose><contact:email/> "flag" attribute (described inSection 2.9 of RFC 5733<xref target="RFC5733"format="default"/>) MUSTsection="2.9"/>) <bcp14>MUST</bcp14> also be applied to all additional email addresses that are added by a contact extension.</li><li>Any<!-- [rfced] Should "that support" here be updated to just "support"? Is is another meaning intended? Original: * Any address included in an extension is intended to be an additional address that's associated only with the primary<contact:email><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 additional 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 existing addresses.</li> </ul> </section> <section numbered="true" toc="default"> <name>Extension Considerations</name> <section numbered="true" toc="default"> <name>Signaling Client and Server Support</name> <t> As described inSection 2.4 of<xref target="RFC5730"format="default"/>,section="2.4"/>, the client and the server can signal support for the extension using a namespace URI in the login and greeting extensionservicesservices, respectively. The namespace URI "urn:ietf:params:xml:ns:epp:addlEmail-1.0" is used to signal support for the extension. The client includes the namespace URI in an <svcExtension> <extURI> element of the <login> command <xref target="RFC5730"format="default"/> <login> Command.format="default"/>. The server includes the namespace URI in an <svcExtension> <extURI> element of the greeting <xref target="RFC5730"format="default"/> greeting.format="default"/>. </t> </section> <section numbered="true" toc="default"> <name>Extension Behavior</name> <section numbered="true" toc="default"> <name>Extension Negotiated</name> <t> If both client and server have indicated support for SMTPUTF8 addresses during session establishment, they <bcp14>MUST</bcp14> be able to process an SMTPUTF8 address 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>The server <bcp14>MUST</bcp14> satisfy the following obligations when support for this extension has been negotiated:</t> <ul> <li>AcceptSMTPUTF8 compliantSMTPUTF8-compliant addresses for the extended contact object in the EPP session.</li> <li>Support email address validation based on the SMTPUTF8 validation rules defined in <xref target="emailAddressSpec"format="default"/></li>format="default"/>.</li> <!-- [rfced] In the first bulleted list in Section 4.2.1, the list items all begin with a verb except for the following one. How may we update this one to create parallel structure? Original: * 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 characters.</li> <li>ReturnSMTPUTF8 compliantSMTPUTF8-compliant addresses for the extended contact object in EPP responses.</li> <li>Support the SMTP extension for internationalized email described in <xref target="RFC6531" format="default"/> when sending or receiving email.</li> </ul> <t>The client <bcp14>MUST</bcp14> satisfy the following obligations when support for this extension has been negotiated:</t> <ul> <li>ProvideSMTPUTF8 compliantSMTPUTF8-compliant addresses for the extended contact object in the EPP session.</li> <li>AcceptSMTPUTF8 compliantSMTPUTF8-compliant addresses for the extended contact object in EPP responses.</li> <li>Support the SMTP extension for internationalized email described in <xref target="RFC6531" format="default"/> when sending or receiving email.</li> </ul> </section> <section numbered="true" toc="default"> <name>Extension Not Negotiated</name> <t>An extended contact object <bcp14>MUST NOT</bcp14> be provided or returned 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> <sectionanchor="commands" title="EPPanchor="commands"> <name>EPP CommandMapping">Mapping</name> <t>A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification <xref target="RFC5730"/>. This section defines the provisioning of an alternate email address.</t> <sectionanchor="queryCommands" title="EPPanchor="queryCommands"> <name>EPP QueryCommands">Commands</name> <t>EPP provides three commands to retrieve object information: <check> to determine if an object can be provisioned, <info> to retrieve information associated with an object, and <transfer> to retrieve object-transfer status information.</t> <sectionanchor="checkCommand" title="EPPanchor="checkCommand"> <name>EPP <check>Command">Command</name> <t>This extension does not add any elements to the EPP <check> command or <check> response described in <xref target="RFC5730"/>.</t> </section><!-- end CHECK command --><sectionanchor="infoCommand" title="EPPanchor="infoCommand"> <name>EPP <info>Command">Command</name> <t>This extension does not add any elements to the EPP <info> command response described in <xref target="RFC5730"/>.</t> <t> If the querywasis successful, the server replies with an<xref target="addlEmailElement"><addlEmail:addlEmail> element</xref><addlEmail:addlEmail> element (<xref target="addlEmailElement"></xref>) along with the regular EPP <resData>. </t><t>The<!-- [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><info> contact response using the<addlEmail:addlEmail><addlEmail:addlEmail> extension with no alternate emailaddress:</t> <figure> <name>Exampleaddress: ... 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 <addlEmail:addlEmail> extension with no alternate emailaddress</name>address:</t> <figure> <name>Example <info> Contact Response Using the <addlEmail:addlEmail> Extension with No Alternate Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <resData> S: <contact:infData S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> S: <contact:id>sh8013</contact:id> S: <contact:roid>SH8013-REP</contact:roid> S: <contact:status s="linked"/> S: <contact:status s="clientDeleteProhibited"/> S: <contact:postalInfo type="int"> S: <contact:name>John Doe</contact:name> S: <contact:org>Example Inc.</contact:org> S: <contact:addr> S: <contact:street>123 Example Dr.</contact:street> S: <contact:street>Suite 100</contact:street> S: <contact:city>Dulles</contact:city> S: <contact:sp>VA</contact:sp> S: <contact:pc>20166-6503</contact:pc> S: <contact:cc>US</contact:cc> S: </contact:addr> S: </contact:postalInfo> S: <contact:voice x="1234">+1.7035555555</contact:voice> S: <contact:fax>+1.7035555556</contact:fax> S: <contact:email>jdoe@example.com</contact:email> S: <contact:clID>ClientY</contact:clID> S: <contact:crID>ClientX</contact:crID> S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate> S: <contact:upID>ClientX</contact:upID> S: <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate> S: <contact:trDate>2000-04-08T09:00:00.0Z</contact:trDate> S: <contact:authInfo> S: <contact:pw>2fooBAR</contact:pw> S: </contact:authInfo> S: <contact:disclose flag="0"> S: <contact:voice/> S: <contact:email/> S: </contact:disclose> S: </contact:infData> S: </resData> S: <extension> S: <addlEmail:addlEmail S: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> S: <addlEmail:email/> S: </addlEmail:addlEmail> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S:</epp>]]></sourcecode> </figure> <t>The following is an example <info> contact response using the <addlEmail:addlEmail> extension with an ASCII alternate email address:</t> <figure> <name>Example <info>contact response usingContact Response Using the <addlEmail:addlEmail>extensionExtension with an ASCIIalternate email address</name>Alternate Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <resData> S: <contact:infData S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> S: <contact:id>sh8013</contact:id> S: <contact:roid>SH8013-REP</contact:roid> S: <contact:status s="linked"/> S: <contact:status s="clientDeleteProhibited"/> S: <contact:postalInfo type="int"> S: <contact:name>John Doe</contact:name> S: <contact:org>Example Inc.</contact:org> S: <contact:addr> S: <contact:street>123 Example Dr.</contact:street> S: <contact:street>Suite 100</contact:street> S: <contact:city>Dulles</contact:city> S: <contact:sp>VA</contact:sp> S: <contact:pc>20166-6503</contact:pc> S: <contact:cc>US</contact:cc> S: </contact:addr> S: </contact:postalInfo> S: <contact:voice x="1234">+1.7035555555</contact:voice> S: <contact:fax>+1.7035555556</contact:fax> S: <contact:email>jdoe@example.com</contact:email> S: <contact:clID>ClientY</contact:clID> S: <contact:crID>ClientX</contact:crID> S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate> S: <contact:upID>ClientX</contact:upID> S: <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate> S: <contact:trDate>2000-04-08T09:00:00.0Z</contact:trDate> S: <contact:authInfo> S: <contact:pw>2fooBAR</contact:pw> S: </contact:authInfo> S: <contact:disclose flag="0"> S: <contact:voice/> S: <contact:email/> S: </contact:disclose> S: </contact:infData> S: </resData> S: <extension> S: <addlEmail:addlEmail S: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> S: <addlEmail:email>jdoe-alt@example.net</addlEmail:email> S: </addlEmail:addlEmail> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S:</epp>]]></sourcecode> </figure> <t>The following is an example <info> contact response using the <addlEmail:addlEmail> extension with an SMTPUTF8 primary email address:</t> <figure> <name>Example <info>contact response usingContact Response Using the <addlEmail:addlEmail>extensionExtension with an SMTPUTF8primary email address</name>Primary Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <resData> S: <contact:infData S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> S: <contact:id>sh8013</contact:id> S: <contact:roid>SH8013-REP</contact:roid> S: <contact:status s="linked"/> S: <contact:status s="clientDeleteProhibited"/> S: <contact:postalInfo type="int"> S: <contact:name>John Doe</contact:name> S: <contact:org>Example Inc.</contact:org> S: <contact:addr> S: <contact:street>123 Example Dr.</contact:street> S: <contact:street>Suite 100</contact:street> S: <contact:city>Dulles</contact:city> S: <contact:sp>VA</contact:sp> S: <contact:pc>20166-6503</contact:pc> S: <contact:cc>US</contact:cc> S: </contact:addr> S: </contact:postalInfo> S: <contact:voice x="1234">+1.7035555555</contact:voice> S: <contact:fax>+1.7035555556</contact:fax> S: <contact:email>jdoe@example.com</contact:email> S: <contact:clID>ClientY</contact:clID> S: <contact:crID>ClientX</contact:crID> S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate> S: <contact:upID>ClientX</contact:upID> S: <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate> S: <contact:trDate>2000-04-08T09:00:00.0Z</contact:trDate> S: <contact:authInfo> S: <contact:pw>2fooBAR</contact:pw> S: </contact:authInfo> S: <contact:disclose flag="0"> S: <contact:voice/> S: <contact:email/> S: </contact:disclose> S: </contact:infData> S: </resData> S: <extension> S: <addlEmail:addlEmail S: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> S: <addlEmail:email primary="true">麥克風@example.com</addlEmail:email> S: </addlEmail:addlEmail> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S:</epp>]]></sourcecode> </figure> </section> <!--end INFO command[rfced] Should the title of Section 5.1.3 be updated from "Query Command" 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 --> <sectionanchor="transferQueryCommand" title="EPPanchor="transferQueryCommand"> <name>EPP <transfer> QueryCommand">Command</name> <t>This extension does not add any elements to the EPP <transfer> query command or <transfer> query response described in <xref target="RFC5730"/>.</t> </section><!-- end TRANSFER QUERY command --></section> <sectionanchor="transformCommands" title="EPPanchor="transformCommands"> <name>EPP TransformCommands">Commands</name> <t>EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object.</t> <sectionanchor="createCommand" title="EPPanchor="createCommand"> <name>EPP <create>Command">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 <create> command of an object mapping like <xref target="RFC5733"/>.</t> <t>The EPP <create> command provides a transform operation that allows a client to create an instance of an object. In addition to the EPP command elements described in an object mapping like <xref target="RFC5733"/>, the command <bcp14>MUST</bcp14> contain a child<xref target="addlEmailElement"><addlEmail:addlEmail> element</xref><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> <figure> <name>Example <create>commandCommand tocreateCreate acontact objectContact Object with analternateAlternate ASCIIemail address</name>Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <create> C: <contact:create C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> C: <contact:id>sh8013</contact:id> C: <contact:postalInfo type="int"> C: <contact:name>John Doe</contact:name> C: <contact:org>Example Inc.</contact:org> C: <contact:addr> C: <contact:street>123 Example Dr.</contact:street> C: <contact:street>Suite 100</contact:street> C: <contact:city>Dulles</contact:city> C: <contact:sp>VA</contact:sp> C: <contact:pc>20166-6503</contact:pc> C: <contact:cc>US</contact:cc> C: </contact:addr> C: </contact:postalInfo> C: <contact:voice x="1234">+1.7035555555</contact:voice> C: <contact:fax>+1.7035555556</contact:fax> C: <contact:email>jdoe@example.com</contact:email> C: <contact:authInfo> C: <contact:pw>2fooBAR</contact:pw> C: </contact:authInfo> C: <contact:disclose flag="0"> C: <contact:voice/> C: <contact:email/> C: </contact:disclose> C: </contact:create> C: </create> C: <extension> C: <addlEmail:addlEmail C: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> C: <addlEmail:email>jdoe-alt@example.net</addlEmail:email> C: </addlEmail:addlEmail> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>]]></sourcecode> </figure> <t>The following is an example <create> command to create a contact object with a primary SMTPUTF8 email address:</t> <figure> <name>Example <create>commandCommand tocreateCreate acontact objectContact Object with aprimaryPrimary SMTPUTF8email address</name>Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <create> C: <contact:create C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> C: <contact:id>sh8013</contact:id> C: <contact:postalInfo type="int"> C: <contact:name>John Doe</contact:name> C: <contact:org>Example Inc.</contact:org> C: <contact:addr> C: <contact:street>123 Example Dr.</contact:street> C: <contact:street>Suite 100</contact:street> C: <contact:city>Dulles</contact:city> C: <contact:sp>VA</contact:sp> C: <contact:pc>20166-6503</contact:pc> C: <contact:cc>US</contact:cc> C: </contact:addr> C: </contact:postalInfo> C: <contact:voice x="1234">+1.7035555555</contact:voice> C: <contact:fax>+1.7035555556</contact:fax> C: <contact:email>jdoe@example.com</contact:email> C: <contact:authInfo> C: <contact:pw>2fooBAR</contact:pw> C: </contact:authInfo> C: <contact:disclose flag="0"> C: <contact:voice/> C: <contact:email/> C: </contact:disclose> C: </contact:create> C: </create> C: <extension> C: <addlEmail:addlEmail C: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> C: <addlEmail:email primary="true">麥克風@example.com</addlEmail:email> C: </addlEmail:addlEmail> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>]]></sourcecode> </figure> <t>This extension does not add any elements to the EPP <create> response described in <xref target="RFC5730"/>.</t> </section><!-- end CREATE command --><sectionanchor="deleteCommand" title="EPPanchor="deleteCommand"> <name>EPP <delete>Command">Command</name> <t>This extension does not add any elements to the EPP <delete> command or <delete> response described in <xref target="RFC5730"/>.</t> </section><!-- end DELETE command --><sectionanchor="renewCommand" title="EPPanchor="renewCommand"> <name>EPP <renew>Command">Command</name> <t>This extension does not add any elements to the EPP <renew> command or <renew> response described in <xref target="RFC5730"/>.</t> </section><!-- end RENEW command --><sectionanchor="transferCommand" title="EPPanchor="transferCommand"> <name>EPP <transfer>Command">Command</name> <t>This extension does not add any elements to the EPP <transfer> command or <transfer> response described in <xref target="RFC5730"/>.</t> </section><!-- end TRANSFER command --><sectionanchor="updateCommand" title="EPPanchor="updateCommand"> <name>EPP <update>Command">Command</name> <t>This extension defines additional elements to extend the EPP <update> command of an object mapping like <xref target="RFC5733"/>.</t> <t>The EPP <update> command provides a transform operation that allows a client to update an instance of an object. In addition to the EPP command elements described in an object mapping like <xref target="RFC5733"/>, the command <bcp14>MUST</bcp14> contain a child<xref target="addlEmailElement"><addlEmail:addlEmail> element</xref><addlEmail:addlEmail> element (<xref target="addlEmailElement"></xref>) for the client to set or unset an alternate email address. If the alternate email address cannot be applied to the object, the server <bcp14>MUST</bcp14> return an EPP error result code of 2201.</t> <t>The following is an example <update> command to set a contact object with an alternate ASCII email address:</t> <figure> <name>Example <update>commandCommand tosetSet acontact objectContact Object with analternateAlternate ASCIIemail address</name>Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <update> C: <contact:update C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> C: <contact:id>sh8013</contact:id> C: </contact:update> C: </update> C: <extension> C: <addlEmail:addlEmail C: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> C: <addlEmail:email>jdoe-alt@example.net</addlEmail:email> C: </addlEmail:addlEmail> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>]]></sourcecode> </figure> <t>The following is an example <update> command to set a contact object with an alternate SMTPUTF8 email address:</t> <figure> <name>Example <update>commandCommand tosetSet acontact objectContact Object with analternateAlternate SMTPUTF8email address</name>Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <update> C: <contact:update C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> C: <contact:id>sh8013</contact:id> C: </contact:update> C: </update> C: <extension> C: <addlEmail:addlEmail C: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> C: <addlEmail:email>麥克風@example.com</addlEmail:email> C: </addlEmail:addlEmail> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>]]></sourcecode> </figure> <t>The following is an example <update> command to unset a contact object alternate email address:</t> <figure> <name>Example <update>commandCommand tounsetUnset acontact object alternate email address</name>Contact Object Alternate Email Address</name> <sourcecode type="xml" markers="false"><![CDATA[ C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <update> C: <contact:update C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> C: <contact:id>sh8013</contact:id> C: </contact:update> C: </update> C: <extension> C: <addlEmail:addlEmail C: xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0"> C: <addlEmail:email/> C: </addlEmail:addlEmail> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>]]></sourcecode> </figure> <t>This extension does not add any elements to the EPP <update> response described in <xref target="RFC5730"/>.</t> </section> <!-- end UPDATE command --> </section> </section> <section anchor="syntax" numbered="true" toc="default"> <name>Formal Syntax</name> <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="W3C.REC-xmlschema-1-20041028"/>,<xreftarget="W3C.REC-xmlschema-2-20041028"/>)target="W3C.REC-xmlschema-1-20041028"/> <xref target="W3C.REC-xmlschema-2-20041028"/> representation of the object mapping suitable for automated validation of EPP XML instances. The <CODE BEGINS> and <CODE ENDS> tags are not part of the XML Schema; they are used to note the beginning and ending of the XML Schema for URI registration purposes.</t> <section numbered="true" toc="default"> <name>EPP Additional Email Address Extension Schema</name> <sourcecode type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:addlEmail="urn:ietf:params:xml:ns:epp:addlEmail-1.0" targetNamespace="urn:ietf:params:xml:ns:epp:addlEmail-1.0" elementFormDefault="qualified"> <annotation> <documentation>Extensible Provisioning Protocol v1.0 additional email address schema.</documentation> </annotation> <!-- Create, Update, and Info Response extension element --> <element name="addlEmail" type="addlEmail:addlEmailType" /> <!-- Single email element that can be empty --> <complexType name="addlEmailType"> <sequence> <element name="email" type="addlEmail:emailType"/> </sequence> </complexType> <complexType name="emailType"> <simpleContent> <extension base="token"> <attribute name="primary" type="boolean" default="false"/> </extension> </simpleContent> </complexType> <!-- End of schema. --> </schema>]]></sourcecode> </section> </section> <section numbered="true" toc="default"> <name>IANA Considerations</name> <section numbered="true" toc="default"> <name>XML Namespace</name> <!-- [rfced] Should this sentence be updated to include "XML schemas"? We ask because 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 conforming to a registry mechanism described in <xref target="RFC3688"format="default">RFC 3688</xref>.format="default"/>. The following URIassignment should beassignments have been made byIANA:</t>IANA: </t> <t>Registrationrequestfor the addlEmail namespace:</t> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:epp:addlEmail-1.0</dd> <dt>Registrant Contact:</dt> <dd>IESG</dd> <dt>XML:</dt> <dd>None. Namespace URIs do not represent an XML specification.</dd> </dl> <t>Registrationrequestfor the addlEmail XML Schema:</t> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:schema:epp:addlEmail-1.0</dd> <dt>Registrant Contact:</dt> <dd>IESG</dd> <dt>XML:</dt> <dd>Seethe "Formal Syntax" section<xref target="syntax"/> of this document.</dd> </dl> </section> <section numbered="true" toc="default"> <name>EPP Extension Registry</name> <t> The EPP extension described in this documentshould behave been registered by IANA in the "Extensions for the Extensible Provisioning Protocol (EPP)" registry described inRFC 7451<xref target="RFC7451" format="default"/>. The details of the registration are as follows: </t> <dl newline="false" spacing="compact"> <dt>Name of Extension:</dt><dd>"Additional<dd>Additional Email Address Extension for the Extensible Provisioning Protocol(EPP)"</dd>(EPP)</dd> <dt>Documentstatus:</dt>Status:</dt> <dd>Standards Track</dd> <dt>Reference:</dt><dd>(This specification)</dd><dd>RFC 9873</dd> <dt>Registrant Name and Email Address:</dt> <dd>IESG, <iesg@ietf.org></dd><dt>Top-Level Domains(TLDs):</dt><dt>TLDs:</dt> <dd>Any</dd> <dt>IPR Disclosure:</dt> <dd>None</dd> <dt>Status:</dt> <dd>Active</dd> <dt>Notes:</dt> <dd>None</dd> </dl> </section> </section> <sectionanchor="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 publication.</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 implementation 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> <sectionnumbered="true" toc="default"> <name>Security Considerations</name> <t>Asisnoted inSection 10.1Sections <xref target="RFC6530" section="10.1" sectionFormat="bare"/> andSection 13<xref target="RFC6530" section="13" sectionFormat="bare"/> of <xref target="RFC6530" format="default"/>, unconstrained Unicode in email addresses can introduce a class of security threats that do not exist with all-ASCII email addresses. As EPP exists in ecosystems where email addresses passed in EPP are displayed inRDAPthe Registration Data Access Protocol (RDAP) and other services, and copy-and-paste of these email addresses is common for businesses transferring domains via EPP, there should be safeguards against these threats. Therefore, use of the SMTPUTF8 email addresses as described in this document <bcp14>SHOULD</bcp14> be done with policies that disallow the use of unconstrained 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 addresses <bcp14>SHOULD</bcp14> be restricted to Unicode that does not introduce the threats noted in <xref target="RFC6530" format="default"/>. One such possible solution would be to disallow characters outside of Unicode Annex 31 <xref target="Unicode-UAX31" format="default"/>.</t> <!-- [rfced] May we revise "of the code points allowed by IDNA Rules and Derived Property Values" in one of the following ways? Original: 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,andan invalid email address may put communication with the end user at risk when such contact is necessary. In case of an invalid domain name in the emailaddressaddress, a malicious actor can register a valid domain name with a similar U-label (homograph attack) and assume control over the domain name associated with the contact using social engineering techniques. To reduce the risk of the use of invalid domain names in email addresses, registries <bcp14>SHOULD</bcp14> validate the domain name syntax in the provided email addresses and validate whether the domain name consists of the code points allowed by <ereftarget="https://www.iana.org/assignments/idna-tables">IDNAtarget="https://www.iana.org/assignments/idna-tables">"IDNA Rules and Derived PropertyValues</eref>.</t>Values"</eref>.</t> <t>Note that the syntax for internationalized email localparts is very liberal. Domains are normalized during MX lookup, while localparts are unconstrained. 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 three code points, see <xref target="RFC5198"format="default"/> Section 3.</t>section="3" sectionFormat="comma"/>.</t> </section> <section numbered="true" toc="default"> <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 addresses 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 numbered="true" toc="default"> <name>Acknowledgments</name> <t>The authors would</middle> <back> <!-- [rfced] Would you like the references tothank 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 forbe alphabetized or left in theircareful review and valuable comments.</t> </section> </middle> <back>current order? --> <references> <name>References</name> <references> <name>Normative References</name>&RFC2119; &RFC3688; &RFC5321; &RFC5322; &RFC5730; &RFC5733; &RFC5890; &RFC6530; &RFC6531; &RFC6532; &RFC8174; &W3C.xmlschema-1; &W3C.xmlschema-2;<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5321.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5322.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5730.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5733.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5890.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6530.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6531.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6532.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <reference anchor="W3C.REC-xmlschema-1-20041028" target="https://www.w3.org/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.org/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> <name>Informative References</name>&RFC5198; &RFC7451; &RFC7942; <referencegroup anchor="STD95" target="https://www.rfc-editor.org/info/std95"> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7480.xml"/><xi:includehref="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7481.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5198.xml"/> <xi:includehref="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9082.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7451.xml"/> <xi:includehref="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9083.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9224.xml"/> </referencegroup>href="https://bib.ietf.org/public/rfc/bibxml9/reference.STD.0095.xml"/> <reference anchor="Unicode-UAX31"target="https://unicode.org/reports/tr31/">target="https://www.unicode.org/reports/tr31/tr31-41.html"> <front> <title>UnicodeStandard Annex #31: UnicodeIdentifiers and Syntax</title><author> <organization>The Unicode Consortium</organization> </author><author fullname="Mark Davis" role="editor"/> <author fullname="Robin Leroy" role="editor"/> <date month="September" year="2024"/> </front> <refcontent>Version 16.0.0</refcontent> <seriesInfo name="Unicode Standard Annex" value="#31"/> <annotation>Latest version available at <eref brackets="angle" target="https://www.unicode.org/reports/tr31/"/>.</annotation> </reference> </references> </references> <sectionnumbered="true" toc="default" removeInRFC="true"> <name>Change History</name> <section anchor="change-00-to-01" numbered="true"numbered="false" toc="default"><name>Change from 00 to 01</name> <ol spacing="normal" type="1"> <li>Changed from update of RFC 5733<name>Acknowledgments</name> <t>The authors would like touse the "Placeholder Textthank <contact fullname="Alexander Mayrhofer"/>, <contact fullname="Chris Lonvick"/>, <contact fullname="Gustavo Lozano"/>, <contact fullname="Jody Kolker"/>, <contact fullname="John C. Klensin"/>, <contact fullname="John Levine"/>, <contact fullname="Klaus Malorny"/>, <contact fullname="Marc Blanchet"/>, <contact fullname="Marco Schrieck"/>, <contact fullname="Mario Loffredo"/>, <contact fullname="Murray S. Kucherawy"/>, <contact fullname="Patrick Mevzek"/>, <contact fullname="Pete Resnick"/>, <contact fullname="Takahiro Nemoto"/>, <contact fullname="Taras Heichenko"/>, <contact fullname="Arnt Gulbrandsen"/>, <contact fullname="Thomas Corte"/>, <contact fullname="Gavin Brown"/>, and <contact fullname="Andrew Newton"/> for their careful review anda New Email Element" EPP Extension approach.</li> </ol>valuable comments.</t> </section><section anchor="change-01-to-02" numbered="true" toc="default"> <name>Change from 01 to 02</name> <ol spacing="normal" type="1"> <li>Fixed the XML schema and the XML examples based on validating them.</li> <li>Added James Gould as co-author.</li> <li>Updated the language to apply to any EPP object mapping and to use</back> <!-- [rfced] We note inconsistencies in theEPP contact mapping as an example.</li> <li>Updatedterms below throughout thestructure of document totext. Should these beconsistent with the other Command-Response Extensions.</li> <li>Replaced the use of "eppEAI" in the XML namespaceuniform? If so, please let us know which form is preferred. command-response extension command andthe XML namespace 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 Extension.</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 toresponse extension local-part localpart ASCII alternate emailsyntax 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 fromaddress alternate ASCII email address all-ASCII ASCII-only --> <!-- [rfced] FYI - We have added expansions for theregext 02 to regext 03 version</name> <ol spacing="normal" type="1"> <li>Changed to use a pointed XML namespace with "0.3" insteadfollowing abbreviation(s) per Section 3.6 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 toRFC7451 is moved to Informative.</li> <li>IPR information is provided</li> <li>Sections are reordered to align with the other regext documents</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 nitpicking7322 ("RFC Style Guide"). Please review each expansion in thesecurity 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 13document carefully toregext 14 version</name> <ol spacing="normal" type="1"> <li>Document updated according the IANAensure correctness. Registration Data Access Protocol (RDAP) --> <!-- [rfced] Please review#1231866.</li> </ol> </section> <section anchor="change-ietf-14-to-ietf-15" numbered="true" toc="default"> <name>Change fromtheregext 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"Inclusive Language" portion of theconceptonline Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> and let us know if any changes are needed. Updates ofa functional extension and 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 instead, 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 approachthis nature typically result 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 Klensin.</li> <li>Revised the Security Considerations section based on feedback and text from 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 supportmore precise language, which is helpful forone or tworeaders. For example, please consider whether "natively" should be updated: Original: The Extensible Provisioning Protocol (EPP) does not natively support internationalized email addressesusing either ASCII or SMTPUTF8 and remove any reference tobecause therequirementspecifications foran ASCII email 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 ASCII-only or SMTPUTF8 addresses in the extension.</li> <li>Replaced "eai" with "addlEmail" in the extension-identifying URNs and schema 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 SMTPUTF8these addressesto an additional email address that can be either an SMTPUTF8 address or an all-ASCII 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 indid not exist when theIntroduction. ThisEPP wasinadvertently 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> </back>developed. --> </rfc>