Re: INTLOC, IRNSS, and Salt Lake City
Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> Fri, 15 February 2002 22:21 UTC
Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GRL00904I41ZG@eListX.com> (original mail from brunner@nic-naa.net); Fri, 15 Feb 2002 17:21:37 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GRL00901I40ZE@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 15 Feb 2002 17:21:36 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GRL00901I40ZD@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 15 Feb 2002 17:21:36 -0500 (EST)
Received: from nic-naa.net (dt0b4n7d.maine.rr.com [24.95.12.125]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GRL004NRI3Z9K@eListX.com> for ietf-irnss@lists.elistx.com; Fri, 15 Feb 2002 17:21:35 -0500 (EST)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.11.6/8.11.1) with ESMTP id g1G1HZS02147; Fri, 15 Feb 2002 17:17:35 -0800 (PST envelope-from brunner@nic-naa.net)
Date: Fri, 15 Feb 2002 17:17:35 -0800
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Subject: Re: INTLOC, IRNSS, and Salt Lake City
In-reply-to: "Your message of Thu, 14 Feb 2002 21:20:09 EST." <45895701.1013721609@localhost>
To: John C Klensin <klensin@jck.com>
Cc: Paul Hoffman / IMC <phoffman@imc.org>, intloc@ops.ietf.org, ietf-irnss@lists.elistx.com, harald@alvestrand.no, brunner@nic-naa.net
Message-id: <200202160117.g1G1HZS02147@nic-naa.net>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>
John, > I think the key question is what should be on that agenda. There probably isn't any point in putting encodings, equivalence classes, intermediate mappings or tables, and other puns for the problem recently solved (incorrectly) in the IDN WG. So, those problems "in layer N" that don't resolve (pardon the pun) uniquely down to the solution that unfortunate activity has proposed "in layer 1" (or "0", I've lost count), aren't ab initio absurd. There's lots of them, the label space semantics can be extended by just a few (ASCII) characters, like blanks, and backspaces for that matter, without meaningfully venturing outside a particular character repitoire. Just assume (as a hypothetical) that only some clueless few Asians and "character mavens" will contribute (bother with) the IETF on i18n issues. If the proposed activity isn't nuanced by ENOASIANS, fine. If the proposed activity _assumes_ participation by Asians qua Asians, on an i18n issue, an assumption check is now in order. Eric
- Re: INTLOC, IRNSS, and Salt Lake City Eric Brunner-Williams in Portland Maine
- Re: INTLOC, IRNSS, and Salt Lake City John C Klensin
- Re: INTLOC, IRNSS, and Salt Lake City Paul Hoffman / IMC
- INTLOC, IRNSS, and Salt Lake City John C Klensin