Greg The scope of the MEF specifications is the Ethernet Service Layer for Carrier Ethernet Services – Fault Management and Performance Management
Regards Don From: L2vpn [mailto:[email protected]] On Behalf Of Greg Mirsky Sent: Thursday, July 31, 2014 6:49 PM To: O'Connor, Don Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: Re: [nvo3] YANG models for OAM Hi Don, thank you for the reference. And I'd point that ITU SG15 is working on standardizing "generic protocol-neutral management information model" for transport network, including OAM. Hence my question, What is the scope of these documents? Regards, Greg On Thu, Jul 31, 2014 at 4:31 PM, O'Connor, Don <[email protected]<mailto:[email protected]>> wrote: Tissa, Greg, all Metro Ethernet Forum has already standardized Yang Modules for Ethernet Service OAM Performance Monitoring and Fault Management. Please see MEF 38 and 39 http://metroethernetforum.org/carrier-ethernet/technical-specifications Regards Don From: L2vpn [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Tissa Senevirathne Sent: Thursday, July 31, 2014 5:53 PM To: Greg Mirsky; Tissa Senevirathne (tsenevir) Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [nvo3] YANG models for OAM Greg Yes it is, generic YANG model steup the base framework. It can be extended to add tools as well as other elements as well technology deviations. Alarms etc either be part of this document will be a separate document that specifies them. That is the reason we have designed the model as modular as possible and extensible as possible. Please let us know if any of the parts are not extensible or not modular enough. Thanks Tissa On Thursday, July 31, 2014 3:17 PM, Greg Mirsky <[email protected]<mailto:[email protected]>> wrote: Hi Tissa, authors, et. al, I've read documents and would like to clarify scope of these documents. OAM is not limited to ping and traceroute functions. It even not limited to continuity check. And in connectionless networks there would not be connectivity verification. And the performance measurement is the big part of OAM as well as protection coordination, defect alarms, and etc. Hence my question, is it in plans of the authors to address all of OAM in respective documents? Regards, Greg On Tue, Jun 10, 2014 at 12:03 PM, Tissa Senevirathne (tsenevir) <[email protected]<mailto:[email protected]>> wrote: All We have published YANG model for OAM. #1 draft below place the generic framework for OAM, that can be augmented for different technologies. #2 and #3 are application of the concept to NVO3 and TRILL, 1. http://datatracker.ietf.org/doc/draft-tissa-netmod-oam/ 2. http://datatracker.ietf.org/doc/draft-tissa-nvo3-yang-oam/ 3. http://datatracker.ietf.org/doc/draft-tissa-trill-yang-oam/ Please review and share your comments Thanks Tissa _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
