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 1YDJmj-0007SE-Ro for bitcoin-development@lists.sourceforge.net; Mon, 19 Jan 2015 21:22:57 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.42 as permitted sender) client-ip=209.85.216.42; envelope-from=brianchoffman@gmail.com; helo=mail-qa0-f42.google.com; Received: from mail-qa0-f42.google.com ([209.85.216.42]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YDJmi-0006dd-Qx for bitcoin-development@lists.sourceforge.net; Mon, 19 Jan 2015 21:22:57 +0000 Received: by mail-qa0-f42.google.com with SMTP id dc16so25615796qab.1 for ; Mon, 19 Jan 2015 13:22:51 -0800 (PST) X-Received: by 10.224.172.198 with SMTP id m6mr51621056qaz.11.1421702571378; Mon, 19 Jan 2015 13:22:51 -0800 (PST) Received: from [192.168.1.2] (pool-96-255-238-248.washdc.fios.verizon.net. [96.255.238.248]) by mx.google.com with ESMTPSA id g12sm13333102qay.44.2015.01.19.13.22.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 19 Jan 2015 13:22:50 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-EEB67EBF-1379-4BC2-ACB2-2527FF1704A4 Mime-Version: 1.0 (1.0) From: Brian Hoffman X-Mailer: iPhone Mail (12B440) In-Reply-To: Date: Mon, 19 Jan 2015 16:22:49 -0500 Content-Transfer-Encoding: 7bit Message-Id: References: <2C7D6208-1921-4DDC-90FE-DB1ABE1D61DB@petertodd.org> <54BD6314.60607@gmail.com> To: Gavin Andresen 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 (brianchoffman[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars -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: 1YDJmi-0006dd-Qx Cc: Bitcoin Dev 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 21:22:58 -0000 --Apple-Mail-EEB67EBF-1379-4BC2-ACB2-2527FF1704A4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Damn if SPKI had won out we would be parsing S-expressions instead of X.509 c= ertificates. ASN.1 is not fun IMHO. > On Jan 19, 2015, at 3:56 PM, Gavin Andresen w= rote: >=20 > 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 buff= ers because I designed it and implemented the original prototype (with lots o= f 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 w= as very familiar with them. >=20 >=20 > What Mike said. Runner-up for encoding was JSON. >=20 > XML+ASN.1 was Right Out, because lots of us hate XML and ASN.1 with a burn= ing passion. Complexity is the Enemy of Security, and both XML and ASN.1 are= too complex. >=20 >=20 > --=20 > -- > Gavin Andresen > Chief Scientist, Bitcoin Foundation > https://www.bitcoinfoundation.org/ >=20 > --------------------------------------------------------------------------= ---- > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development --Apple-Mail-EEB67EBF-1379-4BC2-ACB2-2527FF1704A4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Damn if SPKI had won out we would be p= arsing S-expressions instead of X.509 certificates. ASN.1 is not fun IMHO.

On Jan 19, 2015, at 3:56 PM, Gavin Andresen <gavin@bitcoinfoundation.org> w= rote:

On Mon, Jan 19, 2015 at 3:40 PM= , Mike Hearn <mike@plan99.net> wrote:
OK, I guess we c= an boil this down more simply. BIP 70 uses protocol buffers because I design= ed it and implemented the original prototype (with lots of input from Gavin a= nd 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 wi= th them.

Wh= at Mike said. Runner-up for encoding was JSON.

XML+ASN.1 was Right Out, because lot= s of us hate XML and ASN.1 with a burning passion. Complexity is the Enemy o= f Security, and both XML and ASN.1 are too complex.


--
--
Gavin Andresen
Chief Scientist, Bitcoin Fo= undation

--------------------= ----------------------------------------------------------
N= ew Year. New Location. New Benefits. New Data Center in Ashburn, VA.<= br>GigeNET is offering a free month of service with a new server in As= hburn.
Choose from 2 high performing configs, both with 100T= B of bandwidth.
Higher redundancy.Lower latency.Increased ca= pacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.s= ourceforge.net
https://lists.sourceforge.net/lists/list= info/bitcoin-development
= --Apple-Mail-EEB67EBF-1379-4BC2-ACB2-2527FF1704A4--