Regarding single Unicode code-point labels at the TLD level, there was quite
some discussion on this topic at the GNSO Reserved Names working group and
then at the new gTLD discussion. The final recommendation from the GNSO
was:
"Single and two-character U-labels on the top level and second level
- Original Message -
From: "Eric A. Hall" <[EMAIL PROTECTED]>
> Erik Nordmark wrote:
>
> > Instead of a brand new proposal I'd be more interested in finding out
> > how you can address the DNSSEC issues I pointed out in
> > draft-hall-dm-idns-00.txt
>
> The DNSSEC problem is hard, for mul
- Original Message -
From: "John Stracke" <[EMAIL PROTECTED]>
> Fine. But you were talking about the complexity on the client side. A
> UTF-8 transition would add complexity on the client, not reduce it,
> because the client would then have two cases to consider: servers that
> support
- Original Message -
From: "John Stracke" <[EMAIL PROTECTED]>
> >Again you have fallen into the common underestimation of the upgrade work
> >required for ACE to work perfectly (including display). What I see is
> that
> >applications are already having some trouble going from ASCII and
--- Original Message -
From: "John Stracke" <[EMAIL PROTECTED]>
> OK, but that's a really minor win; you're talking about *maybe* a few
> hundred extra memory-to-memory copies (for large queries/responses)--and
> they're all on the client side (a DNS server with ACE doesn't have to
> decode th
Hi John,
- Original Message -
From: "John Stracke" <[EMAIL PROTECTED]>
> >> >That is, if we start thinking about "8+ everywhere" instead of "ACE
> >> >everywhere" scenario, then how we can get there from here.
> >>
> >> Same question: if you have a non-backwards-compatible server, how do
- Original Message -
From: "James Seng" <[EMAIL PROTECTED]>
To: "Edmon Chung" <[EMAIL PROTECTED]>; "Keld Jørn Simonsen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "John Stracke" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; &l
Hi Keld,
- Original Message -
From: "Keld Jørn Simonsen" <[EMAIL PROTECTED]>
> I was amongst the most vocal proponents af a general 8-bit email
> exchange protocol, the one that emerged as ESMTP. I remember being
> at IETF in Santa Fé 1992-ish, where we discussed this, and I was the
> onl
I am not saying its going to be non-backwards compatible.
Ok, I have mentioned a possible migration path before, let me try it again
(btw, it is funny that everytime I put this out, no one really debate the
merits of it... but then a spurt of discussion on UTF8 breaksout)
1. IDNA clients
- th
I think the issue here is how we can plan a better transition than what we
have done for SMTP.
That is, if we start thinking about "8+ everywhere" instead of "ACE
everywhere" scenario, then how we can get there from here. That is the
question for the IDN group I believe.
Edmon
- Original Mess
- Original Message -
From: "John Stracke" <[EMAIL PROTECTED]>
> Provably false: well-coded applications know the limitations of domain
> names, and do not even attempt to make requests for non-ASCII names.
First of all, I disagree with the "well-coded" part because I believe a
well-coded
- Original Message -
From: "John Stracke" <[EMAIL PROTECTED]>
> That does not follow. A UTF-8 transition would take a very long time
> (your idea about "plugins" is nonsense; there is no plugin architecture
> that can solve this problem for every app--probably not even for any app),
> so
Hi Dave
You seem to be repeating my words in a slightly different "tone"
- Original Message -
From: "Dave Crocker" <[EMAIL PROTECTED]>
> the answer was that it is not happening now and we need to make a
> transition that is independent of converting to utf-8 native.
>
My answer
> >And a
e out of ACE and into UTF8 completely eventually. That is
why we cannot and should not leave it out for now.
Thoughts everyone?
Edmon
- Original Message -
> Dave Crocker wrote:
> >
> > At 09:52 PM 3/20/2002 -0500, Edmon Chung wrote:
> > >An underlying question we must ask
An underlying question we must ask ourselves from all the discussions that
have sprung up every now and then is:
Do we wish to
1. eventually move the DNS towards UTF8/16 OR
2. do we want to stay with ASCII(ACE) for the rest of our lives?
If the answer is 1. then the IDN solution should take it i
15 matches
Mail list logo
