Delivery-Date: Mon, 18 Jan 2016 06:03:32 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 CC5781E300D;
	Mon, 18 Jan 2016 06:03:29 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9617938BBA;
	Mon, 18 Jan 2016 11:03:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 334FB38B8E
 for <tor-talk@lists.torproject.org>; Mon, 18 Jan 2016 11:03:19 +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 z7rDtgeOaPGX for <tor-talk@lists.torproject.org>;
 Mon, 18 Jan 2016 11:03:19 +0000 (UTC)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com
 [IPv6:2a00:1450:400c:c09::230])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id E83B821699
 for <tor-talk@lists.torproject.org>; Mon, 18 Jan 2016 11:03:15 +0000 (UTC)
Received: by mail-wm0-x230.google.com with SMTP id l65so94550674wmf.1
 for <tor-talk@lists.torproject.org>; Mon, 18 Jan 2016 03:03:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to:content-type:content-transfer-encoding;
 bh=KYabUe+URP3yh6RRb89E6goze9pKv8KKHdSPQ8M8zFo=;
 b=ToWiJCpajmNL3eK+zUCihPhnxS3pTvblLysSXdAWLcp54ul8K9klSc9T1YrQPtOAzD
 ZtNQeQUaOZqHWJCK6khbbRGJ9zDO2En1zAdfNlyRKMbE9id+L98npeC7z812JNhoqD8I
 qxyMrBzLqb7AnK2NGGUxKxIhuOyrDncQGb8HvJKhKrMJnLD6LCJ+dJ7LFvfPPzBHkWsi
 n7Ryhu+2nnqiFTAE1HUQdvNLjmw/BJELaOUq32zaS2nGmTx+XhJobicOsa8pq7PEiprs
 ZYIPiWaAxI97fVK3YHLvMcFS4BH6+o2yLKg9b0EYmcV4Lgltbonmqg3wXT+c8JSKU09D
 gODA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:subject:to:references:from:message-id:date
 :user-agent:mime-version:in-reply-to:content-type
 :content-transfer-encoding;
 bh=KYabUe+URP3yh6RRb89E6goze9pKv8KKHdSPQ8M8zFo=;
 b=aazzEi2B/GUzeEsmUhI7wd858m5AR8ASKCoQBn3OINBrmHp/yyJaDwaP/li9+sRiyd
 hBJ2S5VsGdAEZGVjAAtD5FJb9W49s+uKVsHYwemE7c6/MYPJ3eoOVyUv3XrcsBdCIXR4
 CBw/BmKhP8rcCCy7CPs3g2FHiWhjLg4Ho47GgpRWEfnJG3LTO9YDfNVF4r+bJWlyLNY4
 xGaZd5ogr6uNMZLu2Td72qgQWORPjgzLilPCBLeJND7TdWgkX++ophn8a2KxF2z0RtLZ
 iHwF/nc0zudTGaDiXReb9DLsG8O/aApNYjmY6kz65zv2qzlnsQwIgXtR7zCDheS0YUON
 ojfg==
X-Gm-Message-State: ALoCoQmhXW9allYPXRW6FCzPXpN+odzqVXoa8+wc7gkMnmRmugE4vcq12aXIKoOpIrbTqGuhOrXxXm2BBEBdJzTrXXn6z3GkNA==
X-Received: by 10.194.222.135 with SMTP id qm7mr23508168wjc.106.1453114993051; 
 Mon, 18 Jan 2016 03:03:13 -0800 (PST)
Received: from [192.168.1.10] (ANice-654-1-149-214.w86-205.abo.wanadoo.fr.
 [86.205.212.214])
 by smtp.googlemail.com with ESMTPSA id e9sm23231450wja.25.2016.01.18.03.03.11
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Mon, 18 Jan 2016 03:03:12 -0800 (PST)
To: tor-talk@lists.torproject.org
References: <569B8433.7030007@infosecurity.ch>
From: Aymeric Vitte <vitteaymeric@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <569CC670.8030202@gmail.com>
Date: Mon, 18 Jan 2016 12:03:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <569B8433.7030007@infosecurity.ch>
Subject: Re: [tor-talk] Multicast Onion Services for video-streaming?
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="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

It seems similar to what Peersm project (http://www.peersm.com) intends
to do via node-Tor (https://github.com/Ayms/node-Tor)

In its current form browsers are connected to Tor nodes, as well as
Peersm clients (https://github.com/Ayms/node-Tor/tree/master/install)
who are bridging to the bittorrent network.

Despite of the several encryption/hash computation for each Tor packet
we get a rate of 2 Mbps which is normally enough to stream (but we limit
this rate to 1 Mbps currently), the limitation comes more from the
transcoding of the files to adapt them so they can be played by browsers
(https://github.com/Ayms/torrent-live#transcoding-and-file-conversion).

Currently you get data anonymously from one peer, not several ones, it's
obvious that the Tor network is too small to implement a P2P network on
top of it.

So the final phase
(https://github.com/Ayms/node-Tor#anonymous-serverless-p2p-inside-browsers-=
--peersm-specs)
is designed to be a P2P network with browsers as peers communicating via
WebRTC using the Tor protocol but not the Tor network.

Another (complementary or different) idea could be that browsers are
connected to Tor nodes using Websockets (like Peersm phase 1) and
implement a complete Tor relay (not only the Onion proxy function as
Peersm is doing), then relaying data with other browsers and exiting
whether in the clear (like uProxy) or to the Tor network via Websockets
again.

One of the issues of this model is the limitation induced by the upload
bandwidth of the peers, so a traditional Tor connection should use
different circuits and peers to exchange data, and not only one circuit,
which implies some modifications of the Tor protocol.

Le 17/01/2016 13:08, Fabio Pietrosanti (naif) - lists a =E9crit :
> Within the Italian Nexa Center for internet and Society mailing list,
> there was recently a discussion on the IP-level blocking forced by the
> government's judges to ISPs against "informal/unofficial" football video
> streaming services.
> =

> I learned that those kind of services, usually provide browsers plug-in
> to distribute the streaming in a semi-p2p-bittorrent-way.
> =

> Btw, the IP-blocking regardless of the reasons, is basically censorship.
> =

> I was wondering if Tor network couldn't be a network/platform for that
> kind of video-streaming-services.
> =

> Obviously the problem is that video-streaming require a lot of bandwidth
> and massive-services attract a lot of users, so even brainstorming
> something about it, would imply thinking a network/application design
> that does not increase linearly the bandwidth resources required for
> each new user.
> =

> So, it come up to my mind that in MAN (metropolitan area network) that
> share a common network topology and software, multicast is used for that
> kind of purposes.
> =

> On my italian fiber service provider Fastweb, when i use their own TV
> with their own set-top-box and click "Channel X", there's basically a
> "join" to a multicast group, that will then deliver me the streaming and
> in their network topology there are "edges" that does cache and
> redistribute the content.
> =

> So, i was wondering if the multicast streaming concept for content
> distribution with edges-caching, couldn't fit somehow in a future Tor
> network use-cases or design.
> =

> =


-- =

Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
-- =

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

