Re: [regext] Internationalized Email Addresses and EPP

"Hollenbeck, Scott" <shollenbeck@verisign.com> Fri, 20 November 2020 11:17 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E51503A138C for <regext@ietfa.amsl.com>; Fri, 20 Nov 2020 03:17:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THuWJsmAvZgx for <regext@ietfa.amsl.com>; Fri, 20 Nov 2020 03:17:42 -0800 (PST)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 579503A1387 for <regext@ietf.org>; Fri, 20 Nov 2020 03:17:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=4275; q=dns/txt; s=VRSN; t=1605871063; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=UwlQ6SSCH1hipn+G9b92iJijnMt/cOyomnIRUX5bRXU=; b=MQCmjtD4haPR7jHvzNPT+cyRBDj/lMmTeXb6oGDsoP55a1JvA1O5PEb7 8ghID5jZ68RtDzcOcytqTE/SCKmwTYPM9XfW54sXGCwnoHSTEWZgOiipg 7DXIsMlQHwlqmSLmQiXtvCWzXtlKHVJqvl/dqIT3f8EDxjOdo4o19pGyh R/MPdBWQ9eU//cLlYRRQSxPVxPxpcTxSzhS58vTxMRE/jaoA1Gkdgs0jc w3Sq9Vobo914xLQCKjPenJuzQ+OWoOVFbvmWaoMyl8UH0Wc11poXXe2PK Txsr4IQO5irm+wJgUtevB0EgDy6FSNtUN+B5pVFrh+EGoOe9pGQgmb5hK g==;
IronPort-SDR: jNFxSU86cKCS5QHGQsQpPdI4vEPtgx+QmgVq2kiFUndMN73PRQYP/vun7z3OMe/RxqxxQ+hEmw Kt6g8STUxIpe0GSsmifgnH9j/q5oja+w9jgFFwBlWRpPyIUfpeUIAklqjO8iOHjrtezIRKpysX ONI5pU5D1gNmXMwOCxRzleJ3MRqwI0MDJ28xSqe1Nf9KlMR0O0uTfXOAQf1mmfHwo8wZWbevTH rX3IvF/bVwEGHPN4R0fqN2CgEIibom/n5pO/TEZ7UcpWL4Pv5IXm5RVaAgRJ+J03tmVuCUpOII JcM=
X-IronPort-AV: E=Sophos;i="5.78,356,1599537600"; d="scan'208";a="3825864"
IronPort-PHdr: =?us-ascii?q?9a23=3AJJzGhRWbft8cGYxaZpQZBHda7kLV8LGtZVwlr6?= =?us-ascii?q?E/grcLSJyIuqrYZRSEv6dThVPEFb/W9+hDw7KP9fy5BipZvc7K6ilKWacPfi?= =?us-ascii?q?dNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV?= =?us-ascii?q?3wOgVvO+v6BJPZgdip2OCu4Z3TZBhDiCagbb9oIxi6sAfcutMLjYZtNqo9xQ?= =?us-ascii?q?XFrmZVcOlK2G1kIk6ekQzh7cmq5p5j9CpQu/Ml98FeVKjxYro1Q79FAjk4Km?= =?us-ascii?q?45/MLkuwXNQguJ/XscT34ZkgFUDAjf7RH1RYn+vy3nvedgwiaaPMn2TbcpWT?= =?us-ascii?q?S+6qpgVRHlhDsbOzM/7WrajNF7gqBGrxK7vxFxw5DabpyJNPRwfa3dc9EVRW?= =?us-ascii?q?tdUcheWCNMGZ+8b5IND+YdIepUs5fxql0TphW+HwmsA+bvxydGinH02q061+?= =?us-ascii?q?AhHh/A3AM7Ad0BrHfUoM3oP6kPTe+1y7XIzSnNY/hL3jr984jIchclofGIQ7?= =?us-ascii?q?1wd9HexlczGAPGlViQt5LqPymU1uQWsmib4OxgWfizhG4grgF8uz6izdojhY?= =?us-ascii?q?fVnIwa0EzE9Tlnz4YvI921UFN2bN6kHZZMqSyXNZZ7T8ctTmx1tyg21rkLtY?= =?us-ascii?q?KmcCQWxpkpyQPSZv+IfoSU/h7tVOafLSt2in9ndryymRK//FSmx+bhVce0yE?= =?us-ascii?q?5HojdZntXWq3wA1RLe5tKaRvZ98EqtwzmC2gTL5u1ZPUw4j7fXJpw9zrIqi5?= =?us-ascii?q?YevkfOEjXrlEj1iqKda18q9fKy6+v9Z7XrvpqcN4hphQ7gKqkugcm/AfggMg?= =?us-ascii?q?gJQmib5fyw1L398k39R7VHluA7nLXBvpzHJcsVvqG3DA5J3oo98Rq/ESup0N?= =?us-ascii?q?MCnXkfNl5KYg+Ig5L3O1HUO/D4C+2zjEirkDdu3/zGP7vhDYvRLnXbjbvtYa?= =?us-ascii?q?xx51NexQc919xT+pJZB78bLP/8XkL9rNnYAQU4MwywzebnEtJ91oYGVGKUAq?= =?us-ascii?q?+ZN6fSsVuW6eIpOOaDepMauDXmJvg7+fHul345mUQcfamm25sbcmy3HvNjI0?= =?us-ascii?q?mBe3rjns8BEXsWvgo5VOHqlEeNUSVSZ3muRK8z/C00B5i7AojdQ4Chmr+B3C?= =?us-ascii?q?alEZ1IfGxGF0qDG2/yd4qYQ/cMdD6SIsh5nzIBUbiuUZIh1Qq0uAH90bVnKu?= =?us-ascii?q?3U+jcetZPjz9V15OvTlRAq9TxsFciSzn+CRXlunmwUXz82wLx/oUtlx1eZz6?= =?us-ascii?q?d4jOJXFNNP5/5SUwc1K4Lcz+JgB9D1QALBcYTBdFHzCMmvGjA6Zts6ytMDZg?= =?us-ascii?q?B+Gti8yA3KlWL+H7YOlrejDZc9/q/ZmXvwKtg71n+Qh4c7iFxzCOtIMWmrgK?= =?us-ascii?q?Ry/AuXT7XClFmF3e7+bqQb2CrA8m2OxmmmokxCURVxXqODVncaMBiF5e/l71?= =?us-ascii?q?/PGuf9QY8sNRFMnJaP?=
X-IPAS-Result: =?us-ascii?q?A2EZBQCUpLdf/zGZrQpiHgEBCxIMQIYjCpVdlQGFRYFoC?= =?us-ascii?q?wEBAQEBAQEBAQgBLwQBAYFVgnUCgi0mOBMCAwEBCwEBAQUBAQEBAQYDAQEBA?= =?us-ascii?q?oZPC4I3IoN2AQEBAQM6PwwEAgEIEQQBAQEeEDIdCAIEDgUIsgg8dIE0hVeEf?= =?us-ascii?q?IE4jVuBQj6BEYMSPoJdBIEeCgESAYYXBJAlE415iAQtkVgDB4JumC2CZSuDG?= =?us-ascii?q?ooXiF6LbpNXgWUcnRuBQAIEAgQFAhWBa4ELcHCDOVAXAg2OKxeNcTV0AjUCB?= =?us-ascii?q?goBAQMJjTeBEQEB?=
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 20 Nov 2020 06:17:40 -0500
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde]) by BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde%4]) with mapi id 15.01.2106.002; Fri, 20 Nov 2020 06:17:40 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "tasic@academ.kiev.ua" <tasic@academ.kiev.ua>
CC: "Klaus.Malorny@knipp.de" <Klaus.Malorny@knipp.de>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP
Thread-Index: AQHWvxnQ5sxORJ+3oEukC7gtsimNhqnQukmAgAB3poD//6zWgA==
Date: Fri, 20 Nov 2020 11:17:40 +0000
Message-ID: <cf4727d834a340ca98226b3785ce7b19@verisign.com>
References: <AB832A1D-083B-40E4-9F45-B03DB7452B70@verisign.com> <a5446f92-2250-d1e6-16f5-7fdffc48a9c8@knipp.de> <08e72da8ecc745cb8a6c4338566ff0c6@verisign.com> <6EBBAF72-6CFC-4295-A453-66BA1403919D@academ.kiev.ua>
In-Reply-To: <6EBBAF72-6CFC-4295-A453-66BA1403919D@academ.kiev.ua>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/KTYb_HUAOP8llv3kJ9ufom1dUzM>
Subject: Re: [regext] Internationalized Email Addresses and EPP
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2020 11:17:44 -0000

