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; 
MIME-Version: 1.0
Sender: gavinandresen@gmail.com
In-Reply-To: <CANEZrP3ZdFcQsP+EWgTYQDccFZbrZFTk+xi-YdWPCJzMRH79pA@mail.gmail.com>
References: <CAN5esQJe0uUm0NyctaBa6WH7_JjeE_OLR=FY_XQWnSr50VRDyA@mail.gmail.com>
	<CAJHLa0OTynX4oiQoyanpRKE2tpAuS4L5X-2j20328725J9RrvQ@mail.gmail.com>
	<2C7D6208-1921-4DDC-90FE-DB1ABE1D61DB@petertodd.org>
	<CAN5esQLCV=L0kYxDGhK2F=qZ8OqMxyYS+-Pn17U_M+nV4Sj3Og@mail.gmail.com>
	<54BD6314.60607@gmail.com>
	<CANEZrP3ZdFcQsP+EWgTYQDccFZbrZFTk+xi-YdWPCJzMRH79pA@mail.gmail.com>
Date: Mon, 19 Jan 2015 15:56:37 -0500
Message-ID: <CABsx9T1hwCky7s6kza00_RuueaVbNB++ZuHY3j00iwJTN6tCyA@mail.gmail.com>
From: Gavin Andresen <gavin@bitcoinfoundation.org>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e0158c7a0ea97da050d078e57
Subject: Re: [Bitcoin-development] BIP70: why Google Protocol Buffers for
	encoding?
Precedence: list

--089e0158c7a0ea97da050d078e57
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jan 19, 2015 at 3:40 PM, Mike Hearn <mike@plan99.net> 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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Jan 19, 2015 at 3:40 PM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:s=
olid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote"><span class=3D""><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor=3D"#FFFFF=
F" text=3D"#000000">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.<br></div></blockquote></s=
pan><div></div></div></div></div></blockquote></div><div class=3D"gmail_ext=
ra"><br></div><div class=3D"gmail_extra">What Mike said. Runner-up for enco=
ding was JSON.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmai=
l_extra">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.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra"><br></div>-- <br><div class=3D"gmail_signature">--<div>Gav=
in Andresen</div><div>Chief Scientist, Bitcoin Foundation</div><div><a href=
=3D"https://www.bitcoinfoundation.org/" target=3D"_blank">https://www.bitco=
infoundation.org/</a></div><div><br></div></div>
</div></div>

--089e0158c7a0ea97da050d078e57--