Re: [Lime-oam-model] Design Team report

[Gregory Mirsky <[e-mail]>]

Hi Adrian, et. al,
the only identified common OAM function identified so far is ping/traceroute. But this is, primarily, on-demand functions and do not require configuration but are, what is referred, long-running command, which is sort of challenge for Netconf  but not specific to LIME discussion. Configuration of OAM, as I think of it, is primarily for proactive OAM tools, e.g. BFD Async, TWAMP in IP. And that where I find RFC 7276 and attempt to extend TRIL OAM to IP and LDP-based IP/MPLS OAMs come short.

	Regards,
		Greg

-----Original Message-----
From: Adrian Farrel [mailto:[e-mail]] 
Sent: Saturday, March 21, 2015 7:37 AM
To: 'Tom Taylor'; 'Qin Wu'; Gregory Mirsky; 'Ronald Bonica'; [e-mail]
Cc: 'Deepak Kumar (dekumar)'
Subject: RE: [Lime-oam-model] Design Team report

> Bottom line: I'm saying that the generic LIME model should be able to 
> trigger performance monitoring regardless of the layer under examination.

Well say "attempt to" because, if the layer doesn't support a particular OAM function, obviously it won't be triggered.
Similarly, if an implementation is missing that function.

But beyond that, yes, there is a set of generic OAM functions that need to be in the LIME model for config and enablement.
Since the model is generic and layer-independent, we would assume that the function set in the LIME model is a superset of the functions in any specific known layer.

A