Delivery-Date: Mon, 23 Mar 2015 09:09:44 -0400
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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,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 47AB11E01A0
	for <archiver@seul.org>; Mon, 23 Mar 2015 09:09:42 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 48F5A342FA;
	Mon, 23 Mar 2015 13:09:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3DBAE341FB
 for <tor-talk@lists.torproject.org>; Mon, 23 Mar 2015 13:09:35 +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 0q6LQi45dvOg for <tor-talk@lists.torproject.org>;
 Mon, 23 Mar 2015 13:09:35 +0000 (UTC)
Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33])
 (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 12749341F3
 for <tor-talk@lists.torproject.org>; Mon, 23 Mar 2015 13:09:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mail2.openmailbox.org (Postfix) with ESMTP id 3757420306B;
 Mon, 23 Mar 2015 14:09:32 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=openmailbox.org;
 h=content-transfer-encoding:content-type:content-type
 :in-reply-to:references:subject:subject:mime-version:from:from
 :date:date:message-id:received; s=openmailbox; t=1427116169; bh=
 pOVFukFMxB7cOIaQJZ3n+i+z7k5Pavq319rR+pc53Cg=; b=Wh+FR0e5i4IMU999
 0rK6FTJIQevMAcymStODw6cWRkFAdxM8+8Ktg+5UqvwSqCh6lUmkWf/QDI+5PCfH
 Gg2JmTvJSIzs1FPxm07h8lqPOzqX2ToMS6rvo/LASN6SP9EENRseYCUZUxAfCo1S
 AibRt4fS9gi8L+WFIi9JewalCkI=
X-Virus-Scanned: amavisd-new at openmailbox.org
Received: from mail2.openmailbox.org ([62.4.1.33])
 by localhost (mail.openmailbox.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id thsdrod21mwI; Mon, 23 Mar 2015 14:09:29 +0100 (CET)
Message-ID: <5510107E.2050603@openmailbox.org>
Date: Mon, 23 Mar 2015 13:09:18 +0000
From: Nusenu <nusenu@openmailbox.org>
MIME-Version: 1.0
To: Linus Nordberg <linus@nordberg.se>, tor-talk@lists.torproject.org
References: <550C9A31.30203@openmailbox.org> <87wq28jef7.fsf@nordberg.se>
In-Reply-To: <87wq28jef7.fsf@nordberg.se>
Subject: Re: [tor-talk] Who runs the Tor Network? An Overview using MyFamily
 Data
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> This is probably not going to work as intended with how MyFamily 
> works. I guess we should call a-f a big happy family and be done
> with it.

For simplicity reasons probably, but I don't see any reason why a tor
client would have a problem with that? And the group-by family
analysis has no problem with it either. If this kind of MyFamily
configuration is intended by the operators than it is no
misconfiguration by design.
Just in most cases it probably is. For clarity reasons it would be
great if 'organizational' relays (d,e,f) would have distinct
contactInfo (compared to personal relays (a,b,c).

> Then again, MyFamily is on its way out I hear. Is that true and
> when does it disappear?

I hope it will be replaced by prop 242.
https://gitweb.torproject.org/torspec.git/tree/proposals/242-better-families.txt

See also:
https://lists.torproject.org/pipermail/tor-dev/2015-March/008516.html
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVEBB+AAoJEFv7XvVCELh0HNgP/joYlzhIHUrPBCWgWOxJevBC
rjnVLB9In2Y6L78ljJI7MMgkNtk4VCjlCbJPWx61XibVoia8xXiJqq9fK+7ZG/tU
5u4j1PL+/gtOqVbMsH1aYaBcQPvqJMkNgjFgG8UePPRq98KeiIBy87Ob4R7wVD/M
Pw54YXVX0NS2Ye/G1+vdJWtR6yjvJCREwN0Xa1VCVE6yKT4CWbc8h6K+jZ6mEDHn
s1LEsphfF4qlXteTGSSn9XUuAnd2s5kwGnyWVMGrT9uzveZf509yi6QkzfXEDsN7
BHiuPyvqslBa+WnLMaDBJTC39EuXE25r/sEttQfuvQVZdAIVg89L6YOKy+PLU8BT
eAOxA12xMYKIUiQdm9Nk/4ZSKXw5UqSmc+PF3zwoFaVLbOTiF1OzfbcZlT8p1apA
E0BLA8qyI29Ma8EjKqTCNZ91yygWQs/LV3kVwHz+nCl1S0JScMkq4gNmb9XELwtt
vHERKjRL0jNyVyEtIeOfuuHvCvCuDlW4otbn0jXGlm8JmwO3psYWApnYt83PP//4
dBJ4aK7DMD7c6iFWQamkQbtHJxc8H/JJFJfRXbqicZWQ4rh9nH1c+HCbVgB7NPNo
NrWkPEdd1Ekp3hu6yLF2q/aTssfmlYuucVubX9Nf6Y25QJDJBx31j4+mjrz+5mhr
41ZK7UD1AMwqeMsF/Jdk
=i1g3
-----END PGP SIGNATURE-----
-- 
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

