IETF Logo Mail Archive

Re: [DNSOP] I-D Action: draft-vixie-dns-rpz-04.txt

bert hubert <bert.hubert@powerdns.com> Mon, 19 December 2016 09:39 UTC

Return-Path: <bert.hubert@powerdns.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 021FC129552 for <dnsop@ietfa.amsl.com>; Mon, 19 Dec 2016 01:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5
X-Spam-Level:
X-Spam-Status: No, score=-5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1] 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 zGY9srwkRE2M for <dnsop@ietfa.amsl.com>; Mon, 19 Dec 2016 01:39:18 -0800 (PST)
Received: from tmpmail.powerdns.com (tmpmail.powerdns.com [128.199.32.142]) by ietfa.amsl.com (Postfix) with ESMTP id E63E7129539 for <dnsop@ietf.org>; Mon, 19 Dec 2016 01:39:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tmpmail.powerdns.com (Postfix) with ESMTP id 6405D6C7EF; Mon, 19 Dec 2016 04:38:46 -0500 (EST)
Received: from tmpmail.powerdns.com ([127.0.0.1]) by localhost (tmpmail.powerdns.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j9Q80isokhAG; Mon, 19 Dec 2016 04:38:45 -0500 (EST)
Received: from server.ds9a.nl (unknown [IPv6:2001:470:1f15:bba::42]) by tmpmail.powerdns.com (Postfix) with ESMTP id CED4C6C7ED; Mon, 19 Dec 2016 04:38:45 -0500 (EST)
Received: by server.ds9a.nl (Postfix, from userid 1000) id 86860AC2DEC; Mon, 19 Dec 2016 10:38:46 +0100 (CET)
Date: Mon, 19 Dec 2016 10:38:46 +0100
From: bert hubert <bert.hubert@powerdns.com>
To: ac <ac@main.me>
Message-ID: <20161219093846.GA25654@server.ds9a.nl>
References: <20161219.101111.41661466.sthaug@nethelp.no> <20161219092509.0DBA5129452@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20161219092509.0DBA5129452@ietfa.amsl.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/k8Q5D8YYx1u9_W0YnNLiYvbJYgs>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-vixie-dns-rpz-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 19 Dec 2016 09:39:19 -0000

On Mon, Dec 19, 2016 at 11:24:33AM +0200, ac wrote:
> when there is an RFC that describers how to lie and then adds
> deception, this is no longer something to negotiate or to discuss much.

By this token any firewall is censorship and lies. Yet we still use them.

We have also documented ways to distribute blackholing via BGP for the
specific purpose of silencing traffic.

You don't stop something from happening by saying a standard is theft. 

So please realise this is something that people need. Best that they do it
in a standardized fashion.

> Is it okay to publish a draft defining a protocol on how to steal a resource? 
> or maybe defining a protocol for phishing? 

It is very much a protocol against phishing. 

	Bert

v2.23.0 | Report a Bug | By Email