1. Kam LAM (Alcatel-Lucent) onf2015.400.00
Specifications Area – Optical Transport WG IM Modeling call & minutes – 18 August, 2015
Kam LAM (Alcatel-Lucent)
onf

2. ONF Antitrust & Intellectual Policies and Specific Guidance
This is a reminder that all Open Networking Foundation activities are subject to strict compliance with the Open Networking Foundation's Antitrust Guidelines. Each individual participant and attendee at this meeting is responsible for knowing the contents of the Antitrust Guidelines, and for complying with the Antitrust Guidelines. Copies of the Antitrust Guidelines are available at: Participants also are expected to adhere to these Guidelines in any informal meetings or social gatherings in which they might participate in connection with the activities of the Corporation.
You are required to treat the contents, notes, artifacts, and all materials associated with this meeting (including recordings) as protected by the ONF Intellectual Property Rights (IPR) policy. Do not forward any of these contents to any non ONF members. For more information on the ONF IP policy, please consult

3. Participants

4. Agenda Administrative MWD agenda topics Discussion
OTN TTP/CTP Refactoring (onf , onf )
MEP/TCM Refactoring
Ethernet attributes and maintaining alignment in the common IM and DM
Coordination across ONF, ITU-T, MEF, IEEE, IETF
Minute:
Administrative
Member Workday Agenda:
See next slide for the latest view of the draft agenda and slot assignment

5. 9/2015 Members’ Workday week – Suggested Slot Allocation
Location (See Note page)
Day /session
Architecture
Optical transport
IM (IMP & OT-IM)
Transport API
Monday 1 (09:00 – 10:30)
Room1
Room2 OTWG+IMP Joint: Papyrus guideline update, Tech-specific fragments integration into CIM
Monday 2 (11:00 – 12:30)
Room2 OTWG+IMP+TAPI Joint: Overview of LTP & FC relationship, Notification, Intent, NBI topology
Monday 3 (2:00 – 3:30)
Room2 IM+TAPI Joint: Conditional package of Topology, Use cases
Monday 4 (4:00 – 5:30)
Room2 Core model enhancement (FC, LTP, Link, FD)
Room1 Requirements
Tues Sep 8 Session 1 (8: :00)
Architecture / Intent / IM & modeling tool
Tues Sep 8 Session 1 (10: :00)
 Read-out, protocol extension, architecture,
Tues Sep 8 Session 2 (1:00 - 2:45)
X no overlap
Tooling: Git, Mars, Automation, Profile update, Common profile & tooling with other SDOs
Tues Sep 8 Session 3 (3:15 - 5:00)
Wed Sep 9 Session 1 (9: :00)
 Open-Source T-API
Wed Sep 9 Session 1 (10: :00)
no overlap with IM, NBI
Wed Sep 9 Session 2 (1:00 - 2:45)
 WM + OTWG (?)
Intent, Service (validate with Chris)
Wed Sep 9 Session 3 (3:15 - 5:00)
State
Thurs Sep 10 Session 1 (10: :30)
 X WM + OTWG (?)
Thurs Sep 10 Session 2 (1:00 - 2:30)
May joint with wireless 
Thurs Sep 10 Session 3 (2:40 – 4:00)
May joint with NBI
Friday 1 (09:00 – 10:30)
Room 1
 Rm2 YANG/JSON schema
Friday 2 (11:00 – 12:30)
- YANG/JSON schema
Friday 3 (2:00 – 3:30)
Room1 UML-YANG Mapping IM + TAPI joint 
Friday 4 (4:00 – 5:30)
Room1 OT-IM
  - YANG/JSON schema
Location
Monday Sep 7: Hosted by 2903 Bunker Hill Lane, Santa Clara (Diagonally opposite to Hyatt Regency)
Tuesday – Friday: Santa Clara Marriott 2700 Mission College Boulevard, Santa Clara, CA 95054, USA
Monday and Friday: Only two rooms available

