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
|
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 <s9jafroe@stud.uni-saarland.de>) id 1We9y7-0005bt-Fm
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Apr 2014 21:17:07 +0000
X-ACL-Warn:
Received: from theia.rz.uni-saarland.de ([134.96.7.31])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1We9y4-0008K6-4P
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Apr 2014 21:17:07 +0000
Received: from [192.168.2.101] (p54B08286.dip0.t-ipconnect.de [84.176.130.134])
(authenticated bits=0)
by theia.rz.uni-saarland.de (8.14.1/8.14.0) with ESMTP id
s3QLGjvR012116
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
for <bitcoin-development@lists.sourceforge.net>;
Sat, 26 Apr 2014 23:16:57 +0200
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.1 at HIZ-Mailrelay theia.rz.uni-saarland.de
Message-ID: <535C2240.6030600@stud.uni-saarland.de>
Date: Sat, 26 Apr 2014 23:16:48 +0200
From: Jannis Froese <s9jafroe@stud.uni-saarland.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <535C13E0.5070701@jrn.me.uk>
<CANEZrP0iNXRu+pXwjXHVihY4YtgOpyUO3bveLx0ZT5yTqyvXJw@mail.gmail.com>
In-Reply-To: <CANEZrP0iNXRu+pXwjXHVihY4YtgOpyUO3bveLx0ZT5yTqyvXJw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
milter-greylist-3.0 (theia.rz.uni-saarland.de [134.96.7.31]);
Sat, 26 Apr 2014 23:16:57 +0200 (CEST)
X-Spam-Score: -0.7 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1We9y4-0008K6-4P
Subject: Re: [Bitcoin-development] BIP0071 media type registration with IANA
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: Sat, 26 Apr 2014 21:17:08 -0000
Am 2014-04-26 22:17, schrieb Mike Hearn:
> Bitcoin is not a vendor, so I doubt that would work.
By my interpretation of RFC 6838, the Bitcoin Foundation or even Gavin
himself could register a vendor tree for Bitcoin. In the case of the
foundation registering, getting the subtree named vdn.bitcoin should be
no problem.
> I doubt we should spend any time on this. The chance of a string
> collision is extremely low. The current mime types are fine.
It's mostly about the good feeling of having followed the rules and
proper procedures, I doubt that there is a difference in practice
|
