Re: [Din] Draft / Specification of the GNU Name System

Dirk Kutscher <> Tue, 08 December 2020 20:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2CCB83A11BA for <>; Tue, 8 Dec 2020 12:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iuN1Cuq8vTF6 for <>; Tue, 8 Dec 2020 12:02:12 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8EADD3A1375 for <>; Tue, 8 Dec 2020 12:01:28 -0800 (PST)
Received: from [] ([]) by (mreue109 []) with ESMTPSA (Nemesis) id 1MvbO4-1ju4ov3cU2-00shNV; Tue, 08 Dec 2020 21:01:23 +0100
From: "Dirk Kutscher" <>
To: "Martin Schanzenbach" <>
Date: Tue, 08 Dec 2020 21:01:23 +0100
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <>
In-Reply-To: <>
References: <> <>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:JSNBGtmCqvDAgOabP5SXUfTBVcXoaNKIweflnw3ZU3kIfEFKQOL dbCxNrn+um9ELRNS3r0TrNdr1kRAl54MYbstWhZYj3vYuGR5CR9XXCh1eO+/mFFtO7RsNMV DlcSAPcHgAzYtL9KGpaKOuKwit2U2lMJvvpYTk/lJLVSlGgSJODh5Ble9hpbTJqxq9bBEnc 9jvQsR93S9CRFt7YtwcHg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:NW8qJVuxhqs=:8pM414lAtsxfEXca2DmVFK bFXAaHMfKJD6HBjDmYzCOH79M3QSs7STZNf1U7iyttg3BkcAFwKER7EBIedsGOmS4hhfDbxlq QFA4GKi5Y64y5UK926mGVwsAZZV0KUsoiXlh1gBx3Qbjw9L27R60303zwxwrkCxr4aTRsP2Gr wJBjDQaSQh+bt7XM0tz2YnHTggEkibISXhn/o3RUSQV7d8iVY0Wm25XznWir7ORMZDVAFBpBa L+n6dBkGc3/MRIY+5lKwTOzRwqpzyT1eaFgrtH99Od0Z7GuhpDw2CbDkLcjzoZHOUS4+S2aw5 miDiDFjetSxMWc0JhJwESHDHiLsLOgw73tcvQ5mREB3DUqVUYUVAOyBnP9NbIsa8CwOyFK+VC W8sX95HiCpJry566HtbLkWu8Syw6Ts32V1eic701W4gjg7Nqjkh046lti4zQuYQuROjjVP9Mw 17xneXPWgA==
Archived-At: <>
Subject: Re: [Din] Draft / Specification of the GNU Name System
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 08 Dec 2020 20:02:14 -0000

Hi Martin,

> we wanted to check back with you if it makes sense to coordinate next
> week at IETF 109. It seems as if dinrg is not (yet) listed on the
> agenda?
> According to the minutes of IETF 108, the next steps would involve
> coordination/deconflicting with DINRG:

thanks for bringing this up and apologies for the late reply.

We didn't meet around IETF-109.

This is definitely an interesting topic for DINRG, and we should talk 
about it at an upcoming meetings.

We are currently planning upcoming meetings etc., and we should have a 
more concrete plan for early 2021 activities after new year.

In the meantime, please feel free to use the mailing list as well.


> Best Regards
> Martin
> On Sun, 2020-10-18 at 15:13 +0200, Schanzenbach, Martin wrote:
>> Dear DINRG,
>> at IETF 104, we have presented to you our work on the GNU Name System
>> [1].
>> Since then, we have been working on improvements and a technical
>> specification of the system [2].
>> At IETF 108, we appeared at secdispatch in order to discuss if the
>> draft may fit into any existing WG in IETF (or IRTF) [3].
>> We were encouraged to ask DINRG if it would be interested in this
>> work and continue improving and working on it (see minutes of
>> secdispatch). Your charter would certainly support the general theme
>> of the protocol: "The evolution of distributed ledger technologies
>> and the platforms that leverage them has given rise to the
>> development of decentralized communication and infrastructure
>> systems, and experiments with the same. Some examples include name
>> resolution (Namecoin, Ethereum Name Service), identity management
>> (OneName), distributed storage (IPFS, MaidSafe), distributed
>> applications, or DApps (Blockstack), and IP address allocation and
>> delegation."
>> Since our appearance at secdispatch, we have received a lot of
>> feedback from the community and experts. We have taken the time to
>> incorporate the feedback and the result is in the current version of
>> the draft as well as our implementation.
>> As you can see, the draft versions 01 and 02 differ significantly.
>> The two major changes regarding the protocol that we have made are:
>> 1. Improve crypto agility: Allow other zone key types and key
>> derivation schemes and define the required properties.
>> 2. Improve crypto implementation: The used symmetric encryption
>> scheme has been replaced to be more resilient to IND-CCA
>> For (1.) we have drafted an alternative scheme based on Schnorr
>> signatures. This instantiation is still a draft and not implemented.
>> Any feedback here is specifically welcomed and helpful.
>> Finally, we would be happy to appear at the next IETF and discuss
>> whether DINRG would be a place to continue our work with you.
>> Best
>> Martin
>> [1]
>> [2]
>> [3]
> _______________________________________________
> Din mailing list