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

Hi Kent, all,

My main concern with this more general model is whether this model has the right structure to generically model device capabilities.

It is often the case that hardware capabilities might differ by the linecard type that has been inserted (which can change dynamically), and/or the type of interface.

As it stands, I don't think that the current model can describe capabilities for this class of devices:
 - per datastore capabilities are not granular enough
 - per datanode capabilities are too granular (e.g. you would end up with separate capabilities for each interface, and even then they can only describe the interfaces that exist, or might exist).

Possibly, having a xpath selector to identify the set of nodes that the capabilities apply to might be flexible enough, but this would greatly increase complexity.  Perhaps something like a union of a node selector and xpath selector could work?

I don't want to slow work down, but I do question whether we are rushing to a generic capability solution that won't be sufficient for many devices out there.  Hence part of me wonders whether it might be better to get the original notification capabilities draft finished (as a time to market solution), and then look at the generic capabilities requirements/solution with a bit less time pressure.

Thanks,
Rob

-----Original Message-----
From: netconf <netconf-bounces@ietf.org> On Behalf Of Kent Watsen
Sent: 07 January 2020 13:05
To: NETCONF Working Group <netconf@ietf.org>
Subject: Re: [netconf] New Version Notification - draft-ietf-netconf-notification-capabilities-09.txt

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, internet-drafts@ietf.org wrote:
> 
> 
> A new version (-09) has been submitted for draft-ietf-netconf-notification-capabilities:
> https://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-c
> apabilities-09.txt
> 
> 
> The IETF datatracker page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-notification-capab
> ilities/
> 
> Diff from previous version:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-notification-capa
> bilities-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
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf