Re: [I2rs-proto-dt] I2RS meeting

"Susan Hares" <> Sun, 01 November 2015 21:04 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 295AC1A8A89 for <>; Sun, 1 Nov 2015 13:04:31 -0800 (PST)
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 b61BQolQhB2w for <>; Sun, 1 Nov 2015 13:04:30 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EA19D1A8A87 for <>; Sun, 1 Nov 2015 13:04:29 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <>
To: 'Andy Bierman' <>,
References: <>
In-Reply-To: <>
Date: Sun, 01 Nov 2015 16:04:26 -0500
Message-ID: <007101d114e8$e56e3bf0$b04ab3d0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0072_01D114BE.FC99BA90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQNQov59tpy52wLo67Fj+Dn8V0kbspuIiGjw
Content-Language: en-us
Archived-At: <>
Subject: Re: [I2rs-proto-dt] I2RS meeting
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: Sun, 01 Nov 2015 21:04:31 -0000



I really appreciate this email.   Please comment remotely or skype me (Susan.Hares) or send a note to the jabber scribe. 


How is your dog? 




From: I2rs-proto-dt [] On Behalf Of Andy Bierman
Sent: Sunday, November 01, 2015 3:36 PM
To: Susan Hares;
Subject: [I2rs-proto-dt] I2RS meeting




I plan to listen in to the I2RS meeting.

It's probably too late for a conf-call before the meeting,

but I am available.


I think it is OK to say the YANG constraints apply to

the derived "intended config" and also apply

to the running datastore as defined in YANG.


That means if the max-entries is 5, then 5 can exist in

the running config, and new entries added to ephemeral

must override entries in running.  Retrieving the intended config

actually used (e.g., which config entry is disabled) is

a different issue.  The intended config can only have 5 entries

in it.  It falls out that the ephemeral datastore can only

have 5 entries in it as well.


Not all YANG constraints are as easy as min-elements,

and max-elements.


mandatory, must, when, and unique need more careful thought