Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 01630C000E for ; Tue, 31 Aug 2021 19:01:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id D98978100B for ; Tue, 31 Aug 2021 19:01:40 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.402 X-Spam-Level: X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=lifewithalacrity-com.20150623.gappssmtp.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 9OHs4OswopTQ for ; Tue, 31 Aug 2021 19:01:36 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) by smtp1.osuosl.org (Postfix) with ESMTPS id 5B68280F4B for ; Tue, 31 Aug 2021 19:01:36 +0000 (UTC) Received: by mail-vk1-xa32.google.com with SMTP id g34so150324vkd.11 for ; Tue, 31 Aug 2021 12:01:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lifewithalacrity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=d+cJn3jsXl1LPwTdm8h4Qskq5AwUWU03jCwUU4l1gio=; b=1CtcbsMHLfx0YBMn6/GryahQ286Nev2g+ekuOdu3/LGU9TqRDDx79RYDrQcrsxvPQj vHG2FgExfsEUtD0AfUdB0iXIIRIZbHC5sPV+ypgywMCjARDhTVZ9OrMfSxj5G2VTbMr9 9ydBHEwEYNYPCbLZwTVni3rgs8HKkN4+Lq4aW58edIPUsYAWWH99f56m/tsDliICoCw6 o1098/oNwQjHWOlIEHmVr/YG5dLCljS2V4bfLHit5ILJWUXsweJ335FBPUsEUO+JCcJI s4bNI/FG5kG6MDNRuzaaOcPhdmFqJGVH52P89MYSua1Zmz9AT8y19kkYY/E3k48lMWH1 FI6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=d+cJn3jsXl1LPwTdm8h4Qskq5AwUWU03jCwUU4l1gio=; b=PVno5eUdIAyZ8nLX+NIvUqAjNfO8CyDVbDrnKAOlISF8HJbiOm2ijk3wcwE7srdyYy zVzi+CaamUFDsQ6z3Gden/lxPQHfIKRTk92/0gnq13tzfV6Jy+tSuR7aarZ1RRTxeAde Hf/gVAIyAUleVm2IwLH976Y0sBMLuS9MdsZQcjZjX8gY2hta56rNpYia9RjVJGQvd9Vr r+BISWcehOULQs2edeWq6niCCfwjJrqTg5jpHChX3JG3K9mpdlWBpA7K6glU9gAa0kUc /Ouo52vcoLbY0x7n0WklqDEsOr+2IMVnGZD9uO6NaydOI3SpBlHNLbYyn2lvD8E5uXmZ mCZA== X-Gm-Message-State: AOAM533qaJ/2CPh8cbSojeRUZOnEtx75bUDyR3T3V5b9Axta537Snlks zNtBScq4BvBa4HbiLBxhp0CFBoNnq4VNVtXiCy2EQD7gEAk= X-Google-Smtp-Source: ABdhPJykGODKCTpE7JQCQ6DkUgPI9EtvP6b2YYGsHBt+bJ5AI5ex1ocpsLwPZ0541UGMHHu/gX3/xKthohF0wIVXVhM= X-Received: by 2002:a1f:3215:: with SMTP id y21mr19129930vky.13.1630436494732; Tue, 31 Aug 2021 12:01:34 -0700 (PDT) MIME-Version: 1.0 References: <20210831182741.GV91472@coinkite.com> In-Reply-To: <20210831182741.GV91472@coinkite.com> From: Christopher Allen Date: Tue, 31 Aug 2021 12:01:23 -0700 Message-ID: To: Bitcoin Protocol Discussion , Peter Gray , Shannon Appelcline , Wolf McNally Content-Type: multipart/alternative; boundary="00000000000018f1d205cadf9462" X-Mailman-Approved-At: Tue, 31 Aug 2021 22:12:22 +0000 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2021 19:01:41 -0000 --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
Note that a number of wallet companies are now supporting= the UR encoded version of PSBTs, allowing for better QR & Airgap solut= ions, and also leverage CBOR which is an IETF standard.

We have a community of Airgap wallet develo= pers at=C2=A0


<= /div>
=E2=80=94 Christopher Allen [via iPhone]=C2=A0
=

O= n Tue, Aug 31, 2021 at 11:41 AM Peter D. Gray via bitcoin-dev <bitcoin-dev@lists.linuxfo= undation.org> wrote:
Hi list!

I am proposing to register the following MIME (RFC 2046) media types with t= he IANA:


bitcoin/psbt

=C2=A0 =C2=A0 - aka. a BIP-174 file, in binary
=C2=A0 =C2=A0 - does not make any claims about signed/unsigned status; lets= leave that to the file

bitcoin/txn

=C2=A0 =C2=A0 - aka. wire-ready fully-signed transaction in binary

bitcoin/uri

=C2=A0 =C2=A0 - aka [BIP-21](https://g= ithub.com/bitcoin/bips/blob/master/bip-0021.mediawiki)
=C2=A0 =C2=A0 - could be just a bare bech32 or base58 payment address
=C2=A0 =C2=A0 - but can also encode amount, comments in URL args
=C2=A0 =C2=A0 - potentially interesting as a response to 402 - Payment requ= ired


Other thoughts

- some mime-types are proposed in BIP-71 but those are unrelated to above, = and never
=C2=A0 seem to have been registered

- for those who like to encode their binary as base64 or hex, that can be i= ndicated
=C2=A0 as "encoding=3Dhex" or "encoding=3Dbase64" in th= e optional parameters, just like
=C2=A0 "text/plain; encoding=3Dutf-8" does. However, the default = must be binary.

- although the above are useful for web servers, they are also useful elsew= here and I
=C2=A0 intend to use them in NFC (NDEF records) where a shorter length is c= ritical.

- 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=C2=A0 ||=C2=A0 Coinkite=C2=A0 ||=C2=A0 PGP: A3A31BAD 5A2A5B10

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--00000000000018f1d205cadf9462--