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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zellfaze@yahoo.com>) id 1Rb4RA-0003LQ-RB
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 06:05:00 +0000
X-ACL-Warn:
Received: from nm31-vm3.bullet.mail.ne1.yahoo.com ([98.138.229.43])
by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1Rb4R9-0000cY-JO for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 06:05:00 +0000
Received: from [98.138.90.54] by nm31.bullet.mail.ne1.yahoo.com with NNFMP;
15 Dec 2011 06:04:54 -0000
Received: from [98.138.89.167] by tm7.bullet.mail.ne1.yahoo.com with NNFMP;
15 Dec 2011 06:04:54 -0000
Received: from [127.0.0.1] by omp1023.mail.ne1.yahoo.com with NNFMP;
15 Dec 2011 06:04:54 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 456180.7429.bm@omp1023.mail.ne1.yahoo.com
Received: (qmail 44454 invoked by uid 60001); 15 Dec 2011 06:04:54 -0000
X-YMail-OSG: LqVDL10VM1mss3VuT80la44Cj8gmGnT0Gz1J8cyRFguNbRn
u8eNl6EBsUhv73uUCrJnhK6iqa3x_zoap6xJvmPfjKnnbXNIhCmq5zMt5.6e
bRJL8MuuOFDUDxMutO7mWUQuoERC45jqmxonnKoRK4A_bN9Ysw89fOdxJHJH
RYotOyNWGuOlknXeKLqNPDsXrmQFGc15F9WyGZD.ENLdeOhlSYWFC1Uxylmv
0Zq7kbGtCZ52mY4G_NfSUi_o2FXlPl168zAaFn6HlQBpMjok0hXdW17aQSPg
cgzIvXVS9oyNBay3WbCigb423N549Bi0HJSHiB3U5sxv1lVe3Mxgku3iU31b
CSOJj08SDxUPDYFtDpIvbQgTQfKcFy0faxfutiqbxdWrSH3Jb.QDtRNvF3sC
QqKW9YqgR05sAUrDv_YG21GiQxT7E_Cr2E4uQcbnhPxGEQEIf44ELMWZ4qSV
_UY3XmglWgifIPQGDkWFcQoBi41lCt.rbl0jNwAHCUe49aB.yBjNzY7Kh4rB
d.RPZefrrXLOB2VJbfjDv66Oi3OnFIrVCsmSpUXgw273eFwbderA6Y1tUGoW
GNBPQZ1gOA4D5LHGI5uSz12zzBTM178PhOtcq
Received: from [76.100.113.81] by web120902.mail.ne1.yahoo.com via HTTP;
Wed, 14 Dec 2011 22:04:54 PST
X-Mailer: YahooMailClassic/15.0.4 YahooMailWebService/0.8.115.331698
Message-ID: <1323929094.37881.YahooMailClassic@web120902.mail.ne1.yahoo.com>
Date: Wed, 14 Dec 2011 22:04:54 -0800 (PST)
From: Zell Faze <zellfaze@yahoo.com>
To: Kyle Henderson <k@old.school.nz>
In-Reply-To: <CA+QPp0rAJz9wPcrf926q=_c45mCL_67JCyacvM79CWcic9AL2w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="-1577048185-497164864-1323929094=:37881"
X-Spam-Score: -1.3 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zellfaze[at]yahoo.com)
-2.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
1.3 URI_HEX URI: URI hostname has long hexadecimal sequence
1.0 HTML_MESSAGE BODY: HTML included in message
-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
-1.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Rb4R9-0000cY-JO
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 06:05:00 -0000
---1577048185-497164864-1323929094=:37881
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
It is a lot easier to set up an HTTP server to dynamically respond with add=
resses than a DNS record. =C2=A0It is considered a good practice to use a d=
ifferent address for every payment.
------------------------
"It stopped being just a website a long time ago. For many of us, most of u=
s, Wikipedia has become an indispensable part of our daily lives."
=E2=80=94 Jimmy Wales, Founder of Wikipedia=20
Help protect it now. Please make a donation today: http://www.wikimediafoun=
dation.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.c=
om>, 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> wrote:
=0ACould we combine this proposal and the HTTPS proposal?
=0A
=0AThe DNSSEC TXT record could give instructions on how to query an HTTPS s=
erver to get the address. =C2=A0Then we get the dynamism of HTTPS without h=
aving a rigid URL scheme for querying the server along with the advantages =
of DNSSEC.
=0A=0A
=0A
---1577048185-497164864-1323929094=:37881
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" ><tr><td valign=3D"=
top" style=3D"font: inherit;">It is a lot easier to set up an HTTP server t=
o dynamically respond with addresses than a DNS record. It is conside=
red a good practice to use a different address for every payment.<br><br>--=
----------------------<br>"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."<br>=E2=80=94 Jimmy Wales, <i>Founder of Wikipedia</i> <br=
><a rel=3D"nofollow" target=3D"_blank" href=3D"http://2e740a1a.qvvo.com/"><=
/a><tt></tt><p style=3D"MARGIN-TOP:0px;"><tt>Help protect it now. Please ma=
ke a donation today: <a rel=3D"nofollow" class=3D"external free" title=3D"h=
ttp://www.wikimediafoundation.org/wiki/Donate" target=3D"_blank" href=3D"ht=
tp://www.wikimediafoundation.org/wiki/Donate">http://www.wikimediafoundatio=
n.org/wiki/Donate</a></tt><br></p><br><br>--- On <b>Wed, 12/14/11, Kyle Hen=
derson
<i><k@old.school.nz></i></b> wrote:<br><blockquote style=3D"border-l=
eft: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>=
From: Kyle Henderson <k@old.school.nz><br>Subject: Re: [Bitcoin-devel=
opment] Fwd: [BIP 15] Aliases<br>To: "Zell Faze" <zellfaze@yahoo.com>=
<br>Cc: "Luke-Jr" <luke@dashjr.org>, "Rick Wesson" <rick@support-i=
ntelligence.com>, bitcoin-development@lists.sourceforge.net<br>Date: Wed=
nesday, December 14, 2011, 11:56 PM<br><br><div id=3D"yiv1743879651">Just s=
o we're clear, what is the need for HTTP at all?<br><br>A query for a strin=
g and an answer can all be handled via DNS.<br><br><div class=3D"yiv1743879=
651gmail_quote">On Thu, Dec 15, 2011 at 4:57 PM, Zell Faze <span dir=3D"ltr=
"><<a rel=3D"nofollow" ymailto=3D"mailto:zellfaze@yahoo.com" target=3D"_=
blank" href=3D"/mc/compose?to=3Dzellfaze@yahoo.com">zellfaze@yahoo.com</a>&=
gt;</span> wrote:<br>=0A<blockquote class=3D"yiv1743879651gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Could =
we combine this proposal and the HTTPS proposal?<br>=0A<br>=0AThe DNSSEC TX=
T 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 UR=
L scheme for querying the server along with the advantages of DNSSEC.<br>=
=0A=0A<br></blockquote></div><br>=0A</div></blockquote></td></tr></table>
---1577048185-497164864-1323929094=:37881--
|
