Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: COM/NET informational message

  • From: Måns Nilsson
  • Date: Sat Jan 04 05:07:47 2003

Hash: SHA1

- --On Friday, January 03, 2003 18:31:18 +0000 "E.B. Dreger"
<> wrote:

> UTF-8 is a standard.  MS products have used two-octet chars to
> support Unicode for a long time.  Any reason to add yet another
> encoding?

(Sorry, moderator, I have to use upper case here.)


This (ie. IDN) has been discussed (and finally decided) in the IETF IDN wg
for AGES now. If you are so concerned, why did you not engage yourself
there? It is no secret what has been decided there. 

As to technical merit, the others who responded have outlined pretty well
why UTF-8 is a Bad Idea For DNS. 

That Verisign are taking this forward is, in the way they have chosen to
do, not really elegant, but I do understand their reasoning, and to some
extent appreciate that things are happening. Keep in mind that they are not
breaking standards, they are extending one application. 

The other, earlier attempts to do things like this (especially NuNames)
have been way more rogue than this. 

- -- 
Måns Nilsson            Systems Specialist
+46 70 681 7204         KTHNOC  MN1334-RIPE

We're sysadmins. To us, data is a protocol-overhead.
Version: GnuPG v1.0.7 (OpenBSD)


Discussion Communities

About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home

Merit Network, Inc.