summaryrefslogtreecommitdiff
path: root/63/5a3f2fce53e89db2c7a10cbe462084ad7e8f2a
blob: 9e6cbec7b7e2ae2556e6fc93d2b5821b80d01647 (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
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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <tamas@bitsofproof.com>) id 1WTVDk-0007en-Qq
	for bitcoin-development@lists.sourceforge.net;
	Fri, 28 Mar 2014 11:45:12 +0000
X-ACL-Warn: 
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1WTVDi-0004Q6-Sh
	for bitcoin-development@lists.sourceforge.net;
	Fri, 28 Mar 2014 11:45:12 +0000
Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated
	by wp059.webpack.hosteurope.de running ExIM with esmtpsa
	(TLS1.0:RSA_AES_128_CBC_SHA1:16)
	id 1WTVDc-0001VI-Ja; Fri, 28 Mar 2014 12:45:04 +0100
Content-Type: multipart/signed;
	boundary="Apple-Mail=_442A202D-9105-40A7-B809-429540527FD8";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <CA+s+GJCf9o6VEky=JXgrG8v39hyQtPz71yuftF_jyp0bX9WHsA@mail.gmail.com>
Date: Fri, 28 Mar 2014 12:45:03 +0100
Message-Id: <122FC5AD-2117-4CAF-817F-45B00F57D549@bitsofproof.com>
References: <CANEZrP0AwR3WgHfwYWcrC9Z_MHPDwymWXAQwp7D8XZ+o2FsK8g@mail.gmail.com>
	<lh3m7i$v18$1@ger.gmane.org>
	<CA+s+GJCf9o6VEky=JXgrG8v39hyQtPz71yuftF_jyp0bX9WHsA@mail.gmail.com>
To: Wladimir <laanwj@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1396007110;
	952584a0; 
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1WTVDi-0004Q6-Sh
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP 70 refund field
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, 28 Mar 2014 11:45:13 -0000


--Apple-Mail=_442A202D-9105-40A7-B809-429540527FD8
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_E679D78B-D160-4F41-A014-48F69BB53CED"


--Apple-Mail=_E679D78B-D160-4F41-A014-48F69BB53CED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Yes, you begin to see that the payment protocol, as is has a too narrow =
scope of a web cart - customer, and does not even fit that.

It is not about payment requests but about business relationships. We =
need a protocol that deals with that concept instead of individual =
requests,
so we really get out of the hell of addresses. Business relationships =
are terminated by the parties at their own and not bey algorithms and =
timeouts.

Regards,

Tamas Blummer
http://bitsofproof.com

On 28.03.2014, at 12:38, Wladimir <laanwj@gmail.com> wrote:

>=20
> On Fri, Mar 28, 2014 at 12:25 PM, Andreas Schildbach =
<andreas@schildbach.de> wrote:
> I see the problem.
>=20
> However, I don't see how PaymentDetails can be an answer. None of the
> fields (other than outputs and network) can be known in advance (at =
the
> time of the initial payment).
>=20
> You're probably aiming for an expires field? How would you refund a
> payment after expiry? Note its not your choice wether to refund a
> payment -- it can be ordered by a court years after the payment =
happened.
>=20
> Communication between the merchant and buyer would be needed in this =
case.
>=20
> I'd say that would be not unreasonable if something is to be refunded =
after a year or more. After all, people may have moved, bank accounts =
changed, even outside the bitcoin world.
>=20
> It should probably not be accepted to set a very low expiration time =
for the refund address, like <3 months, as it's as bad as not providing =
a refund address at all and brings back all the pre-BIP70 confusion.
>=20
> Wladimir
>=20
> =
--------------------------------------------------------------------------=
----
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--Apple-Mail=_E679D78B-D160-4F41-A014-48F69BB53CED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div =
apple-content-edited=3D"true">Yes, you begin to see that the payment =
protocol, as is has a too narrow scope of a web cart - customer, and =
does not even fit that.</div><div =
apple-content-edited=3D"true"><br></div><div =
apple-content-edited=3D"true">It is not about payment requests but about =
business relationships. We need a protocol that deals with that concept =
instead of individual requests,</div><div apple-content-edited=3D"true">so=
 we really get out of the hell of addresses. Business relationships are =
terminated by the parties at their own and not bey algorithms and =
timeouts.</div><div apple-content-edited=3D"true"><br style=3D"color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; "><span style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
display: inline !important; float: none; ">Regards,</span><br =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; "><br style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
medium; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; display: inline !important; float: none; =
">Tamas Blummer</span><br style=3D"color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; display: inline !important; float: none; =
"><a href=3D"http://bitsofproof.com">http://bitsofproof.com</a></span>
</div>
<br><div><div>On 28.03.2014, at 12:38, Wladimir &lt;<a =
href=3D"mailto:laanwj@gmail.com">laanwj@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Fri, Mar 28, 2014 at 12:25 PM, Andreas =
Schildbach <span dir=3D"ltr">&lt;<a href=3D"mailto:andreas@schildbach.de" =
target=3D"_blank">andreas@schildbach.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">I see the problem.<br>
<br>
However, I don't see how PaymentDetails can be an answer. None of =
the<br>
fields (other than outputs and network) can be known in advance (at =
the<br>
time of the initial payment).<br>
<br>
You're probably aiming for an expires field? How would you refund a<br>
payment after expiry? Note its not your choice wether to refund a<br>
payment -- it can be ordered by a court years after the payment =
happened.<br></blockquote><div><br></div><div>Communication between the =
merchant and buyer would be needed in this case.<br><br></div><div>I'd =
say that would be not unreasonable if something is to be refunded after =
a year or more. After all, people may have moved, bank accounts changed, =
even outside the bitcoin world.<br>
<br></div><div>It should probably not be accepted to set a very low =
expiration time for the refund address, like &lt;3 months, as it's as =
bad as not providing a refund address at all and brings back all the =
pre-BIP70 confusion.<br>
</div><div></div><div><br></div><div =
class=3D"h5">Wladimir<br></div></div><br></div></div>
=
--------------------------------------------------------------------------=
----<br>_______________________________________________<br>Bitcoin-develop=
ment mailing list<br><a =
href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-developm=
ent@lists.sourceforge.net</a><br>https://lists.sourceforge.net/lists/listi=
nfo/bitcoin-development<br></blockquote></div><br></body></html>=

--Apple-Mail=_E679D78B-D160-4F41-A014-48F69BB53CED--

--Apple-Mail=_442A202D-9105-40A7-B809-429540527FD8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTNWDAAAoJEPZykcUXcTkc2fUH/2uCZMruCAH2E+BXc5MYOJR7
KeIK2ffpzFeR784xxywVtKJgvHiKIap1tB8oiOwIdsWfNFLVs+zNhs3jtkySHI+7
ly7qMgHZsxARAigahPV1qlbhkztnn5QvzQjGMUZxUC9DcKDgMbxt9kIfF04wzHs0
PFngTtGDur7QlbsQCqhEmK/POU4XyNvunGV6uUFChrqobU4/LYRBtccbHjSN6NmZ
FKrgt4fjn8tZQjZEU8DnTXjq4xcJWK4umpwMiu+rBX50EMJ9QsI00HGvLkJijdsv
VCxDFmAWzbF06wCDd4DLgEHV0DqvbVXuwlkXaTRzEg0Qc//HteOW03E4jH256B8=
=FJrP
-----END PGP SIGNATURE-----

--Apple-Mail=_442A202D-9105-40A7-B809-429540527FD8--