Time | Item | Who | Notes |
---|---|---|---|
5 min | Admin: Call plan | All | Leader: Kam; (Not available: ) Leader: Bernd; (Not available: ) Leader: Scott; (Not available:) Leader: Kam; (Not available: ) Leader: Cancelled Leader: Nigel; (Not available: ) Leader: Scott; (Not available: Kam) (May adjust to 8:00 PST to accommodate Kam) Leader: ; (Not available: Kam) Leader: ; (Not available: Kam) Leader: ; (Not available: Kam, Scott) Leader: ; (Not available: Scott) |
0 min | Action items due/done | All | Not discussed at this meeting. Deferred to next meeting. IISOMI Action Items done or past due Action items done: Due dates of the following action items updated: |
25 min | YANG enhancement | SM | Scott brought up to our attention that in IETF, there is an individaul I-D "YANG Extension and Metadata annotation for Immutable Flag"
|
30 min | UML <target> to YANG augment statement mapping | All | Question: To find out if the tool is inferring the augment path from the composition associations OR form the target property of the «Specify» association.
Answer: Scott found out that the tool infers from the target property of the «Specify» association. yangification: So, not inferrring from the containment tree. Just by the target path, in each element it takes the first component (module name) and the third component (member end name) and then yangify. No intelligent at all. However, the tool doesn't check whether the class (the middle component) is abstract or concrete. |
1 min | Concrete vs abstract augmenting classes | All | Minutes added to Bernd noted that so far the guideline recommends only dealing with abstract augmenting class. |
x min | AOB | none |