RPZ & content control

[Shane Kerr]

James,

While I tend to agree that RPZ as a specific technology is mostly out of
ICANN's bailiwick, can we agree that widespread filtering of specific
domains is still probably something to track?

For example, if we discover that certain TLD are heavily blocked by ISP
then that may indicate some underlying problem with the way the TLD is
used.

Or if ICANN discovers that an IDN TLD is likely to be blocked then this
seems like something that matters to ICANN and its stakeholders.

Certainly if the NCSG has a reason to think that technology will be
used against its stakeholders than the NCSG has reason to be concerned
and investigate, IMHO.

Cheers,

--
Shane

At 2017-04-12 19:31:36 +0000
James Gannon <james at CYBERINVASION.NET> wrote:

> ??
> This has literally nothing to do with ICANN Compliance?
> 
> -James
> 
> From: NCSG-Discuss <NCSG-DISCUSS at LISTSERV.SYR.EDU<mailto:NCSG-DISCUSS at LISTSERV.SYR.EDU>> on behalf of Salanieta Tamanikaiwaimaro <sala at PASIFIKANEXUS.NU<mailto:sala at PASIFIKANEXUS.NU>>
> Reply-To: Salanieta Tamanikaiwaimaro <sala at PASIFIKANEXUS.NU<mailto:sala at PASIFIKANEXUS.NU>>
> Date: Wednesday 12 April 2017 at 19:17
> To: "NCSG-DISCUSS at LISTSERV.SYR.EDU<mailto:NCSG-DISCUSS at LISTSERV.SYR.EDU>" <NCSG-DISCUSS at LISTSERV.SYR.EDU<mailto:NCSG-DISCUSS at LISTSERV.SYR.EDU>>
> 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 <gbruen at knujon.com<mailto:gbruen at knujon.com>>  and he'll give you an update.
> 
> On Wed, Apr 12, 2017 at 12:50 AM, Niels ten Oever <lists at digitaldissidents.org<mailto:lists at digitaldissidents.org>> 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: sala at pasifikanexus.nu<mailto:sala at pasifikanexus.nu>
> Website: www.pasifikanexus.nu<http://www.pasifikanexus.nu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digitale handtekening
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20170413/fe2805bb/attachment.sig>