1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
Return-Path: <ric@spagni.net>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 5EF5583D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Jul 2015 08:29:47 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vn0-f44.google.com (mail-vn0-f44.google.com
[209.85.216.44])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2DD027C
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Jul 2015 08:29:46 +0000 (UTC)
Received: by vnbg7 with SMTP id g7so271550vnb.12
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Jul 2015 01:29:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to
:content-type;
bh=YIMuKPJqczS0dAX/H/QdMmV/aP8jiwqw73CSsWvLDog=;
b=H3bLHrasKmrgxrJunjaMdmS4lv3X84iQauJf8J9PNj3iATwOIYL9mNkXpBa5FChSf0
mx3T2GmAySk+ehXZQ3zq5BjFhVf7qe3e2yC+R8dU5+Y9nS8wQPaHcZHfYix1wKxfpDwA
eMx6hLJbPi0t2nPPXiBxaEBBZU4dDu2yQEMv/HhKH/gJZG+yoSELOGsR0HFrPeTAwbwm
5Z9LIO49g39Y5tn6JyYGvQO6IfdBN0QUVW8c1rTc2j42On+x1CutRaJdpD4ZlJpdXiPW
ABWjU3OA4N93qTnNL73/C/mAmJ6w7RzJSB2bvVbBygT9RRaEDW4BmD5ELc6qtFx+7m1g
n+fw==
X-Gm-Message-State: ALoCoQk7CFjo7XYuAC1l+Rh00xw7O9KWgF8tnoDbLMedSqdjjZXBJl8jAjM8rHfxUPu2jmP+WWnX
X-Received: by 10.52.176.131 with SMTP id ci3mr34919428vdc.72.1436862585147;
Tue, 14 Jul 2015 01:29:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.92.197 with HTTP; Tue, 14 Jul 2015 01:29:25 -0700 (PDT)
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
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Proposal: extend bip70 with OpenAlias
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2015 08:29:47 -0000
--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'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'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's solution is incredibly limite=
d, it'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--
|