Re: [DNSOP] Fwd: New Version Notification for draft-ogud-dnsop-any-notimp-00.txt

Ralf Weber <dns@fl1ger.de> Fri, 06 March 2015 23:33 UTC

Return-Path: <dns@fl1ger.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175611A8730 for <dnsop@ietfa.amsl.com>; Fri, 6 Mar 2015 15:33:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.847
X-Spam-Level:
X-Spam-Status: No, score=0.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_NET=0.611, HOST_EQ_STATICB=1.372, SPF_PASS=-0.001] autolearn=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 1l0wHn2x0ZzM for <dnsop@ietfa.amsl.com>; Fri, 6 Mar 2015 15:33:47 -0800 (PST)
Received: from smtp.guxx.net (static.85-10-208-173.clients.your-server.de [85.10.208.173]) by ietfa.amsl.com (Postfix) with ESMTP id C3EE41A870D for <dnsop@ietf.org>; Fri, 6 Mar 2015 15:33:47 -0800 (PST)
Received: by nyx.guxx.net (Postfix, from userid 107) id 2D2AC5F40EA2; Sat, 7 Mar 2015 00:33:47 +0100 (CET)
Received: from PorcupineTree.nominum.com (PorcupineTree.ddns.nominum.com [64.89.225.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id B89895F40DCA; Sat, 7 Mar 2015 00:33:44 +0100 (CET)
Date: Fri, 06 Mar 2015 15:33:12 -0800
From: Ralf Weber <dns@fl1ger.de>
To: Paul Vixie <paul@redbarn.org>
Message-ID: <20150306233312.GC60793@PorcupineTree.nominum.com>
References: <20150306172715.24305.58649.idtracker@ietfa.amsl.com> <CAN6NTqw4n_mTqjGDsOc4kT3fvm1PaCWKt+AUPw+4GevQqG3Ymw@mail.gmail.com> <20150306182444.GA50555@PorcupineTree.nominum.com> <54F9FC8D.9050003@redbarn.org> <20150306213856.GA51222@PorcupineTree.nominum.com> <54FA2179.3000403@redbarn.org> <20150306223336.GA60793@PorcupineTree.nominum.com> <54FA2FEE.7000304@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <54FA2FEE.7000304@redbarn.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/WGO9_RLLZuRbzi4jB8VdNmDgVA4>
Cc: Olafur Gudmundsson <olafur@cloudflare.com>, dnsop@ietf.org
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-ogud-dnsop-any-notimp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 23:33:49 -0000

Moin!

On Fri, Mar 06, 2015 at 02:53:34PM -0800, Paul Vixie wrote:
>
> i'd appreciate not having to argue about whether the term "ACL" is one
> of art or one of practice. let's talk about what we're trying to
> accomplish in terms of protocol revision, rather than talking about what
> specific application-specific words we shouldn't use when describing
> those accomplishments.
And I wasn't talking about that. My point was and still is that we
should make the ACL or hell what you call it not a requirement in
the draft, at least not one that is mandatory.

> >  There may be applications that
> > may want to have a default behavior, thus we should not put ACL in the
> > draft.
> 
> i don't understand this statement. make the default "nobody". i thought
> you were disagreeing?
See above. I am fine with a draft that says one can implement an ACL to
allow requests. Lets try with some text for the section 3 of the draft:

A Recursive Resolver can answer with RCODE=0/ANCOUNT=0 to an ANY query
rather than the current content of it's cache. A recursive resolver can
implement a mechanism to allow certain hosts access to the cache content
with an ANY query.

is that what you want? I would be fine with that. I just don't want a
MUST on the ACL thing.

So long
-Ralf