--- 1/draft-ietf-regext-epp-eai-03.txt 2021-08-30 03:13:12.685236724 -0700 +++ 2/draft-ietf-regext-epp-eai-04.txt 2021-08-30 03:13:12.713237427 -0700 @@ -1,20 +1,20 @@ Network Working Group D. Belyavskiy Internet-Draft Intended status: Standards Track J. Gould -Expires: 14 February 2022 VeriSign, Inc. - 13 August 2021 +Expires: 3 March 2022 VeriSign, Inc. + 30 August 2021 Use of Internationalized Email Addresses in the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-epp-eai-03 + draft-ietf-regext-epp-eai-04 Abstract 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. @@ -30,21 +30,21 @@ 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 14 February 2022. + This Internet-Draft will expire on 3 March 2022. Copyright Notice Copyright (c) 2021 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 @@ -76,20 +76,21 @@ 9.1. Normative References . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . 9 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 9 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 9 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 9 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 10 A.5. Change from 04 to the regext 01 version . . . . . . . . . 10 A.6. Change from the regext 01 to regext 02 version . . . . . 10 A.7. Change from the regext 02 to regext 03 version . . . . . 10 + A.8. Change from the regext 03 to regext 04 version . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 1. Introduction [RFC6530] 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 @@ -146,27 +147,27 @@ schema "token" type will fully support the use of EAI addresses, so the primary application of the EAI extension is to apply the use of [RFC6531] instead of [RFC5322] for the email address syntax. Other EPP extensions may follow the formal syntax definition using the XML schema type "eppcom:minTokenType" and the [RFC5322] format specification, where this extension applies to all EPP extensions with the same or similar definitions. The email address format is formally defined in Section 3.4.1 of [RFC5322], which only consists of printable US-ASCII characters for - both the local-part and the domain ABNF rules. In [RFC6531], the - 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. By applying the syntax rules of [RFC5322], the EPP + both the local-part and the domain ABNF rules. [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. By applying the syntax rules of [RFC5322], the EPP extensions will change from supporting only ASCII characters to - supporting Internationailzed characters both in the email address + supporting Internationalized characters both in the email address local-part and domain-part. 4. Functional Extension [RFC5730] 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 @@ -220,21 +221,21 @@ EPP session negotiated object extensions and command-response extensions. For example the element in [RFC5733] and the element in [RFC8543]. * 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 Section 3 - * Storage of email properties that supports internationalized + * Storage of email properties that support internationalized characters. * Return EAI compatible addresses for all email properties in the EPP responses. The client MUST satisfy the following obligations when THE EAI extension has been negotiated: * Provide EAI compatible addresses for all e-mail properties in the EPP session negotiated object extensions and command-response @@ -456,20 +457,24 @@ 1. Removed the concept of the placeholder value A.7. Change from the regext 02 to regext 03 version 1. Changed to use a pointed XML namespace with "0.3" instead of "0.2". 2. Some wording improvements +A.8. Change from the regext 03 to regext 04 version + + 1. Some nitpicking + Authors' Addresses Dmitry Belyavskiy 8 marta st. Moscow 127083 Russian Federation Phone: +7 916 262 5593 Email: beldmit@gmail.com