With all the deprecating of "-state" trees going on these days, the 'status' statement is getting lots of use.
I understand that some feel that the status statement needs to be placed on every node, since it is not inherited. This sentiment likely stems from RFC 7950 stating "If no status is specified, the default is current" and, of course, it not stating that status is inherited. I appreciate that this is just following rules, but it seems excessive and I don't understand how any other interpretation makes sense. Also I question how it's supposed to work for a grouping that is used once in a deprecated tree and again in a not deprecated tree. What if the grouping is defined in another RFC? Would we need to copy the grouping into the current module in order to set status deprecated on all of its nodes? Kent // contributor _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
