Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WK4vB-00044N-PU for bitcoin-development@lists.sourceforge.net; Sun, 02 Mar 2014 11:51:05 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.47 as permitted sender) client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f47.google.com; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WK4vB-00063b-4D for bitcoin-development@lists.sourceforge.net; Sun, 02 Mar 2014 11:51:05 +0000 Received: by mail-oa0-f47.google.com with SMTP id h16so5860654oag.6 for ; Sun, 02 Mar 2014 03:50:59 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.34.196 with SMTP id b4mr22587755obj.13.1393761059799; Sun, 02 Mar 2014 03:50:59 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.71.231 with HTTP; Sun, 2 Mar 2014 03:50:59 -0800 (PST) In-Reply-To: References: Date: Sun, 2 Mar 2014 12:50:59 +0100 X-Google-Sender-Auth: G03f9SNk1LKOluxTqEnqTaJx1zc Message-ID: From: Mike Hearn To: Andreas Schildbach Content-Type: multipart/alternative; boundary=001a11c2cba4df0a9504f39e4899 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: 1WK4vB-00063b-4D Cc: Bitcoin Dev 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: Sun, 02 Mar 2014 11:51:05 -0000 --001a11c2cba4df0a9504f39e4899 Content-Type: text/plain; charset=UTF-8 Thanks Andreas. For BIP standardisation, I think the VIEW intent seems like an obvious one. Bluetooth support probably should come later if/when we put encryption/auth on the RFCOMM link (probably SSL). --001a11c2cba4df0a9504f39e4899 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Andreas.

For BIP standardisati= on, I think the VIEW intent seems like an obvious one. Bluetooth support pr= obably should come later if/when we put encryption/auth on the RFCOMM link = (probably SSL).
--001a11c2cba4df0a9504f39e4899--