Re: [Netconf] Comments on draft-lhotka-netconf-restconf-transactions-00

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 12 July 2018 21:42 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF501311A8 for <netconf@ietfa.amsl.com>; Thu, 12 Jul 2018 14:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 mFtu1mdSJz5B for <netconf@ietfa.amsl.com>; Thu, 12 Jul 2018 14:42:56 -0700 (PDT)
Received: from anna.localdomain (anna.eecs.jacobs-university.de [IPv6:2001:638:709:5::7]) by ietfa.amsl.com (Postfix) with ESMTP id AF1AD1277BB for <netconf@ietf.org>; Thu, 12 Jul 2018 14:42:55 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 8B14223257F1; Thu, 12 Jul 2018 23:42:53 +0200 (CEST)
Date: Thu, 12 Jul 2018 23:42:52 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Ladislav Lhotka <lhotka@nic.cz>
Cc: Robert Wilton <rwilton@cisco.com>, "netconf@ietf.org" <netconf@ietf.org>
Message-ID: <20180712214252.ukoe43tzxxf75bfz@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Ladislav Lhotka <lhotka@nic.cz>, Robert Wilton <rwilton@cisco.com>, "netconf@ietf.org" <netconf@ietf.org>
References: <b26d88fe-2797-a8f8-a2e3-a5aed2fae6d7@cisco.com> <87sh4ofjyd.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <87sh4ofjyd.fsf@nic.cz>
User-Agent: NeoMutt/20180622
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/4BHSZ9Jb6DHTwXv2LPM8Jd7U_DI>
Subject: Re: [Netconf] Comments on draft-lhotka-netconf-restconf-transactions-00
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 21:42:59 -0000

On Thu, Jul 12, 2018 at 07:22:02PM +0200, Ladislav Lhotka wrote:
> > 2) I don't think that this draft needs to mention <intended> at all.  
> > Instead, everywhere you mention <intended> then you should be saying 
> > <running>.  I.e. your staging datastores should update <running> on a 
> > commit operation, just like a commit of <candidate> updates <running>.  
> > <intended> is always just updated as a side effect of a write to 
> > <running>, and as such is a tangential consideration.
> 
> The main reason for using <intended> is that the target datastore into
> which staging datastores are merged has to be valid at all
> times. <running> has somewhat fuzzy semantics both in NETCONF and under
> NMDA. But yes, the text also says that essentially we have <running> and
> <intended> being the same. NMDA explicitly permits this simplification.

I think NMDA says that <running> and <intented> in general are _not_
the same but that for _some_ implementations they may be de factor the
same or indistinguishable. If your proposal assumes <running> equals
<intended>, then your proposal is only applicable to _some_
implementations.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>