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

"Deepak Kumar (dekumar)" <> Thu, 05 February 2015 02:23 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B51071A01A5 for <>; Wed, 4 Feb 2015 18:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Up2sRbJedObP for <>; Wed, 4 Feb 2015 18:23:18 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E0EFD1A019B for <>; Wed, 4 Feb 2015 18:23:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=6984; q=dns/txt; s=iport; t=1423102998; x=1424312598; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=Jti2H62GoFZvFBN3DV0rOw4r/FmWi8LDxS8932dOKmQ=; b=QQl/sV1AsVBbn2GR6Ouj04yOlaf9Jmf9SE5HyMJuP3slbE/Oa3yMliHI uFdDOdzVr0K9OEwSAXSLfEhWwoxz3/FQVq23N9rNU/4Vd3oiDO+JQuBr6 lje80NFWLHEvpvjh2IHf/r0mdI8BkY+doY0ufUeZgvSGob0mbbtdgIRep 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.09,521,1418083200"; d="scan'208,217";a="120682844"
Received: from ([]) by with ESMTP; 05 Feb 2015 02:23:17 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t152NHTE013266 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Feb 2015 02:23:17 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Wed, 4 Feb 2015 20:23:16 -0600
From: "Deepak Kumar (dekumar)" <>
To: Gregory Mirsky <>, "" <>
Thread-Topic: [Lime-oam-model] OAM Model analisys. First cut
Thread-Index: AdBAGLchPnwAqsj7QQeQPOqM2IiiYgAwQTcA
Date: Thu, 5 Feb 2015 02:23:16 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D0F7D05CAB71Edekumarciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Lime-oam-model] OAM Model analisys. First cut
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LIME WG OAM Model Design Team <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 Feb 2015 02:23:21 -0000

Hi Greg,

Thanks for detailed Analysis. I have few queries.
In Metrics Is Lock is covered under Defect Indication?
How's Test signal get covered?
Should we talk about Throughput or as it's application ignore for now.

Metric is covering "Source Information/MEP ID" and "MIP ID", but we should also extend to add other metrics related to Administrative Domain and MEP for completeness.
For Eg:- Administrative Domain, OAM Technology Layer Type, Level (implicit or NA), MEP addressing and ECMP (Flow Entropy or Customer traffic information).

We should also add metrics for Server Layer, Client Layer and also concept similar to Server MEP (Which is lower layer of OAM sending AIS/LCK to upper layer to suppress Alarms).
Also this concept is useful in OAM interworking between different technology also.

I believe providing information regarding server layer in data model will allow application using data model to efficiently go down one layer at a time and Isolate the Fault.


From: Gregory Mirsky <<>>
Date: Tuesday, February 3, 2015 5:22 PM
To: "<>" <<>>
Subject: [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.