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
|
Return-Path: <keatonatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 014C8B94
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 11 Mar 2016 19:32:24 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f42.google.com (mail-oi0-f42.google.com
[209.85.218.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 296E414D
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 11 Mar 2016 19:32:22 +0000 (UTC)
Received: by mail-oi0-f42.google.com with SMTP id d205so93366828oia.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 11 Mar 2016 11:32:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=iNwMo+knjwiVmkpuoWQqw6VSz/nxwNcrRj8wiBv9Cms=;
b=Jn5OB7x1eLS83aVl6TK82EB5TP7nqHuldt7249fxMC1xW7cIK/z3ZNHMRSNUEfzi8g
StyBTWAfqOpK4B5fd7dx4vDAFIp6Mp9yxq0yqM88Rhb5pncXzSG1JiYn+3fKxGhHsSP9
nFi+Mrdpge5k7ddCRAsyXC0qOMnxEpsVQKlgUr8ABgUGnOYYbAZEEgSWdfyHn6Y1yD+1
YHrYafj2bgtScEEWUDt8T07NKgMfYnHGsHENkD8NmLjPfdpTmfVlj5n5f4Sru+vQBR4w
Mc70t/8e1iRmjcYmk6wXdqVDYSeWpuhdOKyrGMQNNTdlAPqQYFn/diCIcmkFyo1A6H2G
s/8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=iNwMo+knjwiVmkpuoWQqw6VSz/nxwNcrRj8wiBv9Cms=;
b=DWr4YV4IsZzUdK/1kr162DrsxUBne6wV9RkaV6VmazZEeElaM+oEjgijcStdboRVvM
58ng97a/Yq6na1fv+tBeDZtYr9Ng1dKxELKhZSOFT2tsTmYDtpAp2YZwW8ejINbROSwa
xFa8gcS8r3xSgfHNugHykdgkYKujDWxrDCB2NEawMdaEx+Xm+sd3RoeS2WVvuUkQm8Jp
JM/sGo8pzUpO/efqLUzdeLA0lTbQrUL7QKSYwO8cG9Nb+QQVuAsMQ7kS6nT2jxoxSdST
ZODi+zgPb+Z6UHCvjH6J1nlNKSnNdNQmM5eo3UExJwBxea9lLBJPZQJ5uLFXMFanT5zY
UdSA==
X-Gm-Message-State: AD7BkJI4tJlGehVCFn8MoXO7zDLxyVTzkxVNqoHjHzfj+o103Kj2GCjj/WytU2rfZY6fJKi26+Q8lJdqCLJdRw==
X-Received: by 10.202.193.10 with SMTP id r10mr6737283oif.126.1457724741607;
Fri, 11 Mar 2016 11:32:21 -0800 (PST)
MIME-Version: 1.0
References: <CAH+Axy6WVtb8Eib0aqS4Pp=zpjnsrDBbWRMmmBrJOZ3rFQAXww@mail.gmail.com>
<nbublk$d1f$1@ger.gmane.org>
In-Reply-To: <nbublk$d1f$1@ger.gmane.org>
From: James MacWhyte <macwhyte@gmail.com>
Date: Fri, 11 Mar 2016 19:32:12 +0000
Message-ID: <CAH+Axy5usVrkKb5w65evJceeR5WG8giHxtZ7uyDwePyRxjbBig@mail.gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>,
bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a113dc36e6765a6052dcafd5a
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 12 Mar 2016 04:54:41 +0000
Subject: Re: [bitcoin-dev] BIP75 - Out of Band Address Exchange
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2016 19:32:24 -0000
--001a113dc36e6765a6052dcafd5a
Content-Type: text/plain; charset=UTF-8
That's a valid point, and one we had thought of, which is why I wanted to
get everyone's opinion. I agree the proposed field extensions have nothing
to do with encryption, but does it make sense to propose a completely
separate BIP for such a small thing? If that is the accepted way to go, we
can split it into two and make a separate proposal.
On Fri, Mar 11, 2016 at 5:48 AM Andreas Schildbach via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> I think it's a bad idea to pollute the original idea of this BIP with
> other extensions. Other extensions should go to separate BIPs,
> especially since methods to clarify the fee have nothing to do with
> secure and authenticated bi-directional BIP70 communication.
>
>
> On 03/10/2016 10:43 PM, James MacWhyte via bitcoin-dev wrote:
> > Hi everyone,
> >
> > Our BIP (officially proposed on March 1) has tentatively been assigned
> > number 75. Also, the title has been changed to "Out of Band Address
> > Exchange using Payment Protocol Encryption" to be more accurate.
> >
> > We thought it would be good to take this opportunity to add some
> > optional fields to the BIP70 paymentDetails message. The new fields are:
> > subtractable fee (give permission to the sender to use some of the
> > requested amount towards the transaction fee), fee per kb (the minimum
> > fee required to be accepted as zeroconf), and replace by fee (whether or
> > not a transaction with the RBF flag will be accepted with zeroconf). I
> > know it doesn't make much sense for merchants to accept RBF with
> > zeroconf, so that last one might be used more to explicitly refuse RBF
> > transactions (and allow the automation of choosing a setting based on
> > who you are transacting with).
> >
> > I see BIP75 as a general modernization of BIP70, so I think it should be
> > fine to include these extensions in the new BIP, even though these
> > fields are not specific to the features we are proposing. Please take a
> > look at the relevant section and let me know if anyone has any concerns:
> >
> https://github.com/techguy613/bips/blob/master/bip-0075.mediawiki#Extending_BIP70_PaymentDetails
> >
> > The BIP70 extensions page in our fork has also been updated.
> >
> > Thanks!
> >
> > James
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a113dc36e6765a6052dcafd5a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">That's a valid point, and one we had thought of, which=
is why I wanted to get everyone's opinion. I agree the proposed field =
extensions have nothing to do with encryption, but does it make sense to pr=
opose a completely separate BIP for such a small thing? If that is the acce=
pted way to go, we can split it into two and make a separate proposal.</div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Mar 11, 2016 at 5:=
48 AM Andreas Schildbach via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@=
lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">I think it's a bad idea to=
pollute the original idea of this BIP with<br>
other extensions. Other extensions should go to separate BIPs,<br>
especially since methods to clarify the fee have nothing to do with<br>
secure and authenticated bi-directional BIP70 communication.<br>
<br>
<br>
On 03/10/2016 10:43 PM, James MacWhyte via bitcoin-dev wrote:<br>
> Hi everyone,<br>
><br>
> Our BIP (officially proposed on March 1) has tentatively been assigned=
<br>
> number 75. Also, the title has been changed to "Out of Band Addre=
ss<br>
> Exchange using Payment Protocol Encryption" to be more accurate.<=
br>
><br>
> We thought it would be good to take this opportunity to add some<br>
> optional fields to the BIP70 paymentDetails message. The new fields ar=
e:<br>
> subtractable fee (give permission to the sender to use some of the<br>
> requested amount towards the transaction fee), fee per kb (the minimum=
<br>
> fee required to be accepted as zeroconf), and replace by fee (whether =
or<br>
> not a transaction with the RBF flag will be accepted with zeroconf). I=
<br>
> know it doesn't make much sense for merchants to accept RBF with<b=
r>
> zeroconf, so that last one might be used more to explicitly refuse RBF=
<br>
> transactions (and allow the automation of choosing a setting based on<=
br>
> who you are transacting with).<br>
><br>
> I see BIP75 as a general modernization of BIP70, so I think it should =
be<br>
> fine to include these extensions in the new BIP, even though these<br>
> fields are not specific to the features we are proposing. Please take =
a<br>
> look at the relevant section and let me know if anyone has any concern=
s:<br>
> <a href=3D"https://github.com/techguy613/bips/blob/master/bip-0075.med=
iawiki#Extending_BIP70_PaymentDetails" rel=3D"noreferrer" target=3D"_blank"=
>https://github.com/techguy613/bips/blob/master/bip-0075.mediawiki#Extendin=
g_BIP70_PaymentDetails</a><br>
><br>
> The BIP70 extensions page in our fork has also been updated.<br>
><br>
> Thanks!<br>
><br>
> James<br>
><br>
><br>
> _______________________________________________<br>
> bitcoin-dev mailing list<br>
> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bl=
ank">bitcoin-dev@lists.linuxfoundation.org</a><br>
> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
><br>
<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--001a113dc36e6765a6052dcafd5a--
|
