Delivery-Date: Wed, 27 Jan 2016 06:44:55 -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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,T_RP_MATCHES_RCVD 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 B32431E0301;
	Wed, 27 Jan 2016 06:44:53 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E4E3D3624D;
	Wed, 27 Jan 2016 11:44:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C7F9E32AF9
 for <tor-talk@lists.torproject.org>; Wed, 27 Jan 2016 11:44:40 +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 uKu8jv7cq5iD for <tor-talk@lists.torproject.org>;
 Wed, 27 Jan 2016 11:44:40 +0000 (UTC)
Received: from continuum.iocl.org (continuum.iocl.org [217.140.74.2])
 by eugeni.torproject.org (Postfix) with ESMTP id 368DD28407
 for <tor-talk@lists.torproject.org>; Wed, 27 Jan 2016 11:44:39 +0000 (UTC)
Received: (from krey@localhost)
 by continuum.iocl.org (8.11.3/8.9.3) id u0RBiZV18072;
 Wed, 27 Jan 2016 12:44:35 +0100
Date: Wed, 27 Jan 2016 12:44:35 +0100
From: Andreas Krey <a.krey@gmx.de>
To: tor-talk@lists.torproject.org
Message-ID: <20160127114435.GC17022@inner.h.apk.li>
References: <c669e36e-b96f-4336-82fe-0db2ffa560df@email.android.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <c669e36e-b96f-4336-82fe-0db2ffa560df@email.android.com>
User-Agent: Mutt/1.4.2.1i
X-message-flag: What did you expect to see here?
Subject: Re: [tor-talk] How stream separation across multiple circuits can
	be implemented?
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>

On Wed, 27 Jan 2016 11:32:56 +0000, Dimitar Milkov wrote:
...
> " If we can move streams across circuits, though, we would need to add queues at each end of the circuit, add sequence numbers so we can send and receive acknowledgements for cells, and so forth."
> 
> Why something like this (implementing TCP stack-like features in Tor itself) will be necessary?

Currently, an application stream (say, an ssh session) exists within
a single circuit. When one of the nodes this circuit hops along fails,
so will the application stream. If you want the application stream to
survive this, first it must not be the exit that fails because then the
TCP connection to the destination is lost, and you need to buffer data
that might be lost in the broken circuit - if you want to deal with
failures in one layer you must implement retransmission on the next layer.

Not worth the effort, apparently.

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
-- 
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

