[{"author": "Kent Watsen", "text": "
Thank you Joel!
", "time": "2022-11-08T09:31:11Z"}, {"author": "Joel Jaeggli", "text": "thanks lou!
", "time": "2022-11-08T09:31:18Z"}, {"author": "Kent Watsen", "text": "Thank you, Jason!
", "time": "2022-11-08T09:31:23Z"}, {"author": "Scott Mansfield", "text": "samans
", "time": "2022-11-08T09:48:25Z"}, {"author": "Carsten Bormann", "text": "Power failure in right front corner?
", "time": "2022-11-08T09:52:28Z"}, {"author": "Robert Wilton", "text": "They have had presentation issues in DNSOP, so have moved on to another presentation, but I will need to step out again, probably in about 15 mins time
", "time": "2022-11-08T09:57:21Z"}, {"author": "Robert Wilton", "text": "Sorry!
", "time": "2022-11-08T09:57:33Z"}, {"author": "Lou Berger", "text": "@rob no problem
", "time": "2022-11-08T09:59:09Z"}, {"author": "Kent Watsen", "text": "agree w/ Balazs regarding that documenting the behavior helps to reduce special cases
", "time": "2022-11-08T10:01:11Z"}, {"author": "Robert Wilton", "text": "Stepping out again now
", "time": "2022-11-08T10:06:01Z"}, {"author": "Beno\u00eet Claise", "text": "Bill, regarding time/date in YANG , should be generic, or within this ACL YANG module? The former, I guess, no?
", "time": "2022-11-08T10:20:06Z"}, {"author": "Kent Watsen", "text": "I do not disagree - this WG is okay
", "time": "2022-11-08T10:30:26Z"}, {"author": "Bill Fenner", "text": "@Beno\u00eet Claise that's a good point too - capture the complexity of recurring events in another module, and refer to it from here.
", "time": "2022-11-08T10:33:38Z"}, {"author": "Beno\u00eet Claise", "text": "@bill, yes, to be reused in ACL, QoS, Service configuration, etc... Hopefully, it won't be too complex/too long to standardise ... We don't want the SUPA experience again :-)
", "time": "2022-11-08T10:35:53Z"}, {"author": "Qin Wu", "text": "@benoit, good question, my impressionis generic, will coordinate with ACL extension authors about this.
", "time": "2022-11-08T10:58:26Z"}, {"author": "Qin Wu", "text": "@benoit, that is not the intention to go to that complexity, but point taken
", "time": "2022-11-08T11:00:35Z"}, {"author": "Carsten Bormann", "text": "If there is a \"don't do this\", I want a tool to support this.
", "time": "2022-11-08T11:16:16Z"}, {"author": "Robert Wilton", "text": "@Carsten, as you mean you want the tool to reject this as valid?
", "time": "2022-11-08T11:17:28Z"}, {"author": "Robert Wilton", "text": "Sorry, do you mean that you want the tool to reject this?
", "time": "2022-11-08T11:17:52Z"}, {"author": "Jason Sterne", "text": "Not sure how easily a tool can find & reject/accept these trees. That requires having access to all (or a large set) of the revisions of a module and analyze the relationship amongst them all. We were more thinking of the tool as working on 2 revisions of a module to compare them.
", "time": "2022-11-08T11:23:02Z"}, {"author": "Robert Wilton", "text": "@Jason, I think that for \"sensible\" semver versions, it should just be possible to check against the previous version in the file.
", "time": "2022-11-08T11:28:25Z"}, {"author": "Jason Sterne", "text": "Maybe - but I'm not sure that analysis can differentiate/identify any of these good vs bad trees. To be analyzed...
", "time": "2022-11-08T11:31:23Z"}]