| | Update from OIF, MEF and other external activities | | OIF Demo testing to start in May - due to time constraints will use TAPI 2.0.1 although RestConf alignment in 2.0.2 seems like the future direction - esp since this aligns with MEF
OIF interest in TAPI certification - support in operator/vendor survey
- questions about what version of TAPI - TAPI will align with MEF, potentially use MEF tools in future - 2.1?
- Karthik - will need testing for multiple versions, use regression since this is a continuous process - automated testing needed - follow typical sw testing procedures
- Semantic compatibility rather than syntactic
- what is being certified? client/server, API/functionality? TAPI/stack? Impact of SBI - OpenConfig vs. TL1
- address operator needs
MEF - MEF 59/60 SDK - still working out administrative issues - standards vs. open source process/licensing
- NRM OAM work continuing - joint with TAPI
- would like to leverage OIF interop work for MEF use cases
- similar issues such as multi-stage muxing
- Thorsten - Telefonica working on optical transponder model, similar to wireless transport model - where does this go? OTIM subproject - should work together on modeling - looking for data model for technology-specific application - sounds like OTIM work
- notes that other activities like ODTN may overlap, also need for multiple operators and vendors involved
- they will analyze to see if existing work addresses or can be extended to meet their needs
- Tracy - work needed on 4G/5G RAN model, may be done in ORAN (formerly xRAN) but want to avoid competing/overlapping models
- want to align this work within Linux Foundation Networking
- Martin - initial look at Core Model technology extension
- potentially part of 5th PoC, yet tbd - WINLAB NYC indoor/outdoor testbed, similar work in Europe? COSMOS Lite, COMET
|