summaryrefslogtreecommitdiff
path: root/73/4eaefdfe97da608ea8ccb5ec68ceb182d73720
blob: 0fccde9455a6c7fa2d82a4376b6d24114fe5b5e9 (plain)
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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <alexy.kot.all@gmail.com>) id 1X2GEp-0004Dv-64
	for bitcoin-development@lists.sourceforge.net;
	Wed, 02 Jul 2014 08:49:59 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.170 as permitted sender)
	client-ip=209.85.220.170; envelope-from=alexy.kot.all@gmail.com;
	helo=mail-vc0-f170.google.com; 
Received: from mail-vc0-f170.google.com ([209.85.220.170])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X2GEn-0005HU-B9
	for bitcoin-development@lists.sourceforge.net;
	Wed, 02 Jul 2014 08:49:59 +0000
Received: by mail-vc0-f170.google.com with SMTP id hy10so10064394vcb.15
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 02 Jul 2014 01:49:51 -0700 (PDT)
X-Received: by 10.58.208.170 with SMTP id mf10mr30673568vec.22.1404290991725; 
	Wed, 02 Jul 2014 01:49:51 -0700 (PDT)
MIME-Version: 1.0
Sender: alexy.kot.all@gmail.com
Received: by 10.58.237.129 with HTTP; Wed, 2 Jul 2014 01:49:10 -0700 (PDT)
In-Reply-To: <CANEZrP1=Z+DPDFiLsE2sqYQ7gYSm2U6gmFNfCoLpkuR1M7qaAQ@mail.gmail.com>
References: <leuunm$tjk$1@ger.gmane.org>
	<CANEZrP0J849oDvMWjf8LWi0xj44Q8DaUwDip5_smVBMNgeQ3mw@mail.gmail.com>
	<CALDj+BZJ0rSKuDHdbL7ANN0Vtaa3-KGYgusqMDzzB-CUxjMz7g@mail.gmail.com>
	<CANEZrP3szn=oQS+ZuqSzjUoSAjtkyPxPWJFaU1vDW43dRNVeNQ@mail.gmail.com>
	<20140320215208.GC88006@giles.gnomon.org.uk>
	<CANEZrP3kHRJ6U-O_Jgei4U6s9GyQGvB_p5ChtcHJEkYR0wWPvQ@mail.gmail.com>
	<20140326224826.GE62995@giles.gnomon.org.uk>
	<CANEZrP2HtJsOf5zOsPz32U=Jot7U9k80yEu=hj5uMPkRC+WGsQ@mail.gmail.com>
	<lgvnc2$eu4$1@ger.gmane.org>
	<CANEZrP1==hL1mW6SWV0qXUMVVx7U_HUXtorpb7qVK2R4mOfzbg@mail.gmail.com>
	<A1269E16-63BC-44D5-B460-D793D45587AD@riseup.net>
	<CALDj+BYkOyNuEiiuTgjd7L-ZeHN4Mb4034W+OeCFob1RwJn=Vg@mail.gmail.com>
	<CANEZrP1HvKAg6d7tTcnY3BJr0_5LuCN1FGYQvQ1+RpL1B6cwHw@mail.gmail.com>
	<D4B82FD9-8078-48B2-9F91-8A3AB23AEAA7@osfda.org>
	<CALDj+BZ8_YB0DHiaGZPq4MB-dvkRqJhBFazcfnrrPX4EvRxbeQ@mail.gmail.com>
	<louibr$8gc$1@ger.gmane.org>
	<1016E2A3-C678-46FA-B80E-F9D86FDEA213@osfda.org>
	<louknu$7ja$1@ger.gmane.org>
	<CALDj+BZveYWed4Redvncdf=h3pEvBYosgAO3stUvhN2gxbb1UQ@mail.gmail.com>
	<CANEZrP1=Z+DPDFiLsE2sqYQ7gYSm2U6gmFNfCoLpkuR1M7qaAQ@mail.gmail.com>
From: Alex Kotenko <alexykot@gmail.com>
Date: Wed, 2 Jul 2014 09:49:10 +0100
X-Google-Sender-Auth: zSNNsZd15qS1dGmCB1R7SJzAth4
Message-ID: <CALDj+BZ-_4XMB5ZAKX6ZSNeWRj71Mo0w4-bR-gYNGPv14rWKng@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=047d7bdc17f6b9228704fd31f9db
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: 1X2GEn-0005HU-B9
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andreas Schildbach <andreas@schildbach.de>
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: Wed, 02 Jul 2014 08:49:59 -0000

--047d7bdc17f6b9228704fd31f9db
Content-Type: text/plain; charset=UTF-8

Ok, agreed. I will submit a pull request to BIP72 then.
Not sure about escaping though. It is indeed not critical for bitcoin URIs,
but still it is a part of RFC, don't think we should go against it.

Andreas, we will implement this on our side, with bluetooth on r= and web
address on r1=.


2014-07-01 18:59 GMT+01:00 Mike Hearn <mike@plan99.net>:

> Nope, r1/r2 sounds good to me. BTW we should update the spec to reflect
> that escaping is largely unnecessary in many cases.
>
>
>

--047d7bdc17f6b9228704fd31f9db
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:courier =
new,monospace;color:#003300">Ok, agreed. I will submit a pull request to BI=
P72 then.</div><div class=3D"gmail_default" style=3D"font-family:courier ne=
w,monospace;color:#003300">

Not sure about escaping though. It is indeed not critical for bitcoin URIs,=
 but still it is a part of RFC, don&#39;t think we should go against it.</d=
iv><div class=3D"gmail_default" style=3D"font-family:courier new,monospace;=
color:#003300">

<br></div><div class=3D"gmail_default" style=3D"font-family:courier new,mon=
ospace;color:#003300">Andreas, we will implement this on our side, with blu=
etooth on r=3D and web address on r1=3D.</div><div class=3D"gmail_extra"><b=
r></div>

<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2014-07-01 18:59 =
GMT+01:00 Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"mailto:mike@plan99.ne=
t" target=3D"_blank">mike@plan99.net</a>&gt;</span>:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

<div dir=3D"ltr"><div class=3D"gmail_extra">Nope, r1/r2 sounds good to me. =
BTW we should update the spec to reflect that escaping is largely unnecessa=
ry in many cases.</div><div class=3D"gmail_extra"><br></div><div class=3D"g=
mail_extra">


<br></div></div>
</blockquote></div><br></div></div>

--047d7bdc17f6b9228704fd31f9db--