| | TAPI OAM model | Andrea, Karthik | - TAPI UML & YANG on OAM
- Both drafts are on the Github
- TAPI OAM, based on ITU-T recommendations: X.739 (1993), Q.822,
- TAPI Ethernet, based on G.8052
- Question from Italo: Will TAPI use G.8052.1 & IEEE CFM or not?
- Undecided yet
- Depends on the interface. Device level (NE) interface, Network level interface
- MEF NRM OAM Information model (July 2018) is on Call for Comments till the end of September;
- The Draft is on MEF website wiki https://wiki.mef.net/display/LSO/Network+Resource+Model+-+OAM
- Should be reviewed so to forward our comments
- The NRM model is used to generate the use case (in NRP), sequence diagram, YANG, ...
- Overall OAM model, extend for TAPI Ethernet
- Andrea walked the group through some of the key aspects of the Draft MEF NRM OAM information model
     - Italo: raise concern on the definition of ME. In middle domain MEP is not visible, suggest don't use ME, just use MEP
- Slide deck: MEF NRM OAM v2.6.4.pptx (need MEF login) slide 2, slide 12
|