IETF Logo Mail Archive

Re: [DNSOP] adoption mechanics and disclaimers wrt dns-rpz

Paul Wouters <paul@nohats.ca> Mon, 20 March 2017 18:46 UTC

Return-Path: <paul@nohats.ca>
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 570E5128CDC for <dnsop@ietfa.amsl.com>; Mon, 20 Mar 2017 11:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 hQWrqUGgWEFG for <dnsop@ietfa.amsl.com>; Mon, 20 Mar 2017 11:46:49 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 9F98A128C83 for <dnsop@ietf.org>; Mon, 20 Mar 2017 11:46:49 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3vn4fv4dngz1Kk; Mon, 20 Mar 2017 19:46:47 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1490035607; bh=iSJC67RWcX2RhP2Uzwu1zvDq7VK3hI65BIcTh8LtiEw=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=awDgd63PKydJXJeHZbz2jbk21fg/DVRlcx4y0gf3YnLtQqO+9u4mGXALTNhiuPNk9 Bd7op51+nCBB2uzaN8dxb6BcdVvxae/dXldsPhln7QdGGKOWW6cuoajhK3YIVKoexX A/7gDG/gXzv/7cmeVQ4BGHs7ypjWxrsWaytthB/I=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id lgm1BvubyqST; Mon, 20 Mar 2017 19:46:46 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 20 Mar 2017 19:46:45 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id C2C89446AE4; Mon, 20 Mar 2017 14:46:44 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca C2C89446AE4
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id AB17541652C6; Mon, 20 Mar 2017 14:46:44 -0400 (EDT)
Date: Mon, 20 Mar 2017 14:46:44 -0400
From: Paul Wouters <paul@nohats.ca>
To: Paul Vixie <vixie@fsi.io>
cc: dnsop@ietf.org
In-Reply-To: <2037898.ovR3IyGq7q@linux-hs2j>
Message-ID: <alpine.LRH.2.20.999.1703201444471.24328@bofh.nohats.ca>
References: <2232822.T0nP9Ksjf9@linux-hs2j> <6316017.BRF0sKMtdU@linux-hs2j> <alpine.LRH.2.20.999.1703201355000.24328@bofh.nohats.ca> <2037898.ovR3IyGq7q@linux-hs2j>
User-Agent: Alpine 2.20.999 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rS8wQb6B_9j2p36pXHIgciwZGOg>
Subject: Re: [DNSOP] adoption mechanics and disclaimers wrt dns-rpz
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, 20 Mar 2017 18:46:51 -0000

On Mon, 20 Mar 2017, Paul Vixie wrote:

> On Monday, March 20, 2017 6:10:32 PM GMT Paul Wouters wrote:
>> Anyway, I said "request the authors". It is not a demand. I'm sure you
>> fully understand my opinion and concern by now. I'll leave it to you to
>> accomodate that with any or no textual modification.
>
> how about "This document describes a method by which a security policy can be
> applied to DNS responses, possibly causing an end system to receive responses
> that do not correspond to actual DNS zone content."

That sounds good. Thanks for accomodating me.

Paul

v2.23.0 | Report a Bug | By Email