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
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <decker.christian@gmail.com>) id 1RMixD-00035V-Va
for bitcoin-development@lists.sourceforge.net;
Sat, 05 Nov 2011 16:18:47 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.161.47 as permitted sender)
client-ip=209.85.161.47;
envelope-from=decker.christian@gmail.com;
helo=mail-fx0-f47.google.com;
Received: from mail-fx0-f47.google.com ([209.85.161.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RMixC-0000A0-Lq
for bitcoin-development@lists.sourceforge.net;
Sat, 05 Nov 2011 16:18:47 +0000
Received: by faat2 with SMTP id t2so1421056faa.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 05 Nov 2011 09:18:40 -0700 (PDT)
Received: by 10.152.0.138 with SMTP id 10mr3063969lae.3.1320509919058; Sat, 05
Nov 2011 09:18:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.4.138 with HTTP; Sat, 5 Nov 2011 09:17:58 -0700 (PDT)
In-Reply-To: <1320507589.87534.YahooMailNeo@web121019.mail.ne1.yahoo.com>
References: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
<CANEZrP1OpuE1AHj1ARsGSkpkAwUQAr1_JaU=i4pjyERO6__+1A@mail.gmail.com>
<CALxbBHXRWjdpttLeGcPrdd4uwVs=kg4QL5Q4fmBghfxTA60Kag@mail.gmail.com>
<1320507570.40074.YahooMailNeo@web121017.mail.ne1.yahoo.com>
<1320507589.87534.YahooMailNeo@web121019.mail.ne1.yahoo.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Sat, 5 Nov 2011 17:17:58 +0100
Message-ID: <CALxbBHWYdt_LRQE5K=36fXNNSqyGVSyYwxi2-p8mxQaei5LCZg@mail.gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: multipart/alternative; boundary=bcaec5485a6ea5db9304b0ff2c51
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(decker.christian[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1RMixC-0000A0-Lq
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Lock protocol version numbers
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: Sat, 05 Nov 2011 16:18:48 -0000
--bcaec5485a6ea5db9304b0ff2c51
Content-Type: text/plain; charset=ISO-8859-1
Sorry for shooting this approach down, but I'm against it. User-agent
strings are an extremely bad idea as it would lead developers to start
making communication choices depending on the client type. User-Agents in
HTTP are only useful if the clients (browsers) do not adhere to a well
defined behavior. I see the version string more as a kind of vanity point
(xyz peers are using my network code) and it would be bad to base choices
on it.
For protocol choices we already have a good mechanism in place (nServices)
to negotiate capabilities.
I for one vote for keeping it as simple as possible, just a simple string,
without any further meaning.
On Sat, Nov 5, 2011 at 4:39 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
> From talking with Patrick Strateman (phantomcircuit), he suggested this
> idea (which I will elaborate more on in the BIP):
>
> User-agent strings are a good starting point, however they aren't easy for
> parsing so we'll make a small modification to them.
>
> We need a hierarchy from protocol, variant, gui, flavour, build
>
> /Satoshi:314700/bitcoin-qt:0.4/
>
> How does that sound? In BitcoinJ's case:
>
> /BitcoinJ:0.2/AndroidBuild:0.8/
>
> Thoughts:
>
> - Do we need a freely defined comments field?
>
> /BitcoinJ:0.2[iPad; U; CPU OS 3_2_1]/AndroidBuild:0.8/
> /Satoshi:314700/bitcoin-qt:0.4[Ubuntu Oneiric]/
>
> ------------------------------
> *From:* Christian Decker <decker.christian@gmail.com>
> *To:* Mike Hearn <mike@plan99.net>
> *Cc:* Amir Taaki <zgenjix@yahoo.com>; "
> bitcoin-development@lists.sourceforge.net" <
> bitcoin-development@lists.sourceforge.net>
> *Sent:* Saturday, November 5, 2011 2:45 PM
> *Subject:* Re: [Bitcoin-development] Lock protocol version numbers
>
> On BitDroid I stopped updating the protocol version at 31700 and set the
> string to be both Version and Client, just like BitcoinJ :-)
>
> On Sat, Nov 5, 2011 at 3:32 PM, Mike Hearn <mike@plan99.net> wrote:
>
> BitCoinJ already sets the subver field to its name and version.
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--bcaec5485a6ea5db9304b0ff2c51
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Sorry for shooting this approach down, but I'm against it. User-agent s=
trings are an extremely bad idea as it would lead developers to start makin=
g communication choices depending on the client type. User-Agents in HTTP a=
re only useful if the clients (browsers) do not adhere to a well defined be=
havior. I see the version string more as a kind of vanity point (xyz peers =
are using my network code) and it would be bad to base choices on it.<br>
For protocol choices we already have a good mechanism in place (nServices) =
to negotiate capabilities.<br><br>I for one vote for keeping it as simple a=
s possible, just a simple string, without any further meaning.<br><br>
<div class=3D"gmail_quote">
On Sat, Nov 5, 2011 at 4:39 PM, Amir Taaki <span dir=3D"ltr"><<a href=3D=
"mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>></span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex;">
<div class=3D"HOEnZb"><div class=3D"h5"><div><div style=3D"color:#000;backg=
round-color:#fff;font-family:times new roman, new york, times, serif;font-s=
ize:12pt"><span>From talking with Patrick Strateman (phantomcircuit), he su=
ggested this idea (which I will elaborate more on in the BIP):</span><div s=
tyle=3D"font-family:times new roman, new york, times, serif;font-size:12pt"=
>
<div style=3D"font-family:times new roman, new york, times, serif;font-size=
:12pt"><div><div><div style=3D"color:#000;background-color:#fff;font-family=
:times new roman, new york, times, serif;font-size:12pt"><div><br><span></s=
pan></div>
<div><span>User-agent strings are a good starting point, however they aren&=
#39;t easy for parsing so we'll make a small modification to them.</spa=
n></div><div><br><span></span></div><div><span>We need a hierarchy from pro=
tocol, variant, gui, flavour,
build</span></div><div><span><br></span></div><div><span>/Satoshi:314700/b=
itcoin-qt:0.4/</span></div><div><br><span></span></div><div><span>How does =
that sound? In BitcoinJ's case:</span></div><div><br><span></span></div=
>
<div><span>/BitcoinJ:0.2/AndroidBuild:0.8/</span></div><div><br><span></spa=
n></div><div><span>Thoughts:</span></div><div><br><span></span></div><div><=
span>- Do we need a freely defined comments
field?</span></div><div><br><span></span></div><div><span>/BitcoinJ:0.2[iP=
ad; U; CPU OS 3_2_1]/AndroidBuild:0.8/</span></div><div><span>/Satoshi:3147=
00/bitcoin-qt:0.4[Ubuntu Oneiric]/<br></span></div><div><br></div><div styl=
e=3D"font-family:times new roman, new york, times, serif;font-size:12pt">
<div style=3D"font-family:times new roman, new york, times, serif;font-size=
:12pt"><font face=3D"Arial" size=3D"2"><hr size=3D"1"><b><span style=3D"fon=
t-weight:bold">From:</span></b> Christian Decker <<a href=3D"mailto:deck=
er.christian@gmail.com" target=3D"_blank">decker.christian@gmail.com</a>>=
;<br>
<b><span style=3D"font-weight:bold">To:</span></b> Mike Hearn <<a href=
=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>><br><b=
><span style=3D"font-weight:bold">Cc:</span></b> Amir Taaki <<a href=3D"=
mailto:zgenjix@yahoo.com" target=3D"_blank">zgenjix@yahoo.com</a>>; &quo=
t;<a href=3D"mailto:bitcoin-development@lists.sourceforge.net" target=3D"_b=
lank">bitcoin-development@lists.sourceforge.net</a>" <<a href=3D"ma=
ilto:bitcoin-development@lists.sourceforge.net" target=3D"_blank">bitcoin-d=
evelopment@lists.sourceforge.net</a>><br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Saturday, November 5, =
2011 2:45 PM<br><b><span style=3D"font-weight:bold">Subject:</span></b> Re:
[Bitcoin-development] Lock protocol version numbers<br></font><br>
<div>On BitDroid I stopped updating the protocol version at 31700 and set t=
he string to be both Version and Client, just like BitcoinJ :-)<br><br><div=
>On Sat, Nov 5, 2011 at 3:32 PM, Mike Hearn <span dir=3D"ltr"><<a rel=3D=
"nofollow" href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.ne=
t</a>></span> wrote:<br>
<blockquote style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">BitCoinJ already sets the subver field to its name and version.<br=
><br>
<br>-----------------------------------------------------------------------=
-------<br>
RSA(R) Conference 2012<br>
Save $700 by Nov 18<br>
Register now<br>
<a href=3D"http://p.sf.net/sfu/rsa-sfdev2dev1" target=3D"_blank">http://p.s=
f.net/sfu/rsa-sfdev2dev1</a><br>___________________________________________=
____<br>
Bitcoin-development mailing list<br>
<a rel=3D"nofollow" href=3D"mailto:Bitcoin-development@lists.sourceforge.ne=
t" target=3D"_blank">Bitcoin-development@lists.sourceforge.net</a><br>
<a rel=3D"nofollow" href=3D"https://lists.sourceforge.net/lists/listinfo/bi=
tcoin-development" target=3D"_blank">https://lists.sourceforge.net/lists/li=
stinfo/bitcoin-development</a><br>
<br></blockquote></div><br>
</div><br><br></div></div></div></div></div><br><br></div></div></div></div=
></div></div><br>----------------------------------------------------------=
--------------------<br>
RSA(R) Conference 2012<br>
Save $700 by Nov 18<br>
Register now<br>
<a href=3D"http://p.sf.net/sfu/rsa-sfdev2dev1" target=3D"_blank">http://p.s=
f.net/sfu/rsa-sfdev2dev1</a><br>___________________________________________=
____<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br>
--bcaec5485a6ea5db9304b0ff2c51--
|
