Re: [perpass] perpass: what next?
Joseph Lorenzo Hall <joe@cdt.org> Thu, 23 April 2015 19:22 UTC
Return-Path: <jhall@cdt.org>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962AA1AD0A9 for <perpass@ietfa.amsl.com>; Thu, 23 Apr 2015 12:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.501
X-Spam-Level: *
X-Spam-Status: No, score=1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] autolearn=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 fzwZ_8KUjpv6 for <perpass@ietfa.amsl.com>; Thu, 23 Apr 2015 12:22:08 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) (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 F3E9F1AD35A for <perpass@ietf.org>; Thu, 23 Apr 2015 12:21:58 -0700 (PDT)
Received: by labbd9 with SMTP id bd9so20035106lab.2 for <perpass@ietf.org>; Thu, 23 Apr 2015 12:21:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=lNfEt0NWRY2MdLmI0b6LKmSG0gnp9ftEANZ5N7HJZoM=; b=e96G5p1Z6EPbyiRzd0SZnS1DxBYeGdxeZbUhz+J92UovnU5z0XfLTclUxqYToy2IEu F1tdnb3MqECJWwHfondQBeQcQ3t/sSwa41o1DEueLTSHmiDdKoWNR9FDJ4gMrcswX3Ll pzT8Dyd8KRr3p2mOV5WfRXifiW1drqakZAKOcF5s+Sv0M8HnN2LWx9N4yKDLPAJ3P1q9 j603ZHVNdnDfhguOCFa1i7qiBenn/1D8L4zJk6bnepNJ1d/gGXSbmfqad1/0n3BG52LN hUmUlqtdWdCR6UPMCZb0w9K7VhHsVZ+T5CtIMCqzfBjVAaQOpjgFvQE+Wke4mrZDbdKf nUQg==
X-Gm-Message-State: ALoCoQlwAyj1en3KjlIZ9K0bXy57LOK/1xBkbHrSITlkiRmr9Xfwq1+u4FeIdKGbFsssESAu6yQ6
X-Received: by 10.152.22.168 with SMTP id e8mr634904laf.27.1429816917512; Thu, 23 Apr 2015 12:21:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.84.15 with HTTP; Thu, 23 Apr 2015 12:21:36 -0700 (PDT)
In-Reply-To: <5530EEAB.5050601@cs.tcd.ie>
References: <5530EEAB.5050601@cs.tcd.ie>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 23 Apr 2015 15:21:36 -0400
Message-ID: <CABtrr-Wcqud_QD8tBvuXTobYgOnnTDp2vYdpP5dBPKsJUdcFOw@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/C5pPIhldDW8aNz-QEDDyG7wvmLg>
Cc: perpass <perpass@ietf.org>
Subject: Re: [perpass] perpass: what next?
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 19:22:09 -0000
On Fri, Apr 17, 2015 at 7:29 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > Please discuss those here and/or send 'em to the IESG or to some > random AD or to me. But discussing 'em on this list is way better, > and of course even betterer is to write an I-D (and please do point > again at ones you've written, just to refresh folks' minds). Heya, We've authored and will be updating soon an I-D on technical methods used to accomplish censorship: https://tools.ietf.org/html/draft-hall-censorship-tech-00 I'm going to be updating that within the next week and will have an academic co-author. I'm looking to generate a series of documents like these that cover topics that IETF engineers might find valuable when doing protocol or implementation work if they'd like to avoid unanticipated and potentially problematic uses of their protocols. The next subject to tackle (and it may be better to break down further) in my mind is traffic analysis, which can be a bear of a topic (i.e., very hard). Since there is no natural WG for this work, but I'm hopeful it could be valuable work, I was hoping perpass would be a great place to have discussion about these kinds of cross-WG topics in pervasive monitoring (and maybe a few will make the cut and garner AD sponsorship... but that seems a ways off!). best, Joe -- Joseph Lorenzo Hall Chief Technologist Center for Democracy & Technology 1634 I ST NW STE 1100 Washington DC 20006-4011 (p) 202-407-8825 (f) 202-637-0968 joe@cdt.org PGP: https://josephhall.org/gpg-key fingerprint: 3CA2 8D7B 9F6D DBD3 4B10 1607 5F86 6987 40A9 A871
- Re: [perpass] perpass: what next? John Levine
- [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Michael Richardson
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Watson Ladd
- Re: [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Tim Bray
- Re: [perpass] perpass: what next? Adam Caudill
- Re: [perpass] perpass: what next? Paul Wouters
- Re: [perpass] perpass: what next? carlo von lynX
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Watson Ladd
- Re: [perpass] perpass: what next? carlo von lynX
- Re: [perpass] perpass: what next? Joseph Lorenzo Hall
- Re: [perpass] perpass: what next? Christian Huitema
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Michael Richardson
- Re: [perpass] perpass: what next? Ted Lemon
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Kathleen Moriarty