Re: Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt

Simon Josefsson <[email protected]> wrote:

> >     When systems use local character sets other than ASCII
> >     and Unicode, this specification leaves the transcoding
> >     problem up to the application.  If applications implement
> >     different transcoding rules, they could interpret the same name
> >     differently and contact different servers.  This problem is not
> >     solved by security protocols like TLS that do not take local
> >     character sets into account.
>
> Before the last sentence it could be useful to also add something
> like: "Furthermore, if a single application uses one mapping table
> in one version, and a subsequent version of the application uses
> a modified mapping table, different interpretations of the same
> internationalized text string may be possible even within the same
> application which has security implications."

How about simply changing "applications" to "different applications (or
different versions of one application)"?

AMC