Skip to end of metadata
Go to start of metadata

Date

08 May 2018

Attendees

Goals

Discussion Items

TimeItemWhoNotes
Admin
  • 2018 June 11 - 15 ONF OIMT & OTCC Ottawa Meeting
  • Agenda plan
    • Key topics: The following key topics were identified
      • Reviewing TR-512 v1.4 for publication
      • Future strategic direction
        • Moving more towards Intent and TOSCA – machine to machine interaction strategy
        • System spec / schema spec and relation to TOSCA (e.g., generalizing the LTP, FC, PC specs)
        • Strengthening the usage of patterns in solutions
        • Submit suggestion before hand
      • TAPI 2.1 model review
        • OAM model for TAPI
        • Ethernet model update
        • OTSi media model
        • Equipment model
      • OAM model (normalized TCM, MEP, MIP)
      • Guidelines
        • Tooling consideration
        • Backward compatibility
        • UML modeling
        • UML to YANG mapping
        • Pruning/refactoring
    • Initial draft agenda plan: oimt2018.KL.005.00.june-agenda-plan
 EthernetKam
  • IEEE 802.1Qcx CFM YANG Data Model
    • Kam noted that IEEE 802.1 has liaised to ITU-T Q14/15 that IEEE has formally started the P802.1Qcx CFM YANG project and the YANG modules is in GitHub at https://github.com/YangModels/yang/tree/master/standard/ieee/802.1/draft.
    • Kam noted that the YANG module on the GitHub is the same version that Bernd used to re-engineered into UML, i.e., the 2018.03.12 version.
    • Kam showed the high-level UML class diagram

    • Kam noted that the IETF Interface class, IEEE MEP, and IEEE MIP should be the anchor class for augmenting the ITU-T G.8013/Y.1731 Carrier Grade Ethernet OAM functionalities, i.e., the G.8052 defined artifacts.
    • RFC-8343 IETF Interface "bidirectional"
  • G.8052.1 UML
    • Kam then showed the high-level augmentation model of G.8052.1 for augmenting to the IEEE 802.1 model

      • The G.8052.1 augmentation model consists of the following main parts
        • Termination: The EthernetTpSpec augments the IETF Interface class for specifying the G.8052 TP properties.
          • Kam noted that in the 5/1/2018 OT-IM call last week, there was comment that the IETF Interface is uni-directional and point-to-point only and thus was not appropriate to augment the IETF Interface with bi-directional TAPI Pacs (namely EthCtpPac, EthTerminationPac, EtyTerminationPac). Therefore he has modified the augmentation approach and now the EthernetTpSpec contains undirectional Pacs (namely EthCtpSiPac, EthCtpSoPac, EthTtpSiPac, EthTtpSoPac, EtySiPac, & EtySoPac)
          • Karthik noted that in IETF RFC8343, the IETF Interface has "in" and "out" statistics and thus seems to be bi-directional.
          • Kam noted that the current approach has the flexibility and allow augmenting to either unidirectional or bidirectional base class.
        • MEP: The EthMepSpec augments the IEEE MEP for specifying the G.8052 MEP properties and Measurement Job properties.
          • He noted that the G.8052 measurement job model the loss measurement (LMM/LMR, CCM, SLM/SLR, 1SL) and delay measurement (DMM/DMR, 1DM), including proactive and on-demand. The loopback, link trace, etc. are maintenance job (i.e., not measurement job) and defined as operations in G.8052

        • MIP: The EthMipSpec augments the IEEE MIP for specifying the G.8052 MIP properties
        • Operations: The EthMepInterface and EthMipInterface UML Interface consolidate the G.8052 operations from the static object classes into the G.8052.1 dynamic behavioral Interfaces.
          • Kam noted that he expects many of the operations, such as the CRUD (create/retreive/update/delete), will not be needed.
          • Bernd reminded that some of the CRUD operations have input parameters that are needed and should be retained.
          • Kam replied that these parameters may be refactored as properites of the Pacs.

      • Kam noted that in the Q14/15 & Q12/15 Nanjing interim meeting next week (May 14-18), they will work on the pruning/refactoring of the atrributes and operations.
      • Italo mentioned that the Dec. 2017 London Q14/15 interim meeting already started pruning/refactoring some of the attributes.
      • Kam noted that yes, those result will be taken into consideration at the Nanjing meeting.

Action Items

  •