summaryrefslogtreecommitdiff
path: root/50/ec70bb6a48065b9e09101f51e391ee939113a7
blob: 05514fbb47409cdfc906ad7e2ca1acc3b84dc0c9 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1SUj7N-0008UX-H7
	for bitcoin-development@lists.sourceforge.net;
	Wed, 16 May 2012 18:38:37 +0000
X-ACL-Warn: 
Received: from mail-lb0-f175.google.com ([209.85.217.175])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SUj7L-0008MZ-6d
	for bitcoin-development@lists.sourceforge.net;
	Wed, 16 May 2012 18:38:37 +0000
Received: by lbol5 with SMTP id l5so1062118lbo.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 16 May 2012 11:38:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type:x-gm-message-state;
	bh=6B8tQMRcGbIr4MvizE+CSdj+Vba2Ze9a8T1FJdJstbU=;
	b=fhC/tC5y8DowAh7kjNpzk+u9RI9qiAXdaSjDc0UwGuZ1URkgiB3y8A9YBeEHp6NeZ6
	ZVmc7zgBMwvTJ5+udhpV4Qcwl0L6403qrqSWqw5d/X85QBih29evDFJ5FmLilR2rcZpD
	tSt/lyWpR3NUtVLsbwxOLf+RkuhKRWkGsy0y/bDYNn0ccrT5Y39Z53Z1tdHXRDH8QDe9
	Px3XZsd+HlL+EUYbMYf9SfDFiSP98upxomjlvVr1Q11BcI2OpvU0wSgbrQ2Q/WPZign0
	4rxmzBj/iuHr5AK7jwJwAX2JTlH1aQaSwb2heDZUf/lpg/9giN50qHFAuShR4x5/WcMW
	IbYg==
MIME-Version: 1.0
Received: by 10.152.111.200 with SMTP id ik8mr4092643lab.15.1337193508621;
	Wed, 16 May 2012 11:38:28 -0700 (PDT)
Received: by 10.114.25.97 with HTTP; Wed, 16 May 2012 11:38:28 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <201205161829.44967.luke@dashjr.org>
References: <CA+8xBpd-0nXdda4fwyFonEY6rOSSyt=5goD-rbMTpvkcuHNTog@mail.gmail.com>
	<201205161829.44967.luke@dashjr.org>
Date: Wed, 16 May 2012 14:38:28 -0400
Message-ID: <CA+8xBpcFPdj9akeU9kN9CxERWp5VxKt7g0-mN4tf8NxsAe2+_w@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQk1Gq0tOZjM6Ux5BAne4iGNAIZP6hpx0W0xaYb8uT91F5YcA8VCbTpOMFmxa6Md33l5N79Q
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SUj7L-0008MZ-6d
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] P2P feature discovery (was Re: BIP 33 -
 Stratized Nodes)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 18:38:37 -0000

On Wed, May 16, 2012 at 2:29 PM, Luke-Jr <luke@dashjr.org> wrote:
> That assumes you already have a connection to the peer in question.
> As I understand it, the service bits are propagated as part of the address,
> so you can see at a glance which nodes you want to connect to for some
> special service. Passing a huge list along might be unwieldy (though it
> makes sense for protocol changes that don't add new services).

If the peer list becomes too, um, stratified maybe that's a Big Hint
that said clients should be using another network entirely, and not
overloading bitcoin's P2P network for wholly unrelated tasks.  The
bitcoin P2P network is not a general message transit network.

Another argument against the proposal, IOW, if you ask me....

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com