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

Jeffrey Haas <jhaas@pfrc.org> Fri, 23 October 2015 15:19 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 4A24D1A1DE1 for <i2rs-proto-dt@ietfa.amsl.com>; Fri, 23 Oct 2015 08:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level:
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UVmRhh6rEgoD for <i2rs-proto-dt@ietfa.amsl.com>; Fri, 23 Oct 2015 08:19:45 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id AB9281A1C02 for <i2rs-proto-dt@ietf.org>; Fri, 23 Oct 2015 08:19:45 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id D88641E508; Fri, 23 Oct 2015 11:19:45 -0400 (EDT)
Date: Fri, 23 Oct 2015 11:19:45 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Andy Bierman <andy@yumaworks.com>
Message-ID: <20151023151945.GG26793@pfrc.org>
References: <CABCOCHRRDZZZF1uj6UVDezmZzM3g8bEQiWTkyZKUPk6HL40fcg@mail.gmail.com> <CABCOCHSinfdgfxhg8Ly9ZDSDCvqi3xse+ZwAAQnYweEaMJ6j7w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABCOCHSinfdgfxhg8Ly9ZDSDCvqi3xse+ZwAAQnYweEaMJ6j7w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/i70XuKOHj44htfeFB2A89MmfmKw>
Cc: i2rs-proto-dt@ietf.org, Susan Hares <shares@ndzh.com>
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: Fri, 23 Oct 2015 15:19:46 -0000

Andy,

On Wed, Oct 21, 2015 at 02:49:12PM -0700, Andy Bierman wrote:
> We need to figure out for each YANG constraint:
>  1) does it apply at all?
>  2) is it MUST, SHOULD, or MAY enforce?
>  3) Does the constraint apply the same in running vs. ephemeral?
>  4) Does the constraint apply to the combined panes of glass or
>      each pane independently?

I'm going to avoid answering your question to let you decide what this
functional requirement means:
Ephemeral nodes SHOULD NOT introduce their own constraints.  
The presence of ephemeral nodes does not trump validation or constraints for
persistent state.

-- Jeff