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

Joseph Lorenzo Hall <joe@cdt.org> Tue, 26 March 2019 08:46 UTC

Return-Path: <jhall@cdt.org>
X-Original-To: pearg@ietfa.amsl.com
Delivered-To: pearg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79FF11202BB for <pearg@ietfa.amsl.com>; Tue, 26 Mar 2019 01:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 W3iHsbDNQejH for <pearg@ietfa.amsl.com>; Tue, 26 Mar 2019 01:45:44 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E06D01202E4 for <pearg@irtf.org>; Tue, 26 Mar 2019 01:45:29 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id 3so9263099oir.7 for <pearg@irtf.org>; Tue, 26 Mar 2019 01:45:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=pfRuMTZtsSuMfjGEJk7i+xBKg8Tqzm+N68Cq2cg3U1c=; b=NiBh4dwH0m8XM19h4Z2vukEfOWw6rlvQUMqrBsPUWsLhNWM8tKEZYqA46w4B3oMDqI naVPwmgGY4qLfjRsWyiTR9FL+QDlTYiiGQPcpxMtVEbRhHoXVkOVmlTgL2iGEe0paadX TrC2xpGPs5tjO2Lk4if1ZMPDqNvz87YoIohJM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pfRuMTZtsSuMfjGEJk7i+xBKg8Tqzm+N68Cq2cg3U1c=; b=ZzKvXEAD/u5H2GvIsKy1cWv3Ap4fsjFK0rXMnLxh2L9KW/69dVroW7Xv7ij4itn8gC /icMvSSkXXa6daRI/wv9M5tGXhNqxeNqBYizV3PJEO5BEaSDkQpwzVPBMjR6n2z5AZeT wMMnQhmiSF0dV+VasH/P7pAr3MEN0nXmwEanCPBbs9MXB7ifz6wyBPEcoZFJQQ+EJ8ZT gYSAMuSxZfqNGxoJQEGC3Q320RijovpdSdYYnBLHbm5tgkagyoeEwvLtVG7sMPAvlX2f ppkTWxgDh0TPxVCdhLYKDzhJFsY3yDFpMn5wXslPI0lyaUABH4kwMJE4XUdB/1vcEfFC glgw==
X-Gm-Message-State: APjAAAX8hlb30V0hq1o7i2PJmFwDENwtFfXAgojhhiufxkXKqnzBYBM/ E+XEF9WUWaFzNaT1CCQxAI+QkH6FUWbuOpKg8z33R8ilq4vxsqA8
X-Google-Smtp-Source: APXvYqz9HvF+SK54qqRRw3i4eWbDpNuqmwkDzK/iB6/qZgooeqmjL187qL1mr75cq8q3fvQAveoScMHZ0FXrvF+Cp4w=
X-Received: by 2002:aca:4507:: with SMTP id s7mr4425411oia.127.1553589928675; Tue, 26 Mar 2019 01:45:28 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Tue, 26 Mar 2019 04:45:17 -0400
Message-ID: <CABtrr-Ubq5z_Nx4-VA7gLgGMaxOBvfpSpXKJfeO9Q9C9eCA8Fg@mail.gmail.com>
To: pearg@irtf.org, Stan Adams <sadams@cdt.org>, Nick Feamster <feamster@cs.princeton.edu>
Content-Type: multipart/alternative; boundary="000000000000d3637d0584fb574e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/Wae_euryORrFihiyYInPWAczKMM>
Subject: [Pearg] descriptive censorship work: draft-hall-censorship-tech
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <pearg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/pearg>, <mailto:pearg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pearg/>
List-Post: <mailto:pearg@irtf.org>
List-Help: <mailto:pearg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pearg>, <mailto:pearg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2019 08:46:14 -0000

(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: https://tools.ietf.org/html/draft-hall-censorship-tech-07
repo: https://github.com/josephlhall/rfc-censorship-tech

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 [https://www.cdt.org]
1401 K ST NW STE 200, Washington DC 20005-3497
e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
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: https://cdt.org/annual-dinner/