At 01:48 PM 9/4/2002 +0900, Soobok Lee wrote: > > Sorry, but IDNA very much does define an enhanced character space for > > domain names. > >true in display and input (that is what i meant),
you need to distinguish between the abstract, formal name space, versus the over-the-wire encoding of that name space. the current specification does not make this distinction clear, but that is a problem with the documentation, not the formal change. > > Please provide descriptions of specific usage scenarios that demonstrate > > technical failings that are special to IDNA. > >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. d/ ---------- Dave Crocker <mailto:[EMAIL PROTECTED]> TribalWise, Inc. <http://www.tribalwise.com> tel +1.408.246.8253; fax +1.408.850.1850
