MIME-Version: 1.0
From: Riccardo Spagni <ric@spagni.net>
Date: Tue, 14 Jul 2015 10:29:25 +0200
Message-ID: <CADhj2oRP+mMKb9QynLzRivKc6Rfc-gZrtCEPKVnY9Lwpt5XmCQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=bcaec5196a6ffaaa90051ad1a3db
Subject: Re: [bitcoin-dev] Proposal: extend bip70 with OpenAlias
Precedence: list

--bcaec5196a6ffaaa90051ad1a3db
Content-Type: text/plain; charset=UTF-8

Hi Mike,

FYI there is a company called Netki is also working on a kind of DNSSEC
> integration with BIP70, there's a thread here about their efforts:
>
>
>
> https://groups.google.com/forum/#!searchin/bitcoinj/dnssec/bitcoinj/QFAH1F2dEwE/36oWDwREEV4J
>
> If you would like to work on this, perhaps it's worth teaming up with them?
> Obviously they plan to have an open spec and open source implementation.
>

Netki's solution is incredibly limited, it's a single return value and no
metadata (where OA encapsulates metadata in KV pairs). This does not lend
itself well to handling BIP70-style communication.

As an aside, they also seem to have a complete disregard for lookup
privacy, which we address in OpenAlias by means of DNSCrypt encrypted
lookups. To that end we have even written the first independent DNSCrypt
implementation (ie. over-and-above dnscrypt-proxy) which provides a full
Python implementation that uses libsodium / nacl if available, but falls
back to a 100% Python slownacl implementation:
https://github.com/openalias/dnscrypt-python

Riccardo

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

<div dir=3D"ltr">Hi Mike,<div><br><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-=
style:solid;padding-left:1ex">
FYI there is a company called Netki is also working on a kind of DNSSEC<br>
integration with BIP70, there&#39;s a thread here about their efforts:<br>
<br>
<br>
<a href=3D"https://groups.google.com/forum/#!searchin/bitcoinj/dnssec/bitco=
inj/QFAH1F2dEwE/36oWDwREEV4J" rel=3D"noreferrer" target=3D"_blank">https://=
groups.google.com/forum/#!searchin/bitcoinj/dnssec/bitcoinj/QFAH1F2dEwE/36o=
WDwREEV4J</a><br>
<br>
If you would like to work on this, perhaps it&#39;s worth teaming up with t=
hem?<br>
Obviously they plan to have an open spec and open source implementation.<br=
></blockquote><div><br></div><div>Netki&#39;s solution is incredibly limite=
d, it&#39;s a single return value and no metadata (where OA encapsulates me=
tadata in KV pairs). This does not lend itself well to handling BIP70-style=
 communication.</div><div><br></div><div>As an aside, they also seem to hav=
e a complete disregard for lookup privacy, which we address in OpenAlias by=
 means of DNSCrypt encrypted lookups. To that end we have even written the =
first independent DNSCrypt implementation (ie. over-and-above dnscrypt-prox=
y) which provides a full Python implementation that uses libsodium / nacl i=
f available, but falls back to a 100% Python slownacl implementation:=C2=A0=
<a href=3D"https://github.com/openalias/dnscrypt-python">https://github.com=
/openalias/dnscrypt-python</a></div><div><br></div><div>Riccardo</div></div=
></div></div></div>

--bcaec5196a6ffaaa90051ad1a3db--