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

Alexander Mayrhofer <> Mon, 18 February 2019 14:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B2D8B130F0D for <>; Mon, 18 Feb 2019 06:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iWnZg3SB3X9k for <>; Mon, 18 Feb 2019 06:17:50 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BDDE112941A for <>; Mon, 18 Feb 2019 06:17:49 -0800 (PST)
Received: by with SMTP id e27so12409980lfj.8 for <>; Mon, 18 Feb 2019 06:17:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RLXbrScUAcZewqf8p39g2s4DCxgAmtLGF9pvUUvJuwE=; b=jgo0LEvk6tUBepJ4OkrNcd4zS/0HUrDFS+Rlew37qqz4ttZx8IYXbiNHFhPx/oEXM1 KZjgQnvsFmWWPa5d+0dc1FU3wBWIyDofKWiNhxM9zzbZF3FWFkiR+HtpY+O7kQrx1yOW vaGGAKiSDtuOTPyy7nP4gDO2Ha3tBJ/fZ6ihx55IbkPCGccnBt9DEAR6vrdCzfs64LUW r6gv9K2sz/fC3K+b+sDk0oiIcFMLt4fk0KFWCx1NI1Syz+6qbcNNyOfH4V9es6DbchcR DkcxNN4X7pDfbAxdL5wYqIWCEQgG3It0SVmdofQP0HBWb1GEvWGE2xTILbA7naDSe5gG r4Ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RLXbrScUAcZewqf8p39g2s4DCxgAmtLGF9pvUUvJuwE=; b=fqBvCuIAjdnVwKucFxwQFmE2I258q4wxeGV+kBpKqm3nY9gqYQrvhOOI0dIZeLuhCU TtausIHEz48kYbRSlTDW/GMilKLlMYoh33lp7RFupnFjplcB7/4umN35If1qt0ZSJHZq dYrayhtxSFND0+CJgSBFtK6Mhws1UdWaqOme72K5BfppuoQXPfv/lEX31WvSaL1SJY2J cZ+rjubePZtK2feDD24QZwoHVArYpmEQlSuT9zJxMr0ZYsi7YUunec1u9bBIMDoYjS0H 0VAzNy4UKR3Sh0uZMMem9englYBZwP0gza2+lpry2BxcagbzonC+4GagO2jSCgHDuEuh u5MQ==
X-Gm-Message-State: AHQUAuYA1dEGPhu6VQJJsRtOZu7VqIXmGQHGTzGUo+d10L2TDrilQSF2 jy8j+I1HNR/nbbo1VBl14JtRq5W4RnxW68smXhU=
X-Google-Smtp-Source: AHgI3Iakqn8kL7je65jDGO9TXMqXiIMEhMQoHPfaUFzP1Ni2jINSEFvel0zdMWTXsaq8wi4UnIf+oGe7jv6WLpb6FNs=
X-Received: by 2002:a19:7406:: with SMTP id v6mr321865lfe.33.1550499467974; Mon, 18 Feb 2019 06:17:47 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <>
In-Reply-To: <>
From: Alexander Mayrhofer <>
Date: Mon, 18 Feb 2019 15:17:37 +0100
Message-ID: <>
To: Melinda Shore <>
Cc: Paul Wouters <>, Stephane Bortzmeyer <>, IETF DNSOP WG <>,
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt
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: Mon, 18 Feb 2019 14:17:53 -0000

On Fri, Feb 15, 2019 at 8:47 PM Melinda Shore
<> wrote:
> I think the question of whether or not to provide
> decentralized identifiers and whether or not this proposal
> delivers on the "decentralized" claim is out of our hands,
> as the core spec (which has a lot of additional problems)
> comes out of the W3C.  I think the IETF's involvement is
> probably limited to their use of DNS in the resolution
> process.

I do agree. We provide the "link" from an IETF protocol to a protocol
developed in another SDO.

> p.s. and it's probably worth pointing out that this work is
> being done in a W3C community group, so until it looks like
> it's actually going to be published as a WC3 spec I'm not
> sure I'd like to see IETF working group resources being
> spent on this.

Yes, exactly, this is a community group work right now. However, i do
understand that the "upgrade" to a working group is currently