Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Date

20 February 2018

Attendees

Goals

  • Focus on the OTSi modeling per TAPI's need

Discussion Items

TimeItemWhoNotes
 OTSiKam
  • Kam presented oimt2018.KL.003.00_OTSi-MI.doc and briefly described the OTSi related management information elements (MI signals)
    • These MI signals are defined in G.798 (12/2017), including
      • The input MIs, which are configurable information elements,
      • The output MIs, which are read-only information elements
      • At the "source" functions, such as OTSiG-O_TT_So
      • At the "sink" functions, such as the OTSiG-O_TT_Si
    • In oimt2018.KL.003.00_OTSi-MI.doc, there are MIs for the other functions, such as
      • The OTS and OMS maintenance entities, the OTU, and related the adaptation functions.
      • Note that the MIs of the ODU-related functions are not listed in the table as they are not for the agenda of this call.
  • Recognizing these MIs need to be managed, the group moved on to discuss where and how OTSiA and OTSiG-O be represented by model artifacts in the model. Functional component figures from the ITU-T recommendstions were looked at
    • Figure 11-1/G.798
    • The following Figure 8-14/G.872 provides the similar but with additional details within the Media elements, including the monitoring points ("P"), which can be associated with the OMS-O and OTS-O maintenance entities.
    • The following Figure 8-15/G.872 shows in addition the OTSiA subnetwork and the coordination aspect of OTSiG and OTSiG-O.
    • The above figures and the TAPI figures were added into oimt2018.KL.003.01_OTSi-MI.docx.
  Karthik
  • Karthik decribed the current TAPI model of OTSi.
  • Overall, the discussion noted that the model seems in the right direction.

Action Items

  •