Re: [perpass] Getting started...

Brian Trammell <trammell@tik.ee.ethz.ch> Sat, 17 August 2013 10:17 UTC

Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635AD11E80D9 for <perpass@ietfa.amsl.com>; Sat, 17 Aug 2013 03:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iMDrzbURuTDV for <perpass@ietfa.amsl.com>; Sat, 17 Aug 2013 03:17:52 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 7A7A811E80DF for <perpass@ietf.org>; Sat, 17 Aug 2013 03:17:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 85DE6D9316; Sat, 17 Aug 2013 12:17:46 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wsWdoXQk1XKy; Sat, 17 Aug 2013 12:17:46 +0200 (MEST)
Received: from [10.0.27.100] (cust-integra-122-165.antanet.ch [80.75.122.165]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 284CBD9307; Sat, 17 Aug 2013 12:17:46 +0200 (MEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <520F4AE1.5040403@cs.tcd.ie>
Date: Sat, 17 Aug 2013 12:17:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE07133E-E19E-4D4F-818A-3BA283ADD0EB@tik.ee.ethz.ch>
References: <520E5684.1090005@cs.tcd.ie> <6.2.5.6.2.20130816171144.0c01f738@resistor.net> <520F4AE1.5040403@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1508)
Cc: SM <sm@resistor.net>, perpass@ietf.org
Subject: Re: [perpass] Getting started...
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <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: Sat, 17 Aug 2013 10:17:58 -0000

hi SM, Stephen, all,

On Aug 17, 2013, at 12:05 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
>> Discussions about monitoring is a sensitive subject.  
> 
> Yes. However, even those who want to be able to monitor at point X,
> probably don't want their sensitive stuff monitored at points Y,Z,...
> So you don't actually have to have inhaled all the fumes to think
> its a good plan for Internet protocols to be more robust against
> pervasive monitoring.
> 
>> I am curious to
>> see whether the 50 people are willing to discuss about that on this
>> mailing list. :-)
> 
> I hope so. We had some good discussions in Berlin at any rate and
> my hope is that at least the people involved in that will chime in.
> But I guess we'll see when we see.

There's also a difference between the threat models of pervasive monitoring (an analysis of what can be done) and operational practice (a report of what _is_ done). We should, to the extent possible, work from the former, referring to the latter anecdotally -- because that, I suspect, is all we're going to get.

Of course, if the threat model is "the adversary cooperates with the endpoint(s) of the communication", there's not a whole lot you can do at the protocol level. But that is, I think, a point for wider discussion, and there is significant work to be done, even if it just ends up being a cross-area awareness-building exercise; on which more soon.

Cheers,

Brian