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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1WzX4j-0003PO-0i
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 20:12:17 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.179 as permitted sender)
client-ip=209.85.160.179; envelope-from=gavinandresen@gmail.com;
helo=mail-yk0-f179.google.com;
Received: from mail-yk0-f179.google.com ([209.85.160.179])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WzX4h-0007vY-6B
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 20:12:16 +0000
Received: by mail-yk0-f179.google.com with SMTP id 20so509747yks.24
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Jun 2014 13:12:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.172.161 with SMTP id t21mr4513568yhl.65.1403640729695;
Tue, 24 Jun 2014 13:12:09 -0700 (PDT)
Received: by 10.170.110.71 with HTTP; Tue, 24 Jun 2014 13:12:09 -0700 (PDT)
In-Reply-To: <BBF86C9B-6B3D-4A03-AC7B-35619C47091F@gmail.com>
References: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
<CAJHLa0Omiz+UhGjSKgYU7+b2YY7aN23w7o8CQntqMePFs7LkjA@mail.gmail.com>
<CANEZrP06gk-JhKaNpvYUTfjFq9AGnCay9=pjUGpVMjMSuX3_ew@mail.gmail.com>
<CAJna-HhX8HOci0KMe4ZScr4QW792S3n5twvU0QhbQe1N_3q7_w@mail.gmail.com>
<6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com>
<CAJHLa0PYfuJg3daPvzPFZpFz7ezH2RHpJ8zyz2g1NDKppM7rWA@mail.gmail.com>
<BBF86C9B-6B3D-4A03-AC7B-35619C47091F@gmail.com>
Date: Tue, 24 Jun 2014 16:12:09 -0400
Message-ID: <CABsx9T13yksenx5aYd4HVqTyVjARx9aTHy=Neu64p6k9FnRRVw@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Gmail <will.yager@gmail.com>
Content-Type: multipart/alternative; boundary=20cf304273e015ffdf04fc9a9336
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
(gavinandresen[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: 1WzX4h-0007vY-6B
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
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: Tue, 24 Jun 2014 20:12:17 -0000
--20cf304273e015ffdf04fc9a9336
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Jun 24, 2014 at 3:00 PM, Gmail <will.yager@gmail.com> wrote:
> Ok, wanting structured data is a decent argument, but why this random
> arbitrary case in particular? There are hundreds of fields like this that
> people might want to use.
>
Protocol buffers are designed to be extensible, and there are hundreds of
field numbers available.
It would be silly to add a "generic stuff" field inside a container format
that ALREADY has all the mechanisms necessary for forwards and backwards
extensibility.
--
--
Gavin Andresen
--20cf304273e015ffdf04fc9a9336
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Tue, Jun 24, 2014 at 3:00 PM, Gmail <span dir=3D"ltr"><<a href=3D"mai=
lto:will.yager@gmail.com" target=3D"_blank">will.yager@gmail.com</a>></s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>Ok, wanting structured data is a decent=
argument, but why this random arbitrary case in particular? There are hund=
reds of fields like this that people might want to use.=A0</div>
<div></div></blockquote></div><br>Protocol buffers are designed to be exten=
sible, and there are hundreds of field numbers available.</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra">It would be silly to =
add a "generic stuff" field inside a container format that ALREAD=
Y has all the mechanisms necessary for forwards and backwards extensibility=
.<br>
<br clear=3D"all"><div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div>
--20cf304273e015ffdf04fc9a9336--
|
