IETF Logo Mail Archive

Re: [core] ue of resource type in collections

Klaus Hartke <klaus.hartke@ericsson.com> Thu, 19 July 2018 14:14 UTC

Return-Path: <klaus.hartke@ericsson.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 05B06130F06 for <core@ietfa.amsl.com>; Thu, 19 Jul 2018 07:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 lBE2oPrBimHO for <core@ietfa.amsl.com>; Thu, 19 Jul 2018 07:13:56 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FEEF130F52 for <core@ietf.org>; Thu, 19 Jul 2018 07:13:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1532009634; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=09WM8orWeqWh8xhjDo/UEZGKtO8ucyoG9il7mT2vSxs=; b=L19pKuX5ercHkwqFcbMZEQeH/gFGuIaVRdWX/v/imBQdR0PTU/hD/RdC3HSRvEB4 3JHnvRpVnD/8sddcQepMPjZBFz7ImAA4QASoLmqiWYRj619zVv4z+CbCW1VBLd/q N8kppPGJQUC0KoCWB1RQyc1gGmt9wHKz0rxVMXqS5NQ=;
X-AuditID: c1b4fb2d-20bff700000055ff-78-5b509ca2e292
Received: from ESESBMB502.ericsson.se (Unknown_Domain [153.88.183.115]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id CC.78.22015.2AC905B5; Thu, 19 Jul 2018 16:13:54 +0200 (CEST)
Received: from ESESSMB502.ericsson.se (153.88.183.163) by ESESBMB502.ericsson.se (153.88.183.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Thu, 19 Jul 2018 16:13:54 +0200
Received: from ESESSMB502.ericsson.se ([153.88.183.190]) by ESESSMB502.ericsson.se ([153.88.183.190]) with mapi id 15.01.1466.003; Thu, 19 Jul 2018 16:13:54 +0200
From: Klaus Hartke <klaus.hartke@ericsson.com>
To: Michel Veillette <Michel.Veillette@trilliant.com>, "consultancy@vanderstok.org" <consultancy@vanderstok.org>, Core <core@ietf.org>
Thread-Topic: [core] ue of resource type in collections
Thread-Index: AQHUF1wyuOvf++gaV0iTcZ7wQsQKq6SVD5AggAFwU4CAACJd8A==
Date: Thu, 19 Jul 2018 14:13:53 +0000
Message-ID: <83b6eff6240048c7a4cb71b5f0a6ddfc@ericsson.com>
References: <018f504348d7d168df65951dae5a44a4@bbhmail.nl> <8a5f01b18f574ed6a6724dc49e4e47e6@ericsson.com> <DM5PR06MB27776B4DBBE95A286FFBD1829A520@DM5PR06MB2777.namprd06.prod.outlook.com>
In-Reply-To: <DM5PR06MB27776B4DBBE95A286FFBD1829A520@DM5PR06MB2777.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.153]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZGbG9WHfRnIBog6U3xCwe7V/FZrHv7Xpm i1U/PrM4MHssWfKTyWNn+xU2jxMN29kDmKO4bFJSczLLUov07RK4Mg7t2MBW0CdTcfPBGfYG xg3SXYycHBICJhI/t15j62Lk4hASOMoosePMFCjnG6PE3c63jCBVQgLLGCXm3UwEsdkE9CRW Tf3BDmKLCHQxSiz6mgtiCwuYSey7uAgozgEUN5eY/aoMosRJYt7ffSwgNouAqkT/gXNgNq+A tcSFZWehxu9jlNjanQ1icwrESvy7doAVxGYUEJP4fmoNE4jNLCAucevJfCaIowUkluw5zwxh i0q8fPyPFcJWkth77DoLyAnMApoS63fpQ7QqSkzpfsgOsVZQ4uTMJywTGEVnIZk6C6FjFpKO WUg6FjCyrGIULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIjJuDW37r7mBc/drxEKMAB6MSDy97 Z0C0EGtiWXFl7iFGCQ5mJRHeRx5AId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rx6q/ZECQmkJ5ak ZqemFqQWwWSZODilGhijk45eFNeMXOM4/+lJuctF/T+bz+iZy/g1ewnpthzaeSdmy0O9K4FN 2uvyXVqPzy3jmena4haof/+vzGm5uJlnlVaXsP5K61iZqXLwXknO4QdCqhp/f08/c/t1ydPQ P4/ecc7cmRbXEyMtwPgl8JXXq1MhTuly17OkprfcXVtwbIvdK9VZKzyVWIozEg21mIuKEwFl nnr7lwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/d0CZ287LoGx_cBd7NacYch0SoRE>
Subject: Re: [core] ue of resource type in collections
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: Thu, 19 Jul 2018 14:14:11 -0000

Hi Michel,

the point is that a server is free to organize its URI space as it sees fit and link annotations are needed to find the right resource.

It's not possible to reserve URI paths for any purpose (with the exception of .well-known paths). You can use /c in your examples if you want, but you cannot mandate that implementations do the same or claim it for CoMI. And I don't think it's time well spent if we'd try to ensure that no example uses a path that already appears in another example.

Klaus


> -----Original Message-----
> From: Michel Veillette <Michel.Veillette@trilliant.com>
> Sent: Thursday, 19 July, 2018 15:55
> To: Klaus Hartke <klaus.hartke@ericsson.com>;
> consultancy@vanderstok.org; Core <core@ietf.org>
> Subject: RE: [core] ue of resource type in collections
> 
> The recommended list of CoAP resources listed in the original email conflict
> with current CoMI recommended resource (/c). To minimize the likelihood of
> conflicts, I recommend to define these resources under a single root
> resource.
> 
> For example:
> </est/skg>;rt="ace.est.skg"
> </est/crts>;rt="ace.est.crts"
> </est>; rt="ace.est"
> </est/att>;rt="ace.est.att"
> </est/sren>;rt="ace.est.sren"
> </est/sen>;rt="ace.est.sen"
> 
> Regards,
> Michel
> 
> -----Original Message-----
> From: core [mailto:core-bounces@ietf.org] On Behalf Of Klaus Hartke
> Sent: Wednesday, July 18, 2018 10:00 AM
> To: consultancy@vanderstok.org; Core <core@ietf.org>
> Subject: Re: [core] ue of resource type in collections
> 
> Peter van der Stok wrote:
> > The coaps-est server uses a collection of resources:
> > The collection resource has been assigned rt=ace.est It is not clear
> > what the resource types of the underlying resources should be.
> 
> According to BCP 190 [1], the coaps-est draft should not mandate particular
> forms of URI substructure. So a server should be free to structure URIs as it
> sees fit, e.g.:
> 
> </a>;rt="ace.est"
> </b>;rt="ace.est"
> </c>;rt="ace.est"
> </d>;rt="ace.est"
> </e>;rt="ace.est"
> </f>;rt="ace.est"
> 
> If a client has trouble selecting the right link from the above list (and they all
> look interchangeable to me), then you'd need to provide more specific link
> information, e.g.:
> 
> </a>;rt="ace.est.skg"
> </b>;rt="ace.est.crts"
> </c>; rt="ace.est"
> </d>;rt="ace.est.att"
> </e>;rt="ace.est.sren"
> </f>;rt="ace.est.sen"
> 
> Klaus
> 
> [1] https://tools.ietf.org/html/bcp190
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email