diff options
| author | Alex Kotenko <alexykot@gmail.com> | 2014-07-01 18:18:23 +0100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-07-01 17:18:31 +0000 |
| commit | 832ad98c2e63474ee450540e3fab413842168563 (patch) | |
| tree | 8c11dd956298cfb1def8408080d2fd87066eff80 | |
| parent | b148e108d204cb2df12e72453a7ea947c6c0bd31 (diff) | |
| download | pi-bitcoindev-832ad98c2e63474ee450540e3fab413842168563.tar.gz pi-bitcoindev-832ad98c2e63474ee450540e3fab413842168563.zip | |
Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments
| -rw-r--r-- | 3c/4d9310a8413d1516ab6011d06953cde79289fc | 486 |
1 files changed, 486 insertions, 0 deletions
diff --git a/3c/4d9310a8413d1516ab6011d06953cde79289fc b/3c/4d9310a8413d1516ab6011d06953cde79289fc new file mode 100644 index 000000000..88c8852c0 --- /dev/null +++ b/3c/4d9310a8413d1516ab6011d06953cde79289fc @@ -0,0 +1,486 @@ +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 1X21hP-0000Dy-7u + for bitcoin-development@lists.sourceforge.net; + Tue, 01 Jul 2014 17:18:31 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.220.172 as permitted sender) + client-ip=209.85.220.172; envelope-from=alexy.kot.all@gmail.com; + helo=mail-vc0-f172.google.com; +Received: from mail-vc0-f172.google.com ([209.85.220.172]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1X21hN-0003d7-GY + for bitcoin-development@lists.sourceforge.net; + Tue, 01 Jul 2014 17:18:31 +0000 +Received: by mail-vc0-f172.google.com with SMTP id hy10so9214581vcb.31 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 01 Jul 2014 10:18:24 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.52.92.12 with SMTP id ci12mr61619vdb.90.1404235103886; Tue, + 01 Jul 2014 10:18:23 -0700 (PDT) +Sender: alexy.kot.all@gmail.com +Received: by 10.58.237.129 with HTTP; Tue, 1 Jul 2014 10:18:23 -0700 (PDT) +Received: by 10.58.237.129 with HTTP; Tue, 1 Jul 2014 10:18:23 -0700 (PDT) +In-Reply-To: <louknu$7ja$1@ger.gmane.org> +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> +Date: Tue, 1 Jul 2014 18:18:23 +0100 +X-Google-Sender-Auth: 3_bS-Nr26D09eZsBaUIq3zgtxsw +Message-ID: <CALDj+BZveYWed4Redvncdf=h3pEvBYosgAO3stUvhN2gxbb1UQ@mail.gmail.com> +From: Alex Kotenko <alexykot@gmail.com> +To: Andreas Schildbach <andreas@schildbach.de> +Content-Type: multipart/alternative; boundary=20cf3071c6c68c637a04fd24f6de +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: 1X21hN-0003d7-GY +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: Tue, 01 Jul 2014 17:18:31 -0000 + +--20cf3071c6c68c637a04fd24f6de +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +Hmm, r1, r2 etc is actually interesting. It takes less chars then array +(yes, array brackets have to be escaped) and provides unlimited number of +options, uniformed approach and priority definition. I'd say that is the +way to go. Any objections? +On 1 Jul 2014 16:39, "Andreas Schildbach" <andreas@schildbach.de> wrote: + +> Ok, one more idea: +> r=3D is used for the first URL, and we *think* of it as r0=3D +> additional URLs are appended as +> r1=3D +> r2=3D +> and so on. This would also define an ordering in case we need it. +> +> +> On 07/01/2014 05:07 PM, Michael Wozniak wrote: +> > Multiple parameters is currently undefined as far as I can tell. Shoul= +d +> the client take the first, last, or ignore it completely if there are +> multiple of any parameter? I think that=E2=80=99s the point of the param= +eter +> pollution discussion, which will define it one way or the other. +> > +> > I=E2=80=99m only familiar with the Electrum implementation, which is cu= +rrently +> checking for any duplicate parameters and treating the entire URI as +> invalid if duplicate parameters exist (following the parameter pollution +> suggestions). +> > +> > - +> > Michael Wozniak +> > +> > On Jul 1, 2014, at 10:59 AM, Andreas Schildbach <andreas@schildbach.de> +> wrote: +> > +> >> Does r[]=3D really need to be encoded as r%5B1%5D=3D ? In this case, I= +'d +> >> advocate for a simple array parameter name, like rs=3D ("plural" of r)= +. +> >> Length really does matter for QR codes. +> >> +> >> I'm fine with either multiple r=3D params or exactly one r=3D plus zer= +o to +> >> many r[]=3D params. Although I think it is a violation of the (current= +) +> >> spec to choke on more than one r=3D parameters, I admit that bitcoinj = +is +> >> currently implemented that way. (We could however fix this in a +> >> maintenance release.) +> >> +> >> However, r=3D should also allow all other protocols, exactly like any = +of +> >> the r[]=3D params. I don't think we should do a distinction here. Also +> >> because of backwards compatibility to the status quo. +> >> +> >> +> >> On 07/01/2014 03:03 PM, Alex Kotenko wrote: +> >>> In my mind it's not like the client's phone is going all directions a= +t +> >>> the same time. There should be a priority method and fallback +> method(s). +> >>> =E2=80=8BAnd I =E2=80=8Bsee p2p radio as priority, and web as fallbac= +k, and BIP21 in +> the +> >>> end as always-working-default. +> >>> +> >>> =E2=80=8BSo I'm keeping support for it all while want to be able to p= +rovide +> best +> >>> user experience. +> >>> Mike, a while ago in =E2=80=8Bthis thread you've described contactles= +s cards +> >>> user experience. I'm also using contactless cards often, and what I'm +> >>> aiming at is creating same level of user experience for Bitcoin users= +. +> >>> +> >>> Encryption over bluetooth is a matter to worry about, and we will +> >>> introduce that, but we need to sort out more low level problems first +> >>> before coming into that stage. +> >>> +> >>> +> >>> So, the backwards compatibility is a good issue Michael pointed out. +> >>> While processing of multiple "r" parameters is indeed uncertain (sinc= +e +> >>> there is no RFC for that various implementations may behave +> >>> differently), the array solution is somewhat better. The array +> parameter +> >>> name is "r%5B1%5D=3D", i.e. it's not "r=3D", and we can add plain "r= +=3D" +> >>> alongside. And if particular implementation understands the array +> >>> construct - it will use it, otherwise it will ignore the "r%5B1%5D=3D= +" +> and +> >>> use only usual "r=3D". +> >>> +> >>> This doens't work though for cases where particular implementation +> >>> understands array construct but doesn't work well with repeating +> >>> parameters, since it will see two repeating "r" - an array and a +> string. +> >>> I don't have a solution for that atm. +> >>> +> >>> +> >>> If add completely new parameter to solve this we will need to make it +> an +> >>> array straight away to address upcoming issues with accommodating oth= +er +> >>> protocols. +> >>> And then I would also modify existing BIP72 to strictly define "r=3D"= + as +> >>> "http(s)" =E2=80=8Bonly =E2=80=8Bparameter, while all other protocols= + (bluetooth, WiFi +> >>> Direct, ultrasound, chirp etc) should go to the new array parameter. +> >>> +> >>> +> >>> =E2=80=8B +> >>> +> >>> +> >>> +> -------------------------------------------------------------------------= +----- +> >>> Open source business process management suite built on Java and Eclip= +se +> >>> Turn processes into business applications with Bonita BPM Community +> Edition +> >>> Quickly connect people, data, and systems into organized workflows +> >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards +> >>> http://p.sf.net/sfu/Bonitasoft +> >>> +> >>> +> >>> +> >>> _______________________________________________ +> >>> Bitcoin-development mailing list +> >>> Bitcoin-development@lists.sourceforge.net +> >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development +> >>> +> >> +> >> +> >> +> >> +> -------------------------------------------------------------------------= +----- +> >> Open source business process management suite built on Java and Eclips= +e +> >> Turn processes into business applications with Bonita BPM Community +> Edition +> >> Quickly connect people, data, and systems into organized workflows +> >> Winner of BOSSIE, CODIE, OW2 and Gartner awards +> >> http://p.sf.net/sfu/Bonitasoft +> >> _______________________________________________ +> >> Bitcoin-development mailing list +> >> Bitcoin-development@lists.sourceforge.net +> >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development +> > +> > +> > +> -------------------------------------------------------------------------= +----- +> > Open source business process management suite built on Java and Eclipse +> > Turn processes into business applications with Bonita BPM Community +> Edition +> > Quickly connect people, data, and systems into organized workflows +> > Winner of BOSSIE, CODIE, OW2 and Gartner awards +> > http://p.sf.net/sfu/Bonitasoft +> > _______________________________________________ +> > Bitcoin-development mailing list +> > Bitcoin-development@lists.sourceforge.net +> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development +> > +> +> +> +> +> -------------------------------------------------------------------------= +----- +> Open source business process management suite built on Java and Eclipse +> Turn processes into business applications with Bonita BPM Community Editi= +on +> Quickly connect people, data, and systems into organized workflows +> Winner of BOSSIE, CODIE, OW2 and Gartner awards +> http://p.sf.net/sfu/Bonitasoft +> _______________________________________________ +> Bitcoin-development mailing list +> Bitcoin-development@lists.sourceforge.net +> https://lists.sourceforge.net/lists/listinfo/bitcoin-development +> + +--20cf3071c6c68c637a04fd24f6de +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<p dir=3D"ltr">Hmm, r1, r2 etc is actually interesting. It takes less chars= + then array (yes, array brackets have to be escaped) and provides unlimited= + number of options, uniformed approach and priority definition. I'd say= + that is the way to go. Any objections?</p> + +<div class=3D"gmail_quote">On 1 Jul 2014 16:39, "Andreas Schildbach&qu= +ot; <<a href=3D"mailto:andreas@schildbach.de">andreas@schildbach.de</a>&= +gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style= +=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Ok, one more idea:<br> +r=3D is used for the first URL, and we *think* of it as r0=3D<br> +additional URLs are appended as<br> +r1=3D<br> +r2=3D<br> +and so on. This would also define an ordering in case we need it.<br> +<br> +<br> +On 07/01/2014 05:07 PM, Michael Wozniak wrote:<br> +> Multiple parameters is currently undefined as far as I can tell. =C2= +=A0Should the client take the first, last, or ignore it completely if there= + are multiple of any parameter? =C2=A0I think that=E2=80=99s the point of t= +he parameter pollution discussion, which will define it one way or the othe= +r.<br> + +><br> +> I=E2=80=99m only familiar with the Electrum implementation, which is c= +urrently checking for any duplicate parameters and treating the entire URI = +as invalid if duplicate parameters exist (following the parameter pollution= + suggestions).<br> + +><br> +> -<br> +> Michael Wozniak<br> +><br> +> On Jul 1, 2014, at 10:59 AM, Andreas Schildbach <<a href=3D"mailto:= +andreas@schildbach.de">andreas@schildbach.de</a>> wrote:<br> +><br> +>> Does r[]=3D really need to be encoded as r%5B1%5D=3D ? In this cas= +e, I'd<br> +>> advocate for a simple array parameter name, like rs=3D ("plur= +al" of r).<br> +>> Length really does matter for QR codes.<br> +>><br> +>> I'm fine with either multiple r=3D params or exactly one r=3D = +plus zero to<br> +>> many r[]=3D params. Although I think it is a violation of the (cur= +rent)<br> +>> spec to choke on more than one r=3D parameters, I admit that bitco= +inj is<br> +>> currently implemented that way. (We could however fix this in a<br= +> +>> maintenance release.)<br> +>><br> +>> However, r=3D should also allow all other protocols, exactly like = +any of<br> +>> the r[]=3D params. I don't think we should do a distinction he= +re. Also<br> +>> because of backwards compatibility to the status quo.<br> +>><br> +>><br> +>> On 07/01/2014 03:03 PM, Alex Kotenko wrote:<br> +>>> In my mind it's not like the client's phone is going a= +ll directions at<br> +>>> the same time. There should be a priority method and fallback = +method(s).<br> +>>> =E2=80=8BAnd I =E2=80=8Bsee p2p radio as priority, and web as = +fallback, and BIP21 in the<br> +>>> end as always-working-default.<br> +>>><br> +>>> =E2=80=8BSo I'm keeping support for it all while want to b= +e able to provide best<br> +>>> user experience.<br> +>>> Mike, a while ago in =E2=80=8Bthis thread you've described= + contactless cards<br> +>>> user experience. I'm also using contactless cards often, a= +nd what I'm<br> +>>> aiming at is creating same level of user experience for Bitcoi= +n users.<br> +>>><br> +>>> Encryption over bluetooth is a matter to worry about, and we w= +ill<br> +>>> introduce that, but we need to sort out more low level problem= +s first<br> +>>> before coming into that stage.<br> +>>><br> +>>><br> +>>> So, the backwards compatibility is a good issue Michael pointe= +d out.<br> +>>> While processing of multiple "r" parameters is indee= +d uncertain (since<br> +>>> there is no RFC for that various implementations may behave<br= +> +>>> differently), the array solution is somewhat better. The array= + parameter<br> +>>> name is "r%5B1%5D=3D", i.e. it's not "r=3D&= +quot;, and we can add plain "r=3D"<br> +>>> alongside. And if particular implementation understands the ar= +ray<br> +>>> construct - it will use it, otherwise it will ignore the "= +;r%5B1%5D=3D" and<br> +>>> use only usual "r=3D".<br> +>>><br> +>>> This doens't work though for cases where particular implem= +entation<br> +>>> understands array construct but doesn't work well with rep= +eating<br> +>>> parameters, since it will see two repeating "r" - an= + array and a string.<br> +>>> I don't have a solution for that atm.<br> +>>><br> +>>><br> +>>> If add completely new parameter to solve this we will need to = +make it an<br> +>>> array straight away to address upcoming issues with accommodat= +ing other<br> +>>> protocols.<br> +>>> And then I would also modify existing BIP72 to strictly define= + "r=3D" as<br> +>>> "http(s)" =E2=80=8Bonly =E2=80=8Bparameter, while al= +l other protocols (bluetooth, WiFi<br> +>>> Direct, ultrasound, chirp etc) should go to the new array para= +meter.<br> +>>><br> +>>><br> +>>> =E2=80=8B<br> +>>><br> +>>><br> +>>> --------------------------------------------------------------= +----------------<br> +>>> Open source business process management suite built on Java an= +d Eclipse<br> +>>> Turn processes into business applications with Bonita BPM Comm= +unity Edition<br> +>>> Quickly connect people, data, and systems into organized workf= +lows<br> +>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards<br> +>>> <a href=3D"http://p.sf.net/sfu/Bonitasoft" target=3D"_blank">h= +ttp://p.sf.net/sfu/Bonitasoft</a><br> +>>><br> +>>><br> +>>><br> +>>> _______________________________________________<br> +>>> Bitcoin-development mailing list<br> +>>> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">B= +itcoin-development@lists.sourceforge.net</a><br> +>>> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoi= +n-development" target=3D"_blank">https://lists.sourceforge.net/lists/listin= +fo/bitcoin-development</a><br> +>>><br> +>><br> +>><br> +>><br> +>> ------------------------------------------------------------------= +------------<br> +>> Open source business process management suite built on Java and Ec= +lipse<br> +>> Turn processes into business applications with Bonita BPM Communit= +y Edition<br> +>> Quickly connect people, data, and systems into organized workflows= +<br> +>> Winner of BOSSIE, CODIE, OW2 and Gartner awards<br> +>> <a href=3D"http://p.sf.net/sfu/Bonitasoft" target=3D"_blank">http:= +//p.sf.net/sfu/Bonitasoft</a><br> +>> _______________________________________________<br> +>> Bitcoin-development mailing list<br> +>> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitco= +in-development@lists.sourceforge.net</a><br> +>> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-de= +velopment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/b= +itcoin-development</a><br> +><br> +><br> +> ----------------------------------------------------------------------= +--------<br> +> Open source business process management suite built on Java and Eclips= +e<br> +> Turn processes into business applications with Bonita BPM Community Ed= +ition<br> +> Quickly connect people, data, and systems into organized workflows<br> +> Winner of BOSSIE, CODIE, OW2 and Gartner awards<br> +> <a href=3D"http://p.sf.net/sfu/Bonitasoft" target=3D"_blank">http://p.= +sf.net/sfu/Bonitasoft</a><br> +> _______________________________________________<br> +> Bitcoin-development mailing list<br> +> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d= +evelopment@lists.sourceforge.net</a><br> +> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo= +pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco= +in-development</a><br> +><br> +<br> +<br> +<br> +---------------------------------------------------------------------------= +---<br> +Open source business process management suite built on Java and Eclipse<br> +Turn processes into business applications with Bonita BPM Community Edition= +<br> +Quickly connect people, data, and systems into organized workflows<br> +Winner of BOSSIE, CODIE, OW2 and Gartner awards<br> +<a href=3D"http://p.sf.net/sfu/Bonitasoft" target=3D"_blank">http://p.sf.ne= +t/sfu/Bonitasoft</a><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> +</blockquote></div> + +--20cf3071c6c68c637a04fd24f6de-- + + |