Child pages
  • 2020-08-06 OIMT Meeting notes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Attendees

Agenda

  • Administrative
  • Security Audit 
  • Optical Amplifier modeling 

Discussion items

Time

Item

Who

Notes

IM-D


AdministrativeAll


Security Audit

Jonathan 

Presentation from Jonathan

  • Premise

  • The Three "As"

  • A bit more on Auditing

OA modelingItalo

Optical Amplifier (OA) modeling

  • Background:
    • In the current draft G.876, the focus of OA is mainly on the power amplification aspect, not on the connectivity aspect.
      •  ROADM port (bidirectional view)

       

      • iLA ports (bidirectional view)    


      • The current proposal in G.876 is thus to model the OA as an auxiliary object, similar to the modeling of the TCS (traffic conditioning/shaping) function in G.8052, where the TCS is modeled as an auxiliary object class.

        • The model could be further simplied by refactoring the OA auxiliary object into the OmsTtpSpec and OmsCtpSpec

    

  • Suggestion from the discussion
    • To model OA in genral as ForwardingConstruct (FC)
      • So that can have general consistency for all cases, including the case of distributed OA although which is not in the scope of the current version of the G.876 model
      • In the case where the FC doesn't need to be explicitly managed, it could be refactored into the LTP (such as the OMS TTP or OMC CTP) as part of the TP. This will achieve the same simplified result of the auxiliary object class proposal
    • To look at the example models of OA in TR-512.A.4
  • Next step
Next calls
  •  : 
    • Security audit
    • OA modeling
  •  : 

Action items

  •