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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rick.wesson@iidf.org>) id 1Td9Ia-0007eX-1u
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 00:45:16 +0000
X-ACL-Warn:
Received: from mail-gh0-f175.google.com ([209.85.160.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Td9IZ-0006DR-Cc
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 00:45:16 +0000
Received: by mail-gh0-f175.google.com with SMTP id z2so1219011ghb.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 26 Nov 2012 16:45:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:x-gm-message-state;
bh=tWitmi30NNWq5Y58R8qHInkaiED8CxeNC0Bv0TGGPYQ=;
b=mV90EdGggZImW8cFmLaihGkVFelQ4VQwXutmUegrC0Z0FVPmdY94yX3CwRxtRxOL1R
jpb5hJgTwd+BWpy6Qzsjalb73InertsW6TRoxJ/MsG1FiYpfZMNxUUKwodan/24vevj1
VGBCyutdIpXRsn+eBGXDJaxwe2ZwMRqykSWjgelZiRfuNfPwJ8QGSbZhCeEVbznEZGIR
k6paIBlngAdXGTwKHFKmsSjRFc+G77a6Fx+548/7EYSnBfLC1H66MdRkGauPPh76z4A5
KqQKg6Pn2v3nfi+/2QSAHO57pvuzItTbQ/bPQOmRuePj4NxWDAPgmKU3MAdwbJTRklKl
/PWg==
MIME-Version: 1.0
Received: by 10.236.85.78 with SMTP id t54mr13487085yhe.48.1353977109930; Mon,
26 Nov 2012 16:45:09 -0800 (PST)
Received: by 10.101.69.3 with HTTP; Mon, 26 Nov 2012 16:45:09 -0800 (PST)
In-Reply-To: <CANEZrP0fhM=N=LsYa=za8MobiJYG9Fbpv+WniL8td6pRpr6jgQ@mail.gmail.com>
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>
Date: Mon, 26 Nov 2012 16:45:09 -0800
Message-ID: <CAJ1JLts=WW3r-eV50513uB=a3XJvPcgjPTwG3OhQ3XnPtM3BNQ@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQna9ZM+5SYuevDYZi3lN0s4YwG1dE8uZMfKxlR3ahYuGVjt5l19xAfSU2x/1ZEHu+4HQtFk
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Td9IZ-0006DR-Cc
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 00:45:16 -0000
On Mon, Nov 26, 2012 at 4:26 PM, Mike Hearn <mike@plan99.net> wrote:
>> Perhaps we should agree to talk about everything _except_ that first?
>
> Yeah, alternatives to X.509 chains don't interest me right now except
> in the sense that they should be cleanly implementable with future
> extensions.
>
> So if you care about DANE or DNSSEC or custom PKI infrastructures or
> whatever, rather than proposing them as replacements here (DOA), just
> figure out how you would extend the protocol in Gavins mail in a
> future extension. If you can't see a clean way to do it then let's
> discuss that. If you can think of a way to do it then let's table it.
> Better replacements can come in later BIPs.
The only part that has an x509 cert associated is in the invoice message.
message Invoice {
// repeated bytes x509chain = 1;
optional string domainName =1;
repeated Output outputs = 2;
required uint64 time = 3;
optional uint64 expires = 4;
optional bool single_use = 5 [default = true];
optional string memo = 6;
optional string receiptURI = 7;
optional bytes merchant_data = 8;
}
Removing that and adding a opaque string called domain name, or
identityName would be sufficient to move the conversation forward
without the x.509 baggage.
-rick
|
