8 marta st. Moscow 127083 Russian Federation +7 916 262 5593 beldmit@gmail.com

VeriSign, Inc.

12061 Bluemont Way Reston VA 20190 US jgould@verisign.com http://www.verisigninc.com

This document describes an EPP extension that permits usage of Internationalized Email Addresses in the EPP protocol and specifies the terms when it can be used by EPP clients and servers. The Extensible Provisioning Protocol (EPP), being developed before appearing the standards for Internationalized Email Addresses (EAI), does not support such email addresses. TO BE REMOVED on turning to RFC: The document is edited in the dedicated github repo. Please send your submissions via GitHub.

Introduction introduced the framework for Internationalized Email Addresses. To make such addresses more widely accepted, the changes to various protocols need to be introduced. This document describes an Extensible Provisioning Protocol (EPP) extension that permits usage of Internationalized Email Addresses in the EPP protocol and specifies the terms when it can be used by EPP clients and servers. A new form of EPP extension, referred to as a Functional Extension, is defined and used to apply the rules for the handling of email address elements in all of the extensions negotiated in the EPP session, which include the object and command-responses extensions. The described mechanism can be applied to any object or command-response extension that uses an email address, where the EPP contact mapping is used in the examples. The Extensible Provisioning Protocol (EPP) specified in is a base document for object management operations and an extensible framework that maps protocol operations to objects. The specifics of various objects managed via EPP is described in separate documents. This document is only referring to an email address as a property of a managed object, such as the <contact:email> element in the EPP contact mapping or the <org:email> element in the EPP organization mapping, and command-response extensions applied to a managed object.

Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. "eai-0.2" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:eai-0.2". The XML namespace prefix "eai" is used, but implementations MUST NOT depend on it. Instead, they are to employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.

Migrating to Newer Versions of This Extension Servers that implement this extension SHOULD provide a way for clients to progressively update their implementations when a new version of the extension is deployed. A newer version of the extension is expected to use an XML namespace with a higher version number than the prior versions.

Email Address Specification Support of non-ASCII email address syntax is defined in RFC 6530. This mapping does not prescribe minimum or maximum lengths for character strings used to represent email addresses. The exact syntax of such addresses is described in section 3.3. The validation rules introduced in RFC 6531 are considered to be followed.

Functional Extension defines three types of extensions at the protocol, object, and command-response level, which impact the structure of the EPP messages. A Functional Extension applies a functional capability to an existing set of EPP extensions and properties. The scope of the applicable EPP extensions and applicable extension properties are defined in the Functional Extension along with the requirements for the servers and clients that support it. The Functional Extension needs to cover the expected behavior of the supporting client or server when interfacing with an unsupporting client or server. Negotiating support for a Functional Extension is handled using the EPP Greeting and EPP Login services.

Internationalized Email Addresses (EAI) Functional Extension

Scope of Functional Extension The functional extension applies to all object extensions and command-response extensions negotiated in the EPP session that include email address properties. Examples include the <contact:email> element in the EPP contact mapping or the <org:email> element in the EPP organization mapping. All registry zones (e.g., top-level domains) authorized for the client in the EPP session apply. There is no concept of a per-client, per-zone, per-extension, or per-field setting that is used to indicate support for EAI, but instead it's a global setting that applies to the EPP session.

Signaling Client and Server Support The client and the server can signal support for the functional extension using a namespace URI in the login and greeting extension services. The namespace URI "eai-0.2" is used to signal support for the functional extension. The client includes the namespace URI in an <svcExtension> <extURI> element of the <login> Command. The server includes the namespace URI in an <svcExtension> <extURI> element of the Greeting.

Functional Extension Behavior

EAI Functional Extension Negotiated If both client and server have indicated the support of the EAI addresses during the session establishment, it implies possibility to process the EAI address in any message having an email property during the established EPP session. Below are the server and client obligations when the EAI extension has been successfuly negotiated in the EPP session. The server MUST satisfy the following obligations when THE EAI extension has been negotiated:

• Accept EAI compatible addresses for all email properties in the EPP session negotiated object extensions and command-response extensions. For example the <contact:email> element in and the <org:email> element in .
• Accept EAI compatible addresses for all registry zones (e.g., top-level domains) authorized for the client in the EPP session.
• Email address validation based on EAI validation rules defined in
• Storage of email properties that supports internationalized characters.
• Return EAI compatible addresses for all email properties in the EPP responses.

The server MUST satisfy the following obligations when THE EAI extension has been negotiated:

