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
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WLbea-0006Ij-CW
for bitcoin-development@lists.sourceforge.net;
Thu, 06 Mar 2014 17:00:16 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.174 as permitted sender)
client-ip=209.85.220.174; envelope-from=mh.in.england@gmail.com;
helo=mail-vc0-f174.google.com;
Received: from mail-vc0-f174.google.com ([209.85.220.174])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WLbeZ-00048U-69
for bitcoin-development@lists.sourceforge.net;
Thu, 06 Mar 2014 17:00:16 +0000
Received: by mail-vc0-f174.google.com with SMTP id im17so2890922vcb.33
for <bitcoin-development@lists.sourceforge.net>;
Thu, 06 Mar 2014 09:00:05 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.52.122.14 with SMTP id lo14mr1029363vdb.38.1394125205520;
Thu, 06 Mar 2014 09:00:05 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.52.24.38 with HTTP; Thu, 6 Mar 2014 09:00:05 -0800 (PST)
In-Reply-To: <lfa9ab$k1c$1@ger.gmane.org>
References: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>
<lf9m0e$q7t$1@ger.gmane.org>
<CANEZrP2GbnsqQANGKMW_5FAugppGJEksaB=Tf8Xu1nRLy3z9yg@mail.gmail.com>
<lfa20f$i2k$1@ger.gmane.org> <lfa9ab$k1c$1@ger.gmane.org>
Date: Thu, 6 Mar 2014 18:00:05 +0100
X-Google-Sender-Auth: nSEI9QqjVagPWs9AZ0iZ7IbEwGw
Message-ID: <CANEZrP2dsaOG9SpSr3SF48ErpRhFzxCACqA-t0wt6r1QaiZSvw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=089e013a1b22a5c64004f3f31173
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WLbeZ-00048U-69
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Instant / contactless payments, IsoDep
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: Thu, 06 Mar 2014 17:00:16 -0000
--089e013a1b22a5c64004f3f31173
Content-Type: text/plain; charset=UTF-8
I think maybe the way you do it is to have a NDEF tag that triggers the
app, and then that starts an IsoDep protocol once opened. I *think*.
On Thu, Mar 6, 2014 at 5:55 PM, Andreas Schildbach <andreas@schildbach.de>wrote:
> On 03/06/2014 03:51 PM, Andreas Schildbach wrote:
>
> >> I'm not sure if iso-dep is the way to go here. Afaik as soon as you
> pick
> >> up the phone the connection breaks.
> >>
> >> If the phone isn't willing to immediately authorise then it'd have to
> >> fall back to HTTPS or Bluetooth as normal.
> >
> > Ok, that would be an option.
>
> One of the first things to explore is if its possible to dispatch
> different isodep applications to different apps. I know you can add an
> intent filter matching action=android.nfc.action.TECH_DISCOVERED and a
> custom "tech filter" android.nfc.tech.IsoDep. However, as long as there
> is no mime type or similar concept, apps will always fight for access to
> IsoDep endpoints. We will want to avoid that situation.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries. Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--089e013a1b22a5c64004f3f31173
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I think maybe the way you do it is to have a NDEF tag that=
triggers the app, and then that starts an IsoDep protocol once opened. I *=
think*.</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">=
On Thu, Mar 6, 2014 at 5:55 PM, Andreas Schildbach <span dir=3D"ltr"><<a=
href=3D"mailto:andreas@schildbach.de" target=3D"_blank">andreas@schildbach=
.de</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 03/06/2014 03:51 PM, Andreas Schildbach w=
rote:<br>
<br>
>> =C2=A0 =C2=A0 I'm not sure if iso-dep is the way to go here. A=
faik as soon as you pick<br>
>> =C2=A0 =C2=A0 up the phone the connection breaks.<br>
>><br>
>> If the phone isn't willing to immediately authorise then it=
9;d have to<br>
>> fall back to HTTPS or Bluetooth as normal.<br>
><br>
> Ok, that would be an option.<br>
<br>
One of the first things to explore is if its possible to dispatch<br>
different isodep applications to different apps. I know you can add an<br>
intent filter matching action=3Dandroid.nfc.action.TECH_DISCOVERED and a<br=
>
custom "tech filter" android.nfc.tech.IsoDep. However, as long as=
there<br>
is no mime type or similar concept, apps will always fight for access to<br=
>
IsoDep endpoints. We will want to avoid that situation.<br>
<br>
<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
Subversion Kills Productivity. Get off Subversion & Make the Move to Pe=
rforce.<br>
With Perforce, you get hassle-free workflows. Merge that actually works.<br=
>
Faster operations. Version large binaries. =C2=A0Built-in WAN optimization =
and the<br>
freedom to use Git, Perforce or both. Make the move to Perforce.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D122218951&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D122218951&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
--089e013a1b22a5c64004f3f31173--
|
