2020-06-25 OIMT Meeting notes

Action items of the April 13-17 vMeeting and forward planning

Nigel Davis 

Nigel reported that

• The discussion of a minor issue in the TAPI LAG UML model (See 2020-06-23 TAPI Meeting notes) led to comparison with the inverse multiplex model in the core model (TR-512.2 section 4.2.3). 
• In the TAPI discussion, it was agreed that there may be an oversimplification in the current TAPI model.
• There will be follow up discussion in TAPI in two weeks. 

Nigel noted that 

• MEF is using LAG as a solution for port/link protection (See https://wiki.mef.net/display/CESG/Protection+and+Resiliency)

Inverse multiplex and link aggregation functional and information models

• ONF TR-512.2 Section 4.2.3 Inverse mulitplexing IM representation
  • 
• ONT TR-512.A.6  (Figure 4-3 LAG as Ethernet example)
  • 
• ITU-T G.8021 LAG function (Figure 9-70 – Generic functional model of Ethernet LAG)
  • 
• ITU-T G.8052 LAG model (Figure 7‑32 – Generic info model of Ethernet LAG (based on G.8021 Fig. 9-70))
  • 
• IEEE 802.1AX-2008 (Ethernet LAG sublayer)
  • 
• ONF_T63
  • 

Discussion occurred on whether traffic load is evenly distributed among all available links or some links are spared for protection prupose.

Will explore more indepth modeling of Inverse multiplexing and LAG

• 23 Jul 2020  Hing-Kam Lam Chris Hartley Model of flow-based inverse multiplex (Ethernet LAG). Also look into the dynamic protection aspects.
• 23 Jul 2020 Malcolm Betts Nigel Davis Jonathan Sadler Model of whole-signal-based inverse multipex, including FlexE/OTN/SDH/. Also look into the dynamic protection aspects.

• Skip July 2nd call
• 09 Jul 2020 : Security auditing
• 16 Jul 2020 
• 23 Jul 2020 : Inverse multiplex / LAG models