Re: [dnsext] the same in old days, was making names the same NEED protocol changes?

Eric Brunner-Williams <ebw@abenaki.wabanaki.net> Mon, 28 February 2011 18:08 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AD023A6C3D; Mon, 28 Feb 2011 10:08:34 -0800 (PST)
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BD593A6C3D for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 10:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level:
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWk2Wt4VwrXy for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 10:08:32 -0800 (PST)
Received: from abenaki.wabanaki.net (abenaki.wabanaki.net [65.99.1.133]) by core3.amsl.com (Postfix) with ESMTP id 2C7273A6C34 for <dnsext@ietf.org>; Mon, 28 Feb 2011 10:08:32 -0800 (PST)
Received: from limpet.local (cpe-67-255-5-237.twcny.res.rr.com [67.255.5.237]) by abenaki.wabanaki.net (8.14.4/8.14.4) with ESMTP id p1SGLtlS028110 for <dnsext@ietf.org>; Mon, 28 Feb 2011 11:21:55 -0500 (EST) (envelope-from ebw@abenaki.wabanaki.net)
Message-ID: <4D6BE4D6.3030103@abenaki.wabanaki.net>
Date: Mon, 28 Feb 2011 13:09:26 -0500
From: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
Organization: wampumpeag
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: dnsext@ietf.org
References: <20110227182720.6537.qmail@joyce.lan> <552AB7D12FAB50296E795CF5@Ximines.local> <alpine.BSF.2.00.1102271336340.6604@joyce.lan> <AF3A2DE418832E7A91CD07A5@Ximines.local> <alpine.BSF.2.00.1102271457570.7355@joyce.lan> <AANLkTi=DLzBEQFLqAmPccbdt63LDSp1cRzShnYkuiDQB@mail.gmail.com> <AANLkTikJvkK27huT0FSQ=1DF2HS1hwUS3TL1u988h8gN@mail.gmail.com>
In-Reply-To: <AANLkTikJvkK27huT0FSQ=1DF2HS1hwUS3TL1u988h8gN@mail.gmail.com>
Subject: Re: [dnsext] the same in old days, was making names the same NEED protocol changes?
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

<snip>
>> If we decide we can change the application client, this whole problem
>> becomes pretty straightforward. Either adopt the 'did you mean'
>> pointer style approach or allow domains to nominate mappings of one
>> charset to another.
>>
> Please do not use "mappings of one charset to another" to represent
> this problem.   At this point, we are all mostly talking about the
> Unicode character set and how to map labels derived from sequences of
> Unicode characters.

well ... it is the case that we have distinct ranges of values, 
subsetting within the Unicode character repertoire, and have, or have 
considered, rules concerning labels composed of values from distinct 
regions.

the latin vs arabic vs indic digit discussion is one example with 
three very modest subsets of that repertoire. should "mixing digits" 
be allowed, pro and con claims followed, invoking directionality or 
similarity, depending upon the choices of subsets to be . there are 
other examples.

so it isn't incorrect to reference, though perhaps charset is 
misleading, mappings from one subset of values to another, in the same 
repertoire. the subsets may, or may not, be contiguous and disjoint, 
or consist of a common set, and two or more point-wise disjoint 
subsets of a single additional set (sc/tc).

-e

_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext