On Fri, Sep 12, 2014 at 05:22:28PM -0400, Joel M. Halpern wrote: > Thanks for doing this Jeff. It is a great start.
Thanks Joel - especially for the patience. FWIW, I invite others to send edits. The xml is posted in github: https://github.com/jhaas-pfrc/I2RS-netmod-netconf-requirements > The Object Relationships issue does need more work however. > Some of the cases are handled... Agreed. This section was flagged by Alia as potentially requiring some attention but we didn't manage to get text in here. I think the biggest concern she had (trying to summarize) is that if B depends on A, when A is updated B needs to "know" that in some form. (And presumably transitive relationships such as C depends on B depends on A and A is updated...) I don't know that there's any specific action here, but certainly an open question. > 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. A number of these items seem logical and perhaps even trivial in a client-side environment. The clarity of whether/how they can be implemented in the agent is one of the reasons why the Architecture document has been not been published. > 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.) How would you distinguish the property that priority imposes on the agent from that which would come from the multi-headed case? > 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? The better question, I believe, is whether NETCONF/RESTCONF handles them appropriately for the YANG involved. Working through some of these cases with Dean B. suggested that you could get most in NETCONF and some in RESTCONF. Whether they make sense for a given use case may drive a particular application. -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
