IETF Logo Mail Archive

Re: [DNSOP] Clarifying referrals (#35)

Dick Franks <rwfranks@acm.org> Wed, 29 November 2017 22:24 UTC

Return-Path: <rwfranks@gmail.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 70BD5124234 for <dnsop@ietfa.amsl.com>; Wed, 29 Nov 2017 14:24:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DRbE58TbsSbd for <dnsop@ietfa.amsl.com>; Wed, 29 Nov 2017 14:24:17 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDC47120721 for <dnsop@ietf.org>; Wed, 29 Nov 2017 14:24:16 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id y82so38147229wmg.1 for <dnsop@ietf.org>; Wed, 29 Nov 2017 14:24:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5aTiteDyEBCL0Il4cGyyCQDvD33pkBZ/O05Bl8YTGt8=; b=FGoJbPGL2BBG5La2isqH5x/ya2OHzXpI2EXS65LYFSiQ4g0B8LzjfhW98ZI1UluBkP Qhety6Qyd/BsM4ZbPs7UnlPfOsvDaJZNoNjW0l+VIf2tn/ZEOagsKXlmHWgvqArsbGZk RhzwB7R694oTp9pOAMm4kmPCk5Ao9UW1aygVkjhUfZtGDmRoLDD6FAxnMRg+EzgDWIkP FBuJu5KVHXd3JhXniI7tJ7zxyN1Rbfg0ItuU7tSboNqPzjAF5S6GCgEksJFA4dyAE8Om 8GFiP+/Fkml6YUcEmHTGjJJWuJVaMj8OnIy/X4FAbgS8bvb7cKiKk5XlSzU0PNSiSnd8 HZcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5aTiteDyEBCL0Il4cGyyCQDvD33pkBZ/O05Bl8YTGt8=; b=hHG9YmUE09IxoiYk2sib2wOO/WXts8IuVM+8/p8NpJ6q2qASg9+vvzxDy/lw9kJwss +VxWnJQACy5ta4EbOZzheGYEcteSD8poD2kMoPHbsumSLbOY96pVb51DdXc/+iQk8mD4 UuzlBGX3VpVInNGFtw60RemV4GBr+kF2udohpKD4c2eDrGjhj+6StywD408HpvJVpkPz vsYXoFV1VkpzU56YZSAQ2/kNQIImnvMcIwr4gXmF2HPZQGgY2PpZKmcWEzL8dSys5YAH 8rz/g2F/p7RmEl2RgpbQqZt9jVEMA13lrmAkcXFAMcpdm1jTKU4rwthxVXMpMK58pqAQ ztaA==
X-Gm-Message-State: AJaThX76LuZdgetbwaXENVfZsedQsgBtuECO/1hXeJQIVdNdzQ3eDFNU LTaFY3lK+w+7fzXRNbYcXM/QyDIK7nuFK5r+Yd8=
X-Google-Smtp-Source: AGs4zMZOWyImtIGNyonZlfnSaXX42E7p7dfhJD7Obh2CYs8nZJmVyybCW4q0gpO/t2HEVZvRCi9artbRtM3J9Jjofts=
X-Received: by 10.28.141.211 with SMTP id p202mr197548wmd.61.1511994255507; Wed, 29 Nov 2017 14:24:15 -0800 (PST)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.223.151.197 with HTTP; Wed, 29 Nov 2017 14:23:34 -0800 (PST)
In-Reply-To: <20171129212354.vu4zmki3pi3qnhzz@mx4.yitter.info>
References: <20171128195025.ifzwsjk42wz7ard6@mx4.yitter.info> <FAA4A6D6-1454-4705-B87F-1FB96CC50658@isc.org> <20171129014436.sx546yjwvobepnyp@mx4.yitter.info> <8E36C30A-A7BC-4908-BE06-6D2B8B469006@isc.org> <20171129015303.kthpahbi6w6m645d@mx4.yitter.info> <AE976F3F-0270-4484-BCE4-FE0E9BF9D03E@isc.org> <20171129020347.b3zq3rcwsubmrlhh@mx4.yitter.info> <476FF2A7-DB80-40B6-917A-2675497DD6FC@isc.org> <20171129121706.4zh4kgx3wmtucmpc@mx4.yitter.info> <CAKW6Ri4T1h0n2r-Zp5xUUvW4n+u4oFPww2SDRnqwQMBF_wjY0g@mail.gmail.com> <20171129212354.vu4zmki3pi3qnhzz@mx4.yitter.info>
From: Dick Franks <rwfranks@acm.org>
Date: Wed, 29 Nov 2017 22:23:34 +0000
X-Google-Sender-Auth: AqcgjMP3_d_rvatyZqz7G-VQ7u4
Message-ID: <CAKW6Ri6paj5FZL1m_7AEbLqfBe7YNrFxw9nGEd7ZB+xHKg7bfA@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114709ea8086c7055f2698c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/a9ipx8iT2zd_B_HnpTe2zKUuK70>
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: Wed, 29 Nov 2017 22:24:19 -0000

On 29 November 2017 at 21:23, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> On Wed, Nov 29, 2017 at 09:18:39PM +0000, Dick Franks wrote:
> >
> > And said referral could be to an arbitrary node in the DNS tree,  i.e.
> > possibly "upward"?
> >
> > Or am I missing something?
>
> That depends on whether you believe the later part of the algorithm in
> RFC 1034 (where it says to do things from the cache) is part of the
> "referral" part, particularly in a mixed-mode server where it has
> received a query with RD=0.  The list appears to have strong feelings
> about that.  It's why Joe and I wrote draft-sullivan-dnsop-refer-down.
>

Mark's example involved two unrelated (which I mistakenly referred to as
arbitrary) zones, and a server having authoritative data for both.
Cached data not involved.

Until Mark's intervention, I was convinced that referrals were downwards
only.
I was trying to establish if this creates a counter-example, which might
require
me to unconvince myself.





> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

v2.23.0 | Report a Bug | By Email