On Sun, Sep 30, 2018 at 1:17 PM, joel jaeggli <[email protected]> wrote:
> On 9/26/18 09:23, Andy Bierman wrote: > > > > > > On Wed, Sep 26, 2018 at 9:09 AM Juergen Schoenwaelder > > <[email protected] > > <mailto:[email protected]>> wrote: > > > > > It is even worse than a step backwards. > > The draft specifies a lot of details about module tag conformance > > that needs to be present in the description-stmt. > > this seems like an important issue to square away before we move ahead. > > agreed. Also, what does it mean to match a module-tag? There is text that implies it is an opaque string and other text that suggests it is a colon-separated list of terms. It cannot really be both. > > The idea that tools must screen-scrape description statements goes > against > > everything YANG-based management is all about. YANG has extension > > statements, so we don't need to put complex syntax into comments and > > descriptions.. > > and parse descriptions for meaning. > So what the choices? 1) IANA 2) YANG extension 3) ad-hoc 4) do nothing IMO IANA has enough to do and it only covers IETF modules anyway, so (1) is out. The current approach is (3). It is slightly better than (4), but there is nothing preventing every module from declaring the module tags differently. This does not help the YANG reader (#1 priority). Only a YANG extension (or real statement in YANG 2.0) supports all modules in a way that is consistent for all readers. > > > IMO all text about module tag conformance and defining tags in > > description-stmts > > should be removed. There is no explanation why a standard YANG module > > would define multiple module-tags for the same module in the first place, > > let alone why each different tag would have different conformance > > requirements. > > > > > > > > ..... > > > > /js > > > > > > Andy > > > Andy > > > > > > -- > > Juergen Schoenwaelder Jacobs University Bremen gGmbH > > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | > Germany > > Fax: +49 421 200 3103 <https://www.jacobs-university.de/> > > > > > > > > _______________________________________________ > > netmod mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/netmod > > > > >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
