Re: [Lime-oam-model] OAM Model analisys. First cut

[Gregory Mirsky <[e-mail]>]

Hi Qin,
IP and IP/MPLS networks are distinctly connectionless and their OAM models, in my view, share very little common elements with Ethernet OAM, which primarily serves transport, i.e. connection-oriented, network, as well as MPLS-TP.

                Regards,
                                Greg

From: Qin Wu [mailto:[e-mail]]
Sent: Wednesday, February 04, 2015 11:34 PM
To: Gregory Mirsky; [e-mail]
Subject: RE: OAM Model analisys. First cut

Sure, IP based OAM model and CFM based OAM model have different addressing,
CFM is originally designed for Ethernet technology. but CFM based OAM model support both connection less and connection oriented communication.
Becos Ethernet technologies support both connection oriented and connection less.

Regards!
-Qin
发件人: Gregory Mirsky [mailto:[e-mail]]
发送时间: 2015年2月5日 14:59
收件人: Qin Wu; [e-mail]<mailto:[e-mail]>
主题: RE: OAM Model analisys. First cut

Hi Qin,
there’s no surprise that CFM and Y.1731 follow the same model. Nor that MEF documents you’ve referenced so close to Y.1731, since Carrier Ethernet is, in fact and for practical purposes, Y.1731. And for those who followed MPLS-TP JWT strong resemblance of Y.1731 is not surprise either.
What I think we’re trying to establish is whether there is enough commonality between IP/IP-based OAM models and CFM/Y.1731/MPLS-TP/TRILL OAM.

                Regards,
                                Greg

From: Qin Wu [mailto:[e-mail]]
Sent: Wednesday, February 04, 2015 10:50 PM
To: Gregory Mirsky; [e-mail]<mailto:[e-mail]>
Subject: RE: OAM Model analisys. First cut

Here is my point.
Using any model from other SDOs as basis doesn’t mean we step into other SDO territory.
From Several reference document I listed, we can see what are LIME related work?
What commonality are they sharing?
e.g., IEEE 802.1Q based model is similar to Y.1731 based model
MEF 38 and MEF39 use 802.1Q based model, i.e., CFM model.
RFC6371 uses Y.1731 based model as basis.
We should not deny this fact, we should not neglect non-IETF work by worrying about stepping into other SDO territory.

Regards!
-Qin
发件人: Gregory Mirsky [mailto:[e-mail]]
发送时间: 2015年2月5日 14:30
收件人: Qin Wu; [e-mail]<mailto:[e-mail]>
主题: RE: OAM Model analisys. First cut

Hi Qin,
many thanks for your suggestion. I think that we should define the scope of our discussion. I believe that non-IETF technologies should be out of scope and only IETF ones analyzed. That is why I’ve included only IP, IP/MPLS, MPLS-TP and TRILL. If we to use the list of references, then we may be stepping into IEEE, ITU-T and MEF territory. Hope our WG chairs can clarify that.

                Regards,
                                Greg

From: Qin Wu [mailto:[e-mail]]
Sent: Wednesday, February 04, 2015 7:15 PM
To: Gregory Mirsky; [e-mail]<mailto:[e-mail]>
Subject: RE: OAM Model analisys. First cut

One thing I am surprising is there is no references have been provided for this analysis.
If we have all the referenced document put together, it will be easy to help us to find what
are common things in these various OAM technologies.
e.g., some references I can provide include:
a. IEEE 802.1Q
b. ITU-T Y.1731
c.  MPLS-TP OAM model in the section 4 of RFC6371
d. MEF-38 Service OAM Fault Management YANG Modules Technical Specification
e. MEF-39 Service OAM Performance Monitoring YANG Module Technical Specification

-Qin
发件人: Gregory Mirsky [mailto:[e-mail]]
发送时间: 2015年2月5日 3:55
收件人: Qin Wu; [e-mail]<mailto:[e-mail]>
主题: RE: OAM Model analisys. First cut

Hi Qin,
I believe that LIME charter is not to develop new OAM tools but to work on OAM data model that is relevant to all or some OAM models. If some OAM models do not have some of functions we find in other models, then we can flag that and discuss but in other group. The table you find in my writing is only start of what OAM model analysis may look like. I’d like the team to review it and help with comments and suggestions to extend the table. Then we can come to informed decision on what is common among IETF OAM models and discuss how useful data model of that common set may be.

                Regards,
                                Greg

From: Qin Wu [mailto:[e-mail]]
Sent: Tuesday, February 03, 2015 6:03 PM
To: Gregory Mirsky; [e-mail]<mailto:[e-mail]>
Subject: RE: OAM Model analisys. First cut

Greg:
What conclusion do you make from this analysis? Do you want to make BDI and FDI being supported as common OAM function? Or do you want to make linktrace and loop back layer independent? Aren’t linktrace and loopback Ethernet specific functions?
I think the example you give in the table 1 gets complete alignment with the Table 4 in the section 5.2 of RFC7276.
[cid:image001.jpg@01D041E8.573F51D0]
That is to say Continuity Check, Connectivity Verification, Path Discovery, Performance measurement are common OAM functions for the all the OAM technologies.
Besides Common OAM functions, we also have fault domain, test point, addressing, technology type, sub technology type, specific layer. They are all common things
for all the OAM technologies.

Regards!
-Qin
发件人: Lime-oam-model [mailto:[e-mail]] 代表 Gregory Mirsky
发送时间: 2015年2月4日 9:22
收件人: [e-mail]<mailto:[e-mail]>
主题: [Lime-oam-model] OAM Model analisys. First cut

Dear All,
apologies for belated update. Attached please find first cut of the proposal for approach to OAM Model comparison and example of it being used.

Your questions, comments, suggestions always welcome and greatly appreciated.

                Regards,
                                Greg