Versions Compared

Key

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

Date

01 October 2018

Attendees

Goals

  • TAPI OAM (Andrea & Karthik)
    • Augmentation for Ethernet OAM
      • Relation to G.8052.1 & CFM 

Discussion Items

TimeItemWhoNotes
TAPI OAM ModelAndrea, Karthik
  • TAPI OAM
  • TAPI Ethernet OAM
    • Agreed update:
      • OamJob has 1..* OamServiceEndPoint (change from 1..2 to 1..*)
      • Remove ME (ME directly associated with Meg, Mip, and Mep only, no direct association to other classes)
      • OamServiceEndPoint unidirectionally associated with Mep and Mip, instead of bidirectional
      • OamService associated with 2..* OamServiceEndPoint (correct the previous typo of 1..*)
      • Add mepIdentifier and peerMepIdentifier attributes to OamServiceEndPoint

    • Open for investigation
      • Right now, OamService and OamServiceEndPoint are external view (view from the Orchastrator). Should there be also internal view of OamService and OamServiceEndPoint too?
    • Action item - Karthik Sethuraman & Andrea Mazzini: update the above meeting notes.
 Model relationshipKam
  • Discussed Italo's comment: What is the relationship of the TAPI Ethernet OAM model and the G.8052.1 model
    • Kam's response:
      • The TAPI Ethernet OAM model is a purpose-specific model.
        • The purpose: augmenting the TAPI OAM model with some of the carrier grade Ethernet OAM functionalities.
      • The G.8052.1 model is another purpose-specific model.
        • The purpose: augmenting the IEEE 802.1Qcx CFM OAM model with some of the carrier grade Ethernet OAM functionalities.

Action Items

  •