diff options
| author | Gavin Andresen <gavinandresen@gmail.com> | 2012-12-05 14:34:49 -0500 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2012-12-05 19:34:59 +0000 |
| commit | 3ad8b25d06cee8c41e0b6858f526869c53731884 (patch) | |
| tree | d130e9c5e13f8bafe60a66454fba8d533950fc0e | |
| parent | 6a2a3b221e2684344b94e4af4c0689cf0bab9c66 (diff) | |
| download | pi-bitcoindev-3ad8b25d06cee8c41e0b6858f526869c53731884.tar.gz pi-bitcoindev-3ad8b25d06cee8c41e0b6858f526869c53731884.zip | |
Re: [Bitcoin-development] Payment Protocol Proposal: Invoices/Payments/Receipts
| -rw-r--r-- | 15/e9b35b548b0f9077780a2ab184d9fd8f9bcd16 | 104 |
1 files changed, 104 insertions, 0 deletions
diff --git a/15/e9b35b548b0f9077780a2ab184d9fd8f9bcd16 b/15/e9b35b548b0f9077780a2ab184d9fd8f9bcd16 new file mode 100644 index 000000000..16166e8bd --- /dev/null +++ b/15/e9b35b548b0f9077780a2ab184d9fd8f9bcd16 @@ -0,0 +1,104 @@ +Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] + helo=mx.sourceforge.net) + by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <gavinandresen@gmail.com>) id 1TgKkF-0006zV-5X + for bitcoin-development@lists.sourceforge.net; + Wed, 05 Dec 2012 19:34:59 +0000 +Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.212.171 as permitted sender) + client-ip=209.85.212.171; envelope-from=gavinandresen@gmail.com; + helo=mail-wi0-f171.google.com; +Received: from mail-wi0-f171.google.com ([209.85.212.171]) + by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1TgKkB-0003Tl-J1 + for bitcoin-development@lists.sourceforge.net; + Wed, 05 Dec 2012 19:34:58 +0000 +Received: by mail-wi0-f171.google.com with SMTP id hn14so1873107wib.10 + for <bitcoin-development@lists.sourceforge.net>; + Wed, 05 Dec 2012 11:34:49 -0800 (PST) +MIME-Version: 1.0 +Received: by 10.180.8.133 with SMTP id r5mr5087940wia.7.1354736089487; Wed, 05 + Dec 2012 11:34:49 -0800 (PST) +Received: by 10.194.27.136 with HTTP; Wed, 5 Dec 2012 11:34:49 -0800 (PST) +In-Reply-To: <CANEZrP2riPBViBqAOWfY9uSQwoEm=gN108JU988XvouMbai1Ug@mail.gmail.com> +References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com> + <20121128233619.GA6368@giles.gnomon.org.uk> + <CABsx9T09FYf2RTaMpmujt3qwTFc2JgnREH_7Hyk2mnCgb3CvAw@mail.gmail.com> + <20121129170713.GD6368@giles.gnomon.org.uk> + <CANEZrP233CytLs3PWBQ1TyuBTMv4sLGJkEMeGWYq5xRi+iLKew@mail.gmail.com> + <20121129185330.GE6368@giles.gnomon.org.uk> + <CABsx9T35qD_xJEVw002eAhJ1kr6x5aMU7RpD+U84XEOZXmXcYw@mail.gmail.com> + <CANEZrP2riPBViBqAOWfY9uSQwoEm=gN108JU988XvouMbai1Ug@mail.gmail.com> +Date: Wed, 5 Dec 2012 14:34:49 -0500 +Message-ID: <CABsx9T023aw11cq6iiZhT3cgfNYJXr=qG40Fzc7rYZOimJ=62w@mail.gmail.com> +From: Gavin Andresen <gavinandresen@gmail.com> +To: Mike Hearn <mike@plan99.net> +Content-Type: text/plain; charset=ISO-8859-1 +X-Spam-Score: -1.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 + (gavinandresen[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + -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: 1TgKkB-0003Tl-J1 +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Payment Protocol Proposal: + Invoices/Payments/Receipts +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: Wed, 05 Dec 2012 19:34:59 -0000 + +I've had some push-back on the names of the proposed messages-- e.g. +"Invoice" in the accounting world means "I've already given you a +product or service, here is what you owe, payment terms, what forms of +payment are accepted, etc." + +I think there might also be confusion about why we're defining our own +Invoice when there are at least three or four other existing standard +for electronic invoices. + +So unless there is strong objection I'm going to change the names of +the messages: + +Invoice --> PaymentRequest +Payment : ok as-is +Receipt --> PaymentACK (payment acknowledgement) + +On Tue, Dec 4, 2012 at 12:06 PM, Mike Hearn <mike@plan99.net> wrote: +> Does it make sense to have this spec not include the details of +> bootstrapping? It's not complicated .... + +BIP 0001 says: "If in doubt, split your BIP into several well-focussed ones." + +I think it makes sense to keep the URI extension separate from the +binary message format. + +> We should define a simple mechanism for extending the protocol now... +> +> message Invoice { +> extensions 1000 to max; +> } + +Ok. + +-- +-- +Gavin Andresen + + |