[Din] Draft / Specification of the GNU Name System

"Schanzenbach, Martin" <schanzen@gnunet.org> Sun, 18 October 2020 13:13 UTC

Return-Path: <schanzen@gnunet.org>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B78B53A0AE0 for <din@ietfa.amsl.com>; Sun, 18 Oct 2020 06:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.974
X-Spam-Level:
X-Spam-Status: No, score=0.974 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wR5PYaxRVsAf for <din@ietfa.amsl.com>; Sun, 18 Oct 2020 06:13:20 -0700 (PDT)
Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AFED3A099F for <din@irtf.org>; Sun, 18 Oct 2020 06:13:20 -0700 (PDT)
Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id C7C7216005C for <din@irtf.org>; Sun, 18 Oct 2020 15:13:16 +0200 (CEST)
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4CDgLM5wZWz6tm6 for <din@irtf.org>; Sun, 18 Oct 2020 15:13:15 +0200 (CEST)
From: "Schanzenbach, Martin" <schanzen@gnunet.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_BC137694-CD47-4ACF-98C7-EE8DE424BF90"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Message-Id: <2E228AD3-F5C7-42A6-B59D-5D523E35E5B8@gnunet.org>
Date: Sun, 18 Oct 2020 15:13:14 +0200
To: din@irtf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/jkbYgEsyuZCknyYQxN-LxDtWpsY>
Subject: [Din] Draft / Specification of the GNU Name System
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Oct 2020 13:13:23 -0000

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] https://www.ietf.org/proceedings/104/slides/slides-104-dinrg-gnu-name-system-00.pdf
[2] https://datatracker.ietf.org/doc/draft-schanzen-gns/
[3] https://www.ietf.org/proceedings/108/agenda/agenda-108-secdispatch-02