IETF Logo Mail Archive

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

Paul Wouters <paul@nohats.ca> Mon, 25 June 2018 15:05 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 292C9130DFD for <dnsop@ietfa.amsl.com>; Mon, 25 Jun 2018 08:05:39 -0700 (PDT)
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 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 AaOqHOof9gOg for <dnsop@ietfa.amsl.com>; Mon, 25 Jun 2018 08:05:36 -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 717D6130DD9 for <dnsop@ietf.org>; Mon, 25 Jun 2018 08:05:36 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 41DstQ0HgBz398; Mon, 25 Jun 2018 17:05:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1529939134; bh=VS/KyevsxhqIeldr3ubtNq/xIqStdjWqYCCXddT9kZo=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=QM+X2nHAhn8sOUxO4gPWI3+VEkhgTaJOW6rFztrGY2NJdezQeiMIFhdrkpr9jlcd6 glxTRRIhGQZWzQGwy2Qs5dKR4cH0s9swAbrixROqqHLfO5p0XQ8iB7zMTovq+FOo5I RVb7z2ysjGOEfH/J9SaWUSbl3FZfU3hRwZ1FYuoE=
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 r-gKOjHLPn4i; Mon, 25 Jun 2018 17:05:32 +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; Mon, 25 Jun 2018 17:05:32 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 57388D3; Mon, 25 Jun 2018 11:05:31 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 57388D3
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 4D47A4215A44; Mon, 25 Jun 2018 11:05:31 -0400 (EDT)
Date: Mon, 25 Jun 2018 11:05:31 -0400
From: Paul Wouters <paul@nohats.ca>
To: Tony Finch <dot@dotat.at>
cc: Ray Bellis <ray@bellis.me.uk>, dnsop@ietf.org
In-Reply-To: <alpine.DEB.2.11.1806251459510.916@grey.csi.cam.ac.uk>
Message-ID: <alpine.LRH.2.21.1806251104490.18905@bofh.nohats.ca>
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>
User-Agent: Alpine 2.21 (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/XD8QJmj1WeoWOUfty5QmgqFdABk>
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:05:39 -0000

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?

Paul

v2.23.0 | Report a Bug | By Email