Re: [netmod] WGLC on draft-ietf-netmod-node-tags-06

[Jürgen Schönwälder <[e-mail]>]

I have a problem with the term "Self-Describing Data Object Tags". It
is not clear what 'self-describing' means. RFC 8819 defines "YANG
Module Tags", i.e., tags that apply to entire modules. Perhaps this
document should be titled "YANG Data Node Instance Tags".

There should be in general a check that terminology aligns with YANG
terminology.  The document talks about 'YANG data object', which is
not a well defined term. In fact, there are three levels of tagging,
you can tag modules (RFC 8819), you can tag data nodes, and you can
tag data node instances. It seems a bit unclear to me what the WGs
strategy is here with covering all three levels.

I have not read the document in detail yet but I find the notion of
data objects and subobjects confusing. I also do not know what
"massive" data object collections are or why both objects and
subobjects can be modeled as YANG data nodes, or what the purpose of
this statement is. When I look at ietf-data-object-tags (likely also a
misnomer), then what I see is a list associating tags to anything
identifiable by a nacm:node-instance-identifier. It feels like this
document has a lot of hot air around something that is at the end
rather basic.

/js

On Fri, Apr 08, 2022 at 06:09:45PM +0000, Kent Watsen wrote:
> This message begins a Working Group Last Call (WGLC) on draft-ietf-netmod-node-tags-06, per the chair-action from the 113 session (minutes <https://notes.ietf.org/#4-Title-Self-Describing-Data-Object-Tags-10-min>).  The WGLC will close in two-weeks (Apr 22).  Here is a direct link to the HTML version of the draft:
> 
> 	https://datatracker.ietf.org/doc/html/draft-ietf-netmod-node-tags <https://datatracker.ietf.org/doc/html/draft-ietf-netmod-node-tags>
> 
> Positive comments, e.g., "I've reviewed this document and believe it is ready for publication", are welcome!  This is useful and important, even from authors. Objections, concerns, and suggestions are also welcomed at this time.
> 
> Please be aware that this draft has declared IPR <https://datatracker.ietf.org/ipr/4216> indicating that license may entail possible royalty/fee. Also, this exchange between Lou and Qin on 8/30/2020 (mailman <https://mailarchive.ietf.org/arch/msg/netmod/SC6zfdYVmvlkquWOzP1qZszxWgs/>):
> 
> [Lou] Since this work is derived from work that I contributed to, I'd be interested in hearing what new mechanism(s) is/are covered by the IPR disclosure prior to supporting WG adoption.  I'm not asking in order to debate this, as that is something for other venues, I'm merely asking that you state for the record what new mechanism is covered.
> 
> [Qin] Thanks for asking, different from module level tag defined in draft-ietf-netmod-module-tags , this work provide data node level tag definition, use these data node level tag definition to provide hint or indication to selection filter in the YANG push and tell the collector or subscriber which specific category data objects needs to fetched.
> 
> 
> Kent (as co-chair)
> 

> _______________________________________________
> netmod mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netmod


-- 
Jürgen Schönwälder              Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>