Network Working Group D. Belyavskiy Internet-Draft TCINET Updates: 5733 (if approved) October 7, 2020 Intended status: Standards Track Expires: April 10, 2021 Use of Internationalized Email Addresses in EPP protocol draft-belyavskiy-epp-eai-00 Abstract This document permits usage of Internationalized Email Addresses in the EPP protocol. TO BE REMOVED on turning to RFC: The document is edited in the dedicated github repo [1]. Please send your submissions via GitHub. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on April 10, 2021. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Belyavskiy Expires April 10, 2021 [Page 1] Internet-Draft Use of EAI in EPP October 2020 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 2. Updates to RFC 5733 . . . . . . . . . . . . . . . . . . . . . 3 2.1. Changes to Email Address specification . . . . . . . . . 3 2.2. Changes to Email Address XML schema . . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 5. Implementation Considerations . . . . . . . . . . . . . . . . 3 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 6.1. Normative References . . . . . . . . . . . . . . . . . . 3 6.2. Informative References . . . . . . . . . . . . . . . . . 4 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction The updates to RFC 5730 [RFC5730]described in this document provide alignment with the 2008 specification for Internationalized Email Addresses (EAI) and add support for internationalized email addresses in EPP protocol. RFC 6530 [RFC6530] introduced the framework for Internationalized Email Addresses. To make such addresses more widely accepted, the changes to various protocols need to be introduced. The Extensible Provisioning Protocol (EPP) specified in RFC 5730 [RFC5730] 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, RFC 5731 [RFC5731], RFC 5732 [RFC5732], RFC 5733 [RFC5733], and RFC 5734 [RFC5734]. RFC 5733 [RFC5733] 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. This document is the only one refering to Email address as a property of a managed object. 1.1. Terminology 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 Belyavskiy Expires April 10, 2021 [Page 2] Internet-Draft Use of EAI in EPP October 2020 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. Updates to RFC 5733 2.1. Changes to Email Address specification Email address is specified in RFC 5733, section 2.6. The reference to the RFC 5322 [RFC5322] is replaced by a reference to RFC 6530. 2.2. Changes to Email Address XML schema The element named 'email' in XML schemas should get the type normalizedString instead of eppcom:minTokenType in terms of RFC 5733. 3. Security Considerations Registries SHOULD validate the validity of the domain names in the provided email addresses. This can be done by validating all code points according to IDNA2008 [RFC5892]. 4. IANA Considerations This document has no IANA actions. 5. 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. 6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, August 2009, . [RFC6530] Klensin, J. and Y. Ko, "Overview and Framework for Internationalized Email", RFC 6530, DOI 10.17487/RFC6530, February 2012, . Belyavskiy Expires April 10, 2021 [Page 3] Internet-Draft Use of EAI in EPP October 2020 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 6.2. Informative References [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, DOI 10.17487/RFC5322, October 2008, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, . [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, August 2009, . [RFC5734] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Transport over TCP", STD 69, RFC 5734, DOI 10.17487/RFC5734, August 2009, . [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)", RFC 5892, DOI 10.17487/RFC5892, August 2010, . 6.3. URIs [1] https://github.com/beldmit/eppeai Author's Address Dmitry Belyavskiy TCINET 8 marta st Moscow Russian Federation Phone: +7 916 262 5593 Email: beldmit@gmail.com Belyavskiy Expires April 10, 2021 [Page 4]