Re: [I18nrp] Additional input needed for i18nRP BOF
Larry Masinter <LMM@acm.org> Fri, 08 June 2018 19:10 UTC
Return-Path: <masinter@gmail.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id B0521130E99
for <i18nrp@ietfa.amsl.com>; Fri, 8 Jun 2018 12:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level:
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001,
HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001]
autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id ABMWM0cdANUq for <i18nrp@ietfa.amsl.com>;
Fri, 8 Jun 2018 12:09:59 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com
[IPv6:2607:f8b0:400e:c00::230])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 3A092130E60
for <i18nrp@ietf.org>; Fri, 8 Jun 2018 12:09:59 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id a22-v6so7082864pfo.12
for <i18nrp@ietf.org>; Fri, 08 Jun 2018 12:09:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=sender:from:to:references:in-reply-to:subject:date:message-id
:mime-version:thread-index:content-language;
bh=c5H1CNrP3Iq7OJyNkgGuCa7EvDwrUGE1RXVAIvg+2tI=;
b=LQ/iDw1/xC+OmmGBQO7dAM726XtJVjtDBKJB4NGn+aitvvUhjVjrVpvFJfpfDvf30o
7ByLxNIO+ra8yIracoe8TH00r3r37xrMoV8z+v/PbIeR4QsXkurxIHtev048VeXRjJJ0
KZrchbV2YufQOiE6sMO+igDdhB6/ZmZMmT5xe0YM8NSU+wXRF3Yz9RYiol9t2M22oibw
GAh29mCuGZG41cEV+uOW6Y/ipIW60ebAdNeziDli9qv8Kh1kxlNfQb4Algz1x65mOgRi
/ufcDcA/FirqEaaQQPBQkWN0l8cB54k007iBZwyztn/J7JWtrgkqEC/jRQCtuMsajjOd
MXRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:sender:from:to:references:in-reply-to:subject
:date:message-id:mime-version:thread-index:content-language;
bh=c5H1CNrP3Iq7OJyNkgGuCa7EvDwrUGE1RXVAIvg+2tI=;
b=FldWGa/shQdsDlzpIFve7Bmzf8pV8sE+9ps32GRkyHXtfCoP+olTIq27Lw/Nv4pEyE
GLrctCA+SFrKKayWNCoeljhtiZk/en1nv7qCaAhdxU1czPZkMGd5HFkmiYg7nQAKdR9+
M6AViTihI8hsIxj19inruXy4SYC3A8xM5E5yySQ1B8eDRYohDSFMn6cMsabXYkn4FxSi
78Tu7EJgWEAuINW+XgwGLj9a9u4MFTcBEWkXnxkt8fMk0F4DqNINLzGRRyAXSVnAj8qG
SrPgEGBlts4kWuqOktHZyyZExr7AhY/aFIBmQLJd9Ka0MAjaXgjXUASYAgXGt/Xri5X+
2wGA==
X-Gm-Message-State: APt69E3jbpSwTioVG3loL2IB+05qgIpe/uWONVDYuG5blEaQEV+Vkecq
svKgGf9qMGBYbzp9DIheJBJh670P
X-Google-Smtp-Source: ADUXVKKrXUFIA8d9ZYzMc6mAlQxU0nUYEO/bkHeyuNz9sICK/8skLjvQbxULezLfsZQPOxmPF9aKaA==
X-Received: by 2002:a63:6ecb:: with SMTP id
j194-v6mr6212450pgc.158.1528484998248;
Fri, 08 Jun 2018 12:09:58 -0700 (PDT)
Received: from TVPC (c-24-6-174-39.hsd1.ca.comcast.net. [24.6.174.39])
by smtp.gmail.com with ESMTPSA id f11-v6sm16196844pgo.62.2018.06.08.12.09.56
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 08 Jun 2018 12:09:56 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'John C Klensin'" <john-ietf@jck.com>,
<i18nrp@ietf.org>
References: <f997170c-3062-0241-e58d-7a3415fba983@nostrum.com>,
<CE6F76BB323F1555D6B217A5@PSB>
In-Reply-To: <CE6F76BB323F1555D6B217A5@PSB>
Date: Fri, 8 Jun 2018 12:09:56 -0700
Message-ID: <013f01d3ff5c$4aa68ee0$dff3aca0$@acm.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0140_01D3FF21.9E482C10"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHT/VErI5/eHgkvWUq6chNtq+jtD6RTQmUAgANtAYs=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/45HJCc80mh63kXY5b6C-MhN2zAA>
Subject: Re: [I18nrp] Additional input needed for i18nRP BOF
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>,
<mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>,
<mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2018 19:10:01 -0000
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
- Re: [I18nrp] Additional input needed for i18nRP B… John R. Levine
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- [I18nrp] Additional input needed for i18nRP BOF Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Eliot Lear (elear)
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Brian E Carpenter
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Benjamin Kaduk
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… John C Klensin
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Nico Williams
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Peter Saint-Andre
- Re: [I18nrp] Additional input needed for i18nRP B… Adam Roach
- Re: [I18nrp] Additional input needed for i18nRP B… Larry Masinter
- Re: [I18nrp] Additional input needed for i18nRP B… Larry Masinter