1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
|
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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CANEZrP0iNXRu+pXwjXHVihY4YtgOpyUO3bveLx0ZT5yTqyvXJw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Ross Nicoll <jrn@jrn.me.uk>
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 <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <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"><<a href=3D"mailto:jr=
n@jrn.me.uk" target=3D"_blank">jrn@jrn.me.uk</a>></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'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 "application/" namespace.<br=
>
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<br=
>
2007 ended up as<br>
"application/vnd.openxmlformats-officedocument.presentationml.presenta=
tion"),<br>
but would be quite a dramatic change to BIP0071.<br>
<br>
What's the general feeling on this? Personally I'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--
|
