Re: [core] Review comments on draft-ietf-core-coap-pubsub-05
Klaus Hartke <hartke@projectcool.de> Sun, 22 July 2018 20:47 UTC
Return-Path: <hartke@projectcool.de>
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 DC69E130E11; Sun, 22 Jul 2018 13:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001] autolearn=no 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 bLo-Ynlcw8LN; Sun, 22 Jul 2018 13:47:55 -0700 (PDT)
Received: from wp382.webpack.hosteurope.de (wp382.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8597::]) (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 A4BAB130DCE; Sun, 22 Jul 2018 13:47:55 -0700 (PDT)
Received: from mail-qt0-f173.google.com ([209.85.216.173]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1fhLGh-0006VH-P5; Sun, 22 Jul 2018 22:47:51 +0200
Received: by mail-qt0-f173.google.com with SMTP id a5-v6so14781761qtp.2; Sun, 22 Jul 2018 13:47:51 -0700 (PDT)
X-Gm-Message-State: AOUpUlHyfyzQoppZWypMr5flfQS6XwijT2i44qGRHn93PlsNo1M36rXA IHEAXWQN4zRTGklJXVbZyCF+Jxs2+zFqPO6O7pc=
X-Google-Smtp-Source: AAOMgpdaLgd4tcx7l8PRpcvpoRwOyGO44Dbbk/tEDBj96DlW5q0a9jRrhFPxY99cVeugNHUubNfKMO/7a1e4pKhYoSE=
X-Received: by 2002:a0c:f643:: with SMTP id s3-v6mr8904773qvm.131.1532292470736; Sun, 22 Jul 2018 13:47:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a0c:d04c:0:0:0:0:0 with HTTP; Sun, 22 Jul 2018 13:47:10 -0700 (PDT)
In-Reply-To: <00f901d421f8$3f6310d0$be293270$@augustcellars.com>
References: <00f901d421f8$3f6310d0$be293270$@augustcellars.com>
From: Klaus Hartke <hartke@projectcool.de>
Date: Sun, 22 Jul 2018 22:47:10 +0200
X-Gmail-Original-Message-ID: <CAAzbHvYSvQ=2_NxVuP_RkQf-a3AToegw-fxzrt8WLspKG2zD-A@mail.gmail.com>
Message-ID: <CAAzbHvYSvQ=2_NxVuP_RkQf-a3AToegw-fxzrt8WLspKG2zD-A@mail.gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
Cc: draft-ietf-core-coap-pubsub@ietf.org, Core <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1532292475; 49a9a1a2;
X-HE-SMSGID: 1fhLGh-0006VH-P5
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/8GaJnJjyYp5eSOer8570Ugg2n4M>
Subject: Re: [core] Review comments on draft-ietf-core-coap-pubsub-05
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
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, 22 Jul 2018 20:47:58 -0000
Jim Schaad wrote: > 1. Welcome to the world of how CoAP defined resolving of URIs. RFC 6690 > either did not do a good job of explaining things or got them wrong. There > is a special case for /.well-known/core in terms of how the resolution of > links are done. As I understand things if you do this > > GET /ps?rt="temperature" > > And get back in the content > > </ps/currentTemp>;rt="temperature";ct=50 > > When you ask for the resource you will look in the following address > > GET /ps/ps/currentTemp Is this really true? I didn't read RFC 6690 for a very long time, but this would be really surprising. From a quick glance at RFCs 6690/3986/6454 I would assume the following: * Reference resolution has two inputs: a URI reference to resolve and a base URI [RFC 3986, Section 5.2]. * Since the above link does not have an anchor parameter, the base URI is the origin of the target URI [RFC 6690, Section 2.1]. * Assuming the target URI is <coap://example.com/ps?rt="temperature">, then the origin of the target URI is the triple ("coap", "example.com", 5683) [RFC 6454, Section 4]. * This presumably means that the base URI is <coap://example.com:5683/> [??]. * Resolving </ps/currentTemp> against <coap://example.com:5683/> results in <coap://example.com:5683/ps/currentTemp> [RFC 3986, Section 5.2]. Klaus
- [core] Review comments on draft-ietf-core-coap-pu… Jim Schaad
- Re: [core] Review comments on draft-ietf-core-coa… Klaus Hartke