From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1We92y-00078g-Jy for bitcoin-development@lists.sourceforge.net; Sat, 26 Apr 2014 20:18:04 +0000 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; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1We92x-0004Sp-KR for bitcoin-development@lists.sourceforge.net; Sat, 26 Apr 2014 20:18:04 +0000 Received: by mail-oa0-f47.google.com with SMTP id i11so5643418oag.20 for ; Sat, 26 Apr 2014 13:17:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.92.132 with SMTP id cm4mr3451775oeb.49.1398543478314; Sat, 26 Apr 2014 13:17:58 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.96.180 with HTTP; Sat, 26 Apr 2014 13:17:58 -0700 (PDT) In-Reply-To: <535C13E0.5070701@jrn.me.uk> References: <535C13E0.5070701@jrn.me.uk> Date: Sat, 26 Apr 2014 22:17:58 +0200 X-Google-Sender-Auth: 3wWfGF86RLNCB-6bqSJ7H1ONQZw Message-ID: From: Mike Hearn To: Ross Nicoll Content-Type: multipart/alternative; boundary=047d7b33d3c63a5afa04f7f7c7b2 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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 X-Headers-End: 1We92x-0004Sp-KR Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2014 20:18:05 -0000 --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 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
Bitcoin is not a vendor, so I doubt that would work.
<= br>
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.


On Sat, Apr 2= 6, 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<= br> 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<= br> vendor namespaces, which look much more feasible (this is how Powerpoint 2007 ended up as
"application/vnd.openxmlformats-officedocument.presentationml.presenta= tion"),
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.n= et/sfu/ExoPlatform
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7b33d3c63a5afa04f7f7c7b2--