Re: [netmod] Decision on the Intended Status of the Revised DS Draft WAS:RE: :candidate, :writable-running and RESTCONF edits

Robert Wilton <rwilton@cisco.com> Thu, 19 January 2017 14:14 UTC

Return-Path: <rwilton@cisco.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 8D90E1270B4 for <netmod@ietfa.amsl.com>; Thu, 19 Jan 2017 06:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level:
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 2V_fxcAUmHmr for <netmod@ietfa.amsl.com>; Thu, 19 Jan 2017 06:14:40 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BECF11295ED for <netmod@ietf.org>; Thu, 19 Jan 2017 06:14:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3983; q=dns/txt; s=iport; t=1484835279; x=1486044879; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=7rvZum9yH9IhGCOiyUdoDDJ0/eVxnBGW667Nnn1i0Tk=; b=QSylDi+LAsesy3/FnR9fhEyyX9brfpRYYzkR5s6pZ2W62G/7gILwPwbI M6d8tJOi6QDbcVs50JfOxsTx7XsL/axKkvNe0mTEtrpO1iGPtaMkdANNF 5M/UjLqjRbDSzV5FgmVgYQJmSpmoeYOfHyg40MavxlDCDtkvHITcigjFY w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALAQCWyIBY/xbLJq1eGQEBAQEBAQEBAQEBBwEBAQEBgm9QAQEBAQGBAieOOHKREZABgxyCD4IMhiICgj0YAQIBAQEBAQEBYyiEaQEBAQMBeRALBBQjC1cGDQgBAReIYAiyECuKFAEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GS4IFgmmEM4V6BZtEkWWKMIY+inSHfB84gRcSCBUVhSmBSD6KGQEBAQ
X-IronPort-AV: E=Sophos;i="5.33,254,1477958400"; d="scan'208,217";a="649964450"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jan 2017 14:14:37 +0000
Received: from [10.63.23.107] (dhcp-ensft1-uk-vla370-10-63-23-107.cisco.com [10.63.23.107]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v0JEEb3a007562; Thu, 19 Jan 2017 14:14:37 GMT
To: Phil Shafer <phil@juniper.net>
References: <201701182126.v0ILQC6h039302@idle.juniper.net>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <5f5bed10-d84e-fcb8-fdaa-722e00078dbb@cisco.com>
Date: Thu, 19 Jan 2017 14:14:32 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <201701182126.v0ILQC6h039302@idle.juniper.net>
Content-Type: multipart/alternative; boundary="------------F17D467CC4070C9E726606B9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/D3G0gLY29kAlwgvGGb_yfdD8LXc>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] Decision on the Intended Status of the Revised DS Draft WAS:RE: :candidate, :writable-running and RESTCONF edits
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 19 Jan 2017 14:14:41 -0000

[Dropping netconf from the reply]

Hi Phil,

On 18/01/2017 21:26, Phil Shafer wrote:
> Robert Wilton writes:
>>> The server is buggy if it is sending data that violates YANG constraints.
>>> If any of these statements need to be different for config and oper
>>> then the old style YANG has to be used instead.
>> You just have a separate state leaf.  These are still allowed in a
>> combined tree.
> We're trying to avoid a "separate state leaf" solution.  That's imho
> the motivation for this whole exercise.
Yes, I agree that we are trying to avoid separate state leaves where 
possible.  But there are some cases where the value space for the 
operational value may differ from the value space that may be configured.

For these point cases, adding an additional config false leaf should be 
fine.  E.g. section 6.4 of draft-nmdsdt-netmod-revised-datastores-00 states:

    o  There may be some differences in the value set of some nodes that
       are used for both configuration and state.  At this point of time,
       these are considered to be rare cases that can be dealt with using
       different nodes for the configured and state values.


Rob

>
> Thanks,
>   Phil
> .
>