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

Mukund Sivaraman <muks@mukund.org> Mon, 17 September 2018 11:55 UTC

Return-Path: <muks@mukund.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 DAD99130DD6 for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 04:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 P1r2zu5CcXrq for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 04:55:57 -0700 (PDT)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id DB2BB1271FF for <dnsop@ietf.org>; Mon, 17 Sep 2018 04:55:56 -0700 (PDT)
Received: from jurassic (unknown [27.5.172.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 3733532C08FD; Mon, 17 Sep 2018 11:55:53 +0000 (UTC)
Date: Mon, 17 Sep 2018 17:25:50 +0530
From: Mukund Sivaraman <muks@mukund.org>
To: Petr =?utf-8?B?xaBwYcSNZWs=?= <petr.spacek@nic.cz>
Cc: dnsop@ietf.org
Message-ID: <20180917115550.GA11502@jurassic>
References: <b73f3dc7-b378-d5d8-c7a2-42bc4326fbae@nic.cz> <20180916095655.GA11121@jurassic> <20180917071414.7pb6elbooockzaa7@nic.fr> <20180917074327.GA13046@jurassic> <409968f7-bea2-fa14-67ba-3a6ea7feb837@bellis.me.uk> <20180917093028.GA3413@jurassic> <bec29c65-feef-0c4a-41ac-0d150f11590f@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <bec29c65-feef-0c4a-41ac-0d150f11590f@nic.cz>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TCZEgogea5W0mQsh1hsxjsDK5ac>
Subject: Re: [DNSOP] abandoning ANAME and standardizing CNAME at apex
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, 17 Sep 2018 11:55:59 -0000

Hi Petr

On Mon, Sep 17, 2018 at 12:29:13PM +0200, Petr Špaček wrote:
> Originally I thought that current workarounds for CNAME at apex (which
> are almost everywhere) deal with it in a more deterministic way.

Do you mean the current workarounds in resolver implementations?  These
can be brought into line going forward if there's a draft of expected
behavior.

I was sold when Evan presented the (basic) ANAME idea at a team meeting
at ISC and thought it was a fine idea. Now it seems that relaxing CNAME
to be a fallback would be the most painless and simple path. I
remembered reading something on dnsop@ and got to this thread. Other
ideas would create yet another chapter in the DNS book to implement
which seems excessive for little added benefit.

		Mukund