From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1X2GEp-0004Dv-64 for bitcoin-development@lists.sourceforge.net; Wed, 02 Jul 2014 08:49:59 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.170 as permitted sender) client-ip=209.85.220.170; envelope-from=alexy.kot.all@gmail.com; helo=mail-vc0-f170.google.com; Received: from mail-vc0-f170.google.com ([209.85.220.170]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X2GEn-0005HU-B9 for bitcoin-development@lists.sourceforge.net; Wed, 02 Jul 2014 08:49:59 +0000 Received: by mail-vc0-f170.google.com with SMTP id hy10so10064394vcb.15 for ; Wed, 02 Jul 2014 01:49:51 -0700 (PDT) X-Received: by 10.58.208.170 with SMTP id mf10mr30673568vec.22.1404290991725; Wed, 02 Jul 2014 01:49:51 -0700 (PDT) MIME-Version: 1.0 Sender: alexy.kot.all@gmail.com Received: by 10.58.237.129 with HTTP; Wed, 2 Jul 2014 01:49:10 -0700 (PDT) In-Reply-To: References: <20140320215208.GC88006@giles.gnomon.org.uk> <20140326224826.GE62995@giles.gnomon.org.uk> <1016E2A3-C678-46FA-B80E-F9D86FDEA213@osfda.org> From: Alex Kotenko Date: Wed, 2 Jul 2014 09:49:10 +0100 X-Google-Sender-Auth: zSNNsZd15qS1dGmCB1R7SJzAth4 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=047d7bdc17f6b9228704fd31f9db 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: 1X2GEn-0005HU-B9 Cc: Bitcoin Dev , Andreas Schildbach 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 08:49:59 -0000 --047d7bdc17f6b9228704fd31f9db Content-Type: text/plain; charset=UTF-8 Ok, agreed. I will submit a pull request to BIP72 then. Not sure about escaping though. It is indeed not critical for bitcoin URIs, but still it is a part of RFC, don't think we should go against it. Andreas, we will implement this on our side, with bluetooth on r= and web address on r1=. 2014-07-01 18:59 GMT+01:00 Mike Hearn : > Nope, r1/r2 sounds good to me. BTW we should update the spec to reflect > that escaping is largely unnecessary in many cases. > > > --047d7bdc17f6b9228704fd31f9db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ok, agreed. I will submit a pull request to BI= P72 then.
Not sure about escaping though. It is indeed not critical for bitcoin URIs,= but still it is a part of RFC, don't think we should go against it.

Andreas, we will implement this on our side, with blu= etooth on r=3D and web address on r1=3D.

2014-07-01 18:59 = GMT+01:00 Mike Hearn <mike@plan99.net>:
Nope, r1/r2 sounds good to me. = BTW we should update the spec to reflect that escaping is largely unnecessa= ry in many cases.



--047d7bdc17f6b9228704fd31f9db--