1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1VBBwo-00021w-O2
for bitcoin-development@lists.sourceforge.net;
Sun, 18 Aug 2013 22:59:46 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.99 as permitted sender)
client-ip=62.13.148.99; envelope-from=pete@petertodd.org;
helo=outmail148099.authsmtp.net;
Received: from outmail148099.authsmtp.net ([62.13.148.99])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1VBBwl-0004dN-10 for bitcoin-development@lists.sourceforge.net;
Sun, 18 Aug 2013 22:59:46 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt12.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
r7IMxa7k069915; Sun, 18 Aug 2013 23:59:36 +0100 (BST)
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r7IMxV7L051570
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Sun, 18 Aug 2013 23:59:33 +0100 (BST)
Date: Sun, 18 Aug 2013 18:59:30 -0400
From: Peter Todd <pete@petertodd.org>
To: Mike Hearn <mike@plan99.net>
Message-ID: <20130818225930.GA23974@savin>
References: <20130818025932.GA372@savin>
<CANEZrP2jONtRJ6oF1YqKJB9nm1HcMkfz_yzeNshEWqD-5fdNiA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp"
Content-Disposition: inline
In-Reply-To: <CANEZrP2jONtRJ6oF1YqKJB9nm1HcMkfz_yzeNshEWqD-5fdNiA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: d940c224-0859-11e3-b5c5-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdwoUGUATAgsB AmUbWVdeVVR7Wmc7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqBmV8 TngZLhl3dgBBeDB2 ZEBqECRSWEQpd0R5
X05cEGQbZGY1a31N VRNdagNUcgZDfk5E bwQuUz1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCWAsMhML bTQlOhBnN2w9LwAA
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1VBBwl-0004dN-10
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_BLOOM BIP
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 22:59:46 -0000
--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Aug 19, 2013 at 12:00:23AM +0200, Mike Hearn wrote:
> The original Bloom filtering spec did not make this feature optional for
> the same reason gzip isn't an optional part of the PNG specification. I s=
ee
> no reason to revisit that. It's definitely not the case that making every
> possible feature optional is smart design, often it's the opposite.
Bloom filtering isn't lossless so to speak.
A better analogy would be making re-sharing an optinal part of the
BitTorrent specification, and then expecting that the majority of users
would never upload data to peers that needed it.
--=20
'peter'[:-1]@petertodd.org
--17pEHd4RhPHOinZp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJSEVHSAAoJECSBQD2l8JH7G/EH/3eWDSakw9TorHneQBxtWmtq
8JLIpLxfEHOeBTdHhVFd4Gz3+CTthe6ysFZMm38iE5StFrijPMWcKnu4lE4QJlTx
lT6B32s4nEQOWg+YfraTLFnKbp7AZQgeKb8/NVUxLsAAaPeppjdFVyG/vTAClYL/
rSfcddzQMcrWEZslng0maOgzQMbTY+gimsvoiEDEz0Z+5lyPDyoLnZh25WRwDi8C
wZPb1t3b0lSvnZ1ur1mo0nufDnOiXbq+OszlZmskiJCbZeX62K1scSqVmUjdgCO1
AzhbRdBjL85J++VWG0gE7EjomwE9bJiL+qduN7DQPs9lcfoihCsyYMqNO5jSeJc=
=ZCOh
-----END PGP SIGNATURE-----
--17pEHd4RhPHOinZp--
|
