IETF Logo Mail Archive

Re: [I18nrp] Mappings for IDNA2008 ?

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 08 February 2019 19:39 UTC

Return-Path: <ajs@anvilwalrusden.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 D5D6B130F58 for <i18nrp@ietfa.amsl.com>; Fri, 8 Feb 2019 11:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=VDXurb9l; dkim=pass (1024-bit key) header.d=yitter.info header.b=m5rorU/i
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 RaqiQVgWeloR for <i18nrp@ietfa.amsl.com>; Fri, 8 Feb 2019 11:39:02 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33D8D130F1A for <i18nrp@ietf.org>; Fri, 8 Feb 2019 11:39:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 6821EBCBCC for <i18nrp@ietf.org>; Fri, 8 Feb 2019 19:38:31 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1549654711; bh=+rgct+PGUTfCpI3YYzcx7f7KRzr4VYW61lO3NFdijbk=; h=Date:From:To:Subject:References:In-Reply-To:From; b=VDXurb9ltlKMKpnUVI/7JQgDGAmiuN9yoiQbIofTT16163b0N4HThZW3hbENNvWZt RVNJCoRxWNslioPXGnpXPc0y/PYF8PcyxFbwy+KiEVIeyf9h+aln7A7you9kUDdKN/ QsvTr/fZdIWgJX2Q1T0+W7FuMdIEkUg6oE63Be0g=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HnLfmt0Fnhmt for <i18nrp@ietf.org>; Fri, 8 Feb 2019 19:38:30 +0000 (UTC)
Date: Fri, 8 Feb 2019 14:38:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1549654710; bh=+rgct+PGUTfCpI3YYzcx7f7KRzr4VYW61lO3NFdijbk=; h=Date:From:To:Subject:References:In-Reply-To:From; b=m5rorU/iUJqdc+M15tlWDNmH9KoZHCbmYg6SMWyQJX2TqMaiDq8bmb3em8jLD0QGu emS02D+veZO6sPrJDt+Dc2wx83C+zIF/DWpXYQxj6UsAEze6IXkFj6WzDCkgrEJEHS J2GB4uGcL9/R4LeynZmttTTkOB2MM4oWsDCn13tQ=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: i18nrp@ietf.org
Message-ID: <20190208193829.skaujoeq2xgzwzg7@mx4.yitter.info>
References: <20190204225047.02583200DC1666@ary.qy> <6660b7e2-1d5b-6a5d-3d1c-55a757e24843@ix.netcom.com> <ADDA4540-9169-4EE6-B33E-3A0D9EED0BD7@frobbit.se> <16ff0d27-9508-7fdd-bc89-9d6fd47396b1@ix.netcom.com> <D5B49CC8-7AEF-4E81-8774-F3F1F05682E8@frobbit.se> <320f4bc3-17b1-595b-34c7-8f95f69c0f33@ix.netcom.com> <B87C6774-4FF7-4A18-A81D-D0834401C293@frobbit.se> <bc7b727d-f75c-bbba-4f63-ebd1dcd87085@it.aoyama.ac.jp> <A5549B92-9414-4210-A94D-8E53339D3961@frobbit.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <A5549B92-9414-4210-A94D-8E53339D3961@frobbit.se>
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/v_g9gBa248w3MgMmVaYUPMMGeC8>
Subject: Re: [I18nrp] Mappings for IDNA2008 ?
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.29
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 Feb 2019 19:39:04 -0000

On Fri, Feb 08, 2019 at 08:16:39PM +0100, Patrik Fältström wrote:
> 
>  modified with the delta that the LOCALE defines.

I'm still trying to understand how you know what the locale of the
various network identifiers are.  People might recall that this was
one of the problems we have identified as a serious issue in the past.
You can know what the locale is, maybe, at lookup time, but since the
information doesn't travel around with the identifier you can't know
what the locale is at creation time.  And that, of course, is how you
get a security problem out of this.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.1.2.p1 | Report a Bug | By Email