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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <eric@voskuil.org>) id 1YJemC-0006tn-RN
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Feb 2015 09:00:36 +0000
X-ACL-Warn:
Received: from mail-pd0-f172.google.com ([209.85.192.172])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YJem7-0003jd-FD
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Feb 2015 09:00:36 +0000
Received: by pdjy10 with SMTP id y10so13508224pdj.9
for <bitcoin-development@lists.sourceforge.net>;
Fri, 06 Feb 2015 01:00:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
:subject:references:in-reply-to:content-type;
bh=tLGuMaZrOioyiYN8uXimHnwBwRmHDf7Bi7oR+aT2sYs=;
b=lLMjJiqucAmLkYkYia0lIULyu0wLLP1y+VSaW6Qhxc7RDJd4Tdx9pl85If0d6cuD95
HNyxMw8EjhW16sMVX4hadEuenQqBCClDq/rLaXdMlacehz+5D81CjlxABcC2OpHKUDaM
57W3gIdmOU+cqvUK9+keNu466rF1Jer3ZuMpmQlYw3ZWDLz0nBTkKxc/EBvWNg+q4RMr
Vo6zcInC+GAbPZYs5MIPwXY4jQEAHCdbJ+/Gt2vESFxJa6XDMMbu5TbYFTHsYNeFqlkt
Gd32mzQNGE34NSTlQwaZxgCg90xYFvUin2osF5PpFaBLqf8+Ox2YqdvWQtot6nMzwZSv
WToA==
X-Gm-Message-State: ALoCoQl1ldMfqHtnHJ8s4KlKWWp82Hc6C9HEmp5QvtmZW5UcrQZBTCyieM3eMX3/PEE65txCUzAf
X-Received: by 10.68.195.65 with SMTP id ic1mr4066263pbc.109.1423213225617;
Fri, 06 Feb 2015 01:00:25 -0800 (PST)
Received: from [10.0.1.3] (c-50-135-46-157.hsd1.wa.comcast.net.
[50.135.46.157])
by mx.google.com with ESMTPSA id oq2sm7336551pbb.60.2015.02.06.01.00.24
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 06 Feb 2015 01:00:24 -0800 (PST)
Message-ID: <54D482B8.9070108@voskuil.org>
Date: Fri, 06 Feb 2015 01:00:40 -0800
From: Eric Voskuil <eric@voskuil.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Andreas Schildbach <andreas@schildbach.de>,
bitcoin-development@lists.sourceforge.net
References: <544174F8.1050208@AndySchroder.com> <54D3FEE9.70502@AndySchroder.com> <54D40C7D.8090804@voskuil.org>
<mb1um3$ee3$1@ger.gmane.org>
In-Reply-To: <mb1um3$ee3$1@ger.gmane.org>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="2rQfG0Snou1R7x4an0G5V0UOWxD11UiVX"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1YJem7-0003jd-FD
Subject: Re: [Bitcoin-development] Two Proposed BIPs - Bluetooth
Communication and bitcoin: URI Scheme Improvements
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: Fri, 06 Feb 2015 09:00:36 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2rQfG0Snou1R7x4an0G5V0UOWxD11UiVX
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
On 02/06/2015 12:40 AM, Andreas Schildbach wrote:
> On 02/06/2015 01:36 AM, Eric Voskuil wrote:
>=20
>> The main advantage of BLE over BT is that it uses much less power, wit=
h
>> a trade-off in lower bandwidth (100 kbps vs. 2 mbps). The BLE range ca=
n
>> be even greater and connection latency lower than BT. For payment
>> purposes the lower bandwidth isn't much of a hit.
>=20
> I'm all for extending the BT:<mac> scheme to Bluetooth LE. If you have
> ideas how this can be done please let us know. I haven't had a chance t=
o
> play around with LE because none of my devices support it.
>=20
> I suspect the way how Bluetooth LE transfers files (like payment
> requests) is opening a plain old Bluetooth socket. If this is true, I'm=
> afraid Bluetooth LE would not add anything for sending the BIP70
> messages back and forth. Note signed payment requests can easily be 4 k=
B
> in size, so speed *does* matter.
Hi Andreas,
I haven't expressed any preference for BLE, just answering questions
that were raised about it. The main thing that BLE brings to the table
is increased battery life, but with larger transfers that benefit is
reduced.
e
--2rQfG0Snou1R7x4an0G5V0UOWxD11UiVX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU1IK5AAoJEDzYwH8LXOFOKAoH/2kdhzGTS/uVi0+qDXI6M+qD
hYXAa2cBtOjCSdKSs+c07emTEr9UbkcDbKCUbpm2syu/RDzo5mArsmt9lhV5Yh5b
0Sc8kMHZOwiB/HS1eIQuHibilgMu+DJLj9yU9cRSY9Ywl0GxfKxnPcU6s2TOtvAE
wECMwySJT1z9LBGCLlF0zYhd5EjFcJ1l4CDLX+zL7ire867md9T3DrQ0q10+SsVT
Ok9RRibrYxC1KoxfHaFhki7t/fiW88yAURJoD0A++TJmwrUx1Hn+zopkjM5rK2OV
w5t7pcW0K+3j5BHYbP7JP6nrmNyoTszOXLB5UifCjEk2iurhTncYVjUBtrc4MrY=
=x+xp
-----END PGP SIGNATURE-----
--2rQfG0Snou1R7x4an0G5V0UOWxD11UiVX--
|
