blob: 83db6e7e993858ee36e944eb1ec3bbd460d00111 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1Td9qt-0006Pp-73
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 01:20:43 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=gavinandresen@gmail.com;
helo=mail-vc0-f175.google.com;
Received: from mail-vc0-f175.google.com ([209.85.220.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Td9qs-0006rp-Gg
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 01:20:43 +0000
Received: by mail-vc0-f175.google.com with SMTP id m8so8530284vcd.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 26 Nov 2012 17:20:37 -0800 (PST)
Received: by 10.52.100.65 with SMTP id ew1mr19024780vdb.125.1353979237017;
Mon, 26 Nov 2012 17:20:37 -0800 (PST)
Received: from [10.224.16.57] (75.sub-174-252-56.myvzw.com. [174.252.56.75])
by mx.google.com with ESMTPS id ey7sm8425355ved.0.2012.11.26.17.20.29
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 26 Nov 2012 17:20:36 -0800 (PST)
References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com>
<201211262319.37533.luke@dashjr.org>
<CAAS2fgS3f1RKzPnni4LXgXfSUrxSrB3+vhdmbsVz2Rs5pScL=w@mail.gmail.com>
<201211262344.03385.luke@dashjr.org>
<CAAS2fgTacBqX7_YpGzUxtqt9okeCeeufsG8d0CYnwVXPF_bu7w@mail.gmail.com>
<CANEZrP0fhM=N=LsYa=za8MobiJYG9Fbpv+WniL8td6pRpr6jgQ@mail.gmail.com>
<CAJ1JLts=WW3r-eV50513uB=a3XJvPcgjPTwG3OhQ3XnPtM3BNQ@mail.gmail.com>
From: Gavin <gavinandresen@gmail.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <CAJ1JLts=WW3r-eV50513uB=a3XJvPcgjPTwG3OhQ3XnPtM3BNQ@mail.gmail.com>
Message-Id: <C9C45A0D-2E83-449F-8A4D-6A59AF375DC1@gmail.com>
Date: Mon, 26 Nov 2012 20:09:25 -0500
To: Rick Wesson <rick@support-intelligence.com>
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (9B206)
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.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
X-Headers-End: 1Td9qs-0006rp-Gg
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 01:20:43 -0000
Supporting DNSSEC/DANE in the future when they are widely deployed is a grea=
t idea.
Note that the x509chain field is 'repeated', and any repeated field may have=
zero entries. So I would suggest supporting other PKI systems in the future=
by adding optional new fields (for maximum compatibility or security mercha=
nts might want to include both a x509chain AND=20
--
Gavin Andresen
|
