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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1RPJIo-0006j6-19
for bitcoin-development@lists.sourceforge.net;
Sat, 12 Nov 2011 19:31:46 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=mh.in.england@gmail.com;
helo=mail-ww0-f53.google.com;
Received: from mail-ww0-f53.google.com ([74.125.82.53])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RPJIm-00055b-Gx
for bitcoin-development@lists.sourceforge.net;
Sat, 12 Nov 2011 19:31:45 +0000
Received: by wwf27 with SMTP id 27so2073628wwf.10
for <bitcoin-development@lists.sourceforge.net>;
Sat, 12 Nov 2011 11:31:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.89.17 with SMTP id b17mr3011034wef.50.1321126297048; Sat,
12 Nov 2011 11:31:37 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.216.37.203 with HTTP; Sat, 12 Nov 2011 11:31:37 -0800 (PST)
In-Reply-To: <1320959761.36702.YahooMailNeo@web121014.mail.ne1.yahoo.com>
References: <1320959761.36702.YahooMailNeo@web121014.mail.ne1.yahoo.com>
Date: Sat, 12 Nov 2011 20:31:37 +0100
X-Google-Sender-Auth: xt62fB2MtnWJ-C7wAAzEhWG5AGU
Message-ID: <CANEZrP19nb7E2zk-ZU=K++RcXCjzA6j9rh=Z4cJGqzDHarfv5A@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: multipart/alternative; boundary=0016e6d975aea395e104b18eaf4c
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1RPJIm-00055b-Gx
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] BIP 14 - Protocol Version and User
Agent
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, 12 Nov 2011 19:31:46 -0000
--0016e6d975aea395e104b18eaf4c
Content-Type: text/plain; charset=UTF-8
Looks pretty reasonable to me. If Gavin changes the mainline client to use
this format I'll change BitcoinJ as well. It'll need a bit of API work so
clients are sure to set it up properly.
On Thu, Nov 10, 2011 at 10:16 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
> Hi,
>
> https://en.bitcoin.it/wiki/BIP_0014
>
> Thanks to Gavin Andresen for proof reading and suggesting clarifications.
> Thanks to Patrick Strateman for suggesting the hierarchical format and
> pointing out some flaws of browser user-agents to me.
>
> The timeline is written in the past tense since BIPs are meant to be
> readable in the future for explaining why we took certain decisions with
> bitcoin. A nice cache for future historians when bitcoin is ubiquitous ;)
>
> The next version 0.6 should be the protocol version which becomes peeled
> off from the current client. There are still some changes migrating into
> the protocol that need to be finished.
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
--0016e6d975aea395e104b18eaf4c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Looks pretty reasonable to me. If Gavin changes the mainline client to use =
this format I'll change BitcoinJ as well. It'll need a bit of API w=
ork so clients are sure to set it up properly.<br><br><div class=3D"gmail_q=
uote">
On Thu, Nov 10, 2011 at 10:16 PM, Amir Taaki <span dir=3D"ltr"><<a href=
=3D"mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>></span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex;">
<div><div style=3D"color:#000;background-color:#fff;font-family:times new r=
oman, new york, times, serif;font-size:12pt"><div>Hi,</div><div><br></div><=
div><a href=3D"https://en.bitcoin.it/wiki/BIP_0014" target=3D"_blank">https=
://en.bitcoin.it/wiki/BIP_0014</a></div>
<div><br></div><div>Thanks to Gavin Andresen for proof reading and suggesti=
ng clarifications. Thanks to Patrick Strateman for suggesting the hierarchi=
cal format and pointing out some flaws of browser user-agents to me.</div>
<div><br></div><div>The timeline is written in the past tense since BIPs ar=
e meant to be readable in the future for explaining why we took certain dec=
isions with bitcoin. A nice cache for future historians when bitcoin is ubi=
quitous ;)<br>
</div><div><br></div><div>The next version 0.6 should be the protocol versi=
on which becomes peeled off from the current client. There are still some c=
hanges migrating into the protocol that need to be finished.</div><div>
<br></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>
--0016e6d975aea395e104b18eaf4c--
|
