Re: [DNSOP] abandoning ANAME and standardizing CNAME at apex

Tony Finch <dot@dotat.at> Mon, 25 June 2018 15:42 UTC

Return-Path: <dot@dotat.at>
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 9874F130EC9 for <dnsop@ietfa.amsl.com>; Mon, 25 Jun 2018 08:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 iZGK3ol2h_GT for <dnsop@ietfa.amsl.com>; Mon, 25 Jun 2018 08:42:44 -0700 (PDT)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (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 9D2E4130DCE for <dnsop@ietf.org>; Mon, 25 Jun 2018 08:42:44 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:40585) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1fXTdY-000Fgj-dQ (Exim 4.91) (return-path <dot@dotat.at>); Mon, 25 Jun 2018 16:42:40 +0100
Date: Mon, 25 Jun 2018 16:42:40 +0100
From: Tony Finch <dot@dotat.at>
To: Paul Wouters <paul@nohats.ca>
cc: dnsop@ietf.org, Ray Bellis <ray@bellis.me.uk>
In-Reply-To: <alpine.LRH.2.21.1806251104490.18905@bofh.nohats.ca>
Message-ID: <alpine.DEB.2.11.1806251637060.916@grey.csi.cam.ac.uk>
References: <CAJhMdTO2kj+nUqESg3ew=wwZuB9OzkJE6pST=mae7pHiEk4-Qw@mail.gmail.com> <20180619190213.B76962846E19@ary.qy> <20180622182752.GA83312@isc.org> <af9b422a-90a0-b204-70d6-12566d7b65dc@bellis.me.uk> <alpine.DEB.2.11.1806251459510.916@grey.csi.cam.ac.uk> <alpine.LRH.2.21.1806251104490.18905@bofh.nohats.ca>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/AozgPHTAXcqIcmWJWQffH39TldM>
Subject: Re: [DNSOP] abandoning ANAME and standardizing CNAME at apex
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 25 Jun 2018 15:42:50 -0000

Paul Wouters <paul@nohats.ca>; wrote:
> On Mon, 25 Jun 2018, Tony Finch wrote:
>
> > That isn't required if the ANAME target records are fetched/updated by an
> > out-of-band provisioning process.
>
> Then you might as well use that mechanism to update A/AAAA records and
> skip the intermediate ANAME?

ANAME will add two things beyond a provisioning-only setup:

* a standard way to signal to dynamic auth servers where to get A/AAAA
  records from

* a way to signal to recursives that they might get a better answer if
  they query the target themselves

Even for a provisioning-only setup, ANAME will give the zone admin a
standard way to configure the provisioning process. That's what I mostly
want it for.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>;  http://dotat.at/
a just distribution of the rewards of success