From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WziWd-0001Ab-EH for bitcoin-development@lists.sourceforge.net; Wed, 25 Jun 2014 08:25:51 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.172 as permitted sender) client-ip=209.85.214.172; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f172.google.com; Received: from mail-ob0-f172.google.com ([209.85.214.172]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WziWb-0001rP-LJ for bitcoin-development@lists.sourceforge.net; Wed, 25 Jun 2014 08:25:51 +0000 Received: by mail-ob0-f172.google.com with SMTP id uy5so1697950obc.17 for ; Wed, 25 Jun 2014 01:25:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.52.77 with SMTP id r13mr6128279oeo.55.1403684744017; Wed, 25 Jun 2014 01:25:44 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Wed, 25 Jun 2014 01:25:43 -0700 (PDT) In-Reply-To: References: <6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com> Date: Wed, 25 Jun 2014 10:25:43 +0200 X-Google-Sender-Auth: 0FTtRSWTafZBC4vGLilqS0uqrQQ Message-ID: From: Mike Hearn To: Gmail Content-Type: multipart/alternative; boundary=001a11330d028b3e7104fca4d26a 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: 1WziWb-0001rP-LJ 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: Wed, 25 Jun 2014 08:25:51 -0000 --001a11330d028b3e7104fca4d26a Content-Type: text/plain; charset=UTF-8 > > I agree. It would be even sillier to start specifying container formats > for random one-off "that would be kind of nice, I guess" features. > No, it'd be sensible. Here's a list I drew up a long time ago of features I imagined adding to the payment protocol: https://bitcointalk.org/index.php?topic=270055.msg2890147#msg2890147 The protocol is there to contain features! There is zero benefit to slavishly following some religious notion of purity or minimalism here. The shared resource in question is just varint encoded integers. So, we should be guided by what will help our users and what will help adoption. Anyway, Gavin asked me to start handling more BIP 70 stuff a few weeks ago. I want to use something simple to set up the extensions process more formally. IMO we need a "living document" version of the payment protocol with all the different extensions out there folded into it, to simplify programming tasks and ensure field numbers don't collide. --001a11330d028b3e7104fca4d26a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I agree. It would be even sillier to start specifying conta= iner formats for random one-off "that would be kind of nice, I guess&q= uot; features.

No, it'd be sensib= le.

Here's a list I drew up a long time ago of features= I imagined adding to the payment protocol:


The protocol is there to contain features! There is zer= o benefit to slavishly following some religious notion of purity or minimal= ism here. The shared resource in question is just varint encoded integers. = So, we should be guided by what will help our users and what will help adop= tion.

Anyway, Gavin asked me to start handling more BIP 70 st= uff a few weeks ago. I want to use something simple to set up the extension= s process more formally. IMO we need a "living document" version = of the payment protocol with all the different extensions out there folded = into it, to simplify programming tasks and ensure field numbers don't c= ollide.
--001a11330d028b3e7104fca4d26a--