[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Re: 7 bits forever!
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
- the client does ACE and display it properly for the user
- servers (including DNS and mail and http, etc.) does NOT upgrade for
ACE. Even administration side is kept as is, allowing leakage
- IDNA clients MUST also be able to decode IDN(UTF8)/EDNS responses
2. IDN(UTF8)/EDNS DNS Server upgrade
- DNS servers will now accept both ACE (as usual) and IDN(UTF8)/EDNS
- ACE requests will yield Both an ACE response + an IDN(UTF8)/EDNS
- IDNA clients continue to send in ACE but will start to see UDNA
3. IDN(UTF8)/EDNS for clients & everywhere
- IDNA clients begin to obsolete, new versions of application software
comes with IDN(UTF8)/EDNS built in.
- In case DNS servers are not upgraded yet, clients will continue to use
the IDNA client, thereby also creating an incentive for server side to
- Other applications/servers upgrade to IDN(UTF8)/EDNS to accept UTF8
domains, administrators might continue to see ACE leakage if the client
still uses IDNA to send requests, but UDNA requests will be managed in UTF8
- Slowly but certainly, we will move towards full UTF8 because
administrators will likely want to deal with UTF8 than ACE, especially for
say those admins in China who are dealing with IDNs frequently. Added to
the urge from the user community to upgrade the server as they upgrade their
clients to IDN(UTF8)/EDNS.
----- Original Message -----
From: "John Stracke" <firstname.lastname@example.org>
Sent: Tuesday, April 02, 2002 10:08 AM
Subject: Re: [idn] Re: 7 bits forever!
> >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 you
> get people to use it?
> |John Stracke |Principal Engineer |
> |email@example.com |Incentive Systems, Inc.|
> |http://www.incentivesystems.com |My opinions are my own.|
> |Speak softly and carry an Illudium Q-32 Explosive Space |
> |Disintegrator. |