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

Mukund Sivaraman <muks@mukund.org> Mon, 17 September 2018 07:43 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 438DB130DE2 for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 00:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 X5oaceGs5pt8 for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 00:43:34 -0700 (PDT)
Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:140:644b::225]) by ietfa.amsl.com (Postfix) with ESMTP id CA007128D0C for <dnsop@ietf.org>; Mon, 17 Sep 2018 00:43:33 -0700 (PDT)
Received: from jurassic (unknown [27.5.243.238]) (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 458A432C072F; Mon, 17 Sep 2018 07:43:30 +0000 (UTC)
Date: Mon, 17 Sep 2018 13:13:27 +0530
From: Mukund Sivaraman <muks@mukund.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-ID: <20180917074327.GA13046@jurassic>
References: <b73f3dc7-b378-d5d8-c7a2-42bc4326fbae@nic.cz> <20180916095655.GA11121@jurassic> <20180917071414.7pb6elbooockzaa7@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180917071414.7pb6elbooockzaa7@nic.fr>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jhRvjEHV9d89rDNGvIbWAWBhrdo>
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 07:43:36 -0000

Hi Stephane

On Mon, Sep 17, 2018 at 09:14:14AM +0200, Stephane Bortzmeyer wrote:
> On Sun, Sep 16, 2018 at 03:26:56PM +0530,
>  Mukund Sivaraman <muks@mukund.org>; wrote 
>  a message of 66 lines which said:
> 
> > Adding resolver support (to resolvers that don't have it, i.e.,
> > vs. RFC 1035) does not appear to break current DNS, i.e., it can be
> > proposed now.
> 
> [Algorithm deleted]
> 
> The difficult thing is not to specify what the new resolvers will have
> to do, but to describe what will happen with the current
> resolvers. What will happen when "CNAME at apex" will be deployed,
> assuming X % of the resolvers will not be upgraded?

I fully realise what you're saying.

The suggestion is only to require support in resolvers going forward for
CNAME co-existing with other types for now. That should not break any
detail of how DNS is used today.

Whether CNAME + other types at apex can be used in the future would be
an operational decision for that time of the world.

Similar things can be said of other proposals.

* If SRV for HTTP is brought into use, what about X% of user agents that
  don't have support for it?

* If a new RR type is introduced, what about X% of resolvers that do not
  support it?

Although it changes current DNS protocol, AFAICT there does not seem to
be anything badly wrong with allowing CNAME + other types at a node,
where the CNAME is considered a fallback when the required type doesn't
exist.

Repeating what the original post's author Petr said, this seems to be a
simpler change than adding other types for similar benefit, esp. when
hacks are already necessary to workaround the case of CNAME and other
types co-existing that are seen in the DNS.

		Mukund