Open Information Model & Tooling OIMT Call Agenda & Minutes / 31 August 2017 (IM-D = 03 – 04 PT) (IM-E = 05 – 06 PT) (IM-F = 07 – 08 PT) Nigel DAVIS (Ciena) & Kam LAM (FiberHome) onf.oimt2017.xxx_2017.08.31_minutes.00

Slots, Topics, Participants & Recording IM-D (Thursday 3:00 – 4:00 am PT) Administrative ) Andrea MAZIZINI (Nokia) Augie JAGAU (Ericsson) Bernd ZEUNER (DT) Chris HARTLEY (Cisco) Claudine (?) Italo BUSI (Huawei) Kam LAM (Fiberhome) Karthik SETHURAMAN (NEC) Malcolm BETTS (ZTE) Nigel DAVIS (Ciena) Qilei WANG (ZTE) Rod LU (ZTE) Scott MANSFIELD (Ericsson) Sibylle SCHALLER (NEC) Xiang YUN (Fiberhome) Yuji TOCHIO (Fujitsu) Apologies IM-E (Thursday 5:00 – 6:00 am PT) TAPI, WT, IMP joint discussion ) Andrea MAZIZINI (Nokia) Bernd ZEUNER (DT) Italo BUSI (Huawei) Kam LAM (Fiberhome) Karthik SETHURAMAN (NEC) Malcolm BETTS (ZTE) Martin SKORUPSKI (Telefonica) Nigel DAVIS (Ciena) Qilei WANG (ZTE) Rod LU (ZTE) Scott MANSFIELD (Ericsson) Xiang YUN (FiberHome) Yuji TOCHIO (Fujitsu) Apologies IM-F(Thursday 7:00 – 8:00 am PT) TAPI, WT, IMP joint discussion ) Andrea MAZIZINI (Nokia) Bernd ZEUNER (DT) Italo BUSI (Huawei) Kam LAM (Fiberhome) Karthik SETHURAMAN (NEC) Malcolm BETTS (ZTE) Martin SKORUPSKI (Telefonica) Nigel DAVIS (Ciena) Qilei WANG (ZTE) Rod LU (ZTE) Scott MANSFIELD (Ericsson) Xiang YUN (FiberHome) Yuji TOCHIO (Fujitsu) Apologies IMP Work Items: onf2017.154 IMP Work Item Scopes: onf2017.159 Time zone mapper: http://www.timeanddate.com/worldclock/fixedform.html

Agenda IM-D: Admin Updates on 1.3 docs progress November 6-10 ONF meeting December 4-8 Invited meeting Resource transition ARO & Webex tool decommissioning and archiving Mailing list, Conference, Document repository, GitHub Discuss OIMT Wiki child page structure, including IISOMI IM-E: ODU Spec Model for TAPI 2.0 IM-F: OTSi Spec Model for TAPI 2.0

Administrative IM-D

Update on TR-512 v1.3 Review Content Reviewer Comments 512.1 Overview KL 512.2 Forwarding  Term MB, AM, CH, MB, CH 512.3 Foundation RL, CH 512.4 Topology CH, RL 512.5 Resilience AM 512.6 Physical KL, CH 512.7 Spec KS, AM, CH CH 512.8 Control CH, KS CH, QW 512.9 OAM   512.10 Operations Pattern KS 512.11 PC CH, KL 512.A.1 512.A.2 Patterns MB, [CH] 512.A.3 Rationale <none> 512.A.4 Media MB 512.A.5 Layer 1-2 512.A.6 Layer 2-3 512.A.7 512.A.8 Timing 512.A.9 512.A.10 KS, AM 512.A.11 512.A.12 Application 512.DD Data Dictionary BZ, XY BZ, XY DD, Gendoc 512.TM Terminology Mapping 512.GT Template 512.FE Further Enhancements Red initials: Have not provided comments yet Yellow box: Will be exposed as no review comment Brown item: For 1.3.1 Brown item: For 1.4 8/31/2017 Status Nigel is still working on addressing the received comments and aiming for release in September Approval procedure still needs clarification, re Project TST vs ONF TST

IMP Transition to OIMT Announcement IMP and Project EAGLE are being transitioned into the OIMT Project 9/8/2017 decommissioned & archived Tools Mailing List (hosted on ARO) Document Repository (hosted on ARO) Scheduled Conferences (webex sessions and licenses) Causeway (OSSDN management site) New tools Project Page: https://www.opennetworking.org/projects/open-information-model-tooling/ Mailing Lists: information-modeling@opennetworking.org Will have a separate list for IISOMI: iisomi@opennetworking.org Document Repository https://rs.opennetworking.org/wiki/pages/viewpage.action?pageId=259325962 Documents from ARO will be imported into this wiki Conferences (uberconference.com) Create and use free version for 10 or fewer participants https://www.uberconference.com/opennetworking support 10+ Meeting Link: https://www.uberconference.com/opennetworking Dial in: 888-534-9311 & 650-389-9884 NOTE: Use Chrome to screen share GitHub will remain active.

