Delivery-Date: Wed, 18 Feb 2015 13:50:49 -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_SIGNED,
	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 8810F1E0BE1
	for <archiver@seul.org>; Wed, 18 Feb 2015 13:50:47 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1841C31D1F;
	Wed, 18 Feb 2015 18:50:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0D97E31B80
 for <tor-talk@lists.torproject.org>; Wed, 18 Feb 2015 18:50:41 +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 bDnLt-SUwNJR for <tor-talk@lists.torproject.org>;
 Wed, 18 Feb 2015 18:50:40 +0000 (UTC)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id E935231A7E
 for <tor-talk@lists.torproject.org>; Wed, 18 Feb 2015 18:50:40 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailout.nyi.internal (Postfix) with ESMTP id 4CB432101E
 for <tor-talk@lists.torproject.org>; Wed, 18 Feb 2015 13:50:38 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute4.internal (MEProxy); Wed, 18 Feb 2015 13:50:38 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=x-sasl-enc:message-id:date:from
 :mime-version:to:subject:references:in-reply-to:content-type
 :content-transfer-encoding; s=smtpout; bh=eRQDHdpoE/5SM5QzokEJ8h
 BoQlo=; b=k0MXCoVKMNehYEfOpVbeW4nHD8BEU3WGM3hoE43N5XzbjEXIjZ810Q
 mJfF2Ec1EpHs2wLZIbYc1Ix8n301iw3y1H4R4vfrXuZTH50/Dy/oMlMT0/jKFpJt
 6YC5YugifO4VS7fE87bt8dTO+za9BvrP4Eg7C1Q0c64BjERYQNONg=
X-Sasl-enc: JerQGywUZyHLRknB9C9z6kRdexQEvYftK2GXpSBpYSHJ 1424285437
Received: from 127.0.0.1 (unknown [176.31.122.216])
 by mail.messagingengine.com (Postfix) with ESMTPA id A133AC002A3
 for <tor-talk@lists.torproject.org>; Wed, 18 Feb 2015 13:50:37 -0500 (EST)
Message-ID: <54E4DEFA.2080107@emails.veryspeedy.net>
Date: Wed, 18 Feb 2015 18:50:34 +0000
From: Lara <lara.tor@emails.veryspeedy.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <54E4CF16.8020109@emails.veryspeedy.net> <851tlnccj9.fsf@boum.org>
In-Reply-To: <851tlnccj9.fsf@boum.org>
Subject: Re: [tor-talk] Tor and HTTP/2?
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>

intrigeri:
> Tor can transport basically anything that lives on top of TCP.
> Assuming HTTP/2 is TCP, then there's basically nothing to do on the
> Tor side, it should just work :)

Right. But see the WebRTC issues, does Tor browser team know of problems
with this new HTTP flavor?

-- 
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

