Re: [DNSOP] refer-down

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 29 May 2018 03:29 UTC

Return-Path: <ajs@anvilwalrusden.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 7C06512D941 for <dnsop@ietfa.amsl.com>; Mon, 28 May 2018 20:29:16 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=FQwnuLaZ; dkim=pass (1024-bit key) header.d=yitter.info header.b=HsV6mdqk
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 tQ1sFC5fhgKZ for <dnsop@ietfa.amsl.com>; Mon, 28 May 2018 20:29:14 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4CA012D77A for <dnsop@ietf.org>; Mon, 28 May 2018 20:29:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 26F11BDEF9 for <dnsop@ietf.org>; Tue, 29 May 2018 03:28:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1527564524; bh=Dlg/r9BOH3H9yLvKKFKIuHKfPVA75q/SNodZfKnlWKg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=FQwnuLaZYxxvIMsyXHGlL88IJgtJ2nvmNbAO4Z3CY7LBaALA+iJ1p9kbHp0eWAceN P4SPi5kA5rE/UfH9eNEBohGccOFIY3fm0o6VsGYPvCFoqDrcfW534NzJvLRng+RfdZ 93JlhkEa6f4ZGxtdHZDczcuhQdsX/fvAEStRCqgI=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RJLvme6iLxUX for <dnsop@ietf.org>; Tue, 29 May 2018 03:28:42 +0000 (UTC)
Date: Mon, 28 May 2018 23:28:40 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1527564522; bh=Dlg/r9BOH3H9yLvKKFKIuHKfPVA75q/SNodZfKnlWKg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=HsV6mdqk4x6kCv3Bm5WExSCF7z+Kl0i6RP/Ts+fK3AK3iUeTZZIMg8VC7124Ydaul uzClGq5PJFh6XVSMzmpinCajfs7UqyAQoj7jeP/oa/j4z4uU2ubNL9ROpnI/pT3AuZ WEWLavrtoGHARsfyh/rUEgzyUtgT1GL0P5h83qGk=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20180529032839.GA18049@mx4.yitter.info>
References: <20180528184759.GI12038@mx4.yitter.info> <20180529013407.0C55F273EFA2@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180529013407.0C55F273EFA2@ary.qy>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kT8NPhBhPHW7aDT0e-u1incdU4Y>
Subject: Re: [DNSOP] refer-down
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: Tue, 29 May 2018 03:29:17 -0000

On Mon, May 28, 2018 at 09:34:06PM -0400, John Levine wrote:
> > Also, you're the only person who's commented directly and that makes
> > me think the WG isn't going to do much review of it
> 
> Sheesh, it's a national holiday in the US and UK today.  Some of us
> were out having picnics.

My apologies for being unclear.  My point was rather that the draft is
about to expire, and Joe and I created it entirely to draw away the
debate of how referrals _should_ happen from the terminology
document.  Tht was what I meant by "the only person".  As someone who
can barely manage to cope with emails at a 1 week interval any more,
I'm hardly likely to complain people don't get back the same day; but
I do apologise that wasn't clear.

> I like it because I like anything that makes the DNS simpler.  I'd
> make the advice clearer, authoritative servers that want to
> interoperate MUST refuse out of zone requests.

This is an interesting suggestion.  

> I'd also like to consider offering clearer advice on what do do when a
> recursive server gets an authoritative query.  Is there any situation
> other than misconfiguration or testing when that would happen?  Are we
> doing anyone a real favor by returning anything other than REFUSED?

You mean, when a server that is not authoritative for anything
nevertheless gets a query with RD==0?  I think that's fine.  How else
do you debug a cache?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com