Re: [dnsext] New Version Notification for draft-barton-clone-dns-labels-fun-profit-00

Alex Bligh <alex@alex.org.uk> Tue, 08 March 2011 09:22 UTC

Return-Path: <alex@alex.org.uk>
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 32BF03A67AC for <dnsext@core3.amsl.com>; Tue, 8 Mar 2011 01:22:39 -0800 (PST)
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 rYpxNgc38cUD for <dnsext@core3.amsl.com>; Tue, 8 Mar 2011 01:22:38 -0800 (PST)
Received: from mail.avalus.com (mail.avalus.com [89.16.176.221]) by core3.amsl.com (Postfix) with ESMTP id 2C2B33A67A1 for <dnsext@ietf.org>; Tue, 8 Mar 2011 01:22:37 -0800 (PST)
Received: from [192.168.100.89] (unknown [193.128.116.237]) by mail.avalus.com (Postfix) with ESMTPSA id 4CF4CC562FB; Tue, 8 Mar 2011 09:23:50 +0000 (GMT)
Date: Tue, 08 Mar 2011 09:24:17 +0000
From: Alex Bligh <alex@alex.org.uk>
To: Doug Barton <dougb@dougbarton.us>, Nicholas Weaver <nweaver@icsi.berkeley.edu>
Message-ID: <7C043A33C72339E8A1FB6659@nimrod.local>
In-Reply-To: <4D758753.3090900@dougbarton.us>
References: <4D74E409.1060409@dougbarton.us> <79987316-C80C-4015-A3D3-77F8D2F33351@icsi.berkeley.edu> <4D758753.3090900@dougbarton.us>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: dnsext@ietf.org
Subject: Re: [dnsext] New Version Notification for draft-barton-clone-dns-labels-fun-profit-00
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Alex Bligh <alex@alex.org.uk>
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: Tue, 08 Mar 2011 09:22:39 -0000

--On 7 March 2011 17:33:07 -0800 Doug Barton <dougb@dougbarton.us> wrote:

> I think you're missing the whole point. :)  Users want to be able to use
> the variant labels (including things like being on the RHS of NS and MX
> records) so the idea is to deal with them on a basis that is as equal as
> possible.

(I've read the draft but am thinking about it before commenting, so don't
take this as a comment on the draft).

I am not sure Nick is missing the point. We do not *know* that users want
to use the variant labels on the RHS of NS and MX records (beyond the
obvious truism that it would be nice to do everything). I am guessing that
most users want to use the variant labels in URLs and email addresses, and
that's it.

Suzanne Woolf is attempting to gather some matrix of requirements and
balance them against disruption. Until such point (that might be never),
all we've got is different proposed solutions with different functionality.
What you're saying is that CLONE (apparently) allows the RHS of an NS
record to be a variant too, which differentiates it from (e.g.) a
CNAME/DNAME combination.

Out of interest, /why/ is a variant being on the RHS of an NS or MX record
useful? This is never visible to end users, and in the majority of use
cases thus far brought up, the RHS of the NS or the MX record gets to be
one user-illegible string beginning "xn--" rather than another illegible
string beginning "xn--".

-- 
Alex Bligh