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

Gregory Mirsky <> Sat, 07 February 2015 02:29 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9F9591A1A38 for <>; Fri, 6 Feb 2015 18:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -104.2
X-Spam-Status: No, score=-104.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 12rf8S1HJW8y for <>; Fri, 6 Feb 2015 18:29:55 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E792C1A038C for <>; Fri, 6 Feb 2015 18:29:54 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-cb-54d5191085e8
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id D0.40.25146.11915D45; Fri, 6 Feb 2015 20:42:09 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0210.002; Fri, 6 Feb 2015 21:29:51 -0500
From: Gregory Mirsky <>
To: "Deepak Kumar (dekumar)" <>, "" <>
Thread-Topic: [Lime-oam-model] OAM Model analisys. First cut
Thread-Index: AdBAGLchPnwAqsj7QQeQPOqM2IiiYgAwQTcAAA0ky3A=
Date: Sat, 7 Feb 2015 02:29:51 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B8EF224eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyuXRPrK6g5NUQg5tNYhY/V31it+hZ3czs wOQx5fdGVo8lS34yBTBFcdmkpOZklqUW6dslcGWcPHaEtWBuesWSZx+ZGxj3R3UxcnJICJhI bLh/kxnCFpO4cG89WxcjF4eQwBFGiXfX+9ghnGWMElNb+1lBqtgEjCRebOxhB7FFBNIlGmd+ YgSxhQWsJWavms4GEbeR+HN1O5RtJbHx4wSwGhYBFYlf6/vA5vAK+Ep8eP6fBcQWEiiSmLVs NtgVnAL6EhP2bgGrYQS66PupNUwgNrOAuMStJ/OZIC4VkFiy5zzU1aISLx//Y4WwlSQmLT3H ClGfL/F7zn5GiF2CEidnPmGZwCgyC8moWUjKZiEpg4jrSCzY/YkNwtaWWLbwNTOMfebAYyZk 8QWM7KsYOUqLU8ty040MNzEC4+eYBJvjDsYFnywPMQpwMCrx8BrwXw0RYk0sK67MPcQozcGi JM5bduVgiJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGaeZ8XEaH/YTnR7lcNf3dpH9vq4nX aZGJ+u5HhJdrOurNS5rVe1iWQcj7k+IT1/P1RseLd1ZHhjHPMlvFaHU9cK5+t5FKovaMZ2fa j9xiKNn4KI5rtyGL4ormstb9LcIRNT/qL4h7cHkvK3Z9a22TkLTmic/aPyyz0vT3Kluu1D8U vTW0KVaJpTgj0VCLuag4EQDshtC3gAIAAA==
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: Sat, 07 Feb 2015 02:29:58 -0000

Hi Deepak,
many thanks for your suggestions and questions. Please find my notes in-line and tagged GIM>>.


From: Deepak Kumar (dekumar) []
Sent: Wednesday, February 04, 2015 6:23 PM
To: Gregory Mirsky;<>
Subject: Re: [Lime-oam-model] OAM Model analisys. First cut

Hi Greg,

Thanks for detailed Analysis. I have few queries.
In Metrics Is Lock is covered under Defect Indication?
GIM>> Frankly, I haven't thought of Lock. AFAIK, Lock is not to indicate a defect or failure but is the step to turn a service off of the given connection.
How's Test signal get covered?
GIM>> Do you refer to ETH-TST?
Should we talk about Throughput or as it's application ignore for now.
GIM>> Throughput measurement is not an operation but method that can be implemented using different operations.

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.
GIM>> Agree, will add.
For Eg:- Administrative Domain, OAM Technology Layer Type, Level (implicit or NA), MEP addressing and ECMP (Flow Entropy or Customer traffic information).
GIM>> In MPLS-TP Level is realized through SPME, which is a hack, IMO.
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).
GIM>> I think that Server and Client Layers are distinct only in
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.

GIM>> I agree that will be beneficial. To add to your point, having Defect data model shared among reviewed OAM models will help as well.


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.