1. Services Area – Information Modeling
IMP Call Agenda & Minutes / 20 August, 2015 (Part I = 05:00 – 06:00 PDT) (Part II = 07:00 – 08:00 PDT)
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 – IMP (8/20 Thursday)
Administrative (<10 minutes)
2 one-hour slots
MWD agenda topics
Liaison LS-077: TMF TR-225 (defer to next week)
Liaison LS-076: OIF Response to T-API work (defer to T-API call)
ETSI NFV presentation (onf ) follow-up
Progress updates (<10 minutes)
NBI model comment resolution and document update
Model views
Papyrus version update - Mars in Git
Model profile update
State model
L3VPN (MWD)
Discussion
Tapi questions (20 minutes)
Directionality (20 minutes) (defer to next week)
Intent model (20 minutes) (defer to next week)
UML-Yang mapping (20 minutes)
AOB

5. Minutes – Administrative
Additional time for weekly IMP call
2 one-hour slots for every Thursday
Part 1: Thursday 5:00 – 6:00 Pacific
Part 2: Thursday 7:00 – 8:00 Pacific
Some members reported that they haven’t received the Part II call invitation yet. Kam to re-send the invitation again.
Only 7 members joined the first Part I call today.
Some members experienced difficulty in joining the audio connection. Reported to ONF staff.
MWD agenda
See next slide
Doodle poll for Monday and Friday attendance:
Liaisons
LS-077: Incoming TMF Liaison Statement that provides the TMF-TR225 Logical Resource Network Function Model R
Deferred to next week due to shortage of time
LS-076: OIF response to T-API work.
Ask for guidance on how to refactor the Core Information Model (CIM) so that identifiers as well as name spaces from UNI and E‐NNI reference points can be reflected in a purpose specific view of the CIM
Name space/identifier issue will be addressed in the T-API work /call together with IM team. Focus is on TRI and how this is represented in the model
ETSI NFV presentation (onf ) follow-up
Nigel had discussion with NFV IFA, including their need of extension to the model profile for supporting notification.
The NFV Profile needs have been added to the Open Model Profile version
This version will be used by all version of Eclipse (Luna and Mars).;
NFV IFA has started the modeling work. Will engage with NFV to work together on their modeling

6. 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 model
Thurs Sep 10 Session 1 (10: :30)
Thurs Sep 10 Session 2 (1:00 - 2:30)
Joint Wireless Mobile modeling discussion with OWTG and WMWG
Thurs Sep 10 Session 3 (2:40 – 4:00)
Joint T-API and NBI modeling discussion
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 and TAPI)  
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

7. Minutes – Progress
NBI Topology model comment resolution and document update
Nigel will complete the diagram updates by today.
Nigel and Kam will join the NBI call tomorrow and raise that the NBI document is not ready for review yet
Model views: No specific progress
Papyrus version update:
Steps of migrating from Luna to Mars in Git have defined and are being execute. The goal is to be completed before MWD meeting.
The Model Open Profile is being update. It will be version There are still some issues (lifecycle stereotype cannot be added to some UML constructs such as “comment”) and thus not ready for push to Git yet
State model
No progress
Latest requirement document is onf
Will be discussed on September 3 Thursday IMP call and also during MWD
L3VPN model
Will be discussed during MWD

8. Minutes –T-API questions (Part II call)
The discussion agreed that in the case where there is 1-1 relationship between LinkEnd and LTP (such as one Link per LTP), the role of LindEnd can roll into the LTP
In the discussion of Path (realization of FcHasLowerLevelFc), it was noted that the first release of T-API will not cover protection.
In depth discussion on clarifying the topology view and node view of ForwardDomain and why Tapi:Service and Tapi:Connection are contained in Tapi:Node instead of Tapi:Topology.
The output slide deck from the Aug 17 TAPI call were used for the discussion and further updated.
See slides 7, 8, 9, 10, and 13 of the embedded T-API slide deck

