[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] host name vs. domain name
- To: Karlsson Kent - keka <email@example.com>
- Subject: Re: [idn] host name vs. domain name
- From: "David R. Conrad" <David.Conrad@nominum.com>
- Date: Fri, 17 Mar 2000 15:02:35 -0800
- Cc: "'Eugene M. Kim'" <firstname.lastname@example.org>, email@example.com
- Delivery-date: Fri, 17 Mar 2000 15:03:54 -0800
- Envelope-to: firstname.lastname@example.org
- Organization: Nominum, Inc.
> But these internationalised names would primarily be
> intended for people that *can* read an write them.
Another aspect of this discussion is the whole question of the in-addr.arpa
tree. By using UTF-8 names, it becomes "a bit" more challenging to try to
interpret log files, traceroute output, etc. I am not sure this is of
critical importance, but it is something that should be taken into
> Hmm, I though the point with the TESes (like CIDNUC) would be that they
> primarily was used between client and server, and were preferably not
> seen by the "end user".
I suspect this may be true, however the ability to use TESes does, at least,
provide a more general solution that can be used by those without the
appropriate input methods and/or the explicit setting up of aliases.
> the IP number "name" would be just as good as the second name here
> (though maybe somewhat less permanent).
This is a bad idea. IP addresses really need to be treated as transient
entities and should not be advertised as an identity.