Re: [I2rs-proto-dt] I2RS meeting

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
>
>