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

"Susan Hares" <shares@ndzh.com> Wed, 28 October 2015 11:12 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs-proto-dt@ietfa.amsl.com
Delivered-To: i2rs-proto-dt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FF541B5102 for <i2rs-proto-dt@ietfa.amsl.com>; Wed, 28 Oct 2015 04:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDl_U7ZbWfy3 for <i2rs-proto-dt@ietfa.amsl.com>; Wed, 28 Oct 2015 04:12:49 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3EAA1B5104 for <i2rs-proto-dt@ietf.org>; Wed, 28 Oct 2015 04:12:48 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.177;
From: "Susan Hares" <shares@ndzh.com>
To: "'Andy Bierman'" <andy@yumaworks.com>
References: <CABCOCHRRDZZZF1uj6UVDezmZzM3g8bEQiWTkyZKUPk6HL40fcg@mail.gmail.com>
In-Reply-To: <CABCOCHRRDZZZF1uj6UVDezmZzM3g8bEQiWTkyZKUPk6HL40fcg@mail.gmail.com>
Date: Wed, 28 Oct 2015 07:12:39 -0400
Message-ID: <014301d11171$91b61160$b5223420$@ndzh.com>
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
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/ZF4A_J-XEnT10Kiz6jrIIsN2k3s>
Cc: i2rs-proto-dt@ietf.org
Subject: Re: [I2rs-proto-dt] couple YANG details
X-BeenThere: i2rs-proto-dt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: I2RS protocol design team <i2rs-proto-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs-proto-dt>, <mailto:i2rs-proto-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs-proto-dt/>
List-Post: <mailto:i2rs-proto-dt@ietf.org>
List-Help: <mailto:i2rs-proto-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs-proto-dt>, <mailto:i2rs-proto-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2015 11:12:51 -0000

Andy: 

 

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

 

Sue 

 

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

 

Hi,

 

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?