IETF Logo Mail Archive

Re: [netmod] some comments on revised-datastores-01

Martin Bjorklund <mbj@tail-f.com> Sun, 19 March 2017 16:37 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C55AC127BA3 for <netmod@ietfa.amsl.com>; Sun, 19 Mar 2017 09:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 j0barWmEAJC4 for <netmod@ietfa.amsl.com>; Sun, 19 Mar 2017 09:37:07 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 09988124C27 for <netmod@ietf.org>; Sun, 19 Mar 2017 09:37:06 -0700 (PDT)
Received: from localhost (h-148-188.a165.priv.bahnhof.se [176.10.148.188]) by mail.tail-f.com (Postfix) with ESMTPSA id BFA721AE0332; Sun, 19 Mar 2017 17:37:02 +0100 (CET)
Date: Sun, 19 Mar 2017 17:37:02 +0100
Message-Id: <20170319.173702.1332458451679178380.mbj@tail-f.com>
To: kwatsen@juniper.net
Cc: andy@yumaworks.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <CEDE2294-1BCB-451A-B79E-9E60294419FF@juniper.net>
References: <CABCOCHQDWqDXtkVtQH4dsRRO4HFAJELU1_06TBvhjnZZtj9t8g@mail.gmail.com> <20170319.094733.1957440769000198080.mbj@tail-f.com> <CEDE2294-1BCB-451A-B79E-9E60294419FF@juniper.net>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/REhwekeef2YQcQ2I3N4LsVVUMfw>
Subject: Re: [netmod] some comments on revised-datastores-01
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Mar 2017 16:37:09 -0000

Kent Watsen <kwatsen@juniper.net> wrote:
> 
> 
> 
> > Currently there is no explicit mechanism for a server to
> > advertise which datastores is supports, other that the advertisment of
> > features in "ietf-datastore".  Maybe we should add an explicit list of
> > supported datastores (but this will be protocol-dependent, since some
> > protocols might not expose all datastores).
> 
> The new dynamic datastores are (per this draft) advertised by being
> listed in YANG Library.  Only the "built in" datastores wouldn't have
> a module-backing.

Actually, in the current draft, each module has a leaf-list of all
datastores (not only dynamic) where the module is implemented.

We have discussed various variations on this theme, but the current
leaf-list is probably the simplest.

> This is okay for the most part today as NETCONF has its capabilities
> and RESTCONF has its unified datastore, but it does leave <intended>
> hanging in the wind.
> 
> Formally defining the built-in datastores as you suggest, using a
> module to define their presence, would be nice from a consistency
> perspective.



/martin

v2.23.0 | Report a Bug | By Email