Re: [DNSOP] Minimum viable ANAME

Tony Finch <dot@dotat.at> Thu, 20 September 2018 09:16 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 9BB9A130E50 for <dnsop@ietfa.amsl.com>; Thu, 20 Sep 2018 02:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 RcIA2niHGrbY for <dnsop@ietfa.amsl.com>; Thu, 20 Sep 2018 02:16:17 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9767128D68 for <dnsop@ietf.org>; Thu, 20 Sep 2018 02:16:17 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id AA3EE1EC; Thu, 20 Sep 2018 05:16:16 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 20 Sep 2018 05:16:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=WVtqaE 3fLjzbCbmyr5RlX9J34bqjBGUotjlsTKWqgUc=; b=kYvOhaw6aHWFwn2JKlduYD ibAAP6Cyiksg0jK7YqX6bc1CR+29JHW6ZA7GsXqeF+ZNmzzyibtoNDPWABHCrGho cS4rMNRekvv0+UoM5/dp/X5mLkUfTDjHpQ+iRS+qHwPDpscFe5T3dFqaSEhmaCmR V7HTuOeMZ3gVhXU6BG+HyHTl9qKxz8UDV8ILDsJSlEFd+Os00RgupNqN+6YRUpBE sVMhSCB0SVTQWY36ofARurHQbc+6IKyDDJQX5lY2+JCXXGXRjNAcPDvfiaJAAk5I GuCcOIc6R0X1hhO1JiMjxPn/8rA4/6T53oVWotVBw1R53Iz02aTTf3wT/ZOCIbmw ==
X-ME-Proxy: <xmx:X2WjWxWTkkhTtxDlPuOqHltbNgk3N2s2KfVXcsZsK18eNNHNgVUj7Q> <xmx:X2WjW3cB8OULytkzgJAdSfigfZlbyM-JX4QvKt2k9jQq51lEeLy0TA> <xmx:X2WjW4kgvixz1N9Lc2GbUFKxNbe7Q7oRqu2OswwO9M-qVSOZGWr0dg> <xmx:X2WjW-Z0kAIUL3SIsnb-jtaYgD09oVxeRay3mt1NOuwRg1078Gt_HQ> <xmx:X2WjW0HzrL8C7Bz98vEQ2WYvdu4nkJRwxGVR9BW1DNH6_uwouwMzjw> <xmx:YGWjW7rw0ZJ8qLp6AIzTm0mWQq5CKl2cYVCqrYUFD83nV0R1-gQdLA>
X-ME-Sender: <xms:X2WjW7aMMPozgaoQoqqNrfmTx51wPW_ZlXmsgXahrNPy_2spwrbGfA>
Received: from [192.168.1.231] (unknown [195.147.34.210]) by mail.messagingengine.com (Postfix) with ESMTPA id 5F03D102DD; Thu, 20 Sep 2018 05:16:15 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Tony Finch <dot@dotat.at>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <20180920061343.GA754@jurassic>
Date: Thu, 20 Sep 2018 10:16:12 +0100
Cc: John Levine <johnl@taugh.com>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <712C2478-D7F8-4396-A975-74ED86337022@dotat.at>
References: <20180919201401.8E0C220051382A@ary.qy> <08C8A740-D09B-4577-AF2A-79225EDB526B@dotat.at> <20180920061343.GA754@jurassic>
To: Mukund Sivaraman <muks@mukund.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/KSCFoqw_DOpy08sGXzQ8j_4FyMg>
Subject: Re: [DNSOP] Minimum viable ANAME
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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 Sep 2018 09:16:19 -0000

> On 20 Sep 2018, at 07:13, Mukund Sivaraman <muks@mukund.org> wrote:
> 
> I don't follow how ANAME, if resolvers have to implement it, can be
> deployed within a few years, 

Resolvers don’t “have to”  implement it: resolver support is just an optimisation that helps when the target is on a CDN. ANAME is mostly just a provisioning side hack to automatically keep address records up-to-date, so it can be deployed unilaterally and it will “just work” with existing software.

The other options we have been discussing require a forklift upgrade before they can be relied on, and until that is complete they offer no advantage to zone publishers.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at