Re: [core] Report on first Resource Directory plugtest

Christian M. Amsüss <christian@amsuess.com> Tue, 17 April 2018 15:26 UTC

Return-Path: <christian@amsuess.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 6D41C12D955 for <core@ietfa.amsl.com>; Tue, 17 Apr 2018 08:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.921
X-Spam-Level:
X-Spam-Status: No, score=-0.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979] 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 Fqu3A_Dh3c6q for <core@ietfa.amsl.com>; Tue, 17 Apr 2018 08:26:05 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 655F112D953 for <core@ietf.org>; Tue, 17 Apr 2018 08:26:05 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 7CACC497AB; Tue, 17 Apr 2018 17:26:02 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 5E7566F; Tue, 17 Apr 2018 17:26:01 +0200 (CEST)
Received: from hephaistos.amsuess.com (hephaistos.amsuess.com [IPv6:2a02:b18:c13b:8010::db8]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 13F1831; Tue, 17 Apr 2018 17:26:01 +0200 (CEST)
Received: (nullmailer pid 22057 invoked by uid 1000); Tue, 17 Apr 2018 15:25:59 -0000
Date: Tue, 17 Apr 2018 17:25:59 +0200
From: "Christian M. Amsüss" <christian@amsuess.com>
To: Jim Schaad <ietf@augustcellars.com>
Cc: 'Carsten Bormann' <cabo@tzi.org>, 'peter van der Stok' <consultancy@vanderstok.org>, 'Core WG mailing list' <core@ietf.org>
Message-ID: <20180417152558.GA18144@hephaistos.amsuess.com>
References: <20180413110301.GL18144@hephaistos.amsuess.com> <29B20CA2-4179-4BBA-A0A7-5365C5A2BE85@tzi.org> <011501d3d4ea$384220d0$a8c66270$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Z83JOb+Pp/DrQW9p"
Content-Disposition: inline
In-Reply-To: <011501d3d4ea$384220d0$a8c66270$@augustcellars.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/_iNK2CFnpy2P4H-MMEm_mjMpytk>
Subject: Re: [core] Report on first Resource Directory plugtest
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: Tue, 17 Apr 2018 15:26:08 -0000

On Sun, Apr 15, 2018 at 11:47:32AM -0700, Jim Schaad wrote:
> Carsten Bormann wrote:
> > We could also use formal URI templates and just say that they are to be
> > interpreted in the sensible way described above.
> > 
> > (I’m not a fan of RFC 6570 URI templates at all, because the approach is full of
> > brokenness of the kind you describe(*); but it was available at the time…)
> 
> I would agree that I would not have read this as needing to have two
> "?" characters in the query parameters.  My issue is that I worry
> about the case that an RD decides to use foo=XXX as the location query
> and then some application decides to use foo as a query parameter in
> the extra parameters or in a link description.  This works fine on RD
> implementation #1 because it is just using a location path to point to
> the end point, but when it hits RD implementation #2 which is using
> the location query as well it starts failing.  

There would not be a conflict with use in links descriptions, but still
would be with extra parameters in a registration update.

On those grounds I'll propose a text to rule out query parameters.

Thanks
Christian

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom