[core] Separate formats for fetch and patch (was: WG Last Call of draft-ietf-core-senml-etch-03.txt)

Christian Amsüss <christian@amsuess.com> Wed, 26 June 2019 13:30 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 3486812003E for <core@ietfa.amsl.com>; Wed, 26 Jun 2019 06:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 fGW2O3hp6trP for <core@ietfa.amsl.com>; Wed, 26 Jun 2019 06:30:40 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF9241200D6 for <core@ietf.org>; Wed, 26 Jun 2019 06:30:40 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 1FBB4460B9; Wed, 26 Jun 2019 15:30:37 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id B801636; Wed, 26 Jun 2019 15:30:35 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:b187:7d3a:a59c:185]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 7B35F2A; Wed, 26 Jun 2019 15:30:35 +0200 (CEST)
Received: (nullmailer pid 10211 invoked by uid 1000); Wed, 26 Jun 2019 13:29:59 -0000
Date: Wed, 26 Jun 2019 15:29:59 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: Klaus Hartke <hartke@projectcool.de>
Cc: core <core@ietf.org>
Message-ID: <20190626132951.GA3528@hephaistos.amsuess.com>
References: <9AD3C4BB-7965-4776-84C4-6B5BFDCAA262@tzi.org> <e3a61d2c-1183-5ece-74d8-b1bad26ddfe6@ericsson.com> <3E80442D-9EBF-4973-89E1-7B4A69F42754@tzi.org> <E8AD8AB7-DF40-4049-901E-18C0655A3DAD@tzi.org> <CAAzbHvbT6Dyjh+33Mnb74wk1oh8iSWo-hUPq1hpBwgWyPe15Bg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH"
Content-Disposition: inline
In-Reply-To: <CAAzbHvbT6Dyjh+33Mnb74wk1oh8iSWo-hUPq1hpBwgWyPe15Bg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/V6dRc5z15E5lyjmeQkkp8A4X5qw>
Subject: [core] Separate formats for fetch and patch (was: WG Last Call of draft-ietf-core-senml-etch-03.txt)
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: Wed, 26 Jun 2019 13:30:43 -0000

On Mon, Jun 24, 2019 at 01:21:31PM +0200, Klaus Hartke wrote:
> General questions:
> 
> * It seems the new data formats are supersets of the existing data
> formats. Also, it seems the same data format is used for fetching and
> patching data. Is this what we, as CoRE WG, recommend (1 media type
> for data, 1 media type for fetching and patching)? CoRAL is doing it
> differently at the moment.

I'd view this not as a general recommendation but as a way to go if for
some reason the "descriptive" format can not be extended within its own
constraints. In CoRAL, I don't see a need for separate media types.
Applications mint their own dictionaries anyway.

An application can make restrictions like in [1] for some operations
(eg. "an Information Provider must only use dictionary I on resource
representations returned from GET, and may accept dictionary F for
FETCH-like operations if supported").

Best regards
Christian

[1]: https://tools.ietf.org/html/draft-hartke-t2trg-coral-08#section-6.1.3

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