Architecture, Semantic and Behavior

Date

7am PDT | 10am EDT | 14:00 UTC | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST |


Web Conference:

Please use this link (thanks to Telefonica)  

Attendees

(please feel free to correct, update your names (wink) Thank you very much!!!) 

Info to: 

Goals

  • going forward

Discussion items

TimeItemWhoNotes
00:00YangAlex Stancu

pyang warning for must statement - link to issue - eth32

How to address?

@Prathiba: Could you please check how such 'must' statement and 'path' statement is generated by UML2YANG and what may need to change. 

@Mark: May I kindly ask you to check if the yang syntax is supported by ODL.

@Leo; @Roberto; @Leo; @Daniela; @Nader: Could you please check, if your NetConfServer framework support the xPath function "deref(.)".

00:30

dropping-behavior-kind on device/switch level - link to issue - eth30

AI: Danilo PalaMichael BinderDaniela Spreafico: Please provide options how to solve the issue and a recommendation for discussion next week. 

We think there are more attributes.

Please comment the issue to get forward. 

00:35

radio-signal-id: proposal of simplification - link to issue - air39

Answer: 

The comment of the expectedRadioSignalID attribute should get additional phase "Only relevant, if expectedEqualsTransmittedRadioSignalID==false.".


AI: Martin think where in TR docs such "rule" are documented. 


Other similar cases:

config attribute, where the device supports only one value.

e.g. Maintenance Timer: 

should be handled in future.


AI: should be agreed in ONF 5G-xHaul.

Action items