• Provide EAI compatible addresses for all e-mail attribute fields in the EPP session negotiated object extensions and command-response extensions. For example the <contact:email> element in and the <org:email> element in .
• Provide EAI compatible addresses for all registry zones (e.g., top-level domains) authorized for the client in the EPP session.
• Accept EAI compatible addresses in the EPP responses for all email properties in the EPP session negotiated object extensions and command-response extensions.

EAI Functional Extension Not Negotiated The lack of EAI support can cause data and functional issues, so an EAI supporting client or server needs to handle cases where the opposite party doesn't support EAI. Below are the server and client obligations when the EAI extension is not negotiated due to either lack of support by the opposite party. The EAI supporting server MUST satisfy the following obligations when the client does not support the EAI extension:

• When the email property is required in the EPP extension command, the server SHOULD validate the email property by the client using the ASCII email validation rules.
• When the email property is optional according the EPP extension command, if the client supplies the email property the server SHOULD validate the email property using the ASCII email validation rules.
• When the email property is required in the EPP extension response, the server MUST validate whether the email property is an EAI address and if so return the predefined placeholder email TBD and otherwise return the email property that has been set.
• When the email property is optional in the EPP extension response, the server MUST validate whether the email property is an EAI address and if so don't return the email property in the response and otherwise return the email property that has been set based on server policy.

The EAI supporting client MUST satisfy the following obligations when the server does not support the EAI extension:

• When the email property is required in the EPP extension command and the email property is an EAI address with no alternative ASCII address, the client MUST provide the predefined placeholder email address TBD.
• When the email property is optional in the EPP extension command and the email property is an EAI address with no alternative ASCII address, the client SHOULD omit the email property.

Security Considerations Registries SHOULD validate the domain names in the provided email addresses. This can be done by validating all code points according to IDNA2008 .

IANA Considerations

XML Namespace This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in RFC 3688. The following URI assignment should be made by IANA: Registration request for the eai namespace:

EPP Extension Registry The EPP extension described in this document should be registered by IANA in the "Extensions for the Extensible Provisioning Protocol (EPP)" registry described in RFC 7451 . The details of the registration are as follows: Top-Level Domains(TLDs): Any IPR Disclosure: None Status: Active Notes: None ]]>

Implementation Considerations Registries MAY apply extra limitation to the email address syntax (e.g. the addresses can be limited to Left-to-Right scripts). These limitations are out of scope of this document.

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. The Extensible Provisioning Protocol (EPP) is an application layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document presents guidelines for use of EPP's extension mechanisms to define new features and object management capabilities. This memo provides information for the Internet community. This document describes an application-layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. This document obsoletes RFC 4930. [STANDARDS-TRACK] This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts. This document obsoletes RFC 4933. [STANDARDS-TRACK] Full use of electronic mail throughout the world requires that (subject to other constraints) people be able to use close variations on their own names (written correctly in their own languages and scripts) as mailbox names in email addresses. This document introduces a series of specifications that define mechanisms and protocol extensions needed to fully support internationalized email addresses. These changes include an SMTP extension and extension of email header syntax to accommodate UTF-8 data. The document set also includes discussion of key assumptions and issues in deploying fully internationalized email. This document is a replacement for RFC 4952; it reflects additional issues identified since that document was published. [STANDARDS-TRACK] This document specifies an SMTP extension for transport and delivery of email messages with internationalized email addresses or header information. [STANDARDS-TRACK] The Extensible Provisioning Protocol (EPP) includes features to add functionality by extending the protocol. It does not, however, describe how those extensions are managed. This document describes a procedure for the registration and management of extensions to EPP, and it specifies a format for an IANA registry to record those extensions. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). [STANDARDS-TRACK] This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning and management of organization objects stored in a shared central repository.

Change History

Change from 00 to 01

1. Changed from update of RFC 5733 to use the "Placeholder Text and a New Email Element" EPP Extension approach.

Change from 01 to 02

1. Fixed the XML schema and the XML examples based on validating them.
2. Added James Gould as co-author.
3. Updated the language to apply to any EPP object mapping and to use the EPP contact mapping as an example.
4. Updated the structure of document to be consistent with the other Command-Response Extensions.
5. Replaced the use of "eppEAI" in the XML namespace and the XML namespace prefix with "eai".
6. Changed to use a pointed XML namespace with "0.2" instead of "1.0".

Change from 02 to 03

1. The approach has changed to use the concept of Functional EPP Extension.
2. The examples are removed