Re: Request for well-known URI: opendiscovery

Henrik Biering <hb@peercraft.com> Mon, 11 December 2017 08:23 UTC

Return-Path: <hb@peercraft.com>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469471286B1 for <wellknown-uri-review@ietfa.amsl.com>; Mon, 11 Dec 2017 00:23:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=peercraft.com header.b=K2tJXISq; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Sni8IYus
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 eYBXdVMOMq9N for <wellknown-uri-review@ietfa.amsl.com>; Mon, 11 Dec 2017 00:23:30 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31704126BF0 for <wellknown-uri-review@ietf.org>; Mon, 11 Dec 2017 00:23:30 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7846020A80; Mon, 11 Dec 2017 03:23:29 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Mon, 11 Dec 2017 03:23:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peercraft.com; h=cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=QHDJoudZGYrpXMz5fWef0Ir86ReGWYKgCabRKsyFo4E=; b=K2tJX ISqeOmhEwgibCgVXUX1lT2oXhAUFguBUH5IXxL4pRotyFuakyheIm6H4k6PjkaB/ AxSBFpcL1bNd3yFfMfM+0U2QISVmmdDn/p4EOdczMjdEqGqXkKAhIR+pwfp56eku IFmQSBR2BsCsFkbF2AvkGRdsGFDJXdnkkjcFSw=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=QHDJoudZGYrpXMz5fWef0Ir86ReGW YKgCabRKsyFo4E=; b=Sni8IYusnsaiwHMCZVc7xpAPVVLMmgY9asoJ6x5yvQHBn jTIMdJrp3kpsYDqtHAkPVQZwckCuC7Lcd0fo/q68QPnXmisQ/JDF1B8ymVql4P3g UxdDkHTRNLNCbE//dVwD1amzR3SW5QjhlwL24RZ3lTUVoyavNOpHnXkfWYkLYRvA EeVQ0ZjVQi/AolzxqcZsXOlVld0ZLzlf9coKh4Bheh7Ih9qi+SMkSCoBQncEVYxh MIX3cbHoO55V8cV/qGsc/9j266S9ZDjv47HigNUb5uaPaoV68c6lOp5E60cYPf27 PcyaZGPIR5wx9OIVMJkwngvSEZjIfRc9SfXCREOXg==
X-ME-Sender: <xms:gUAuWtmSsfjvzs6HJ50MsMdKfZ0qUrD9XkxKnHAQ5-rVgpWTDCuxug>
Received: from [192.168.0.2] (xd4ed86d1.cust.hiper.dk [212.237.134.209]) by mail.messagingengine.com (Postfix) with ESMTPA id 7F43C7E7D3; Mon, 11 Dec 2017 03:23:28 -0500 (EST)
Subject: Re: Request for well-known URI: opendiscovery
To: Mark Nottingham <mnot@mnot.net>
Cc: wellknown-uri-review@ietf.org
References: <4da0efc0-8d74-8bd7-d4fa-88011e43ace7@peercraft.com> <44104BC0-FB75-46C5-902D-88E0FEBF3DF1@mnot.net>
From: Henrik Biering <hb@peercraft.com>
Message-ID: <e48f25b7-d8db-ebde-643a-15e11bf90ccf@peercraft.com>
Date: Mon, 11 Dec 2017 09:23:33 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <44104BC0-FB75-46C5-902D-88E0FEBF3DF1@mnot.net>
Content-Type: multipart/alternative; boundary="------------83763429BFBC243403F165C3"
Content-Language: da
Archived-At: <https://mailarchive.ietf.org/arch/msg/wellknown-uri-review/urp6Af9yA-0kwMloDvSr-FMiPO8>
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wellknown-uri-review/>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Dec 2017 08:23:33 -0000

"Hi Mark,
thank you for your various comments and hints. And sorry for the equally 
late reply (we are also busy here). Our immediate impression is that 
there might be both advantages and disadvantages of using host-meta. We 
will return later, when we have had the time to work through a number of 
specific use cases and extend the specification."

Best,
Henrik

Den 21-11-2017 kl. 03:13 skrev Mark Nottingham:
> Hi Henrik,
>
> Sorry for the delay; IETF week (and the lead-up to it) tends to be 
> all-consuming.
>
> I see a couple of issues here:
>
> 1) As it is, the link you've provided isn't a sufficient reference; it 
> is required to be "in sufficient detail so that interoperability 
> between independent implementations is possible" 
> <https://tools.ietf.org/html/rfc8126#section-4.6>;. It also seems far 
> from "sufficiently stable and permanent" (ibid.).
>
> 2) As per RFC5785, Section 1.1 explains inappropriate use of 
> well-known URIs:
>
> """
> well-known URIs are not intended for general information retrieval or 
> establishment of large URI namespaces on the Web.  Rather, they are 
> designed to facilitate discovery of information on a site when it 
> isn't practical to use other mechanisms; for example, when discovering 
> policy that needs to be evaluated before a resource is accessed, or 
> when using multiple round-trips is judged detrimental to performance.
> """
>
> It's hard to tell because the vagueness of the specification, but it 
> seems like this mechanism is veering towards that. Have you explored 
> other mechanisms, such as host-meta <https://tools.ietf.org/html/rfc6415>?
>
> Cheers,
>
> P.S. I also see you're trying to use a HTTP header beginning with 
> "X-"; this practice is deprecated in 
> <https://tools.ietf.org/html/rfc6648>;.
>
>
>
> On 1 Nov 2017, at 4:30 am, Henrik Biering <hb@peercraft.com 
> <mailto:hb@peercraft.com>> wrote:
>
>> This is a request to register the well-known URI 
>> suffix “opendiscovery” allowing registered business entities to 
>> associate themselves with their online services and trusted third 
>> party claims, in order to make these easily discoverable without 
>> the need for a common third party.
>>
>> Presently the project is at the "Proof of Concept" stage with a basic 
>> preliminary specification, but we would like to have the suffix 
>> registered now as it reflects the project name and we are in talks 
>> with both interested user groups and public authorities on how to 
>> organize the further standardization and implementation efforts 
>> for various business purposes.
>>
>> The requested registry content is:
>>
>> URI suffix:
>> opendiscovery
>>
>> Change controller:
>> The OpenDiscovery Project
>> https://www.opendiscovery.biz/
>> info@opendiscovery.biz
>> +45 46 96 56 36
>> c/o Peercraft ApS, Aalandsgade 23, 2300 Copenhagen S, DENMARK
>>
>> Specification document:
>> https://www.opendiscovery.biz/specifications
>>
>> Related information:
>> https://www.opendiscovery.biz/
>> (Project website with links to background docs and Github repositories)
>> https://ec.europa.eu/futurium/en/blog/native-business-service-discovery-critical-issue-ngi
>> (Relevance to the upcoming EU Next Generation Internet 
>> efforts https://ec.europa.eu/futurium/en/node/1460)
>> -- 
>> On behalf of the Opendiscovery Project,
>> Henrik Biering
>> CEO
>> linkedin.com/in/hbiering
>>
>> Peercraft ApS
>> Aalandsgade 23
>> 2300 Copenhagen S
>> DENMARK
>>
>> www.peercraft.com
>> +45 46 96 56 36
>> hb@peercraft.com
>>
>>
>> _______________________________________________
>> wellknown-uri-review mailing list
>> wellknown-uri-review@ietf.org
>> https://www.ietf.org/mailman/listinfo/wellknown-uri-review
>
> --
> Mark Nottingham https://www.mnot.net/
>