Re: [I2rs-proto-dt] I2RS meeting

Andy Bierman <andy@yumaworks.com> Sat, 14 November 2015 19:56 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 462891B2AB7 for <i2rs-proto-dt@ietfa.amsl.com>; Sat, 14 Nov 2015 11:56:16 -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 ZORph3Z8hnS7 for <i2rs-proto-dt@ietfa.amsl.com>; Sat, 14 Nov 2015 11:56:14 -0800 (PST)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 EE0201B2AB2 for <i2rs-proto-dt@ietf.org>; Sat, 14 Nov 2015 11:56:13 -0800 (PST)
Received: by lfdo63 with SMTP id o63so68562228lfd.2 for <i2rs-proto-dt@ietf.org>; Sat, 14 Nov 2015 11:56:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks_com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kF0qJOqILWGaXdOdsd/jd68bX5eB+5ul+D4ySr4BavE=; b=b9qAU4KYM/9rLk5FWpnkU0JAIQrPP9+XcV/+zjG19Cmbv6+4i2yCxEi9Y1Yozek+tb ny3K9pQiPPWgs36jeuIG2wBJ0lIYORCgPYs4z5jjj/IjS5Pzc7T4Y14hZ9JrPZGgZnyR UzEW344znzJZTGHwzeTtUNsB/G9jB5B2dnldlOy6xSh9GMO7FrjPdPXsJqeyIg+mf1fp GmwsToKGA+iWLHt9jiJp1gE4w6OGNKcbZI61HRfEU631diWC4wC9YZgSyKDg9i9SKUZ/ MBQtPQwVM4FRmOR58tbfZbJuFcthJaZMod8deVvVQhJHz2oif3gNwEZ0TdMEC/beKrHt 7M1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kF0qJOqILWGaXdOdsd/jd68bX5eB+5ul+D4ySr4BavE=; b=fareJlNP32rSyXrvhzOE2aA5qmjauF+sbU3hOkShy378emie7PjRhiZjJOGe8e229g +mBWXj8NwKAZWyMIcyoWxCstglU0E8s/ZPXOpW2l1LlvfMTEEuLkoQuyFVfvb2wpObPk HpaSp37lXnCX/sNj5LhzuW65u/760a6vFv5CzePM9/3XrJMXii/tLsX0E+0Uu82NzEDs oxokRHnL1T+oNibRjcTEvY20gLb9osJ8k3VsrE2zGKPKVgMlXc13mY7BW3pgAzDnGFZf TS1tc8S+aPktLd4jhmyNYKyfeeCuvH+QnDBjHgHg85AxMUN0Y1EW7Zf8Sta+JKhqHxSN NuLw==
X-Gm-Message-State: ALoCoQk9BFb3OQh2HxhuaceaREvDG1V96thAD5Rti/uXh3HCJLFSJ7RpaFLCY2ZjPsamJoy15QfN
MIME-Version: 1.0
X-Received: by 10.25.145.80 with SMTP id t77mr10348552lfd.88.1447530972084; Sat, 14 Nov 2015 11:56:12 -0800 (PST)
Received: by 10.112.144.106 with HTTP; Sat, 14 Nov 2015 11:56:11 -0800 (PST)
In-Reply-To: <616EAB9D-3E23-40A1-822F-D49D9E8BC37C@gmail.com>
References: <CABCOCHQmW34gjQ3zrhLvk3a1zYk5LFftLfTgy+rPq1skCbqhXA@mail.gmail.com> <007101d114e8$e56e3bf0$b04ab3d0$@ndzh.com> <616EAB9D-3E23-40A1-822F-D49D9E8BC37C@gmail.com>
Date: Sat, 14 Nov 2015 11:56:11 -0800
Message-ID: <CABCOCHSnRkiFmUDtjJj9J29MhEPRsnOAtMCLszBPyrNjGOG-xA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Dean Bogdanovic <ivandean@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140203a64928305248591fe
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/Xd9HqEl7-paHe-JJa79VLByVMI4>
Cc: i2rs-proto-dt@ietf.org, Susan Hares <shares@ndzh.com>
Subject: Re: [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: Sat, 14 Nov 2015 19:56:16 -0000

Hi,

I have more questions ;-)
I want to help Susan get a good draft out soon.

Maybe the I2RS priority model is easy to describe using the thermostat.

Susan's daughter sets the "hold" button to 82 degrees F.

Susan's smartphone app is monitoring the /thermostat resource and gets
and update that the hold-button is now set to 82.

Susan's phone now sets the hold-button to 72.  Since Susan has the
highest priority, her edit is accepted by the I2RS agent.

Her daughter's smartphone app is monitoring the /thermostat resource and
gets
and update that the hold-button is now set to 72.

She tries to set it to 82 again and gets an error.
The /thermostat resource is not altered.

Susan eventually deletes the "hold 72" data.
The thermostat goes back to normal program (running config).
The previous client setting of 82 is long forgotten.

Is this the correct model? Seems OK to me. No caching is done.

Is it completely up to the client to subscribe to the /thermostat resource
or is the
I2RS agent expected to automatically subscribe the client to the target
resource?


Andy



On Sun, Nov 1, 2015 at 1:32 PM, Dean Bogdanovic <ivandean@gmail.com>; wrote:

> I support Andy's comments
>
> On Nov 2, 2015, at 06:04, Susan Hares <shares@ndzh.com>; wrote:
>
> Andy:
>
>
>
> 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?
>
>
>
> Sue
>
>
>
> *From:* I2rs-proto-dt [mailto:i2rs-proto-dt-bounces@ietf.org
> <i2rs-proto-dt-bounces@ietf.org>] *On Behalf Of *Andy Bierman
> *Sent:* Sunday, November 01, 2015 3:36 PM
> *To:* Susan Hares; i2rs-proto-dt@ietf.org
> *Subject:* [I2rs-proto-dt] I2RS meeting
>
>
>
> 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
>
>
>
> _______________________________________________
> I2rs-proto-dt mailing list
> I2rs-proto-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs-proto-dt
>
>