Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt

Paul Wouters <paul@nohats.ca> Thu, 20 April 2017 23:48 UTC

Return-Path: <paul@nohats.ca>
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 71AF4129BCE for <dnsop@ietfa.amsl.com>; Thu, 20 Apr 2017 16:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 l2fRGfh7zSml for <dnsop@ietfa.amsl.com>; Thu, 20 Apr 2017 16:48:43 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40EED129B66 for <dnsop@ietf.org>; Thu, 20 Apr 2017 16:48:43 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w8Ftt41VYzCss; Fri, 21 Apr 2017 01:48:38 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492732118; bh=ESdMrglvwO5iZHujqCWj/1DQjn+yEWMdQEHsx53aFIg=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=W+RajctiheqCNW2T8yggrc5jMUoSJVuZ0Zax1R8wPb/cCqgjCxLI7KfagNxFcrWRV MzD0VHDaFfTXstARBI+u4wJno1OWT3O2yDJUL0McwTFlZuLOyHpc20RWBAC8FpdHsW dSiNTR+e1TLjlQtM94l+WmbC7Ns3mcOkgZmHBKSY=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id l-smJBe4D32Z; Fri, 21 Apr 2017 01:48:36 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 21 Apr 2017 01:48:35 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 88FF1418565; Thu, 20 Apr 2017 19:48:34 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 88FF1418565
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 687E140D811F; Thu, 20 Apr 2017 19:48:34 -0400 (EDT)
Date: Thu, 20 Apr 2017 19:48:34 -0400
From: Paul Wouters <paul@nohats.ca>
To: Evan Hunt <each@isc.org>
cc: dnsop <dnsop@ietf.org>
In-Reply-To: <20170420215155.GB96219@isc.org>
Message-ID: <alpine.LRH.2.20.999.1704201944070.18536@bofh.nohats.ca>
References: <20170414200316.86192.qmail@ary.lan> <CA3AE8E2-A54F-4F9D-A6F3-D754A6829B75@powerdns.com> <alpine.LRH.2.20.999.1704191436580.15622@bofh.nohats.ca> <20170420063648.GA73884@isc.org> <alpine.LRH.2.20.999.1704201650180.14463@bofh.nohats.ca> <20170420215155.GB96219@isc.org>
User-Agent: Alpine 2.20.999 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jHhrOiKwbA1GD_McuuU2MqGGq2E>
Subject: Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Apr 2017 23:48:44 -0000

On Thu, 20 Apr 2017, Evan Hunt wrote:

> Once again, the recursive resolver needn't be built in. It only has to be
> accessible -- via resolv.conf, for example.

Mmmm, populating auth servers based on at most an AD bit of something
from resolv.conf. Which more and more people are just pointing to
8.8.8.8. I don't think that's a good idea.

Maybe some good software and an internal-only ANAME special record
with a secure DNS helper app isn't too bad after all. But again,
if done well, would not require ANAME to ever go over the wire.

I think we've circled sufficiently around now that I'll step back and
let others chime in.

Paul