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
Subject: Re: [Bitcoin-development] BIP0071 media type registration with IANA
Precedence: list

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