Hi,
If weâre going to stand firm on the current working group consensus,
then I believe the question to be answered is why EPP is special and
shouldnât be required to align with accepted practice?
What's accepted practice?
We have phone numbers, postal addresses and email addresses in wh
Thursday, 3 August 2023 17:48:19 CEST writes:
On Thu, Aug 3, 2023 at 10:49 AM Arnt Gulbrandsen
wrote:
Hi,
...
IMHO, it's more nuanced than that. Text-capable phones and all-ASCII
email addresses
can be verified via automated processes, and there are some regular
processes in both th
Thursday, 3 August 2023 20:14:41 CEST writes:
On Thu, Aug 3, 2023 at 1:23 PM Gould, James wrote:
So, rollback to draft-ietf-regext-epp-eai-17 with the concept
of a transition period removed and inclusion of "at least one
of the email values MUST be an ASCII address"?
Doesn't that put us ba
Hi,
I've tried a few times to write something.
I fail at writing anything involving alternate addresses. My problem is
that I think that if someone wants to use EAI and is required to supply an
ASCII alternative, then there's a decent chance that they'll forward the
ASCII alternative to their
Murray S. Kucherawy writes:
Hi Andrew,
Apologies for the delay processing this one. I'm digging my
way out of this December backlog.
I'm neither Andrew nor you, but that backlog seems familiar ;)
My plan is to get it reviewed by an I18N expert in its current
form. I'm pushing to get that
Hi,
I suggested some wording changes several months ago (new wording in
sections 3 and 6.2). It took me several tries to put together that wording,
and I quite like it: I think the database check requirement takes care of
John's worries in a practical way.
Arnt
I fail at writing anything in
Hi,
that makes sense to me. But after I sent mail earlier today, I realised
that there should perhaps be an explicit error code to say "unknown error
related to storing that address".
I'll update and send you suggested text off-list. Not sure whether the
revised text will contain any MUSTs,
Hi,
All-ASCII addresses are sort of optional in EPP already…
If you want to use 名字@例子.中国 as a contact address, all you need to do is
open to your registrar's web site, register a domain and tick the checkbox
labelled something like "keep my email address private". The registrar will
provide a
Hi,
I've attended the meetings since Prague but am not an EPP person. Permit me
to offer a different perspective, based on what you've been saying about
the other topics of discussion.
When you've talked about EPP during those meetings, you talked about the
data model, the commands, but you
I want to digress on one point here.
John C Klensin writes:
(1) As you know, I personally favor the idea that, if non-ASCII email
addresses are to be used in a global context, all-ASCII alternatives
should be available.
This sounds so plausible, but it hinges on that global context.
There's i
James Galvin writes:
https://datatracker.ietf.org/doc/draft-ietf-regext-epp-eai/22/
Please also take this message as a reminder to indicate your
support or any question or concerns you might have.
Since I've been critical about some aspects of older revisions, I'll just
state for the record
Hollenbeck, Scott writes:
Please note that I have a comment from Joseph Yee that needs to
be addressed if there's no objection to do so.
Why does it need to be addressed?
EPP doesn't even try to tell you that a contact object will be invalidated
if the domain is transferred, or that a contact
12 matches
Mail list logo
