Re: [Time] Editor's proposed draft of TIME/LIME Problem Statement

Qin Wu <bill.wu@huawei.com> Sat, 06 September 2014 09:38 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: time@ietfa.amsl.com
Delivered-To: time@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648371A01FF for <time@ietfa.amsl.com>; Sat, 6 Sep 2014 02:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.364
X-Spam-Level:
X-Spam-Status: No, score=-0.364 tagged_above=-999 required=5 tests=[BAYES_50=0.8, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] 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 0UEBauUOjYXA for <time@ietfa.amsl.com>; Sat, 6 Sep 2014 02:38:04 -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 C59A41A0201 for <time@ietf.org>; Sat, 6 Sep 2014 02:38:03 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJD11001; Sat, 06 Sep 2014 09:38:01 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 6 Sep 2014 10:37:58 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.209]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Sat, 6 Sep 2014 17:37:51 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "time@ietf.org" <time@ietf.org>
Thread-Topic: [Time] Editor's proposed draft of TIME/LIME Problem Statement
Thread-Index: AQHPyalU4JMG30eSaUSJISQbv/6P1Zvz0sfg
Date: Sat, 6 Sep 2014 09:37:50 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA845C0C01@nkgeml501-mbs.china.huawei.com>
References: <5409DA04.2020200@gmail.com>
In-Reply-To: <5409DA04.2020200@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
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/time/ixPn7nFPUIH3W_TuxOKt44zkoQw
Subject: Re: [Time] Editor's proposed draft of TIME/LIME Problem Statement
X-BeenThere: time@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <time.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/time>, <mailto:time-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/time/>
List-Post: <mailto:time@ietf.org>
List-Help: <mailto:time-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/time>, <mailto:time-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Sep 2014 09:38:06 -0000

Hi, Tom:
Yes, we need to split architecture and gap analysis from this draft and we need a clear scoped problem statement. 
Architecture will give us a whole picture for what consolidated management looks like.
I am happy to see this PS draft did discuss what architecture MUST define. I think It is a very good starting point.
I have shared some of my thoughts on the architecture through this list(e.g., model all the OAM technologies in the same way by applying some template).
I would be interested to know what other people think about the architecture for consolidated management?

Regards!
-Qin
-----邮件原件-----
发件人: Time [mailto:time-bounces@ietf.org] 代表 Tom Taylor
发送时间: 2014年9月5日 23:43
收件人: time@ietf.org
主题: [Time] Editor's proposed draft of TIME/LIME Problem Statement

Qin Wu drafted me as editor of the Problem Statement I-D.

There has been a lot of activity behind the scenes. When I  was brought into the picture, I was given a version -03 of draft-ww-opsawg-multi-layer-oam as a starting point. This built on the published -02 version but had a lot more text up front and in the future work section. It also dropped "Architecture" from the title, removing it as a focus.

My view was that the Problem Statement had to be tightly focussed precisely on that topic, and the future work section would become the core of a gap analysis document. This view was accepted. As a result, I have prepared an Editor's Proposal, draft-edprop-opsawg-multi-layer-oam-ps-00, which I plan to submit on Monday after some people have looked it over. It is much stripped down from the original text and has a lot of new text, but I hope it is not a shock to TIME/LIME participants. A key issue was extremely careful attention to terminology and nuances of meaning.

The concluding Problem Statement section is fairly brief, so I'll quote it here:

5.  Problem Statement

    Operators have a need for a management subsystem satisfying the
    objectives stated in Section 3.  The analysis presented above
    indicates that the solution lies in the direction of a consolidated
    management function that operates in the first instance on a
    technology and layer independent view of network and service
    performance.

    There is value in attempting to define an architecture for
    consolidated management that may reasonably be argued to meet the
    stated objectives.  If this attempt succeeds, it can be followed up
    with a gap analysis, which in turn will define a further program of
    standardization.

    At the detailed level, Section 4.3.1 and Section 4.3.2 deal with the
    matter of abstraction and its relationship to the specification of
    YANG modules.  This is work beyond the initial definition of
    architecture and awaits justification and prioritization by the gap
    analysis.  A similar consideration relates to the solution to the
    ECMP problem.

    The remaining issue is the OAM interworking issue identified in
    Section 4.3.3.  This is architectural in nature, and should be
    addressed by the proposed work on architecture.

Tom Taylor		

_______________________________________________
Time mailing list
Time@ietf.org
https://www.ietf.org/mailman/listinfo/time