From: Dmitry Belyavsky <beld...@gmail.com> Sent: Monday, October 19, 2020 4:12 PM To: Hollenbeck, Scott <shollenb...@verisign.com> Cc: Gould, James <jgo...@verisign.com>; jo...@taugh.com; regext@ietf.org Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP
On Mon, Oct 19, 2020 at 10:03 PM Hollenbeck, Scott <shollenbeck=40verisign....@dmarc.ietf.org<mailto:40verisign....@dmarc.ietf.org>> wrote: > -----Original Message----- > From: regext <regext-boun...@ietf.org<mailto:regext-boun...@ietf.org>> On Behalf Of Gould, James > Sent: Monday, October 19, 2020 2:50 PM > To: jo...@taugh.com<mailto:jo...@taugh.com>; regext@ietf.org<mailto:regext@ietf.org> > Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP > > John, > > The signal would be handled via support for an EPP extension XML > namespace in option 2, an operational practice XML namespace in what I > would call 2b, or most likely a new contact XML namespace (contact-1.1) in > option 1 for RFC 5733. The XML namespace would be reflected in the EPP > greeting services and login services. I'm more a fan of using an extension with a new namespace than I am a fan of trying to update 5733. An extension would be more easily consumed by other extensions that use email addresses vs. having to also update all existing extensions that use email addresses. Adding support of an extension is harder than just allowing EAI email addresses, both for registries and registrars. Also, we get some fuzziness on implementation level. E.g., can we set ASCII email via this extension? [SAH] I disagree on both points. Extensions are, by definition, opt-in. Registries and registrars can add support for them as they see fit. By changing the core protocol we impose a mandate for implementation. I’d rather not do that until we know that all elements of the underlying mail system (SMTP servers, mail stores, etc) support EAI email addresses. Extensions are additive, so yes, it’ll be possible to support both the legacy email addresses and the extended addresses if the extension is done properly. Scott
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
