Re: [idn] universal typability

["Eugene M. Kim" <ab@astralblue.com>]

One semi-random question: it seems almost certain that we must consider
about this typeability, but at which level should it be defined?  My
guess is to define a BCP for a transfer encoding (like UTF5 or CIDNUC)
which is to be implemented by browsers.  IMHO these TEs should not
appear anywhere in the core standard protocol for obvious reasons (and
that means none of DNS servers (normal or caching) wouldn't know about
this encoding).

Regards,
Eugene

a.irvine@bfs.phone.com wrote:

| The point is that i18n URI's (hostname and path) should have ASCII
| equivalents as fallback so that universal access is possible (even if
| %HH is somewhat geeky).

-- 
Eugene M. Kim <ab@astralblue.com>

"Is your music unpopular?  Make it popular; make music
which people like, or make people who like your music."