diff options
author | Alex Kotenko <alexykot@gmail.com> | 2014-07-01 14:03:52 +0100 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2014-07-01 13:04:42 +0000 |
commit | c7c930e2137e990a541c484cd140e299de73b6f8 (patch) | |
tree | fb38753c0fdd545a0856d0584717182ccac7d78b | |
parent | 7d7b56cbacba0530efbd670c84bed26e6a242222 (diff) | |
download | pi-bitcoindev-c7c930e2137e990a541c484cd140e299de73b6f8.tar.gz pi-bitcoindev-c7c930e2137e990a541c484cd140e299de73b6f8.zip |
Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments
-rw-r--r-- | d9/2a6a799fa0fc05220c285cc4986a05a1240e97 | 211 |
1 files changed, 211 insertions, 0 deletions
diff --git a/d9/2a6a799fa0fc05220c285cc4986a05a1240e97 b/d9/2a6a799fa0fc05220c285cc4986a05a1240e97 new file mode 100644 index 000000000..a03f561c3 --- /dev/null +++ b/d9/2a6a799fa0fc05220c285cc4986a05a1240e97 @@ -0,0 +1,211 @@ +Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <alexy.kot.all@gmail.com>) id 1X1xjm-0007yw-4p + for bitcoin-development@lists.sourceforge.net; + Tue, 01 Jul 2014 13:04:42 +0000 +Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.220.175 as permitted sender) + client-ip=209.85.220.175; envelope-from=alexy.kot.all@gmail.com; + helo=mail-vc0-f175.google.com; +Received: from mail-vc0-f175.google.com ([209.85.220.175]) + by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1X1xjk-0003C9-7f + for bitcoin-development@lists.sourceforge.net; + Tue, 01 Jul 2014 13:04:42 +0000 +Received: by mail-vc0-f175.google.com with SMTP id hy4so8864339vcb.6 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 01 Jul 2014 06:04:32 -0700 (PDT) +X-Received: by 10.52.24.68 with SMTP id s4mr1047033vdf.37.1404219872526; Tue, + 01 Jul 2014 06:04:32 -0700 (PDT) +MIME-Version: 1.0 +Sender: alexy.kot.all@gmail.com +Received: by 10.58.237.129 with HTTP; Tue, 1 Jul 2014 06:03:52 -0700 (PDT) +In-Reply-To: <D4B82FD9-8078-48B2-9F91-8A3AB23AEAA7@osfda.org> +References: <leuunm$tjk$1@ger.gmane.org> + <CANEZrP3nQfvDArKTRgje0Cus4G2JD_zpxSjA3fXfxM2TNAP80Q@mail.gmail.com> + <CALDj+BafD+6KTNcYDBEu5gNPzYozSkiC-JCxrY-PzXL2DYBRsw@mail.gmail.com> + <CAJHLa0N4J_Z907+D0ENSNKfNAW2N=7Jf4JzSCO=SU558GtGTzA@mail.gmail.com> + <lge7nk$3mf$2@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> + <lou05t$2ra$1@ger.gmane.org> + <D4B82FD9-8078-48B2-9F91-8A3AB23AEAA7@osfda.org> +From: Alex Kotenko <alexykot@gmail.com> +Date: Tue, 1 Jul 2014 14:03:52 +0100 +X-Google-Sender-Auth: uJUtZWDC-7Yu4dLmOMnUYPvj6Z8 +Message-ID: <CALDj+BZ8_YB0DHiaGZPq4MB-dvkRqJhBFazcfnrrPX4EvRxbeQ@mail.gmail.com> +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Content-Type: multipart/alternative; boundary=20cf3071cfdeb0475d04fd216a0d +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.2 MISSING_HEADERS Missing To: header + 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: 1X1xjk-0003C9-7f +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 13:04:42 -0000 + +--20cf3071cfdeb0475d04fd216a0d +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +In my mind it's not like the client's phone is going all directions at 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 fallback, and BIP21 in the e= +nd as +always-working-default. + +=E2=80=8BSo I'm keeping support for it all while want to be able to provide= + best +user experience. +Mike, a while ago in =E2=80=8Bthis thread you've described contactless card= +s 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 (since +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 other +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 (blue= +tooth, WiFi +Direct, ultrasound, chirp etc) should go to the new array parameter. + + +=E2=80=8B + +--20cf3071cfdeb0475d04fd216a0d +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:'cou= +rier new',monospace;color:rgb(0,51,0)">In my mind it's not like the= + client's phone is going all directions at the same time. There should = +be a priority method and fallback method(s). =E2=80=8BAnd I =E2=80=8Bsee p2= +p radio as priority, and web as fallback, and BIP21 in the end as always-wo= +rking-default.<br> + + +</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div = +class=3D"gmail_default" style=3D"font-family:'courier new',monospac= +e;color:rgb(0,51,0)">=E2=80=8BSo I'm keeping support for it all while w= +ant to be able to provide best user experience.=C2=A0</div> + + +<div class=3D"gmail_default" style=3D"font-family:'courier new',mon= +ospace;color:rgb(0,51,0)">Mike, a while ago in =E2=80=8Bthis thread you'= +;ve described contactless cards user experience. I'm also using contact= +less cards often, and what I'm aiming at is creating same level of user= + experience for Bitcoin users.=C2=A0</div> + + +<div class=3D"gmail_default" style=3D"font-family:'courier new',mon= +ospace;color:rgb(0,51,0)"><br></div><div class=3D"gmail_default" style=3D"f= +ont-family:'courier new',monospace;color:rgb(0,51,0)">Encryption ov= +er 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 sta= +ge.=C2=A0</div> + + +<div class=3D"gmail_default" style=3D"font-family:'courier new',mon= +ospace;color:rgb(0,51,0)"><br></div><div class=3D"gmail_default" style=3D"f= +ont-family:'courier new',monospace;color:rgb(0,51,0)"><br></div><di= +v class=3D"gmail_default" style=3D"font-family:'courier new',monosp= +ace;color:rgb(0,51,0)"> + + +So, the backwards compatibility is a good issue Michael pointed out.=C2=A0<= +br></div><div class=3D"gmail_default" style=3D"font-family:'courier new= +',monospace;color:rgb(0,51,0)">While processing of multiple "r&quo= +t; parameters is indeed uncertain (since there is no RFC for that various i= +mplementations may behave differently), the array solution is somewhat bett= +er. The array parameter name is "<span style=3D"font-size:13px">r%5B1%= +5D=3D</span>", i.e. it's not "r=3D", and we can add plai= +n "r=3D" alongside. And if particular implementation understands = +the array construct - it will use it, otherwise it will ignore the "<s= +pan style=3D"font-size:13px">r%5B1%5D=3D</span>" and use only usual &q= +uot;r=3D".=C2=A0</div> + + +<br></div><div class=3D"gmail_extra"><div class=3D"gmail_default" style=3D"= +font-family:'courier new',monospace;color:rgb(0,51,0)">This doens&#= +39;t work though for cases where particular implementation understands arra= +y construct but doesn't work well with repeating parameters, since it w= +ill see two repeating "r" - an array and a string. I don't ha= +ve a solution for that atm.=C2=A0</div> + + +<br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><= +div class=3D"gmail_default" style=3D"font-family:'courier new',mono= +space;color:rgb(0,51,0)">If add completely new parameter to solve this we w= +ill need to make it an array straight away to address upcoming issues with = +accommodating other protocols.=C2=A0</div> + + +<div class=3D"gmail_default" style=3D"font-family:'courier new',mon= +ospace;color:rgb(0,51,0)">And then I would also modify existing BIP72 to st= +rictly 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.</div> + + +<br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><= +span style=3D"color:rgb(0,51,0);font-family:'courier new',monospace= +">=E2=80=8B</span><br></div></div> + +--20cf3071cfdeb0475d04fd216a0d-- + + |