Re: [regext] Internationalized Email Addresses and EPP
Dmitry Belyavsky <beldmit@gmail.com> Fri, 20 November 2020 11:34 UTC
Return-Path: <beldmit@gmail.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 16B353A1C45 for <regext@ietfa.amsl.com>; Fri, 20 Nov 2020 03:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3Le5FdiYQjN5 for <regext@ietfa.amsl.com>; Fri, 20 Nov 2020 03:34:34 -0800 (PST)
Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D68743A1730 for <regext@ietf.org>; Fri, 20 Nov 2020 03:34:33 -0800 (PST)
Received: by mail-ej1-x634.google.com with SMTP id a16so12427049ejj.5 for <regext@ietf.org>; Fri, 20 Nov 2020 03:34:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J78JMKNfQDyUq01R+QNwUgMgZS7qb/JIQVdIdaXN9xQ=; b=L2M6zMJF5bvzd9/ffRqAqraei/O9MEovoKBP4NNEUTuiuVfVNCKgkje/1RkYq7Awob qkk2gkBdjdJ2VVVHY32iygSmKqhAQfjroqGMi/frILhmYRlehruktRBr3IBu/tmuUTqU iESIofQrAMrj8WUaZ1QNUGjuPkTQUPDWyIcaSIrx+MrMGVbieIcqEURQD23jOVMPPje5 /ekrrqNweRrW8gwt2e2fW4yQK4UbUW7wu66WIz0up1qOAC8hTsyObj1bshgdppxieXrf sJZ30x4kIvE/VPWpL5bMHTBg6+ilVG1sWKVhpBb0TxUA+SB/X38pOKOV7wOXEht1j3o4 D4Cg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=J78JMKNfQDyUq01R+QNwUgMgZS7qb/JIQVdIdaXN9xQ=; b=YIV8Q1EkUv/qkxfmFpxBj7Hk14n604RmWLUULd9C/PQBqFzQ9BRwT6RH/zgA2aqao6 sWggdqWAQ+Fdc8dClpmjiQqbPXTXxPI9TGTxImlsE3L/gAlrSgAQ60NF+N/ZbfUYPegn StFZHauTaQdSr6ifLSj/5hgt4o8Jj2X0Y6HZFi4TBV9fgRByaT4bHEjBS65V/BACPmMS IOT5M4Pg+FUL5gAhXNzTyiQpq0otJ5A+sWQwwKlXVgxr6VBNhh/n2zzF+ELuecQtac7y CRG6t3xBxODRFmOkd1jL8yGvNqnWhWU2c+9f9j4wsk3KVpCy/d9XBruMgVYbYjqaHJIk FdmA==
X-Gm-Message-State: AOAM530/hcTZVQDzkJAQd5iMAEZSmaMJ8GLHq22cTVxenDjSwUyBvbd0 qiGfoIr1IRkqvIJgvIJjRd2QhtmW5iJHnDxVFC744yw91Sg=
X-Google-Smtp-Source: ABdhPJyzFR2SzCtbc9047Roqti7Q3/wKb5ja0TMAcV9VAag2IPr4CXAR1Bwo98gwBPlWH1ZJcV1cPehapiXRl/7g8wE=
X-Received: by 2002:a17:906:854c:: with SMTP id h12mr1255902ejy.212.1605872072041; Fri, 20 Nov 2020 03:34:32 -0800 (PST)
MIME-Version: 1.0
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> <cf4727d834a340ca98226b3785ce7b19@verisign.com>
In-Reply-To: <cf4727d834a340ca98226b3785ce7b19@verisign.com>
From: Dmitry Belyavsky <beldmit@gmail.com>
Date: Fri, 20 Nov 2020 14:34:20 +0300
Message-ID: <CADqLbz+kU9Usf-uH8DhiYpr6JHgkdRb-ickEuLe+4021K6DNLQ@mail.gmail.com>
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>
Cc: "tasic@academ.kiev.ua" <tasic@academ.kiev.ua>, "regext@ietf.org" <regext@ietf.org>, "Klaus.Malorny@knipp.de" <Klaus.Malorny@knipp.de>
Content-Type: multipart/alternative; boundary="00000000000068a87405b4883ad8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/5VkV5R9fVvzv3c0DLP2QlVQDQKw>
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:34:37 -0000
On Fri, Nov 20, 2020 at 2:17 PM Hollenbeck, Scott <shollenbeck= 40verisign.com@dmarc.ietf.org> wrote: > > -----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. > >From my *implementation* experience, the extension (as a body, not just as a marker) is more complex than relaxing the email syntax. And we anyway have a much larger volume of work when the registrar starts tuning his mail system to work with EAI... -- SY, Dmitry Belyavsky
- [regext] Internationalized Email Addresses and EPP Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Barry Leiba
- Re: [regext] Internationalized Email Addresses an… Gould, James
- Re: [regext] Internationalized Email Addresses an… Dmitry Belyavsky
- Re: [regext] Internationalized Email Addresses an… Mario Loffredo
- Re: [regext] Internationalized Email Addresses an… Gould, James
- Re: [regext] Internationalized Email Addresses an… John Levine
- Re: [regext] Internationalized Email Addresses an… Gould, James
- Re: [regext] Internationalized Email Addresses an… John Levine
- Re: [regext] Internationalized Email Addresses an… Gould, James
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Dmitry Belyavsky
- Re: [regext] Internationalized Email Addresses an… Mario Loffredo
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Jiankang Yao
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Klaus Malorny
- Re: [regext] Internationalized Email Addresses an… Gould, James
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Klaus Malorny
- Re: [regext] Internationalized Email Addresses an… Gould, James
- Re: [regext] Internationalized Email Addresses an… Klaus Malorny
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Dmitry Belyavsky
- Re: [regext] Internationalized Email Addresses an… Mario Loffredo
- Re: [regext] Internationalized Email Addresses an… Alexander Mayrhofer
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Matthias Pfeifer
- Re: [regext] Internationalized Email Addresses an… Dmitry Belyavsky
- Re: [regext] Internationalized Email Addresses an… Gould, James
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… John Levine
- Re: [regext] Internationalized Email Addresses an… Dmitry Belyavsky
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Hollenbeck, Scott
- Re: [regext] Internationalized Email Addresses an… Patrick Mevzek
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Taras Heichenko
- Re: [regext] Internationalized Email Addresses an… Gould, James