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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WTtKe-0004kG-Hd
for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 13:29:56 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.50 as permitted sender)
client-ip=209.85.219.50; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f50.google.com;
Received: from mail-oa0-f50.google.com ([209.85.219.50])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WTtKb-0007xB-8m
for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 13:29:56 +0000
Received: by mail-oa0-f50.google.com with SMTP id i7so7305653oag.23
for <bitcoin-development@lists.sourceforge.net>;
Sat, 29 Mar 2014 06:29:48 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.117.73 with SMTP id kc9mr12118204obb.20.1396099787893;
Sat, 29 Mar 2014 06:29:47 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Sat, 29 Mar 2014 06:29:47 -0700 (PDT)
In-Reply-To: <20140329092721.GG62995@giles.gnomon.org.uk>
References: <CANEZrP0AwR3WgHfwYWcrC9Z_MHPDwymWXAQwp7D8XZ+o2FsK8g@mail.gmail.com>
<lh3m7i$v18$1@ger.gmane.org>
<CANEZrP3zBFs=JpJi6eazTvrTaRX6XCJLu-zrraE6bezYW7b9pQ@mail.gmail.com>
<lh49pp$4bc$1@ger.gmane.org> <5335BD17.6050408@plan99.net>
<lh4nma$h3e$1@ger.gmane.org>
<20140329092721.GG62995@giles.gnomon.org.uk>
Date: Sat, 29 Mar 2014 14:29:47 +0100
X-Google-Sender-Auth: gSF93f3Y8QKASqPya0wxcpoSErc
Message-ID: <CANEZrP3+-kJiO+pCAdEGtzebcR65eAnTjuFQgQPbzAmh6v-WyQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Roy Badami <roy@gnomon.org.uk>
Content-Type: multipart/alternative; boundary=f46d044796f3edc6f704f5becf1e
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: 1WTtKb-0007xB-8m
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: Sat, 29 Mar 2014 13:29:56 -0000
--f46d044796f3edc6f704f5becf1e
Content-Type: text/plain; charset=UTF-8
So how about we say two months? That way it's easy for merchants to comply
with the EU DSD and we keep RAM usage in check until we come up with a more
sophisticated refund scheme.
There's another issue with BIP 70 and refunds that I noticed. The
PaymentRequest doesn't specify whether refunds are possible. So wallets
have to either never submit refund data, or always submit it even if it
makes no sense. Because setting things up to get refunds has a non-zero
cost for the sender, it'd help if we could optimise it away for merchants
that simply refuse to issue refunds for whatever reason.
On Sat, Mar 29, 2014 at 10:27 AM, Roy Badami <roy@gnomon.org.uk> wrote:
> On Fri, Mar 28, 2014 at 09:56:57PM +0100, Andreas Schildbach wrote:
> > On 03/28/2014 07:19 PM, Mike Hearn wrote:
> >
> > >> Ok, why don't fix this in the spec for now, by defining a fixed expiry
> > >> time. In the EU, most products are covered by a 2 years warranty, so
> it
> > >> seems appropriate to pick 2.5 years (30 months) -- allowing for some
> > >> time to ship the product back and forth.
> > >
> > > Yeah I was thinking something like that on the walk home. But 2 years
> is
> > > a long time. Do we have enough RAM for that?
> >
> > It depends on usage stats, script size, etc...
> >
> > > Plus warranties usually
> > > result in the defective goods being replaced rather than a monetary
> > > refund, right?
> >
> > Usually yes. The next smaller "unit of time" in Germany would be two
> > weeks, the so-called "Fernabsatzgesetz". It allows you to send back
> > mail-orders and usually you want the money back. Don't know if that made
> > it into EU law or how it applies to other countries.
>
> It's EU law, but the Distance Selling Directive only says "at least
> seven days", so the exact period probably varies by country (in the UK
> it is 7 days).
>
> But the clock only starts ticking when you receive the goods, and the
> Distance Selling Directive allows the supplier 30 days "to execute the
> order" (I *think* the 30 days always has to include shipping, because
> for consumer contracts title doesn't pass until the goods are
> delivered, so the order wouldn't be considered complete until then).
>
> So I think latest possible deadline for returning the goods for refund
> could be up to 30 days to execute the order plus "at least 7 days"
> (with some countries allowing more). Plus, conceivably, shipping
> time, if some member states have chosen to interpret the 30 day
> execution differently.
>
> So I think this adds up to "a couple of months, give or take". In
> practice, though, even a couple of months is a bit on the short time.
> What if the goods are delayed. How many people have had miner orders
> outstanding for the best part of a year?
>
> roy
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--f46d044796f3edc6f704f5becf1e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">So how about we say two months? That way it's easy for=
merchants to comply with the EU DSD and we keep RAM usage in check until w=
e come up with a more sophisticated refund scheme.<div><br></div><div>There=
's another issue with BIP 70 and refunds that I noticed. The PaymentReq=
uest doesn't specify whether refunds are possible. So wallets have to e=
ither never submit refund data, or always submit it even if it makes no sen=
se. Because setting things up to get refunds has a non-zero cost for the se=
nder, it'd help if we could optimise it away for merchants that simply =
refuse to issue refunds for whatever reason.</div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Mar 29, 2014 at 10:27 AM, Roy Badami <span dir=3D"ltr"><=
<a href=3D"mailto:roy@gnomon.org.uk" target=3D"_blank">roy@gnomon.org.uk</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"><div class=3D"">On Fri, Mar 28, 2014 at 09:5=
6:57PM +0100, Andreas Schildbach wrote:<br>
> On 03/28/2014 07:19 PM, Mike Hearn wrote:<br>
><br>
> >> Ok, why don't fix this in the spec for now, by defining a=
fixed expiry<br>
> >> time. In the EU, most products are covered by a 2 years warra=
nty, so it<br>
> >> seems appropriate to pick 2.5 years (30 months) -- allowing f=
or some<br>
> >> time to ship the product back and forth.<br>
> ><br>
> > Yeah I was thinking something like that on the walk home. But 2 y=
ears is<br>
> > a long time. Do we have enough RAM for that?<br>
><br>
> It depends on usage stats, script size, etc...<br>
><br>
> > Plus warranties usually<br>
> > result in the defective goods being replaced rather than a moneta=
ry<br>
> > refund, right?<br>
><br>
> Usually yes. The next smaller "unit of time" in Germany woul=
d be two<br>
> weeks, the so-called "Fernabsatzgesetz". It allows you to se=
nd back<br>
> mail-orders and usually you want the money back. Don't know if tha=
t made<br>
> it into EU law or how it applies to other countries.<br>
<br>
</div>It's EU law, but the Distance Selling Directive only says "a=
t least<br>
seven days", so the exact period probably varies by country (in the UK=
<br>
it is 7 days).<br>
<br>
But the clock only starts ticking when you receive the goods, and the<br>
Distance Selling Directive allows the supplier 30 days "to execute the=
<br>
order" (I *think* the 30 days always has to include shipping, because<=
br>
for consumer contracts title doesn't pass until the goods are<br>
delivered, so the order wouldn't be considered complete until then).<br=
>
<br>
So I think latest possible deadline for returning the goods for refund<br>
could be up to 30 days to execute the order plus "at least 7 days"=
;<br>
(with some countries allowing more). =C2=A0Plus, conceivably, shipping<br>
time, if some member states have chosen to interpret the 30 day<br>
execution differently.<br>
<br>
So I think this adds up to "a couple of months, give or take". =
=C2=A0In<br>
practice, though, even a couple of months is a bit on the short time.<br>
What if the goods are delayed. =C2=A0How many people have had miner orders<=
br>
outstanding for the best part of a year?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
roy<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
---------------------------------------------------------------------------=
---<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>
</div></div></blockquote></div><br></div>
--f46d044796f3edc6f704f5becf1e--
|
