From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YDJNL-00055Q-Rm for bitcoin-development@lists.sourceforge.net; Mon, 19 Jan 2015 20:56:43 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.169 as permitted sender) client-ip=209.85.160.169; envelope-from=gavinandresen@gmail.com; helo=mail-yk0-f169.google.com; Received: from mail-yk0-f169.google.com ([209.85.160.169]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YDJNK-0004uQ-Ls for bitcoin-development@lists.sourceforge.net; Mon, 19 Jan 2015 20:56:43 +0000 Received: by mail-yk0-f169.google.com with SMTP id 200so3595501ykr.0 for ; Mon, 19 Jan 2015 12:56:37 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.236.32.129 with SMTP id o1mr19215591yha.196.1421700997222; Mon, 19 Jan 2015 12:56:37 -0800 (PST) Sender: gavinandresen@gmail.com Received: by 10.170.130.19 with HTTP; Mon, 19 Jan 2015 12:56:37 -0800 (PST) In-Reply-To: References: <2C7D6208-1921-4DDC-90FE-DB1ABE1D61DB@petertodd.org> <54BD6314.60607@gmail.com> Date: Mon, 19 Jan 2015 15:56:37 -0500 X-Google-Sender-Auth: jIVUiHopPZpcmlNVDmnFgotV1Mg Message-ID: From: Gavin Andresen To: Bitcoin Dev Content-Type: multipart/alternative; boundary=089e0158c7a0ea97da050d078e57 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 (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_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: 1YDJNK-0004uQ-Ls Subject: Re: [Bitcoin-development] BIP70: why Google Protocol Buffers for encoding? 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: Mon, 19 Jan 2015 20:56:44 -0000 --089e0158c7a0ea97da050d078e57 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jan 19, 2015 at 3:40 PM, Mike Hearn wrote: > OK, I guess we can boil this down more simply. BIP 70 uses protocol >> buffers because I designed it and implemented the original prototype (with >> lots of input from Gavin and an earlier proposal by sipa). I used protocol >> buffers because, beyond all their nice properties, I used to work at Google >> and so was very familiar with them. >> > What Mike said. Runner-up for encoding was JSON. XML+ASN.1 was Right Out, because lots of us hate XML and ASN.1 with a burning passion. Complexity is the Enemy of Security, and both XML and ASN.1 are too complex. -- -- Gavin Andresen Chief Scientist, Bitcoin Foundation https://www.bitcoinfoundation.org/ --089e0158c7a0ea97da050d078e57 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On M= on, Jan 19, 2015 at 3:40 PM, Mike Hearn <mike@plan99.net> wrot= e:
OK, I guess we can boil this down more simply. BIP 70 u= ses protocol buffers because I designed it and implemented the original pro= totype (with lots of input from Gavin and an earlier proposal by sipa). I u= sed protocol buffers because, beyond all their nice properties, I used to w= ork at Google and so was very familiar with them.

What Mike said. Runner-up for enco= ding was JSON.

XML+ASN.1 was Right Out, because lots of us hate XML and ASN.1 wit= h a burning passion. Complexity is the Enemy of Security, and both XML and = ASN.1 are too complex.


--
--
Gav= in Andresen
Chief Scientist, Bitcoin Foundation

--089e0158c7a0ea97da050d078e57--