Re: [trill] [nvo3] YANG models for OAM

"Tissa Senevirathne (tsenevir)" <> Thu, 31 July 2014 23:49 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id AFFC91A0080; Thu, 31 Jul 2014 16:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tDh5YZej6E02; Thu, 31 Jul 2014 16:49:06 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7BB171A0301; Thu, 31 Jul 2014 16:49:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=19801; q=dns/txt; s=iport; t=1406850544; x=1408060144; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Svw2C60Lw80f7gy7vE3gbzXzQZOfSehj3k6z268wzis=; b=ccyoKFSB6y6+ZdMKxvTKU9KZXMh2zjvSVtaVheLKkYFEphcCksdRttAj 64DQrHzpVyNim+CRbohcg+uwfT4pwhoWFokXx5WXJt6B67sLu+gIhWtqa kdDWk5qHX7CksEGILxNgNpTqno4os0OGXjqrXxIWy6RTPMJ4s3uOG31cS I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.01,775,1400025600"; d="scan'208,217";a="344292690"
Received: from ([]) by with ESMTP; 31 Jul 2014 23:49:03 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id s6VNn3Ia024256 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 31 Jul 2014 23:49:03 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Thu, 31 Jul 2014 18:49:03 -0500
From: "Tissa Senevirathne (tsenevir)" <>
To: "O'Connor, Don" <>, Tissa Senevirathne <>, Greg Mirsky <>
Thread-Topic: [nvo3] YANG models for OAM
Thread-Index: Ac+E3qlMyPi638vnRGmjYh75Wx+edAoWIbcAAAE6agAACU5iwAAR6gcA
Date: Thu, 31 Jul 2014 23:49:03 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_FBEA3E19AA24F847BA3AE74E2FE193562EEE0F1Bxmbrcdx08ciscoc_"
MIME-Version: 1.0
Cc: "" <>, "" <>, "" <>, "" <>, "" <>
Subject: Re: [trill] [nvo3] YANG models for OAM
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Jul 2014 23:49:08 -0000


I am aware of that, but this is different, MEF YANG model is specifically for Ethernet and structure does not allow to bring different addressing schemes other than MAC address. Additionally the proposed standard allow to add flow entropies and facilitate nested OAM between different technologies. You may have to read in to the details to see the actual differences.

From: O'Connor, Don []
Sent: Thursday, July 31, 2014 4:32 PM
To: Tissa Senevirathne; Greg Mirsky; Tissa Senevirathne (tsenevir)
Subject: RE: [nvo3] YANG models for OAM

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



From: L2vpn [] On Behalf Of Tissa Senevirathne
Sent: Thursday, July 31, 2014 5:53 PM
To: Greg Mirsky; Tissa Senevirathne (tsenevir)
Subject: Re: [nvo3] YANG models for OAM


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.


On Thursday, July 31, 2014 3:17 PM, Greg Mirsky <<>> 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?

On Tue, Jun 10, 2014 at 12:03 PM, Tissa Senevirathne (tsenevir) <<>> wrote:

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,


Please review and share your comments


nvo3 mailing list<>