| Time | Item | Who | Notes |
|---|
| IM-D | Admin | Kam/Nigel | - Year End 2017 call plan
- Discussed and agreed on the following plan:
- Keep Dec. 19 OT-IM call
- Keep Dec. 21 OIMT calls
- Cancel Dec. 26 OT-IM call
- Cancel Dec. 28 OIMT calls
- Cancel Jan. 2 call (Not available: Yuji, Rod, Andrea, Aikra)
- Keep Jan. 4 calls (Not available: Rod)
- 2018 meeting plan: Not change. See Face-to-Face Meetings
- Noted that the March 12 - 16, 2018 London meeting is the same week of the OFC San Diego meeting
- Action item - Kam: send email to the group to make aware of the overlap of the 12-16 March 2018 London meeting with the OFC San Diego meeting
- Posting of large file
- No problem with TR-512 draft and publication. The solution is:
- The TR-512 v1.3 suite will be published on the ONF public library.
- The draft of the TR-512 v1.4 suite will be segmented into small subset to fit the file size limitation of wiki posting
- Issue remain is posting of minute recording.
- Typical file size of a one-hour meeting is near 100 mb, which is way exceed the wiki limitation
- Bernd: Who needs to listen/view the meeting recording.
- Answer: Mainly Nigel and Kam for making the meeting minute more complete and accurate
- Kam: Attendees are welcome to update the wiki minutes page.
- Nigel: Need to ensure simultaneous editing. That will cause crash.
- Action item - Nigel: Will research the possibility of using GooglePage/Doc, which seems allow parallel editing
- Kam: In the meantime, please feel free to update the wiki minute page, either after the call or pause Kam while in the call
- Time for discussing UML-OpenAPI and UML-ProtoBuf review comments
- Kam reported on the current status of the group review and received comments.
- See below (v1.4 Topic) for the status
- Action - Chris and project leads (Nigel, Kam, Lyndon): To contact CORD & ONOS colleagues (Sapan/Scott/Andrea) to to ensure having feedback from them.
- Action - Kam: Schedule time for comment discussion. Set for January 4 Thursday OIMT IM-D slot
- MEF liaison (Andrea/Nigel)
- Nigel to get input from people at the ONAP meeting this week, and follow up with Andrea for closure
- ITU-T Q14/15 liaisons (Kam)
- The two LSs have been posted on the ARO Archive wiki page https://wiki.opennetworking.org/pages/viewpage.action?title=Liaisons&spaceKey=AA.
- Currently there is a problem with the access control. Access is denied even one logs into that page. Cassandra is working to resolve the problem.
- The LS is posted here temporarily.
- The LS to ONF (SG15-LS81: Liaison Statement on Information Modeling (to OIMT and OTCC Projects) has items relevant to OIMT:
- Requesting multi-layer examples. Related to TR-512.A.4, A.5, & A.6
- Media management model
|
| | Action from Nov. F2F Meeting | | - Core model ongoing work items (v3)
- Action items from Nov. 2017 Face-to-Face Meeting (v1)
- Kam reminded people to sign-up for the action items
|
| | v1.3.1 | | - #7: Layer examples (Xiang/Nigel):
- Nigel noted that he, Xiang, and Malcolm had worked on the layer examples during the London meeting last week.
- He present the figures and asked the group's opinion on how details the layer protocol stack should be shown in the figures. For example in the Figure 3-1 below
 - Should the ODU stacks be explicit or collapsed? For example,
- Explicit:
 i.e., showing all the "sub-layers" of the ODU2 protocol stack; or - Collapsed
 i.e., collapse all the sub-layers of the ODU2 protocol stack. Note that the properties of individual sub-layers are still modeled in the pacs.
- Decision from the group: Showing once at the begining all the sub-layers and the corresponding collapsed views. From then on, just use the collapsed view.
- Thus, the following figure (Figure 3-2) will be simplied.
 - Action - Nigel/Xiang: will update the figures
- Nigel already has the surrounding description text.
|
| | v1.4 Topics | | - #20: UML-OpenAPI Mapping Guidelines (Rick)
- Draft for group review (Nov. 17 - Dec. 2)
- Review comments & resolution
- #27: UML-ProtoBuf Mapping Guidelins (Chris)
- Draft for group review (Dec. 1 - 15)
|
| IM-E | TAPI Termination point model | Karthik | Not discussed. |
| | Wireless transport discussion | Martin | Not discussed - Model backward compatibility
|
| | v1.4 Topics | | - #1: Controller (Nigel)
- For TR-512.8
- Nigel presented the model sketch
- Key artifacts: ControlComponent, ControlPort, UserRole, ProviderRole, ControlSystemView, ControlTask
- ControlSystemView is a kind of ConstraintDomain
- ControlComponent is a kind of ProcessingConstruct;
- Has more details/specific with respect to the generic ProcessingConstruct
- Involve another entity (the thing being controlled)
- Other kinds of ProcessingConstruct are such as FC, C&SC, LTP, ...
- ControlPort: Talk to it about
- two roles: provider or user. Can have both on a ControlPort instance
- two type of controls: sysn and asyn;
- apply (act on): input constraint, output constraint
- retrieve
- Signal (notification) for Async
- G.8052 MeasurementJob is a kind of ControlTask
- #5: OAM
- Andrea reported in the progress: Had discussion, but no update yet;
- Action item - Andrea:
- Set delicated call(s) for discussion
- Assign sub-work-item to team members: Kam, Bernd, Malcolm, Xiang, Nigel, Yuji, Karthik, Scott
- #12: Entity Lifecycle
- A draft update has been produced; Got comments from Chris; further updates have been made; Will close with Chris on the commetns; Will share the draft in a OIMT call in January 2018.
- Still a long way, mainly what & where to document. Entity lifecycle is relevant to many entities. May be in an Appendix of TR-512.
|
| IM-F | Ethernet OAM | Kam | - Fix the schedule of discussion to IM-A
- G.8052.1
- Kam presented briefly the MEP Pruning & Refactoring sketch
- Discussed pruning of the ETH TTP & CTP classes
- ETH TTP and ETH CTP
- layerProtocolName, lpDirection, and terminationState: Need further thought. To check if the IEEE YANG already has support on these or not.
- alarmStatus, currentProblemList, and alarmSeverityAssignmentProfilePointer: Need further thought.
- Sketch-PR-TP diagram
- Discussion will be continued at the OTIM call next week
|
| | | Bernd | - Fix the schedule of discussion to IM-A
- IEEE 802
Bernd presented briefly the UML model of the IEEE cfm YANG module (re-engineered). It was pointed out that the UML Model - is still not complete
- contains all YANG artifacts
- mappings to be reviewed are highlighted in blue
- artifacts for which mappings are missing are highlighted in red
- attribute cardinalities are all [1] (Papyrus default) and still need to be set
The YANG modules which are imported by the cfm YANG module contain only those artefacts used in cfm; i.e., are not complete at all. - Discussion will be continued at the OTIM call next week
|
