Re: [Pearg] descriptive censorship work: draft-hall-censorship-tech

Shivan Sahib <> Fri, 17 May 2019 02:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D2CDE12033B for <>; Thu, 16 May 2019 19:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eir46Xuh2XUK for <>; Thu, 16 May 2019 19:23:51 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8F82212032E for <>; Thu, 16 May 2019 19:23:51 -0700 (PDT)
Received: by with SMTP id e184so9610714ite.1 for <>; Thu, 16 May 2019 19:23:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nvr8fWybffwSyC5OzUnfzF08IY5E2YFw/z6Cx8nH7jo=; b=ERmQRuWtLLmi5TFpdc9oju2AHTN4b/QODsOLt3k3FAa2v/u7YlYch3cpNfZDvSRZ22 ATDpDAZBY1944AE1iCHbF6/OLu/FekL5RV3rx9JaujElZB7dix4gUyV9OdiRWdm0f66B em2wzZA2hOCKrZcTa6paxYm25L4GNmejbjoiI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nvr8fWybffwSyC5OzUnfzF08IY5E2YFw/z6Cx8nH7jo=; b=KOFr7i26SzEmhVLnrxT0po6cuU1P20SzowKQAK6RCOJ9OVQgWydJ/hzeOP10Nnzg5y USm1MOvumKzxrBnR+mrjx8PVRiUWuOXW5PqKUgov5uS+odUELdWZnkkXre9QfhOHmFZ3 ZKn/42Z+ahCVqhFXziW7WF8EtYPw5nsmc8ucLxg85NJxcFj2Ra0rUfU5IEVepEGUj3E4 Ep1WqCUdwp34LAksV/UBNByVWz6o4CBwdddjVRyVbN2O5817PMp5E22Awrtlx4cpIXDk 2IktzYMBFQzVXf6lTjcPgaXtsU6I/6N0V21KcVje68FFeJJpVeMXwGPd4bqsiWRee5Ix NTUg==
X-Gm-Message-State: APjAAAXBR+C5xfuAf0RxTAcZ2+SpxoKJdrLAAtWv8trpkx1kuszlwZxv 1mQnPJGWIFSoDKaxXTSWODBf7vXv9v5Nt2nNqNFXzg==
X-Google-Smtp-Source: APXvYqx14ntqY8EdIjnXLx7hFwCtM2NbQMH0Ja/pGsvH3Aiim6N+KBupQayTB4/y7T3wZNP+/hGqF1AMYJUQJfjPeRM=
X-Received: by 2002:a24:ac58:: with SMTP id m24mr810068iti.65.1558059830630; Thu, 16 May 2019 19:23:50 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Shivan Sahib <>
Date: Thu, 16 May 2019 19:23:40 -0700
Message-ID: <>
To: Joseph Lorenzo Hall <>
Cc:, Stan Adams <>, Nick Feamster <>
Content-Type: multipart/alternative; boundary="000000000000be9cab05890c12f5"
Archived-At: <>
Subject: Re: [Pearg] descriptive censorship work: draft-hall-censorship-tech
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 17 May 2019 02:23:54 -0000

Hi Joe!

Chris, you and I have talked about this offline, but just to close that
loop, I would personally like to see this draft in PEARG. We can discuss
whether we want to keep this a regularly-updated-draft or something else in
the RG meeting at IETF 105 (we can do a short presentation, if you're

One thing that would be good to see more of in the draft would be technical
ways to get around censorship by using privacy-preserving technology. That
discussion definitely does not have to be exhaustive!


On Tue, Mar 26, 2019 at 1:46 AM Joseph Lorenzo Hall <> wrote:

> (Bcc'ing SECDISPATCH and SAAG as an FYI; thread on PEARG)
> Hello, apologies for cross-posting.
> At IETF 91 in 2014 we presented some very early work before SAAG that
> describes how global censors use protocols to censor data flows (block,
> impair, modify, etc.). After some editing in subsequent years based on
> superb feedback from SAAG folks (Stephane B., Andrew M., thank you!) we had
> tentative AD sponsorship and some thoughts that this was better on the IETF
> side of the house rather than in a RG.
> We've started to work on it again* and since the original draft we now
> have SECDISPATCH to help "the misfit toys of security" find a home in terms
> of IETF process... I very briefly described this work yesterday in
> SECDISPATCH and Chris Wood, the new PEARG co-chair, suggested that PEARG
> would be a good place for this work since part of what they would like to
> do in that RG is document certain privacy-implicating things in the real
> world.
> We don't really have a preference where this ends up -- there's even a
> case to be made that given the dynamic nature of censorship that this will
> necessarily always be a work in progress. We have heard people find it
> useful and PEARG seems as good as anywhere, and obviously the process to
> get to an RG RFC would help it get better (at least that is my impression!).
> Here is the current version of the draft and the repo we're using to track
> issues and version the doc:
> draft:
> repo:
> Would love to hear if this is something people think PEARG would like to
> work on and we have some ideas about additional documents in a series like
> this (e.g., having some real-world descriptive reference on research and
> practice in terms of traffic analysis could be really useful for IETF
> folks, I suspect.)
> Cheers! --Joe Hall
> (copying two co-authors, Stan from CDT and Nick from Princeton)
> * IASA2 has been a big focus of my own for the last two years.
> --
> Joseph Lorenzo Hall
> Chief Technologist, Center for Democracy & Technology [
> ]
> 1401 K ST NW STE 200, Washington DC 20005-3497
> e:, p: 202.407.8825, pgp:
> Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
> Don't miss out! CDT's Tech Prom is April 10, 2019, at The
> Anthem. Please join us:
> --
> Pearg mailing list