From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WzVww-0001Uy-R3 for bitcoin-development@lists.sourceforge.net; Tue, 24 Jun 2014 19:00:10 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.44 as permitted sender) client-ip=209.85.192.44; envelope-from=will.yager@gmail.com; helo=mail-qg0-f44.google.com; Received: from mail-qg0-f44.google.com ([209.85.192.44]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WzVwv-0002Fs-3W for bitcoin-development@lists.sourceforge.net; Tue, 24 Jun 2014 19:00:10 +0000 Received: by mail-qg0-f44.google.com with SMTP id j107so701838qga.31 for ; Tue, 24 Jun 2014 12:00:03 -0700 (PDT) X-Received: by 10.140.82.113 with SMTP id g104mr4511364qgd.55.1403636403506; Tue, 24 Jun 2014 12:00:03 -0700 (PDT) Received: from [10.255.130.128] ([65.115.226.29]) by mx.google.com with ESMTPSA id u4sm1770872qab.1.2014.06.24.12.00.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Jun 2014 12:00:02 -0700 (PDT) Content-Type: multipart/signed; boundary=Apple-Mail-ADD7CE9F-8B5E-424C-886C-D8E9DCE67E6E; protocol="application/pkcs7-signature"; micalg=sha1 Mime-Version: 1.0 (1.0) From: Gmail X-Mailer: iPhone Mail (11D201) In-Reply-To: Date: Tue, 24 Jun 2014 15:00:02 -0400 Content-Transfer-Encoding: 7bit Message-Id: References: <6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com> To: Jeff Garzik 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 (will.yager[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars -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 -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [209.85.192.44 listed in list.dnswl.org] X-Headers-End: 1WzVwv-0002Fs-3W Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposed BIP 70 extension 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: Tue, 24 Jun 2014 19:00:11 -0000 --Apple-Mail-ADD7CE9F-8B5E-424C-886C-D8E9DCE67E6E Content-Type: multipart/alternative; boundary=Apple-Mail-3D033F15-7563-4A23-AE8D-F44F07B66109 Content-Transfer-Encoding: 7bit --Apple-Mail-3D033F15-7563-4A23-AE8D-F44F07B66109 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Ok, wanting structured data is a decent argument, but why this random arbitr= ary case in particular? There are hundreds of fields like this that people m= ight want to use.=20 If we're going to support one random cosmetic field, we might as well suppor= t them all with a generic structured data format.=20 I'd rather we just didn't have this essentially pointless "feature" at all. L= et's try and keep as much cruft as possible out of the payment protocol. The= textual memo field is already more than sufficient.=20 > On Jun 24, 2014, at 11:48, Jeff Garzik wrote: >=20 > I think there is nothing wrong with having a numeric memo field, which > is effectively what this is. Structured rather than unstructured > data. --Apple-Mail-3D033F15-7563-4A23-AE8D-F44F07B66109 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Ok, wanting structured data is a decen= t argument, but why this random arbitrary case in particular? There are hund= reds of fields like this that people might want to use. 

=
If we're going to support one random cosmetic field, we might as w= ell support them all with a generic structured data format. 
=
I'd rather we just didn't have this essentially pointless "fe= ature" at all. Let's try and keep as much cruft as possible out of th= e payment protocol. The textual memo field is already more than sufficient.&= nbsp;

On Jun 24, 2014, at 11:48, Jeff Garzik <jgarzik@bitpay.com> wrote:

I think there is nothing wrong with having a num= eric memo field, which
is effectively what this is.  St= ructured rather than unstructured
data.<= /body>= --Apple-Mail-3D033F15-7563-4A23-AE8D-F44F07B66109-- --Apple-Mail-ADD7CE9F-8B5E-424C-886C-D8E9DCE67E6E Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIDYjCCA14w ggJGoAMCAQICAQEwCwYJKoZIhvcNAQELMEoxFjAUBgNVBAMMDVdpbGxpYW0gWWFnZXIxCzAJBgNV BAYTAlVTMSMwIQYJKoZIhvcNAQkBFhR3aWxsLnlhZ2VyQGdtYWlsLmNvbTAeFw0xMzExMTMyMzQ0 MDlaFw0xNDExMTMyMzQ0MDlaMEoxFjAUBgNVBAMMDVdpbGxpYW0gWWFnZXIxCzAJBgNVBAYTAlVT MSMwIQYJKoZIhvcNAQkBFhR3aWxsLnlhZ2VyQGdtYWlsLmNvbTCCASIwDQYJKoZIhvcNAQEBBQAD ggEPADCCAQoCggEBAK+DkBdyRq8raiByDg9lye6EyMxmVstEg7/+Tw+BFyvoiPsIlmMzhJ3o8Vhl 8m3rn5JVun5h+BrWW5Efb4i+n7/3zmX0JHeR27Fl2r7KiyZnmeVUWGefiqTr1UmP+jN+wd2qZA5C N4EzHlV4AkGGD/+lYxJqj9VXCRMoguV16G5LaUlNIsrsSiMeQ5htXS2LgTMzl/+KDuQ28yKrFfE/ puBtg33IRM4t0LV/X5ePfHY6UirDLdg/0E9QkkNeFyfegftRNNqsxpR00727C3iZd1R2/0r5ePdo ZZ26i6ccnCTlAd3cw2KONnoYIXauTYu9ZltrdTil//jARFjdvw0MEQECAwEAAaNRME8wDgYDVR0P AQH/BAQDAgL8MBwGA1UdJQEB/wQSMBAGCCsGAQUFBwMEBgRVHSUAMB8GA1UdEQQYMBaBFHdpbGwu eWFnZXJAZ21haWwuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQCEFtUaBk/T6t7Z7LiNsWbWxYaV+e5I Sv1Xgcf+HUveHF2pNPy1dESKm4SwFgzeXRbFrJoR9iAUn5Sp4BW7BK36HAgi4R4nTPPlnDOuwuhg PayrIjP4hxJs56sxeloeakgXhryON0OmQDBCTsStZo1yJQ2ThGXrvlhJVCYu5q781QvLdO+FrNkT v/G+SNsPf+rZviqiUdw645x8fbfvEXMKgYWvyvXlCGGMNNi2/DzqNqY+oBaLeX4GJTdgly//FcNm U0SAH/9VM6UubDnqf1zcPMbTNDrBWvq82Oj1ABRuDCZ3N+A4Wbe/z5Y6C1E47QdIu1Ubecxh0/hF oBQbvkQjMYICmTCCApUCAQEwTzBKMRYwFAYDVQQDDA1XaWxsaWFtIFlhZ2VyMQswCQYDVQQGEwJV UzEjMCEGCSqGSIb3DQEJARYUd2lsbC55YWdlckBnbWFpbC5jb20CAQEwCQYFKw4DAhoFAKCCAR8w GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQwNjI0MTkwMDAzWjAj BgkqhkiG9w0BCQQxFgQUcBJtPZMzdSuPxlJkSPANiw1yR6EwXgYJKwYBBAGCNxAEMVEwTzBKMRYw FAYDVQQDDA1XaWxsaWFtIFlhZ2VyMQswCQYDVQQGEwJVUzEjMCEGCSqGSIb3DQEJARYUd2lsbC55 YWdlckBnbWFpbC5jb20CAQEwYAYLKoZIhvcNAQkQAgsxUaBPMEoxFjAUBgNVBAMMDVdpbGxpYW0g WWFnZXIxCzAJBgNVBAYTAlVTMSMwIQYJKoZIhvcNAQkBFhR3aWxsLnlhZ2VyQGdtYWlsLmNvbQIB ATANBgkqhkiG9w0BAQEFAASCAQAnUtuNmQXTnDKBL+BH7/rRRQsgJDWu4PthGAd6/6lD4TC9FLJR lohAfQfepyw+CeuMAPJn0Og3aybXsQoDVMZrQ6QdbfUjHnUyNyINiUmK5cyIx07KlPX52z/2ZDCs NfKqEwWNMeF43lewXtmW1FaPBDHpd3ncRPBnvYd3DLyAjdSLeH884oITrFHgq5xZHHlVk1nRpwxb sjSX+3n/obFtt4i4ZPznR517OHSk3FGkboWALqHhwHd6/9RLOH1NHQKFhNU+1OUtw3Lt9AxAcrDN RI9beKKECA/maLl9khsByIleEN3uSQP7rE9DPhYXYjtL+LrswN6iya91m7foTtqGAAAAAAAA --Apple-Mail-ADD7CE9F-8B5E-424C-886C-D8E9DCE67E6E--