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
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rick.wesson@iidf.org>) id 1RbDSj-0001Ei-DM
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 15:43:13 +0000
X-ACL-Warn:
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RbDSX-000711-Jq
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 15:43:13 +0000
Received: by mail-vx0-f175.google.com with SMTP id f1so781947vcb.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 15 Dec 2011 07:43:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.21.211 with SMTP id x19mr3549686vde.58.1323963779293; Thu,
15 Dec 2011 07:42:59 -0800 (PST)
Received: by 10.52.37.80 with HTTP; Thu, 15 Dec 2011 07:42:59 -0800 (PST)
In-Reply-To: <1323929094.37881.YahooMailClassic@web120902.mail.ne1.yahoo.com>
References: <CA+QPp0rAJz9wPcrf926q=_c45mCL_67JCyacvM79CWcic9AL2w@mail.gmail.com>
<1323929094.37881.YahooMailClassic@web120902.mail.ne1.yahoo.com>
Date: Thu, 15 Dec 2011 07:42:59 -0800
Message-ID: <CAJ1JLts1KnhJbKfDv8Qu1iX6XNRS4ovgmvS2a5-CWLPR9sxDtg@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Zell Faze <zellfaze@yahoo.com>
Content-Type: multipart/alternative; boundary=20cf3079bafac2a3d104b4235678
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.3 URI_HEX URI: URI hostname has long hexadecimal sequence
1.0 HTML_MESSAGE BODY: HTML included in message
-1.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RbDSX-000711-Jq
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
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: Thu, 15 Dec 2011 15:43:13 -0000
--20cf3079bafac2a3d104b4235678
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Are we designing protocols or applications, its easier and better for all
involved if we design a protocol and then let the applications implement
it.
Lets stick to understanding how labels (dns) or URIs can be leveraged to
securly obtain a bitcoin address, rather than reviewing capabilities of
current applications.
-rick
On Wed, Dec 14, 2011 at 10:04 PM, Zell Faze <zellfaze@yahoo.com> wrote:
> It is a lot easier to set up an HTTP server to dynamically respond with
> addresses than a DNS record. It is considered a good practice to use a
> different address for every payment.
>
> ------------------------
> "It stopped being just a website a long time ago. For many of us, most of
> us, Wikipedia has become an indispensable part of our daily lives."
> =97 Jimmy Wales, *Founder of Wikipedia*
> <http://2e740a1a.qvvo.com/>
>
> Help protect it now. Please make a donation today:
> http://www.wikimediafoundation.org/wiki/Donate
>
>
> --- On *Wed, 12/14/11, Kyle Henderson <k@old.school.nz>* wrote:
>
>
> From: Kyle Henderson <k@old.school.nz>
>
> Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
> To: "Zell Faze" <zellfaze@yahoo.com>
> Cc: "Luke-Jr" <luke@dashjr.org>, "Rick Wesson" <
> rick@support-intelligence.com>, bitcoin-development@lists.sourceforge.net
> Date: Wednesday, December 14, 2011, 11:56 PM
>
>
> Just so we're clear, what is the need for HTTP at all?
>
> A query for a string and an answer can all be handled via DNS.
>
> On Thu, Dec 15, 2011 at 4:57 PM, Zell Faze <zellfaze@yahoo.com<http://mc/=
compose?to=3Dzellfaze@yahoo.com>
> > wrote:
>
> Could we combine this proposal and the HTTPS proposal?
>
> The DNSSEC TXT record could give instructions on how to query an HTTPS
> server to get the address. Then we get the dynamism of HTTPS without
> having a rigid URL scheme for querying the server along with the advantag=
es
> of DNSSEC.
>
>
>
--20cf3079bafac2a3d104b4235678
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Are we designing protocols or applications, its easier and better for all i=
nvolved if we design a protocol and then let the applications implement it.=
=A0<div><br></div><div>Lets stick to understanding how labels (dns) or URIs=
can be leveraged to securly obtain a bitcoin address, rather than reviewin=
g capabilities of current applications.</div>
<div><br></div><div>-rick</div><div><br><div class=3D"gmail_quote">On Wed, =
Dec 14, 2011 at 10:04 PM, Zell Faze <span dir=3D"ltr"><<a href=3D"mailto=
:zellfaze@yahoo.com">zellfaze@yahoo.com</a>></span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0"><tbody><tr><td vali=
gn=3D"top" style=3D"font:inherit">It is a lot easier to set up an HTTP serv=
er to dynamically respond with addresses than a DNS record. =A0It is consid=
ered a good practice to use a different address for every payment.<br>
<br>------------------------<br>"It stopped being just a website a lon=
g time ago. For many of us, most of us, Wikipedia has become an indispensab=
le part of our daily lives."<br>=97 Jimmy Wales, <i>Founder of Wikiped=
ia</i> <br>
<a rel=3D"nofollow" href=3D"http://2e740a1a.qvvo.com/" target=3D"_blank"></=
a><tt></tt><p style=3D"MARGIN-TOP:0px"><tt>Help protect it now. Please make=
a donation today: <a rel=3D"nofollow" title=3D"http://www.wikimediafoundat=
ion.org/wiki/Donate" href=3D"http://www.wikimediafoundation.org/wiki/Donate=
" target=3D"_blank">http://www.wikimediafoundation.org/wiki/Donate</a></tt>=
<br>
</p><br><br>--- On <b>Wed, 12/14/11, Kyle Henderson
<i><<a href=3D"mailto:k@old.school.nz" target=3D"_blank">k@old.school.n=
z</a>></i></b> wrote:<br><blockquote style=3D"border-left:2px solid rgb(=
16,16,255);margin-left:5px;padding-left:5px"><br>From: Kyle Henderson <<=
a href=3D"mailto:k@old.school.nz" target=3D"_blank">k@old.school.nz</a>>=
<div class=3D"im">
<br>Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases<br></div>To: &=
quot;Zell Faze" <<a href=3D"mailto:zellfaze@yahoo.com" target=3D"_b=
lank">zellfaze@yahoo.com</a>><br>Cc: "Luke-Jr" <<a href=3D"=
mailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>>, "Ri=
ck Wesson" <<a href=3D"mailto:rick@support-intelligence.com" target=
=3D"_blank">rick@support-intelligence.com</a>>, <a href=3D"mailto:bitcoi=
n-development@lists.sourceforge.net" target=3D"_blank">bitcoin-development@=
lists.sourceforge.net</a><br>
Date: Wednesday, December 14, 2011, 11:56 PM<div><div class=3D"h5"><br><br>=
<div>Just so we're clear, what is the need for HTTP at all?<br><br>A qu=
ery for a string and an answer can all be handled via DNS.<br><br><div>On T=
hu, Dec 15, 2011 at 4:57 PM, Zell Faze <span dir=3D"ltr"><<a rel=3D"nofo=
llow" href=3D"http://mc/compose?to=3Dzellfaze@yahoo.com" target=3D"_blank">=
zellfaze@yahoo.com</a>></span> wrote:<br>
<blockquote style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">Could we combine this proposal and the HTTPS proposal?<br>
<br>
The DNSSEC TXT record could give instructions on how to query an HTTPS serv=
er to get the address. =A0Then we get the dynamism of HTTPS without having =
a rigid URL scheme for querying the server along with the advantages of DNS=
SEC.<br>
<br></blockquote></div><br>
</div></div></div></blockquote></td></tr></tbody></table></blockquote></div=
><br></div>
--20cf3079bafac2a3d104b4235678--
|
