Re: Possible BofF question -- I18n
"tom p." <daedulus@btconnect.com> Tue, 05 June 2018 08:52 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25C6D130F21 for <ietf@ietfa.amsl.com>; Tue, 5 Jun 2018 01:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 PvdLEuNgmVHc for <ietf@ietfa.amsl.com>; Tue, 5 Jun 2018 01:52:55 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50130.outbound.protection.outlook.com [40.107.5.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 508A6130F1D for <ietf@ietf.org>; Tue, 5 Jun 2018 01:52:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ki4H3aoS+mnAC4YQ+ye3TtbcWnTccoMAYh0G0xkIVvA=; b=eeJEmtr3xQVqY8v056mBjB6kwAB5d2kT+tbQ+spG7DhmejFvTNykxjvNMC7DS/53ObSvhNK6ApS0mFHqJjIyax4cq/jw9d62u2Z+uEQ0BMwD+VvfnU81x26aN1j4dTHL/U3z0W0hA9o5LxDkFiuwmgcnaOftsJCox1DcgaQUBTs=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com;
Received: from pc6 (86.165.129.94) by VI1PR0701MB2351.eurprd07.prod.outlook.com (2603:10a6:800:6b::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.841.12; Tue, 5 Jun 2018 08:52:52 +0000
Message-ID: <01e301d3fcaa$54a648e0$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: Barry Leiba <barryleiba@computer.org>, Nico Williams <nico@cryptonector.com>
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
References: <383c2404-7beb-63e9-b2b2-e75fd1b174f1@mozilla.com> <20180601041949.GH14446@localhost> <A13FFF23-49BD-459D-8B5B-D3448154EEBC@frobbit.se> <20180601151053.GI14446@localhost> <2584adb9-1622-8b49-7236-ecc7dd374974@mozilla.com> <alpine.OSX.2.21.1806011219340.7621@ary.qy> <CAK3OfOgv33SJiPJ6ypo8k5hcpnjcJdRso6EXb9b12YNcdDgMUg@mail.gmail.com> <6c5d5618-74a5-dcc8-d818-89243a41f307@gmail.com> <20180603061350.GM14446@localhost> <d125f213-c096-1e93-0a6e-ffdfc55a7ac6@gmail.com> <20180605031021.GO14446@localhost> <CAC4RtVAHd37mHFv7TypVdKATtHtBNX0pEszbn+ke5RMh-oExMA@mail.gmail.com>
Subject: Re: Possible BofF question -- I18n
Date: Tue, 05 Jun 2018 09:49:03 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.165.129.94]
X-ClientProxiedBy: LO2P265CA0182.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::26) To VI1PR0701MB2351.eurprd07.prod.outlook.com (2603:10a6:800:6b::18)
X-MS-PublicTrafficType: Email
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7193020); SRVR:VI1PR0701MB2351;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR0701MB2351; 3:k6fCoM88OZkzY767VX3dHYT4zU0Rve1qy1UbuT/tLrwUewMC3U1QYGJbtLoqP8R7CHDKfVh9WN13UJsfwGarP/mbjzhFZIdCzipSmRP2XSnOdjsVlkB3NNk8DE9TLzSxffRwaib8meLDJpzRED/jJyeUDuNF5ylCbgLDe4rV9ec/wcIjqjVjfJPTNjbjcpAha16Xs7KOdmq5hkVz+F2I28XqvRnsRNOuFqcplqGbgfxNaVaynAg9umnYD3Oqfti1; 25:D27tPiCWSsyjU2mp+84ON3JTlzEAhWZ7seI90kVTSRgepunF0BVD6bvBBmPxBsWxC5HA/TxYzghu6SS3JFkKVz8GW0T9avXZf27H7MfbIEYFN1zfSYvPtQguCawCG2y8zsD8UU3EYyoshx2pyhHENiTyg5tXklbC2moVkLvZTbOjv07NlUhyI4Zm+Z+BE2Q+iTQZBjqia9+IAqbXnXT2lHQYmti2xU5DozgqBn7ebFwcNASfY0XJ1sVsMNzWhLmAAlTp5bayfCePAom5vY4cGjBs0nIAq7oxdm0lrljGu/siGPX/xWOiMFshxXzMyV3Ds27JDUjDWQEScTeB150UsA==; 31:DODSmo1HhZ8p8sT7AciyLj4u1DfCMBDeIXCbjSlohLrBXc/xPQRy929A/Kqta8En0TujeglklOZZ5ccQw9pmAfmpndoTvvCJWMBOApDnQEEf9abbYnxjKzzrcALbETkQLTj5PsZNHx1/PYyZAzMxmbyd5BS1BXFP3a/NeE1jS5LO4H66o+RQZaDwRPiz4JW/BzY9Hxg7Rg4LgUwB9WPKd4Au0CPVqMeck6ujtOfPGh4=
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2351:
X-Microsoft-Exchange-Diagnostics: 1; VI1PR0701MB2351; 20:gRcHgfyzetcj7ydSj6sxQBwFIDlc07ZPT/b+/9dqafYtWOH1YYEipi9CRdFQAQu9pHvHpF5rmBtUSLCd/V/osdBoOJd1MgtBoT4XD03nQl9KyBc+kuneLeqmVpa4awTCl5MPbb/7c2CnnF3vu72bSeY3Ld7zpN1mp29+ysGiY+g=; 4:KtYBypjWyUWktGLWVzpyDfx3f7FFcIAuIYcGJ8Dwz4KIweuLBhx5+Dcs6CbKfCjGuZjrGIveY6vEHZrJOaTPfuz3aYyM8OyoPsDAqr/G5MSiweFrn94ZzegbxvLcqqrZ8KcoS3ZU1nUfAjCY1/O4t/t9zCeUsz10fGx8seGiZWiwRVlCsKnLPDRfec6C7NGgFejLiRzp09DWb0C4TTTim0237defHnlo5AcUyl1DYdfKIyXG9UeKIVKGOz1v7xlcBNZ1dNmK8L0tBJH/w6iqBIXH8O2IsbHSUydsgrDSzIUluP6Rhqk9tPrRek4erjQp
X-Microsoft-Antispam-PRVS: <VI1PR0701MB235139DE69AACC1FA06F82A4C6660@VI1PR0701MB2351.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(192374486261705);
X-MS-Exchange-SenderADCheck: 1
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:VI1PR0701MB2351; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0701MB2351;
X-Forefront-PRVS: 0694C54398
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(39380400002)(396003)(39860400002)(366004)(376002)(346002)(189003)(199004)(13464003)(66066001)(2486003)(6486002)(551544002)(62236002)(44716002)(47776003)(5660300001)(53546011)(229853002)(2870700001)(186003)(478600001)(33896004)(50226002)(16526019)(386003)(6496006)(6666003)(59450400001)(44736005)(81816011)(26005)(81686011)(23676004)(76176011)(52116002)(9686003)(2906002)(4720700003)(6116002)(3846002)(25786009)(4326008)(6246003)(97736004)(110136005)(84392002)(53936002)(54906003)(68736007)(61296003)(106356001)(93886005)(50466002)(316002)(446003)(486006)(86362001)(8676002)(7736002)(81156014)(8936002)(956004)(14496001)(305945005)(81166006)(1556002)(476003)(105586002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR0701MB2351; H:pc6; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: 1;VI1PR0701MB2351;23:z394Rkvhh9jkcUNE1GXQgzqZlteneN+FpPgFg6Z50gcxXbQ+/o+NffyzvkUIeJnILPgrztSDhVY+PwTB4smLRVoDEDdfiFjEjbND2G7I/c/ligrXIUCRV/18Ll1+B3aKOZX8J1Q77jgJJVQLWB33jr+JLvmhfPdwzoGy3Oska21LPLnSS8rDBFk0GmKdvwAqusKYjohAbUKZgZEOwUtFnLWro2gBrpL1BrQ4hf1HaC5EH2RNb4FBTaJwQMSGYM/qg3N9wQm74bWQGgPoHuIMcj2o2fs68wu4cFYaw4tUlA6z9anZIH6mvIWXpka40iwQN+oxd/DtoGgraFQ79sv16+h+lFK42dUZf3r0AHbcowYEmGpZBYdpN+zjGrklBHoMxv5TlN/HH2YCdbbtS0xBtmN9ZwoLEVohnZcXO/IJqbEqBYf1YHSN9sMV9oPzPaLk1TN2L9NncoH/lvSnN/+IUcLQmSs9Vzk08yW1R9ri1yiUczsxCrzp+Jq8/mksR2RzwPhbB6XC9mtzu1Zde1CLELo71BX17qZAgDqlXbxrf90TzPHMwTPL2zuU8Ky+K0+sZpiqQ3o0O9Ebu6gpqCBOojwAygH6XZeVnpJrBJxKXK1fyuajS2ZlX8fVHBWeujVqeM3GlzHhOZzW806qE3n1ZL6gB9salWW9yFmkHPVQ7AdueCWq2wmFZ5ltBbCGCUp08V/rKzVxmS99viy4VckG6GMNP0Ht09dE5jUWpLUP/A1HvKxdtMO3ysh6eHvPpG3KkmGxCbwmbVnJuWiNS5r3tyWM36/ZbEov6lDG2GrkF2lxHyeYdOIIaA6MlnyK6yxcWIESq0boQ4Owt6nRPjs1OO1ZY5voBM2LfYRiu7NkZGmW4O9JdEhcl2P3y51SO65gTor4rIS8wfgUwX4rd7QBHf6lWAuUU8t5W5wQ+jrZePxOz0rKP2adhpR1wxWnqOvRGLlLya07O+uBLZgrv0Ra1gmw9lmo80DxwdgRvyrnxq147HXDvkPoSFwlTVDOPzv/xhOxJ0Rps6Z9LwWAc/4hgKyRGi4ywQQJJvtaWODZvAGjLTQuyDuPZuRZxjKscpU3M1Rf9d9NX2tDL9F4b+uNtu6CzO/4s0APKsrzAGVD+3GwjjhYKZ6vI+/Lprd4JAv66Vx6yKr5GcgWvo2FSA+ReOD67caujNBzsqRixpKQdABTQKlJwU9hfoszbnHpwkGco5D9JDxKvUKV1TGsJTUgrWhkp6MzAEsrwXd6hGMxK1bwg6gxMYzGWmzOKC2b4bApWE2l0Pcab6dzTQddVr5oP7+mzDQX5E9chJT2Lgi6TTcfYlmFQXeK7vagWszX6MTDT+EGJHIOWd1c2U/Addq/Nw410fY+901GhlxsnsoHPWFZB+Bv2bisj5SXpXuJ/TDeigGKVx4sGGEg5o0SLpRn5/Q2vf99EChX6y0lfIMqd0EXAjgDED30oKqtaa1MQQdzPF7jOOqYEkWK3LZYQQIdKwGvXMUcU7HTmOqN6NVgAL9HWCmszDckAZVQw6wMpe0wGYgNXYmvqnnPQqigppQNPXteAmJIruf01vLfum91TBs=
X-Microsoft-Antispam-Message-Info: lZfY/RqTgC3CZuBeHLtm99ZoSOyFFo18NIr27602gqWrbOvwX3B0uZOmL7lMgQtQdWiUQPFJqn/4l6ly63lD2ZRDdEoA1p3g2KFICvxxIcCvh1qsgMuAiC44LhkzDxdsAM0OysByCU1XqRzhADo5z50DXWbxlLxRjR6LAURBcGL0wsRfhpMCX8Xvk7Vpb0Ej
X-Microsoft-Exchange-Diagnostics: 1; VI1PR0701MB2351; 6:l8bjAOgY1V4WM3G0nXC0/UFNlAZBslcAMJH9oBfuyaiQ9vSNtbGB0PQ2uUaiXKXh2gOK4+5yqcf6l3w8O13EiNENSpnEU0qEQgCSCStkpjGQKZE5Kt2OVSoWPaw6S5uy9YBqFdomB6CyFQuozJhVmwMZ+u2orS9Cq9HQFWQ5mVLktPaMC5dugVUKZbJ0gApvoDh50WU56MiuSbV9e6XzAJoK15P9MtgZCPd6p86j5OIQaTP7/dNPmrX8EUgoydCMvkSRqL42tTxIb2SfvVVrJcvj4DOQhtkUTvK3cB83d6WCDkT4xhMdsNtDeg2zgdgeqvL+MmyaKxKh2FN6HBVCjvW0VtESgfwh9THTpiLHmHAincVzr6trm/1gVvT7hyDwDQ1ClLJCj+9AfWR6HL9acZGFOUzamSMumexdWYyd/1RnwdvHwRp9hCUcx8ZFOtsC6peI5fXkTt9xGg86vvpa2Q==; 5:HdrDdbnhSSxguFKRK84DLN5sm2ibqyGyLPH2Lrmy3gNW7uZZdODxaD2+6SHc2ocZL58G0uDE9XfTbA0v+aFL5x3D5oYwV6UKQGOlUPBRIOQVJHCAdTulONj1doJYyeyJtsr/QKyxl2qL0PGknlNBxY3CVCjJyz47elKIk6LkTjA=; 24:2JwHvMil8gN1ZhXPmkZe+g6puk/kz9Xp2SK3FhgblasFG2Cj1zsOIACkjgr7gXkY4s8oOcsF+vlkSNjA3So41CAgrhXjNz5mdPiRlGPfGrA=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR0701MB2351; 7:1b627JnY6XcJgyJJuMGX5DgT1tFiRbrtof72ZeyyxmTNulLUQWZ/l4tMx8A/mdfv7rNJQh+0EJUnv/8vP9Jq22XjYD5JhF4g17jFEThcaBtEzGZl1mBspbba9Xz6OkgJSh11U4wdhPj88aFxVjbMUpOduesNImfX8XWAN4aC2UhMZhHnUxJTYJOUuVa1Bhl+SQrSo6rnabXUdADqmE04VdROnj3AfbTdHKWIlLA9dp0Ay4nyT4vQW+auVBkbz0VD
X-MS-Office365-Filtering-Correlation-Id: 4395714d-8bcf-4fc7-5f8e-08d5cac1b923
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Jun 2018 08:52:52.2020 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 4395714d-8bcf-4fc7-5f8e-08d5cac1b923
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2351
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wbBwrqUROBwQjWNhF37pL3IJVCc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.26
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 05 Jun 2018 08:52:59 -0000
----- Original Message ----- From: "Barry Leiba" <barryleiba@computer.org> Sent: Tuesday, June 05, 2018 6:50 AM On Mon, Jun 4, 2018 at 11:10 PM, Nico Williams <nico@cryptonector.com> wrote: >> We're in a space where the evaluation of A==B depends on more than >> the bit strings A and B. Your post about form-insensitive filename >> comparisons is a case in point, although I don't pretend to understand >> it. OK, we can argue whether that's a dark art or simply complicated > > form_insensitive_strcmp(a, b) == memcmp(normalize(a), normalize(b)) > > Except that actually one can greatly optimize this to avoid most of the > compute and memory cost of normalization. > > To see why consider comparing my first name as I usually write it > (Nicolas) vs. how it should be written (Nicolás). The two strings > should compare as not equivalent. But the two ways to write the second > form (with the ´ precomposed vs. decomposed) should compare as > equivalent (because they are). But there's one of the things that makes this a complicated topic: - we say that "nicolas" is not equivalent to "nicolás" - but we say that "nicolás" *is* equivalent to "nicola´s", and we handle this using normalization - does that mean that it's OK to have "nicolas" and "nicolás" as two different usernames assigned to two different users? - if yes, how do we deal with the human interface issues involved? What happens if the human identified as "nicolás" uses an input mechanism that doesn't have a way to enter "á"? How can he log in? - if no, how do we make sure (in an automated way) that we don't make that assignment? - does the answer change if "nicolás" is a domain name instead of a username? - does the answer change if "nicolás" is a *password*? - and what about "nicolàs"? and "nicolâs"? and "nicoläs"? - what about "nicolаs" (that's a Cyrillic character in the penultimate position)? - what about "nicolαs" (that's a Greek character in the penultimate position)? - what about other Unicode characters that look like "a", either exactly (as with Cyrillic) or closely (as with Greek)? - what about handling of "ä" vs "ae"? Do we want to avoid assigning "käse" and "kaese" as distinct usernames? Does the answer to this differ depending upon whether the language is German (where using "ae" to represent "ä" is common) or Swedish (where it is not)? Now extend this to the many other characters that can look similar (say, "n" vs "ñ" in Spanish). Extend it to other language-related issues ("i" vs "ı" vs "İ" vs "I" in Turkish; all the character variants in Arabic). These are only some of the reasons it's difficult. And the number of people who stand up and say, "oh, just <do this> and the problem is solved," demonstrates that too too too many people *think* they understand... and don't. <tp> Barry, This is a cut out and keep e-mail that I shall still be referring to in 10 years time because it summarises so beautifully the problems. It also is the kind of data that led me upthread to assert, contentiously, that only Europeans were likely to know what it was about since they had been living with for decades in a way the most Americans had not. I mentioned CJK but John rightly pointed out that, worldwide, it was far worse, with right-to-left, vertical and so on and so the most skills may now lie further afield. Two thoughts. One is that your e-mail displayed superbly (the only glitch being that my MUA did not differentiate the Cyrillic character) so I looked at the encoding Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable so that is something we got brilliantly right a long time ago. (The bad news is that I get an ever growing number of messy e-mails from some e-mail ids who use some complicated Unicode characters instead of ASCII punctuation; a sort of single quote being the commonest so the technology, for me, gets misused). My second thought is that much has been done in the IETF on security in recent times but have we done enough to at least publicise, if not eliminate, the scope for evil actors to exploit confusable and suchlike characters by saying that they SHOULD NOT be used anywhere where it matters for security - people SHOULD NOT be handed the rope with which to hang themselves on a plate:-) - I suspect not. Tom Petch Barry
- Possible OBF question -- I18n John C Klensin
- Re: Possible OBF question -- I18n John Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… tom p.
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… Donald Eastlake
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n Adam Roach
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n Brian E Carpenter
- RE: Possible BofF question -- I18n (was: Re: Poss… Larry Masinter
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- RE: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Benjamin Kaduk
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… Niels ten Oever
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Stephen Farrell
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Peter Saint-Andre
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Spencer Dawkins at IETF
- Re: Possible BofF question -- I18n Brian E Carpenter
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n John R Levine
- Re: Possible BofF question -- I18n (was: Re: Poss… John C Klensin
- Re: Possible BofF question -- I18n (was: Re: Poss… Nico Williams
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n (was: Re: Poss… Patrik Fältström
- Re: Possible BofF question -- I18n Brian E Carpenter
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n Barry Leiba
- Re: Possible BofF question -- I18n Viktor Dukhovni
- Re: Possible BofF question -- I18n Christian Huitema
- Re: Possible BofF question -- I18n Nico Williams
- Re: Possible BofF question -- I18n tom p.
- Re: Possible BofF question -- I18n Barry Leiba
- Re: Possible BofF question -- I18n ned+ietf
- Re: Possible BofF question -- I18n ned+ietf