Re: [DNSOP] Fundamental ANAME problems

Måns Nilsson <mansaxel@besserwisser.org> Mon, 05 November 2018 08:35 UTC

Return-Path: <mansaxel@besserwisser.org>
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 4E95F12D4EB for <dnsop@ietfa.amsl.com>; Mon, 5 Nov 2018 00:35:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.222
X-Spam-Level:
X-Spam-Status: No, score=-3.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 LuPlqjkBumZW for <dnsop@ietfa.amsl.com>; Mon, 5 Nov 2018 00:35:36 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 7C73C12EB11 for <dnsop@ietf.org>; Mon, 5 Nov 2018 00:35:30 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 68C6D9D98; Mon, 5 Nov 2018 09:35:28 +0100 (CET)
Date: Mon, 5 Nov 2018 09:35:28 +0100
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Tony Finch <dot@dotat.at>
Cc: Brian Dickson <brian.peter.dickson@gmail.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-ID: <20181105083526.GA12204@besserwisser.org>
References: <CAH1iCirXYsYB3sAo8f1Jy-q4meLmQAPSFO-7x5idDufdT_unXQ@mail.gmail.com> <alpine.DEB.2.20.1811021543210.24450@grey.csi.cam.ac.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S"
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1811021543210.24450@grey.csi.cam.ac.uk>
X-URL: http://vvv.besserwisser.org
X-Clacks-Overhead: "GNU Sir Terry Pratchett"
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/N36JcuhskOGlNxdc3Kyn1Dgevtk>
Subject: Re: [DNSOP] Fundamental ANAME problems
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: Mon, 05 Nov 2018 08:35:38 -0000

Subject: Re: [DNSOP] Fundamental ANAME problems Date: Fri, Nov 02, 2018 at 04:39:09PM +0000 Quoting Tony Finch (dot@dotat.at):
> It's really good to see more discussion about ANAME.

I agree. 
 
> I think a resolver-side or client-side alternative (like the various
> web-specific record types we have been discussing) is defintely soemthing
> we should aim for in the long term, but that isn't what this work is
> about.

IMNSHO _any_ work on "fixing CNAMES at apex" that gets traction is 
a spanner in the works for what we seem to agree is a better solution.
A interim fix will be deployed and stall every attempt at DTRT.

I am well aware of "perfect being the enemy of good enough" but I'm not
certain DNAME is "good enough". 

-- 
Måns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE           SA0XLR            +46 705 989668
Now KEN and BARBIE are PERMANENTLY ADDICTED to MIND-ALTERING DRUGS ...