TAPI Call: 2 hours - tentative considering that we enter in vacation period for many attendees. To be checked the day before.
Tentative, depends on attendee availability to be checked the day before.
|10 mins||Announcement||Arturo Mayoral|
Arturo Mayoral announces that his collaboration to the TAPI team will end with this year end.
Victor Lopez confirms that Telefonica will continue to contribute to the TAPI project, no change in our priorities.
Ramon Casellas will continue his collaboration in the TAPI project.
All the team is really sorry for Arturo leaving, recognising his fundamental contribution to TAPI development and consolidation.
Thanks to Arturo Mayoral the TAPI project has been successfully developed above and beyond the conceptual model. TR-547 is a milestone which enables really interoperable implementations.
|20 mins||New version of TR-547||Arturo Mayoral|
Arturo Mayoral presents the draft of the new version of TR-547
which are not generated by the tool, see YANG to OAS tool does not generate GET with potentially multiple replies (#497), considering that same result is achievable leveraging field and depth based filtering (e.g. /tapi-common:context/tapi-connectivity:connectivity-context/ shall include in the reply all ConnectivityServices and their CSEPs).
|10 mins||Some clarifications on Restconf/depth||Andrea Mazzini|
Andrea Mazzini confirms that the depth filtering can be sistematically applied to any API, but considering that in case of complex data types it may be necessary a full depth to get all values.
Restconf Issue 501
Andrea Mazzini shows the results of some tests.
Continue discussion on OTU(+ODUCn) CEP/CSEP as single point for OTU/OTSiA ConnectivityService provisioning