6. Minutes – OTN TTP/CTP Refactoring
Kam reported on the progress of refactoring ITU-T G v2.08
Use the “Applied comments” field of object class to describe which attributes are related to which transport processes.
7/22/2015 snap shoot: onf , which covers refactoring of
ODUk_TTP: abstract, sink, source, bidirectional
ODUk_TTP-h: abstract, sink, source, bidirectional
ODUk_CTP: abstract, sink, source, bidirectional
ODUk_CTP-h: abstract, sink, source, bidirectional
ODUkT_TTP: abstract, sink, source, bidirectional
NIM, ODUk_NIM, ODUkT_NIM
Gcc0TerminationPoint, sink/source/ bidirectional,
Gcc12TerminationPoint, sink/source/ bidirectional
8/11/2015 snap shoot : onf , which covers refactoring of
DelayMeasurementCapability
OCh_TTP: abstract, sink, source, bidirectional;
OChr_TTP: abstract, sink, source, bidirectional
OCh_CTP: abstract, sink, source, bidirectional;
OChr_CTP: abstract, sink, source, bidirectional
OCh_NIM, OCT_NIM, OCTDk_NIM
OCh_SubNetwork, OCh_SubNetworkConnection, OCh_CrossConnection,
OCh_ProtectionGroup
OChClient_CTP: abstract, sink, source, bidirectional
ODUk_SubNetwork, ODUk_SubNetworkConnection, ODUk_CrossConnection
ODUk_ProtectionGroup
ODUkClient_CTP: Abstract, sink, source, bidirectional
ODUk: CD, HD
ODUkClient: CD, HD
ODUkT: CD, HD
ODUkTm: CD, HD
OMSn: CD, HD
OMSn_CTP: abstract, sink, source, bidirectional;
OMSn_TTP: abstract, sink, source, bidirectional;

7. Minutes – OTN TTP/CTP Refactoring
8/17/2015 snap shoot: onf , which covers refactoring of
OMSnP_ProtectionGroup, OMSnP_ProtectionUnit
OPS: CD, HD
OPSMnk: Abstract, sink, source, bidirectional
OPSn: Abstract, sink, source, bidirectional
OSx: CD, HD
OTM-n
OTN: CD, HD
OtnNetworkElement:
OTS: CD, HD
OTS: Abstract, sink, source, bidirectional
OTUk_CTP: Abstract, sink, source, bidirectional
OTUk: CD, HD,
OTUk_Fec: CD, HD
OTUk_NIM
OTUk_TTP: Abstract, sink, source, bidirectional
Next steps
Integrate the OTN fragment into CIM
TTP/CTP
Change the TTP/CTP object classes to become conditional packages; to be contained in LayerProtocol (after the OTN fragment has been imported into the CIM Papyrus Model Project)
PM CurrentData & HistoryData
Change the CD & HD object classes to become conditional packages and be contained in the corresponding TTP conditional packages
Forwarding: SN, SNC, XC, ProtectionGroup, ProtectionUnit
The Core model FD, FC, and Link object classes will be used for OTN forwarding.
Expect that the OTN SubNetwork, SubNetworkConnection, CrossConnection and ProtectionGroup object classes are not needed.
OTN-specific aspect, if any, will be modelled as conditional packages to be contained in FD, Link, or FC, similar to the approach for LTP / LP.
Question: Will there be LP under FD and/or FC?
If needed, will define LP-equivalent object class under FD, FC, Link, to allow attachment of layer-specific parameters
TCM & NIM
To be model as MEP
Do the same for G.8052 and G.8152 models
Decide on the approach for MEP/TCM refactoring (Next topic)

8. MEP/MIP/TCM/NIM Refactoring
Minutes
Coarse grain view of the MEP model
Fine grain view of the MEP model
Current assessment and recommendation
Coarse grain technology-specific base model is sufficient, in particular for future pruning/refactoring for interface-specific models
Fine grain model may be necessary for the development of machine interpretable Spec-model describing functional dependencies, e.g. for defect correlation
Will decide at the next meeting

9. Ethernet attributes and maintaining alignment in the common IM and DM
Minutes
As transport-technology-specific model fragments are being developed and will be integrated into the ONF CIM, the group discussed how to ensure alignment of the Ethernet fragment of the ONF CIM (and its ultimate Industry-wide CIM) with the Ethernet Data Models being developed in the various SDOs
The group recognizes the urgent need of coordination across the SDOs (ONF, ITU-T, MEF, IEEE, and IETF)
Functional level/area
Device/protocol (IEEE)
Equipment (ITU-T)
Network (TMF)
Service (MEF)
Modeling level
IM (critical mass in ONF) DM
Plan: First step
Identify and engage related experts from other SDOs under the MEF Unite “umbrella”
Action Item (Kam & Nigel): Draft a LS from ONF to MEF to stimulate the above

10. Thank You

11. OTN TTP/CTP/OAM Refactoring
Within each object class, the “Applied comments” field has been used to indicate which attributes are correlated