IETF Logo Mail Archive

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

Evan Hunt <each@isc.org> Mon, 17 September 2018 16:11 UTC

Return-Path: <each@isc.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 D6640130E82 for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 09:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 nIateHKs_0dK for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 09:11:24 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 AABC9130E81 for <dnsop@ietf.org>; Mon, 17 Sep 2018 09:11:24 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 2C2773AB042; Mon, 17 Sep 2018 16:11:24 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 14BA6216C1C; Mon, 17 Sep 2018 16:11:24 +0000 (UTC)
Date: Mon, 17 Sep 2018 16:11:24 +0000
From: Evan Hunt <each@isc.org>
To: Mukund Sivaraman <muks@mukund.org>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-ID: <20180917161124.GA39810@isc.org>
References: <b73f3dc7-b378-d5d8-c7a2-42bc4326fbae@nic.cz> <20180916095655.GA11121@jurassic> <20180917071414.7pb6elbooockzaa7@nic.fr> <20180917074327.GA13046@jurassic>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180917074327.GA13046@jurassic>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Fom05wUObBG2fTyRXaGgGu-ex3U>
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 16:11:26 -0000

On Mon, Sep 17, 2018 at 01:13:27PM +0530, Mukund Sivaraman wrote:
> 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?

They're no worse off than they already were. The old methods would still
work just as well or badly as they do today.

If apex CNAME were declared legitimate, then people using legacy resolvers
*would* be worse off than they are now.

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.

v2.23.0 | Report a Bug | By Email