[core] What do coap URIs mean
Jim Schaad <ietf@augustcellars.com> Sun, 08 December 2019 05:03 UTC
Return-Path: <ietf@augustcellars.com>
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 AEB4312003E for <core@ietfa.amsl.com>; Sat, 7 Dec 2019 21:03:07 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 gXlfS3haSg3l for <core@ietfa.amsl.com>; Sat, 7 Dec 2019 21:03:05 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D96A120033 for <core@ietf.org>; Sat, 7 Dec 2019 21:03:05 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 7 Dec 2019 21:02:59 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Klaus Hartke' <klaus.hartke@ericsson.com>, 'Carsten Bormann' <cabocabo@gmail.com>
CC: core@ietf.org
Date: Sat, 07 Dec 2019 21:02:58 -0800
Message-ID: <039101d5ad84$c3d656b0$4b830410$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdWtWgTMrYSayXktTNaOYW0MrHp1WQ==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/bx75nqbTbUJSvM28_ryJX9Lomcc>
Subject: [core] What do coap URIs mean
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 08 Dec 2019 05:03:08 -0000
I have been playing with the HREF and CoRAL documents and ended up with a question that I have no idea what the answer is. coap://host.example/a/b/c This URI represents a resource on the server that you can send a set of verbs to. Given that I represent resources in my implementation as a tree, this is an easy thing to describe and find. coap://host.example/a//b/c This URI is a bit strange, but again I can build this tree and be happy with receiving a verb addressed to that path. It is also something that appears to be totally legal based on the URI -> CoAP options algorithm. coap://host.example/a/b/c/ I don't know what this URI represents. Is this supposed to go to the same location as the first example above, or is it supposed to go to a resource with an empty name under c in my tree? Jim
- [core] What do coap URIs mean Jim Schaad
- Re: [core] What do coap URIs mean Carsten Bormann