1. Open Transport Config and Control Project Agenda and Notes
Sep 11, 2017
Lyndon Ong

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: Guidelines.pdf 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 Policy-2016.pdf
Guidelines for all our meetings

3. Agenda Status Updates Any other business
recording started automatically
Status Updates
MEF SDK
Documentation work
Project Status
ONF procedures review
Future
Next call – Sept 24– 6:30am Pacific
Note registration open for the November CORD Build meeting
Review of November Meeting plans
Any other business
Note: MEF has announced TAPI-based LSO Presto SDK v2017R1
Thanks to Karthik, Andrea, Jack, et al

4. Documentation Design Team
TAPI 2.0 White Paper final version posted
Available on github and on OTCC wiki
High level description plus reference links
FRD
Draft text on Node Constraints
Draft text on Resilience
More detail on SC to be added
Updates to Terminology and Notification in progress
Other sections tbd
As before, please contact Lyndon if interested in helping on this

5. Project Status TAPI (Karthik) WT (Giorgio) OTIM (Kam)
RC2 release planned for this week
Work going on now on Spec models for ODU and OTSi
Alignment with ITU-T
Next version will hopefully be an official release (v2.0)
WT (Giorgio)
Extension of model – plan to issue new version of TR by end of year
Ethernet model – will be brought to OTCC attention
Started by identifying gaps, need to integrate with core model
Nader – should discuss with OTIM group
Kam – OTIM is forum to discuss this – OTIM slot better due to WT conflict with TAPI slot
Note IEEE has been working on PHY model
Should try to pin down where the work is done – Kam and Giorgio to work this out
Integration into broader architecture
Proposal from AT&T – integration into ONAP – investigating at Winlab – ODL-based
Will circulate pointer to Giorgio’s slides on this
OTIM (Kam)
Discussion with TAPI on ITU-T and Spec models for ODU and OTSi
Next focus will be Ethernet model discussion
Note next week will be ITU-T meeting, will have feedback

6. OTCC Structure OTCC Technical Steering Team Sub-Projects Notes:
The TST is approved by the Board and serves to steward OTCC overall directions
The TST provides a point of interface with other ONF and non-ONF groups
The TST will meet biweekly by uberconference to review project status
Sub-Projects
Technical discussion and work will primarily be done within Sub-Projects
Sub-Projects may organize conferences and discussions as needed to make progress
Can form ad hoc internal design teams for specific work – reports back to sub- project (?)
Issues that cannot be resolved within a Sub-Project can be elevated to the TST
Notes:
How to start new work within sub-projects – especially if overlapping with other groups – can be brought to TST for discussion
When/how to form new sub-projects?

7. OTCC Sub-Projects
OTCC currently has 3 Sub-Projects: Transport API (TAPI), Wireless Transport (WT) and Open Transport Information Modeling (OTIM)
TAPI Project (Karthik – Lead)
TAPI has as its goal to develop an common industry-standard “Application Programming Interface (API)” to program (configure and control) a Software Defined Network (SDN) for transport control applications.
WT Project (Giorgio – Lead)
WT has as its goal to develop a common information model for Wireless Transport products and integrate it with the broader transport architecture.
OTIM Project (Kam – Lead)
OTIM has as its goal to facilitate knowledge transfer of the base technology specifications (such as the ITU-T Recommendations for Media, OTN, Ethernet, MPLS-TP, Synchronization, Resilience/Protection, etc.) to be applied by the OTCC interface sub- projects such as TAPI and WT.

8. OTCC Document Approval
ONF Board (or future ONF TST) approval is required for TS and TRs
Informational documents such as White Papers, Reports, etc. can be published directly by OTCC on approval by the OTCC TST
Documents will be posted on the OTCC Wiki
They may also be publicized via, e.g., ONF Blog entries, listing on ONF site
Within OTCC any Technical Documents (e.g., TRs) will get at least 2 week Last Call via OTCC list
If there are significant technical comments this may require additional Last Calls
Once comments have been resolved TS or TR documents will be referred to ONF TST for approval
Informational Documents such as White Papers will generally get 2 week Last Call via OTCC list
If external deadlines are involved, this may be reduced to 1 week
Significant technical comments should still result in additional review

9. OTCC SDK Approval
SDK will follow a Release process using github/Jira to track issues, comments and resolution
The associated Sub-Project Lead will determine when baseline code is ready to be tagged as an Release-candidate (RC)
This will be driven by roadmaps and timelines
The RC will be reviewed and identified bugs/issues will be raised on github/jira
As many RCs will be generated as needed to fix identified bugs and issues
When the sub-project lead determines an RC to be stable (no significant issues pending), a 2 week “Last-Call” will be announced to OTCC list
If no more significant issues are identified or pending, the OTCC- TST would approve the RC to be tagged as an official release. The OTCC-TST could also determine that additional RC/Last-Call is needed before the release is official.

10. Other Groups
As in the past, the work will be closely coordinated with the ONF OIMT Project
OTCC will continue to collaborate with OIMT work on CIM and Tooling
ONF Leadership has emphasized the importance of coordination with other ONF work such as CORD, ONOS and vPOTS projects
Joint discussions and work (e.g., PoCs) is strongly encouraged
As with other ONF projects, there will be a focus on development of software (including SDK and reference implementations)
The group will continue to actively seek to make its work available for other interested bodies to use (e.g., MEF, OIF)

11. November Interim Meeting
The registration for the CORD Build event is now open.  Registration at: 
Registration is FREE if your organization is an ONF member.
“Open Transport Project” + “Open IM & Tooling Project” Meeting will be co-located with the CORD Build event at the QCT facility on Tuesday, Wednesday, & Thursday, and at the ONF Lab on Monday & Friday.
Note – registration and poll for M/F meeting needed
Note also plan for ITU-T meetings – see Kam’s notes

12. November (6-10) Workplan
CORD Build Event: November 7 – 9 (Tuesday – Thursday)
Venue
Google Facility: Quanta Cloud Technology (QCT), 1010 Rincon Circle, San Jose, CA 95131
Schedule:
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
Venue and host for Monday and Friday: ONF Lab
1000 El Camino Real #100, Menlo Park, CA 94025
The Glass conference room has been reserved, which can hold people comfortably
Monday 9:30 – 18:00; Friday 8:00 – 18:00
Expect less than 20
Invitation letter template for visa application: onf  

13. 2017 Quarterly Milestones 1Q17 2Q17 3Q17 4Q17
Update to OpenFlow extensions (tbd)
WP with OIF on TAPI demonstration
TAPI Technology Spec Models (in progress)
2Q17
4th Wireless Transport PoC (June)
TAPI White Paper (August)
OAM Modeling (incorporated into TAPI 2.0)
3Q17
TAPI 2.0 SDK – RC achieved – Release tbd
Update to TR-527 FRD (in progress)
4Q17
Alarm Models
Ethernet Spec
Wireless/TAPI PoC and ONOS/CORD PoC planning

14. Attendees Lyndon Ong Italo Busi Kam Lam Giorgio Cazzaniga
Andrea Mazzini
Nader Zein
Xiang Yun
Nigel Davis
Victor Lopez