Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.47 as permitted sender)
	client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f47.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <535C13E0.5070701@jrn.me.uk>
References: <535C13E0.5070701@jrn.me.uk>
Date: Sat, 26 Apr 2014 22:17:58 +0200
Message-ID: <CANEZrP0iNXRu+pXwjXHVihY4YtgOpyUO3bveLx0ZT5yTqyvXJw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Ross Nicoll <jrn@jrn.me.uk>
Content-Type: multipart/alternative; boundary=047d7b33d3c63a5afa04f7f7c7b2
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0071 media type registration with IANA
Precedence: list

--047d7b33d3c63a5afa04f7f7c7b2
Content-Type: text/plain; charset=UTF-8

Bitcoin is not a vendor, so I doubt that would work.

I doubt we should spend any time on this. The chance of a string collision
is extremely low. The current mime types are fine.


On Sat, Apr 26, 2014 at 10:15 PM, Ross Nicoll <jrn@jrn.me.uk> wrote:

> Dear all,
>
> Still going through the payment protocol specifications... the MIME
> types in BIP0071 aren't IANA registered, and honestly look unlikely to
> be accepted if they were submitted as-is.
>
> Latest RFC on media type registration is RFC 6838, which very strictly
> restricts what can go in the default "application/" namespace.
> Essentially they'd want it to be an ISO standard or similar. There are
> vendor namespaces, which look much more feasible (this is how Powerpoint
> 2007 ended up as
>
> "application/vnd.openxmlformats-officedocument.presentationml.presentation"),
> but would be quite a dramatic change to BIP0071.
>
> What's the general feeling on this? Personally I'm in favour of
> following the registration process, so register a Bitcoin vendor
> namespace with IANA, then allocate MIME types such as:
>
> application/vnd.bitcoin.payment.request
> application/vnd.bitcoin.payment.payment
> application/vnd.bitcoin.payment.ack
>
> Thoughts?
>
> Ross
>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--047d7b33d3c63a5afa04f7f7c7b2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Bitcoin is not a vendor, so I doubt that would work.<div><=
br></div><div>I doubt we should spend any time on this. The chance of a str=
ing collision is extremely low. The current mime types are fine.</div></div=
>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, Apr 2=
6, 2014 at 10:15 PM, Ross Nicoll <span dir=3D"ltr">&lt;<a href=3D"mailto:jr=
n@jrn.me.uk" target=3D"_blank">jrn@jrn.me.uk</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
Dear all,<br>
<br>
Still going through the payment protocol specifications... the MIME<br>
types in BIP0071 aren&#39;t IANA registered, and honestly look unlikely to<=
br>
be accepted if they were submitted as-is.<br>
<br>
Latest RFC on media type registration is RFC 6838, which very strictly<br>
restricts what can go in the default &quot;application/&quot; namespace.<br=
>
Essentially they&#39;d want it to be an ISO standard or similar. There are<=
br>
vendor namespaces, which look much more feasible (this is how Powerpoint<br=
>
2007 ended up as<br>
&quot;application/vnd.openxmlformats-officedocument.presentationml.presenta=
tion&quot;),<br>
but would be quite a dramatic change to BIP0071.<br>
<br>
What&#39;s the general feeling on this? Personally I&#39;m in favour of<br>
following the registration process, so register a Bitcoin vendor<br>
namespace with IANA, then allocate MIME types such as:<br>
<br>
application/vnd.bitcoin.payment.request<br>
application/vnd.bitcoin.payment.payment<br>
application/vnd.bitcoin.payment.ack<br>
<br>
Thoughts?<br>
<br>
Ross<br>
<br>
---------------------------------------------------------------------------=
---<br>
Start Your Social Network Today - Download eXo Platform<br>
Build your Enterprise Intranet with eXo Platform Software<br>
Java Based Open Source Intranet - Social, Extensible, Cloud Ready<br>
Get Started Now And Turn Your Intranet Into A Collaboration Platform<br>
<a href=3D"http://p.sf.net/sfu/ExoPlatform" target=3D"_blank">http://p.sf.n=
et/sfu/ExoPlatform</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>

--047d7b33d3c63a5afa04f7f7c7b2--