Re: [netmod] FW: New Version Notification for draft-chairs-netmod-opstate-reqs-00.txt - REQ 6 clarification

Thanks Rob, that clarifies the situation for me. Regards, Benoit On 14 September 2015 at 08:43:53, Benoit Claise (bcla...@cisco.com) wrote: 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

Re: [netmod] FW: New Version Notification for draft-chairs-netmod-opstate-reqs-00.txt - REQ 6 clarification

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

Re: [netmod] FW: New Version Notification for draft-chairs-netmod-opstate-reqs-00.txt - REQ 6 clarification

On 14 September 2015 at 08:43:53, Benoit Claise (bcla...@cisco.com) wrote: > 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

Re: [netmod] FW: New Version Notification for draft-chairs-netmod-opstate-reqs-00.txt - REQ 6 clarification

Rob, thanks for clarifying the need for 6B. No new GitHub issues filed for this thread. Kent On 9/14/15, 10:16 AM, "Rob Shakir" wrote: > >On 14 September 2015 at 08:43:53, Benoit Claise (bcla...@cisco.com) wrote: > >> Re-reading this section 4.5, I understand 6A and 6C, but is