Re: [hrpc] Censorship
Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 22 March 2022 07:22 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 3FAF23A0B58
for <hrpc@ietfa.amsl.com>; Tue, 22 Mar 2022 00:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.661
X-Spam-Level:
X-Spam-Status: No, score=0.661 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1,
FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001,
NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H5=0.001,
RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665,
T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001]
autolearn=no 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 XhVlWPVL7Yuz for <hrpc@ietfa.amsl.com>;
Tue, 22 Mar 2022 00:22:06 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr
[132.168.224.13])
(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 087CC3A0B57
for <hrpc@irtf.org>; Tue, 22 Mar 2022 00:22:05 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21])
by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP
id 22M7M2Fh001768; Tue, 22 Mar 2022 08:22:02 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1])
by localhost (Postfix) with SMTP id 74F32202562;
Tue, 22 Mar 2022 08:22:02 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr
[132.166.192.13])
by pisaure.intra.cea.fr (Postfix) with ESMTP id 6264B200C1A;
Tue, 22 Mar 2022 08:22:02 +0100 (CET)
Received: from [10.11.240.12] ([10.11.240.12])
by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP
id 22M7M020000646; Tue, 22 Mar 2022 08:22:00 +0100
Content-Type: multipart/alternative;
boundary="------------5fVb3fOkBYGjFVrlk1gKPNtE"
Message-ID: <f3e96f23-fe0c-fe86-ca35-326734848b2c@gmail.com>
Date: Tue, 22 Mar 2022 08:22:00 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Content-Language: fr
To: Desiree Miloshevic <miloshevic@gmail.com>
Cc: hrpc@irtf.org
References: <6.2.5.6.2.20220314013727.07d5c430@elandnews.com>
<CAGVFjMLY6i5jGSPrc5zTri7Zhanq4QWjKfrhBsUK8Mu-re4bWw@mail.gmail.com>
<CAN1qJvA5-Yx8qgx7TZ-k0sk6ZSWdd5=THF_eRHh5W112Zu2XQQ@mail.gmail.com>
<6996c4e4-db8e-9b30-bf65-b52c7b96c344@nielstenoever.net>
<CAN1qJvBM+4FSxAin8-SkyG0h18bm4FiEBW_CCtD+Q-EM4sqr1g@mail.gmail.com>
<67F9D62F-9DC2-41DC-9142-58CDDC2B2CFA@gmail.com>
<9c328c22-216e-6dcd-b5e0-95a1c1796900@gmail.com>
<138C9949-D67E-4E13-80CA-42E558FAEF70@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <138C9949-D67E-4E13-80CA-42E558FAEF70@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/F3e3BdakwbsTluA0I5SAsb9bSy8>
Subject: Re: [hrpc] Censorship
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: hrpc discussion list <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>,
<mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>,
<mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2022 07:22:11 -0000
Hi, When they say the RIPE meeting is "14h-15h30 (UTC+1)" - what does it mean? Does it mean they consider 14h to be 14h UTC and I need to add 1 hour to it now in order to find the right start time for Paris? Or does it mean they consider 14h to be Paris time, so I dont need to add 1 hour to it now? (various people consider various answers to this question, generally speaking, but I need to know what does this meeting organizer think, so I dont miss it) Yours, Alex Le 21/03/2022 à 17:57, Desiree Miloshevic a écrit : > > >> On 21 Mar 2022, at 14:59, Alexandre Petrescu >> <alexandre.petrescu@gmail.com> wrote: >> > Hi Alex >> >> Le 19/03/2022 à 13:18, Desiree Miloshevic a écrit : >>> Hi all >>> >>> Fwiw - there’s a panel next Tuesday on the topic of Internet >>> sanctions and connectivity, organised by the RIPE Coop WG. >>> It does clash with some parts of the IETF program, but it maybe a >>> good place to continue the discussion thread. >>> >>> https://www.ripe.net/participate/ripe/wg/active-wg/coop/remote-sessions/remote-session-22-march-2022 >> >> >> Thanks, I registered. >> >> The URL provides a list of 4 other URLs with interesting text, some >> of which were already mentioned. ( >> >> * Keep The Internet Open <https://keepitopen.net/> >> * Multistakeholder Imposition of Internet >> Sanctions<https://www2.computable.nl/uploads/pdf/multistakeholder-imposition-of-internet-sanctions.pdf> >> * Civil Society letter to Biden Administration re. >> Sanctions<https://cdt.org/wp-content/uploads/2022/03/Civil-society-letter-to-Biden-Admin-re-Russia-sanctions-and-internet-access-10-March-2022-1.pdf> >> * RIPE NCC Response to Request from Ukrainian >> Government<https://www.ripe.net/publications/news/announcements/ripe-ncc-response-to-request-from-ukrainian-government>) >> >> All 4 references point to long letters speaking official words for >> 'err.. not sure... better wait'. >> >> There are other references that say otherwise - why aren't they >> cited? I mean, all these reports of internet cuts and restores, the >> DDoSes, the invisible sites, the 'unkillable internet' statements, >> the oneweb cancelled launches (Internet in space), the social media >> cancellations or almost-cancellation, the reports of desires of >> self-cut, the 6G project plans avoiding Russian partners, the .su >> abnormality, the internet coverage of bomb shelters, the temporary >> lack of communication to sensor networks in sensible areas… >> > The list is long indeed. > The above documents were cited because some of their signatories > participate at the discussion and may argue one way or the other. >> >> What will be the take-aways, the next steps, the actionable items >> after the session? >> > It is for the RIPE community and the participants to decide. > > Desiree > -- >> >> Alex >> >> >>> >>> Desiree >>> — >>> >>> >>>> On 18 Mar 2022, at 13:48, farzaneh badii <farzaneh.badii@GMAIL.COM> >>>> wrote: >>>> On Wed, Mar 16, 2022 at 12:47 PM Niels ten Oever >>>> <mail@nielstenoever.net> wrote: >>>> >>>> Dear Farzaneh, >>>> >>>> Thank you very much for your email, please allow me to respond >>>> in-line: >>>> >>>> On 15-03-2022 17:40, farzaneh badii wrote: >>>> > Hello, >>>> > Just to provide you with a little bit of context, it is true >>>> that there has not been a collective action about this, but >>>> certainly we have raised the issue of sanctions at ICANN, some >>>> did about participation at the IETF, we have focussed on RIR's >>>> and sanctions. I provided a proposal about RIRs defense pact >>>> against sanctions applied to Internet infrastructure after the >>>> unfortunate events in Afghanistan (didn't get anywhere). Many >>>> of us have been working on these issues for years because well >>>> because we are either from those regions and/or understand the >>>> implications in real time or because some operators actually >>>> believe in interconnectedness and non-discriminatory treatment >>>> at infrastructure level. >>>> >>>> I believe in that as well, that is why I think that >>>> institutions that limit the interconnectedness of others should >>>> not get away with it. >>>> >>>> >>>> How? By gathering some people to take collective action against >>>> networks that you will decide whether they are military or >>>> propaganda? I even saw in these debates that some called >>>> interconnectivity Internet exceptionalism. The initial discussions >>>> we had, the intention was not even providing sanction relief, that >>>> was not even what some people had in mind or even knew about the >>>> effects. Some were upset that RIPE had declared that it is neutral >>>> (I interpret in favor of interconnectivity). So we were discussing >>>> what can be done. We were in the middle of the debate about how and >>>> if we can go about demilitarization without harming connectivity >>>> and what are the best remedies during war and conflict that we saw >>>> your initiative emerged. Which in my opinion included some people >>>> that thought sanctions should be imposed and some believed that >>>> sanctions should not be imposed or if imposed should be imposed in >>>> a certain way so they came up with this tortured document that can >>>> be contradictory even. All with good intentions. No doubt. >>>> >>>> >>>> >>>> > Anyhow let me tell you what has been done so far, I am sure I >>>> am missing the great work of many others about these issues. >>>> > ccTLDs and IP addresses were threatened by sanctions and >>>> jurisdictions for many years, one interesting case was request >>>> to attach .IR .SY etc to terrorist victims in the US, read >>>> about it here, ICANN in that instance sent its lawyers to argue >>>> against the >>>> attachment:https://www.icann.org/en/system/files/files/calderon-cardona-motion-to-quash-writs-29jul14-en.pdf<https://www.icann.org/en/system/files/files/calderon-cardona-motion-to-quash-writs-29jul14-en.pdf> >>>> > Sanctions and ICANN: (2017, a multistakeholder! >>>> recommendation to receive a general OFAC >>>> licensehttps://www.internetgovernance.org/2017/01/13/icanns-jurisdiction-sanctions-and-domain-names/<https://www.internetgovernance.org/2017/01/13/icanns-jurisdiction-sanctions-and-domain-names/> >>>> > A bit of background about domain names being hampered by >>>> sanctions:https://www.internetgovernance.org/2017/04/08/icann-jurisdiction-and-domain-name-issues-report-your-problems/<https://www.internetgovernance.org/2017/04/08/icann-jurisdiction-and-domain-name-issues-report-your-problems/> >>>> > More background on how sanctions affect domain name >>>> registrants:https://www.internetgovernance.org/2017/01/13/icanns-jurisdiction-sanctions-and-domain-names/<https://www.internetgovernance.org/2017/01/13/icanns-jurisdiction-sanctions-and-domain-names/> >>>> > New gTLD and sanctions: >>>> https://circleid.com/posts/20220217-oneworld-.someinternet-new-gtld-registries-and-sanctioned-countries<https://circleid.com/posts/20220217-oneworld-.someinternet-new-gtld-registries-and-sanctioned-countries> >>>> > Sanctions and >>>> Afghanistan:https://labs.ripe.net/author/farzaneh-badiei/the-tragedy-of-internet-infrastructure-in-afghanistan/<https://labs.ripe.net/author/farzaneh-badiei/the-tragedy-of-internet-infrastructure-in-afghanistan/> >>>> > Sanctions and CDNs: (by Ensafi and >>>> other)https://ensa.fi/papers/403forbidden_imc18.pdf<https://ensa.fi/papers/403forbidden_imc18.pdf>,https://digitalmedusa.org/sanctions-global-internet-connectivity-and-content-delivery-networks/<https://digitalmedusa.org/sanctions-global-internet-connectivity-and-content-delivery-networks/> Where >>>> can this be discussed? League of Internet networks? >>>> > >>>> > >>>> > The thing that makes me super uncomfortable with this >>>> initiative is that I believe it was born out ofa revenge >>>> fantasy >>>> <https://digitalmedusa.org/internet-governance-revenge-fantasy-or-helping-ukraine/> >>>> that will do no good for Ukraine but it will affect >>>> connectivity, despite all the good intentions and nice >>>> principles they set out. >>>> > >>>> > I am not sorry about the shameless publicity of the materials, >>>> >>>> Could you elaborate what you mean with this? >>>> >>>> >>>> In conferences, sometimes when people want to promote their own >>>> papers and writings, they make a joke that they are sorry for >>>> shameless self-promotion or shameless publicity. But I am not sorry >>>> for promoting these materials. Because obviously some even think we >>>> have not been focussing and discussing sanctions until now! Hope >>>> that is enough elaboration . >>>> >>>> >>>> > we have been shouting about this and knocking on many doors >>>> for at least a decade. Many have focussed on these issues and >>>> can tell you exactly what the problems are when you act at >>>> the infrastructure level and introduce discrimination. I am in >>>> favor of demilitarization of the Internet. I have spoken >>>> against cruel dictatorships, I will be the first to sign up for >>>> any private collective that would come out effectively against >>>> the atrocities of these regimes to their people and others on >>>> the Internet and provide relief for sanctions and dream to >>>> demilitarize the Internet. But this initiative unfortunately >>>> has way too many pitfalls to endorse it. >>>> > >>>> > >>>> > >>>> >>>> In the resources above you describe there are two major problems: >>>> >>>> 1. Civilians are more impacted by sanctions than institutions >>>> 2. Companies over-comply, resulting in more harm and less >>>> precise sanctions. >>>> >>>> I think point 2. is relatively easily addressed if the >>>> implementation 100% operationalizable as it was intended >>>> (through BGP and RPZ). Point 1. depends on the design of the >>>> sanctions, which can be even better designed if that is done in >>>> collaboration with the implementers, correct? >>>> >>>> >>>> Well, reducing years of work to two points and then providing some >>>> ambiguous technical solution is not my favorite approach to things. >>>> Could you tell me how your implementation through BGP and RPZ would >>>> work that could address civilians being impacted. And I suppose you >>>> mean military organizations, not just "institutions". From the >>>> outside looking in, your list is going to be more about who has the >>>> AS than what the network behavior is. Which will have >>>> devastating effects for the Internet. But I would be happy to hear >>>> more. >>>> As for sanctions to be done in collaboration with the implementers >>>> (you mean those who have to comply with sanctions), you won't be >>>> able to do that because "sanctions" are laws and regulatory >>>> approaches and the governments will not share that power with >>>> others. Sanction regimes have been in place for years, you can't >>>> tell the govs to ditch their regime and come participate in your >>>> multistakeholder circle, it is already the law of land. If you >>>> wanted to tell how companies should comply with sanctions, then >>>> that would have been a nice initiative (I won't comment on >>>> effectiveness, I don't think the legal counsels would have allowed >>>> their companies to join!). But this initiative wants to impose >>>> sanctions in a nice way. It's like coming up with a jail system and >>>> say mine is nicer cause it's private, voluntary and multistakeholder. >>>> This initiative has nothing new but the word "multistakeholder" in >>>> it. It's even debatable whether that's new because we actually >>>> practiced "multistakeholder" compliance with sanctions at ICANN. >>>> Governments have taken the list-based approach for years. >>>> Governments have even tried to bring due process to the unfair >>>> decisions, both by issuing general licenses and waivers as well as >>>> providing a judicial system! The unintended consequences of >>>> sanction regimes are plenty which this group cannot address with >>>> its current design, and boycott at the infrastructure level can >>>> lead to discrimination and harming connectivity and not necessarily >>>> to demilitarization of the Internet. >>>> >>>> >>>> >>>> Especially since multistakeholder sanctions (or boycott if you >>>> will) could be designed with those who implement it, and there >>>> they could also be relatively easy reversed or adapted. >>>> >>>> Best, >>>> >>>> Niels >>>> > >>>> > >>>> > On Tue, Mar 15, 2022 at 11:54 AM Mallory Knodel >>>> <mknodel@cdt.org<mailto:mknodel@cdt.org>> wrote: >>>> > >>>> > On Monday, March 14, 2022, S Moonesamy >>>> <sm+ietf@elandsys.com >>>> <mailto:sm%2Bietf@elandsys.com><mailto:sm%2Bietf@elandsys.com >>>> <mailto:sm%252Bietf@elandsys.com>>> wrote: >>>> > >>>> > Hi Mallory, >>>> > >>>> > As for my view, I'm with Stephen in that I don't >>>> think it's a >>>> > particularly effective approach that the PCH >>>> letter takes and yet the >>>> > political risks are tremendous. If we are to >>>> build the capacity in >>>> > internet governance spaces like the IRTF/IETF-- >>>> and I would argue that >>>> > is a far better goal than a new IG body-- it had >>>> better be on rock solid >>>> > ground in terms of understanding efficacy and >>>> tradeoffs. >>>> > >>>> > >>>> > One of the questions which Bill raised was whether it >>>> was appropriate to do nothing in response to the recent >>>> events. There is anecdotal evidence that some "digital" >>>> certificates were revoked. I doubt that it has anything to do >>>> with protocol considerations or either of the two statements. >>>> > >>>> > There was agenda item nearly a decade ago [1]. There >>>> hasn't been much open discussion on those topics in response to >>>> the recent events. This could mean two things: >>>> > >>>> > (i) There isn't the capacity in those spaces; or >>>> > >>>> > (ii) People in those spaces are not interested in >>>> those topics. >>>> > >>>> > >>>> > I would argue it’s worth building that capacity and >>>> garnering that interest. >>>> > >>>> > -Mallory >>>> > >>>> > >>>> > >>>> > >>>> 1.https://documents-dds-ny.un.org/doc/UNDOC/LTD/G12/147/10/PDF/G1214710.pdf<https://documents-dds-ny.un.org/doc/UNDOC/LTD/G12/147/10/PDF/G1214710.pdf> >>>> > >>>> > >>>> > >>>> > -- >>>> > Mallory Knodel >>>> > CTO, Center for Democracy and Technology >>>> > gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 >>>> A271 BD3C C780 >>>> > >>>> > >>>> > _______________________________________________ >>>> > hrpc mailing list >>>> > hrpc@irtf.org<mailto:hrpc@irtf.org> >>>> > >>>> https://www.irtf.org/mailman/listinfo/hrpc<https://www.irtf.org/mailman/listinfo/hrpc> >>>> > >>>> > >>>> > _______________________________________________ >>>> > hrpc mailing list >>>> >hrpc@irtf.org >>>> >https://www.irtf.org/mailman/listinfo/hrpc >>>> >>>> -- >>>> Niels ten Oever, PhD >>>> Postdoctoral Researcher - Media Studies Department - University >>>> of Amsterdam >>>> Affiliated Faculty - Digital Democracy Institute - Simon Fraser >>>> University >>>> Non-Resident Fellow 2022-2023 - Center for Democracy & Technology >>>> Associated Scholar - Centro de Tecnologia e Sociedade - >>>> Fundação Getúlio Vargas >>>> Research Fellow - Centre for Internet and Human Rights - >>>> European University Viadrina >>>> >>>> W:https://nielstenoever.net >>>> E:mail@nielstenoever.net >>>> T: @nielstenoever >>>> P/S/WA: +31629051853 >>>> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3 >>>> >>>> Read my latest article on Internet infrastructure governance in >>>> Globalizations >>>> here:https://www.tandfonline.com/doi/full/10.1080/14747731.2021.1953221 >>>> >>>> _______________________________________________ >>>> hrpc mailing list >>>> hrpc@irtf.org >>>> https://www.irtf.org/mailman/listinfo/hrpc >>>> >>>> _______________________________________________ >>>> hrpc mailing list >>>> hrpc@irtf.org >>>> https://www.irtf.org/mailman/listinfo/hrpc >>> >>> >>> _______________________________________________ >>> hrpc mailing list >>> hrpc@irtf.org >>> https://www.irtf.org/mailman/listinfo/hrpc >> _______________________________________________ >> hrpc mailing list >> hrpc@irtf.org >> https://www.irtf.org/mailman/listinfo/hrpc >
- [hrpc] Censorship Vittorio Bertola
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Vittorio Bertola
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Eliot Lear
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Eliot Lear
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship avri
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] Censorship Bill Jouris
- Re: [hrpc] Censorship Jens Finkhaeuser
- Re: [hrpc] Censorship Vittorio Bertola
- Re: [hrpc] Censorship Paul Wouters
- Re: [hrpc] Censorship Eliot Lear
- Re: [hrpc] Censorship Mallory Knodel
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Bill Jouris
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship farzaneh badii
- Re: [hrpc] Censorship Paul Wouters
- Re: [hrpc] Censorship Paul Wouters
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship Andrew Sullivan
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship Jens Finkhaeuser
- Re: [hrpc] Censorship Bill Woodcock
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Andrew Sullivan
- [hrpc] draft-irtf-hrpc-association (was Re: Censo… Andrew Sullivan
- Re: [hrpc] draft-irtf-hrpc-association (was Re: C… Niels ten Oever
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Andrew Sullivan
- Re: [hrpc] Censorship Jens Finkhaeuser
- Re: [hrpc] ***SPAM**** Re: Censorship Stephen Farrell
- Re: [hrpc] Censorship bzs
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] ***SPAM**** Re: Censorship Mallory Knodel
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] ***SPAM**** Re: Censorship Bill Woodcock
- Re: [hrpc] Censorship Mallory Knodel
- Re: [hrpc] ***SPAM**** Re: Censorship Mallory Knodel
- Re: [hrpc] ***SPAM**** Re: Censorship Niels ten Oever
- Re: [hrpc] Censorship farzaneh badii
- Re: [hrpc] ***SPAM**** Re: Censorship Eliot Lear
- Re: [hrpc] Censorship Andrew Sullivan
- Re: [hrpc] ***SPAM**** Re: Censorship Mallory Knodel
- Re: [hrpc] ***SPAM**** Re: Censorship Melinda Shore
- Re: [hrpc] Censorship Stephen Farrell
- Re: [hrpc] ***SPAM**** Re: Censorship Eliot Lear
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship Niels ten Oever
- Re: [hrpc] Censorship farzaneh badii
- Re: [hrpc] Censorship Desiree Miloshevic
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship Desiree Miloshevic
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship Alexandre Petrescu
- Re: [hrpc] Censorship S Moonesamy
- Re: [hrpc] RIPE Cooperation Working Group Remote … Alexandre Petrescu