[I2rs-proto-dt] couple YANG details

Andy Bierman <andy@yumaworks.com> Wed, 21 October 2015 21:46 UTC

Return-Path: <andy@yumaworks.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 0E5481B31D4 for <i2rs-proto-dt@ietfa.amsl.com>; Wed, 21 Oct 2015 14:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 B6fUFeGZGBoa for <i2rs-proto-dt@ietfa.amsl.com>; Wed, 21 Oct 2015 14:45:59 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAF651B31D2 for <i2rs-proto-dt@ietf.org>; Wed, 21 Oct 2015 14:45:58 -0700 (PDT)
Received: by lfaz124 with SMTP id z124so27509786lfa.1 for <i2rs-proto-dt@ietf.org>; Wed, 21 Oct 2015 14:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks_com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=7Jbv6SB0h1GPjx/q9MDDTT9bTyNPHDdOKWsrz+mmm98=; b=XPAFp24QGIyvvMUc2FY6TjEy/LMlk9HsO89KZSQ58tkQ7ILBJkwMEET4cfn1uoaMNF olGhOgP5JUBrFBgt0wct6lmb50hvTN54DCXsXDVIEgPmMYzYjMnKKOwZTvAXtIFmuZlj pTggMyNkLM3KqQ0QBJWXRxUiPYeUkvp7WkmV30V18JDEZ1gOL5MLdFDBZW2mHFzW9p7I ickD5hFXOI11Eg8gaD6x678mxUpT13MXZvrnfrJtXIenn0ciLv4IItAYyCtyzUWLSL3p gEYCEscJmTogBPB8WCRhsPPEBtKCbbJPcznF0eZV723iAuWwE6Lvy30cxcdzfUmuar3K ADjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=7Jbv6SB0h1GPjx/q9MDDTT9bTyNPHDdOKWsrz+mmm98=; b=IQjrsAMMO5eSH7T2nQ682+DZVNLGSOrZsviY3khRbEPtU7kMV4rnW+RXTYCawrSiPT XXVYobrFKovRBT8vrQsrNOOn+5NB5lJiZ62EhCGw+p/eMuD91d3ovGqW+52ZamyqeV1w 9gsnkMXeVLMN8HWk1BF9qAeIzVWVnvyNXp3jXVQRJ7D38ykrf+3p8btXJSab2V8zCIxU CY4SYXjtxLbAAVTXtTMbATX/Fxldaj0tMX4bSCKMSHczgfIPtxQuSrdF6JWd94TRXN49 E9deIqd1qfWo3/uk9OHeD+AjQNaHIhoZd9fQiXf+VJM99TMhVAkYoIfmMIC5H8jgXy4j T0ww==
X-Gm-Message-State: ALoCoQkLOtqfHd7NWGeXVTaYt3hdwsNSmBGk30AzJ7SDBG4m2HObgsKdetTx0hK19o0w2NIOsUlg
MIME-Version: 1.0
X-Received: by 10.25.44.80 with SMTP id s77mr4271932lfs.37.1445463956857; Wed, 21 Oct 2015 14:45:56 -0700 (PDT)
Received: by 10.112.138.72 with HTTP; Wed, 21 Oct 2015 14:45:56 -0700 (PDT)
Date: Wed, 21 Oct 2015 14:45:56 -0700
Message-ID: <CABCOCHRRDZZZF1uj6UVDezmZzM3g8bEQiWTkyZKUPk6HL40fcg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Susan Hares <shares@ndzh.com>, i2rs-proto-dt@ietf.org
Content-Type: multipart/alternative; boundary=001a11410916af439a0522a44d03
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/3fCjWzRICPZdnffJlHznDZ7WXhM>
Subject: [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, 21 Oct 2015 21:46:00 -0000

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?