From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WQlz8-00010G-Eq for bitcoin-development@lists.sourceforge.net; Thu, 20 Mar 2014 23:02:50 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.174 as permitted sender) client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f174.google.com; Received: from mail-ob0-f174.google.com ([209.85.214.174]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WQlz7-0002YP-Mu for bitcoin-development@lists.sourceforge.net; Thu, 20 Mar 2014 23:02:50 +0000 Received: by mail-ob0-f174.google.com with SMTP id wo20so1686075obc.5 for ; Thu, 20 Mar 2014 16:02:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.173.99 with SMTP id bj3mr8779539oec.55.1395356564385; Thu, 20 Mar 2014 16:02:44 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.231 with HTTP; Thu, 20 Mar 2014 16:02:44 -0700 (PDT) In-Reply-To: <20140320215208.GC88006@giles.gnomon.org.uk> References: <20140320215208.GC88006@giles.gnomon.org.uk> Date: Fri, 21 Mar 2014 00:02:44 +0100 X-Google-Sender-Auth: _urUh5vXTjlMbDExYWws8Uh8_F8 Message-ID: From: Mike Hearn To: Roy Badami Content-Type: multipart/alternative; boundary=047d7ba9818c5af4f804f511c476 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: 1WQlz7-0002YP-Mu 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: Thu, 20 Mar 2014 23:02:50 -0000 --047d7ba9818c5af4f804f511c476 Content-Type: text/plain; charset=UTF-8 > > It's not unusual, in a face-to-face transaction at a bricks-and-mortar > establishment, that you know neither the legal name of the entity > running the establishment I'd hope that people can get certs for their actual business name, but sometimes it does differ yes. However remember that signing in BIP70 is about more than just security, though that's the driving factor. It's also needed for things like dispute mediation, receipts, etc. --047d7ba9818c5af4f804f511c476 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It's not unusual, in a face-to-face transact= ion at a bricks-and-mortar
establishment, that you know neither the legal name of the entity
running the establishment

I'd hope that= people can get certs for their actual business name, but sometimes it does= differ yes.

However remember that signing in BIP7= 0 is about more than just security, though that's the driving factor. I= t's also needed for things like dispute mediation, receipts, etc.=C2=A0=
--047d7ba9818c5af4f804f511c476--