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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
Return-Path: <keatonatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 29EB994D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 21 Jun 2016 20:56:52 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f175.google.com (mail-qk0-f175.google.com
[209.85.220.175])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0167B1D4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 21 Jun 2016 20:56:50 +0000 (UTC)
Received: by mail-qk0-f175.google.com with SMTP id t127so39052880qkf.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 21 Jun 2016 13:56:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=F0UwbEt58vhOGmW+vCe4TwPrTrgBefcMNCdtPOhzpoc=;
b=ORlH2/exVob81Ze82VtKBuw8NLgayGbQkNNcuTWHPg9JsX3AazHM6y2NZZmUD8Scj1
U5BfC/AKvb6sNH/s/RpkijRxnpj3G3TP/7kH4+/X2+H8yPnBDqSameH/rfoXzo6+pR3r
P8IwRv1dKspm+leHssCVNMVdhB0S05rC9ef3P8GSgnD7pbnjvpcNW/4DVvzEMjq5j7Nv
txqg0QDNt9a25EV3gO79yL8Qc/OhLtb8JXWt2v41GKwhwALMyHlg42ayt5uoBB2ZLIsG
ivmGqbU+Ch38CJNI7IcgXgdStIAxPBdSvoZ1SGEUOPaOjKM8qGzxTOBNgEdfIYryz4i/
WQzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=F0UwbEt58vhOGmW+vCe4TwPrTrgBefcMNCdtPOhzpoc=;
b=UwxJOm+DA0G+BBoCk2RDa5Zfbn0N0qiTr2EWIvPwwgQcBKo3/Del+ZTjqgeDUc62EF
xr0PK2pFTRP59xeWHkx+zGJAin7GcAk3HRU2UQ2nWYb6TWi/R3342eGYqDbqLuKZKETk
Lp5VQpEQK3SAKswUd7Dux886a74C2ntVlqNpZtUbWd0na+tC18O/40i8LsZL7WQIqTZ2
BR8V0SIR8OVv3A3VUNvMmCmqSwR9rz728qNDGhBxbg9LcdeXusSkmOqxZHy2QIZMj+MM
kCdJyUWCNXW+poRy5ypqiGVS8ogOhJKBS7IuOdPYglAgpm+h37cJvELVeSRSy429wr3f
JdHg==
X-Gm-Message-State: ALyK8tK0lXaAPuqqoWCGiqtz6dYBj/HtfGhEnu800zy5rhJ8UqOIbd3CVZO8VYA2AsPAsx91DfEVv3ekOA311w==
X-Received: by 10.55.165.4 with SMTP id o4mr31509665qke.15.1466542609828; Tue,
21 Jun 2016 13:56:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
In-Reply-To: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com>
From: James MacWhyte <macwhyte@gmail.com>
Date: Tue, 21 Jun 2016 20:56:40 +0000
Message-ID: <CAH+Axy7OtGgbtmz+grfuob419PwQJiYfZsQnMEs=_McZFBqu2A@mail.gmail.com>
To: Erik Aronesty <erik@q32.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114fac884e92490535d00ff5
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2016 20:56:52 -0000
--001a114fac884e92490535d00ff5
Content-Type: text/plain; charset=UTF-8
Thanks for starting this discussion, Erik.
> Should this be a new BIP? I know netki's BIP75 is out there - but I think
> it's too specific and too reliant on the domain name system.
>
This is not quite accurate. BIP75 is designed to be independent of any name
resolution system. You could use it with a static URL that you share, for
example, or even use it to implement a mesh-network payment system over
bluetooth. Netki's wallet names do use DNS, but that isn't related to this
discussion.
What BIP75 *does* do is provide a way for a client to get a new payment
address for every payment. I personally think it is better than BIP47 for
the uses you mentioned (subscriptions, etc).
I'm glad you brought up identity methods other than x509. At breadwallet we
are thinking about how to establish the most universal system, and letting
users identify themselves with any of a selection of identity systems is
ideal. I think the pki_data slot should be constantly expanded to allow new
identity types, but they should be explained/standardized in the BIPs that
add them and use universal names. "netki://" wouldn't be appropriate, for
example, if their method is open sourced and possibly used by others--it
should instead be given a product name like "dnswallet://" or something
more clever.
James
--001a114fac884e92490535d00ff5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thanks for starting this discussion, Erik.<br><br><div><di=
v class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><di=
v><br></div><div>Should this be a new BIP?=C2=A0 I know netki's BIP75 i=
s out there - but I think it's too specific and too reliant on the doma=
in name system.<br></div></div></blockquote><div>=C2=A0</div><div><font col=
or=3D"#212121" face=3D"helvetica neue, helvetica, arial, sans-serif">This i=
s not quite accurate. BIP75 is designed to be independent of any name resol=
ution system. You could use it with a static URL that you share, for exampl=
e, or even use it to implement a mesh-network payment system over bluetooth=
. Netki's wallet names do use DNS, but that isn't related to this d=
iscussion.</font></div><div><font color=3D"#212121" face=3D"helvetica neue,=
helvetica, arial, sans-serif"><br></font></div><div><font color=3D"#212121=
" face=3D"helvetica neue, helvetica, arial, sans-serif">What BIP75 *does* d=
o is provide a way for a client to get a new payment address for every paym=
ent. I personally think it is better than BIP47 for the uses you mentioned =
(subscriptions, etc).</font></div><br class=3D"inbox-inbox-Apple-interchang=
e-newline"><div>I'm glad you brought up identity methods other than x50=
9. At breadwallet we are thinking about how to establish the most universal=
system, and letting users identify themselves with any of a selection of i=
dentity systems is ideal. I think the pki_data slot should be constantly ex=
panded to allow new identity types, but they should be explained/standardiz=
ed in the BIPs that add them and use universal names. "<span style=3D"=
line-height:1.5">netki://" wouldn't be appropriate, for example, i=
f their method is open sourced and possibly used by others--it should inste=
ad be given a product name like "dnswallet://" or something more =
clever.<br><br>James<br><br><br></span></div></div></div></div>
--001a114fac884e92490535d00ff5--
|
