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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1RdAl8-0005KW-3p
for bitcoin-development@lists.sourceforge.net;
Wed, 21 Dec 2011 01:14:18 +0000
X-ACL-Warn:
Received: from nm36-vm3.bullet.mail.ne1.yahoo.com ([98.138.229.115])
by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1RdAl5-0001cG-Sv for bitcoin-development@lists.sourceforge.net;
Wed, 21 Dec 2011 01:14:18 +0000
Received: from [98.138.90.52] by nm36.bullet.mail.ne1.yahoo.com with NNFMP;
21 Dec 2011 01:14:10 -0000
Received: from [98.138.87.7] by tm5.bullet.mail.ne1.yahoo.com with NNFMP;
21 Dec 2011 01:14:10 -0000
Received: from [127.0.0.1] by omp1007.mail.ne1.yahoo.com with NNFMP;
21 Dec 2011 01:14:10 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 277027.4628.bm@omp1007.mail.ne1.yahoo.com
Received: (qmail 30969 invoked by uid 60001); 21 Dec 2011 01:14:10 -0000
X-YMail-OSG: vvXT0xgVM1kME_OsGGIJHgcOPt4wktOE7lDo6CBw45RhKj8
ePHfMBLMzsVXU49YvqmVFe0iSsP6RW4cDFOjgYzoGJoBh10ayDpGbTHtuc.8
YMAnGT.yrOptK70Cror8LaJ_OrUFEUBPsw8nbaV.nBptVkh2FVe57A88fi7e
Jf9o2jKDysM628mDsg5IvH5teZpV.PC4LKoo00aJKeJEgIKRaqtjU7fxvwYW
1y0SNRu1wObPGTmM9a2OyQB28J9iSl2JwKD.3ykFUaZ5_QiylLaSSdH_gdLe
_sI2A9qe_MzDFVniqkomu0XG.MnihK7ptjKrD5dUI9sUKpp5lpl3OauWmPLn
LugGoe_4NoUUyRlRWnhKqcXh_bIJT_nhqmf3OooxzjSc36J20jwRZtLoijUl
v_SM3lT8JXgG5XDOviL8.JlqAkQ--
Received: from [92.20.117.196] by web121001.mail.ne1.yahoo.com via HTTP;
Tue, 20 Dec 2011 17:14:10 PST
X-Mailer: YahooMailWebService/0.8.115.331698
References: <CAAS2fgQpMWYLoT_1Za5AxvgNaXvEuJOZ2BjE94o09=t+LyfM5A@mail.gmail.com>
<1324429140.3740.YahooMailNeo@web121001.mail.ne1.yahoo.com>
<201112202007.49399.luke@dashjr.org>
Message-ID: <1324430050.21731.YahooMailNeo@web121001.mail.ne1.yahoo.com>
Date: Tue, 20 Dec 2011 17:14:10 -0800 (PST)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <201112202007.49399.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="344044665-1924334194-1324430050=:21731"
X-Spam-Score: -1.9 (-)
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
(zgenjix[at]yahoo.com)
-2.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 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
-0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RdAl5-0001cG-Sv
Subject: Re: [Bitcoin-development] BIP language on normative behavior
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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: Wed, 21 Dec 2011 01:14:18 -0000
--344044665-1924334194-1324430050=:21731
Content-Type: text/plain; charset=us-ascii
OK, give me a shout on IRC. It is a lot of work though, so be prepared. Bring bags of patience :)
________________________________
From: Luke-Jr <luke@dashjr.org>
To: Amir Taaki <zgenjix@yahoo.com>
Sent: Wednesday, December 21, 2011 1:07 AM
Subject: Re: [Bitcoin-development] BIP language on normative behavior
On Tuesday, December 20, 2011 7:59:00 PM Amir Taaki wrote:
> A few weeks back I was in discussion with the IANA on getting a bitcoin URI
> accepted in the standard. As a prerequisite I had to read 5 huge
> documents. I did not end up writing that RFC.
I also contacted the IANA about getting the bitcoin URI spec accepted on their
index, however never heard back. If you want, please have whoever you
discussed it with get in touch with me. Either way, please be sure whatever
they index is compliant with the spec on the wiki as-is (especially not being
BTC unit specific, as this is clearly non-scalable).
Luke
--344044665-1924334194-1324430050=:21731
Content-Type: text/html; charset=us-ascii
<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>OK, give me a shout on IRC. It is a lot of work though, so be prepared. Bring bags of patience :)<br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Luke-Jr <luke@dashjr.org><br> <b><span style="font-weight: bold;">To:</span></b> Amir Taaki <zgenjix@yahoo.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, December 21, 2011 1:07 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Bitcoin-development] BIP language on normative behavior<br> </font> <br>
On Tuesday, December 20, 2011 7:59:00 PM Amir Taaki wrote:<br>> A few weeks back I was in discussion with the IANA on getting a bitcoin URI<br>> accepted in the standard. As a prerequisite I had to read 5 huge<br>> documents. I did not end up writing that RFC.<br><br>I also contacted the IANA about getting the bitcoin URI spec accepted on their <br>index, however never heard back. If you want, please have whoever you <br>discussed it with get in touch with me. Either way, please be sure whatever <br>they index is compliant with the spec on the wiki as-is (especially not being <br>BTC unit specific, as this is clearly non-scalable).<br><br>Luke<br><br><br> </div> </div> </div></body></html>
--344044665-1924334194-1324430050=:21731--
|