Re: [Lime] LIME OAM Yang Model Applicability

"Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com> Tue, 15 September 2015 01:41 UTC

Return-Path: <zhuangyan.zhuang@huawei.com>
X-Original-To: lime@ietfa.amsl.com
Delivered-To: lime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3C101B3A03; Mon, 14 Sep 2015 18:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.21
X-Spam-Level:
X-Spam-Status: No, score=-6.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, 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 onErsNrUlciO; Mon, 14 Sep 2015 18:41:15 -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 15E701A907E; Mon, 14 Sep 2015 18:39:22 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BXP62498; Tue, 15 Sep 2015 01:39:21 +0000 (GMT)
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 15 Sep 2015 02:39:20 +0100
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.52]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0235.001; Tue, 15 Sep 2015 09:39:13 +0800
From: "Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "draft-zhuang-lime-yang-oam-model-applicability@ietf.org" <draft-zhuang-lime-yang-oam-model-applicability@ietf.org>, "draft-zhang-mpls-tp-yang-oam@ietf.org" <draft-zhang-mpls-tp-yang-oam@ietf.org>, "draft-zheng-mpls-lsp-ping-yang-cfg@ietf.org" <draft-zheng-mpls-lsp-ping-yang-cfg@ietf.org>, "draft-zheng-bfd-yang@ietf.org" <draft-zheng-bfd-yang@ietf.org>, "draft-tissa-lime-yang-oam-model@ietf.org" <draft-tissa-lime-yang-oam-model@ietf.org>, "lime@ietf.org" <lime@ietf.org>
Thread-Topic: LIME OAM Yang Model Applicability
Thread-Index: AQHQ2ggK/psnkbXozky5uf8tJiH/c548qmhwgABN9IA=
Date: Tue, 15 Sep 2015 01:39:12 +0000
Message-ID: <9B4BC45FDEDDD84F813E9E4A5BAF8785937AD66C@nkgeml503-mbx.china.huawei.com>
References: <799A4873-B704-4F07-92AC-9E7FD35221FB@cisco.com> <7347100B5761DC41A166AC17F22DF112218CBD45@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF112218CBD45@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.135.170.230]
Content-Type: multipart/alternative; boundary="_000_9B4BC45FDEDDD84F813E9E4A5BAF8785937AD66Cnkgeml503mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/lime/ceg6xN6jcLbBQRPkxkEwIYFp6f4>
X-Mailman-Approved-At: Mon, 14 Sep 2015 18:43:52 -0700
Cc: "Benoit Claise (bclaise)" <bclaise@cisco.com>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "bfd-chairs@ietf.org" <bfd-chairs@ietf.org>
Subject: Re: [Lime] LIME OAM Yang Model Applicability
X-BeenThere: lime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." <lime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lime>, <mailto:lime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lime/>
List-Post: <mailto:lime@ietf.org>
List-Help: <mailto:lime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lime>, <mailto:lime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2015 01:41:17 -0000

Dear Greg, and all,

Thanks for the email to bring the applicability document discussion back to the mailing list.
Yes, we’re working on the update. It takes a little time to gather as many comments as we can from people in different groups, including authors of specific OAM models.

Here we’d  like to share the initial update 01 version *soon* for people’s review based on comments received until now. Apologize to keep you wait…

The proposed changes we have already made in the new version include:

l  Updates based on Greg’s comments (thanks Greg for your comments and suggestions).

l  Rewrite guideline section to tell the location in the common structure of LIME base model we can insert the data.

l  Separate MPLS-TP OAM from MPLS OAM, Add MPLS-TP OAM support.

l  Add performance management support in the base model structure.

Please let us know if you have any other suggestions on the scope of LIME applicability.

Regards,

Yan

发件人: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
发送时间: 2015年9月15日 4:56
收件人: Carlos Pignataro (cpignata); draft-zhuang-lime-yang-oam-model-applicability@ietf.org; draft-zhang-mpls-tp-yang-oam@ietf.org; draft-zheng-mpls-lsp-ping-yang-cfg@ietf.org; draft-zheng-bfd-yang@ietf.org; draft-tissa-lime-yang-oam-model@ietf.org; lime@ietf.org
抄送: mpls-chairs@ietf.org; bfd-chairs@ietf.org; lime-chairs@ietf.org; Benoit Claise (bclaise)
主题: RE: LIME OAM Yang Model Applicability

Dear All,
I haven’t seen any discussion after the invitation from LIME WG chairs. Earlier I’ve sent my comments to authors of the applicability draft and, I understand, they are working on the update. Perhaps it would be more productive if we start our discussion of the new, updated version of the applicability document.

                Regards,
                                Greg



From: Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com]
Sent: Tuesday, August 18, 2015 3:49 PM
To: draft-zhuang-lime-yang-oam-model-applicability@ietf.org<mailto:draft-zhuang-lime-yang-oam-model-applicability@ietf.org>; draft-zhang-mpls-tp-yang-oam@ietf.org<mailto:draft-zhang-mpls-tp-yang-oam@ietf.org>; draft-zheng-mpls-lsp-ping-yang-cfg@ietf.org<mailto:draft-zheng-mpls-lsp-ping-yang-cfg@ietf.org>; draft-zheng-bfd-yang@ietf.org<mailto:draft-zheng-bfd-yang@ietf.org>; draft-tissa-lime-yang-oam-model@ietf.org<mailto:draft-tissa-lime-yang-oam-model@ietf.org>
Cc: mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>; bfd-chairs@ietf.org<mailto:bfd-chairs@ietf.org>; lime-chairs@ietf.org<mailto:lime-chairs@ietf.org>; Benoit Claise (bclaise)
Subject: LIME OAM Yang Model Applicability

Hi, All,

I am starting this thread, based on a discussion during the LIME meeting in Prague and subsequent action item.

LIME (https://datatracker.ietf.org/wg/lime) has a deliverable as follows:
- Applicability document: The YANG model(s) specified in this working group must be usable and extensible by the existing OAM technologies. This usability and extensibility must be demonstrated, for example with IP Ping, traceroute, BFD, and LSP Ping. Note the technology-specific data model extensions should ideally be worked on in the respective working groups.
which basically builds a working dependency on efforts that are building protocol-based OAM YANG models.
Based on this, I am copying the authors of the following 5 documents, and the chairs of the target WGs:

  1.  LIME Applicability http://datatracker.ietf.org/doc/draft-zhuang-lime-yang-oam-model-applicability
  2.  LIME YANG Model http://datatracker.ietf.org/doc/draft-tissa-lime-yang-oam-model
  3.  MPLS http://datatracker.ietf.org/doc/draft-zhang-mpls-tp-yang-oam
  4.  MPLS http://datatracker.ietf.org/doc/draft-zheng-mpls-lsp-ping-yang-cfg
  5.  BFD http://datatracker.ietf.org/doc/draft-zheng-bfd-yang
The main goal of this note is to explicitly connect all these streams of work, and ensure there is coherence and alignment. As LIME defines a protocol-independent YANG model (1), the Applicability document (2) should show how the model can be used, extended, and augmented to realize protocol-specific ones (3) (4) (5).

We would be happy to help facilitate this dialogue, which BTW can take the shape of an informal meeting or a virtual interim (thinking aloud) before next IETF.

Discuss!!! :-)

— Carlos.