[dnsext] Terminological precision (was: the same in old days, was making names the same NEED protocol changes?)

Andrew Sullivan <ajs@shinkuro.com> Mon, 28 February 2011 20:10 UTC

Return-Path: <ajs@shinkuro.com>
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 0F9FD3A6C8A for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 12:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.607
X-Spam-Level:
X-Spam-Status: No, score=-102.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 yNGOoZMlsQe1 for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 12:10:18 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 46D513A6C89 for <dnsext@ietf.org>; Mon, 28 Feb 2011 12:10:18 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id C828E1ECB41D for <dnsext@ietf.org>; Mon, 28 Feb 2011 20:11:18 +0000 (UTC)
Date: Mon, 28 Feb 2011 15:11:17 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsext@ietf.org
Message-ID: <20110228201116.GP80597@shinkuro.com>
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> <AANLkTimaSvbs00TCevsPH5ZX43TzuPk7VXO7Fo3qFdhM@mail.gmail.com> <4D6BFCA0.80806@abenaki.wabanaki.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4D6BFCA0.80806@abenaki.wabanaki.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [dnsext] Terminological precision (was: 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>
X-List-Received-Date: Mon, 28 Feb 2011 20:10:19 -0000

On Mon, Feb 28, 2011 at 02:50:56PM -0500, Eric Brunner-Williams wrote:
> do you seriously think phillip was contemplating playing shuttlecock  
> with a pair of labels, one GB, one Big5?

Speaking as one who is going to have the happy task of determining
consensus on this topic, but with no particular official role, I
appreciate Ted's insistence on terminological precision.

For instance, I foolishly failed to cut off a debate about mixed case
lookup, which led to speculation about problems that nobody actually
has.  I was wrong to have let it go on, and I'd like to learn from
that mistake by not making it again.  Allowing discussions of more
than one character set is actually going to be worse, because some
people will forget that we're talking always about DNS labels, which
either have no character set at all or else are US-ASCII (and likely
LDH, at that).

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.