IMP Transition to OIMT OIMT Wiki Space Links Mission & Charter Publication: https://www.opennetworking.org/software-defined-standards/models-apis/ Presentations Meeting Calendar GitHub Mailing List Child pages Meeting logistic and notes Modeling IISOMI (could use the same structure as in the OSSDN community) UML Modeling Guidelines Papyrus and GitHub Guidelines UML  YANG Mapping Guidelines & Tool UML  Open API (JSON) Mapping Guidelines & Tool

IMP Transition to OIMT Feedback from the group ARO document repository It was noticed Chris and Kam’s documents are no longer in the ARO, while documents of other people are still in ARO It seems that these are the IMP documents It was suggested to keep the ARO documents be still accessible in ARO. Uber Conference Right now there is no need to enter a pin in order to join the call. Feedback from the group is that, it is better to require entering a pin in order to join the call. This is for better control although our calls are supposed to open to all. Regarding recording, right now it is automatically recorded once the call starts. The feedback is that let the host/organizer to manually start/pause the recording during the call session. The host/organizer should also be able to mute the participants. This needs a host/organizer specific pin

November (6-10) ONF Meeting Same as shared on the Tuesday IM-A call CORD Build Event: November 7 – 9 (Tuesday – Thursday) Venue Google Facility: Quanta Cloud Technology (QCT), 1010 Rincon Circle, San Jose, CA 95131 Schedule: http://cordbuild.org/?page_id=17 https://cordbuild2017.sched.com/overview/type/Project+Feeder+Track?iframe=yes&w=100%&sidebar=yes&bg= no Work plan: There will be a specific track for the Open Transport (OT) and Open Information Modeling/Tooling (OIMT) projects Wednesday morning: We have a presentation; this will be on the CORD Build agenda Wednesday afternoon: We have a track for TAPI and Core IM; this will be on the CORD Build agenda Tuesday and Thursday we have a large room for us to work; this will NOT be on the CORD Build agenda Science fair stand for demo, 2 hours per day at lunch time on Tuesday, Wednesday, & Thursday Registration: CORD Build: http://cordbuild.org/ Now open. Free for ONF members Monday and Friday registration: TO BE PROVIDED OT and OIMT Projects interim meeting: November 6 – 10 (Monday – Friday) Venue and host for Monday and Friday: ONF Lab The Glass conference room has been reserved, which can hold1 0-12 people comfortably Monday 9:30 – 18:00; Friday 8:00 – 18:00 Expect less than 20 Invitation letter template for visa application: onf2017.132.00 

December (4-8) and Invited Q14/15 Meeting Same as shared on the Tuesday IM-A call Dec 4 – 8, 2017 London ITU-T Q14/15 Interim Meeting; ONF experts are invited Focus will be on Transport Ethernet OAM YANG (G.8052.1) and alignment with IEEE CFM YANG Photonic model (G.media-mgmt) Synchronization management model (G.sync-mgmt.) Logistic Stephen will handle the Ciena invitation letter for visa application Two rooms booked for 30 people (18 and 12) Monday morning till Friday noon Register with ITU-T January 27, 2018 (Saturday) Geneva Joint IEEE 802.1, IEEE 802.3, and SG15 Workshop One of the four sessions focusing on management of Ethernet Current status 15 minutes demo on Pruning & Refactoring and conversion to YANG Scott noted that there are 6+ YANG model projects in IEEE Bridge, LLDP, CFM, and couple of other, based on Clause 12 of 802.1aq Can carry on with more conversation and work (a drafting session)

Joint TAPI/WT/IM IM-E ODU Spec model for TAPI 2.0

ODU Spec Model for TAPI 2.0 (8/31) Karthik presented the latest ODU Spec model Action Item – Karthik: To commit the latest ODU Spec model to Snowmass Action Item – Bernd: To generate Data Dictionary from the committed ODU Spec Model Action Item – Italo: To update the comment Excel based on the DD from Bernd Action Item – Kam: To check the committed ODU Spec Model against G.874.1 to see whether any attributes are missing in the ODU Spec Model

Joint TAPI/WT/IM IM-F OTSi Spec model for TAPI 2.0

OTSi Spec Model for TAPI 2.0 (8/31) Karthik presented the latest OTSi Spec model Confirmed that OTSiA will be modeled, but not the OTSiG and OTSiG-O individually at this phrase Attributes of OTSi_ModDemodPac added Attributes of OTSiA_PoolPac added Media will not be modeld at this phrase Action Item – Karthik: To commit the latest model to Snowmass F n=1 OTU CEP OTU NEP OTSiA CEP OTSiA NEP Other OTSi Client NEP(s) OTSiA CtpPac OTSi ModDemodPac [1..*] selectedNominalCentralFrequency supportableNominalCentralFrequency [1..*] selectedApplicationIdentifier supportableApplicationIdentifer [1..*] OTSiA_OTU AdapPac OTSiG_O TermPac OTSiA PoolPac availableFrequencySlot [0..*] occupiedFrequencySlot [0..*] FrequencySlot is defined as centralFrequency slotWidth OTU CtpPac OTU PoolPac OTU TermPac OTU_ODU AdapPac

