IETF Logo Mail Archive

Re: [netmod] WG Last Call: draft-ietf-netmod-revised-datastores-04 updates

Andy Bierman <andy@yumaworks.com> Sat, 16 September 2017 16:59 UTC

Return-Path: <andy@yumaworks.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 51B02133066 for <netmod@ietfa.amsl.com>; Sat, 16 Sep 2017 09:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.com
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 UuqnO-WYvVuu for <netmod@ietfa.amsl.com>; Sat, 16 Sep 2017 09:59:36 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3CDA1326ED for <netmod@ietf.org>; Sat, 16 Sep 2017 09:59:33 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id u21so4790760lfk.12 for <netmod@ietf.org>; Sat, 16 Sep 2017 09:59:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=PNls2MqxKv87w+0gmjenYs1ZJ3HXwiN4+U4kgtyshV4=; b=OnYnRzXNWMa+n0wFLHTPVPwo29X4tvMUov9yT2U9VpH+JdWl70S2xatznX07QK81di UpAvAhN0IbZHDFM6ynvLmbSwXTuLjZpJB0SbubsVoT7SWvepApEOtQJNL1Oj3T6lB7B9 j2Et1JX/SPVCoKB0Lz2nCCzAuQ3/4lPMr+AJqG7wF4f088bx0Sgwu8ZkLbmf3uXQcb/R PgSeiMgvYUUHhJiMfrqeSrJLFZfppcwMdxTpCAq/CxuK9tz2xADp3j/ur/5TRej3dx8x TR0nrweX+QXruY6ZsDVfhDlePKvyt4DunHcqhSTco97JN8oyBBgS/JCa2gAzsM0vvqlQ nw9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=PNls2MqxKv87w+0gmjenYs1ZJ3HXwiN4+U4kgtyshV4=; b=kwdUX5eeNySZgxJ2liHYJPKyB54MoerxVTbYswFyCuiDHnXYvNugQ32bZTZLDirPbz Ad9UpxmgCbDjuiUDh/ZEwcUeX+lwi7pDkmBxRBs1BkXQEFdDRLOCvnYgUUSa3VNKdToo vLQLCc2/Zi5crqK/9I12WjXw4yAs/mk8r4YRfB7iztsz8HlSy6yDRTU2DWlFuKSYW1On Aqe5lBTpaLFjrARkxdMtipzCafpdBMROYd/unO0wZuA4mn+8YCMk1LfuiWzLCK/rEnXX sCQeo211YqQLm+K4MU2bFyibL8nr9K1vrGafqqGPDuagALfGAgHTNjaxi4BeiPqPQyqC Pybw==
X-Gm-Message-State: AHPjjUgUmXUG3xbbReFNklYsF4P15WYInIOAqJ08KN3XCjlWqcSSv1s2 qKGkacmplBWrAG97OHfjzFECVZPafoGVbk7picZEyw==
X-Google-Smtp-Source: AOwi7QCR+arj9jBCtOYG1QBc0AD4VdEb52yJTfCZGgNPeqCxIbAPqSiafTNWCe644mtVbVnqIG0DZLT7O4S3prCfwDs=
X-Received: by 10.25.142.9 with SMTP id q9mr1528865lfd.89.1505581171808; Sat, 16 Sep 2017 09:59:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.18.41 with HTTP; Sat, 16 Sep 2017 09:59:30 -0700 (PDT)
In-Reply-To: <20170916101408.v7kimhqkrgxo65m3@elstar.local>
References: <511deba5-34ca-dde2-6637-ceaf4c4af125@labn.net> <022001d32e14$8d5d4540$4001a8c0@gateway.2wire.net> <20170915123443.kvagu7dut7oaqoo2@elstar.local> <CABCOCHQcSUSUZMvzVGyaXObHadZqksKge89_6YcH9PCbxMCG=g@mail.gmail.com> <20170916072403.xp37556z6g7b42gr@elstar.local> <CABCOCHT8CMCAnqf6Oe1bKMzQ-B_0GjrQiQ8YXgQJvCo-NBOBBA@mail.gmail.com> <20170916101408.v7kimhqkrgxo65m3@elstar.local>
From: Andy Bierman <andy@yumaworks.com>
Date: Sat, 16 Sep 2017 09:59:30 -0700
Message-ID: <CABCOCHR0FyizNN5cHwTu6Xo8o4KMfDHiDwKmcv9gYScD1N2TPw@mail.gmail.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, "t.petch" <ietfc@btconnect.com>, Lou Berger <lberger@labn.net>, netmod WG <netmod@ietf.org>, NetMod WG Chairs <netmod-chairs@ietf.org>, draft-ietf-netmod-revised-datastores@ietf.org
Content-Type: multipart/alternative; boundary="f403045f5070ed2fa60559516efa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/mXmlst0DsSUgt7ReDIv_iME2WjU>
Subject: Re: [netmod] WG Last Call: draft-ietf-netmod-revised-datastores-04 updates
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: Sat, 16 Sep 2017 16:59:37 -0000

On Sat, Sep 16, 2017 at 3:14 AM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Sat, Sep 16, 2017 at 02:56:45AM -0700, Andy Bierman wrote:
>
> > Either way, the new YANG rules seem half-baked and not ready
> > for standardization.
>
> OK. Then please tell us where you see problems. The usage of must vs
> MUST does not seem to be the issue.
>
>

sec 4.4:

    Validation is performed on the contents of <intended>.


Does this mean validation is not done on <running>?
The draft does not say.  If so, then this seems to break all
existing clients that validate <running>. Standard operations
such as <commit> or <edit-config> with :writable-running capability work
this way.

What happens if a client does validation on <running>? It now can fail even
though RFC 7950, sec. 8.1 says:

   *The running configuration datastore MUST always be valid.*

The motivation is clear in the RD draft, sec 4.3:

   The running configuration datastore (<running>) holds the complete
   current configuration on the device.  It may include inactive
   configuration or template-mechanism-oriented configuration that
   require further expansion.


This forces a client to accept unspecified proprietary inactive
configuration and proprietary templates
that apparently are not subject to YANG validation.

   Currently there are no standard mechanisms defined that affect
   <intended> so that it would have different contents than <running>,
   but this architecture allows for such mechanisms to be defined.


This is a significant change in the NETCONF/RESTCONF standards which is
completely unrelated to operational state. The client MUST understand
unspecified
proprietary differences between <running> and <intentional>.  The client
can now
assume that <running> is always valid, but this draft breaks that.

IMO, only the <operational> datastore work is standards-ready.


Andy



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

v2.23.0 | Report a Bug | By Email