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
|
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 <zellfaze@yahoo.com>) id 1Rb2RX-0005JV-Ty
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 03:57:15 +0000
X-ACL-Warn:
Received: from nm38-vm5.bullet.mail.ne1.yahoo.com ([98.138.229.149])
by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1Rb2RW-0003Ks-Ql for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 03:57:15 +0000
Received: from [98.138.90.51] by nm38.bullet.mail.ne1.yahoo.com with NNFMP;
15 Dec 2011 03:57:09 -0000
Received: from [98.138.88.235] by tm4.bullet.mail.ne1.yahoo.com with NNFMP;
15 Dec 2011 03:57:09 -0000
Received: from [127.0.0.1] by omp1035.mail.ne1.yahoo.com with NNFMP;
15 Dec 2011 03:57:09 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 667810.65356.bm@omp1035.mail.ne1.yahoo.com
Received: (qmail 96807 invoked by uid 60001); 15 Dec 2011 03:57:09 -0000
X-YMail-OSG: 0EkAhGwVM1lZLZWfEMBoETHyjKBjTWUafxJdKFqRrquXVpF
tAvQRVQ53VoegjnTjfyQV4nTYwTYY_rRlfTVdERnBrtso8AQxCGtuK59HWa_
IDLVF49YVgCCzZ1t4C44O6e3F9RUSkbD2M.t8bL8oLXs572vH9a9wC7Dlaca
2KgTQhEz46ip7Zl4i2vscTTox4YSrI3JEbsVYfwQWXLbnuKgeN8RXorESz97
Othfw.4qBgq_HvAhKcPG1EOu_cdCQnRmsQCeMnjJBsTUyub2KuDskLKGn0CU
QRx9SQE1L.m1Etk1CstPQPrhfiVTS09GZ5ivNy7imZqCvfQC51CYWNEG6894
ZfhdzsEkElzFMorv_DenJ3JeBwnZTCrR7sY3QhvG854NqrGuqAAKGXKmxs0y
e7E1vt4VknUyWtNxWKhOfgcmnUVXkLL0se2R3hEuFu4V8Xazf0XM.saltfxI
cp_5cvg019QC8LPmPxivJFEwFKoOqpJ6F38hea7DsykF9qWb.71qIUUEZoOF
ip6kpT4vwGOAirAsE8URmVK9qRbIFn0xLijE3Md.e
Received: from [76.100.113.81] by web120901.mail.ne1.yahoo.com via HTTP;
Wed, 14 Dec 2011 19:57:09 PST
X-Mailer: YahooMailClassic/15.0.4 YahooMailWebService/0.8.115.331698
Message-ID: <1323921429.68086.YahooMailClassic@web120901.mail.ne1.yahoo.com>
Date: Wed, 14 Dec 2011 19:57:09 -0800 (PST)
From: Zell Faze <zellfaze@yahoo.com>
To: Luke-Jr <luke@dashjr.org>, Rick Wesson <rick@support-intelligence.com>
In-Reply-To: <CAJ1JLtuxTmbBZsZQjKZU6zdDKx96JKTbdzuoQ=+S2h81qA9mhQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.6 (--)
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.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-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: 1Rb2RW-0003Ks-Ql
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 03:57:16 -0000
Could we combine this proposal and the HTTPS proposal?=0A=0AThe DNSSEC TXT =
record could give instructions on how to query an HTTPS server to get the a=
ddress. Then we get the dynamism of HTTPS without having a rigid URL schem=
e for querying the server along with the advantages of DNSSEC.=0A=0A=0A--- =
On Wed, 12/14/11, Rick Wesson <rick@support-intelligence.com> wrote:=0A=0A>=
From: Rick Wesson <rick@support-intelligence.com>=0A> Subject: Re: [Bitcoi=
n-development] Fwd: [BIP 15] Aliases=0A> To: "Luke-Jr" <luke@dashjr.org>=0A=
> Cc: bitcoin-development@lists.sourceforge.net=0A> Date: Wednesday, Decemb=
er 14, 2011, 8:22 PM=0A> understand that not *everyone* wants=0A> or will a=
dhere to that best=0A> practice and in my NSHO it isn't.=0A> =0A> -rick=0A>=
=0A> 2011/12/14 Luke-Jr <luke@dashjr.org>:=0A> > On Wednesday, December 14=
, 2011 6:02:25 PM Rick Wesson=0A> wrote:=0A> >> I also am largely in favor =
of using secured zones=0A> to publish TXT=0A> >> records to digital currenc=
ies. I've been thinking=0A> mainly about TXT=0A> >> using the following for=
mat for bitcoin.=0A> >>=0A> >> _btc.<lhs>.<rhs>=0A> >=0A> > Don't confuse B=
TC (Bitcoin unit) with BC (Bitcoin in=0A> general / protocol)...=0A> > The =
hard part of using DNS will be sticking to the=0A> standard good practice o=
f=0A> > using a new address for every transaction.=0A> =0A> ---------------=
---------------------------------------------------------------=0A> 10 Tips=
for Better Server Consolidation=0A> Server virtualization is being driven =
by many needs.=A0=0A> =0A> But none more important than the need to reduce =
IT=0A> complexity =0A> while improving strategic productivity.=A0 Learn Mor=
e! =0A> http://www.accelacomm.com/jaw/sdnl/114/51507609/=0A> ______________=
_________________________________=0A> Bitcoin-development mailing list=0A> =
Bitcoin-development@lists.sourceforge.net=0A> https://lists.sourceforge.net=
/lists/listinfo/bitcoin-development=0A>
|
