Re: [netconf] New Version Notification - draft-ietf-netconf-notification-capabilities-09.txt

[Balázs Lengyel <[e-mail]>]

-----Original Message-----
From: netconf <[e-mail]> On Behalf Of Martin Bjorklund
Sent: 2020. január 9., csütörtök 12:44
To: [e-mail]
Subject: Re: [netconf] New Version Notification - draft-ietf-netconf-notification-capabilities-09.txt

Hi,

I think this document is heading in the right direction.  However, I think we need to clarify how these "system capabilities" are different from NETCONF and RESTCONF capabilities.  Also define the terms "system capability" and perhaps "protocol capability" (to make the distinction clear).  Then use "system capability" instead of just "capability" in the doc.


BALAZS: What would be your definition?
I wanted to use a term that is as broad as possible because:
- we can leave the definition of specific capabilities to other RFCs, so there is no need to be too specific here
- it is not just NETCONF and RESTCONF. We are already working on draft-ietf-netconf-https-notif which brings in HTTP; we might have capabilities that define e.g. the logging file sizes or really anything. We do not want to restrict the possibilities now. Later we may decide that logging file sizes belong here or maybe not.
I am at loss how to define system capabilities: "Any capability of the system implementing the server or the publisher."  Does that really add any information?

It says:

       System capabilities may include capabilities of a
       NETCONF or RESTCONF server or a notification publisher.

I think that this is not correct; they describe the capabilities of a server (where the term "server" is as defined in RFC 8342).


BALAZS: We do want to ALSO include publisher capabilities. E.g. The minimum (reporting) period or the maximum-number of changes per  notification is not a capability of the server. It is the capability of the publisher. Do you want to remove the words "RESTCONF or NETCONF" ?


The document says that system capabilities can be specified "on system/publisher level, datastore level or for specific data nodes".

[edit: s;/publisher;; since it is now more general than notifs]

But you don't actually specify anything on the datastore level; this is done by doing a normal data node capability for the root node.
This is not explicitly stated but kind of implied.  I suggest that this is either removed, or made explicit.

BALAZS: It is stated in the module:
"The special value '/' denotes all data nodes   in the datastore."
I will also add a sentence:
OLD:
Capability values can be specified on system/publisher level,
   datastore level or for specific data nodes (and their contained sub-
   tree) of a specific datastore.  Capability values on a smaller, more
   specific part of the system's data always override more generic
   values.
NEW:
Capability values can be specified on system/publisher level,
   datastore level (BY SELECTING ALL NODES IN THE DATASTORE) or for specific data nodes (and their contained sub-
   tree) of a specific datastore.  Capability values on a smaller, more
   specific part of the system's data always override more generic
   values.
/martin

Kent Watsen <[e-mail]> wrote:
> 
> Dear WG,
> 
> This is a fairly substantial update that defines a generic 
> "ietf-system-capabilities’
> module and a separate "ietf-notification-capabilities” module that 
> augments into it.
> 
> We could start WGLC #2 now, but it would be good to get a few 
> high-level reactions from the WG before doing so.
> 
> Please provide comments as to if you believe the draft is ready for 
> WGLC #2.
> 
> Thanks,
> Kent // as shepherd
> 
> 
> > On Jan 7, 2020, at 3:28 AM, [e-mail] wrote:
> > 
> > 
> > A new version (-09) has been submitted for
> > draft-ietf-netconf-notification-capabilities:
> > https://www.ietf.org/internet-drafts/draft-ietf-netconf-notification
> > -capabilities-09.txt
> > 
> > 
> > The IETF datatracker page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-netconf-notification-cap
> > abilities/
> > 
> > Diff from previous version:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-notification-ca
> > pabilities-09
> > 
> > Please note that it may take a couple of minutes from the time of 
> > submission until the diff is available at tools.ietf.org.
> > 
> > IETF Secretariat.
> > 
> 
> _______________________________________________
> netconf mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netconf
_______________________________________________
netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf