Re: [DNSOP] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 15 February 2019 09:37 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B3A130F82 for <dnsop@ietfa.amsl.com>; Fri, 15 Feb 2019 01:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 0ksjm6U3I3FX for <dnsop@ietfa.amsl.com>; Fri, 15 Feb 2019 01:37:16 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 5A5BB130F5F for <dnsop@ietf.org>; Fri, 15 Feb 2019 01:37:16 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id C301B2804E8; Fri, 15 Feb 2019 10:37:14 +0100 (CET)
Received: from relay01.prive.nic.fr (pa-th3.interco.nic.fr [192.134.4.74]) by mx4.nic.fr (Postfix) with ESMTP id BC94428047F; Fri, 15 Feb 2019 10:37:14 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id B8F7B6424E49; Fri, 15 Feb 2019 10:37:14 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id B1FD1401CB; Fri, 15 Feb 2019 10:37:14 +0100 (CET)
Date: Fri, 15 Feb 2019 10:37:14 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com>
Cc: IETF DNSOP WG <dnsop@ietf.org>, din@irtf.org
Message-ID: <20190215093714.t23ulbslbg52t2dp@nic.fr>
References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> <CAHXf=0r0DqC_XHw-2=h4ZkH5SgjzTjPMuML3GjxtQbe6so3=vw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHXf=0r0DqC_XHw-2=h4ZkH5SgjzTjPMuML3GjxtQbe6so3=vw@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 9.7
X-Kernel: Linux 4.9.0-8-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/a5Jx_6nbXPgb5y11yV0kmCUrpKs>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2019 09:37:18 -0000

On Fri, Feb 08, 2019 at 02:58:38PM +0100,
 Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com> wrote 
 a message of 59 lines which said:

> Feedback highly appreciated,

I think that it is an important work because it brings the power of
the DNS to many other identifier systems. So, I support it.

May be more examples could help people figure out the use cases? "My
Bitcoin address is at foobar.example" and then the Bitcoin software
would query _did.foobar.example and get
<did:bitcoin:1NZc7FJ7eHJgRMRSrmncJJM9bPnusJeuR6>.

I note that there exists already non-standard (and probably not really
deployed) solutions in that space, some specific to a TLD
<https://www.nominet.uk/domain-names-unlock-new-potential-on-blockchain/>
<http://domainincite.com/23273-my-brain-explodes-trying-to-understand-mmxs-new-blockchain-deal-for-luxe>

Regarding draft -01: it seems OK to me. The only problem I find:

> particularly the concerns around downgrade attacks when the record
> is not signed

Why downgrade attacks specifically? Without DNSSEC, a lot of attacks
are possible.