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

"John Levine" <johnl@taugh.com> Sat, 08 April 2017 22:41 UTC

Return-Path: <johnl@taugh.com>
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 99B651205F0 for <dnsop@ietfa.amsl.com>; Sat, 8 Apr 2017 15:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[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 Z5AEExHAtzA0 for <dnsop@ietfa.amsl.com>; Sat, 8 Apr 2017 15:41:40 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A1A11200C1 for <dnsop@ietf.org>; Sat, 8 Apr 2017 15:41:39 -0700 (PDT)
Received: (qmail 82961 invoked from network); 8 Apr 2017 22:41:38 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 8 Apr 2017 22:41:38 -0000
Date: 8 Apr 2017 22:41:16 -0000
Message-ID: <20170408224116.58162.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Cc: paul@nohats.ca
In-Reply-To: <alpine.LRH.2.20.999.1704081826570.9031@bofh.nohats.ca>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vhnKMPB_GvvVzx7315ykekgj7DA>
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: Sat, 08 Apr 2017 22:41:42 -0000

>If these are the premises for ANAME, and its special handling, wouldn't
>it be better to generalise asking for multiple records (eg A + AAAA
>+ ANAME) where ANAME has no special handling on its own? And then do the
>generealised multi-query-at-once using one of the previously suggested
>proposals?

But that doesn't solve the original problem.  Clients ask for an A or
an AAAA record, and that's what they want to get back.  The ANAME is
really just a provisioning hack built into the authoritative server
and, depending on the implementation, maybe the cache.

I suppose they might ask for both A and AAAA but that's a separate
problem, even though it might use a similar mechanism.

R's,
John