[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [idn] Why we can go directly to UTF-8
- To: "Eric A. Hall" <ehall@ehsco.com>, <idn@ops.ietf.org>
- Subject: RE: [idn] Why we can go directly to UTF-8
- From: "Brian W. Spolarich" <briansp@walid.com>
- Date: Fri, 25 May 2001 09:00:52 -0400
- Delivery-date: Fri, 25 May 2001 06:00:36 -0700
- Envelope-to: idn-data@psg.com
| Now look, seriously, there is *no* *freakin* *way* that we can go to
| just-do-UTF-8. At the very least resolvers need to know about the
| difference between wide() and normal names, systems need $HOSTNAME calls
| that support UTF-8 encodings, etc. This is a massive undertaking.
The 'just send UTF-8' approach also ignores the normalization issues
addressed by nameprep, unless you think, as Bill Semich has suggested,
that a protocol based on nameprep only somehow makes sense and is
actually deployable.
-bws