Re: [core] draft-ietf-core-resource-directory is update atomic

peter van der Stok <stokcons@xs4all.nl> Mon, 14 August 2017 07:56 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 4CD90131D19; Mon, 14 Aug 2017 00:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 j2b-6eTkniYZ; Mon, 14 Aug 2017 00:56:29 -0700 (PDT)
Received: from lb1-smtp-cloud7.xs4all.net (lb1-smtp-cloud7.xs4all.net [194.109.24.24]) (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 9259E13203D; Mon, 14 Aug 2017 00:56:27 -0700 (PDT)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:216]) by smtp-cloud7.xs4all.net with ESMTPA id hAEZdBzI2Ar7rhAEZd10va; Mon, 14 Aug 2017 09:56:26 +0200
Received: from ip565c6c1e.direct-adsl.nl ([86.92.108.30]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Mon, 14 Aug 2017 09:56:23 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Mon, 14 Aug 2017 09:56:23 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Jim Schaad <ietf@augustcellars.com>
Cc: draft-ietf-core-resource-directory@ietf.org, core@ietf.org
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <00eb01d312bf$a8548040$f8fd80c0$@augustcellars.com>
References: <00eb01d312bf$a8548040$f8fd80c0$@augustcellars.com>
Message-ID: <0205144dc49c2c291e42e035c95765c5@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfPvwvdajfTXruSfvqYc1C4tRaWfFlOd8oSz9dyNb7Dfjuu89qkxxWVpRS0jRdtul0pFCuynZ67FyDayxLU/RphAriGEpa1xhrgJHwL8Ypi0V4gSKvmgj jg6cUp+74Ni23ASeOqvdKdLaqva2xUg5VrhT4fqeSW7Fpui97c855sxmVxtoge+FWzgFPrU6ddftKVX9PcnenANiapUsv8uPkfSBcksKxMGCEeTAzDbtwyi7 sazPHlYrNBHclV1KPLRqXA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/qXPhWtLE3NNhaKK2ICr-Sdew0pU>
Subject: Re: [core] draft-ietf-core-resource-directory is update atomic
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: Mon, 14 Aug 2017 07:56:31 -0000

Thanks Jim,

I try to answer below. I hope I understand the meaning correctly.

Jim Schaad schreef op 2017-08-11 18:34:
> I am going through and figuring out how to implement this specification 
> and
> I came up with a questions on how things work.
> 
> 1.  The document says that PATCH is supported.  What about iPATCH?
Good remark. The document should probably state that both are allowed 
but iPATCH is preferred.
> 
> 2. Are PATCH and POST update operations atomic?
The spec says that registrations need to be idempotent, that is not 
repeated for the other operations (but implied?).
The update changes the lt; you might argue that this is not an 
idempotent operation as the effects at a given time changes after a 
second invocation of the same update. Nevertheless, I would call it 
idempotent.
Idempotency => atomic? (as meaning: all or nothing)
> Is a partial update
> permitted or is that not allowed?
Partial updates are permitted for PATCH and also for POST under the 
conditions specified in section 5.4.1
Or is your argument that POST should not be used for partial updates.
> 
> Jim

Hope this helps.

peter
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core