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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <alexy.kot.all@gmail.com>) id 1WR1XD-00021O-N2
for bitcoin-development@lists.sourceforge.net;
Fri, 21 Mar 2014 15:39:03 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.175 as permitted sender)
client-ip=209.85.128.175; envelope-from=alexy.kot.all@gmail.com;
helo=mail-ve0-f175.google.com;
Received: from mail-ve0-f175.google.com ([209.85.128.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WR1XC-0007Et-SE
for bitcoin-development@lists.sourceforge.net;
Fri, 21 Mar 2014 15:39:03 +0000
Received: by mail-ve0-f175.google.com with SMTP id oz11so2730020veb.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 21 Mar 2014 08:38:57 -0700 (PDT)
X-Received: by 10.58.38.166 with SMTP id h6mr17069209vek.22.1395416337294;
Fri, 21 Mar 2014 08:38:57 -0700 (PDT)
MIME-Version: 1.0
Sender: alexy.kot.all@gmail.com
Received: by 10.59.0.38 with HTTP; Fri, 21 Mar 2014 08:38:17 -0700 (PDT)
In-Reply-To: <lghjle$2er$1@ger.gmane.org>
References: <lc5hmg$1jh$1@ger.gmane.org> <leuunm$tjk$1@ger.gmane.org>
<CANEZrP3nQfvDArKTRgje0Cus4G2JD_zpxSjA3fXfxM2TNAP80Q@mail.gmail.com>
<CALDj+BafD+6KTNcYDBEu5gNPzYozSkiC-JCxrY-PzXL2DYBRsw@mail.gmail.com>
<lge7lv$3mf$1@ger.gmane.org>
<CALDj+BZRsXnU5w=1B+01PDfMPY-7zqU3GP_52vr9wknEdTJ59Q@mail.gmail.com>
<lgh1q8$1dc$1@ger.gmane.org>
<CALDj+Bb=CR1pL0Ze1M6k22wfQM1bL6-w+EyipJQWc1OHhAY0rg@mail.gmail.com>
<lghjle$2er$1@ger.gmane.org>
From: Alex Kotenko <alexykot@gmail.com>
Date: Fri, 21 Mar 2014 15:38:17 +0000
X-Google-Sender-Auth: AW9WE_b4gqlHhuqJY7B0YdX4hlQ
Message-ID: <CALDj+Ba3WKdLYkmjHSgepmwXYv-QhB0K5d4HKSykY93XpnVPxQ@mail.gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=089e013a0d40192a5e04f51fafaa
X-Spam-Score: -0.6 (/)
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
(alexy.kot.all[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1WR1XC-0007Et-SE
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments
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, 21 Mar 2014 15:39:03 -0000
--089e013a0d40192a5e04f51fafaa
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
2014-03-21 14:51 GMT+00:00 Andreas Schildbach <andreas@schildbach.de>:
>
> Quoting from RFC 3986, Section 3.4. Query: "The characters slash ("/")
> and question mark ("?") may represent data within the query component."
>
Ok.=E2=80=8B=E2=80=8B
So BIP72 with a BT URI in the 'r' parameter?
Yes.=E2=80=8B=E2=80=8B
--089e013a0d40192a5e04f51fafaa
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
2014-03-21 14:51 GMT+00:00 Andreas Schildbach <span dir=3D"ltr"><<a href=
=3D"mailto:andreas@schildbach.de" target=3D"_blank">andreas@schildbach.de</=
a>></span>:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
Quoting from RFC 3986, Section 3.4. Query: =C2=A0"The characters slash=
("/")<br>
and question mark ("?") may represent data within the query compo=
nent."<br></blockquote><div class=3D"gmail_default" style=3D"font-fami=
ly:'courier new',monospace;color:rgb(0,51,0)">Ok.=E2=80=8B=E2=80=8B=
<br><br></div><div class=3D"gmail_default" style=3D"font-family:'courie=
r new',monospace;color:rgb(0,51,0)">
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
So BIP72 with a BT URI in the 'r' parameter?</blockquote><div class=
=3D"gmail_default" style=3D"font-family:'courier new',monospace;col=
or:rgb(0,51,0)">Yes.=E2=80=8B=E2=80=8B</div></div><br><br>
</div></div>
--089e013a0d40192a5e04f51fafaa--
|