> -----Original Message-----
> From: Taras Heichenko <tasic@academ.kiev.ua>
> Sent: Friday, November 20, 2020 6:13 AM
> To: Hollenbeck, Scott <shollenbeck@verisign.com>
> Cc: Klaus.Malorny@knipp.de; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP
>
> Caution: This email originated from outside the organization. Do not click links
> or open attachments unless you recognize the sender and know the content
> is safe.
>
>
> > On 20 Nov 2020, at 11:06, Hollenbeck, Scott
> <shollenbeck=40verisign.com@dmarc.ietf.org> wrote:
> >
> >> -----Original Message-----
> >> From: regext <regext-bounces@ietf.org> On Behalf Of Klaus Malorny
> >> Sent: Friday, November 20, 2020 3:47 AM
> >> To: regext@ietf.org
> >> Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses
> >> and EPP
> >>
> >> Caution: This email originated from outside the organization. Do not
> >> click links or open attachments unless you recognize the sender and
> >> know the content is safe.
> >>
> >> On 19.11.20 19:14, Gould, James wrote:
> >>> Klaus,
> >>>
> >>> The EAI support goes beyond RFC 5733 and is a perfect example of the
> >>> use
> >> of the extensibility built into EPP.  Revising the RFCs and EPP
> >> extensions that use email addresses for EAI with new XML namespaces
> >> and potentially other changes is much more impactful than creating an
> >> EPP extension that specifically addresses the issue with
> >> applicability across any EPP object.  I was involved with revising
> >> RFC 4310 to RFC 5910, which was needed to address significant
> >> implementation issues with RFC 4310, so I see it as a different use
> >> case.  The intent is to make the EPP extension as lightweight as
> >> possible, to apply across multiple EPP objects, and to include an
> >> appropriate level of signaling (e.g., session-level, object-level, element-
> level).  Any feedback is welcome.
> >>>
> >>> Thanks,
> >>>
> >>
> >> Hi James,
> >>
> >> I chose DNSSEC as an example as I know that you took the major part
> >> in writing the update. At the very end, it is a matter of taste, and
> >> one cannot argue about. So I respect your position.
> >>
> >> As you might know, my company is developing software both for the
> >> registry side (our TANGO software) and for the registrar side (for
> >> customers and our own purpose). And for the latter, dealing with all
> >> the slightly different implementations of the EPP, within the limits
> >> of the specifications and beyond, and dealing with the flood of
> >> extensions, including different versions of them, is really anything but
> fun.
> >>
> >> As I understand it, the original idea of EPP was to have a common
> >> protocol for all registries, and it "failed by the wayside"
> >> (hopefully the right idiom). It is not about blaming anyone for this,
> >> maybe the idea was just too ambitious. So IMHO with every proposed
> >> change to the EPP ecosystem one should ask oneself whether it
> >> increases or decreases the overall complexity and the need for case
> >> differentiation, specifically in the long run. I do not remember who
> >> said this, but there is a proverb which goes like the following: If
> >> you design a protocol, don't ask what you can add to it, but what you can
> remove from it. While this is likely idealistic, I'll try to keep this in my mind.
> >>
> >> Coming back to the issue, I see internationalized e-mail addresses
> >> coming to stay, like IPv6 did and IDN. So make it an integral part of
> >> the protocol, not an optional one, in the long run. But hey, that's only my
> taste.
> >
> > Please keep in mind that they're currently an OPTIONAL SMTP extension. I
> think that would need to change before they become a MUST for EPP.
>
> I fully agree with Klaus, the proposed extension increases the protocol
> complexity, adds a lot of job to the EPP software developers, and what it
> gives back? Less work with the RFCs? Do you really think it is a valuable
> exchange? And in a new RFC, support of non-ASCII email addresses may be
> optional.

Sorry, but an extension is a whole lot less complex than changing the core protocol.

Scott