idnits 2.17.1 draft-belyavskiy-epp-eai-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The draft header indicates that this document updates RFC5733, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 7, 2020) is 1287 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 179 Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Belyavskiy 3 Internet-Draft TCINET 4 Updates: 5733 (if approved) October 7, 2020 5 Intended status: Standards Track 6 Expires: April 10, 2021 8 Use of Internationalized Email Addresses in EPP protocol 9 draft-belyavskiy-epp-eai-00 11 Abstract 13 This document permits usage of Internationalized Email Addresses in 14 the EPP protocol. 16 TO BE REMOVED on turning to RFC: The document is edited in the 17 dedicated github repo [1]. Please send your submissions via GitHub. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 10, 2021. 36 Copyright Notice 38 Copyright (c) 2020 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Updates to RFC 5733 . . . . . . . . . . . . . . . . . . . . . 3 56 2.1. Changes to Email Address specification . . . . . . . . . 3 57 2.2. Changes to Email Address XML schema . . . . . . . . . . . 3 58 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 60 5. Implementation Considerations . . . . . . . . . . . . . . . . 3 61 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 6.1. Normative References . . . . . . . . . . . . . . . . . . 3 63 6.2. Informative References . . . . . . . . . . . . . . . . . 4 64 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 The updates to RFC 5730 [RFC5730]described in this document provide 70 alignment with the 2008 specification for Internationalized Email 71 Addresses (EAI) and add support for internationalized email addresses 72 in EPP protocol. 74 RFC 6530 [RFC6530] introduced the framework for Internationalized 75 Email Addresses. To make such addresses more widely accepted, the 76 changes to various protocols need to be introduced. 78 The Extensible Provisioning Protocol (EPP) specified in RFC 5730 79 [RFC5730] is a base document for object management operations and an 80 extensible framework that maps protocol operations to objects. The 81 specifics of various objects managed via EPP is described in separate 82 documents, RFC 5731 [RFC5731], RFC 5732 [RFC5732], RFC 5733 83 [RFC5733], and RFC 5734 [RFC5734]. 85 RFC 5733 [RFC5733] describes an Extensible Provisioning Protocol 86 (EPP) mapping for the provisioning and management of individual or 87 organizational social information identifiers (known as "contacts") 88 stored in a shared central repository. This document is the only one 89 refering to Email address as a property of a managed object. 91 1.1. Terminology 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 95 "OPTIONAL" in this document are to be interpreted as described in BCP 96 14 [RFC2119] [RFC8174] when, and only when, they appear in all 97 capitals, as shown here. 99 2. Updates to RFC 5733 101 2.1. Changes to Email Address specification 103 Email address is specified in RFC 5733, section 2.6. The reference 104 to the RFC 5322 [RFC5322] is replaced by a reference to RFC 6530. 106 2.2. Changes to Email Address XML schema 108 The element named 'email' in XML schemas should get the type 109 normalizedString instead of eppcom:minTokenType in terms of RFC 5733. 111 3. Security Considerations 113 Registries SHOULD validate the validity of the domain names in the 114 provided email addresses. This can be done by validating all code 115 points according to IDNA2008 [RFC5892]. 117 4. IANA Considerations 119 This document has no IANA actions. 121 5. Implementation Considerations 123 Registries MAY apply extra limitation to the email address syntax 124 (e.g. the addresses can be limited to Left-to-Right scripts). These 125 limitations are out of scope of this document. 127 6. References 129 6.1. Normative References 131 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 132 Requirement Levels", BCP 14, RFC 2119, 133 DOI 10.17487/RFC2119, March 1997, 134 . 136 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 137 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 138 August 2009, . 140 [RFC6530] Klensin, J. and Y. Ko, "Overview and Framework for 141 Internationalized Email", RFC 6530, DOI 10.17487/RFC6530, 142 February 2012, . 144 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 145 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 146 May 2017, . 148 6.2. Informative References 150 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 151 DOI 10.17487/RFC5322, October 2008, 152 . 154 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 155 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 156 . 158 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 159 Domain Name Mapping", STD 69, RFC 5731, 160 DOI 10.17487/RFC5731, August 2009, 161 . 163 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 164 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 165 August 2009, . 167 [RFC5734] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 168 Transport over TCP", STD 69, RFC 5734, 169 DOI 10.17487/RFC5734, August 2009, 170 . 172 [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and 173 Internationalized Domain Names for Applications (IDNA)", 174 RFC 5892, DOI 10.17487/RFC5892, August 2010, 175 . 177 6.3. URIs 179 [1] https://github.com/beldmit/eppeai 181 Author's Address 183 Dmitry Belyavskiy 184 TCINET 185 8 marta st 186 Moscow 187 Russian Federation 189 Phone: +7 916 262 5593 190 Email: beldmit@gmail.com