[I2rs-proto-dt] I2RS meeting

Andy Bierman <andy@yumaworks.com> Sun, 01 November 2015 20:35 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 C77B51B8D28 for <i2rs-proto-dt@ietfa.amsl.com>; Sun, 1 Nov 2015 12:35:35 -0800 (PST)
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 2TEgiBXZdyDN for <i2rs-proto-dt@ietfa.amsl.com>; Sun, 1 Nov 2015 12:35:34 -0800 (PST)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 85C2C1B8D27 for <i2rs-proto-dt@ietf.org>; Sun, 1 Nov 2015 12:35:34 -0800 (PST)
Received: by lbbec13 with SMTP id ec13so76944278lbb.0 for <i2rs-proto-dt@ietf.org>; Sun, 01 Nov 2015 12:35:32 -0800 (PST)
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=PqTKCdQf61TUAIQXeL8dg9WWXVMZ25x0sX/zQfb4IW8=; b=SUE+LTCdpC8qKO5YbFx7xClk2VqPrIeJznat5LKTZIp9tjG4xmm09wEKKG9s1wxsWJ xAIPRKDEyen5fJ7yKpvK+SXzIJua5X8nIbBeuEjRMG7hf2D0g6GAdr73y0XkN8+8EjkV 6C+zLEwhTMgSArahMAMjW4aYBKF9pXCqT+r4XFceFl2tK370RQ2r9+7FYIM+Nz1pFd9y 1EXnZpjsD/5hP2F/U1db9I/fuo/fBawGrntP4f/3RhmnnKGxZ01rMb38P8iB34STymw6 JfWXnJUClc5XGEUipWOtlhC9UXSvDX5ehlU8dHhXiZL+sLHAvokm5UK7+H39YcBNX210 nUoQ==
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=PqTKCdQf61TUAIQXeL8dg9WWXVMZ25x0sX/zQfb4IW8=; b=J01hKnrO56ygmyy2VDSrWgUBiY0irxaApyg4hkmukUFqcqOQ9BxhQeUSmoW10MipxE cds+b17N15Hz8j2fmkW6ADPcOST0x49BG5CBSXH1ObqjMv9ko/EOlWLTpHKdmmQ2rTeZ ImBRMXggOGtbj7I4H4z2V0CBmdcCxnxbR4cpBy+2VsjzeMT58IZbQ/kYMDl6wro4sGBW 3gDbzg46KIRLDUG1OYtfgsg+4VmEYmDPsr+uiwjtdFhDIflgDPFmrnuHtvNJvx/JmPgR N7q3d8xYLF5fUQ6HQA3lcZYKkojrsejIqHahNr/ZRRFGFVS9eCikWyT2TZZNjNe6CHRs 8IRw==
X-Gm-Message-State: ALoCoQl6w5BXOnAXMfNWFQxoZRrGVdKy040WYBV+gG0PvJFLWd+bDQxvNLEzzj1blnjKZi3p2HuJ
MIME-Version: 1.0
X-Received: by 10.112.141.7 with SMTP id rk7mr8300206lbb.82.1446410132647; Sun, 01 Nov 2015 12:35:32 -0800 (PST)
Received: by 10.112.144.106 with HTTP; Sun, 1 Nov 2015 12:35:32 -0800 (PST)
Date: Sun, 01 Nov 2015 12:35:32 -0800
Message-ID: <CABCOCHQmW34gjQ3zrhLvk3a1zYk5LFftLfTgy+rPq1skCbqhXA@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="001a11c37e1a280e870523809aed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/QF9vHHEZb9BKEJoO4DOVRm9zT30>
Subject: [I2rs-proto-dt] I2RS meeting
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: Sun, 01 Nov 2015 20:35:36 -0000

Hi,

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


Andy