IETF Logo Mail Archive

Re: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure

Rob Shakir <rjs@rob.sh> Tue, 26 July 2016 16:43 UTC

Return-Path: <rjs@rob.sh>
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 22ADC12D567 for <netmod@ietfa.amsl.com>; Tue, 26 Jul 2016 09:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.186
X-Spam-Level:
X-Spam-Status: No, score=-3.186 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.287] 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 4GRjLUXrnot9 for <netmod@ietfa.amsl.com>; Tue, 26 Jul 2016 09:43:51 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2a03:9800:10:4c::cafe:b00c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3409112B054 for <netmod@ietf.org>; Tue, 26 Jul 2016 09:43:50 -0700 (PDT)
Received: from [199.87.120.129] (helo=jivecommunications.com) by cappuccino.rob.sh with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <rjs@rob.sh>) id 1bS5S1-0004wN-Gv; Tue, 26 Jul 2016 17:43:25 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_F4A4DB76-BDDF-413E-8528-5EB40E981AC0"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <bed9398c-0e6a-450e-d2ac-b381b6bebf87@cisco.com>
Date: Tue, 26 Jul 2016 10:43:40 -0600
Message-Id: <9C023EE2-6977-4FDB-8672-FC1241FC73FE@rob.sh>
References: <D3A935F0.6A4DC%acee@cisco.com> <eb15fd23-2c0a-50c4-1ebc-7c0e4867dfd8@cisco.com> <20160721174033.GB54646@elstar.local> <d18f5dd0-64d0-e223-88a9-faa4df4b7866@cisco.com> <DCB3EBBF-5EB1-4C8E-AA55-F59C4B5A8E4D@juniper.net> <bed9398c-0e6a-450e-d2ac-b381b6bebf87@cisco.com>
To: Robert Wilton <rwilton@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/GpbG4B1MbglJXaUyyxy9qxCRPXs>
Cc: netmod WG <netmod@ietf.org>
Subject: Re: [netmod] OpsState Direction Impact on Recommended IETF YANG Model Structure
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: Tue, 26 Jul 2016 16:43:53 -0000

> On 26 Jul, 2016, at 9:52 AM, Robert Wilton <rwilton@cisco.com> wrote:
> 
> What other alternatives are available?  As a WG we need to tell the other WGs how the IETF YANG models should be structured.

An interested observer could note that the convention that was described in the initial OpenConfig proposal had objections to it based on the fact that it required models to be written in a certain way. Although this way is prescriptive, and could be observed to cause some pain to the model writer (albeit limited), it has a number of advantages in terms of being very deterministic as to how the model should be structured, allowing leaves to be easily related to each other, and can be programmatically verified.

It seems to me like the working group is trying to have its cake and eat it — that is to say, get these advantages without being prescriptive to the model writer. It is not clear to me that this is actually achievable.

r, An Interested Observer.

v2.23.0 | Report a Bug | By Email