public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jannis Froese <s9jafroe@stud.uni-saarland.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP0071 media type registration with IANA
Date: Sat, 26 Apr 2014 23:16:48 +0200	[thread overview]
Message-ID: <535C2240.6030600@stud.uni-saarland.de> (raw)
In-Reply-To: <CANEZrP0iNXRu+pXwjXHVihY4YtgOpyUO3bveLx0ZT5yTqyvXJw@mail.gmail.com>

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



      reply	other threads:[~2014-04-26 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-26 20:15 [Bitcoin-development] BIP0071 media type registration with IANA Ross Nicoll
2014-04-26 20:17 ` Mike Hearn
2014-04-26 21:16   ` Jannis Froese [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=535C2240.6030600@stud.uni-saarland.de \
    --to=s9jafroe@stud.uni-saarland.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox