Dear all,

I have a clarification question wrt the requirement 6

  6.  Ability to relate configuration with its corresponding
       operational state

       A.  Ability to map intended config nodes to corresponding applied
           config nodes

       B.  Ability to map intended config nodes to associated derived
           state nodes

       C.  The mappings needs to be programmatically consumable

From the appendix A, we can see that this requirement comes from draft-openconfig-netmod-opstate-01 <https://tools.ietf.org/html/draft-openconfig-netmod-opstate-01>, Section 4.5 <https://tools.ietf.org/html/draft-chairs-netmod-opstate-reqs-00#section-4.5> Re-reading this section 4.5, I understand 6A and 6C, but is 6B also required? Do we need to make the link between a config node and all the derived counters/statistics it influences, which might be in different YANG models btw?

Regards, Benoit
The AD and chairs thought it best to formalize the consensus on the
requirements a bit more.  So we created the I-D listed below to track and
capture final consensus.

Additionally, we want to use this GitHub issue tracker to track issues:

        https://github.com/netmod-wg/opstate-reqs/issues

Consistent with Tom's earlier email, we want to collect any issues with
these requirements before EOB Monday, September 14, 2015 at 5PM EST.  If
you have an issue, in addition to posting it to the list, please consider
adding it to the GitHub tracker, and let people know you did so.   Our
goal is to close the issues as quickly as possible, some will go to DEAD
while others may remain OPEN, based on WG consensus.

Thanks,
Kent & Tom


On 9/11/15, 5:36 PM, "internet-dra...@ietf.org" <internet-dra...@ietf.org>
wrote:

A new version of I-D, draft-chairs-netmod-opstate-reqs-00.txt
has been successfully submitted by Kent Watsen and posted to the
IETF repository.

Name:           draft-chairs-netmod-opstate-reqs
Revision:       00
Title:          NETMOD Operational State Requirements
Document date:  2015-09-11
Group:          Individual Submission
Pages:          5
URL:
https://www.ietf.org/internet-drafts/draft-chairs-netmod-opstate-reqs-00.t
xt
Status:
https://datatracker.ietf.org/doc/draft-chairs-netmod-opstate-reqs/
Htmlized:
https://tools.ietf.org/html/draft-chairs-netmod-opstate-reqs-00


Abstract:
   This document captures consensus on operational state requirements by
   the NETMOD working group.


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.

The IETF Secretariat

_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to