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
|
Return-Path: <achow101-lists@achow101.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
by lists.linuxfoundation.org (Postfix) with ESMTP id D7C51C000E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 31 Aug 2021 19:47:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id BF98182456
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 31 Aug 2021 19:47:11 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=achow101.com
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 3HR0Biv6pJq8
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 31 Aug 2021 19:47:06 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from mail-0201.mail-europe.com (mail-0201.mail-europe.com
[51.77.79.158])
by smtp1.osuosl.org (Postfix) with ESMTPS id 6787F82423
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 31 Aug 2021 19:47:06 +0000 (UTC)
Date: Tue, 31 Aug 2021 19:46:55 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=achow101.com;
s=protonmail; t=1630439217;
bh=tjr8hwgzVyQKavyFKJ4IGNqW2DkKP4fZLnXfMf+MIok=;
h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From;
b=yF5ONShx3FECAkGbI4XEjPZvulh9JjjGyJ8IRLiLa5t+u8iykfR+ojLnWfDKEqz0y
/sWmHY8R4wT2K75YVsnfNNhujtfakSaOLrcXUwN7ESKmQlax4sDiHcGgaGLrVP6DyO
2o6XCX86wEE6qnz6WtJmhzBdIA4WbnpnKDaX6VHsmU8xDLa8f/CI0nB+d8kiP5CK0B
pjcBRrV3Vj9kH6aYu6kibP5hW7SNeExgLDBJxtUn80wVe30sMnSN6W8P+DY0KtNRf3
htP2YnmfqQ4KtENOH1yiRm3qu6X3tAJYfF3xHpdUuS2A997DYW0ZksN/0n5lkWrwpx
brQL37yun93tA==
To: Peter Gray <peter@coinkite.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: Andrew Chow <achow101-lists@achow101.com>
Reply-To: Andrew Chow <achow101-lists@achow101.com>
Message-ID: <775f2a59-7cd7-6234-23d2-1780e2c4da58@achow101.com>
In-Reply-To: <20210831182741.GV91472@coinkite.com>
References: <mailman.9346.1630015566.1160.bitcoin-dev@lists.linuxfoundation.org>
<20210831182741.GV91472@coinkite.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] Proposal for a few IANA mime-types related to
Bitcoin
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2021 19:47:12 -0000
Hi Peter,
It would be nice to have mime types registered for Bitcoin things, but
I'm not sure that it will be possible, at least not in the way that we
would like. I tried doing this with "application/bitcoin-psbt" back in
2019 but it was not accepted. From that attempt, here is what I have
learned:
There are only a few accepted top level types, so we would not be able
to use "bitcoin" as the top level (unless you want to submit an RFC to
add a "bitcoin" top level). Of the available top level types,
"application" is the most appropriate for Bitcoin.
Next is the tree that the mime type should be in. The best would be the
Standards tree, but it has some requirements that Bitcoin doesn't really
meet. In order to be in the standards tree, the registration must be
either associated with an IETF specification (so a RFC) or registered by
a recognized standards related organization. Unfortunately the closest
thing to a standards organization that Bitcoin has is the BIPs process,
and that is not a really a standards organization nor is it recognized
by IANA. So in order to register the mimetypes as Standards tree types,
we would need to write an RFC, but this could be an independent
submission (https://www.rfc-editor.org/about/independent/) rather than
IETF-stream submission. I did not continue to pursue this because I
didn't have the time.
Another alternative would be to use the Vendor tree, but that would
prefix the mimetype with "vnd." so it would end up being something like
"application/vnd.bitcoin.psbt". I did not think this was an reasonable
so I did not continue to pursue this avenue.
Andrew Chow
On 8/31/21 2:27 PM, Peter D. Gray via bitcoin-dev wrote:
> Hi list!
>
> I am proposing to register the following MIME (RFC 2046) media types with=
the IANA:
>
>
> bitcoin/psbt
>
> - aka. a BIP-174 file, in binary
> - does not make any claims about signed/unsigned status; lets leave =
that to the file
>
> bitcoin/txn
>
> - aka. wire-ready fully-signed transaction in binary
>
> bitcoin/uri
>
> - aka [BIP-21](https://github.com/bitcoin/bips/blob/master/bip-0021.=
mediawiki)
> - could be just a bare bech32 or base58 payment address
> - but can also encode amount, comments in URL args
> - potentially interesting as a response to 402 - Payment required
>
>
> Other thoughts
>
> - some mime-types are proposed in BIP-71 but those are unrelated to above=
, and never
> seem to have been registered
>
> - for those who like to encode their binary as base64 or hex, that can be=
indicated
> as "encoding=3Dhex" or "encoding=3Dbase64" in the optional parameters,=
just like
> "text/plain; encoding=3Dutf-8" does. However, the default must be bina=
ry.
>
> - although the above are useful for web servers, they are also useful els=
ewhere and I
> intend to use them in NFC (NDEF records) where a shorter length is cri=
tical.
>
> - I have no idea how easily IANA will accept these proposals.
>
> - current approved mime types: https://www.iana.org/assignments/media-typ=
es/media-types.xhtml
>
> Thoughts?
>
> ---
> @DocHEX || Coinkite || PGP: A3A31BAD 5A2A5B10
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
