Delivery-Date: Sat, 31 Jan 2015 00:51:44 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 2F2C11E0B3D
	for <archiver@seul.org>; Sat, 31 Jan 2015 00:51:43 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id CF3B032F90;
	Sat, 31 Jan 2015 05:51:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0990832F85
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 05:51:36 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id u0gHBTd04Lgm for <tor-talk@lists.torproject.org>;
 Sat, 31 Jan 2015 05:51:35 +0000 (UTC)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com
 [IPv6:2607:f8b0:4003:c01::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id DBFC83058D
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 05:51:35 +0000 (UTC)
Received: by mail-ob0-f179.google.com with SMTP id va8so16602590obc.10
 for <tor-talk@lists.torproject.org>; Fri, 30 Jan 2015 21:51:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=Eh+xOSzpXbhdlRrJ1Xkl/mQbsaplQ9pfZ8VFQ60/RzU=;
 b=QXCuqW7j42S6cSg7b5wvLBr28ur82Jl3e+7HlShtRfYnuTTjV5whiox7DDmmutyh3g
 89OorCQ4razKd19LDVAvrzER9mKE4vTm2Tt7T8gn7ZjxuKDN8wTie6ptXlk8U9ssS1Ru
 XYg51yysJoV81rSmHln9D9+SvLvbp48Zi2w4MF9/7zSmrasVKnUdycKWn3TkXOsMCm5G
 VoZywOLjTzqSJ93Di0cZ4IQRyeKmltZQRxEQSfzt3VkGMP3647tgcRCL0BPgn7qODVbG
 5uszQqh9qnN4ti9uj4yuJ1cgDTTKEyxs7ZpWO0856V+XNpGnDZyHcVbR2KyJG6+1IfOZ
 ruOg==
MIME-Version: 1.0
X-Received: by 10.182.65.97 with SMTP id w1mr5840043obs.73.1422683493426; Fri,
 30 Jan 2015 21:51:33 -0800 (PST)
Received: by 10.60.31.71 with HTTP; Fri, 30 Jan 2015 21:51:33 -0800 (PST)
In-Reply-To: <54C82093.6040101@cs.tcd.ie>
References: <CAH7M2h=S0n6aWoEEwP8b0c3Mtb8s6MWq1aHdjc1VmXCCHKH8MQ@mail.gmail.com>
 <20150124224855.BD6D5EA9FD@snorky.mixmin.net>
 <19D7B5ED-1C5E-4E31-B746-F8721E628BAD@vpnc.org>
 <20150126131726.82505EAA8C@snorky.mixmin.net>
 <54C6B4FA.6070108@av8n.com>
 <CAD2Ti2_qAW26wiaTo74ULXfeRAeAONA4a58=aFroamoYN9Z8=A@mail.gmail.com>
 <3731C61B-D8BB-49F2-9F92-4E5B845116CB@lrw.com>
 <CABrd9ST1K1zw45BuOBq8fP3WCccp+sMyhAvwACZzNjuQmRq-+Q@mail.gmail.com>
 <201501272313.t0RNDACl012560@new.toad.com>
 <54C82093.6040101@cs.tcd.ie>
Date: Sat, 31 Jan 2015 00:51:33 -0500
Message-ID: <CAD2Ti28+eAAf0y1dBM0e5Ayvmr4ins8e9Ni5TDg3ooezEbmFdw@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: [tor-talk] Fwd: [Cryptography] traffic analysis -> let's write an
	RFC?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Relating to passive analysis, link/path padding, and crypto.
See the relavent threads in archive for further context.
http://www.metzdowd.com/mailman/listinfo/cryptography

---------- Forwarded message ----------
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Tue, Jan 27, 2015 at 6:34 PM
Subject: Re: [Cryptography] traffic analysis -> let's write an RFC?
To: <cryptography@metzdowd.com>

If folks wanted to work on that RFC angle, I'd be delighted
to help out as I can.

I think that traffic analysis mitigation is the next big area
we need to start trying hard to work. So far, we've (IETF)
gotten general padding capabilities added to protocols (HTTP/2.0
for example, still in discussion for TLS1.3) on a case by
case basis, but we've not yet done anything systematic. I'd
love to see a WG chartered to try figure out how to most
effectively counter traffic analysis and then go write
protocol and/or BCPs as needed. (Speaking personally of
course, it'd require IETF consensus for that to happen
obviously.)

Pragmatically, it's very late for a BoF to happen at the
March IETF in Dallas. Deadline is Feb 6 for requests which
are mostly far more developed than one single email:-) But
if someone wanted to speak to the topic, we still have
space/time available in the agenda for the security area
meeting in Dallas. Ping me if you're interested and willing
and able to work on that.

Cheers,
S.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

