[core] resource-directory must implement lookup interface
Christian Amsüss <c.amsuess@energyharvesting.at> Thu, 08 June 2017 17:16 UTC
Return-Path: <c.amsuess@energyharvesting.at>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7B26129440 for <core@ietfa.amsl.com>; Thu, 8 Jun 2017 10:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 YR70ePZSjKzi for <core@ietfa.amsl.com>; Thu, 8 Jun 2017 10:16:26 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE9841293D9 for <core@ietf.org>; Thu, 8 Jun 2017 10:16:25 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 421A3471DF for <core@ietf.org>; Thu, 8 Jun 2017 19:16:24 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (poseidon-mailbox.amsuess.com [10.13.13.231]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 466D636 for <core@ietf.org>; Thu, 8 Jun 2017 19:16:23 +0200 (CEST)
Received: from hephaistos.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 19806389 for <core@ietf.org>; Thu, 8 Jun 2017 19:16:22 +0200 (CEST)
Received: (nullmailer pid 8171 invoked by uid 1000); Thu, 08 Jun 2017 17:16:22 -0000
Date: Thu, 08 Jun 2017 19:16:22 +0200
From: Christian Amsüss <c.amsuess@energyharvesting.at>
To: core@ietf.org
Message-ID: <20170608171622.ahh5gxh7bhsxzqwf@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="njnn7v2ljapi5ztu"
Content-Disposition: inline
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/V0VqYAbMMyW8fc4ceHOrqAOoclE>
Subject: [core] resource-directory must implement lookup interface
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jun 2017 17:16:28 -0000
Hello CoRE working group, in the development of the resource-directory draft, it is the authors' opinion that contrary to previous drafts, the lookup should not be an optional interface. Both "sides" of the resource directory are designed to be usable by constrained devices, are essential components of the RD when constrained nodes are supposed to interact with each other. Leaving lookup optional would lead to incompatibility between constrained nodes. Note that this would not mandate that all the information in the RD must actually be exposed; the lookup interface can (and actually SHOULD) be subject to access restrictions up to the extent of always presenting emtpy results to requesters. Please let us know if you know of good reasons not to do this change. Best regards Christian -- Christian Amsüss | Energy Harvesting Solutions GmbH founder, system architect | headquarter: mailto:c.amsuess@energyharvesting.at | Arbeitergasse 15, A-4400 Steyr tel:+43-664-97-90-6-39 | http://www.energyharvesting.at/ | ATU68476614
- [core] resource-directory must implement lookup i… Christian Amsüss