There may be some restrictions on the use of those keywords that I
missed. But from what I can tell. those tools let us say that item A
references and uses the values from item B. (The require part is not
actually spelled out in our requirements, but is a useful tool.) This
seems to match teh primary mode we called for. It does not handle some
of the other cases. I don't think this has anything to do with
ephemeral vs config vs operational.
Yours,
Joel
On 9/17/14, 7:12 PM, Susan Hares wrote:
Joel and Jeff:
Can you comment on why and why not you consider "instance-identifier" and
"require-instance" yang key words to satisfying the requirements for object
relationship requirements? Are you both assuming a configuration state
datastore in which one instance is "config true tagged empheral" and a
second instance is tagged "config" without the empheral tag?
Sue
-----Original Message-----
From: i2rs [mailto:[email protected]] On Behalf Of Joel M. Halpern
Sent: Friday, September 12, 2014 5:22 PM
To: [email protected]
Subject: Re: [i2rs] I-D Action:
draft-haas-i2rs-netmod-netconf-requirements-00.txt
Thanks for doing this Jeff. It is a great start.
The Object Relationships issue does need more work however.
Some of the cases are handled...
YANG's tools for reuse can be used to meet the inheritance requirements.
I think that the requires and when clauses are probably powerful enough to
meet the architecture requirements for optionality (arch 6.4.5.2).
I do not know of anything in YANG that corresponds to agent side templating,
as was agreed by the working group and captured in arch 6.4.5.3. (Since I
am one who argued against this, if we need more detailed examples I would
appreciate some assistance.)
The object relationships are three piece. Arch 6.4.5.4.2 on correlation and
arch 6.4.5.4.3 on actual references seem to be covered by various parts of
YANG. But the initialization reference described in arch
6.4.5.4.1 does not correspond to anything I know of in YANG. Is there a
YANG tool for that? This is the case where the definition of an object Foo
says that whenever a new Foo is created, it takes its initial values from an
instance of Bar, so as to simplify instantiation. This is similar too, but
not the same as the templates material.
You talk about the priority requirements. You should probably mention the
multi-headed behavioral requirements there (as I think that the resolutions
will be tightly coupled.)
Section 7.9 of the archtiecture document talks about several transactional
scopes. The text you have does not seem to deal with all of these. Does
YANG handle them all easily?
Yours,
Joel
On 9/12/14, 4:59 PM, [email protected] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
Title : I2RS requirements for netmod/netconf
Author : Jeffrey Haas
Filename : draft-haas-i2rs-netmod-netconf-requirements-00.txt
Pages : 10
Date : 2014-09-12
Abstract:
This document covers requests to the netmod and netconf Working
Groups for functionality to support requirements to implement the
I2RS architecture.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requir
ements/
There's also a htmlized version available at:
http://tools.ietf.org/html/draft-haas-i2rs-netmod-netconf-requirements
-00
Please note that it may take a couple of minutes from the time of
submission until the htmlized version and diff are available at
tools.ietf.org.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
_______________________________________________
I-D-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
