Re: [Time] Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

[Qin Wu <[e-mail]>]

Greg:
Very good comment, this is something important we need to sort out first.
My initial thought to this, we adopt IEEE 802.1ag CFM model and apply these common definitions to both IP/MPLS and Ethernet, MPLS-TP.
Yes, segment OAM and end to end OAM is another common thing we need to sort out.

Regards!
-Qin
发件人: Gregory Mirsky [mailto:[e-mail]]
发送时间: 2014年6月18日 16:35
收件人: Qin Wu; [e-mail]
主题: RE: Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

Hi Qin,
I’d note that IP and IP/MPLS do not have definitions of MEP and MIP. These, Up and Down MEP and MIP, been only defined in Ethernet and MPLS-TP so far. Thus I believe that we should start with defining these, their location relative to traffic, ports, switching elements, and etc. Further, we should look whether IP and IP/MPLS support only e2e service OAM or Segment and/or Link, e.g. through OAM Levels as in Ethernet Service OAM model of IEEE/ITU-T. MPLS-TP, for example, does support Segment OAM though through SPME LSP.

                Regards,
                                Greg

From: Time [mailto:[e-mail]] On Behalf Of Qin Wu
Sent: Wednesday, June 18, 2014 12:36 AM
To: [e-mail]<mailto:[e-mail]>
Subject: [Time] Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

[cid:[e-mail]2F0D0]


Different level has different layer OAM. In the abstract level(i.e., Level3), we can use transport independent OAM. All these OAM at different level forms end to end OAM.