Re: [Netconf] Fwd: New Version Notification for draft-lengyel-netconf-notification-capabilities-01.txt

[Balazs Lengyel <[e-mail]>]

On 6/13/2018 10:11 PM, Eric Voit (evoit) wrote:

Hi Balazs,

 

This is good stuff.   I certainly would vote for adoption.

 

Some other thoughts:

 

Section 2

//which ones they are not/which ones are not/

BALAZS: OK

 

Not sure what “purely model driven” means.   Is this getting to the point that sometimes for a single schema, some instance data might be subscribable, and some might not?

BALAZS: Purely model driven OAM application would be something that e.g. mirrors the datastore in the NMS, but does not really care what the data means. It job is just to get the data into the NMS. As long as it has a valid model, it does not care how that has changed over time.
Yes Martin and some others wanted to handle the use-case where the capability of sending on-change notifications depends on things like 1) HW availability, HW version running the SW or 2) even the CPU load. Things that change, but not too rapidly, otherwise it becomes meaningless.

 

For implementation time information, it might be good to describe the interaction of this information with run-time on-change support markings.  E.g., is it possible for implementation time to be “Yes” and run-time to be “No”?  Should we care about this?

BALAZS: This is mentioned in the instance data draft, but also at the end of section 3.
If the information retrieved via Netconf/Restconf and the YANG
   Instance Data File conflict, the former MUST be considered
   authoritative.

 

 

Section 3.1

Instead of boolean for notification-sent-for-config-default and notification-sent-for-state-default, should there be a boolean for each datastore?

BALAZS: For config=false the answer is easy, only valid for operational.
For config=true your question is valid. However you could ask the same for the full YAM including the on-change-notification-capability list. IMO that would be an overkill.

 

Thanks,

Eric

 

From: Netconf <[e-mail]> On Behalf Of Balazs Lengyel
Sent: Wednesday, June 13, 2018 10:19 AM
To: [e-mail]
Subject: [Netconf] Fwd: New Version Notification for draft-lengyel-netconf-notification-capabilities-01.txt

 

Hello,

I submitted a new version of the draft-lengyel-netconf-notification-capabilities updated with comments from the last IETF and others. I would like to get this adopted as a workgroup item. Please review it and if you like it, please indicate that you support it as a workgroup item.

Changes:
   o  Augment only the new yanglib branch
   o  Correct the conditions for notifying about state data
   o  Corrections, clarifications

regards Balazs

-------- Forwarded Message --------

Subject:	New Version Notification for draft-lengyel-netconf-notification-capabilities-01.txt
Date:	Wed, 13 Jun 2018 01:57:58 -0700
From:	[e-mail]
To:	Alexander Clemm <[e-mail]>, Balazs Lengyel <[e-mail]>

 

A new version of I-D, draft-lengyel-netconf-notification-capabilities-01.txt

has been successfully submitted by Balazs Lengyel and posted to the

IETF repository.

Name:         draft-lengyel-netconf-notification-capabilities

Revision:     01

Title:        YangPush Notification Capabilities

Document date: 2018-06-13

Group:        Individual Submission

Pages:        10

URL:            https://www.ietf.org/internet-drafts/draft-lengyel-netconf-notification-capabilities-01.txt" rel="nofollow">https://www.ietf.org/internet-drafts/draft-lengyel-netconf-notification-capabilities-01.txt

Status:         https://datatracker.ietf.org/doc/draft-lengyel-netconf-notification-capabilities/" rel="nofollow">https://datatracker.ietf.org/doc/draft-lengyel-netconf-notification-capabilities/

Htmlized:       https://tools.ietf.org/html/draft-lengyel-netconf-notification-capabilities-01" rel="nofollow">https://tools.ietf.org/html/draft-lengyel-netconf-notification-capabilities-01

Htmlized:       https://datatracker.ietf.org/doc/html/draft-lengyel-netconf-notification-capabilities" rel="nofollow">https://datatracker.ietf.org/doc/html/draft-lengyel-netconf-notification-capabilities

Diff:           https://www.ietf.org/rfcdiff?url2=draft-lengyel-netconf-notification-capabilities-01" rel="nofollow">https://www.ietf.org/rfcdiff?url2=draft-lengyel-netconf-notification-capabilities-01

Abstract:

   This document proposes a YANG module that allows a YANG server to

   specify for which data nodes it will send "YANG Datastore

   Subscription" on-change notifications.  It also proposes to use YANG

   Instance Data to document this information in implementation time.

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

-- 

Balazs Lengyel                       Ericsson Hungary Ltd.

Senior Specialist

Mobile: [phone]              email: [e-mail] 

-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
Senior Specialist
Mobile: [phone]              email: [e-mail]