Re: [Lime] OAM Initiative: Situation
Benoit Claise <bclaise@cisco.com> Tue, 23 September 2014 16:05 UTC
Return-Path: <bclaise@cisco.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 AED321A8731 for <lime@ietfa.amsl.com>; Tue, 23 Sep 2014 09:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level:
X-Spam-Status: No, score=-15.286 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 M5TTorI4Qi8U for <lime@ietfa.amsl.com>; Tue, 23 Sep 2014 09:05:10 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 134A01A8733 for <lime@ietf.org>; Tue, 23 Sep 2014 09:05:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13227; q=dns/txt; s=iport; t=1411488309; x=1412697909; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=xv/2xsdHRM7dvY3w0z05jGkHDw21GhN4oAOMtUHb/2g=; b=gYRwZsM/QcUUJiyBwKzlIQXpMCOG9x4+5nq3UYJOiYcEXXJCLflL09ex xywbv2Jwf23mj3K7aUmTQJoN/KCUSNUDBRJJK347Hs2vSGHLWau2DRmwN QdvUyS6OuLMdbnIQTzAQWlAxjDLeEjfQAEMiSAlvbtBDxTeStB0d12uFK o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMEAAmZIVStJssW/2dsb2JhbABggkiBcIhcyEsBgSIBeoQDAQEBBC1BCgEQCxEEAQEKFggHCQMCAQIBNAkIBg0BBQIBAYg6w10BF48lEQFQBgGESwEEj0KJEIRKh0yOB4NkOy+BD4E7AQEB
X-IronPort-AV: E=Sophos;i="5.04,580,1406592000"; d="scan'208,217";a="182405713"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 23 Sep 2014 16:05:07 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s8NG56Fg009129; Tue, 23 Sep 2014 16:05:06 GMT
Message-ID: <54219A32.1070904@cisco.com>
Date: Tue, 23 Sep 2014 18:05:06 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>
References: <541817C4.6070100@cisco.com> <C02846B1344F344EB4FAA6FA7AF481F12ACEFF25@SZXEMA502-MBS.china.huawei.com>
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F12ACEFF25@SZXEMA502-MBS.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------060502030006040605070309"
Archived-At: http://mailarchive.ietf.org/arch/msg/lime/XFY0UptMIZIZl8GASQy2mX-KEzg
Cc: "lime@ietf.org" <lime@ietf.org>
Subject: Re: [Lime] OAM Initiative: Situation
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: <http://www.ietf.org/mail-archive/web/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, 23 Sep 2014 16:05:13 -0000
Hi Frank, See my reply in-line. > > Hi Benoit, > > I agree with your initial conclusion. > > I still have some further questions as inline, hoping to get your opinion. > > Thanks! > > B.R. > > Frank > > *From:*Lime [mailto:lime-bounces@ietf.org] *On Behalf Of *Benoit Claise > *Sent:* Tuesday, September 16, 2014 6:58 PM > *To:* lime@ietf.org > *Subject:* [Lime] OAM Initiative: Situation > > Dear all, > > LIME is a new mailing list, transitioning from TIME (in case you want > to read the archives). > As one of the first email to the list, let me summarize the current > situation. > > During the last IETF meeting, there were various discussions with > different audiences regarding this OAM initiative. > > Here is what we concluded: > 1. Building an OAM generic protocol is impractical for multiple reasons. > 2. It is desirable to have an unified view of OAM information at each > layer, in order to correlate information, and detect the faulty > element in the network path > 3. Consistent configuration, reporting, and presentation for the OAM > mechanisms makes sense. > 4. Using YANG as a modeling language is a logical choice. Note that > there are already some efforts in that direction > > */[Frank] : Before we define any YANG model for this objective, does > it need some basic Information Model definition firstly? Is the > Information model in the scope of this work?/* > [benoit] This is a very good question. In my charter reviews since I became OPS AD, I've been stressing the need to have an information model before specifying the data model(s), especially for WGs that still need to determine their management requirements: fault, configuration, accounting, performance? push/pull? OAM or not? ... Now, the LIME work is special: it's specific to configuration, and for configuration there is a primary language: YANG. The growing interest in YANG throughout the industry proves YANG is the right way to go. So I'm wondering if, in _this __SPECIFIC _(potential) WG, it's necessary to go with an information model first? I would say no, but could be convinced otherwise. > *//* > > > 5. A set of guidelines for future OAM developments would be welcome > for consistency sake > > */[Frank] : What kind of guidelines does here mean? Does the future > OAM developments only refer to OAM in management plane, or also > include OAM in data plane? I think maybe both./* > [Benoit] I would say both Regards, Benoit > > We also believe that there is sufficient interest to start working on > a charter proposal. > > Regards, Joel and Benoit (OPS ADs) >
- [Lime] OAM Initiative: Situation Benoit Claise
- [Lime] LIME Charter Propsosal v1 Qin Wu
- Re: [Lime] LIME Charter Propsosal v1 Qin Wu
- Re: [Lime] LIME Charter Propsosal v1 Romascanu, Dan (Dan)
- Re: [Lime] LIME Charter Propsosal v1 Qin Wu
- Re: [Lime] LIME Charter Propsosal v1 Qin Wu
- Re: [Lime] LIME Charter Propsosal v1 Stewart Bryant
- Re: [Lime] LIME Charter Propsosal v1 Ronald Bonica
- Re: [Lime] LIME Charter Propsosal v1 Susan Hares
- Re: [Lime] LIME Charter Propsosal v1 Stewart Bryant
- Re: [Lime] LIME Charter Propsosal v1 Qin Wu
- Re: [Lime] LIME Charter Propsosal v1 Jouni Korhonen
- Re: [Lime] LIME Charter Propsosal v1 Qin Wu
- Re: [Lime] LIME Charter Propsosal v1 Yuji Tochio
- Re: [Lime] LIME Charter Propsosal v1 Qin Wu
- Re: [Lime] LIME Charter Propsosal v1--Charter Des… Qin Wu
- Re: [Lime] OAM Initiative: Situation Xialiang (Frank)
- Re: [Lime] LIME Charter Propsosal v1 Xialiang (Frank)
- Re: [Lime] OAM Initiative: Situation Benoit Claise