Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt

Evan Hunt <each@isc.org> Thu, 20 April 2017 06:36 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 8C95A12EB14 for <dnsop@ietfa.amsl.com>; Wed, 19 Apr 2017 23:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 APs7Qo7HTB0B for <dnsop@ietfa.amsl.com>; Wed, 19 Apr 2017 23:36:51 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 88D6F1200C1 for <dnsop@ietf.org>; Wed, 19 Apr 2017 23:36:51 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::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 71B513493BC; Thu, 20 Apr 2017 06:36:48 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 64D9E216C1E; Thu, 20 Apr 2017 06:36:48 +0000 (UTC)
Date: Thu, 20 Apr 2017 06:36:48 +0000
From: Evan Hunt <each@isc.org>
To: Paul Wouters <paul@nohats.ca>
Cc: dnsop <dnsop@ietf.org>
Message-ID: <20170420063648.GA73884@isc.org>
References: <20170414200316.86192.qmail@ary.lan> <CA3AE8E2-A54F-4F9D-A6F3-D754A6829B75@powerdns.com> <alpine.LRH.2.20.999.1704191436580.15622@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.20.999.1704191436580.15622@bofh.nohats.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/p4bu780UDO2TzvRaeK_JQTkewnA>
Subject: Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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 Apr 2017 06:36:52 -0000

On Wed, Apr 19, 2017 at 10:47:24PM -0400, Paul Wouters wrote:
> ANAME could just be a regular RRTYPE without any special handling,
> meaning "go look there for up to date information on A/AAAA". It could
> come along A/AAAA records using one of the existing bitmaps multi-type
> query proposals that have been suggested in the last two years.

But, because there are always going to be legacy servers, the client would
then need to send an ANAME query, and when it got no answer, send another
query for A and AAAA.

If clients were willing to do that, then they'd have been willing to use
SRV, and we'd have standardized on that long since.  Which would've been
fine, but browser vendors have had years to do it, and they never have.

Apparently, what they want is to send address queries and get redirected
answers. And if we can't make them do the smart thing, at least we can
give them an interoperable and standards-compliant way to do the dumb
thing.

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