Re: [dnsext] Some thoughts on the updated aliasing draft
Cary Karp <ck@nic.museum> Mon, 28 March 2011 06:09 UTC
Return-Path: <ck@nic.museum>
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 B6E8C3A6816 for <dnsext@core3.amsl.com>; Sun, 27 Mar 2011 23:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 X7eNeSGBqgIn for <dnsext@core3.amsl.com>; Sun, 27 Mar 2011 23:09:16 -0700 (PDT)
Received: from nic.frd.net (nic.frd.net [83.145.59.99]) by core3.amsl.com (Postfix) with ESMTP id C8FCA3A67D0 for <dnsext@ietf.org>; Sun, 27 Mar 2011 23:09:15 -0700 (PDT)
Received: from [192.168.1.10] (h47n6-hy-d6.ias.bredband.telia.com [217.210.140.47]) (authenticated bits=0) by nic.frd.net (8.13.8/8.13.8) with ESMTP id p2S6AgOE001476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Mar 2011 08:10:42 +0200
Message-ID: <4D902663.5030107@nic.museum>
Date: Mon, 28 Mar 2011 08:10:43 +0200
From: Cary Karp <ck@nic.museum>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: Suzanne Woolf <woolf@isc.org>
References: <20110327192512.90424.qmail@joyce.lan> <47131.1301261826@nsa.vix.com> <20110327224749.GB10959@bikeshed.isc.org>
In-Reply-To: <20110327224749.GB10959@bikeshed.isc.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (nic.frd.net [83.145.59.99]); Mon, 28 Mar 2011 08:10:42 +0200 (CEST)
X-yoursite-MailScanner-Information: Please contact the ISP for more information
X-yoursite-MailScanner-ID: p2S6AgOE001476
X-yoursite-MailScanner: Found to be clean
X-yoursite-MailScanner-From: ck@nic.museum
Cc: dnsext@ietf.org
Subject: Re: [dnsext] Some thoughts on the updated aliasing draft
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 Mar 2011 06:09:17 -0000
Quoting Suzanne > Well....I hope they will speak for themselves, but I think at this > point that what "the IDN people" want from the DNS people is some real > sense of what's possible, with roughly what tradeoffs. I think they > want any news we can give them, even if it's bad (and I'm not even > sure this is bad news). > > We can go into this a little more (briefly) in the session Monday > afternoon-- Andrew and anyone else who was in the ICANN IDN meetings > in San Francisco can probably shed some light. The impression I got from the ICANN IDN meetings in San Francisco was that the people who frequent such events have a strong qualitative sense of there being a problem but haven't yet managed to articulate it clearly, much less solve it. What might constitute a solution from their perspective is similarly elusive, but in ICANN terms would mean something that can serve as a basis for "consensus policies" (the sidestepping of which caused the present headache, in the first place). The expectation on the ICANN side has always been that the technical community, by virtue of its superior understanding of the quantifiable intricacies of the DNS, would be able to extrapolate whatever it needs to know about "the problem" from the discussion as it is being conducted in the ICANN venue. There is no basis for assuming that the potential insufficiency of that belief can be successfully communicated, so the best we're going to be able to do here is second guess something that might actually help. If that were an unequivocal statement of bad news, I have no idea how it would be received, but suspect that it's unsafe to make any assumptions about its potential for bringing the discussion to an end. /Cary
- [dnsext] Some thoughts on the updated aliasing dr… Ted Hardie
- Re: [dnsext] Some thoughts on the updated aliasin… John Levine
- Re: [dnsext] Some thoughts on the updated aliasin… Paul Vixie
- Re: [dnsext] Some thoughts on the updated aliasin… Suzanne Woolf
- Re: [dnsext] Some thoughts on the updated aliasin… Ted Hardie
- Re: [dnsext] Some thoughts on the updated aliasin… John Levine
- Re: [dnsext] Some thoughts on the updated aliasin… Paul Vixie
- Re: [dnsext] Some thoughts on the updated aliasin… Suzanne Woolf
- Re: [dnsext] Some thoughts on the updated aliasin… John Levine
- Re: [dnsext] Some thoughts on the updated aliasin… Suzanne Woolf
- Re: [dnsext] Some thoughts on the updated aliasin… Mark Andrews
- Re: [dnsext] Some thoughts on the updated aliasin… Masataka Ohta
- Re: [dnsext] Some thoughts on the updated aliasin… John R. Levine
- Re: [dnsext] Some thoughts on the updated aliasin… Cary Karp
- Re: [dnsext] Some thoughts on the updated aliasin… Xiaodong Lee
- Re: [dnsext] Some thoughts on the updated aliasin… Paul Vixie
- Re: [dnsext] Some thoughts on the updated aliasin… Alex Bligh
- Re: [dnsext] Some thoughts on the updated aliasin… Tony Finch
- Re: [dnsext] Some thoughts on the updated aliasin… Tony Finch
- Re: [dnsext] Some thoughts on the updated aliasin… John Levine
- Re: [dnsext] Some thoughts on the updated aliasin… Douglas Otis
- Re: [dnsext] Some thoughts on the updated aliasin… Florian Weimer
- Re: [dnsext] Some thoughts on the updated aliasin… Tony Finch
- Re: [dnsext] Some thoughts on the updated aliasin… Doug Barton