Post
๐Ÿ“… Original date posted:2015-07-23 ๐Ÿ“ Original message:Le 23/07/2015 11:48, Thomas Voegtlin via bitcoin-dev a รฉcrit : > > One benefit of having an intermediate "_wallet" level is to allow zone > delegation. Is that the reason for that choice? > 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 at 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 at example.com _btc.john._oa2.example.com <-- bitcoin address of john at example.com
0
๐Ÿ“… Original date posted:2015-07-27 ๐Ÿ“ Original message:Thomas, I think this is interesting and has some good thoughts behind it. For clarity, are you recommending that the "_oa2" portion of the domain name be "hidden" as a way to make it easier to delegate just wallet names from a zone? On Thu, Jul 23, 2015 at 6:07 AM, Thomas Voegtlin via bitcoin-dev < bitcoin-dev at lists.linuxfoundation.org> wrote: > Le 23/07/2015 11:48, Thomas Voegtlin via bitcoin-dev a รฉcrit : > > > > One benefit of having an intermediate "_wallet" level is to allow zone > > delegation. Is that the reason for that choice? > > > > 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 at 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 at example.com > _btc.john._oa2.example.com <-- bitcoin address of john at example.com > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev at lists.linuxfoundation.org > lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > -- Justin W. Newton Founder/CEO NetKi, Inc. justin at netki.com +1.818.261.4248 -------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150727/9f2e9f77/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 10972 bytes Desc: not available URL: <lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150727/9f2e9f77/attachment-0001.tiff>
0