On Fri, Sep 8, 2017 at 3:56 AM, Juergen Schoenwaelder < [email protected]> wrote:
> On Fri, Sep 08, 2017 at 11:17:10AM +0100, Robert Wilton wrote: > > > > > > On 07/09/2017 22:23, Juergen Schoenwaelder wrote: > > > On Thu, Sep 07, 2017 at 10:51:54AM -0700, Andy Bierman wrote: > > > > I suggested the naming guideline because the NMDA design team > decided to > > > > add semantics to certain naming patterns, so authors have to be > warned. > > > > > > > > But this is a really bad idea (and slippery slope). > > > I agree. > > I think that there are really a few aspects to this: > > > > [...] > > CLRs are always created with the best intention but then they become > over time a problem. There is quite some experience with this. > > yes -- naming conventions are fine but they cannot be used by automation tools. The YANG language says these strings have no meaning so tools cannot count on them to have any meaning. The issue here is whether there are standard extensions to tag YANG modules or whether each tool vendor will have their own extensions instead. It is not critical that the IETF provide these YANG extensions, but they will get used one way or another. CLRs always start out as clever little rules. They usually turn to something else only after some time. /js > > Andy > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
