Re: [I2rs-proto-dt] couple YANG details

"Susan Hares" <> Fri, 23 October 2015 20:36 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id CEBA91A9063 for <>; Fri, 23 Oct 2015 13:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -96.354
X-Spam-Status: No, score=-96.354 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iMqzJbyd-_Yj for <>; Fri, 23 Oct 2015 13:36:02 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 335CA1A9061 for <>; Fri, 23 Oct 2015 13:36:02 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: "Susan Hares" <>
To: "'Andy Bierman'" <>, <>
References: <>
In-Reply-To: <>
Date: Fri, 23 Oct 2015 16:36:03 -0400
Message-ID: <030c01d10dd2$6fd3cda0$4f7b68e0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_030D_01D10DB0.E8C53AE0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKMEsdjPzkqeQIW8vtZ5c+9e7UOnJ0DfnSw
Content-Language: en-us
Archived-At: <>
Subject: Re: [I2rs-proto-dt] couple YANG details
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: I2RS protocol design team <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 23 Oct 2015 20:36:04 -0000



Sorry for the delay in responding. 


Declaring module-level “ephemeral” by declaring the top-node as ephemeral is fine.  However,   do you think people will want to query by the module library whether a module is ephemeral. 




From: I2rs-proto-dt [] On Behalf Of Andy Bierman
Sent: Wednesday, October 21, 2015 5:46 PM
To: Susan Hares;
Subject: [I2rs-proto-dt] couple YANG details




I would like to simplify the draft a bit further.


1) module-level "ephemeral" flag

Since the data node flag applies to the entire subtree,

it should be simple enough to just require each top-level

data node to declare 'ephemeral true' if needed.

There are usually 1 - 2 top-level data nodes per module so

this is not a burden.  Checking 2 places is too complicated

and they can conflict.


2) groupings wrt/ edit overlap


YANG already has a way to say what sub-nodes must

be present (mandatory=true, min-elements>0).

Is this good enough for I2RS?  Can the requirements

for the ephemeral version be different than the

persistent version, wrt/ mandatory & min-elements?