Child pages
  • Contributions

ONF OIMT & OTCC 2018. 12 CA Interim Meeting Agenda Plan

Host: Infinera

Meeting Venue – Infinera facility: 220 Humboldt Ct, Sunnyvale, CA 94089

Registration : https://wiki.opennetworking.org/pages/viewpage.action?pageId=351338509

 

Timing

Monday – Thursday: P1 (9:00 – 10:30) break P2 (11:00 – 12:30) Lunch (12:30 – 13:30) P3 (13:30 – 15:30) break P4 (16:00 – 17:30)

Friday: P1 (9:00 – 10:30) break P2 (11:00 – 12:30) Lunch (12:30 – 13:30)

 

Room/Site allocation: Room Sydney

  • Monday:
  • Tuesday:
  • Wednesday:
  • Thursday:
  • Friday:

Remote Participation:

  • ZOOM to be provided:
    • URL:
    • International numbers available:

Key topics:

  • Reaching out: communicating with others, the CIM intro slide deck could be use. E.g., TOSCA, …, OpenConfig on photonic,
  • Future direction, including organizational and administrative aspects of the modeling/API work.
  • UML/Modeling/Core model introduction for external presentation
  • Task review
  • Criteria of version 1.x and 2.0
  • TR-512 v1.5
  • TR-512 v1.6 or v2.0
  • TAPI 2.2
  • TAPI 3.0
  • Modeling infrastructure and tooling

 

  • Future direction: Monday
    • Reach out
      • Internal: How can we be more relevant to ONF
      • External: Strategy for other standards bodies/Open source activities 
      • moving together
      • Moving more towards Intent and TOSCA – machine to machine interaction strategy
    • Strengthening the usage of patterns in solutions
      • Explore and apply/reject other patterns
  • Task Review
    •  
  • TR-512 v1.5 drafting & review
    • Model structure (Chris)
    •  
  • TR-512 v1.6 or v2.0 plan Tuesday - Thursday
  1. Review outstanding items from 1.5 (Kam/Nigel)
  2. LTP port (Nigel)
  3. Capability (Nigel)
  4. Strengthen the use of Component-Port pattern, e.g. port for LTPs (Nigel)
  5. Improve the Component-System pattern description and relation to TOSCA etc. (Nigel)
  6. Semantic versioning (Martin/Nigel)
  7. Event driven solutions (Chris/Nigel)
  8. Expressing capability and needs especially system/scheme spec (Nigel)
  9. Goal/Outcome and subgraph occurrence (Nigel)
  10. Interface architectural patterns (Nigel/Karthik)
  11. Interface generation tooling (Karthik)
  12. Pruning and refactoring method and tooling (Nigel)
  13. Model structure (Chris) 
  • TAPI 2.2 model review Tuesday - Thursday
    • Equipment (Nigel/Kam)
    • OAM model for TAPI (Andrea)
      • Including OAM model (normalized TCM, MEP, MIP)
    • Ethernet model update (Andrea)
    • OTSi media model (Nigel/Stephane)
    • Structural changes and issues (Karthik)
  • TAPI 3.0
    • Connection management (Karthik/Stephane)
  • Infrastructure and tooling Tuesday - Thursday
    • Backward compatibility (model + generated artefacts) (Martin)
    • Guideline work (Bernd)
      • UML modeling (including OCL)
      • Tooling consideration
      • UML to YANG mapping
      • Pruning/refactoring
  • Review & Summarize (1/2 day) Friday AM
    • Reach out and follow up
    • Review work items for next 6 months
    • Prioritize work list spreadsheet
    • Recap of action items from the F2F


 

Day

P

OIMT & OT-IM & TAPI Joint

Document

Mon

3 rd

 

20

1

Admin [10 minutes] (Kam/Nigel/Lyndon)

 

 

 

2

 

 

3

 

 

4

 

 

Tue

4 th

 

1

 

 

2

 

 

3

 

 

4

 

 

Wed

5 th

 

1

 

 

2

 

 

3

 

 

4

 

 

Thu

6 th

 

1

 

 

2

 

 

3

 

 

4

 

 

Fri

7 th

 

1

 

 

2

 

 

3

 

 

4

 

 

 

_____________________________