Re: [I18nrp] Additional input needed for i18nRP BOF

Thanks, Larry. It's good to hear from you.

This seems like sound advice. I'll point out that we're trying to 
determine a *process* for addressing i18n issues rather than addressing 
the actual issues right now.

/a

On 6/8/18 2:09 PM, Larry Masinter wrote:
>
> Focus on confusables, untypables. Unicode greatly expands these.
>
> I say ‘greatly expanded’ because ASCII has confusables (MlCR0S0FT – 
> note lower-L vs upper-i and zero vs upper-o) but short lower-case 
> ASCII might be ok.
>
> Separate unintended vs. malicious cases.
>
>   * Unintended can be reduced by providing more information to those
>     choosing names.
>   * To address maliciously introduced confusables may require protocol
>     changes:
>
> To deal with maliciously introduced confusables, reduce the reliance 
> on humans to compare or read or retype accurately of unvalidated name 
> from a non-trusted source (as commonly exploited by phishing) might 
> mean recommending the ‘resolution’ of typed-in or even copy-pasted 
> URLs into searches, and using directory search for non-ASCII email 
> addresses as well.
>
> Give up trying to enumerate and mandate the non-use of confusables ,as 
> it is too dependent on the population, their language, and the 
> software they have.
>
> Larry
>
>
>
> _______________________________________________
> i18nRP mailing list
> i18nRP@ietf.org
> https://www.ietf.org/mailman/listinfo/i18nrp