Re: [DNSOP] ALT-TLD and (insecure) delgations.

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 04 February 2017 02:13 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A4C1295F1 for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 18:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 cbcAM1r255En for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 18:13:57 -0800 (PST)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id DFD6D127735 for <dnsop@ietf.org>; Fri, 3 Feb 2017 18:13:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 715E711649 for <dnsop@ietf.org>; Sat, 4 Feb 2017 02:14:01 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6K0eMX3uzdAD for <dnsop@ietf.org>; Sat, 4 Feb 2017 02:14:00 +0000 (UTC)
Received: from mx2.yitter.info (192-0-220-231.cpe.teksavvy.com [192.0.220.231]) by mx2.yitter.info (Postfix) with ESMTPSA id A9ABF1162D for <dnsop@ietf.org>; Sat, 4 Feb 2017 02:14:00 +0000 (UTC)
Date: Fri, 03 Feb 2017 21:13:53 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170204021353.GF67739@mx2.yitter.info>
References: <CAHw9_i+8PA3FQx8FqW-xQ_96it7k-g5UrMB7fxARUi1gwQ++hw@mail.gmail.com> <20170201204455.6nymmjlj5lzq2ect@mycre.ws> <CAHw9_iJ50jWgsAe+hRKUtubfAtpt7+GEeCKEASzypcf86+4nYA@mail.gmail.com> <20170204015158.GB67739@mx2.yitter.info> <5BB1A3F5-5EFB-4164-9720-68E262E58636@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5BB1A3F5-5EFB-4164-9720-68E262E58636@fugue.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/LdP6eXG575Ud6IEF8IOc-FirRj0>
Subject: Re: [DNSOP] ALT-TLD and (insecure) delgations.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 04 Feb 2017 02:13:58 -0000

On Fri, Feb 03, 2017 at 08:54:59PM -0500, Ted Lemon wrote:
> On Feb 3, 2017, at 8:51 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> > If the resolver "has a local zone for alt" -- I think this means it is
> > authoritative for that zone -- why would it ask the root about it at
> > all?
> 
> As long as the stub resolver isn't validating, it's no problem. If it is validating, then the recursive resolver can't fool the stub resolver if there's a secure denial of existence.
> 

Right, that's always been the problem with using this _for the DNS_.
Homenet has no choice in that, because the whole point of the homenet
name is precisely to enable in-homenet DNS without reference to the
global DNS.  I think you're quite correct that we need to decide
whether alt is to be used for those purposes.  I'm not convinced
that's so useful.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com