Re: [DNSOP] Clarifying referrals (#35)

Paul Vixie <paul@redbarn.org> Mon, 13 November 2017 16:14 UTC

Return-Path: <paul@redbarn.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 D5B0C129B06 for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 08:14:16 -0800 (PST)
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 g648ajgE2mX3 for <dnsop@ietfa.amsl.com>; Mon, 13 Nov 2017 08:14:15 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54DE5120454 for <dnsop@ietf.org>; Mon, 13 Nov 2017 08:14:15 -0800 (PST)
Received: from [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc] (unknown [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 6D0B361FA2; Mon, 13 Nov 2017 16:14:14 +0000 (UTC)
Message-ID: <5A09C4D6.6080202@redbarn.org>
Date: Mon, 13 Nov 2017 08:14:14 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.20 (Windows/20171012)
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
CC: dnsop@ietf.org
References: <20171112075445.tf2ut5dxzhhnqe7l@mx4.yitter.info> <20171112131831.GA32208@laperouse.bortzmeyer.org> <20171113014445.ncldrwnuuvluecx7@mx4.yitter.info> <5A08FD96.8030907@redbarn.org> <20171113020736.ga7rzgst2hurb56h@mx4.yitter.info> <5A09068A.3030206@redbarn.org> <20171113032640.tbn7icsllm6jeeny@mx4.yitter.info>
In-Reply-To: <20171113032640.tbn7icsllm6jeeny@mx4.yitter.info>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/BRe7eUxPZTmTlzzqqdg8uP401ho>
Subject: Re: [DNSOP] Clarifying referrals (#35)
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, 13 Nov 2017 16:14:17 -0000


Andrew Sullivan wrote:
> Hi,
>
> This is quite a helpful response, thanks.  I wonder whether more of it
> ought to go in discussion (or a new draft), however.

i probably should not be involved in a new draft other than as a 
reviewer. (consider the fate of resimprove.)

> For I'm struck
> by this:
>
> On Sun, Nov 12, 2017 at 06:42:18PM -0800, Paul Vixie wrote:
>>> always be generated using only local data, and either contains the
>>> answer to the question or a referral to other name servers "closer" to
>>> the desired information.
>> the operative phrase is '"closer" to'. this is repeated in 4.3.1:
>
> If I ask the authoritative server for example.com about a name
> label.example.net, in a graph-theoretic sense the NS RRset for the
> root zone is clearly closer to label.example.net than anything else I
> can give.

dns is not that kind of graph.

if the qname is acetes.pa.dec.com and the query is being processed by 
the dec.com authority server who knows that pa.dec.com is a delegation, 
then pa.dec.com is closer to acetes.pa.dec.com than the root would be.

> The current approaches that people have for this are either NODATA
> responses and REFUSED.  Only the latter seems obviously consistent
> with the text, though I'm aware that there's controversy over using
> REFUSED here.

as i wrote during the SOPA wars, REFUSED has been widely used as an 
administrative denial, and repurposing it would not be effective at this 
late date.

see:

http://www.circleid.com/posts/20120111_refusing_refused_for_sopa_pipa/

-- 
P Vixie