IETF Logo Mail Archive

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

Qin Wu <bill.wu@huawei.com> Wed, 04 February 2015 02:03 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: lime-oam-model@ietfa.amsl.com
Delivered-To: lime-oam-model@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3232C1A1BB0 for <lime-oam-model@ietfa.amsl.com>; Tue, 3 Feb 2015 18:03:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level:
X-Spam-Status: No, score=-1.204 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gIYq2j-8sziV for <lime-oam-model@ietfa.amsl.com>; Tue, 3 Feb 2015 18:03:41 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 258131A1B6C for <lime-oam-model@ietf.org>; Tue, 3 Feb 2015 18:03:39 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSB42881; Wed, 04 Feb 2015 02:03:38 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 4 Feb 2015 02:03:36 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Wed, 4 Feb 2015 10:03:29 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "lime-oam-model@ietf.org" <lime-oam-model@ietf.org>
Thread-Topic: OAM Model analisys. First cut
Thread-Index: AdBAGLchPnwAqsj7QQeQPOqM2IiiYgAA/89Q
Date: Wed, 04 Feb 2015 02:03:28 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA846D3149@nkgeml501-mbs.china.huawei.com>
References: <7347100B5761DC41A166AC17F22DF1121B8ECAE6@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B8ECAE6@eusaamb103.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: multipart/related; boundary="_004_B8F9A780D330094D99AF023C5877DABA846D3149nkgeml501mbschi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/lime-oam-model/-prrCdIOjeeuvZCPfd1ccrpUZsA>
Subject: Re: [Lime-oam-model] OAM Model analisys. First cut
X-BeenThere: lime-oam-model@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LIME WG OAM Model Design Team <lime-oam-model.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lime-oam-model>, <mailto:lime-oam-model-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lime-oam-model/>
List-Post: <mailto:lime-oam-model@ietf.org>
List-Help: <mailto:lime-oam-model-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lime-oam-model>, <mailto:lime-oam-model-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 02:03:45 -0000

Greg:
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.
[cid:image001.jpg@01D04061.D2466AE0]
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.

Regards!
-Qin
发件人: Lime-oam-model [mailto:lime-oam-model-bounces@ietf.org] 代表 Gregory Mirsky
发送时间: 2015年2月4日 9:22
收件人: lime-oam-model@ietf.org
主题: [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.

                Regards,
                                Greg

v2.23.0 | Report a Bug | By Email