IETF Logo Mail Archive

Re: IDNA and U+08A1 and related cases (was: Re: Barry Leiba's Discuss on draft-ietf-json-i-json-05: (with DISCUSS and COMMENT))

Nico Williams <nico@cryptonector.com> Mon, 26 January 2015 18:14 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3DB81A8718; Mon, 26 Jan 2015 10:14:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 6r3NFXfgaKn6; Mon, 26 Jan 2015 10:14:32 -0800 (PST)
Received: from homiemail-a108.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id B81F41A86FE; Mon, 26 Jan 2015 10:13:15 -0800 (PST)
Received: from homiemail-a108.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a108.g.dreamhost.com (Postfix) with ESMTP id 984142005D82D; Mon, 26 Jan 2015 10:13:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=t68jF9w8gfcx9f Orkc0DszhYvWE=; b=fei7qST2yVUuyY96fTrDX7qF9icvEGD7HljumJbHsmHqtn Vt9twUaQy3pIsa9473/nCf/bhnIcn5MZOUTVtsIABOV31aCKBXSVg1naJx35qqYD O/9sG/BrHVE2Iu6JlIGAOnSqcAQflbFzhMd1jiJu0FdFz44BheLfmj0PR5hEs=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a108.g.dreamhost.com (Postfix) with ESMTPA id 3B8ED2005D82E; Mon, 26 Jan 2015 10:13:14 -0800 (PST)
Date: Mon, 26 Jan 2015 12:13:09 -0600
From: Nico Williams <nico@cryptonector.com>
To: Asmus Freytag <asmusf@ix.netcom.com>
Subject: Re: IDNA and U+08A1 and related cases (was: Re: Barry Leiba's Discuss on draft-ietf-json-i-json-05: (with DISCUSS and COMMENT))
Message-ID: <20150126181305.GB19544@localhost>
References: <B22C902579D0C7B5ADAA03C4@JcK-HP8200.jck.com> <20150121194249.GT2350@localhost> <5A8468D3DF4EEDF3A4715FD7@JcK-HP8200.jck.com> <20150121212700.GU2350@localhost> <F51F2760094ECDCACD7BD411@JcK-HP8200.jck.com> <54C5DF1E.2070106@ix.netcom.com> <54C5E9F9.2000501@qti.qualcomm.com> <54C5FAD2.1010507@ix.netcom.com> <CAK3OfOiomYxRk-o_Hi+EBnO6rdefmL1rJRPcGXC4wKULh4Wq=g@mail.gmail.com> <54C65ECE.8030500@ix.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <54C65ECE.8030500@ix.netcom.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/lTQ5eJXRZlyXAS5F-DqRlk9w5Ms>
Cc: ietf@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, idna-update@alvestrand.no, The IESG <iesg@ietf.org>, John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 18:14:33 -0000

On Mon, Jan 26, 2015 at 07:35:42AM -0800, Asmus Freytag wrote:
> On 1/26/2015 1:12 AM, Nico Williams wrote:
> >As far as I'm concerned it's clear that the correct way to handle
> >these cases is: as confusables.  Is this wrong?
> 
> I basically agree with you.
> 
> I'm making a further distinction between confusables by accident and
> confusables by intent, and am advocating that the latter can be
> handled more explicitly. But basically, yes.

I'm not sure that the cause of the confusability makes any difference.
It's there.  Once it's there we have to deal.

The details of how a confusable came about are certainly interesting,
but they don't really matter to how we handle them, right?

Nico
--

v2.23.0 | Report a Bug | By Email