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

"Susan Hares" <> Wed, 28 October 2015 11:12 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0FF541B5102 for <>; Wed, 28 Oct 2015 04:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 EDl_U7ZbWfy3 for <>; Wed, 28 Oct 2015 04:12:49 -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 E3EAA1B5104 for <>; Wed, 28 Oct 2015 04:12:48 -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: Wed, 28 Oct 2015 07:12:39 -0400
Message-ID: <014301d11171$91b61160$b5223420$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0144_01D11150.0AA70970"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKMEsdjPzkqeQIW8vtZ5c+9e7UOnJ0KuySA
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: Wed, 28 Oct 2015 11:12:51 -0000



I’m not sure I answered #2 – is the mandatory good enough for I2RS?  The answer is yes. 




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?