Date: Tue, 21 Jun 2016 18:13:47 -0400
From: Peter Todd <pete@petertodd.org>
To: Erik Aronesty <erik@q32.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20160621221347.GC10196@fedora-21-dvm>
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="O3RTKUHj+75w1tg5"
Content-Disposition: inline
In-Reply-To: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
Precedence: list


--O3RTKUHj+75w1tg5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 20, 2016 at 05:33:32PM +0000, Erik Aronesty via bitcoin-dev wro=
te:
> BIP 0070 has been a a moderate success, however, IMO:
>=20
> - protocol buffers are inappropriate since ease of use and extensibility =
is
> desired over the minor gains of efficiency in this protocol.  Not too late
> to support JSON messages as the standard going forward
>=20
> - problematic reliance on merchant-supplied https (X509) as the sole form
> of mechant identification.   alternate schemes (dnssec/netki), pgp and
> possibly keybase seem like good ideas.   personally, i like keybase, since
> there is no reliance on the existing domain-name system (you can sell with
> a github id, for example)
>=20
> - missing an optional client supplied identification

Note that "client supplied identification" is being pushed for AML/KYC
compliance, e.g. Netki's AML/KYC compliance product:

http://www.coindesk.com/blockchain-identity-company-netki-launch-ssl-certif=
icate-blockchain/

This is an extremely undesirable feature to be baking into standards given =
it's
negative impact on fungibility and privacy; we should not be adopting stand=
ards
with AML/KYC support, for much the same reasons that the W3C should not be
standardizing DRM.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--O3RTKUHj+75w1tg5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJXabwYAAoJEGOZARBE6K+yxk4H/ij5A+OCAOHga1YCDUZqi5mX
MNIF/n9TKmAMMOUaBwdRwX8UBiZndnVWSdzfTYmUCgCzGbCTRtO9LQbKsR5tEOqN
rDvg/Q+FfTZbcedHBsnTsE2IzDCov3wjsxqoSwdsW9GJT4EE1um2CwysA189V40o
2jYmXw0c1VOvgfFfj/b3XbQGl4eEx3zaCRTQNbT5hihynH6tiAGuPYXs4EJeQokQ
hYjZ0cFZZioT+ecQtiGTPWZLanfYreTAEUmFvpdPEbKZW9Q7Eo3VGzbE8rzMGHCE
JhtcHpUKgXCZxwPczEluI6gMv6br+bfJ9q4eeb8fjU6vSHOqJHTrw+ATxH1ulLw=
=booV
-----END PGP SIGNATURE-----

--O3RTKUHj+75w1tg5--