Re: [DNSOP] Client Validation - filtering validation?

S Moonesamy <sm+ietf@elandsys.com> Tue, 28 April 2020 19:30 UTC

Return-Path: <sm@elandsys.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 6E5553A0A94 for <dnsop@ietfa.amsl.com>; Tue, 28 Apr 2020 12:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 nucDdxmPFGG5 for <dnsop@ietfa.amsl.com>; Tue, 28 Apr 2020 12:30:31 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id B80013A0A9F for <dnsop@ietf.org>; Tue, 28 Apr 2020 12:30:31 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.162.161]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 03SJUAvf000696 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Apr 2020 12:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1588102223; x=1588188623; i=@elandsys.com; bh=DrBA9p2mL/w759DuNP3jq26RxOPrRhjZ/ehuL9c4kBo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NXoWRqLlnnFLriSScy521JAAjp6wdLqVT1fttP3KOzLhyRB3I94jXxvoa1/gLt89w a1HqY6KFWlHm4CVifJ/s4jPPVTMmKC5S4WphWXqL3bjZlBMKVHOhQ/XIgxx6CbVo+f PPePu/8Y9acCXY/uMMTcWBHntSPLqGzK+NiMH/Rg=
Message-Id: <6.2.5.6.2.20200428121847.081a29e8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 28 Apr 2020 12:29:49 -0700
To: Paul Wouters <paul@nohats.ca>, dnsop@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Brian Dickson <brian.peter.dickson@gmail.com>, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
In-Reply-To: <alpine.LRH.2.21.2004280934590.18623@bofh.nohats.ca>
References: <CAHPuVdV9eSCLQOqMF0cq8fHcuSZs7nCgjhHMfMoaV5H=ekbtSA@mail.gmail.com> <CAHPuVdUh4UTP5pH_X83pm8OvY7juEotSYT6FLbVyE4_S-ev9Bg@mail.gmail.com> <71d22908-b0a9-5f0c-585e-0d10aa3edc8a@nic.cz> <2119709.gsHikbp680@linux-9daj> <CAH1iCiprfBNuMPWeraogqE9vR-UesZ_BWEzzeXQQGM1AZxipFw@mail.gmail.com> <843057379.5811.1588069262749@appsuite-gw2.open-xchange.com> <alpine.LRH.2.21.2004280934590.18623@bofh.nohats.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jCk3kG_cooyY0LVXveMdErt3IcM>
Subject: Re: [DNSOP] Client Validation - filtering validation?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Apr 2020 19:30:34 -0000

Hi Paul,
At 06:38 AM 28-04-2020, Paul Wouters wrote:
>There is only one method where you can trust the filtering service. That
>is that they offer you the filtered data in a neutralized fashion. I
>have already been waiting a few years for the RPZ draft to pass the ISE
>publication process so the IETF can work on the bis document that moves
>the censored data into the authoritative section. That way, you get
>all the data innoculated. Clients not supporting this will not see
>this data and get filtered. Clients supporting this can talk to an
>enduser if one is available to say their data was filtered and present
>a choice on accepting the filter or not.
>
>I have poked Paul Vixie and the ISE a number of times on the RPZ draft.
>I even gave them another full review, but it seems nothing is happening
>to move this draft forward.

I found a WG draft (expired) from 2017 about RPZ.  I am not sure why 
it stalled in DNSOP.  There is also a 2018 draft (expired).  I 
vaguely recall looking at a draft.  However, proposed changes were 
not accepted.

Regards,
S. Moonesamy