Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.172 as permitted sender)
	client-ip=209.85.212.172; envelope-from=nicolas.dorier@gmail.com;
	helo=mail-wi0-f172.google.com; 
MIME-Version: 1.0
Sender: slashene@gmail.com
Date: Wed, 28 Jan 2015 13:45:29 +0100
Message-ID: <CALYO6Xt-jTYwpywUaH-s4YPYyGUp1_BLSEswscnwX+Vu166Lcw@mail.gmail.com>
From: Nicolas DORIER <nicolas.dorier@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=f46d04428f0019972c050db5bfb0
Subject: Re: [Bitcoin-development] BIP70: why Google Protocol Buffers for
	encoding?
Precedence: list

--f46d04428f0019972c050db5bfb0
Content-Type: text/plain; charset=UTF-8

I agree that the use protocol buffer and x509 by BIP70 is a poor choice.

The choice should have been done to maximize portability, not to maximize
efficiency and flexibility.

What I ended up doing for having a similar codebase on all plateform is to
parse a BIP70 messages with the help of a web service that convert it to
JSON.
I don't like this solution since it had a trust dependency, and the
certificate verification become handled by the web service, not the device.
But even if I solved google buffer problem, I would stumble upon having
headache to validate the x509 certificate chain on every plateforms.

A simple BIP70 using JSON + HTTPS would have make things more easy.
I agree that it requires that the merchant own the domain name of the BIP70
endpoint, but I don't consider such a big of a deal, since this is how
e-commerce works.

--f46d04428f0019972c050db5bfb0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>I agree that the use protocol buffer and x509 by=
 BIP70 is a poor choice.<br><br></div>The choice should have been done to m=
aximize portability, not to maximize efficiency and flexibility.<br><br></d=
iv><div>What I ended up doing for having a similar codebase on all platefor=
m is to parse a BIP70 messages with the help of a web service that convert =
it to JSON.<br></div><div>I don&#39;t like this solution since it had a tru=
st dependency, and the certificate verification become handled by the web s=
ervice, not the device. But even if I solved google buffer problem, I would=
 stumble upon having headache to validate the x509 certificate chain on eve=
ry plateforms.<br></div><div><br></div><div>A simple BIP70 using JSON + HTT=
PS would have make things more easy.<br></div><div>I agree that it requires=
 that the merchant own the domain name of the BIP70 endpoint, but I don&#39=
;t consider such a big of a deal, since this is how e-commerce works.<br></=
div></div>

--f46d04428f0019972c050db5bfb0--