Hello all,
Otion 1 is ideal and option 2 are reasonable.
Since not many registries and registrars support EAI services and few
registrants use EAI address in the near future, I think that option 2 might be
the current direction.
Best Regards
Jiankang Yao
From: Barry Leiba
Date: 2020-10-19 17:48
To: Hollenbeck, Scott
CC: art-...@ietf.org; regext@ietf.org
Subject: Re: [regext] Internationalized Email Addresses and EPP
Hi, Scott,
An interesting question...
I think it depends upon how you want this to appear from an EPP point of view:
1. Do you want the EPP standard to support non-ASCII email addresses?
2. Do you want to *extend* EPP to support non-ASCII email addresses,
as an option for those who implement the extension?
For (2), then the EPP extension would be the easiest option, where the
extension would "update" 5733 and say that the extension changes the
definition to allow non-ASCII email addresses. The extension would be
at Proposed Standard, and 5733 would be at Internet Standard as it is
now.
For (1), the best way would be to revise 5733 and change the
definition of email address syntax, republishing it at Proposed
Standard and "obsolete" 5733. The protocol (the new RFC) would then
be back at Proposed Standard. You could then do a status change later
to move the new RFC to Internet Standard (without publishing yet
another revision).
So... does the working group want it to appear that support for
non-ASCII email addresses is an optional extension, or part of the
base EPP?
Barry
On Wed, Oct 14, 2020 at 7:54 AM Hollenbeck, Scott
<shollenb...@verisign.com> wrote:
>
> Barry, Murray:
>
> We have a question about IETF process as it related to updating an Internet
> Standard document. RFC 5733 ("Extensible Provisioning Protocol (EPP) Contact
> Mapping", part of Standard 69) was published in August 2009. It includes a
> normative reference to RFC 5322 for the definition of email address syntax.
> RFC 6530 ("Overview and Framework for Internationalized Email") was published
> in 2012. The regext working group is discussing how we can best update the
> email address syntax specification in RFC 5733 to add support for the local
> part of internationalized email addresses to EPP. The EPP XML Schema already
> "works" as it should, so that doesn't need to change. It's just that pesky
> normative reference to RFC 5322 that isn't updated by RFC 6530. We think we
> have a couple of options:
>
> Create an EPP extension by writing an Internet-Draft that would explicitly
> add support for internationalized email address without touching anything
> associated with 5733.
>
> Write another document that updates 5733 to include the reference to 6530, if
> it's possible to update an Internet Standard that way.
>
> Submit an errata report to note the additional normative reference to 6530,
> though this isn't a technical or editorial error.
>
> There may be other possibilities. What are your thoughts on the best way to
> proceed? I personally think that the first option is the easiest and
> cleanest, and it's the way we've added additional functionality in the past.
> I'm wondering if there's an easier way, though.
>
> Scott
>
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
