IETF Logo Mail Archive

Re: [core] 🔔 WG Last Call of draft-ietf-core-etch-01

peter van der Stok <stokcons@xs4all.nl> Thu, 14 July 2016 15:28 UTC

Return-Path: <stokcons@xs4all.nl>
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 3498C12D7EF for <core@ietfa.amsl.com>; Thu, 14 Jul 2016 08:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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 YXSda41MONJM for <core@ietfa.amsl.com>; Thu, 14 Jul 2016 08:28:03 -0700 (PDT)
Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2F6E12D685 for <core@ietf.org>; Thu, 14 Jul 2016 08:28:02 -0700 (PDT)
Received: from webmail.xs4all.nl ([194.109.20.209]) by smtp-cloud6.xs4all.net with ESMTP id JfU01t00n4WfiVN01fU019; Thu, 14 Jul 2016 17:28:01 +0200
Received: from 2001:983:a264:1:4563:dcea:23df:e56a by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Thu, 14 Jul 2016 17:28:00 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Thu, 14 Jul 2016 17:28:00 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Ari Keränen <ari.keranen@ericsson.com>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <DCC9C696-75E5-4F77-BB83-9EDB65F18D9E@ericsson.com>
References: <6292828E-BF6C-456B-82A5-6B86C120D013@ericsson.com> <81E0417A-71AC-4783-8D81-1B1C4111222D@ericsson.com> <c0ae655306a72cf087dc7901a052ef9b@xs4all.nl> <DCC9C696-75E5-4F77-BB83-9EDB65F18D9E@ericsson.com>
Message-ID: <ad023a2300c49fb939b522db0668674e@xs4all.nl>
X-Sender: stokcons@xs4all.nl (Pp8R1TPfb9aiR8JoycM4YxbJKWBVO91V)
User-Agent: XS4ALL Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/f8pPGHVeJwWf2Qh_wMWxxgEfK9M>
Cc: core <core@ietf.org>, draft-ietf-core-etch@tools.ietf.org
Subject: Re: [core] 🔔 WG Last Call of draft-ietf-core-etch-01
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: consultancy@vanderstok.org
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, 14 Jul 2016 15:28:04 -0000

What do the
>>> implementations use? I'm thinking that something like xpath
>>> (/jsonpath?) media type would be easy to define.
>> 
>> An array of JSON identifiers looks reasonable. Is it your suggestion 
>> to define that in this draft?
> 
> What would be the semantics of that array? "Give only these
> key-value-pairs"? How would that work with nested structures and
> arrays?
> 
> The xpath and jsonpath media types could do that and much more. Some
> of that complexity may not be good for the most constrained devices
> though.
> 
In CoMI we will define an array of YANG identifiers.
I can imagine that this is confirmed (extended) in a later content 
format draft.

PS.
For the other point I refer to Carsten's e-mails.

Peter

v2.23.0 | Report a Bug | By Email