[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] San Diego Meeting Notes
- To: idn@ops.ietf.org
- Subject: Re: [idn] San Diego Meeting Notes
- From: "D. J. Bernstein" <djb@cr.yp.to>
- Date: 24 Jan 2001 02:29:59 -0000
- Delivery-date: Tue, 23 Jan 2001 18:30:59 -0800
- Envelope-to: idn-data@psg.com
- Mail-Followup-To: idn@ops.ietf.org
Paul Hoffman / IMC writes:
> That document appears to detail the costs (but does not quantify
> "massive") for upgrading applications to any form of IDN. It does not
> differentiate the costs between upgrading to an ACE or to UTF8.
False. The web page describes in detail one ACE proposal and its costs,
and then one UTF-8 proposal and its costs. Many programs need updates
and redeployment only for ACE.
> all programs are going to need to be updated
False. The UTF-8 proposal analyzed on my web page involves redeployment
of only a few programs.
> If it has a presentation layer
Please give a clear definition of ``presentation layer,'' and explain
which of the following programs have ``presentation layers'': named;
dents; tinydns; tcpclient; telnetd; sshd; tcpd; tcpserver; fetchmail;
apache; boa; fhttpd; gn; mathopd; publicfile; roxen; thttpd; webfs; wn.
Those are some of the programs that have to be upgraded and redeployed
for ACE.
> http://www.imc.org/nameprep
Is that (1) up to date and (2) normative?
---Dan