IETF Logo Mail Archive

Re: [DNSOP] New draft for ALIAS/ANAME type

Evan Hunt <each@isc.org> Mon, 03 April 2017 22:25 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 A36CB1293FC for <dnsop@ietfa.amsl.com>; Mon, 3 Apr 2017 15:25:33 -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 NSqiZ26F7M_5 for <dnsop@ietfa.amsl.com>; Mon, 3 Apr 2017 15:25:32 -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 64A44128B44 for <dnsop@ietf.org>; Mon, 3 Apr 2017 15:25:32 -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 2BAB03493AC; Mon, 3 Apr 2017 22:25:31 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 1F75B216C1C; Mon, 3 Apr 2017 22:25:31 +0000 (UTC)
Date: Mon, 03 Apr 2017 22:25:31 +0000
From: Evan Hunt <each@isc.org>
To: Paul Wouters <paul@nohats.ca>
Cc: Dan York <york@isoc.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Message-ID: <20170403222531.GB72941@isc.org>
References: <CA+nkc8Bwc6eQz6YPAnMLNjvHm4POLTyvsTRQC5Pn+R4iTzaB-g@mail.gmail.com> <20170330230806.6273.qmail@ary.lan> <20170330231358.GA92307@isc.org> <3A4E2834-2BD4-4DC3-9D5A-A15B3DCDA738@isoc.org> <alpine.LRH.2.20.999.1704031546230.16478@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.1704031546230.16478@bofh.nohats.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_kzUgHcVfm-4zbfKlAhUrh91V-w>
Subject: Re: [DNSOP] New draft for ALIAS/ANAME type
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: Mon, 03 Apr 2017 22:25:34 -0000

On Mon, Apr 03, 2017 at 03:48:49PM -0400, Paul Wouters wrote:
> As Evan said, there should not be any code in an authoritative server
> that requires it to do recursive validation.

I said what now?  Had I recently had dental surgery?  I don't remember
this.

If you mean the comment I made on the ANAME thread, I was just saying
that it's possible to implement CNAME flattening without a built-in
resolver; several implementations already do.

(I do believe an authoritative server should be *able* to operate without
built-in recursive code, and enabling such operation is on my list of
things to get around to someday in BIND: if auth servers could be
configured to use external resolvers, then security bugs affecting
only the recursive code wouldn't be any risk to them. But I definitely
wouldn't phrase that as "there should not be any code".)

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

v2.23.0 | Report a Bug | By Email