1. Open Transport Config and Control Project Agenda and Notes
Sep 25, 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 ONF procedures review
recording started automatically
Recording link: to be added
Status Updates
Shift from uberconference to gotomeeting
Documentation work
Project Status
ONF procedures review
Future
Next call – Oct 9– 6:30am Pacific
Note November CORD Build meeting coming up
Review of November Meeting plans
Any other business

4. Various Many complaints about Uberconference Documentation work - FRD
Difficulty accessing, browser issues, poor resolution
Cassandra planning to switch to GoToMeeting
MEF has had good success with this
Note –Cassandra will set up regular webex for WT call until GTM avail
Documentation work - FRD
Now draft text on Node Constraints, Resilience and Virtual Network Service
Updates to Terminology and Notification in progress
Need work on OAM
As before, please contact Lyndon if interested in helping on this

5. Project Status TAPI (Karthik) WT (Giorgio) OTIM (Kam)
TAPI IM will be tagged as RC2 – updated OAM, resilience, ODU/OTSi spec models
May be changes due to discussions with MEF NRM/NRP
Expect another RC after RC2 – esp. spec model enhancements, plus possible feedback on core TAPI framework from MEF modeling folks
Need more explanation of the model in the FRD – connection/topology decomposition
Requests for location – could be geolocation, equipment (slot, etc.), address
Equipment model – incorporate into TAPI? Open for this – expansion of “control” or further erosion of the boundary between control and mgmt
WT (Giorgio)
Note ONAP includes AAI – active available inventory
Model – v1.1 for December – still working on what will be added
Joint session on Ethernet model with OTIM tomorrow
PoC – looking at AT&T proposal to integrate to ONAP (Telefonica also interested)
ODL controller would manage WT equipment and expose inventory to ONAP
OTIM (Kam)
Joint session on Ethernet PHY, also will discuss WT spec model
Also continuing on ODU/OTSi, Ethernet spec models
Q on MEF L2 service model – Andrea co-authoring this – complementary work

6. OTCC Structure (Updated)
OTCC Technical Steering Team
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:
If starting work within sub-projects – especially if overlapping with other groups – bring to TST for discussion
Formation of formal new subprojects may need ONF approval

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. Documents (New – to be aligned with OIMT)
Documents will be stored on the Wiki
Group working documents separate from contributions/presentations
If there are concerns about copyright of submitted material (contributions and presentations) these can be submitted in company template with copyright notice
Otherwise an ONF format can be used
Documents should be allocated numbers, e.g., onf-year- xxx_YY_briefTitle (to be discussed with OIMT) where
xxx is a 3 digit sequential number starting with 001
YY is the initial of the author in capital letters, e.g., JD for John Doe
The file name can be appended with .r1, .r2, etc. to indicate the revisions. (check what Confluence supports for search – could make some of this unnecessary, e.g., YY)

10. OTCC SDK Approval (Updated)
SDK will follow a Release process using github/Jira to track issues, comments and resolution
The associated Sub-Project group/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 group/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.

11. 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)

12. 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 – Kam if planning to attend M/F meeting

13. 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  

14. F2f meeting planning
Nigel to contact David about populating the Build registration site with more information - names

15. 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

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