Message-ID: <55B0E719.4030004@electrum.org>
Date: Thu, 23 Jul 2015 15:07:37 +0200
From: Thomas Voegtlin <thomasv@electrum.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bitcoin-dev@lists.linuxfoundation.org
References: <CADhj2oT_rgaf6LFgwMawwJKaA8384v5jQ=e-7T8GNY4gGZ2udQ@mail.gmail.com>	<CABqynxKf=xBOG_38LYqtps2jXWeOR3g4PVFm6AKbJKLndG3Tig@mail.gmail.com>	<CABqynxL5AhEPLSw8TYjn9CVTc42+OHihKPGY6X3GP5W6u6TZaQ@mail.gmail.com>
	<55B0B858.8000106@electrum.org>
In-Reply-To: <55B0B858.8000106@electrum.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] Proposal: extend bip70 with OpenAlias
Precedence: list

Le 23/07/2015 11:48, Thomas Voegtlin via bitcoin-dev a =E9crit :
>=20
> One benefit of having an intermediate "_wallet" level is to allow zone
> delegation. Is that the reason for that choice?
>=20

Thinking about it, I think that it would be better to separate those two
operations: on one hand, the listing of TXT records under a name, and on
the other hand, the possibility to use Zone Delegation.

For example, let us use the "_oa2" name (Openalias version 2) when we
need to introduce an intermediate level, and "_oa2_keys" for key listing.

Here is an example:

_oa2_keys.sample      3600 IN TXT "btc ltc email fullname"
_btc.sample           3600 IN TXT "bitcoinaddress"
_ltc.sample           3600 IN TXT "litecoinaddress"
_btc.sample           3600 IN TXT "otherbitcoinaddress"
_email.sample         3600 IN TXT "john.smith@googlemail.com"
_fullname.sample      3600 IN TXT "John Smith"

Zone Delegation: Let us assume example.com wants to delegate all its
Bitcoin aliases to Netki. We introduce an intermediate level, with the
"_oa2" name. In the alias, this string is translated as "@"

john._oa2.example.com        <--  will be looked up as john@example.com
_btc.john._oa2.example.com   <--  bitcoin address of john@example.com