THANK YOU!

TAPI (8/17) TAPI SDK 2.0 Status and plan RC2 is targeted for release this week RC 3 is targeted for release next week, Call plan 8/17 IM-E: OAM model update, ODU 8/17 IM-F: ODU Spec 8/22 IM-A: OTSi Spec 8/22 IM-B/C: Resilience

TAPI (8/17) OAM Generic issues discussed MEP containment – ME or MEG? If contained by ME, how to share MEPs in rooted multi-point case? If contained by MEG, do we even need to model ME? Agreed: MEP & MIP are contained in MEG Keep ME. ME aggregate MEP & MIP Do we need an association between MEG/ME and Connection(s) ME has 1-1 relationship with Route Can we use association pointers for MEP/MIP relationship with NEP/CEP instead of augment? – question raised in MEF Should MeasurementJobs be associated with OSEP/MEP or OamService - what is the multiplicity of ProActiveJobs ? Do we flatten the MEP to be bidirectional or maintain the source/sink Pacs? What about NEP/CEP LP Pacs? Agreed: Could be flatten in the Interface model OAM technology issues (e.g. OduTcmMep/OduNcmMep augments) Do we augment the MEP/MIP or their respective source/sink Pac?

TAPI (8/17) ODU Spec model issues discussed Inheritance or composition, how much want to flattening ODU TTP Abstract, Source, Sink, Bidirectional Agreed: TAPI will flatten, i.e., merge all the sink source attribute into the abstract class The Spec class will point to the standards specification (e.g., ITU-T Rec), Operator specification, and Vendor specification The discussion confirmed that ODU_TTP is NCM MEP ODUT_TTP is TCM MEP ODUT_NIM is TCM MIP Agreed OCh can be covered in the OTSi model as special case when the group size of OTSiG (or OTSiA) is one, and thus no need to explicitly model OCh. Model OTSiA as a managed/controlled entity and is sufficient for now for TAPI RC3 and will not further expose it constituent OTSiG and OTSiG-O.

TAPI (8/10) Specification pattern Current specification pattern For example, see the Test Model on the right The “target” property of the 《Specify》 stereotype of an augmentation identifies which entity class to be augmented by the spec class. For examples: SpecOc1AugmentsOc1 Oc24SpecAugmentsOc2 and Oc24SpecAugmentsOc4 Oc5SpecAugmentsOc5 Furthermore, the 《Specify》 stereotype could have more than one targets in case the targeted entity class has more than one possible branches in the instantiation tree. For example: ObjectClass5Spec augments ObjectClass5 via the augmentation “Oc5SpecAugmentsOc5”. Its 《Specify》stereotype has two targets, Oc1-Oc2-Oc5 and Oc3-Oc4-Oc5. One will be used at run-time instantiation. Note that the targeted entity class could be global class (e.g., Oc1, Oc3) or local class (e.g., Oc2, Oc4, Oc5)

TAPI (continue) Specification pattern (continue) New specification pattern: augment global classes Augmenting the global classes, rather than the local class; such as augmenting LTP rather than LP for layer-specific information For example as shown in the right lower diagram in red MEF feedback, it is more intuitive to augment the LTP rather than the LP, easier to call out the augmentation In this way, we can remove the “target” property of the 《Specify》 stereotype since the path can be determined by the mapping tool automatically. The “support” and “condition” properties of the object class can be used to define a conditional augmentation.

TAPI (continue) Specification pattern (continue) Yet anther specification pattern: empty spec class Conditional Pacs attached to the specification class For example, in the following diagram (re-engineered from ietf-microwave-radio-link.yang), Attach XpicPair, MimoGroup and TdmConnections conditionally using the condition property Topic not discussed. For next call: TAPI OAM operations/jobs TAPI Resilience constraints

Features of 1.4 IM-F

Next releases work items Response to work items: The work item list was reviewed and updated See onf2017.154_IMP_Work-Items.02.xlsx Action items: AI – Karthik: to confirm his items AI – Nigel: to ask Chris LAUWERS if he could participate in the TOSCA related item Scope of work items: onf2017.159_IMP_work-items_scopes.02.pptx contains the scope statements from Items scoped: Chris: 2 (PC), 4 (Software), 13 (Model structure) Kam: 8 (Equipment), 15 (Model rationale) Xiang: 7 (Layer examples) Nigel: 1 (Controller), 3 (Spec), 10 (Operation pattern), 11 (Views), 14 (Topology), 16 (Pruning & Refactoring Methodology) Went through the new ones from Nigel Update version: onf2017.159_IMP_work-items_scopes.03.pptx posted AI - Leads: to provide a one slide scope for the work item