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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <k@old.school.nz>) id 1Rb3qQ-0005GJ-BT
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 05:27:02 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of old.school.nz
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=k@old.school.nz;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Rb3qP-000729-Ed
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 05:27:02 +0000
Received: by vbbfc21 with SMTP id fc21so1762542vbb.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 14 Dec 2011 21:26:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.69.70 with SMTP id c6mr1401990vdu.65.1323925013100; Wed, 14
Dec 2011 20:56:53 -0800 (PST)
Received: by 10.220.107.70 with HTTP; Wed, 14 Dec 2011 20:56:52 -0800 (PST)
X-Originating-IP: [60.234.234.61]
In-Reply-To: <1323921429.68086.YahooMailClassic@web120901.mail.ne1.yahoo.com>
References: <CAJ1JLtuxTmbBZsZQjKZU6zdDKx96JKTbdzuoQ=+S2h81qA9mhQ@mail.gmail.com>
<1323921429.68086.YahooMailClassic@web120901.mail.ne1.yahoo.com>
Date: Thu, 15 Dec 2011 17:56:52 +1300
Message-ID: <CA+QPp0rAJz9wPcrf926q=_c45mCL_67JCyacvM79CWcic9AL2w@mail.gmail.com>
From: Kyle Henderson <k@old.school.nz>
To: Zell Faze <zellfaze@yahoo.com>
Content-Type: multipart/alternative; boundary=20cf307f32401d770704b41a500d
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Rb3qP-000729-Ed
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 05:27:02 -0000
--20cf307f32401d770704b41a500d
Content-Type: text/plain; charset=UTF-8
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:
> 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 advantages
> of DNSSEC.
>
>
--20cf307f32401d770704b41a500d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Just so we're clear, what is the need for HTTP at all?<br><br>A query f=
or a string and an answer can all be handled via DNS.<br><br><div class=3D"=
gmail_quote">On Thu, Dec 15, 2011 at 4:57 PM, Zell Faze <span dir=3D"ltr">&=
lt;<a href=3D"mailto:zellfaze@yahoo.com">zellfaze@yahoo.com</a>></span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left: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. =C2=A0Then we get the dynamism of HTTPS without havi=
ng a rigid URL scheme for querying the server along with the advantages of =
DNSSEC.<br>
<br></blockquote></div><br>
--20cf307f32401d770704b41a500d--
|
