Re: [Uri-review] Fwd: Registration request: did URI scheme

Manu Sporny <msporny@digitalbazaar.com> Mon, 14 May 2018 15:33 UTC

Return-Path: <msporny@digitalbazaar.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 853DE12D952 for <uri-review@ietfa.amsl.com>; Mon, 14 May 2018 08:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 1mKY8_DskoEY for <uri-review@ietfa.amsl.com>; Mon, 14 May 2018 08:33:32 -0700 (PDT)
Received: from mail.digitalbazaar.com (mail.digitalbazaar.com [96.89.14.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B428126BF7 for <uri-review@ietf.org>; Mon, 14 May 2018 08:33:32 -0700 (PDT)
Received: from [192.168.0.149] by mail.digitalbazaar.com with esmtp (Exim 4.86) (envelope-from <msporny@digitalbazaar.com>) id 1fIFTd-0004iu-Aj; Mon, 14 May 2018 11:33:29 -0400
To: Graham Klyne <gk@ninebynine.org>, uri-review@ietf.org
Cc: Graham Klyne <gklyne@gmail.com>
References: <c7b3123a-f5db-d365-3bc7-31fd6d11eaa3@digitalbazaar.com> <cd5cb373-7bd8-e0c7-ba6d-a293562589f3@digitalbazaar.com> <5AF9A5C3.7010307@ninebynine.org>
From: Manu Sporny <msporny@digitalbazaar.com>
X-Opacus-Archived: none
Message-ID: <9e5d4e01-6b79-7390-fa61-5efd47f28303@digitalbazaar.com>
Date: Mon, 14 May 2018 11:33:29 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5AF9A5C3.7010307@ninebynine.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-CA
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 192.168.0.149
X-SA-Exim-Mail-From: msporny@digitalbazaar.com
X-SA-Exim-Scanned: No (on mail.digitalbazaar.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/va6-40E6akp__bBuuz6CMRzQXRo>
Subject: Re: [Uri-review] Fwd: Registration request: did URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2018 15:33:34 -0000

On 05/14/2018 11:05 AM, Graham Klyne wrote:
> I think the issue might be titled something like: "Allow DID 
> documents to be retrieved using any URI scheme".

Ok, I understand the point you're making now. I've created a new issue
to track this here:

https://github.com/w3c-ccg/did-spec/issues/84

... and will track the discussion there.

> Rather, a generally preferred approach is to dereference the URI and
>  examine the content-type of what is returned.

What happens if the protocol you're using to resolve the identifier
doesn't provide a content-type in return? We have a couple of DID
Resolvers that might never return content-types (Bitcoin and Ethereum
come to mind). I guess we could require that all Resolvers return
content-types... but given the absence of a content-type, the front part
of the URI "did" provides all the information you need to process the
document.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches
https://tinyurl.com/veres-one-launches