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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <turkeybreast@yahoo.com>) id 1Up4Q9-0005md-3v
for bitcoin-development@lists.sourceforge.net;
Tue, 18 Jun 2013 22:30:37 +0000
X-ACL-Warn:
Received: from nm42-vm10.bullet.mail.bf1.yahoo.com ([216.109.114.155])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Up4Q7-0001lY-Rm
for bitcoin-development@lists.sourceforge.net;
Tue, 18 Jun 2013 22:30:36 +0000
Received: from [98.139.212.152] by nm42.bullet.mail.bf1.yahoo.com with NNFMP;
18 Jun 2013 22:30:30 -0000
Received: from [98.139.212.216] by tm9.bullet.mail.bf1.yahoo.com with NNFMP;
18 Jun 2013 22:30:30 -0000
Received: from [127.0.0.1] by omp1025.mail.bf1.yahoo.com with NNFMP;
18 Jun 2013 22:30:30 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 297737.99472.bm@omp1025.mail.bf1.yahoo.com
Received: (qmail 29881 invoked by uid 60001); 18 Jun 2013 22:30:30 -0000
X-YMail-OSG: C10amPEVM1k8T8mGoD7F1niUr5O9OA.gM290XOz41eBA0MM
jSXiRl8NEAkKcTFSyqVQ72it3EzWPEDEMiH0gVYyvr71PlE9xvoVneVal7yV
bsfB.rqucMoUHasrIEkms4oeQ7p7MCFWQtYb8JGpjwzuqVI21SwbFmixDp91
0y7Y1Njcnxf5ABhFyTaWSEoGBhFVauXul0EkEq9Gn856JsjHBwDQP2rS1WhB
AqzVv_DAdvLTxdGpQur5Y37TENos_1z.FqLciddBbU8qIlFFyy59LGmyogFM
9zSts4J_4U5sy8CAr7jPBmfIP5SGw5rWVVqwz7QUTt7ZuoMYTmJSSQci9ohh
fWHcvdKn1cE6jt9Bl88c0Jhqcs7E7dtb3uyBHuyAFOr1tiWoYUKzC1L08wNf
4afD7rrR86lNHACLVevLOKOEW6eBCWe0r_7kaSvpCYBEDTsFd4d6D4C.VPMa
_ThUqF0ko1gOWm5cguAmqNSxxj_np4nCftwsAjdGUicz3QKfyPh9TVJ4S_O6
DsG8kEt4GKtHCd6tAEGNzXGbMVUg_SDnnNdyKJDdtF3GlJXLjEpDd_2Ef.kr
0ePcbtN0JuIAtXgW5SrQGBVdlez6moq2W0Rei7xsUXfg.Hik8JxygOU83Kbg -
Received: from [87.160.180.101] by web162703.mail.bf1.yahoo.com via HTTP;
Tue, 18 Jun 2013 15:30:30 PDT
X-Rocket-MIMEInfo: 002.001,
VGhhdCdzIG1lLiBJIG5ldmVyIHNhaWQgdG8gbWFrZSBhbGwgbWVzc2FnZXMgZml4ZWQgbGVuZ3RoLiBJIHNhaWQgdG8gbWFrZSBhIGZpeGVkIG51bWJlciBvZiBmaWVsZHMgcGVyIHByb3RvY29sLiBTbyBnaXZlbiBhIHByb3RvY29sIHZlcnNpb24gbnVtYmVyLCB5b3Uga25vdyB0aGUgbnVtYmVyIG9mIGZpZWxkcyBpbiBhIG1lc3NhZ2UuIFRoaXMgaXMgbm90IG9ubHkgZWFzaWVyIGZvciBwYXJzaW5nIG1lc3NhZ2VzLCBidXQganVzdCBnb29kIHByYWN0aWNlLiBJIGRvbid0IHNlZSB3aHkgYSAxIGJ5dGUgZmwBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.147.553
References: <1371577555.61696.YahooMailNeo@web162703.mail.bf1.yahoo.com>
<CANEZrP0ViJSQr_UUxLqM-eFTir=-FGwZ2cSxuPgaVi=KiM8gsA@mail.gmail.com>
Message-ID: <1371594630.18036.YahooMailNeo@web162703.mail.bf1.yahoo.com>
Date: Tue, 18 Jun 2013 15:30:30 -0700 (PDT)
From: Turkey Breast <turkeybreast@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CANEZrP0ViJSQr_UUxLqM-eFTir=-FGwZ2cSxuPgaVi=KiM8gsA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="-1395274837-803414910-1371594630=:18036"
X-Spam-Score: -0.3 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [216.109.114.155 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(turkeybreast[at]yahoo.com)
-1.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 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: 1Up4Q7-0001lY-Rm
Subject: Re: [Bitcoin-development] Missing fRelayTxes in version message
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Turkey Breast <turkeybreast@yahoo.com>
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: Tue, 18 Jun 2013 22:30:37 -0000
---1395274837-803414910-1371594630=:18036
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
That's me. I never said to make all messages fixed length. I said to make a=
fixed number of fields per protocol. So given a protocol version number, y=
ou know the number of fields in a message. This is not only easier for pars=
ing messages, but just good practice. I don't see why a 1 byte flag needs t=
o be optional anyway.=0A=0A=0A=0A________________________________=0A From: =
Mike Hearn <mike@plan99.net>=0ATo: Turkey Breast <turkeybreast@yahoo.com> =
=0ACc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> =0ASent: Tue=
sday, June 18, 2013 9:48 PM=0ASubject: Re: [Bitcoin-development] Missing fR=
elayTxes in version message=0A =0A=0A=0AIt's not a bug (although there was =
recently a change to make bitcoind/qt always send this field anyway).=A0=0A=
=0AI don't know where Amir is going with BIP 60. Version messages have alwa=
ys been variable length. There's nothing inherent in the Bitcoin protocol t=
hat says all messages are fixed length, indeed, tx messages are allowed to =
have arbitrary data appended after them that gets relayed.=0A=0A=0A=0AOn Tu=
e, Jun 18, 2013 at 7:45 PM, Turkey Breast <turkeybreast@yahoo.com> wrote:=
=0A=0ASee this BIP. I'm not sure if this is a bug or what, but it would be =
good if messages always had a fixed number of fields per protocol version.=
=0A>=0A>=0A>https://en.bitcoin.it/wiki/BIP_0060#Code_Updates=0A>=0A>=0A>Thi=
s BIP details everything that needs to be done and proposes a protocol upgr=
ade.=0A>=0A>---------------------------------------------------------------=
---------------=0A>This SF.net email is sponsored by Windows:=0A>=0A>Build =
for Windows Store.=0A>=0A>http://p.sf.net/sfu/windows-dev2dev=0A>__________=
_____________________________________=0A>Bitcoin-development mailing list=
=0A>Bitcoin-development@lists.sourceforge.net=0A>https://lists.sourceforge.=
net/lists/listinfo/bitcoin-development=0A>=0A>
---1395274837-803414910-1371594630=:18036
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><div><span>That's me.=
I never said to make all messages fixed length. I said to make a fixed num=
ber of fields per protocol. So given a protocol version number, you know th=
e number of fields in a message. This is not only easier for parsing messag=
es, but just good practice. I don't see why a 1 byte flag needs to be optio=
nal anyway.<br></span></div><div><br></div> <div style=3D"font-family: tim=
es 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 d=
ir=3D"ltr"> <hr size=3D"1"> <font face=3D"Arial" size=3D"2"> <b><span styl=
e=3D"font-weight:bold;">From:</span></b> Mike Hearn <mike@plan99.net>=
<br> <b><span style=3D"font-weight: bold;">To:</span></b> Turkey Breast <=
;turkeybreast@yahoo.com> <br><b><span style=3D"font-weight: bold;">Cc:</=
span></b>
Bitcoin Dev <bitcoin-development@lists.sourceforge.net> <br> <b><spa=
n style=3D"font-weight: bold;">Sent:</span></b> Tuesday, June 18, 2013 9:48=
PM<br> <b><span style=3D"font-weight: bold;">Subject:</span></b> Re: [Bitc=
oin-development] Missing fRelayTxes in version message<br> </font> </div> <=
div class=3D"y_msg_container"><br>=0A<meta http-equiv=3D"x-dns-prefetch-con=
trol" content=3D"off"><div id=3D"yiv1208554063"><div dir=3D"ltr">It's not a=
bug (although there was recently a change to make bitcoind/qt always send =
this field anyway). <div><br></div><div style=3D"">I don't know where =
Amir is going with BIP 60. Version messages have always been variable lengt=
h. There's nothing inherent in the Bitcoin protocol that says all messages =
are fixed length, indeed, tx messages are allowed to have arbitrary data ap=
pended after them that gets relayed.</div>=0A</div><div class=3D"yiv1208554=
063gmail_extra"><br><br><div class=3D"yiv1208554063gmail_quote">On Tue, Jun=
18, 2013 at 7:45 PM, Turkey Breast <span dir=3D"ltr"><<a rel=3D"nofollo=
w" ymailto=3D"mailto:turkeybreast@yahoo.com" target=3D"_blank" href=3D"mail=
to:turkeybreast@yahoo.com">turkeybreast@yahoo.com</a>></span> wrote:<br>=
=0A<blockquote class=3D"yiv1208554063gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;"><div><div style=3D"font-siz=
e:12pt;font-family:times new roman, new york, times, serif;"><div>See this =
BIP. I'm not sure if this is a bug or what, but it would be good if message=
s always had a fixed number of fields per protocol version.</div>=0A<div><b=
r></div><div style=3D"font-style:normal;font-size:16px;background-color:tra=
nsparent;font-family:times new roman, new york, times, serif;"><a rel=3D"no=
follow" target=3D"_blank" href=3D"https://en.bitcoin.it/wiki/BIP_0060#Code_=
Updates">https://en.bitcoin.it/wiki/BIP_0060#Code_Updates</a></div>=0A<div =
style=3D"font-style:normal;font-size:16px;background-color:transparent;font=
-family:times new roman, new york, times, serif;"><br></div><div style=3D"f=
ont-style:normal;font-size:16px;background-color:transparent;font-family:ti=
mes new roman, new york, times, serif;">=0AThis BIP details everything that=
needs to be done and proposes a protocol upgrade.<br></div></div></div><br=
>--------------------------------------------------------------------------=
----<br>=0AThis <a target=3D"_blank" href=3D"http://sf.net/">SF.net</a> ema=
il is sponsored by Windows:<br>=0A<br>=0ABuild for Windows Store.<br>=0A<br=
>=0Ahttp://p.sf.net/sfu/windows-dev2dev<br>________________________________=
_______________<br>=0ABitcoin-development mailing list<br>=0A<a rel=3D"nofo=
llow" ymailto=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=
=3D"_blank" href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitco=
in-development@lists.sourceforge.net</a><br>=0A<a rel=3D"nofollow" target=
=3D"_blank" href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment">https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
</a><br>=0A<br></blockquote></div><br></div>=0A</div><meta http-equiv=3D"x-=
dns-prefetch-control" content=3D"on"><br><br></div> </div> </div> </div></=
body></html>
---1395274837-803414910-1371594630=:18036--
|
