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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1XFiGP-0008GO-33
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 11:23:13 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.213.170 as permitted sender)
client-ip=209.85.213.170; envelope-from=jgarzik@bitpay.com;
helo=mail-ig0-f170.google.com;
Received: from mail-ig0-f170.google.com ([209.85.213.170])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XFiGO-0005PN-3q
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 11:23:13 +0000
Received: by mail-ig0-f170.google.com with SMTP id h3so2364850igd.5
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 Aug 2014 04:23:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=EgWBa3H6nKYknBpjtelLuAAtBCudifK+I+4ENwVKu1U=;
b=eIOCRmuXfIdGDqyLwqgmlkd6Wi+qZsJaVl/cODhqG1UaBb/5yTDqPqG6blX5CbXsyq
nxo5kUWCYuvVafNWgSodV4dPm2QWGlQmqcT7QkA7S/x8Dzh0affiUgRCuhqBYA8zZfi8
B7mbRUsReedhlmxje1oll5+o3JPQiYbDLWtILodYFF1Y3DTyRfSWANqhoBRYO2v6S2We
Lqcm73mAxQLkyj5mHVdsSjr9ReqQqvuMm1LPdOjOUsbkCoApbAuoUd5REAq08tI70atP
Ks5wJjxMXFlYZZCQinWSI2trd4df2f/b4raALf7YDB7cvKCr1h5cDKaBVxKvtFFBbAZE
BG2A==
X-Gm-Message-State: ALoCoQml/iTesOIhsl0OQX1j/Ojc13GmLInKXO4Qsu1/qZNB9ICwyqJ931vnk+YjWD5fQZFNWxsT
X-Received: by 10.42.178.133 with SMTP id bm5mr10918369icb.75.1407496986658;
Fri, 08 Aug 2014 04:23:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.10.78 with HTTP; Fri, 8 Aug 2014 04:22:46 -0700 (PDT)
In-Reply-To: <CALxbBHXPCpZ9npacPOgU2q6=xTpcOVi2fJ+C8v93U2Oyuorrgw@mail.gmail.com>
References: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>
<CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com>
<CA+s+GJD+9qpwFcVfHOCCsFYjmk7A0V=65vG-7jJ6D7jj4Pi_7g@mail.gmail.com>
<CANEZrP245242JYDBBo72XVmKgEBO96QPjcJi8Jy2Dm_r90n1Bw@mail.gmail.com>
<CA+s+GJBUgi7XF4nyVEXqpZi4XYO86vTXMs40gzfu9tCdmp59tw@mail.gmail.com>
<CA+s+GJDjSR3272LsSax-2V--x4_taoqrTMiDoXSEvuiS5-MBKw@mail.gmail.com>
<CALxbBHXPCpZ9npacPOgU2q6=xTpcOVi2fJ+C8v93U2Oyuorrgw@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 8 Aug 2014 07:22:46 -0400
Message-ID: <CAJHLa0NwzLcGcKLyJVFhXoc49CRnSaqYnSbi=Z8FFXWQir0e9A@mail.gmail.com>
To: Christian Decker <decker.christian@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1XFiGO-0005PN-3q
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related
services
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: Fri, 08 Aug 2014 11:23:13 -0000
This is not a generic "I run a website!" advertisement feature.
NODE_EXT_SERVICES is tightly focused on services that exist
if-any-only-if a P2P bitcoin node (bitcoind) is reachable via the same
advertised address.
You may usefully create overlay networks of specialized services.
On Fri, Aug 8, 2014 at 6:41 AM, Christian Decker
<decker.christian@gmail.com> wrote:
> I wonder whether we actually want to support this kind of advertisement in
> the P2P protocol. We have a working mechanism for protocol extensions in the
> P2P network (service flags) so this is obviously only for services that are
> not P2P extensions, so why have them in there at all?
>
> I'd argue that a parallel network, external to Bitcoin, could take over the
> task of advertising external services.
>
> Regards,
> Chris
>
> --
> Christian Decker
>
>
> On Fri, Aug 8, 2014 at 11:26 AM, Wladimir <laanwj@gmail.com> wrote:
>>
>> On Fri, Aug 8, 2014 at 12:15 PM, Wladimir <laanwj@gmail.com> wrote:
>> > On Fri, Aug 8, 2014 at 12:01 PM, Mike Hearn <mike@plan99.net> wrote:
>> >>> He wants to use it to advertise services that are not part of the P2P
>> >>> protocol itself, but run on a different port. Reserving services bits
>> >>> for those is not acceptable.
>> >>
>> >>
>> >> Why not? Does the port matter much?
>> >
>> > Yes. The services bits are for advertising services on the P2P
>> > network. That's not open for discussion.
>>
>> It also wouldn't work. A bit is not enough to find an external service
>> except in the naive case where the advertised service would have a
>> fixed port. Not even bitcoind has a fixed port. So there needs to be a
>> mechanism to find how to connect to the 'external service'. This is
>> provided by the proposed extension.
>>
>> It would in principle be possible to advertise an extra service bit
>> *in addition to* this one, to make it easier to find through the addr
>> mechanism. But it would be confusing and IMO an abuse of P2P service
>> bits.
>>
>> Wladimir
>>
>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
