Re: [DNSOP] dnames, was My "toxic" remark at the mic today

"Joe Abley" <jabley@hopcount.ca> Fri, 06 November 2015 14:44 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1201A90CF for <dnsop@ietfa.amsl.com>; Fri, 6 Nov 2015 06:44:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmSP7lLGO7aO for <dnsop@ietfa.amsl.com>; Fri, 6 Nov 2015 06:44:09 -0800 (PST)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9058D1A914D for <dnsop@ietf.org>; Fri, 6 Nov 2015 06:44:09 -0800 (PST)
Received: by vkfw189 with SMTP id w189so15380913vkf.2 for <dnsop@ietf.org>; Fri, 06 Nov 2015 06:44:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=SBmeMgW2xQZfqI05XF/bJbXXi3yc3W8LI9+KAIjWJQc=; b=Li9Hg7sNfvhQinsGUMiux0UDule+xwZl7OaZUcLwSPI+4jQX1mztzxmKsI8VHvoehb EE2LBO6AvQ21CwFK692sx6UXMvHsoEn32h37zK5lF5VsY8NUI+4EPKzNacmuBvswZcxC r7dox1wbQd9eufY/ogFA58thvd8VNZcgvWZGc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=SBmeMgW2xQZfqI05XF/bJbXXi3yc3W8LI9+KAIjWJQc=; b=gsLBcHHrbQaZ2FLeQ36JmD/zerHeDfsTgnswyy0cv/JfBHs083LHMK49DioAFGFvp5 5QnfWEoLS9dGGa5ciaSRevJIXKIS+8ZF8jSdjtALXMyhM1QC2u1l05p9PoBTfY1/ziTq 67Fdub2ireSEfO7MnfqA/dxQ58qnipWtw38GVfiFxR7PO3uQov8ngEt1lFlgCZ/RvcWC F8PVQDFuuw7Wvq28ciNsP5fPvS9Ja3YneqJcCf578+NAXK2K0xrhW7z4DRalp6lIj34F 8wCgC7AO1baRvTtP3FfUhy28LgPh8RsFVBGcstjORp+SgrpIOo9kFz4E/HxtCKj+rP1D Ei9g==
X-Gm-Message-State: ALoCoQnaFXZ22zc4Fbzc5WCt57ZNox42OzzetuB+bAnvwh9WfLVpqYhatgwK/jlrKWmXD/IzqV8h
X-Received: by 10.31.9.13 with SMTP id 13mr13437711vkj.128.1446821048605; Fri, 06 Nov 2015 06:44:08 -0800 (PST)
Received: from [172.19.128.14] (135-23-68-43.cpe.pppoe.ca. [135.23.68.43]) by smtp.gmail.com with ESMTPSA id 133sm368036vkf.9.2015.11.06.06.44.06 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 06 Nov 2015 06:44:07 -0800 (PST)
From: Joe Abley <jabley@hopcount.ca>
To: John R Levine <johnl@taugh.com>
Date: Fri, 06 Nov 2015 09:44:06 -0500
Message-ID: <846F82EC-E937-4275-9335-69FC7A96747A@hopcount.ca>
In-Reply-To: <alpine.OSX.2.11.1511061607350.79472@ary.local>
References: <20151105105009.53009.qmail@ary.lan> <90A15CB0-C8C4-46E1-9E0E-DB249C61A8F1@frobbit.se> <alpine.OSX.2.11.1511061607350.79472@ary.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.2r5141)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/7ykcd4NjA9UmdI8_gWpCYK9sQ88>
Cc: dnsop@ietf.org, ajs@anvilwalrusden.com
Subject: Re: [DNSOP] dnames, was My "toxic" remark at the mic today
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 14:44:11 -0000


On 6 Nov 2015, at 2:17, John R Levine wrote:

>>> I'm not sure how toxic it is, but I agree that we are unlikely to 
>>> have
>>> anything useful to say on the topic.
>>
>> Speaking personally, I do not see DNAME toxic, but the question has 
>> almost always been:
>
> To clarify, it's us offering advice on what goes into the root zone 
> that's toxic, not dname specifically.

I get the distinction.

To the tangential point of whether it's reasonable or practical to have 
DNAME in the root zone (side-stepping the issue you were talking about, 
about who should have opinions about that and who should make decisions) 
there was some work commissioned by ICANN a number of years ago and 
carried out by João Damas to evaluate the behaviour of many different 
code bases to a root zone that contained DNAME. The context of that work 
was the potential solution to use DNAME in the root zone to provision 
variant IDN TLDs (see ICANN board resolution 10 adopted on 12 March 
2010), but the report was arguably general enough to be instructive in 
this different context.

   
https://www.icann.org/resources/board-material/resolutions-2010-03-12-en#10
   https://www.icann.org/news/announcement-2011-05-24-en

Additionally, there was an experiment carried out to quantify the 
availability of DNAME support in the real world for AS112 by George 
Michaelson and Geoff Huston. The results are documented in an appendix 
of RFC 7535.


Joe