📅 Original date posted:2014-04-26
📝 Original message: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 at 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/10d25654/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:20:24
in reply to nevent1q…y6l8
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:20:24Event JSON
{
"id": "41e1071f1debf7263fc1a46df9d8c366dd0682f16806f4a20db6de9998dc2bf8",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686151224,
"kind": 1,
"tags": [
[
"e",
"eead7eb71aa5c3163acf136804322750e41e1f430fdfe72cb055df5c60d16049",
"",
"root"
],
[
"e",
"468ec9fa4914c6aacc43c308d9cd92d74e68205d33fa1d162e17fd31969b67ba",
"",
"reply"
],
[
"p",
"787ecd48da0d9610d322fb67c86ad23a5287d688559b2ff8ee546721fd990129"
]
],
"content": "📅 Original date posted:2014-04-26\n📝 Original message:Bitcoin is not a vendor, so I doubt that would work.\n\nI doubt we should spend any time on this. The chance of a string collision\nis extremely low. The current mime types are fine.\n\n\nOn Sat, Apr 26, 2014 at 10:15 PM, Ross Nicoll \u003cjrn at jrn.me.uk\u003e wrote:\n\n\u003e Dear all,\n\u003e\n\u003e Still going through the payment protocol specifications... the MIME\n\u003e types in BIP0071 aren't IANA registered, and honestly look unlikely to\n\u003e be accepted if they were submitted as-is.\n\u003e\n\u003e Latest RFC on media type registration is RFC 6838, which very strictly\n\u003e restricts what can go in the default \"application/\" namespace.\n\u003e Essentially they'd want it to be an ISO standard or similar. There are\n\u003e vendor namespaces, which look much more feasible (this is how Powerpoint\n\u003e 2007 ended up as\n\u003e\n\u003e \"application/vnd.openxmlformats-officedocument.presentationml.presentation\"),\n\u003e but would be quite a dramatic change to BIP0071.\n\u003e\n\u003e What's the general feeling on this? Personally I'm in favour of\n\u003e following the registration process, so register a Bitcoin vendor\n\u003e namespace with IANA, then allocate MIME types such as:\n\u003e\n\u003e application/vnd.bitcoin.payment.request\n\u003e application/vnd.bitcoin.payment.payment\n\u003e application/vnd.bitcoin.payment.ack\n\u003e\n\u003e Thoughts?\n\u003e\n\u003e Ross\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Start Your Social Network Today - Download eXo Platform\n\u003e Build your Enterprise Intranet with eXo Platform Software\n\u003e Java Based Open Source Intranet - Social, Extensible, Cloud Ready\n\u003e Get Started Now And Turn Your Intranet Into A Collaboration Platform\n\u003e http://p.sf.net/sfu/ExoPlatform\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/10d25654/attachment.html\u003e",
"sig": "ccdfcb0732be519c12b8fc27b28a11f77ecf30740c9ac105ee876acd76c92af1678613950d8db9cec8d0ad1a0598f1a5df3a5ea23de1d95f83eff992e71e9600"
}