9. Minutes – Directionality Overview
Not discussed due to shortage of time
Defer to next week

10. Minutes – Intent model Not discussed due to shortage of time
Defer to next week

11. Minutes – UML-Yang Mapping (Part I call)
Bernd walked through the changes from 0.2 to 0.3 of draft v03 of the mapping document
Comments provided by Yun Xiang on pre- and post-conditions taken into account.
Open Model Profile YANG Extensions module added in section 6.2.
Link to new draft YANG package statement added in section
Comments provided by Italo Busi on the netmod list taken into account.
Comments provided by Ari Mark Sodhi on the netmod list taken into account.
Section “Mapping Issues” moved to subsection 4.11 in Mapping Guidelines.
passedByReference example added to Table 4.9.
Mapping examples added to all artifacts.
Mapping of UML Support and Condition added in section 5.4.
Re-engineered ietf-inet-types.yang and ietf-yang-types.yang added in Figure 4.1.
It will be posted on ARO
After the call, v03 was posted: onf _Mapping_Gdls_UML-YANG.03.docx
Scott will update draft-mansfield-netmod-uml-to-yang according to v03
Bernd noted that there are still many issues in v03, including many newly identified issues

12. THANK YOU!

13. Minutes – Discussion on L3VPN
No discussion during the call because of shortage of time
Progress update:
June 4: NBI team requested help from IMP team on modeling of L3VPN
June 8 Darmstadt discussion (see slide 13 of the meeting minute onf ):
Agreement: The VRF (virtual routing function) should be modeled as ForwardingConstruct
The embedded figure in slide 13 was from Italo capturing the discussion
Action items (Italo): Show how traffic is forwarded between two CEs of the same L3VPN attached to the same PE
July 30: Slides from Italo
Slide 1 is the same that was attached to the Darmstadt minutes (onf )
Slides 2 and 3 show the forwarding of traffic
Will be discussed during MWD

14. IMP 2015 YE Position, Goals and Deliverable Status
Section Subtitle

15. IMP 2015 YE Position Desired position of IMP by end 2015
We see at the end of 2015, the IMP group will be
Recognized as core to the definition of the SDN information/data and rationalization of that information/data which is itself recognized as core to ONF
Actively driving the open sourcing of the model and sharing at least part (including the open model profile) developed collaboratively with at least one other body
Seen as owners and drivers of key tooling and successful in driving tooled generation of at least one interface from the model demonstrating that interfaces no longer need be hand crafted
Seen as ODL “partners” and recognized as originators of critical information model for ODL
Seen as providers of model for intention based interfaces and engaged in demonstrating the flow from Forwarding Intention and adjacency intention through core model to an open flow network
Source of key topology elements in IETF
Seen as a critical part of the success of ONF

16. Service Area – Information Modeling
2015 Goals and Deliverables:
Activity Name
Activity Status
End Date
Owner
Comments
Core Model -Technical Requirement
Open
9/30/2015
(TR) Core Foundation Module
completed
3/31/2015
Nigel Davis
Published: TR-512
(TR) Core Network Module - Topology Subset
(TR) Core Network Module - Forwarding Subset
(TR) Core Network Module - Termination Subset
(TR) Notification Module
 TBD
(TR) Papyrus Guideline -Technical Requirement
Completed
Bernd Zeuner
Published: TR-515
(TR) Process Guidelines -Technical Requirement
Malcolm Betts
Published: TR-513
(TR) UML Modeling Guidelines
Published: TR-514
Pruning/ Refactoring/ Mapping
12/31/2015
1 (Code) Tooling Enhancement
5 months after fund received
No ONF funding.
Pending on alternative funding
2 (Code) UML-YANG mapping guidelines
Kam Lam
Onf
3 (Code) JSON/REST mapping guidelines
12/30/2015
4 (Code) OF-Switch mapping guidelines