From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: <6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com> Date: Tue, 24 Jun 2014 16:12:09 -0400 Message-ID: From: Gavin Andresen To: Gmail 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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

= 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 hund= reds of fields like this that people might want to use.=A0

Protocol buffers are designed to be exten= sible, and there are hundreds of field numbers available.

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= .


--
--
Gavin Andresen
--20cf304273e015ffdf04fc9a9336--