1. Pages
2. …
3. Open Transport Configuration and Control Home
4. OTCC
5. OTCC Meeting Notes

2019-03-04 OTCC TST Meeting notes

•  ODTN OFC Demo - Monday 3/4 OFC Demo Zone (Andrea)
• Tuesday 3/5 Exhibit Hall Theater III session, Disaggregated Transport/TIP (Victor)
• Thursday 3/7 Exhibit Hall Theater II session, OIF Interop Testing Review (Lyndon, Victor)

• Held F2F meeting in Madrid
• Information Modeling discussion
  • Seems agreement on using UML as well as YANG
  • Modeling tools under discussion: PlantUML vs. Papyrus - suggested consulting with IISOMI, OIMT
    • suggest inviting them to OIMT on Thursday, or alternatively IISOMI if Wednesday is better
    • Tracy notes multiple tools might be used - e.g., one tool (Papyrus) for UML, another tool for sequence diagrams
    • ONAP strongly behind Papyrus for UML/IM but use another tool for sequence diagrams
    • Petr notes one tool might be simpler if that's possible, also good to invite Bernd into discussion
  • pointing towards 3GPP models as basis
  • link to Core Model through 3GPP UIM? Nigel asking SA5 chair for more information
• Joint PoC planned using Open FH M-Plane spec and ONAP controller, will involve YANG models from M-Plane spec for RU components
  • hope is to deconstruct some of the models to make them more generally usable

• OIF still discussing possible TAPI certification

• Update on TAPI (Karthik)
  • Note received comments that documentation is lacking on some of the additions that have been made to TAPI - should we institute a policy to require submitters to also provide documentation? (For discussion continue on TAPI call).
    • need people to work on this, currently not enough resources - need to document usage
    • also comment that usage for multilayer could use more common agreement (by design we provide multiple options)
      • maybe more an Implementation Agreement type of topic (OIF?)
  • Working on 2.2 release items, targeted for RC1 at end of March, full release end of May
  • Contents basically the same as before: OAM updates, Photonic Model updates, LLDP model (new), Equipment model (new)
• Update on OIMT (Kam)
  • Ethernet IEEE CFM YANG and ITU-T Carrier OAM G.8052.1 IM/YANG
  • Continue jointly the monthly coordination calls. Last one was on Feb.18.
  • The latest IEEE 802.1 CFM YANG (version 2019.01.17) is now available onhttps://github.com/YangModels/yang/tree/master/standard/ieee/draft/802.1. Same content as the 2018.12.10 version. Just moved to the new restructured Github repository directory.
  • The latest draft G.8052.1 is v0.08 available at  https://www.itu.int/ifa/t/2017/sg15/exchange/wp3/q14/2018.11-2019.06_eMeetings_Modeling/cd/cd06r3_g8052.1_v0.08draft_2019.02.18.docx. This version finished the initial round of pruning/refactoring of the MEP, MIP, and Operations from the base G.8052 OAM. The next step is to provide the YANG mapping for the G.8052.1 UML.
  • The next monthly coordination call is 1400 – 1500 Geneva time on March 11, 2019. Note that US daylight saving starts on March 10, 2019, so the time of the call is 09:00 – 10:00 US EST. The G.8021 editor Akira Sakura (NEC) will provide a detail gap analysis between the CFM YANG and ITU MI_signals.
• Update on MW (Giorgio & Thorsten):
  • TR 532v1.1 has cleared sub-project review with minor comments (Thorsten as editor)
  • an updated version is now available and Thorsten has started an OTCC level review/Last Call going for 2 weeks (until 3/18)

  • Tr532v1.1_1.1.0-tr532v1_1.190204.1013+tr.190304.1201.docx can be found on the sub-project's page on the ONF Wiki

    https://wiki.opennetworking.org/display/OTCC/Wireless+Transport+working+documents
    
    

- Detailed report of PoC MW (Nov 2018) will be distributed this week
- Under analysis the change requests to be included in the next TR-532 2.0
- Under discussion the proposal by Thorsten for

o   splitting the MW model into one model per *_Pac (currently 6 together), splitting would enable these to be used separately

(Example is: Being able to use the EthernetContainer_Pac from the MW model also in the Ethernet PHY model.)

o   switching to referencing to models in the TR document instead of listing all attributes of a single UML (helps better matching of UML and YANG, also could reference other models from other sources)

o   extending the scope of the TR-532, e.g. on the wireless transport connections (e.g. technology specific extensions to the ForwardingConstruct) and further interfaces (technology specific extensions to the LP) for being able to manage the entire wireless device.

Kam notes ITU has synchronization model that may be helpful, reference is G.7721 - https://www.itu.int/rec/T-REC-G.7721-201811-P/en - has been liaised to ONF so should be avialable through link in ONF Incoming LS wiki page: Liaisons

• SG15-LS163: https://wiki.opennetworking.org/download/attachments/287997985/SG15-LS163.docx?version=1&modificationDate=1541102622000&api=v2
  • In the dropbox link (https://www.dropbox.com/sh/5r5j0lqn3vpgp8u/AAA0stzx8ETd3KrKDHOF_F-4a?dl=0), look for ols163-att-3-PLEN-0300R1.docx, which is the consented version of G.7721 that was then approved.

Further on,

-          there is a discussion about how to develop models in regards to backward compatibility in the WTP. Proposals include 1) ignore 2) make periodic breaks 3) sliding window for each new version identifying deprecated attributes and eventually deleting them - should be discussed with other teams as well - may need to be coordinated with lifecycle states

-          First review of TR-541 Ethernet PHY has been executed. Feedback has been consolidated during and after the review period. Most issues already closed. 

• Update on DMIP (Thorsten)
  • Very little open issues on TR-545 DMIP. Weekly call is shared with discussions about TR-541 Ethernet PHY. Discussion about Automated Commissioning is on-going.