MIME-Version: 1.0
References: <mailman.9346.1630015566.1160.bitcoin-dev@lists.linuxfoundation.org>
 <20210831182741.GV91472@coinkite.com>
In-Reply-To: <20210831182741.GV91472@coinkite.com>
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Tue, 31 Aug 2021 12:01:23 -0700
Message-ID: <CACrqygDZGWxrv+3w=gmwVRO4iTLYJnn8QLBEwNQ_EdkXNr46Ww@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 Peter Gray <peter@coinkite.com>, 
 Shannon Appelcline <shannon.appelcline@gmail.com>,
 Wolf McNally <wolf@wolfmcnally.com>
Content-Type: multipart/alternative; boundary="00000000000018f1d205cadf9462"
Subject: Re: [bitcoin-dev] Proposal for a few IANA mime-types related to
	Bitcoin
Precedence: list

--00000000000018f1d205cadf9462
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Note that a number of wallet companies are now supporting the UR encoded
version of PSBTs, allowing for better QR & Airgap solutions, and also
leverage CBOR which is an IETF standard.

We have a community of Airgap wallet developers at
https://github.com/BlockchainCommons/Airgapped-Wallet-Community

=E2=80=A6and libraries at
https://github.com/BlockchainCommons/crypto-commons#urs

We=E2=80=99d love for you to register UR as well, maybe as bitcoin/psbt+ur

Can you bring this up in our community for further discussion?
https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussions

Thanks!

=E2=80=94 Christopher Allen [via iPhone]

On Tue, Aug 31, 2021 at 11:41 AM Peter D. Gray via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> 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 binar=
y.
>
> - although the above are useful for web servers, they are also useful
> elsewhere and I
>   intend to use them in NFC (NDEF records) where a shorter length is
> critical.
>
> - I have no idea how easily IANA will accept these proposals.
>
> - current approved mime types:
> https://www.iana.org/assignments/media-types/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
>

--00000000000018f1d205cadf9462
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Note that a number of wallet companies are now supporting=
 the UR encoded version of PSBTs, allowing for better QR &amp; Airgap solut=
ions, and also leverage CBOR which is an IETF standard.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">We have a community of Airgap wallet develo=
pers at=C2=A0<div><a href=3D"https://github.com/BlockchainCommons/Airgapped=
-Wallet-Community">https://github.com/BlockchainCommons/Airgapped-Wallet-Co=
mmunity</a></div><div dir=3D"auto"><br></div><div dir=3D"auto">=E2=80=A6and=
 libraries at=C2=A0<div><a href=3D"https://github.com/BlockchainCommons/cry=
pto-commons#urs">https://github.com/BlockchainCommons/crypto-commons#urs</a=
></div><div dir=3D"auto"><br></div><div dir=3D"auto">We=E2=80=99d love for =
you to register UR as well, maybe as bitcoin/psbt+ur</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Can you bring this up in our community for fur=
ther discussion?=C2=A0<div><a href=3D"https://github.com/BlockchainCommons/=
Airgapped-Wallet-Community/discussions">https://github.com/BlockchainCommon=
s/Airgapped-Wallet-Community/discussions</a></div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto">Thanks!</div></div></div></div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">=E2=80=94 Christopher Allen [via iPhone]=C2=A0</div>=
<div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Tue, Aug 31, 2021 at 11:41 AM Peter D. Gray via bitcoin-dev &lt;<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfo=
undation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid=
;padding-left:1ex;border-left-color:rgb(204,204,204)">Hi list!<br>
<br>
I am proposing to register the following MIME (RFC 2046) media types with t=
he IANA:<br>
<br>
<br>
bitcoin/psbt<br>
<br>
=C2=A0 =C2=A0 - aka. a BIP-174 file, in binary<br>
=C2=A0 =C2=A0 - does not make any claims about signed/unsigned status; lets=
 leave that to the file<br>
<br>
bitcoin/txn<br>
<br>
=C2=A0 =C2=A0 - aka. wire-ready fully-signed transaction in binary<br>
<br>
bitcoin/uri<br>
<br>
=C2=A0 =C2=A0 - aka [BIP-21](<a href=3D"https://github.com/bitcoin/bips/blo=
b/master/bip-0021.mediawiki" rel=3D"noreferrer" target=3D"_blank">https://g=
ithub.com/bitcoin/bips/blob/master/bip-0021.mediawiki</a>)<br>
=C2=A0 =C2=A0 - could be just a bare bech32 or base58 payment address<br>
=C2=A0 =C2=A0 - but can also encode amount, comments in URL args<br>
=C2=A0 =C2=A0 - potentially interesting as a response to 402 - Payment requ=
ired<br>
<br>
<br>
Other thoughts<br>
<br>
- some mime-types are proposed in BIP-71 but those are unrelated to above, =
and never<br>
=C2=A0 seem to have been registered<br>
<br>
- for those who like to encode their binary as base64 or hex, that can be i=
ndicated<br>
=C2=A0 as &quot;encoding=3Dhex&quot; or &quot;encoding=3Dbase64&quot; in th=
e optional parameters, just like<br>
=C2=A0 &quot;text/plain; encoding=3Dutf-8&quot; does. However, the default =
must be binary.<br>
<br>
- although the above are useful for web servers, they are also useful elsew=
here and I<br>
=C2=A0 intend to use them in NFC (NDEF records) where a shorter length is c=
ritical.<br>
<br>
- I have no idea how easily IANA will accept these proposals.<br>
<br>
- current approved mime types: <a href=3D"https://www.iana.org/assignments/=
media-types/media-types.xhtml" rel=3D"noreferrer" target=3D"_blank">https:/=
/www.iana.org/assignments/media-types/media-types.xhtml</a><br>
<br>
Thoughts?<br>
<br>
---<br>
@DocHEX=C2=A0 ||=C2=A0 Coinkite=C2=A0 ||=C2=A0 PGP: A3A31BAD 5A2A5B10<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div>

--00000000000018f1d205cadf9462--