Re: Document Status?

"Soobok Lee" <[email protected]>
Newsgroups gmane.ietf.idn
Message-ID <1ddb01c253d1$513ce210$0101010a@temp>
----- Original Message ----- 
From: "Dave Crocker" <[email protected]>
 > >
> >If some company don't want to trust and invite IDN and don't want to 
> >modify its applications,
> >but, IDN is encoded in trusted ASCII and penetrate into the applications and
> >get trusted by the unmodified applications as other trusted ASCII domains.
> 
> You are concerned that an IDNA string somehow has a lower level of 
> authentication than a regular, ASCII DNS string?
> 
> This cannot be true, since an IDNA string is a regular ASCII DNS string.
> 
> >  IN protocol world,
> >Dynamic DNS updates protocols are affected directly by that holes.
> 
> IDNA introduces no changes to the mechanism for Dynamic DNS updating.
> 
 
THey have been suggested may reasons why some companies may not want to trust
and support IDN (IDNA + all other utf8 based proposals) in their applications. 
IDN  introduce ambiguity in higer layers than machine protocols.

By "trust" i mean that 7bit applications accept 7bit ASCII domains as fairly 
"unambiguous" identifiers historically and had been putting trust in it ..
I didn't mean soome trust mechanisms like DNSSEC or X509. Just common trust in ASCII
which is  the greast common divisor in all internationally-used scripts.

IDNA strings does not deserve the same trust as ASCII domains have now in end 
users.

Soobok Lee
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.