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

Gregory Mirsky <> Wed, 04 February 2015 19:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 79E091A6EFE for <>; Wed, 4 Feb 2015 11:54:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.194
X-Spam-Status: No, score=-101.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_04=0.556, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, 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 c70uGioMyMx3 for <>; Wed, 4 Feb 2015 11:54:49 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ECA0A1A1B61 for <>; Wed, 4 Feb 2015 11:54:48 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-c0-54d219948a90
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 9F.18.25146.49912D45; Wed, 4 Feb 2015 14:07:33 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0210.002; Wed, 4 Feb 2015 14:54:45 -0500
From: Gregory Mirsky <>
To: Qin Wu <>, "" <>
Thread-Topic: OAM Model analisys. First cut
Thread-Index: AdBAGLchPnwAqsj7QQeQPOqM2IiiYgAA/89QACWrxLA=
Date: Wed, 4 Feb 2015 19:54:44 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_7347100B5761DC41A166AC17F22DF1121B8ED195eusaamb103erics_"; type="multipart/alternative"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJIsWRmVeSWpSXmKPExsUyuXSPt+5UyUshBrs6+S0ez13AatGzupnZ gcmj5chbVo8lS34yBTBFcdmkpOZklqUW6dslcGVs7utnK2jcyVbR9ia4gfH1XLYuRk4OCQET ibWN31kgbDGJC/fWA8W5OIQEjjBK/P9wnxXCWcYosevAdWaQKjYBI4kXG3vYQWwRgTCJh42z wGxhAS2JBacmMkLEtSU+/r3MBGFbSbzr3w9mswioSFx+cAyshlfAV2JS4x+obTMZJfpa7oCd xAk09OLjw2BDGYFO+n5qDVgzs4C4xK0n85kgThWReHjxNNQLohIvH/9jhbAVJfb1T2cHGcos 0M0osenuSahtghInZz5hmcAoMgvJrFnI6mYhqYMoype4er+THcLWkpjX8JsJwlaUmNL9ECqu KXFl8iEoW1ti2cLXzBC2rsT0CUfg6mcvf8UIYQOD8uqyaghbR6J37iJmZDMXMPKuYuQoLU4t y003MtzECIzrYxJsjjsYF3yyPMQowMGoxMO7QepiiBBrYllxZe4hRmkOFiVx3rIrB0OEBNIT S1KzU1MLUovii0pzUosPMTJxcEo1MNbftBTZczRjfu/U67yL/R1eznhYkcHEzDLPU8ZG636z r8IBc0ZZ+89qepfnKxZ1bDw363hWoPsaYZEbOjfbRfduOMBasmsPU2CRx/81P6WWTHLiXd3S vOWJ5Hb/l84xLRvMgjKMns3Rk77L8KDXRqNUYfmM5Sf33Hi/TUl49bP7UxYc0TbRfKnEUpyR aKjFXFScCABkB+CBzAIAAA==
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: Wed, 04 Feb 2015 19:54:51 -0000

Hi Qin,
I believe that LIME charter is not to develop new OAM tools but to work on OAM data model that is relevant to all or some OAM models. If some OAM models do not have some of functions we find in other models, then we can flag that and discuss but in other group. The table you find in my writing is only start of what OAM model analysis may look like. I’d like the team to review it and help with comments and suggestions to extend the table. Then we can come to informed decision on what is common among IETF OAM models and discuss how useful data model of that common set may be.


From: Qin Wu []
Sent: Tuesday, February 03, 2015 6:03 PM
To: Gregory Mirsky;
Subject: RE: OAM Model analisys. First cut

What conclusion do you make from this analysis? Do you want to make BDI and FDI being supported as common OAM function? Or do you want to make linktrace and loop back layer independent? Aren’t linktrace and loopback Ethernet specific functions?
I think the example you give in the table 1 gets complete alignment with the Table 4 in the section 5.2 of RFC7276.
That is to say Continuity Check, Connectivity Verification, Path Discovery, Performance measurement are common OAM functions for the all the OAM technologies.
Besides Common OAM functions, we also have fault domain, test point, addressing, technology type, sub technology type, specific layer. They are all common things
for all the OAM technologies.

发件人: Lime-oam-model [] 代表 Gregory Mirsky
发送时间: 2015年2月4日 9:22
主题: [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.