ONF presentations to ETSI NFV Info Modelling Industry Status ONF Modeling Update 29 March 2016 Note that some points are related to the Multi-SDO Issues documented in NFV(16)000031r3 using notation [MSDO #]

IM WS Result Sharing & Feedback The ONF Information Modelling Team’s effort and achievement in the Workshop was well recognized by the ONF Overall observation There is a recognition that there is a problem and some dawning recognition that information model work may hold some part of the answer to the problem ONF/ITU-T/MEF/TMF collaborative working is strengthening but there are still challenges getting agreement to work as one (governance) [MSDO 11, 16 and 49] ONF/MEF/TMF members are working as closely as allowed by current mandates to maintain and strengthen alignment We can make progress with NFV joining models but this will take significant effort. It would appear worth the effort (with the usual governance challenges) [MSDO 8 and 18] Some members are actively working to help further alignment Specific MSDO follow-up: With NFV: post WS on 1/14 as well as ad-hoc discussions and member contributions to promote alignment [MSDO 8 and 18] With TOSCA: Face to face post WS on 1/14 and at ONF MWD as well as several calls [MSDO 44, 41 and 43]

Progress of IM/DM Work in ONF since 1/2016 WS Infrastructure and Tooling (ONF initiated open project activity – Eagle (see next slide)) [MSDO 20 and 32] Open Model Profile enhancement (used by ETSI NFV, ONF, MEF etc) – Artefact lifecycle state, … UML modelling guidelines updated UML-YANG mapping guidelines updates and tooling enhanced (both ONF and MEF teams are using the tooling) Initial work on the Pruning and Refactoring guidelines Core model enhancement in progress [(related to) MSDO 30] State model Capacity model Topology model Protection model (uses controller model)t Ltp/Lp Spec model Transitional link model Physical equipment model Refactoring the NE (uses controller model and physical equipment model) Controller model [MSDO 12 (IM work)] Operation normalization and common pattern extraction Interface oriented models [(related to ) MSDO 26 and 32] Intent work are progressing [(related to) MSDO 41 and 43] Tapi work progressing using pruning and refactoring approach and is generating the interface schema using the UML-Yang tooling [MSDO 12b]

Progress of IM/DM Work in ONF since 1/2016 WS (cont.) Continue to move work to Open Source [MSDO 20, 12b and 32] https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools Open Model Profile https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools/tree/OpenModelProfile UML Tools: https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools/tree/UmlTools Papyrus guidelines Pruning and refactoring guidelines UML modelling guidelines UML-YANG Tools: https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools/tree/UmlYangTools xmi2yang tool-v1.3 UML-Yang Mapping Tool User Guide-v1.3 JSONCode Tools: https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools/tree/JsonCodeTools Issues list: https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools/issues

Progress of IM/DM Work in ONF since 1/2016 WS (cont.) Informal Inter SDO Open Model Initiative (IISOMI) [MSDO 20, 12b and 32] Held internal preparation call For the setup of an “Informal Inter-SDO Open Model Initiative” which can collaboratively develop the work contained in the Open Source EAGLE project Two teams Modelling infrastructure (Tool & Guidelines) Subject matter (Core Model) Working method Participants need mandate from their SDOs regarding major bug fixes and content changes EAGLE workflow Frequency and moderation of conference calls Documentation ownership and versioning Versioning Ownership and IPR and Copyright SDO experts contacted: ITU-T SG15, ETSI-NFV, TMF, MEF

Feedback on Multi-SDO Issues spread sheet (NFV(16)000031r3.xlsx) Provided, to the NFV_MULTISDO mailing list on 24 (25) Feb, a commented version focussing on areas of particular interest to ONF Most areas are touched on in the earlier slides The following items are not fully covered by the earlier slides [MSDO 12] Overlapping control/management architectures, [MSDO 40] Lack of common architecture mapping between OCC/NFV/ONF and [MSDO 43] Differences in architectures The ONF Architecture team has a strong interest in participating in such a Tiger Team but would like to see clarification of problem statement and what output might be expected. Action proposed: Multi-SDO Leadership: Stimulate definition of problem statement, team mandate and output. Multi-SDO participants: In the interim prior to formalization of the Tiger Team activity make others aware of specific multi-group architecture activities, their scope an conclusion. [MSDO 20] Lack of translation from IM to DM, [MSDO 12b] Interfaces are generated by hand inconsistently and [MSDO 32] Lack of translation from IM to DM The ONF IM team has chosen to not use the term Data Model due to ambiguity in the definition of the distinction between IM and DM (see RFC3444). As a consequence the term Information Model is used for any representation of things/properties/relationships. The ONF IM team has chosen to use UML for all such cases. Clearly a coded solution is required. The final stage of a process is to produce runnable code, interface schema etc. The approach ONF is taking is to develop and use Open Source tooling to convert an appropriately formed UML model into an interface data schema. Multi-SDO participants: Consider use of the ONF Eagle tooling (and consider participating in its advancement). See https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools (see also ONF Proposal slide 17)

THANK YOU

Background material https://docbox.etsi.org/ISG/NFV/Open/Other/2016_01_13_NFV_Information_Modelling_Workshop-Louisville/ NFV(16)000022r1_ONF_Common_Information_Model___Core_Information_Model.pptx NFV(16)000023r1_ONF_Proposal_for_way_forward.pptx NFV(16)000024_ONF_Proposal_Summary.pptx