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

Ted Hardie <ted.ietf@gmail.com> Mon, 28 February 2011 19:41 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 04D833A6A2A; Mon, 28 Feb 2011 11:41:54 -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 95A653A6A2A for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 11:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.335
X-Spam-Level:
X-Spam-Status: No, score=-3.335 tagged_above=-999 required=5 tests=[AWL=-0.336, BAYES_00=-2.599, J_CHICKENPOX_57=0.6, RCVD_IN_DNSWL_LOW=-1]
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 L4R00RfvZgdU for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 11:41:51 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id A5F6B3A6A24 for <dnsext@ietf.org>; Mon, 28 Feb 2011 11:41:51 -0800 (PST)
Received: by qyk29 with SMTP id 29so2363488qyk.10 for <dnsext@ietf.org>; Mon, 28 Feb 2011 11:42:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=yfKdagJyhCpMDeQhgxovK/8J2mWcHgfN8yS7XOyR9V4=; b=PbW6kIanTcd1imPfoCbKTP+vbPkfwlpjc2T4IlkH4YJ0EccDjLpPHaBvK1ynlahv0z tv1Zyw902h7nueZVGlwEgwNYxJoUEsw4aEz/pAtN0BKEcYnv36GQUn+hJcQcnObGUu+R 1zyNMSxZ7261/WH4wlKDUVDCRESTZJ1WOVMmk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ib2GaEKpJGtWzh3d80p5W5eHKkbiXXQ9Y83pOb865m99CSYyrkUZlbK2Sfw9d3dZ1e ELu6MCTMFZFwAdF0DL/ld00QjUIg4rkvwXVis4gJ9aYnjF9go9g48lxfXcb/4Fw4Aqdo oQMLQvHt3qKXOMrZqT5ef+AF452HeamJf1yOY=
MIME-Version: 1.0
Received: by 10.229.192.15 with SMTP id do15mr4582122qcb.155.1298922172346; Mon, 28 Feb 2011 11:42:52 -0800 (PST)
Received: by 10.229.98.210 with HTTP; Mon, 28 Feb 2011 11:42:52 -0800 (PST)
In-Reply-To: <4D6BE4D6.3030103@abenaki.wabanaki.net>
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> <4D6BE4D6.3030103@abenaki.wabanaki.net>
Date: Mon, 28 Feb 2011 11:42:52 -0800
Message-ID: <AANLkTimaSvbs00TCevsPH5ZX43TzuPk7VXO7Fo3qFdhM@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
Cc: dnsext@ietf.org
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On Mon, Feb 28, 2011 at 10:09 AM, Eric Brunner-Williams
<ebw@abenaki.wabanaki.net> wrote:
>perhaps charset is misleading,

I think at this point casting the "sameness" problem in terms of
charset mapping is more than misleading.  In IETF terms, a charset is
a character repertoire in a particular encoding.  The IDN effort can
be seen as changing the character repertoire in a way that re-used the
previous codepoints in a new encoding.  That was hard enough for
people to get their heads around.

At the label level, .xn--fiqz9s and xn--fiqs8s being equivalent is no
different from colour.example and color.example being "the same".

Let's not confuse our terminology further, please.

regards,

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