Re: [Lime-oam-model] Design Team report

Qin Wu <bill.wu@huawei.com> Sat, 21 March 2015 18:40 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 32C6A1ACD37 for <lime-oam-model@ietfa.amsl.com>; Sat, 21 Mar 2015 11:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level:
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, 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 ESFJKuL8PI9i for <lime-oam-model@ietfa.amsl.com>; Sat, 21 Mar 2015 11:40:45 -0700 (PDT)
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 0B6A21ACD35 for <lime-oam-model@ietf.org>; Sat, 21 Mar 2015 11:40:44 -0700 (PDT)
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 BTZ16061; Sat, 21 Mar 2015 18:40:43 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 21 Mar 2015 18:40:42 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Sun, 22 Mar 2015 02:40:39 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Tom Taylor'" <tom.taylor.stds@gmail.com>, "'Ronald Bonica'" <rbonica@juniper.net>, "lime-oam-model@ietf.org" <lime-oam-model@ietf.org>
Thread-Topic: [Lime-oam-model] Design Team report
Thread-Index: AQHQYoJk3N7qFUQxyU+EYPD/wRsQwp0kpn3ggAAisICAAV47gIAAIt+AgAAzeACAADg2gIAAj8+Q
Date: Sat, 21 Mar 2015 18:40:38 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8470DAE7@nkgeml501-mbs.china.huawei.com>
References: <CO1PR05MB4422C6491A3B7179F229574AE130@CO1PR05MB442.namprd05.prod.outlook.com> <7347100B5761DC41A166AC17F22DF1121B92F482@eusaamb103.ericsson.se> <B8F9A780D330094D99AF023C5877DABA84702B17@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B92F643@eusaamb103.ericsson.se> <B8F9A780D330094D99AF023C5877DABA84704C4C@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B92FA5F@eusaamb103.ericsson.se> <B8F9A780D330094D99AF023C5877DABA847066E3@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B930603@eusaamb103.ericsson.se> <BLUPR05MB433DD2E1CBEDF363CB13884AE010@BLUPR05MB433.namprd05.prod.outlook.com> <B8F9A780D330094D99AF023C5877DABA8470BE79@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B9349F2@eusaamb103.ericsson.se> <550B2FEF.1030402@gmail.com> <B8F9A780D330094D99AF023C5877DABA8470D37B@nkgeml501-mbs.china.huawei.com> <550C13BD.60209@! gmail.com> <015f01d063b9$46c0bb80$d4423280$@olddog.co.uk> <550D56C9.1030! 406@gmail.com> <019a01d063e4$7443fb50$5ccbf1f0$@olddog.co.uk> <7347100B5761DC41A166AC17F22DF1121B937323@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B937323@eusaamb103.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.149.99]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/lime-oam-model/TLrBOb3rXlVuvAXGUebLN-7O5a0>
Cc: "'Deepak Kumar \(dekumar\)'" <dekumar@cisco.com>
Subject: Re: [Lime-oam-model] Design Team report
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: Sat, 21 Mar 2015 18:40:47 -0000

I think we can support both proactive mode and on demand mode by generalizing ping/traceroute rpc.

-Qin
-----邮件原件-----
发件人: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com] 
发送时间: 2015年3月22日 1:58
收件人: adrian@olddog.co.uk; 'Tom Taylor'; Qin Wu; 'Ronald Bonica'; lime-oam-model@ietf.org
抄送: 'Deepak Kumar (dekumar)'
主题: RE: [Lime-oam-model] Design Team report

Hi Adrian, et. al,
the only identified common OAM function identified so far is ping/traceroute. But this is, primarily, on-demand functions and do not require configuration but are, what is referred, long-running command, which is sort of challenge for Netconf  but not specific to LIME discussion. Configuration of OAM, as I think of it, is primarily for proactive OAM tools, e.g. BFD Async, TWAMP in IP. And that where I find RFC 7276 and attempt to extend TRIL OAM to IP and LDP-based IP/MPLS OAMs come short.

	Regards,
		Greg

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Saturday, March 21, 2015 7:37 AM
To: 'Tom Taylor'; 'Qin Wu'; Gregory Mirsky; 'Ronald Bonica'; lime-oam-model@ietf.org
Cc: 'Deepak Kumar (dekumar)'
Subject: RE: [Lime-oam-model] Design Team report

> Bottom line: I'm saying that the generic LIME model should be able to 
> trigger performance monitoring regardless of the layer under examination.

Well say "attempt to" because, if the layer doesn't support a particular OAM function, obviously it won't be triggered.
Similarly, if an implementation is missing that function.

But beyond that, yes, there is a set of generic OAM functions that need to be in the LIME model for config and enablement.
Since the model is generic and layer-independent, we would assume that the function set in the LIME model is a superset of the functions in any specific known layer.

A