??

This has literally nothing to do with ICANN Compliance?



-James



From: NCSG-Discuss <[log in to unmask]<mailto:[log in to unmask]>> on behalf of Salanieta Tamanikaiwaimaro <[log in to unmask]<mailto:[log in to unmask]>>

Reply-To: Salanieta Tamanikaiwaimaro <[log in to unmask]<mailto:[log in to unmask]>>

Date: Wednesday 12 April 2017 at 19:17

To: "[log in to unmask]<mailto:[log in to unmask]>" <[log in to unmask]<mailto:[log in to unmask]>>

Subject: Re: RPZ & content control



Thanks for picking this up Niels.



The At Large Community has been up at arms on this issue frequently in the past and has made numerous submissions to ICANN's Compliance Team through the ALAC or through the ALS's or individual members.  For institutional memory, in that department you may wish to connect with   Garth Bruen <[log in to unmask]<mailto:[log in to unmask]>>  and he'll give you an update.



On Wed, Apr 12, 2017 at 12:50 AM, Niels ten Oever <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Hi all,



Have you all followed the discussion around RPZ ? It is a

(proposed)protocol which allows for the blacklisting of certain

addresses, reportedly to address malware, but you can imagine how this

could be used differently.



https://tools.ietf.org/html/draft-ietf-dnsop-dns-rpz-00



https://dnsrpz.info/



http://www.circleid.com/posts/20100728_taking_back_the_dns/



Is this a discussion that has also been held in ICANN, or is this a

'let's route around ICANN'-kind of solution?



Cheers,



Niels



PS Sorry if I have missed earlier discussions on this.







--

Niels ten Oever

Head of Digital



Article 19

www.article19.org<http://www.article19.org>



PGP fingerprint    8D9F C567 BEE4 A431 56C4

                     678B 08B5 A0F2 636D 68E9







--

Salanieta Tamanikaiwaimaro

Director

Pasifika Nexus

P.O Box 17862

Suva

FIJI



Cell: +679 7656770

Tel: +679 3362003

E: [log in to unmask]<mailto:[log in to unmask]>

Website: www.pasifikanexus.nu<http://www.pasifikanexus.nu>