summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWalter Stanish <walter@stani.sh>2012-11-27 11:31:36 +0800
committerbitcoindev <bitcoindev@gnusha.org>2012-11-27 03:31:44 +0000
commit3fe5354d24f39bd0d334e7d8371d2b34686bdf13 (patch)
treee210b01147a0dacaae3c00797e63513346e8850a
parentbd10887c7c68240e256bdca99c24ab2998cf62ed (diff)
downloadpi-bitcoindev-3fe5354d24f39bd0d334e7d8371d2b34686bdf13.tar.gz
pi-bitcoindev-3fe5354d24f39bd0d334e7d8371d2b34686bdf13.zip
Re: [Bitcoin-development] Payment Protocol Proposal: Invoices/Payments/Receipts
-rw-r--r--34/b8df0b783be6d3eedafbc8be1a3d6922c3511c83
1 files changed, 83 insertions, 0 deletions
diff --git a/34/b8df0b783be6d3eedafbc8be1a3d6922c3511c b/34/b8df0b783be6d3eedafbc8be1a3d6922c3511c
new file mode 100644
index 000000000..9d508752b
--- /dev/null
+++ b/34/b8df0b783be6d3eedafbc8be1a3d6922c3511c
@@ -0,0 +1,83 @@
+Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
+ helo=mx.sourceforge.net)
+ by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <walter.stanish@gmail.com>) id 1TdBtg-0002vi-1t
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 27 Nov 2012 03:31:44 +0000
+Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
+ designates 209.85.214.47 as permitted sender)
+ client-ip=209.85.214.47; envelope-from=walter.stanish@gmail.com;
+ helo=mail-bk0-f47.google.com;
+Received: from mail-bk0-f47.google.com ([209.85.214.47])
+ by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1TdBtf-0001iv-9p
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 27 Nov 2012 03:31:44 +0000
+Received: by mail-bk0-f47.google.com with SMTP id j4so3471817bkw.34
+ for <bitcoin-development@lists.sourceforge.net>;
+ Mon, 26 Nov 2012 19:31:37 -0800 (PST)
+MIME-Version: 1.0
+Received: by 10.204.11.70 with SMTP id s6mr4236155bks.63.1353987096938; Mon,
+ 26 Nov 2012 19:31:36 -0800 (PST)
+Sender: walter.stanish@gmail.com
+Received: by 10.204.49.133 with HTTP; Mon, 26 Nov 2012 19:31:36 -0800 (PST)
+In-Reply-To: <CAJ1JLtuJ8HQri7++2bodc2ACRrE7Y48oy0HkPR8d400MooHaqA@mail.gmail.com>
+References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com>
+ <CACwuEiP7CGeZZGW=mXwrFAAqbbwbrPXTPb8vOEDuO9_96hqBGg@mail.gmail.com>
+ <CAAS2fgSY8hHiCJYEDv=y48hYRJJtB-R5EBX8JLz6NivBm+Z9PQ@mail.gmail.com>
+ <CACwuEiMjf8WYOpfmzHUHMa-sy2VsJHaUNj1cj722Y=P_sosbvw@mail.gmail.com>
+ <CAJ1JLtuJ8HQri7++2bodc2ACRrE7Y48oy0HkPR8d400MooHaqA@mail.gmail.com>
+Date: Tue, 27 Nov 2012 11:31:36 +0800
+X-Google-Sender-Auth: JI3a9eQtj7ZFx3Qf3hqaY0a_aI4
+Message-ID: <CACwuEiMgcv09U2P9dD58x-oMXMSg==fPYo0yRLsqzyuax96Eqw@mail.gmail.com>
+From: Walter Stanish <walter@stani.sh>
+To: Rick Wesson <rick@support-intelligence.com>
+Content-Type: text/plain; charset=ISO-8859-1
+X-Spam-Score: -1.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
+ (walter.stanish[at]gmail.com)
+ -0.0 SPF_PASS SPF: sender matches SPF record
+ 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: 1TdBtf-0001iv-9p
+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: Tue, 27 Nov 2012 03:31:44 -0000
+
+>> We are currently working with IETF staff, with open offers of support
+>> from multiple well funded commercial bodies, to transition these
+>> proposals through to IANA management.
+>
+> I hate to inform you that you have been mislead. The IETF and the IANA
+> do not operate as you outlined above. Having spent too many years
+> within ICANN/IETF/IANA I can assure you are mistaken.
+> Your drafts are expired and it appears that there is no support for a
+> "finance" working group in the IETF.
+
+We are not establishing an IETF working group, which is an option that
+was explored prior to the Paris meeting and has been sidelined at
+present for depth-of-bureaucracy by the backing commercial entities.
+Rather, we are establishing a top-level IANA registry group. This is
+not anticipated by the IETF old-guard working with us to be either (a)
+controversial or (b) possible to block.
+
+- Walter
+
+