[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[idn] Re: Alternative Solutions
- To: "Edmon" <edmon@neteka.com>
- Subject: [idn] Re: Alternative Solutions
- From: Dave Crocker <dhc@dcrocker.net>
- Date: Tue, 01 May 2001 17:43:53 -0700
- Cc: <idn@ops.ietf.org>
- Delivery-date: Tue, 01 May 2001 17:56:48 -0700
- Envelope-to: idn-data@psg.com
At 05:23 PM 5/1/2001, Edmon wrote:
>Server-side ACE - ACE transformation takes place at server end
If the transformation is done at the server, then the data travel from the
client as binary. How is that different from your second alternative?
For that matter, why bother with an ACE transformation at that point?
Please clarify.
>Protocol Extension - use extension mechanisms such as EDNS or other bit
>flagging & use UTF
This is a class, "dual-stack" operation. One stack is the original system
and the second is the new.
(By way of raising a warning flag early, one danger with this approach is
what we have seen with IPv6. Namely, people will try to add zillions of
changes and features, thereby delaying the effort by years.)
d/
----------
Dave Crocker <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking <http://www.brandenburg.com>
tel: +1.408.246.8253; fax: +1.408.273.6464