Re: [Netconf] {+restconf}/data
Ladislav Lhotka <lhotka@nic.cz> Thu, 19 July 2018 20:53 UTC
Return-Path: <lhotka@nic.cz>
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 8202B130F16 for <netconf@ietfa.amsl.com>; Thu, 19 Jul 2018 13:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 PtSSQJw63_SD for <netconf@ietfa.amsl.com>; Thu, 19 Jul 2018 13:53:07 -0700 (PDT)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB34130E30 for <netconf@ietf.org>; Thu, 19 Jul 2018 13:53:07 -0700 (PDT)
Received: by trail.lhotka.name (Postfix, from userid 109) id 01D621820CC0; Thu, 19 Jul 2018 22:59:01 +0200 (CEST)
Received: from localhost (dhcp-9627.meeting.ietf.org [31.133.150.39]) by trail.lhotka.name (Postfix) with ESMTPSA id DFE711820053; Thu, 19 Jul 2018 22:58:59 +0200 (CEST)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: Netconf <netconf@ietf.org>
In-Reply-To: <20180719084156.llzgfj465hov4s47@anna.jacobs.jacobs-university.de>
References: <87efg0nxa1.fsf@nic.cz> <20180719084156.llzgfj465hov4s47@anna.jacobs.jacobs-university.de>
Date: Thu, 19 Jul 2018 16:53:01 -0400
Message-ID: <87o9f39ccy.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/XUl0W6gjgqGkZpd5Pbpejy_L5TU>
Subject: Re: [Netconf] {+restconf}/data
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, 19 Jul 2018 20:53:10 -0000
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> writes: > Lada, > > there is no point in changing the definition of {+restconf}/data since > this would lead to interoperability issues and hence {+restconf}/data > remains what it is. Clients can have interoperability issues already now, e.g. if the server upgrades to the new "ietf-interfaces" module: - it can receive loads of unexpected state data and statistics - no data may be available under "interfaces-state" (because of the ambiguity of the deprecated status). > > Yes, the new datastore names are longer but we did not want to require > globally unique datastore names (which would require some form of a > registry and that everybody uses the registry). Most of the text in RFC 8040 deals with the {+restconf}/data resource and its descendants, so effectively deprecating it in another document seems pretty confusing. I think that {+restconf}/data should remain the main entry point to configuration for an average client. Lada > > /js > > On Wed, Jul 18, 2018 at 03:45:10PM -0400, Ladislav Lhotka wrote: >> Hi, >> >> it seems that using RESTCONF with the updated NMDA-compatible modules >> leads to the (IMO undesirable) result where under the "legacy" root >> "{+restconf}/data" state data are mixed with configuration. For example, >> with ietf-interfaces@2018-02-20 >> >> GET {+restconf}/data/ietf-interfaces:interfaces >> >> yields configuration, state data and statistics, whereas with the old >> revision ietf-interfaces@2014-05-08 GET on the same URL yields only >> configuration. I think this defeats the purpose of NMDA. >> >> On the other hand, the short datastore-less URLs are too handy to be >> simply deprecated. I would therefore propose that {+restconf}/data be >> essentially an alias for the configuration datastore that the user can >> directly edit. This means: >> >> - with writable <running> it will be an alias to running >> >> - if the implementation uses <candidate>, it will be an alias to >> <candidate>. >> >> Lada >> >> -- >> Ladislav Lhotka >> Head, CZ.NIC Labs >> PGP Key ID: 0xB8F92B08A9F76C67 >> >> _______________________________________________ >> Netconf mailing list >> Netconf@ietf.org >> https://www.ietf.org/mailman/listinfo/netconf > > -- > 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/> -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67
- [Netconf] {+restconf}/data Ladislav Lhotka
- Re: [Netconf] {+restconf}/data Juergen Schoenwaelder
- Re: [Netconf] {+restconf}/data Ladislav Lhotka
- Re: [Netconf] {+restconf}/data Andy Bierman
- Re: [Netconf] {+restconf}/data Ladislav Lhotka
- Re: [Netconf] {+restconf}/data Andy Bierman
- Re: [Netconf] {+restconf}/data Juergen Schoenwaelder